asterisk users - Nov 2007 - Telus (Alberta) PRI Caller ID NAME, Display IE, Facility ID

We are trying to send caller ID NAME information over a Telus PRI in 
Alberta.

The PRI tech says that he sees the NAME information, and for calls over 
the same network, that NAME info should be reaching the receiving 
station, but it is not.

The technician was stumped. I suspect there's something specific that I 
need to do to make it work, since many PBXs can do this. The switch is a 
Nortel DMS 100 in National ISDN 2 mode.

I've put some 'pri intense debug' output below. Names and numbers
have
been changed to protect the innocent :)

Is there anybody out there using a Sangoma A10X series card on a Telus 
PRI in Alberta, and do you have CID NAME working?
>> Informational frame:
>> SAPI: 00  C/R: 0 EA: 0
>>  TEI: 000        EA: 1
>> N(S): 043   0: 0
>> N(R): 039   P: 0
>> 90 bytes of data
> -- Restarting T203 counter
> Stopping T_203 timer
> Starting T_200 timer
>> Protocol Discriminator: Q.931 (8)  len=90
>> Call Ref: len= 2 (reference 4/0x4) (Originator)
>> Message type: SETUP (5)
>> [04 03 80 90 a2]
>> Bearer Capability (len= 5) [ Ext: 1  Q.931 Std: 0  Info transfer
capability: Speech (0)
>>                              Ext: 1  Trans mode/rate: 64kbps,
circuit-mode (16)
>>                              Ext: 1  User information layer 1: u-Law
(34)
>> [18 03 a9 83 81]
>> Channel ID (len= 5) [ Ext: 1  IntID: Implicit, PRI Spare: 0, Exclusive
Dchan: 0
>>                        ChanSel: Reserved
>>                       Ext: 1  Coding: 0   Number Specified   Channel
Type: 3
>>                       Ext: 1  Channel: 1 ]
>> [1c 1a 9f 8b 01 00 a1 14 02 01 04 02 01 00 80 0c 41 63 75 72 65 20 48
65 61 6c 74 68]
>> Facility (len=28, codeset=0) [ 0x9f, 0x8b, 0x01, 0x00, 0xa1, 0x14,
0x02, 0x01, 0x04, 0x02, 0x01, 0x00, 0x80, 0x0c, 'Customer', 0x20,
'Health' ]
>> [1e 02 80 83]
>> Progress Indicator (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)
0: 0   Location: User (0)
>>                               Ext: 1  Progress Description: Calling
equipment is non-ISDN. (3) ]
>> [28 0d b1 41 63 75 72 65 20 48 65 61 6c 74 68]
>> Display (len=13) Charset: 31 [ Customer Name ]
>> [6c 0c 21 80 34 30 33 35 33 39 35 37 39 37]
>> Calling Number (len=14) [ Ext: 0  TON: National Number (2)  NPI:
ISDN/Telephony Numbering Plan (E.164/E.163) (1)
>>                           Presentation: Presentation permitted, user
number not screened (0) '4035555814' ]
>> [70 0c a1 31 36 30 34 32 39 38 32 37 39 34]
>> Called Number (len=14) [ Ext: 1  TON: National Number (2)  NPI:
ISDN/Telephony Numbering Plan (E.164/E.163) (1) '16045552794' ]
>     -- Called g0/16045552794
> pbx*CLI>
> < [ 00 01 01 58 ]
You can see that it's sending both Facility IE and Display IE name 
information. The technician was suggesting that sending both might be 
the problem. If so, I have no idea how to turn off the Display IE, and I 
solicit suggestions :)

