Dear Divya
As per RFC 3261 section 25.1
<RFC3261>------------------------------------------------------------------
SIP-URI = "sip:" [ userinfo ] hostport uri-parameters [ headers ]
userinfo = ( user / telephone-subscriber ) [ ":" password ] "@"
user = 1*( unreserved / escaped / user-unreserved )
user-unreserved = "&" / "=" / "+" / "$" / "," / ";" / "?" / "/"
unreserved = alphanum / mark
mark = "-" / "_" / "." / "!" / "~" / "*" / "'"
</RFC3261>-----------------------------------------------------------------
and also please note page no 223
<RFC3261>------------------------------------------------------------------
The BNF for telephone-subscriber can be found in RFC 2806 [9]. Note,
however, that any characters allowed there that are not allowed in
the user part of the SIP URI MUST be escaped.
</RFC3261>-----------------------------------------------------------------
Hence apart from the user part what ever the character allowed in
rfc2806 for telephone-subscriber must be escaped.
here # must be escaped.
Regards
Prithvi
Divya Singh wrote:
> Hi,
> Is it syntactically correct to have *# in the username part of the uri?
>
> In Rfc 2806, "*" & "#" are defined as DTMF-digits & it appears that we can
> have tel:*#123 etc. in tel uri's. but what about sip uri's of the form
> sip:[EMAIL PROTECTED];user=phone
> here the username part will be a phone number. So can we have "*" & "#" in
> the username part of the sip uri of the above format ?
>
> You can also refer the relevant Rfc
>
> Regards,
> Divya
>
> *********************** Aricent-Unclassified ***********************
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely
> for the use of
> the individual to whom it is addressed. It may contain privileged or
> confidential information and should not be
> circulated or used for any purpose other than for what it is intended. If you
> have received this message in error,
> please notify the originator immediately. If you are not the intended
> recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of this
> message. Aricent accepts no responsibility for
> loss or damage arising from the use of the information transmitted by this
> email including damage from virus."
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
