[asterisk-users] Asterisk 1.8 and character sets and AMI

[Örn Arnarson]

Hello again,

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>

I have also attached PCAP files (from a different call setup, but with
same information) for each scenario.

Best regards,
Örn

On Fri, Oct 29, 2010 at 5:08 PM, Tilghman Lesher <tlesher at digium.com> wrote:
> On Friday 29 October 2010 11:46:01 Örn Arnarson wrote:
>> Hi,
>>
>> Just tried upgrading to 1.8 and ran into two problem immediately;
>>
>> 1. 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.
>
> You'll need to include the relevant raw SIP messages for us to know if this
> is compliant behavior or not.
>
>> 2. My AMI scripts have stopped working and Asterisk console shows a
>> Broken Pipe error. Has the I/O to AMI changed? I had a quick glance
>> through the change log and couldn't find anything indicating
>> different. Haven't started looking at what the output looks like, but
>> it would be nice if someone could point me to a document going through
>> the changes so I don't have to re-invent the wheel.
>
> Any change to the protocol should be documented in UPGRADE.txt.  AFAIK,
> there has been no change to the actual protocol, but the various headers
> may have changed slightly to ensure consistency between commands.
>
> --
> Tilghman Lesher
> Digium, Inc. | Senior Software Developer
> twitter: Corydon76 | IRC: Corydon76-dig (Freenode)
> Check us out at: www.digium.com & www.asterisk.org
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>               http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1.6.2.11.pcap
Type: application/x-extension-pcap
Size: 3716 bytes
Desc: not available
Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20101101/ecea24fc/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1.8.0.pcap
Type: application/x-extension-pcap
Size: 3688 bytes
Desc: not available
Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20101101/ecea24fc/attachment-0001.bin