Hi Ranga, I did not quite understand the conclusion. Where is the DNS fault? In sipX? And what is it actually causing?
Why does sipX ignore 200 OK after two 401? Why does sipX stop registration of that trunk? Regards, Sven -----Original Message----- From: M. Ranganathan [mailto:mra...@gmail.com] Sent: 31 May 2010 23:01 To: Sven Evensen Cc: sipx-users@list.sipfoundry.org Subject: Re: SIP trunk stops registering On Mon, May 31, 2010 at 2:33 PM, M. Ranganathan <mra...@gmail.com> wrote: > On Mon, May 31, 2010 at 1:55 PM, Sven Evensen <sven.even...@onrelay.com> > wrote: >> Hi Ranga, >> >> The problem is a little more subtle, I will try to explain. And I will send >> you a snapshot too. >> >> 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=1 (fault ITSP?) from resent first REGISTER and trunk >> is "blocked" >> sipX receives 200 OK cseq=2 from REGISTER with nonce, but disregards it. >> Fault sipX? > > > It would be interesting to see a debug log if you can generate one. > > (might be a bit large but it would be worth while). > > edit etc/sipxpbx/log4j.properties. Add the line > log4j.category.org.sipfoundry.sipxbridge=trace > > AND turn ON debug level logging only for sipxbridge. Then let the > trunk time out as above and please send me the trace. > > Only sipXbridge needs to have DEBUG turned on. > > Ranga Looking at the log sent by Sven, it appears that there are DNS issues that lead to this. "2010-05-31T20:43:01.328000Z":33528:JAVA:WARNING:ec2-175-41-131-35.ap-southeast-1.compute.amazonaws.com:Timer-0:00000000:SipUtilities:"FindSipServer::findServer Unable to resolve by A portahk.cordiaip.netx" "2010-05-31T20:43:01.328000Z":33529:JAVA:ERR:ec2-175-41-131-35.ap-southeast-1.compute.amazonaws.com:Timer-0:00000000:RegistrationTimerTask:"Unexpected Exception Sending registration in timer task" javax.sip.SipException: No route to registrar found at org.sipfoundry.sipxbridge.SipUtilities.createRegistrationRequestTemplate(SipUtilities.java:449) at org.sipfoundry.sipxbridge.SipUtilities.createRegistrationRequest(SipUtilities.java:561) at org.sipfoundry.sipxbridge.RegistrationManager.sendRegistrer(RegistrationManager.java:45) at org.sipfoundry.sipxbridge.RegistrationTimerTask.run(RegistrationTimerTask.java:38) at java.util.TimerThread.mainLoop(Timer.java:512) > > >> >> Also sipX does NOT attempt any re REGISTER. This trunk is blocked until >> sipXBridge is restarted. Fault sipX? >> >> I will attempt to send a snapshot, but this sequence of events is pretty >> clear from the pcap I attached. >> >> NB So the 500ms timer is a generic SIP timer. That sounds pretty short if >> you have a little latency to your ITSP. >> >> Regards, >> Sven >> >> >> -----Original Message----- >> From: M. Ranganathan [mailto:mra...@gmail.com] >> Sent: 31 May 2010 17:24 >> To: Sven Evensen >> Cc: sipx-users@list.sipfoundry.org >> Subject: Re: SIP trunk stops registering >> >> If sipxbridge sees two 401 or 407 for two successive REGISTER >> transactions that implies it tired to authenticate, failed, tried >> again, failed and hence there is a problem with the credentials. If >> such is the case, then sipxbridge will retry again in 60 sec. >> >> This has nothing to do with the 500 ms. timer setting which is the SIP >> base timer interval. >> >> Please provide additional information (snapshots) to determine whether >> there is a problem at hand. >> >> Thanks >> >> Ranga >> >> >> On Sun, May 30, 2010 at 8:44 AM, Sven Evensen <sven.even...@onrelay.com> >> wrote: >>> Hi, >>> >>> >>> >>> We have sipX running in EC2 Singapore and a US SIP trunk provider (Cordia) >>> with break out in Hong Kong. >>> >>> >>> >>> We need to register one trunk per incoming DID, 8 total, (don't like this >>> solution, but ok for this trial) and >>> >>> one trunk for all outgoing calls. >>> >>> >>> >>> The incoming trunks lose their registrations over time, a few hours and half >>> are gone. >>> >>> >>> >>> After tedious study of WireShark (see attached pcap), the conclusion is as >>> follows. >>> >>> >>> >>> Line 6 Register cseq 139 sent >>> >>> Line 8 401 received cseq 139 after 488 ms >>> >>> - That is too late for sipX, New Register is already being sent from >>> within sipX >>> >>> Line 9 Register cseq 139 is resent >>> >>> Line 10 Register cseq 140 sent with nonce in response to line 8, >>> 401 >>> >>> Line 11 401 received cseq 140 (I think this is response to line >>> 9, but wrong cseq) >>> >>> - At this point sipX has received two 401, channel now marked >>> "bad", thinking line 11 is response to line 10 >>> >>> Line 12 200 OK received cseq 140 >>> >>> - This comes too late, channel already dead >>> >>> >>> >>> I think the problem is line 11, that 401 should have cseq 139! Also, sipX >>> disregards the 200 OK, line 12, after >>> >>> two 401 have been received. >>> >>> >>> >>> Question to sipX: >>> >>> Where can I adjust the 500ms "re-register" timer? >>> >>> Why does sipX never start re-registration, once channel is dead, it remains >>> so until sipXBridge is restarted. >>> >>> >>> >>> >>> >>> >>> >>> Regards, >>> >>> Sven >>> >>> >>> >>> >>> >>> >>> >>> ________________________________ >>> >>> From: mpatter...@cordiacorp.com [mailto:mpatter...@cordiacorp.com] >>> Sent: 28 May 2010 18:02 >>> To: mpatter...@cordiacorp.com >>> Cc: Sven Evensen; Tim Caputo; Robert Yumul; Enterprise Support PH; >>> entsupp...@cordiaip.com >>> Subject: RE: Registration Problem - 42035028 >>> >>> >>> >>> Cordia Team, >>> >>> If Sven moves his trunks to register on the cchk2 node, we need to know the >>> exact time that a trunk loses registration. We have our vendor assisting us >>> and they are running a debug analysis with Sven's ip address, but to resolve >>> this quicker we need to provide the time it occurs. >>> >>> Also, once we confirm that Sven has moved the trunks to cchk2, we need to >>> change his RP to outside. >>> >>> Sven, any information regarding the time you lose a registration would be >>> very helpful. >>> >>> >>> --- Original message --- >>> Subject: RE: Registration Problem - 42035028 >>> From: <mpatter...@cordiacorp.com> >>> To: Sven Evensen <sven.even...@onrelay.com> >>> Cc: Tim Caputo <tcap...@cordiacorp.com>, Robert Yumul >>> <ryu...@cordiacorp.ph>, Enterprise Support PH <entsupp...@cordiacorp.ph>, >>> <entsupp...@cordiaip.com> >>> Date: Friday, 28/05/2010 12:43 PM >>> >>> Would it be possible for you to register to cchk2.cordiaip.net? This may >>> cause problems with inbound service but i want to eliminate one piece of >>> equipment from the equation. >>> >>> --- Original message --- >>> Subject: RE: Registration Problem - 42035028 >>> From: Sven Evensen <sven.even...@onrelay.com> >>> To: <mpatter...@cordiacorp.com> >>> Cc: Tim Caputo <tcap...@cordiacorp.com>, Robert Yumul >>> <ryu...@cordiacorp.ph>, Enterprise Support PH <entsupp...@cordiacorp.ph>, >>> <entsupp...@cordiaip.com> >>> Date: Friday, 28/05/2010 12:21 PM >>> >>> Hi Mike, >>> >>> >>> >>> Here is a summary of what I believe is happening. >>> >>> >>> >>> We send 8 REGISTER to you every 25 seconds (I think the expire time on 200 >>> OK is 30 sec). >>> >>> Normally we get 8 200 OK back. >>> >>> >>> >>> After a while we get on one or more of the trunks a 401 not authorized. We >>> respond with a >>> >>> REGISTER including nonce. >>> >>> >>> >>> But sometimes our second REGISTER (with nonce) also gets a 401 not >>> authorized and in this case sipX >>> >>> marks this channel as "dead". >>> >>> >>> >>> One sequence of events we saw that might be causing this was as follows (for >>> one specific DID) : >>> >>> >>> >>> REGISTER cseq 77 à >>> >>> >>> >>> REGISTER cseq 77 à >>> >>> ß- 401 Not Authorized >>> cseq 77 >>> >>> REGISTER cseq 78 à >>> >>> ß 401 Not Authorized >>> cseq 78 >>> >>> ß 200 OK cseq 78 >>> >>> >>> >>> So there could be a timing issue. I do not think there is a latency issue, >>> pinging from Singapore to HK was >>> >>> stable 36-38 ms. >>> >>> >>> >>> Regards, >>> >>> Sven >>> >>> >>> >>> ________________________________ >>> >>> From:mpatter...@cordiacorp.com [mailto:mpatter...@cordiacorp.com] >>> Sent: 28 May 2010 14:15 >>> To: Sven Evensen >>> Cc: Tim Caputo; Robert Yumul; Enterprise Support PH; entsupp...@cordiaip.com >>> Subject: RE: Registration Problem - 42035028 >>> >>> >>> >>> Sven, >>> >>> We are making contact with your SiPX contact that you provided. I just >>> want to clarify what you are seeing at your equipment. Do you see a 401 and >>> a 200oK message coming back at the same time, or do they occur with a >>> corresponding register? In other words the 401 is a normal occurrence and >>> is supposed to occur when the previous nonce expiration time has been >>> reached. One of the Cordia engineers mentioned to me that you are seeing >>> the 401 and the 200 at the same time. As a result of both coming back you >>> lose your registration. >>> >>> Regards, >>> >>> Mike >>> >>> --- Original message --- >>> Subject: RE: Registration Problem - 42035028 >>> From: Sven Evensen <sven.even...@onrelay.com> >>> To:<mpatter...@cordiacorp.com> >>> Cc: Tim Caputo <tcap...@cordiacorp.com>, Robert Yumul >>> <ryu...@cordiacorp.ph>, Enterprise Support PH <entsupp...@cordiacorp.ph>, >>> <entsupp...@cordiaip.com> >>> Date: Thursday, 27/05/2010 5:56 PM >>> >>> >>> I have been looking for this "re-register" timer, not found yet. Might have >>> to ask Ranga (sipX). >>> >>> >>> >>> Sven >>> >>> >>> >>> ________________________________ >>> >>> From:mpatter...@cordiacorp.com [mailto:mpatter...@cordiacorp.com] >>> Sent: 27 May 2010 22:45 >>> To: Sven Evensen >>> Cc: Tim Caputo; Robert Yumul; Enterprise Support PH; entsupp...@cordiaip.com >>> Subject: RE: Registration Problem - 42035028 >>> >>> >>> >>> Your are correct, I meant your registraton timer not your invite / re-invite >>> timer. Thank you for the contact info of the sipx developer. This will >>> come in handy. >>> >>> >>> --- Original message --- >>> Subject: RE: Registration Problem - 42035028 >>> From: Sven Evensen <sven.even...@onrelay.com> >>> To:<mpatter...@cordiacorp.com>, Tim Caputo <tcap...@cordiacorp.com> >>> Cc: Robert Yumul <ryu...@cordiacorp.ph>, Enterprise SupportPH >>> <entsupp...@cordiacorp.ph>, <entsupp...@cordiaip.com> >>> Date: Thursday, 27/05/2010 5:18 PM >>> >>> >>> >>> Mike, >>> >>> >>> >>> Thanks for the update, appreciate the effort. I am not sure about why >>> re-invite is relevant for the REGISTER problem. >>> >>> Your efforts here are not only helping me (hopefully), but will enable you >>> to support sipX. Can I suggest you email the >>> >>> developer of sipXBridge (the SBC which handles the REGISTER) directly. >>> mra...@gmail.comhe is based in Boston >>> >>> >>> >>> Regards, >>> >>> Sven >>> >>> >>> >>> >>> >>> >>> >>> ________________________________ >>> >>> From:mpatter...@cordiacorp.com [mailto:mpatter...@cordiacorp.com] >>> Sent: 27 May 2010 21:44 >>> To: Tim Caputo >>> Cc: Sven Evensen; Robert Yumul; Enterprise SupportPH; >>> entsupp...@cordiaip.com >>> Subject: Re: Registration Problem - 42035028 >>> >>> >>> >>> Sven, >>> >>> I wanted to give you my assurance that we are dedicating all available >>> resources to your account to resolve this problem. We have the engineers >>> with our switch vendor assisting as well. We have not run into this problem >>> with other customers using a variety of different pbx's so this is a new >>> problem for us. Personally I am familiar with SipX and know of plenty of >>> people using it but I have not had a chance to get a SipX system up and >>> running. We have a lab in our Orlando, Floridaoffice and they are working >>> on this problem as well. Could you please tell me if you have a >>> configurable re-invite timer in the SipX configuration files? >>> >>> Regards and thank you. >>> >>> Mike >>> >>> >>> >>> --- Original message --- >>> Subject: Re: Registration Problem - 42035028 >>> From: Tim Caputo <tcap...@cordiacorp.com> >>> To: Sven Evensen <sven.even...@onrelay.com> >>> Cc: Mike Patterson <mpatter...@cordiacorp.com>, Robert Yumul >>> <ryu...@cordiacorp.ph>, Enterprise SupportPH <entsupp...@cordiacorp.ph>, >>> <entsupp...@cordiaip.com> >>> Date: Thursday, 27/05/2010 3:10 PM >>> >>> Sven, >>> We see the 401 responses we are sending your PBX and we have our Switch >>> engineers working on this. Thank you for your patience and we will keep you >>> updated on our progress. >>> >>> Thank You, >>> Tim Caputo >>> >>> Sven Evensen wrote: >>> >>> Can someone please have a look at this for me. >>> >>> >>> >>> Regards, >>> >>> Sven >>> >>> >>> >>> -----Original Message----- >>> >>> From: Sven Evensen >>> >>> Sent: 27 May 2010 14:34 >>> >>> To: Mike Patterson >>> >>> Cc: Robert Yumul; Enterprise Support PH; entsupp...@cordiaip.com; >>> >>> 'tcap...@cordiacorp.com' >>> >>> Subject: RE: Registration Problem - 42035028 >>> >>> >>> >>> Hi Mike, >>> >>> >>> >>> I did not really get anywhere working through the night with the >>> >>> Manila guys. They said they had sent the case to the guys in US east. >>> >>> Can some one there please take a look at my case >>> >>> >>> >>> Regards, >>> >>> Sven >>> >>> >>> >>> -----Original Message----- >>> >>> From: Dennis Nacino [mailto:dnac...@cordiacorp.ph] >>> >>> Sent: 27 May 2010 08:35 >>> >>> To: Sven Evensen >>> >>> Cc: Robert Yumul; Enterprise Support PH; entsupp...@cordiaip.com; Mike >>> >>> Patterson >>> >>> Subject: Re: Registration Problem - 42035028 >>> >>> >>> >>> Hi >>> >>> >>> >>> Does your PBX send the nonce string together with the response string at >>> >>> >>> >>> a time when it got a 401 response from our server? >>> >>> Can you do a packet capture on your end? >>> >>> >>> >>> Do you have Instant messaging if you have, >>> >>> >>> >>> please add mine; >>> >>> >>> >>> @AIM: csmdnacino >>> >>> @YM: dennis_nac...@yahoo.com >>> >>> @msn: dmnac...@hotmail.com >>> >>> >>> >>> >>> >>> >>> >>> On 5/27/2010 3:20 PM, Sven Evensen wrote: >>> >>> >>> >>> As far as I can tell, only 6 are registered now. Can you see why that >>> >>> happened? >>> >>> >>> >>> -----Original Message----- >>> >>> From: Robert Yumul [mailto:ryu...@cordiacorp.ph] >>> >>> Sent: 27 May 2010 08:11 >>> >>> To: Sven Evensen >>> >>> Cc: Enterprise Support PH; entsupp...@cordiaip.com; Mike Patterson >>> >>> Subject: Re: Registration Problem - 42035028 >>> >>> >>> >>> I see 8 lines registered. >>> >>> >>> >>> 85230519805 Online >>> >>> 85230519811 Online >>> >>> 85230519814 Online >>> >>> 85230519815 Online >>> >>> 85230519816 Online >>> >>> 85230519817 Offline >>> >>> 85230519819 Online >>> >>> 85230519821 Online >>> >>> 85230519826 Offline >>> >>> 85230519829 Online >>> >>> 85230519840 Offline >>> >>> >>> >>> Are the above lines correct? >>> >>> >>> >>> >>> >>> Thanks >>> >>> Robert >>> >>> >>> >>> On May 27, 2010, at 3:01 PM, Sven Evensen wrote: >>> >>> >>> >>> >>> >>> >>> >>> Ok, I restarted SIP trunks and there should be 8 registered now >>> >>> >>> >>> -----Original Message----- >>> >>> From: Robert Yumul [mailto:ryu...@cordiacorp.ph] >>> >>> Sent: 27 May 2010 06:51 >>> >>> To: Sven Evensen >>> >>> Subject: Re: Registration Problem - 42035028 >>> >>> >>> >>> We have have some minor adjustments on the back end. Please keep >>> >>> registration interval to 60 seconds and observe. >>> >>> >>> >>> I now see only 7 DID registered. >>> >>> >>> >>> 85230519805 Online >>> >>> 85230519811 Online >>> >>> 85230519814 Offline >>> >>> 85230519815 Online >>> >>> 85230519816 Online >>> >>> 85230519817 Offline >>> >>> 85230519819 Online >>> >>> 85230519821 Online >>> >>> 85230519826 Offline >>> >>> 85230519829 Online >>> >>> 85230519840 Offline >>> >>> >>> >>> >>> >>> On May 27, 2010, at 1:18 PM, Sven Evensen wrote: >>> >>> >>> >>> >>> >>> >>> >>> fyi >>> >>> Even though I selected 60 seconds, it is registering every 25 >>> >>> >>> >>> >>> >>> seconds. >>> >>> >>> >>> >>> >>> sven >>> >>> >>> >>> -----Original Message----- >>> >>> From: Robert Yumul [mailto:ryu...@cordiacorp.ph] >>> >>> Sent: 27 May 2010 06:12 >>> >>> To: Sven Evensen >>> >>> Cc: Enterprise Support PH; entsupp...@cordiaip.com; Mike Patterson >>> >>> Subject: Re: Registration Problem - 42035028 >>> >>> >>> >>> Hi Sven, >>> >>> I see the following DIDs: >>> >>> >>> >>> 85230519805 Online >>> >>> 85230519811 Online >>> >>> 85230519814 Online >>> >>> 85230519815 Online >>> >>> 85230519816 Online >>> >>> 85230519817 >>> >>> 85230519819 Online >>> >>> 85230519821 Online >>> >>> 85230519826 >>> >>> 85230519829 Online >>> >>> 85230519840 >>> >>> >>> >>> Can you please change your registration interval to 60 seconds for >>> >>> >>> >>> >>> >>> now >>> >>> >>> >>> >>> >>> and I will try to analyze the registration. >>> >>> >>> >>> >>> >>> Thanks, >>> >>> Robert >>> >>> >>> >>> >>> >>> On May 27, 2010, at 1:05 PM, Sven Evensen wrote: >>> >>> >>> >>> >>> >>> >>> >>> Hi Robert, >>> >>> >>> >>> The DDIs are : >>> >>> +852 30519829, 30519821, 30519819, 30519816, 30519815, 30519814, >>> >>> 30519811, 30519805 >>> >>> >>> >>> As we speak now, it seems all 8 are registered. I have changed the >>> >>> registration interval from 25 seconds to 10 minutes approx. >>> >>> >>> >>> What I saw earlier was that suddenly Unauthorized came back instead >>> >>> >>> >>> >>> >>> of >>> >>> >>> >>> >>> >>> 200 OK. >>> >>> >>> >>> If you want, I can speed up the registrations again, that might >>> >>> >>> >>> make >>> >>> >>> >>> >>> >>> >>> >>> it >>> >>> >>> >>> >>> >>> faster to capture the problem. >>> >>> >>> >>> Regards, >>> >>> Sven >>> >>> >>> >>> -----Original Message----- >>> >>> From: Robert Yumul [mailto:ryu...@cordiacorp.ph] >>> >>> Sent: 27 May 2010 06:00 >>> >>> To: Sven Evensen >>> >>> Cc: Enterprise Support PH; entsupp...@cordiaip.com; Mike Patterson >>> >>> Subject: Registration Problem - 42035028 >>> >>> >>> >>> Hi Sven, >>> >>> Apologies for the late reply. Can you please send me the DID you >>> >>> >>> >>> are >>> >>> >>> >>> trying to register so we can dig some more on our end. >>> >>> >>> >>> Thanks >>> >>> Robert >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Tim Caputo >>> >>> VOIP Engineer >>> >>> Cordia Corporation >>> >>> 13275 West Colonial Drive >>> >>> Winter Garden, FL 34787 >>> >>> Main: 1-407-313-7091 >>> >>> corgtcaputo - AIM >>> >>> www.cordiacorp.com >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> >> >> >> -- >> M. Ranganathan >> > > > > -- > M. Ranganathan > -- M. Ranganathan _______________________________________________ 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/
