Unicode character "€" inserted from PRI and Dial Plan becomes Unknown

We have a client that is using AT&T IPFlex and we have found a character “€” in Caller ID that is causing our Grandstream GVX3240 phones to lockup on inbound calls. We are working with Grandstream to see why their phone app is crashing when the call is presented to the phone but we believe it is an issue from AT&T and would like to get your help to prove that. We are capturing PRI logs on one of the servers and have evidence that this happens on outbound and inbound calls and the character shows up only from the PRI… possibly dial plan error? I apologize for my lack of full understanding ahead of time, but could really use your help to track this down. We have been fighting it for over 5 months and it has recently intensified with the addition of a Call Center.

Thanks in advance!

Dave

Here is part of the log that show what is happening. I have other larger examples if needed.
Outbound call from 7709571887 to 18002222798 at 8:40 am on 05/05/2016

[2016-05-05 08:40:09] VERBOSE[26152] chan_dahdi.c: PRI Span: 1 > Called Number (len=14) [ Ext: 1 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) ‘18002222798’ ] <— Dial plan is correct
[2016-05-05 08:40:09] VERBOSE[26152] chan_dahdi.c: PRI Span: 1 q931.c:6036 q931_setup: Call 34719 enters state 1 (Call Initiated). Hold state: Idle
[2016-05-05 08:40:09] VERBOSE[26152][C-0000e9ac] app_dial.c: – Called DAHDI/g0/18002222798
[2016-05-05 08:40:09] VERBOSE[17819] chan_dahdi.c: PRI Span: 1
[2016-05-05 08:40:09] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < Protocol Discriminator: Q.931 (8) len=10
[2016-05-05 08:40:09] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < TEI=0 Call Ref: len= 2 (reference 1951/0x79F) (Sent to originator)
[2016-05-05 08:40:09] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < Message Type: CALL PROCEEDING (2)
[2016-05-05 08:40:09] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < [18 03 a9 83 81]
[2016-05-05 08:40:09] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < Channel ID (len= 5) [ Ext: 1 IntID: Implicit Other(PRI) Spare: 0 Exclusive Dchan: 0
[2016-05-05 08:40:09] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < ChanSel: As indicated in following octets
[2016-05-05 08:40:09] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < Ext: 1 Coding: 0 Number Specified Channel Type: 3
[2016-05-05 08:40:09] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < Ext: 1 Channel: 1 Type: CPE]
[2016-05-05 08:40:09] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 Received message for call 0x7fe598471e00 on link 0x7fe5987be7e0 TEI/SAPI 0/0
[2016-05-05 08:40:09] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 – Processing IE 24 (cs0, Channel Identification)
[2016-05-05 08:40:09] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 q931.c:8454 post_handle_q931_message: Call 34719 enters state 3 (Outgoing Call Proceeding). Hold state: Idle
[2016-05-05 08:40:09] VERBOSE[17819] sig_pri.c: Span 1: Processing event PRI_EVENT_PROCEEDING(13)
[2016-05-05 08:40:09] VERBOSE[26152][C-0000e9ac] app_dial.c: – DAHDI/i1/18002222798-16ec is proceeding passing it to SIP/3023-00009d37
[2016-05-05 08:40:11] VERBOSE[17819] chan_dahdi.c: PRI Span: 1
[2016-05-05 08:40:11] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < Protocol Discriminator: Q.931 (8) len=9
[2016-05-05 08:40:11] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < TEI=0 Call Ref: len= 2 (reference 1951/0x79F) (Sent to originator)
[2016-05-05 08:40:11] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < Message Type: PROGRESS (3)
[2016-05-05 08:40:11] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < [1e 02 81 88]
[2016-05-05 08:40:11] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < Progress Indicator (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Private network serving the local user (1)
[2016-05-05 08:40:11] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < Ext: 1 Progress Description: Inband information or appropriate pattern now available. (8) ]
[2016-05-05 08:40:11] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 Received message for call 0x7fe598471e00 on link 0x7fe5987be7e0 TEI/SAPI 0/0
[2016-05-05 08:40:11] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 – Processing IE 30 (cs0, Progress Indicator)
[2016-05-05 08:40:11] VERBOSE[17819] sig_pri.c: Span 1: Processing event PRI_EVENT_PROGRESS(17)
[2016-05-05 08:40:11] VERBOSE[26152][C-0000e9ac] app_dial.c: – DAHDI/i1/18002222798-16ec is making progress passing it to SIP/3023-00009d3
[2016-05-05 08:40:13] VERBOSE[17819] chan_dahdi.c: PRI Span: 1
[2016-05-05 08:40:13] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < Protocol Discriminator: Q.931 (8) len=20
[2016-05-05 08:40:13] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < TEI=0 Call Ref: len= 2 (reference 1951/0x79F) (Sent to originator)
[2016-05-05 08:40:13] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < Message Type: CONNECT (7)
[2016-05-05 08:40:13] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < [4c 0d 80 80 31 38 30 30 32 32 32 32 37 39 38]
[2016-05-05 08:40:13] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 < Connected Number (len=15) [ Ext: 1 TON: Unknown Number Type (0) NPI: Unknown Number Plan (0) ‘€18002222798’ ] <— Dial plan is lost - character is inserted in header
[2016-05-05 08:40:13] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 Received message for call 0x7fe598471e00 on link 0x7fe5987be7e0 TEI/SAPI 0/0
[2016-05-05 08:40:13] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 – Processing IE 76 (cs0, Connected Number)
[2016-05-05 08:40:13] VERBOSE[17819] chan_dahdi.c: PRI Span: 1 q931.c:8384 post_handle_q931_message: Call 34719 enters state 8 (Connect Request). Hold state: Idle
[2016-05-05 08:40:13] VERBOSE[17819] sig_pri.c: Span 1: Processing event PRI_EVENT_ANSWER(8)

Very Strange endeed, you can enable the debug on the PRI card to know how is sending the information. You can do that by setting the debug in the dahdi configuration or using the asterisk cli like:

asterisk -rnvvvvvvvvddddd | tee /tmp/PRIDEBUG.log

Then when you are in the asterisk cli run: PRI INTENSIVE DEBUG SPAN X
where X is the number of your span.

daveman11, did you ever get this resolved? I have a similar issue going on with a PRI coming from ATT. We are getting unicode characters in our p-asserted-identity. We had this issue previously and i would reboot the ATT Cisco router and it would resolve it for a few months.