Re: [reSIProcate] URI encoding - # symbol

[Alan Hawrylyshen <alan@xxxxxxxxxx>]

On 21-Jan-06, at 5:46 AM, Daniel Pocock wrote:

> I notice in RFC 2396, section 2.4.3, that the # symbol is supposed  
> to be excluded from URIs.
>
> This symbol is commonly used in telecoms, as it is one of the  
> buttons on a DTMF keypad.
>
> It appears that reSIProcate escapes this symbol (Uri.cxx) as %23  
> when writing the URI into a SIP header.
>
> However, many other products behave differently - I've just tried  
> sending a call to a carrier using Nextone, and they don't recognise  
> the escaped #.  Asterisk sends them the # un-escaped, and they  
> accept the call.
>
> - is it maybe a good idea to patch Uri.cxx so that the application  
> can override escaping behaviour, eg, the application could provide  
> a \0 terminated list of characters not to escape?
>
> - has this issue already been discussed elsewhere?  I realise I am  
> new to this list and may have missed something obvious.
>
> Regards,
>
> Daniel

Daniel,
I don't think this has come up before and it is a reasonable  
suggestion. Permitting the application to set (or override) the  
escaped character list would be reasonable in my opinion. Especially  
for interoperability issues.

Alan