Re: Register Unauthorized issue -- ven if correct Realm is specified
Manoj Joshi <manoj <at> ascenttelecom.com>
2009-05-15 15:33:28 GMT
Ok...
Actually the SIP Server is Nextone MSX. I am not sure they will make any
changes at their side. Can you suggest some workaround?
I wonder how x-lite is able to register.
Regards,
Manoj
-----Original Message-----
From: Daniel Petrie [mailto:dpetrie <at> sipez.com]
Sent: Friday, May 15, 2009 8:24 PM
To: Alexander Chemeris; Manoj Joshi
Cc: sipxtapi-dev <at> list.sipfoundry.org
Subject: RE: [sipxtapi-dev] Register Unauthorized issue -- ven if
correct Realm is specified
Hi Manoj:
The registry server that you are using in this case is broken. It is
sending the 401 response with no Cseq header (should be Cseq: 101). As such
it is an invalid SIP response that cannot be matched to the REGISTER
request. You will notice that the REGISTER request is resent several times
as defined by RFC3261 for reliability (search for resend in log) it then
attempts resending over TCP. The 401 responses are ignored as they do not
match the transaction for the REGISTER request.
sipX will not send a REGISTER request with authentication info it it as it
never receives the 401 with the realm and nonce which it needs to send an
authenticated REGISTER request.
Cheers,
Dan
--- On Fri, 5/15/09, Manoj Joshi <manoj <at> ascenttelecom.com> wrote:
> From: Manoj Joshi <manoj <at> ascenttelecom.com>
> Subject: RE: [sipxtapi-dev] Register Unauthorized issue -- ven if correct
Realm is specified
> To: dpetrie <at> sipez.com, "Alexander Chemeris" <Alexander.Chemeris <at> sipez.com>
> Cc: sipxtapi-dev <at> list.sipfoundry.org
> Date: Friday, May 15, 2009, 9:33 AM
> Hello Dan,
>
> Thank you for the reply. I made sure i am using correct
> credentials. To
> double check i used the same User with X-lite and it
> registered instantly. I
> am attaching the complete SIPXtapi log for your reference.
>
> Additionally i am also sending you all credentials here so
> that you can
> verify at your end as well may be by using it on SIpx
> phone.
>
> 1. SIP Server IP: sip.checkcdr.com / 217.72.243.59
>
> 2. SIP Port: 5060
>
> 3. Test Account: 399917
>
> 4. Test PIN: 840759
>
> Plaese note that "217.72.243.59" is coming as Realm in 401
> response.
>
> Regards,
>
> Manoj
>
> -----Original Message-----
> From: Daniel Petrie [mailto:dpetrie <at> sipez.com]
> Sent: Friday, May 15, 2009 6:33 PM
> To: Alexander Chemeris; Manoj Joshi
> Cc: sipxtapi-dev <at> list.sipfoundry.org
> Subject: Re: [sipxtapi-dev] Register Unauthorized issue --
> ven if
> correct Realm is specified
>
>
>
> 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:399917 <at> sip.checkcdr.com,
> 399917, 399917 <at> sip.checkcdr.com)
> 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 <manoj <at> ascenttelecom.com>
> wrote:
>
> > From: Manoj Joshi <manoj <at> ascenttelecom.com>
> > Subject: [sipxtapi-dev] Register Unauthorized issue --
> ven if correct
> Realm is specified
> > To: "Alexander Chemeris" <Alexander.Chemeris <at> sipez.com>
> > Cc: sipxtapi-dev <at> list.sipfoundry.org
> > 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:399917 <at> sip.checkcdr.com;tag=54c76b10\r\nTo:
> > sip:399917 <at> sip.checkcdr.com\r\nCall-Id:
> > 43686df6a892f0153535663565dc18a6\r\nCseq: 101
> > REGISTER\r\nContact:
> >
> <sip:399917 <at> 192.168.0.5: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:399917 <at> sip.checkcdr.com;tag=54c76b10\r\nTo:
> > sip:399917 <at> sip.checkcdr.com\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:399917 <at> sip.checkcdr.com;tag=54c76b10\r\nTo:
> > sip:399917 <at> sip.checkcdr.com\r\nCall-Id:
> > 43686df6a892f0153535663565dc18a6\r\nCseq: 101
> > REGISTER\r\nContact:
> >
> <sip:399917 <at> 192.168.0.5: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:399917 <at> sip.checkcdr.com;tag=54c76b10\r\nTo:
> > sip:399917 <at> sip.checkcdr.com\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
>
>
>
> --
> Internal Virus Database is out-of-date.
> Checked by AVG.
> Version: 7.5.557 / Virus Database: 270.12.11/2089 - Release
> Date: 4/30/2009
> 5:53 PM
>
>
--
Internal Virus Database is out-of-date.
Checked by AVG.
Version: 7.5.557 / Virus Database: 270.12.11/2089 - Release Date: 4/30/2009
5:53 PM
_______________________________________________
sipxtapi-dev mailing list
sipxtapi-dev <at> list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
RSS Feed