Ranga, Dale The same thing happened when I used IP addresses.
1 REGISTER-287 2 REGISTER-287 3 401-287 4 REGISTER-288 w/nonce 5 401-288 6 200-288 I believe there are three faults. 1. The ITSP (Asterisk) should not send cseq 288 in line 5. 2. sipX should not disregard the 200 OK in line 6 3. sipX should not stop registering. Dale, The branch value in the 401 line 5 is the same as sipX sends in line 4. But there should not be a 401 in response to the REGISTER with nonce! Regards, Sven -----Original Message----- From: WORLEY, Dale R (Dale) [mailto:dwor...@avaya.com] Sent: 01 June 2010 19:03 To: Sven Evensen; M. Ranganathan Cc: sipx-users@list.sipfoundry.org Subject: RE: SIP trunk stops registering ________________________________________ From: Sven Evensen [sven.even...@onrelay.com] should be cseq=2 in line 5, which is a fault from the ITSP?: sipX sends REGISTER cseq=1. after 500ms sipX resends REGISTER cseq=1. a few ms later 401 cseq=1 is received for first REGISTER. sipX sends new REGISTER with nonce cseq=2. sipX receives 401 cseq=2 (fault ITSP?) from resent first REGISTER and trunk is "blocked" sipX receives 200 OK cseq=2 from REGISTER with nonce, but disregards it. ________________________________________ You can tell if the ITSP has made a mistake by comparing the Via header 'branch' values -- they should match the CSeq in requests and responses. If you've sent a snapshot, we can see this. We probably should have a more sophisticated algorithm for restoring service on a trunk. On the other hand, this does seem to be an ITSP problem and they should fix it. Dale _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
