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

[Benjamin on Asterisk Mailing Lists]

I am trying to get Asterisk to register with a SIP provider who
officially only supports ATAs of the incumbent telephone monopolist
over here.

I have so far been lucky enough to get them to ***respond*** to my
requests for information on what parameters need changing in the
REGISTER messages in order to successfully register. Confusion arises
from the fact that there are two different user IDs, one is a
telephone number associated with the SIP account, say 05099999999, the
other is an account name, say DUDEDUDE.

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.

If I use "register => phonenumber at domain.com" then then Asterisk will
construct a REGISTER message with the phone number in both the From
field and the username field in the digest. If I use "register =>
accountname at domain.com" then Asterisk uses the account name in both
places. The optional parameter at the end of the register directive
only seems to have an effect on the contact field, ie "register =>
fred at domain.com/123456789" will still put "fred" into both the From
field and the username field of the digest while "123456789" will show
up in the Contact field only.

Can somebody comment on this?

- is it in compliance with RFC3261 to have different values in the
>From and the Digest username fields?
- can Asterisk construct such a REGISTER message?

To illustrate this a bit further, here is an excerpt from a session
transscript ...

REGISTER sip:ispvoip-9999.ocn.ne.jp SIP/2.0
Via: SIP/2.0/UDP 9.9.9.9:5060;branch=z9hG4bK6920ea27
From: <sip:05099999999 at ispvoip-3437.ocn.ne.jp>;tag=as040e1159
To: <sip:05099999999 at ispvoip-9999.ocn.ne.jp>
Call-ID: 999999999999999999999999999999 at 9.9.9.9
CSeq: 961 REGISTER
Authorization: Digest username="05099999999", realm="ocn.ne.jp",
algorithm="MD5", uri="sip:210.9.9.9", nonce="1099640598",
response="a9d877017f24bb624cdc1a39a8a73b4c", opaque=""
Expires: 120
Contact: <sip:05099999999 at 9.9.9.9>
Event: registration

SIP/2.0 401 Unauthorized
v: SIP/2.0/UDP 9.9.9.9:5060;branch=z9hG4bK6920ea27
From: <sip:05099999999 at ispvoip-9999.ocn.ne.jp>;tag=as040e1159
To: <sip:05099999999 at ispvoip-9999.ocn.ne.jp>
Call-ID: 999999999999999999999999999999 at 9.9.9.9
CSeq: 961 REGISTER
Expires: 120
Event: registration
Date: Fri, 05 Nov 2004 08:17:48 GMT
WWW-Authenticate: Digest realm="ocn.ne.jp", domain="sip:210.9.9.9",
nonce="1099640598", opaque="", stale=FALSE, algorithm=MD5

The provider's support staff suggested that their server expected to
see a REGISTER message like the following:

REGISTER sip:ispvoip-9999.ocn.ne.jp SIP/2.0
Via: SIP/2.0/UDP 9.9.9.9:5060;branch=z9hG4bK6920ea27
From: <sip:05099999999 at ispvoip-3437.ocn.ne.jp>;tag=as040e1159
To: <sip:05099999999 at ispvoip-9999.ocn.ne.jp>
Call-ID: 999999999999999999999999999999 at 9.9.9.9
CSeq: 961 REGISTER
Authorization: Digest username="DUDEDUDE", realm="ocn.ne.jp",
algorithm="MD5", uri="sip:210.9.9.9", nonce="1099640598",
response="a9d877017f24bb624cdc1a39a8a73b4c", opaque=""
Expires: 120
Contact: <sip:05099999999 at 9.9.9.9>
Event: registration

Unfortunately, I have not been able to get Asterisk to construct a
message like the above.

any hints appreciated.

rgds
benjk

-- 
Sunrise Telephone Systems, 9F Shibuya Daikyo Bldg., 1-13-5 Shibuya,
Tokyo, Japan.

NB: Spam filters in place. Messages unrelated to the * mailing lists
may get trashed.