[Asterisk-Users] SIP REGISTER -- Asterisk non-compliant or is it the provider?

[Girish Gopinath]

Hello,

--- Benjamin on Asterisk Mailing Lists <benjk.on.asterisk.ml at gmail.com> wrote:

> The provider's support staff says that the userid in 'From:
> <sip:userid at domain.com> ...' should be the phone number while the
> userid in 'Authorization: Digest username="userid"...' of the same
> REGISTER message should be the account name. I am not sure if this can
> be right. At least, whether compliant or not, it would seem that such
> a REGISTER message cannot be constructed by Asterisk.

The From header field in a SIP message is used to identify the initiator of the request.
AFAIK, the 05099999999 in the From header acts as a display name. It can be used to
determine the processing rules by other SIP entities. For example, PSTN gateways can use
it to determine if it is a valid callerid or not (For INVITEs). The Auth credentials in
the Request can be different. It should be the username and password for the account that
the provider has given you. I hope others here will give a better explanation on this...

> - is it in compliance with RFC3261 to have different values in the
> >From and the Digest username fields?

I think yes. Our UACs register with SIP Express Router with different values in these
fields. Attached below is an ngrep trace of such a request processing.

> - can Asterisk construct such a REGISTER message?
Sorry. I am not sure about this. 

Regards, Girish


Here's the trace:

REGISTER sip:XXX.XXX.XXX.XXX SIP/2.0.
Via: SIP/2.0/UDP 192.168.68.24:12894.
Max-Forwards: 70.
From: <sip:Girish at XXX.XXX.XXX.XXX>;tag=699fdcaedde144a68097a86c5ec00655;epid=7de641515e.
To: <sip:Girish at XXX.XXX.XXX.XXX>.
Call-ID: 8e134249fa054bf9b9ffee10575b6b26 at 192.168.68.24.
CSeq: 1 REGISTER.
Contact: <sip:192.168.68.24:12894>;methods="INVITE, MESSAGE, INFO, SUBSCRIBE, OPTIONS,
BYE, CANCEL, NOTIFY, ACK, REFER".
User-Agent: RTC/1.2.4949 
Event: registration.
Allow-Events: presence.
Content-Length: 0.
.
 
SIP/2.0 401 Unauthorized.
Via: SIP/2.0/UDP 192.168.68.24:12894;rport=4061;received=XX.XX.XX.XXX.
From: <sip:Girish at XXX.XXX.XXX.XXX>;tag=699fdcaedde144a68097a86c5ec00655;epid=7de641515e.
To: <sip:Girish at XXX.XXX.XXX.XXX>;tag=b27e1a1d33761e85846fc98f5f3a7e58.d1fd.
Call-ID: 8e134249fa054bf9b9ffee10575b6b26 at 192.168.68.24.
CSeq: 1 REGISTER.
WWW-Authenticate: Digest realm="XXX.XXX.XXX.XXX",
nonce="418cd4b94a2ea94004191fd618b7bbb7041f8f40", qop="auth".
Server: SIP EXpress Router (0.8.14 (i386/linux)).
Content-Length: 0.
.
.
REGISTER sip:XXX.XXX.XXX.XXX SIP/2.0.
Via: SIP/2.0/UDP 192.168.68.24:12894.
Max-Forwards: 70.
From: <sip:Girish at XXX.XXX.XXX.XXX>;tag=699fdcaedde144a68097a86c5ec00655;epid=7de641515e.
To: <sip:Girish at XXX.XXX.XXX.XXX>.
Call-ID: 8e134249fa054bf9b9ffee10575b6b26 at 192.168.68.24.
CSeq: 2 REGISTER.
Contact: <sip:192.168.68.24:12894>;methods="INVITE, MESSAGE, INFO, SUBSCRIBE, OPTIONS,
BYE, CANCEL, NOTIFY, ACK, REFER".
User-Agent: RTC/1.2.4949
Authorization: Digest username="girish-smarttest-com", realm="XXX.XXX.XXX.XXX", qop=auth,
algorithm=md5, uri="sip:XXX.XXX.XXX.XXX",
nonce="418cd4b94a2ea94004191fd618b7bbb7041f8f40", nc=00000001,
cnonce="15420645451543562242791578613325", response="89d8531e598629b022230df475b5bb65".
Event: registration.
Allow-Events: presence.
Content-Length: 0.
.
.
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 192.168.68.24:12894;rport=4061;received=XX.XX.XX.XXX.
From: <sip:Girish at XXX.XXX.XXX.XXX>;tag=699fdcaedde144a68097a86c5ec00655;epid=7de641515e.
To: <sip:Girish at XXX.XXX.XXX.XXX>;tag=b27e1a1d33761e85846fc98f5f3a7e58.d1fd.
Call-ID: 8e134249fa054bf9b9ffee10575b6b26 at 192.168.68.24.
CSeq: 2 REGISTER.
Expires: 120.
Contact: <sip:XX.XX.XX.XXX:4061>;q=0.00;expires=3600.
Server: SIP EXpress Router (0.8.14 (i386/linux)).
Content-Length: 0.



		
__________________________________ 
Do you Yahoo!? 
Check out the new Yahoo! Front Page. 
www.yahoo.com