Dale R. Worley wrote:
On Thu, 2005-11-17 at 16:05 +0100, Andreas Byström wrote:
My problem is that I'm not sure if a SIP stack would support sending a #
character in a sip URI (or telURI). * is a valid character as far as I can
understand from the RFCs, but the # must be escaped. Is is at all possible
to have # in the sip uri? Do anyone know if any examples (maybe in some call
flows)? The stack I'm currently are using just crashes as soon as I try to
send or receive a #, independent if it is excaped or not...
You should become familiar with section 25.1 of RFC 3261, which
specifies what sorts of escapes can be done where in sip URIs in
exacting detail.
For example, sip:[EMAIL PROTECTED] is valid, but sip:[EMAIL PROTECTED] is not.
You can use sip:[EMAIL PROTECTED], though. If your SIP stack crashes when
it sees that, it has serious bugs.
OTOH, the following are both legal:
tel:*;phone-context=example.com
tel:#;phone-context=example.com
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
