> First of all, if I didn't cover all of the bases, PLEASE, do not hijack my > thread about it, either start another or email me personally. > > 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. > Sometimes, the phone will come back on it's own, other times, it doesn't > return until the phone is restarted. Mind you, on the phone itself, you would > not know that anything is wrong, it still has dial tone, it still has active > looking states but it's no longer registered. > > We have not yet found a pattern, are still looking for one. We thought it > might be after making a call to a phone, when done, it seems to un-register > but that's not the case. We cannot replicate it so far. > > As part of the same problem, this doesn't appear to happen to only one phone > but ALL of the phones which are registered will sometimes drop, randomly. > > Since I cannot merge logs, and someone suggested I post a snapshot, which I > have, but would prefer sending personally to anyone who is interested in > looking at it instead of posting it on the list itself. > > The phones connected at the time, and still, include LinkSys SPA941 and > SPA942 running the last versions I know of which is 5.1.8, some are local, > some are remote, they all drop at the same time. > Another phone is a Polycom 330 running 3.2.3 which was suggested I update. > Another phone is a Nortel 1535 running 2.x which we just got and are testing. > > The server is a test system, running fully updated, current Centos 5, Sipx > 4.2.0 ISO updated through yum to the very latest. The last update I saw come > in was sipregistrar last night. > > The hardware checks out fine and is an IBM BladeCenter LS20 blade, dual > duo-2.2Ghz, 4GB memory, dual SCSI drives. The diagnostics will usually show > me when there are hardware problems, I don't see any. > > I would appreciate some leads on how to find the source of this problem and > will post what ever additional information is needed. http://wiki.sipfoundry.org/display/xecsuserV4r2/Phone+Registration+Troubleshooting#PhoneRegistrationTroubleshooting-LateRegistrationRefresh
Set your registrar logging to INFO (the DEBUG level is almost certainly overkill, and produces a _lot_ more data you very likely do not need). Note the times when the phones are not registered, and look in the logs prior to those times for registration failures. There is a script installed with 4.2 called 'regtimes' that helps to analyze whether or not you are having the problem described at the wiki link above - you may need to install some Perl packages to use it (it will give you the names if needed). It's also possible that something is unregistering them - a register request that has Expires: 0 and Contact: * means 'unregister all contacts for this address' - if some phone is sending this, it could be knocking out all other registrations for the same lines (and the phones would not know). _______________________________________________ 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/
