________________________________________ From: [email protected] [[email protected]] On Behalf Of [email protected] [[email protected]]
For a couple of weeks or more now, we have started noticing a behavior which is that of phones dropping registration. Dropping, meaning that they disappear from the Active Registrations screen and are no longer reachable. _______________________________________________ It seems like you might have a number of different problems (which may stem from only one fundamental cause). To prevent confusion, let's start by diagnosing this problem, because it's clearly important, and you can easily identify its occurrences. 1) Set your logging level to INFO (or DEBUG if you like that better). 2) Wait for the problem to be manifest, that is, a phone is first seen and then later not seen on the Active Registrations screen without any explanation. 3) Take a snapshot using the Diagnostics -> Snapshot screen. Request the time period to be covered by the captured logs to be the present back to about 3 hours ago. That should be enough time to capture the genesis of the problem. 4) Un-gzip and un-tar the snapshot file in some convenient directory on the system. 5) cd to var/log/sipxpbx in the unpacked snapshot. 6) Do "merge-logs --ft=[extension] --include-method=register", where [extension] is the extension of the phone in question. This extracts the REGISTER requests and their responses which have From or To fields containing [extension]. 7) Do "sipviewer merged.xml &" to run sipviewer and display the filtered log information. 8) Stare at the sipviewer screen to see what's going wrong. What you should see is REGISTER requests going from the phone to the proxy to the registrar, and responses going back. The requests will come in pairs, the first one gets a 401/407 response, the second gets a 200 response. Then there will be a gap of several minutes, then the next pair, etc. With the default settings, the times at the left are in local time, so you should look around the time when the phone was unexpectedly not registered. (You can change the times to UTC from the pulldown menus.) Each 200 response contains a header "Expires: [number]", where [number] is the number of seconds into the fiture that the registration has been extended until. The next successful REGISTER should complete within that number of seconds of each successful REGISTER. Admittedly, one of these steps might fail. If so, please copy down the details of the failure, and we will (have to) solve that problem first. (See http://www.urbandictionary.com/define.php?term=yak+shaving) 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 sipXecs IP PBX -- http://www.sipfoundry.org/
