Re: Stack dropped 200 for INVITE

Hi Lebing,

The URI 
sip:[email protected]:5064;caller="sip:[email protected]" 
is invalid because " may not appear unencoded in a URI parameter value (nor 
may '@'). You should use 
sip:[email protected]:5064;caller=%22sip:9223%40193.175.134.86%22

Ranga: It would be reasonable for the stack to perform such escaping (our 
implementation does)

Regards,

Jeroen


----- Original Message ----- 
From: "Lebing Xie" <[email protected]>
To: "M. Ranganathan" <[email protected]>
Cc: "sip mailing" <[email protected]>
Sent: Wednesday, May 10, 2006 4:14 PM
Subject: Re: [nist-sip] Stack dropped 200 for INVITE


> Hi, Rang
>
> The URI is:
> sip:[email protected]:5064;caller="sip:[email protected]"
>
> but the URL Parser (gov.nist.javax.sip.parser.AddressParser L33) return:
> sip:[email protected]:5064;caller=
>
> urs Lebing
>
>
> Error Log:
>
> Expecting >>>><<< got >>>"<<< java.text.ParseException: From:
> <sip:[email protected]:5064;caller="sip:[email protected]">;tag=599416 
> Expecting >>>><<< got >>>"<<< at 
> gov.nist.core.LexerCore.match(LexerCore.java:248) at 
> gov.nist.javax.sip.parser.AddressParser.nameAddr(AddressParser.java:38) at 
> gov.nist.javax.sip.parser.AddressParser.address(AddressParser.java:86) at 
> gov.nist.javax.sip.parser.AddressParametersParser.parse(AddressParametersParser.java:29) 
> at gov.nist.javax.sip.parser.FromParser.parse(FromParser.java:34) at 
> gov.nist.javax.sip.parser.StringMsgParser.parseMessage(StringMsgParser.java:555) 
> at 
> gov.nist.javax.sip.parser.StringMsgParser.parseSIPMessage(StringMsgParser.java:327) 
> at 
> gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:235) 
> at java.lang.Thread.run(Thread.java:595)
>
>
> On Wed, 2006-05-10 at 08:41 -0400, M. Ranganathan wrote:
>> Lebing,
>>
>> That is odd! Seems  to work fine and your branch is fine too. Check in
>> the debug log to see if there was an error in parsing the response
>> (resulting in the response being dropped). If this is not the case,
>> mail  me a debug log and I can figure it out.
>>
>>
>> Ranga
>>
>> Lebing Xie wrote:
>>
>> >Hallo,
>> >
>> >JAIN-SIP-1.2 stack(CVS yesterday) dropped the 200 for INVITE (Lister did
>> >not get the ResponseEvent). Stack tried to retransmit INVITE for a while
>> >and got a transaction timeout later. BranchID in 200 seemed OK, any idea
>> >about it?
>> >
>> >thanx, urs Lebing
>> >
>> >
>> >
>> >
>> >************ INVITE ************
>> >
>> >Session Initiation Protocol
>> >Request-Line: INVITE
>> >sip:[email protected];voicexml=http://193.175.134.83:8080/vxml/mailbox_main.vxml
>> >SIP/2.0
>> >Message Header
>> >Call-ID: [email protected]
>> >CSeq: 1 INVITE
>> >From:
>> ><sip:[email protected]:5064;caller="sip:[email protected]">;tag=657366
>> >To:
>> ><sip:[email protected];voicexml=http://193.175.134.83:8080/vxml/mailbox_main.vxml>
>> >Via: SIP/2.0/UDP
>> >pellmell.open-ims.org:5064;sipseesessionid=1ir0oxwe30s0i;branch=z9hG4bKaf12489b1bb84bdb2daf3d7a997d74ac
>> >Max-Forwards: 70
>> >Route: <sip:[email protected];lr>
>> >Content-Type: application/sdp
>> >Contact: <sip:[email protected]:5064;transport=udp>
>> >Record-Route:
>> ><sip:pellmell.open-ims.org:5064;lr;transport=udp;sipseesessionid=1ir0oxwe30s0i>
>> >Content-Length: 241
>> >Message body
>> >
>> >
>> >*********** first 200 **************
>> >
>> >Session Initiation Protocol
>> >Status-Line: SIP/2.0 200 Ok
>> >Message Header
>> >Server: SnowShoreMediaServer/2.0.0-060228A.FC2
>> >Via: SIP/2.0/UDP
>> >pellmell.testDomain.org:5064;received=193.175.134.83;sipseesessionid=1ir0oxwe30s0i;branch=z9hG4bKaf12489b1bb84bdb2daf3d7a997d74ac
>> >To:
>> ><sip:[email protected];voicexml=http://193.175.134.83:8080/vxml/mailbox_main.vxml>;tag=1147261142
>> >From:
>> ><sip:[email protected]:5064;caller="sip:[email protected]">;tag=657366
>> >Call-ID: [email protected]
>> >CSeq: 1 INVITE
>> >Record-Route:
>> ><sip:pellmell.testDomain.org:5064;lr;transport=udp;sipseesessionid=1ir0oxwe30s0i>
>> >Contact: sip:193.175.134.78:5060
>> >Content-Type: application/sdp
>> >Session-Expires: 1200
>> >Content-Length: 184
>> >Message body
>> >
>> >
>> >_______________________________________________
>> >nist-sip mailing list
>> >[email protected]
>> >http://www-x.antd.nist.gov/mailman/listinfo/nist-sip
>> >
>> >
>> >
>>
>>
>
>
> _______________________________________________
> nist-sip mailing list
> [email protected]
> http://www-x.antd.nist.gov/mailman/listinfo/nist-sip