Örn Arnarson
2010-Oct-29 16:46 UTC
[asterisk-users] Asterisk 1.8 and character sets and AMI
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. 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. Anyone have any info on either one? Best regards, ?rn Arnarson
Tilghman Lesher
2010-Oct-29 17:08 UTC
[asterisk-users] Asterisk 1.8 and character sets and AMI
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