Nokia N95 SIP REGISTER problem
Hi all,
I have a problem registering my N95 phone via a SIP REGISTER.
The SIP register message that I would like the SIP stack on the phone to send should look similar to below:
REGISTER sip:test.abc.com;transport=UDP SIP/2.0
Route: <sip:test.abc.com;lr;transport=UDP>
Via: SIP/2.0/UDP 10.1.0.55:5060;branch=z9hG4bKcbcun07br1hc71i5sbnoe9q;rport
From: <sip:alice;mext=123456@test.abc.com>;tag=f70en01n8dhc7ee0sbno
To: <sip:alice;mext=123456@test.abc.com>
Contact: <sip:alice;mext=123456@10.1.0.55;transport=UDP>;expires=3600
CSeq: 1181 REGISTER
Call-ID: -dTHw5-KoIcKtebLsJC25cmRA10ojK
Supported: sec-agree
User-Agent: Nokia RM-227 1.0633.22.05
Max-Forwards: 70
Content-Length: 0
The problem that I have is that the Sip stack on the N95 phone does not like a SIP user parameter like "alice;mext=123456". If the user parameter is specified like this, the SIP stack does not send any REGISTER (I use Wireshark to monitor the SIP traffic).
If I change the user parameter to "alice" only, the SIP stack sends a REGISTER message as it should!
I have tried the same SIP settings on a Nokia E61i and on a Nokia E65, and the SIP stack on these phones do not have a problem with having the SIP user parameter specified as "alice;mext=123456", they send SIP REGISTER messages that looks like above. I only see this problem on the Nokia N95 phone...
Any ideas?
Regards,
bdun
Re: Nokia N95 SIP REGISTER problem
Normally the SIP-URI parameters are
in the end of the URI like transport=UDP:
<sip:alice@10.1.0.55;transport=UDP;mext=123456>
In practice RFC 3261 ([url]http://www.ietf.org/rfc/rfc3261.txt[/url])
also allows syntax "alice;mext=123456"
in the userinfo part of the URI (see page 221).
I just do not see why you should create a URI like that.
Re: Nokia N95 SIP REGISTER problem
Hi anklemet,
The concept of user parameters is not defined in RFC3261 but allowed by the bnf and the general idea of having it in the user part of the sip uri is that it is domain specific. According to 3261 the user part is case-sensitive but a domain may decide to treat it case-insensitive.
User parameters are used in many rfc:s involving tel uri and I belive Nokia should not have their own opinion about what is allowed in the user part by adding limitations to the client. Instead they should push for an update of RFC3261 to exclude ";" from the bnf.
Examples where user parameters are used:
[url]http://tools.ietf.org/html/rfc3966[/url]
[url]http://tools.ietf.org/html/rfc3261[/url] - 19.1.6 Relating SIP URIs and tel URLs
[url]http://tools.ietf.org/html/rfc4904[/url]
[url]http://tools.ietf.org/html/rfc4967[/url]
/bdun
Re: Nokia N95 SIP REGISTER problem
I think it is clear that there is a bug
in S60 SIP implementation here.
It should allow also SIP-URIs like
"sip:alice;mext=123456@test.abc.com".
Seems that at least RFC 4904 utilizes
these kind of user-parameters.
Nokia should fix this.
