Smells like a feature request to me... clock fudge. :-)
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:sipx-users- > [EMAIL PROTECTED] On Behalf Of Gabor Paller > Sent: Thursday, November 20, 2008 4:40 AM > To: Dale Worley > Cc: [email protected] > Subject: Re: [sipx-users] Re-registration problem > > Hi, > > It took some time but I went after the re-registration issues. > The NCH Express Talk softphone, Basic Free Version, V3.08 does the > wrong > thing. It requests 1 hour subscription expiration period and ignores > the > expiration period returned by SipX. Therefore its subscription will > expire and it will not be accessible until its hourly re-registration. > It's a pity because we had the best experiences with this softphone. > > The Cisco 7940 (SIP image, P0S3-08-5-00) is a more complicated issue. > The phone processes SipX expiration response correctly but it tries to > re-register exactly after that time period. It seems that due to minor > differences between the clock of the PC running SipX and the clock of > the Cisco phone, the Cisco phone is regularly late. Not by much, the > maximum time it spent unsubscribed was less than 1 minute. It still > happens, however, and when it happens, the endpoint is unregistered and > cannot receive calls. > > Would it be possible for SipX to "lie" in its subscription expiration > time, e.g. report back X seconds to the endpoint and set its internal > timeout to X+D seconds? Minor clock differences between the device and > the endpoint could be then overcome. > > Regards, > Gabor > > -----Original Message----- > From: Dale Worley [mailto:[EMAIL PROTECTED] > Sent: 13 November 2008 16:06 > To: Gabor Paller > Cc: Nikolay Kondratyev; [email protected] > Subject: Re: [sipx-users] Re-registration problem > > On Thu, 2008-11-13 at 12:38 +0000, Gabor Paller wrote: > > It seems to happen with Cisco 7940 (SIP image, P0S3-08-5-00). It is > > still unconfirmed, seems to happen spuriously and only for a few > > seconds. > > There's a way to extract just the messages regarding a single phone: > > merge-logs --include-method=REGISTER --ft=[ext.no.]@ > /var/log/sipxpbx/sipregistrar.log > > That will generate file "merged.xml" that you can feed into sipviewer. > But it's also readable by text. What it contains is all REGISTER > messages and responses to/from the registrar that contain the string > "[ext.no.]@" in their From or To headers, which extracts all the > registration messages from phone [ext.no.]. > > Look at those messages to see when the phone registers, and compare it > to the expires times provided in the REGISTER responses. > > Dale > > > _______________________________________________ > 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
