We've not seen a pattern yet but I'm watching to see if that is related. For example, maybe as someone mentioned before, one of the phones is taking them all down.
On Wed, 7 Jul 2010 02:28:46 +0000, Matthew Kitchin (Public) wrote: > Did they countdown to 0 and then disappear or simply disappear no matter > how much time they had left before they were supposed to expire/re-register? > > -----Original Message----- > From: "[email protected]" <[email protected]> > Sender: [email protected] > Date: Tue, 6 Jul 2010 21:21:11 > To: sipx-users<[email protected]> > Reply-To: [email protected] > Subject: Re: [sipx-users] Random Dropped Registrations > > Same as explained before, dropped, vanished, from the list of Active > Registrations. > Slowly but surely, they have all come back and I'm watching to see when it > happens again. > I'm also monitoring the sipregistrar.log file at the same time. > > The OS and hardware time are still correct. > > > On Wed, 7 Jul 2010 02:19:01 +0000, Matthew Kitchin (Public) wrote: >> What does dropped mean in this specific case? >> >> -----Original Message----- >> From: "[email protected]" <[email protected]> >> Sender: [email protected] >> Date: Tue, 6 Jul 2010 21:12:43 >> To: sipx-users<[email protected]> >> Reply-To: [email protected] >> Subject: Re: [sipx-users] Random Dropped Registrations >> >> The problem is not solved. The time is correct and all phones just dropped >> again. >> Happy to send a snapshot privately. >> >>> In this instance you've said "The merge-logs command and the regtimes >>> command don't [exist] on the ISO", but you haven't *copied down the >>> details >>> of the failure*. What is the command line that you entered? What is >>> the >>> error message that was printed? >>> >> I always try to do so. It would be in the threads I had going on this. >> I can post them here or in another thread when I get back to those >> problems. Probably best to start a new thread or look back at an old one >> which touched on these other problems. >> >>> Now I can guess at some problems that are likely to have occurred, so >>> I'd >>> like you to also execute some commands and *report the output*: "which >>> merge-logs", "ls -l /usr/bin/merge-logs", and "locate merge-logs". And >>> you >>> should try to find merge-logs using any other command you use to locate >>> programs whose locations you don't know. >>> >> I did these things as well in other threads. As I recall, I said that it >> was installed but not sure if I showed it's path or not. >> >>> As a general rule, SIP phones do not need to register in order to make >>> outgoing calls. >>> >> Guessing that means local phones only since remotes have to register to >> connect. >> >>> But once a call is established, registration does not need to be >>> maintained to continue the call. >>> >> Good to know. >> >>> It is likely that your dropped call problem and your failed registration >>> problem >>> >> I think we established that vonage was most likely the culprit for the >> call >> which was dropped while on the phone. It just happened to be during the >> same time that we started looking at this problem. >> >> Mike >> > > _______________________________________________ > 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/ _______________________________________________ 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/
