[asterisk-dev] Asterisk 1.8 and character sets
Klaus Darilion
klaus.mailinglists at pernau.at
Wed Nov 10 16:49:58 CST 2010
On 03.11.2010 11:02, Örn Arnarson wrote:
> I sent this first to the Asterisk users list, but this question
> probably belongs on the dev list, so here goes:
>
> Caller-ID behavior is different -- now when I set the caller-id name
> to something with special characters (Ö, for example), the SIP INVITE
> now has %C3%96 instead of the Ö character. I've tried doing
> Set(CALLERID(name-charset)=utf8) as well as iso8859-1, but it's always
> the same behavior.
>
> Here's the header as it appears in 1.6.2.11 CLI output:
>
> INVITE sip:1502 at 192.168.10.169:5060;transport=udp SIP/2.0
> Via: SIP/2.0/UDP 192.168.10.3:5060;branch=z9hG4bK73713002;rport
> Max-Forwards: 70
> From: "SIP ehf/Örn Arnarson"<sip:7712552 at 192.168.10.3>;tag=as2813a8fe
> To:<sip:1502 at 192.168.10.169:5060;transport=udp>
> Contact:<sip:7712552 at 192.168.10.3>
>
> Here is the header with the same caller-id information in 1.8.0:
>
> INVITE sip:1502 at 192.168.10.169:5060;transport=udp SIP/2.0
> Via: SIP/2.0/UDP 192.168.10.3:5060;branch=z9hG4bK1ff411d7
> Max-Forwards: 70
> From: "SIP ehf/%C3%96rn Arnarson"<sip:7712552 at 192.168.10.3>;tag=as701c8835
> To:<sip:1502 at 192.168.10.169:5060;transport=udp>
> Contact:<sip:7712552 at 192.168.10.3:5060>
Have you checked the RFC? I guess that UTF-8 is allowed in the display
name, but %-encoding may be allowed too.
regards
klaus
More information about the asterisk-dev
mailing list