Hi Manoj: The trace you sent does not contain the re-REGISTER attempt with the Auth header and digest from sipX. It has the original REGISTER in it for Cseq 101 twice. Without that I can only guess at some common issues people have with configuration.
Here is a guess at somethings that you can check. The first thing that I would do would be to verify that you are using the correct password AND more importantly the correct user ID expected by the server. Some server use all or different parts of the address of record (AOR) (e.g. sip:[email protected], 399917, [email protected]) for the authentication user ID or completely different strings for the user IDs for authentication that do not contain any part of the AOR. Some servers use multiple passwords (e.g. for different contexts). This can sometimes get confusing. If you are sure of these things, send me a trace using a password that you are willing to give out and I can check the calculations of the MD5 hash. Cheers, Dan --- On Fri, 5/15/09, Manoj Joshi <[email protected]> wrote: > From: Manoj Joshi <[email protected]> > Subject: [sipxtapi-dev] Register Unauthorized issue -- ven if correct Realm > is specified > To: "Alexander Chemeris" <[email protected]> > Cc: [email protected] > Date: Friday, May 15, 2009, 3:53 AM > Hello, > > I am using SIPXtapi and its working well with many of the > SIP Servers. But > with some proxy servers it does not registers. > > Detailed issue description > **************************** > 1- SIPXTapi sends register request (without > WWW-Authenticate header) > 2- SIP Proxy (Nextone) rejects register with 401 > Unauthorized. > 3- SIPXtapi keeps on sending register request WITHOUT > WWW-Authenticate > header (I can see that Realm is correctly specified) > > Logs > ******************* > > First Register > ++++++++++++++++ > "SipUserAgent::sendUdp UDP SIP User Agent sent > message:\n----Remote > Host:217.72.243.59---- Port: 5060----\nREGISTER > sip:sip.checkcdr.com > SIP/2.0\r\nFrom: sip:[email protected];tag=54c76b10\r\nTo: > sip:[email protected]\r\ncall-id: > 43686df6a892f0153535663565dc18a6\r\nCseq: 101 > REGISTER\r\nContact: > <sip:[email protected]:16281;LINEID=1ab69e9e48d9>\r\nExpires: > 3600\r\nDate: > Fri, 15 May 2009 07:25:50 GMT\r\nMax-Forwards: > 70\r\nUser-Agent: > 399917\r\nAccept-Language: \r\nSupported: replaces\r\nVia: > SIP/2.0/UDP > 192.168.0.5:16281;branch=z9hG4bK-3bebc0f84853;rport\r\nContent-Length: > 0\r\n\r\n--------------------END--------------------\n" > > Reject Response > ++++++++++++++++++ > "Read SIP message:\n----Remote Host:217.72.243.59---- > Port: > 5060----\nSIP/2.0 401 Unauthorized\r\nVia: SIP/2.0/UDP > 192.168.0.5:16281;branch=z9hG4bK-3bebc0f84853;rport\r\nFrom: > sip:[email protected];tag=54c76b10\r\nTo: > sip:[email protected]\r\nwww-authenticate: > Digest > realm=\"217.72.243.59\", nonce=\"1242372372\", > algorithm=MD5\r\nContent-Length: > 0\r\n\r\n====================END====================\n" > > Fiurther Register and Reject messages > +++++++++++++++++++++++++++++++++++++++++ > SIP User Agent sent message:\n----Remote > Host:217.72.243.59---- Port: > 5060----\nREGISTER sip:sip.checkcdr.com SIP/2.0\r\nFrom: > sip:[email protected];tag=54c76b10\r\nTo: > sip:[email protected]\r\ncall-id: > 43686df6a892f0153535663565dc18a6\r\nCseq: 101 > REGISTER\r\nContact: > <sip:[email protected]:16281;LINEID=1ab69e9e48d9>\r\nExpires: > 3600\r\nDate: > Fri, 15 May 2009 07:25:50 GMT\r\nMax-Forwards: > 70\r\nUser-Agent: > 399917\r\nAccept-Language: \r\nSupported: replaces\r\nVia: > SIP/2.0/UDP > 192.168.0.5:16281;branch=z9hG4bK-3bebc0f84853;rport\r\nContent-Length: > 0\r\n\r\n--------------------END--------------------\n" > Read SIP message:\n----Remote Host:217.72.243.59---- Port: > 5060----\nSIP/2.0 > 401 Unauthorized\r\nVia: SIP/2.0/UDP > 192.168.0.5:16281;branch=z9hG4bK-3bebc0f84853;rport\r\nFrom: > sip:[email protected];tag=54c76b10\r\nTo: > sip:[email protected]\r\nwww-authenticate: > Digest > realm=\"217.72.243.59\", nonce=\"1242372372\", > algorithm=MD5\r\nContent-Length: > 0\r\n\r\n====================END====================\n" > > > Not able to understand whats wrong > > Regards, > > Manoj _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
