> For the past two days I have been having a problem where my 
> phones cannot register for several minutes after I start me 
> developer build.
> ( Revision: 15868 )
> log says:
> "2009-07-01T19:22:52.908351Z":374:SIP:DEBUG:kelaptop:SipRegist
> rar:B72FFB90:SipRegistrar:"SipRegistrar::handleMessage() 
> Start processing SIP message"
> "2009-07-01T19:22:52.908440Z":375:SIP:DEBUG:kelaptop:SipRegist
> rarServer:B6AF7B90:SipRegistrar:"SipRegistrarServer::handleMes
> sage() - Start processing REGISTER Message"
> "2009-07-01T19:22:52.908483Z":376:AUTH:DEBUG:kelaptop:SipRegis
> trarServer:B6AF7B90:SipRegistrar:"SipRegistrar::isValidDomain(
> kelaptop.us.nortel.com:5060) VALID"
> "2009-07-01T19:22:52.908526Z":377:SIP:INFO:kelaptop:SipRegistr
> arServer:B6AF7B90:SipRegistrar:"SipRegistrarServer::handleMess
> age() Allowing use of domain alias; To domain 
> 'kelaptop.us.nortel.com' -> 'kelaptop.us.nortel.com'"
> "2009-07-01T19:22:52.908601Z":378:AUTH:DEBUG:kelaptop:SipRegis
> trarServer:B6AF7B90:SipRegistrar:"SipRegistrarServer::isAuthor
> ized fromNameAddr='\"667-274 
> snom\"<sip:[email protected];transport=udp>;tag=ctdfh
ktp7r', toUri='\"667-274 snom\"<sip:274>
@kelaptop.us.nortel.com;transport=udp>', 
> realm='kelaptop.us.nortel.com'"
> "2009-07-01T19:22:52.908651Z":379:AUTH:DEBUG:kelaptop:SipRegis
> trarServer:B6AF7B90:SipRegistrar:"Message Authorization 
> received: reqRealm='kelaptop.us.nortel.com', reqUser='274'"
> "2009-07-01T19:22:52.908669Z":380:AUTH:DEBUG:kelaptop:SipRegis
> trarServer:B6AF7B90:SipRegistrar:"SipRegistrarServer::isAuthor
> ized Realm Matches"
> "2009-07-01T19:22:52.908692Z":381:SIP:DEBUG:kelaptop:SipRegist
> rarServer:B6AF7B90:SipRegistrar:"SipNonceDb::nonceSignature: 
> callId='3c267021c5c1-pdov97v4i...@snom360-000413232667' 
> fromTag='ctdfhktp7r' realm='kelaptop.us.nortel.com' 
> timestamp='4a4bb78c'"
> "2009-07-01T19:22:52.908835Z":382:AUTH:ERR:kelaptop:SipRegistr
> arServer:B6AF7B90:SipRegistrar:"Unable to get credentials for 
> '[email protected]', realm='kelaptop.us.nortel.com', 
> user='274'"
> "2009-07-01T19:22:52.908865Z":383:SIP:DEBUG:kelaptop:SipRegist
> rarServer:B6AF7B90:SipRegistrar:"SipNonceDb::nonceSignature: 
> callId='3c267021c5c1-pdov97v4i...@snom360-000413232667' 
> fromTag='ctdfhktp7r' realm='kelaptop.us.nortel.com' 
> timestamp='4a4bb78c'"
> 
> The behavior began on a build I had been using without a 
> problem (no code changes, no rebuild).  My dynamic ip address 
> had changed the previous day, but I didn't notice the delayed 
> registration behavior at that time.
> 
> Is anyone else seeing this?
> Is it a real problem?

This suggests that the credential.xml file replicated by sipXconfig does
not contain an entry for user '274'.  You can verify that by looking at
.../var/sipxdata/sipdb/credential.xml.   If you do not see a user '274'
in there while you see one in the sipXconfig user pages, this smells
like replication problems and an entry in the job status page of
sipXconfig should echo the replication error.  Unfortunately, if that
turns out to be your problem, I do not know how to fix it but someone on
the list will.
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to