The rest of the PRI stuff is just call setup.
> 
> < Supervisory frame:
> < SAPI: 00  C/R: 0 EA: 0
> <  TEI: 000        EA: 1
> < Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
> < N(R): 044 P/F: 0
> < 0 bytes of data
> -- ACKing all packets from 42 to (but not including) 44
> -- ACKing packet 43, new txqueue is -1 (-1 means empty)
> -- Since there was nothing left, stopping T200 counter
> -- Nothing left, starting T203 counter
> -- Restarting T203 counter
> pbx*CLI>
> < [ 02 01 4e 58 08 02 80 04 02 18 03 a9 83 81 ]
> pbx*CLI>
> < Informational frame:
> < SAPI: 00  C/R: 1 EA: 0
> <  TEI: 000        EA: 1
> < N(S): 039   0: 0
> < N(R): 044   P: 0
> < 10 bytes of data
> -- ACKing all packets from 43 to (but not including) 44
> -- Since there was nothing left, stopping T200 counter
> -- Stopping T203 counter since we got an ACK
> -- Nothing left, starting T203 counter
> < Protocol Discriminator: Q.931 (8)  len=10
> < Call Ref: len= 2 (reference 4/0x4) (Terminator)
> < Message type: CALL PROCEEDING (2)
> < [18 03 a9 83 81]
> < Channel ID (len= 5) [ Ext: 1  IntID: Implicit, PRI Spare: 0, Exclusive
Dchan: 0
> <                        ChanSel: Reserved
> <                       Ext: 1  Coding: 0   Number Specified   Channel
Type: 3
> <                       Ext: 1  Channel: 1 ]
> Sending Receiver Ready (40)
> 
>> [ 02 01 01 50 ]
> 
>> Supervisory frame:
>> SAPI: 00  C/R: 1 EA: 0
>>  TEI: 000        EA: 1
>> Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
>> N(R): 040 P/F: 0
>> 0 bytes of data
> -- Restarting T203 counter
> -- Restarting T203 counter
>     -- Zap/1-1 is proceeding passing it to SIP/121-082399e8
> pbx*CLI>
> < [ 02 01 50 58 08 02 80 04 01 1e 02 80 88 ]
> pbx*CLI>
> < Informational frame:
> < SAPI: 00  C/R: 1 EA: 0
> <  TEI: 000        EA: 1
> < N(S): 040   0: 0
> < N(R): 044   P: 0
> < 9 bytes of data
> -- ACKing all packets from 43 to (but not including) 44
> -- Since there was nothing left, stopping T200 counter
> -- Stopping T203 counter since we got an ACK
> -- Nothing left, starting T203 counter
> < Protocol Discriminator: Q.931 (8)  len=9
> < Call Ref: len= 2 (reference 4/0x4) (Terminator)
> < Message type: ALERTING (1)
> < [1e 02 80 88]
> < Progress Indicator (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)
0: 0   Location: User (0)
> <                               Ext: 1  Progress Description: Inband
information or appropriate pattern now available. (8) ]
> Sending Receiver Ready (41)
> 
>> [ 02 01 01 52 ]
> pbx*CLI>
>> Supervisory frame:
>> SAPI: 00  C/R: 1 EA: 0
>>  TEI: 000        EA: 1
>> Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
>> N(R): 041 P/F: 0
>> 0 bytes of data
> -- Restarting T203 counter
> -- Restarting T203 counter
>     -- Zap/1-1 is ringing
> T203 counter expired, sending RR and scheduling T203 again
> Sending Receiver Ready (41)
> 
>> [ 00 01 01 53 ]
> pbx*CLI>
>> Supervisory frame:
>> SAPI: 00  C/R: 0 EA: 0
>>  TEI: 000        EA: 1
>> Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
>> N(R): 041 P/F: 1
>> 0 bytes of data
> -- Restarting T203 counter
> pbx*CLI>
> < [ 00 01 01 59 ]
> pbx*CLI>
> < Supervisory frame:
> < SAPI: 00  C/R: 0 EA: 0
> <  TEI: 000        EA: 1
> < Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
> < N(R): 044 P/F: 1
> < 0 bytes of data
> -- ACKing all packets from 43 to (but not including) 44
> -- Since there was nothing left, stopping T200 counter
> -- Stopping T203 counter since we got an ACK
> -- Nothing left, starting T203 counter
> -- Got RR response to our frame
> -- Restarting T203 counter
> pbx*CLI>
> < [ 02 01 52 58 08 02 80 04 07 ]
> pbx*CLI>
> < Informational frame:
> < SAPI: 00  C/R: 1 EA: 0
> <  TEI: 000        EA: 1
> < N(S): 041   0: 0
> < N(R): 044   P: 0
> < 5 bytes of data
> -- ACKing all packets from 43 to (but not including) 44
> -- Since there was nothing left, stopping T200 counter
> -- Stopping T203 counter since we got an ACK
> -- Nothing left, starting T203 counter
> < Protocol Discriminator: Q.931 (8)  len=5
> < Call Ref: len= 2 (reference 4/0x4) (Terminator)
> < Message type: CONNECT (7)
> pbx*CLI>
>> [ 00 01 58 54 08 02 00 04 0f ]
> pbx*CLI>
>> Informational frame:
>> SAPI: 00  C/R: 0 EA: 0
>>  TEI: 000        EA: 1
>> N(S): 044   0: 0
>> N(R): 042   P: 0
>> 5 bytes of data
> -- Restarting T203 counter
> Stopping T_203 timer
> Starting T_200 timer
>> Protocol Discriminator: Q.931 (8)  len=5
>> Call Ref: len= 2 (reference 4/0x4) (Originator)
>> Message type: CONNECT ACKNOWLEDGE (15)

Here's the zapata.conf:
> ;autogenerated by /usr/local/sbin/config-zaptel  do not hand edit
> ;Zaptel Channels Configurations (zapata.conf)
> ;
> ;For detailed zapata options, view /etc/asterisk/zapata.conf.orig
> 
> [trunkgroups]
> 
> [channels]
> context=default
> usecallerid=yes
> hidecallerid=no
> callwaiting=yes
> usecallingpres=yes
> callwaitingcallerid=yes
> threewaycalling=yes
> transfer=yes
> canpark=yes
> cancallforward=yes
> callreturn=yes
> echocancel=yes
> echocancelwhenbridged=yes
> relaxdtmf=yes
> rxgain=0.0
> txgain=0.0
> group=1
> callgroup=1
> pickupgroup=1
> 
> immediate=no
> 
> ;Sangoma A101 port 1 [slot:2 bus:4 span: 1]
> switchtype=national
> nsf=none
> facilityenable=yes
> context=from-pstn
> group=0
> signalling=pri_cpe
> channel => 1-23
> ;channel => 1-10
Ideas and suggestions welcome. Many thanks!

-Stephen-

On 11/6/07, Stephen Bosch <posting at vodacomm.ca>
wrote:
>
> We are trying to send caller ID NAME information over a Telus PRI in
> Alberta.
>
> The PRI tech says that he sees the NAME information, and for calls over
> the same network, that NAME info should be reaching the receiving
> station, but it is not.

I've had no end of trouble getting CNAM out of NI-2 PRIs with Telus. 
We're
in Ontario, but the switch configs are the same across the country I
believe.

It survives if it goes to a Telus customer, but not if it crosses over to
Bell, Rogers, etc.

One tech claimed it was because I was sending calling name in addition to
the IE, while another claimed it was just a problem when the call passes
from a NI-2 circuit to NI-1 (which some of the other carriers still use).

So, no real solution for you, but at least you know it's not something
obvious you're doing.  I've tweaked my zaptel settings back and forth
and
tested with Telus on the phone to no avail.  In the end, we deemed the
effort to not be worth it.

-- 
j.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20071106/f5e8aa37/attachment.htm