[SIPForum-discussion] [SIP-Forum discussion] Support of # into Request-Uri

Sankar Senthil frenzpark at gmail.com
Thu Dec 2 20:15:05 UTC 2010


Hi Federico,

We also experienced the same issue, This could happen

When you send Request-Uri with a # symbol, there are chances that request
uri will be a part in the Call-ID of that Session, According to RFC 3261 the
Call-ID header should not contain a # on that.

If possible take a Wireshark Trace and test a call with # in the Request-Uri
and check whether the Call-ID has the # Symbol.

Regards,
Senthil


On Wed, Dec 1, 2010 at 9:06 PM, Federico piesio <fede.legge at gmail.com>wrote:

> Dear members,
> I have one doubt regarding use of digit # into R-Uri. The vendor of Class4
> softswitch is saying that RFC 3261 specifies that # is not supported as a
> digit in a sip uri or tel uri, so their implementation is that softswitch
> receives a R-Uri containing # and changes digit "#" with extradecadic "C"
> when sending ahead the INVITE.
>
> Does anyone know about this limitation in SIP? I'm really not sure of what
> vendor states about. I didn't find anything about in 3261 or 2806.
>
> Thank you
> Regards
> Federico
>
> _______________________________________________
> This is the SIP Forum discussion mailing list
> TO UNSUBSCRIBE, or edit your delivery options, please visit
> http://sipforum.org/mailman/listinfo/discussion
> Post to the list at discussion at sipforum.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20101203/27469072/attachment-0002.html>


More information about the discussion mailing list