reSIProcate

Mailing Lists

Source Code

< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate-users] endless Re-Invite ping-ping

First off, let's see some DEBUG logs. Also, I don't think the two logs you've provided below are quite in sync. One possibility is that your app is trying to send a new reInvite when it gets the onOfferRejected() callback when the 491 comes in (It doesn't look like provideOffer() or requestOffer() will let you do this. However, targetRefresh() will.) 

Best regards,
Byron Campen


Hi,
I've implemented two SIP endpoints (based on DUM) setting up a session and sending each other occasionally Re-Invites.If they're doing that in more or less the same instant both sends ends up in an endless message ping-pong whithin the SIP stack. 
Does anybody has any suggestions?

regards
Daniel

Server:
INFO | 20070718-191536.078 | | RESIP:DUM | 3652 | InviteSession.cxx: 2067 | Transition InviteSession::SentReinvite -> InviteSession::SentReinviteGlare INFO | 20070718-191536.250 | | RESIP:DUM | 3652 | InviteSession.cxx: 2067 | Transition InviteSession::SentReinviteGlare -> InviteSession::SentReinvite INFO | 20070718-191536.250 | | RESIP:DUM | 3652 | InviteSession.cxx: 858 | Retra nsmitting the reINVITE (glare condition timer) INFO | 20070718-191536.313 | | RESIP:DUM | 3652 | DialogUsageManager.cxx:1227 | Got: SipResp: 491 tid=c41285753547605c cseq=INVITE / 15 from(wire) INFO | 20070718-191536.313 | | RESIP:DUM | 3652 | InviteSession.cxx: 2067 | Transition InviteSession::SentReinvite -> InviteSession::SentReinviteGlare 

Client:
INFO | 20070718-191536.047 | | RESIP:DUM | 2948 | DialogUsageManager.cxx:1554 | Handling in-dialog request: SipReq: INVITE 127.0.0.1:9002 tid=2f5c0257e54e5c3e cseq=INVITE contact=130.145.231.102:4000 / 14 from(wire) INFO | 20070718-191536.281 | | RESIP:DUM | 2948 | DialogUsageManager.cxx:1227 | Got: SipReq: INVITE 127.0.0.1:9002 tid=c41285753547605c cseq=INVITE contact=13 
0.145.231.102:4000 / 15 from(wire)
INFO | 20070718-191536.281 | | RESIP:DUM | 2948 | DialogUsageManager.cxx:1554 | Handling in-dialog request: SipReq: INVITE 127.0.0.1:9002 tid=c41285753547605c cseq=INVITE contact=130.145.231.102:4000 / 15 from(wire) INFO | 20070718-191536.719 | | RESIP:DUM | 2948 | InviteSession.cxx: 777 | Retransmitting: 
SIP/2.0 200 OK
Via: SIP/2.0/TCP 127.0.0.1:4000;branch=z9hG4bK- d8754z-5a155f2a85509718-1---d8754 
z-;rport=3189
Contact: <sip:>
To: <sip:NLVEHVRES2DTW61.code1.emi.philips.com>;tag=fd78e968
From: <sip:130.145.231.102:4000>;tag=ef4ffd0f
Call-ID: YTZlNjc4ODgwYjBkYjY1OWRjYjg2YTI5NGQ1NGFkNzM.
CSeq: 5 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE
Content-Type: application/sdp
Content-Length: 267

v=0
o=Karl 42 1 IN IP4 NLVEHVRES2DTW61.code1.emi.philips.com
s=audioForward
t=0 0
a=endTime:0
a=globalDelay:0.12
a=neededLocalDelay:0.0392
a=startTime:0
m=audio 9002 RTP/AVP 4
c=IN IP4 NLVEHVRES2DTW61.code1.emi.philips.com
a=rtpmap:4 G723/8000
a=sendonly
INFO | 20070718-191537.188 | | RESIP:DUM | 2948 | InviteSession.cxx: 777 | Retransmitting: 
SIP/2.0 200 OK
Via: SIP/2.0/TCP 127.0.0.1:4000;branch=z9hG4bK- d8754z-5a155f2a85509718-1---d8754 
z-;rport=3189
Contact: <sip:>
To: <sip:NLVEHVRES2DTW61.code1.emi.philips.com>;tag=fd78e968
From: <sip:130.145.231.102:4000>;tag=ef4ffd0f
Call-ID: YTZlNjc4ODgwYjBkYjY1OWRjYjg2YTI5NGQ1NGFkNzM.
CSeq: 5 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE
Content-Type: application/sdp
Content-Length: 267

v=0
o=Karl 42 1 IN IP4 NLVEHVRES2DTW61.code1.emi.philips.com
s=audioForward
t=0 0
a=endTime:0
a=globalDelay:0.12
a=neededLocalDelay:0.0392
a=startTime:0
m=audio 9002 RTP/AVP 4
c=IN IP4 NLVEHVRES2DTW61.code1.emi.philips.com
a=rtpmap:4 G723/8000
a=sendonly


_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/

Attachment: smime.p7s
Description: S/MIME cryptographic signature