Kurt, However this may cause problems with certain gateways or carriers that use the # character in the tech prefix, your code should be as close to standards as possible and the standard-compliant way is to perform # <-> %23 en-/decoding on both incoming and outgoing messages. In my practice Quintum gateways understand %23 encoding just OK, but Cisco gateways do not. You may implement some sort of workaround, for example keep the list of hosts that have this problem with understanding of "%23" in place of "#" and want to see hash character unquoted.
Mailing List wrote: > Thx Andrew, > > So according to the standard, it must be escaped but in reality it is > send not escaped. So it depends on the SIP stack implementation if it > will be considered as a valid request or not ? Product A will parse > the message but product B can drop the message because it strictly > implements RFC3261 and considers the message being invalid ? > > Regards, > > Kurt -- Sincerely, Andrew Pogrebennyk _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
