" I believe that you're just seeing the normal 20-second expiration of the branch."
This is probably true. " The other one is not CANCELed because it sent SDP - this triggers some exception handling because early media sessions are sometimes used by PSTN gateways for extended periods of time." Are the rules of this exception handling public? I am curious, after how much time the branch with SDP would be CANCELed. Regards, Gabor -----Original Message----- From: Scott Lawrence [mailto:[EMAIL PROTECTED] Sent: 25 November 2008 17:08 To: Gabor Paller Cc: [email protected] Subject: Re: [sipx-users] CANCEL other branch on 180 Ringing? On Tue, 2008-11-25 at 15:32 +0000, Gabor Paller wrote: > Hi, > > > > I am investigating a strange case (see attached SIP log. I edited the > long and clunky SIP log, if anyone is interested, I can provide the > original). There is an incoming call (User 405, from 10.1.5.74) to > user 402 which is branched to two endpoints subscribed to user 405 > (SIP001E136C6F0.test.onrelay.local.sip is a desk phone, > sipxecs.test.onrelay.local.5560 is a software agent). The desk phone > starts to ring, the software agent starts to set up a call, emits 183 > Session progress responses and eventually a 180 Ringing (at > 10:33:47.521220). Then, miraculously, the SipX proxy cancels the desk > phone branch (at 10:34:00.950099). The call setup with the other > branch goes on and eventually succeeds (edited out from the log, > nothing unusual there). I believe that you're just seeing the normal 20-second expiration of the branch. The other one is not CANCELed because it sent SDP - this triggers some exception handling because early media sessions are sometimes used by PSTN gateways for extended periods of time. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
