Thanks, Nikolay, that was the problem. Although in many cases SipX reports back expiration time that is close to the requested time (e.g. 1800->1703), sometimes it happens that the expiration time reported back by significantly lower than the requested value (e.g. 1800->672). The endpoint does not take into account the returned value and is therefore unregistered.
Thanks again for the help, Gabor -----Original Message----- From: Nikolay Kondratyev [mailto:[EMAIL PROTECTED] Sent: 13 November 2008 12:07 To: Gabor Paller; [email protected] Subject: RE: [sipx-users] Re-registration problem Hi, If you really see that your sip endpoint sends register messages every 1800 sec, then I can tell (with high probability) that your endpoint does not conform to frc 3261 :). The thing is that, afaik, sipx always "randomly redistributes" re-registrations: that is when endpoint asks for the registration for 1800 sec, sipx gives him a smaller period of time, for example, 1630. Pay attention to the "expires" parameter of "contact" field of 200ok message. Rfc 3261 says, that it is this parameter (not the "expires" in register msg) defines registration lifetime. And UA must renew it's registration before this time. Some UA's does not react on it, and renew their registrations according to "expires" in register msg. So, in the example above, for the period of 170 sec your endpoint will be unregistered from the sipx point of view, though the endpoint will consider itself registered. And during this period only outgoing calls from this endpoint will work. Please check if my guess is correct. If yes you can: 1. Change your endpoint :) 2. Workaround: configure your endpoint to register every 300 sec. This is minimum registration time, accepted by sipx, and in this case sipx will give 300 sec in 200 ok msg. Hope this helps, Nikolay. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:sipx-users- > [EMAIL PROTECTED] On Behalf Of Gabor Paller > Sent: Thursday, November 13, 2008 1:59 PM > To: [email protected] > Subject: [sipx-users] Re-registration problem > > Hi, > > I am running 3.10.2 and I observed a strange phenomenon about > re-registrations. My endpoint re-registers periodically, with an > expiration value of 1800 seconds. The re-registration is successful, > REGISTER messages and responses are exchanged correctly. Monitoring from > the "Registrations" page of sipXconfig, I notice that the expiration > value is not refreshed immediately. It takes several minutes before the > re-registration takes effect, meanwhile the old expiration counter > continues to count downwards. It happens that it expires before the > re-registration takes effect and then the endpoint is left unregistered > for a certain time period. > > I will send logs if there is no immediate answer for the problem (e.g. > "this conforms to RFC xxxx :-))) > > Regards, > Gabor > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
