I wrote the original wiki page on the m3, which snom oem's from another manufacturer with their own "version" of firmware.
I have not experienced this issue with my m3's, ever. I assume the m9 is "not that much different" from the m3. Please refer to the wiki page: http://wiki.sipfoundry.org/display/xecsuser/Configuring+Snom+M3+Wireless+SIP-DECT+Phones <http://wiki.sipfoundry.org/display/xecsuser/Configuring+Snom+M3+Wireless+SIP-DECT+Phones>and look at the re-registration time (which on the m3 is 600 seconds), and see if you can adjust your upwards. I will look your trace over later today and see if I can understand anything else from it. I am also running 4.2.1 and dont believe it to be re-registering with a different session, so it may have something to do with the snop firmware, which would not be a big surprise to me, because I never got satisfaction out of snom for the bugs I tried to get them to open. Given the phone is oem'd, I somewhat doubted they would be willing to "fix" very much anyway. Also, the version of firmware you are using might be pertinent. http://wiki.snom.com/Snom_m9/Firmware/Release_Notes <http://wiki.snom.com/Snom_m9/Firmware/Release_Notes>The last version, 9.1.63, alludes to fixes for CSeq problems, however that ALL they say about it. On Wed, Aug 11, 2010 at 7:50 AM, Ali Nebi <[email protected]> wrote: > Hi, > > we bought snom m9 some weeks ago and configured it to connect to our sip > providers. On one of our servers we have installed Sipxecs 4.2.1 version > and we have configured snom m9 phone to connect to Sipxecs. > > We experience a very strange problem. > > 1. Phone register to Sipxecs as the phone is set to propose expiration > time around 360s. Phone register and we see in sipx traces and logs and > web interface that the phone is registered. > 2. When the timer shows around 120s until expiration time, then we see > that the phone is registering again, but it is different registration > session not the first one. So now we have 2 registrations with the same > identity. What happens is that the first registration expires and it > does not reregister. Then the second session expiration time decrease > around 120s and phone again creates anothe registration session, and > previous session expire after 120s (not exactly 120s) and it does not > reregister also. > > This happens all the time for all identities that connects to Sipxecs. > > What i see in Sipxecs traces is that phone gets Registration Too Brief > message. Minimum registration expiration time is 300s in sipx. > > Another thing that i see in sipx is the following situation: > > 1. Phone send registration request with proposal for expiration time > 360s. > 2. Sipxecs returns "401 Unauthorized" request to the phone so phone can > register with authentication > 3. Then phone sends again Register requests, but now the Expires header > is set to 120s. > 4. In normal situation Sipxecs should return (200 OK), but it returns > "423 Registration Too Brief". > > I think the whole problems with expiring registration sessions and not > reregistering happens, because the Expire header is set incorrectly. How > to fix this? > > Or if you think that the reason for this problem is something else, let > me know what you think. > > What is expected: > > Phone should create only one registration session for one identity to > Sipxecs. Phone register successfully, without error like "Registration > Too Brief" and session does not expire, but the reregister before to > expire. Phone does not create more than one sessions to Sipxecs for the > same identity. > > I attached a trace from sipregister components. There you can see what > happens. > > Any suggestions how to proceed? > > > Thanks in advanced. > > P.S. > sipXconfig (4.2.1-018932 2010-06-25T10:44:53 build24) > 87.xxx.xxx.43 is server where Sipxecs is installed. > 213.xxx.xxx.151 my public ip address from where i register. > mydomain.com is my domain name. > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
