Stack dropped 200 for INVITE

Lebing Xie <[email protected]>
Newsgroups gmane.comp.voip.nist-sip
Organization Fraunhofer Fokus
Message-ID <1147263570.8442.6.camel@Lebing>
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.