[asterisk-users] 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: 000EA: 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) '403814' ] [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: 000EA: 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: 000EA: 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: 000EA: 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: 000EA: 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)
Re: [asterisk-users] Telus (Alberta) PRI Caller ID NAME, Display IE, Facility ID
On 11/6/07, Stephen Bosch [EMAIL PROTECTED] wrote: It survives if it goes to a Telus customer, but not if it crosses over to Bell, Rogers, etc. Well -- here's where you can help me, because our name info is not even surviving on Telus' own network. I don't really care too much about Bell and Rogers, since Bell barely has a footprint out here and Rogers doesn't provide CNAM on its mobile network anyway (and nobody is using Rogers home phone ;) ). So -- if you had it working on Telus, what did you do? As soon as I turned on facilityenable=yes, outbound name display started to work for me. One tech claimed it was because I was sending calling name in addition to the IE, He probably meant the Display IE *and* the Facility IE. If you see my post it's what the technician I was working with suggested. Would be great if I knew a way of turning off the Display IE, if that's even possible/allowed. If it's not, then the don't send both idea is wrong. Probably correct, as that's what I'm sending now: [1c 15 9f 00 00 00 00 00 00 00 00 00 00 00 00 00 43 6f 6d 77 61 76 65] Facility (len=23, codeset=0) [ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 'Namehere'] [00 00 00 00 00 00 00 00 00 00 00] Display (len= 8) Charset: 31 [ Namehere ] I just checked dialing out of and back into my system, and the Facility IE comes back in the SETUP message, but the Display IE does not. Did you end up adding name records to the LIDB? For our purposes name display was a nice to have, so we didn't go down this path. Anyway -- again -- what did you do to get it working on Telus' network? Do you know what kind of switch you were connected to? To the best of my knowledge, we're connected to a 5ESS running NI-2. Here's the relevant zapata bits I use: facilityenable = yes pridialplan=unknown priindication=outofband overlapdial=no resetinterval=86400 echocancel=yes switchtype=national signalling=pri_cpe callerid=asreceived Hope that helps. -- j. ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Telus (Alberta) PRI Caller ID NAME, Display IE, Facility ID
Hi, James -- thanks for your comments. James FitzGibbon wrote: On 11/6/07, *Stephen Bosch* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 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. Well, that's not strictly true. Configurations in BC and Alberta are different, a legacy of the pre BCTel/Telus merger days. BCTel had a lot of GTE Automatic Electric equipment in its network. It survives if it goes to a Telus customer, but not if it crosses over to Bell, Rogers, etc. Well -- here's where you can help me, because our name info is not even surviving on Telus' own network. I don't really care too much about Bell and Rogers, since Bell barely has a footprint out here and Rogers doesn't provide CNAM on its mobile network anyway (and nobody is using Rogers home phone ;) ). So -- if you had it working on Telus, what did you do? One tech claimed it was because I was sending calling name in addition to the IE, He probably meant the Display IE *and* the Facility IE. If you see my post it's what the technician I was working with suggested. Would be great if I knew a way of turning off the Display IE, if that's even possible/allowed. If it's not, then the don't send both idea is wrong. 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). Yeah, I've confirmed that this is an issue through a number of different people. 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. Did you end up adding name records to the LIDB? Anyway -- again -- what did you do to get it working on Telus' network? Do you know what kind of switch you were connected to? -Stephen- ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Telus (Alberta) PRI Caller ID NAME, Display IE, Facility ID
On 11/6/07, Stephen Bosch [EMAIL PROTECTED] 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. ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users