Kris Boutilier
2004-Sep-16  02:48 UTC
[Asterisk-Users] No Caller Name sent from Asterisk over National or DMS100 PRI to a Norstar MICS?
I have a PRI link up and running between Asterisk and a Nortel Norstar MICS
v4.1 . I'm having a problem getting the textual Caller Name across the link
from Ast to Ns, however numeric Caller ID arrives and displays fine. From Ns
to Ast both elements come through fine. I'm forcing dummy values for testing
using:
 exten => s,1,SetCIDName(Test)
 exten => s,2,SetCallerID(1234561234)
 exten => s,3,Dial(zap/g1/${ARG1},15)
I've tried switchtype=national and dms100 (adjusting accordingly on Ns) with
no change. zapata.conf is currently:
 ; Norstar #2 (Wharf Road)
 context=in-t1nstar
 group=1
 usecallerid=yes
 hidecallerid=no
 usecallingpres=no
 switchtype=dms100
 pridialplan=local
 signalling=pri_net
 channel => 1-23
The SETUP frame from Ast contains:
> Protocol Discriminator: Q.931 (8)  len=40
> Call Ref: len= 2 (reference 2/0x2) (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 a1 83 81]
> Channel ID (len= 5) [ Ext: 1  IntID: Implicit, PRI Spare: 0, Preferred
Dchan: 0>                        ChanSel: Reserved
>                       Ext: 1  Coding: 0   Number Specified   Channel Type:
3>                       Ext: 1  Channel: 1 ]
> [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) ]> [6c 0c 21 80 31 32 33 34 35 36 31 32 33 34]
> 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) '1234561234' ]> [70 05 c1 36 31 30 31]
> Called Number (len= 7) [ Ext: 1  TON: Subscriber Number (4)  NPI:
ISDN/Telephony Numbering Plan (E.164/E.163) (1) '6101' ]
Which doesn't seem to even contain the CIDName... On the other hand, the
SETUP frame from the Ns contains:
< Protocol Discriminator: Q.931 (8)  len=56
< Call Ref: len= 2 (reference 1/0x1) (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 a1 83 97]
< Channel ID (len= 5) [ Ext: 1  IntID: Implicit, PRI Spare: 0, Preferred
Dchan: 0
<                        ChanSel: Reserved
<                       Ext: 1  Coding: 0   Number Specified   Channel Type:
3
<                       Ext: 1  Channel: 23 ]
< [28 0b b1 53 43 52 44 20 4b 72 69 73 42]
< Display (len=11) Charset: 31 [ SCRD KrisB ]
< [6c 0c 21 80 36 30 34 38 38 35 36 38 30 38]
< 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) '6048856808' ]
< [70 0c 80 39 36 30 34 38 38 35 36 38 30 38]
< Called Number (len=14) [ Ext: 1  TON: Unknown Number Type (0)  NPI:
Unknown Number Plan (0) '96048856808' ]
Which has the textual ID in the 'Display' element... However I
understand
from http://resource.intel.com/telecom/support/tnotes/tnbyos/2000/tn033.htm
that there is no definitive standard for transmitting the name.
So, should even I be expecting Ast to put the name on the wire when it's
originating? 
Kris Boutilier
Information Systems Coordinator
Sunshine Coast Regional District
David Troy
2004-Sep-16  04:57 UTC
[Asterisk-Users] No Caller Name sent from Asterisk over National or DMS100 PRI to a Norstar MICS?
Bill Lohr, et al: I can say from personal experience that with a PRI in MD (Verizon or Verizon-CLEC) territory, it is possible to inject CALLER ID NUMBER on a per call basis regardless of what channel the call originates from. The callee's PSTN carrier performs a reverse lookup on the NUMBER and displays whatever name is in the public directory they use for the reverse lookup. For instance, it is possible to set your Caller ID Number on an outbound PRI call to 202-456-1414; on the callee's caller ID Display, the name and number will read "THE WHITE HOUSE" <202-456-1414>. However, I do not recommend doing this. It is just a colorful example. I do not believe it is possible to set Caller ID Number on a per-call basis using anything other than a PRI or other ISDN/SS7 interconnection. Possibly there are ways it can be tweaked with other types of signalling but most carriers are probably unwilling/unable to support it. I do not believe there is any instance where the PSTN will pay any attention at all to *-set Caller ID Name fields on outbound calls; this app/field is seemingly only used by non pstn channels, such as SIP. Setting Caller ID Number dynamically on a per call basis on a POTS, channelized T1, or other sort of line is definitely not possible. With Caller ID Name for inbound calls, this is a configurable setting on a PRI and your provider may or may not be giving you that data. It is almost always sent on a POTS line. Additionally there are some special values for the Caller ID Name field that CPE can interpret: "O" means "Out of Area", "P" for "Private", etc. As for solving the Caller ID Name problem for outbound calls, I am somewhat stumped. Presumably, this data is generated, compiled, and maintained by the ILEC/CLECs involved. In theory, CLECs who issue phone numbers to their customers should be responsible for the reverse mapping and sharing of this information, however, as we live in a world where CLEC's freely trade numbering resources and reverse lookups are not a top business priority, results may vary considerably. Not to mention most ILECs couldn't care less about CLEC numbers and what is displayed. They'd be happy to sabotage that process entirely and undoubtedly that's what they are doing, whether actively or by default. Outbound calls from Vonage, which is for the most part PRI based, indicate a proper Caller ID Number, however the reverse name lookups I have seen indicate "VONAGE" as the Caller ID Name. Since Vonage is getting its lines from various CLECs, somewhere somebody has managed to set the reverse lookup for their numbers to "VONAGE" in a public database that Verizon listens to. If anyone has any real insight or experience with this process or the applicable databases, I'd love to hear about it. Dave> I have a PRI link up and running between Asterisk and a Nortel Norstar MICS > v4.1 . I'm having a problem getting the textual Caller Name across the link > from Ast to Ns, however numeric Caller ID arrives and displays fine. From Ns > to Ast both elements come through fine. I'm forcing dummy values for testing > using: > > exten => s,1,SetCIDName(Test) > exten => s,2,SetCallerID(1234561234) > exten => s,3,Dial(zap/g1/${ARG1},15) > > I've tried switchtype=national and dms100 (adjusting accordingly on Ns) with > no change. zapata.conf is currently: > > ; Norstar #2 (Wharf Road) > context=in-t1nstar > group=1 > usecallerid=yes > hidecallerid=no > usecallingpres=no > switchtype=dms100 > pridialplan=local > signalling=pri_net > channel => 1-23 > > The SETUP frame from Ast contains: > >> Protocol Discriminator: Q.931 (8) len=40 >> Call Ref: len= 2 (reference 2/0x2) (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 a1 83 81] >> Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, Preferred > Dchan: 0 >> ChanSel: Reserved >> Ext: 1 Coding: 0 Number Specified Channel Type: > 3 >> Ext: 1 Channel: 1 ] >> [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) ] >> [6c 0c 21 80 31 32 33 34 35 36 31 32 33 34] >> 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) '1234561234' ] >> [70 05 c1 36 31 30 31] >> Called Number (len= 7) [ Ext: 1 TON: Subscriber Number (4) NPI: > ISDN/Telephony Numbering Plan (E.164/E.163) (1) '6101' ] > > Which doesn't seem to even contain the CIDName... On the other hand, the > SETUP frame from the Ns contains: > > < Protocol Discriminator: Q.931 (8) len=56 > < Call Ref: len= 2 (reference 1/0x1) (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 a1 83 97] > < Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, Preferred > Dchan: 0 > < ChanSel: Reserved > < Ext: 1 Coding: 0 Number Specified Channel Type: > 3 > < Ext: 1 Channel: 23 ] > < [28 0b b1 53 43 52 44 20 4b 72 69 73 42] > < Display (len=11) Charset: 31 [ SCRD KrisB ] > < [6c 0c 21 80 36 30 34 38 38 35 36 38 30 38] > < 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) '6048856808' ] > < [70 0c 80 39 36 30 34 38 38 35 36 38 30 38] > < Called Number (len=14) [ Ext: 1 TON: Unknown Number Type (0) NPI: > Unknown Number Plan (0) '96048856808' ] > > Which has the textual ID in the 'Display' element... However I understand > from http://resource.intel.com/telecom/support/tnotes/tnbyos/2000/tn033.htm > that there is no definitive standard for transmitting the name. > > So, should even I be expecting Ast to put the name on the wire when it's > originating? > > Kris Boutilier > Information Systems Coordinator > Sunshine Coast Regional District > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-- ====================================================================David C. Troy [dave@toad.net] 410-384-2500 Sales ToadNet - Expect More! 410-544-1329 FAX 570 Ritchie Highway, Severna Park, MD 21146-2925 www.toad.net
Alfred Nurnberger
2004-Sep-16  07:23 UTC
[Asterisk-Users] No Caller Name sent from Asterisk over National or DMS100 PRI to a Norstar MICS?
There is a bugreport open about * when set as PRI_NET sending the CNAME field in the DISPLAY IE instead of the FACILITY IE. Look at bugs.digium.com, I don't rmember the bugreport number. -Alfred. Kris Boutilier wrote:>I have a PRI link up and running between Asterisk and a Nortel Norstar MICS >v4.1 . I'm having a problem getting the textual Caller Name across the link >from Ast to Ns, however numeric Caller ID arrives and displays fine. From Ns >to Ast both elements come through fine. I'm forcing dummy values for testing >using: > > exten => s,1,SetCIDName(Test) > exten => s,2,SetCallerID(1234561234) > exten => s,3,Dial(zap/g1/${ARG1},15) > >I've tried switchtype=national and dms100 (adjusting accordingly on Ns) with >no change. zapata.conf is currently: > > ; Norstar #2 (Wharf Road) > context=in-t1nstar > group=1 > usecallerid=yes > hidecallerid=no > usecallingpres=no > switchtype=dms100 > pridialplan=local > signalling=pri_net > channel => 1-23 > >The SETUP frame from Ast contains: > > > >>Protocol Discriminator: Q.931 (8) len=40 >>Call Ref: len= 2 (reference 2/0x2) (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 a1 83 81] >>Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, Preferred >> >> >Dchan: 0 > > >> ChanSel: Reserved >> Ext: 1 Coding: 0 Number Specified Channel Type: >> >> >3 > > >> Ext: 1 Channel: 1 ] >>[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) ] > > >>[6c 0c 21 80 31 32 33 34 35 36 31 32 33 34] >>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) '1234561234' ] > > >>[70 05 c1 36 31 30 31] >>Called Number (len= 7) [ Ext: 1 TON: Subscriber Number (4) NPI: >> >> >ISDN/Telephony Numbering Plan (E.164/E.163) (1) '6101' ] > >Which doesn't seem to even contain the CIDName... On the other hand, the >SETUP frame from the Ns contains: > >< Protocol Discriminator: Q.931 (8) len=56 >< Call Ref: len= 2 (reference 1/0x1) (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 a1 83 97] >< Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, Preferred >Dchan: 0 >< ChanSel: Reserved >< Ext: 1 Coding: 0 Number Specified Channel Type: >3 >< Ext: 1 Channel: 23 ] >< [28 0b b1 53 43 52 44 20 4b 72 69 73 42] >< Display (len=11) Charset: 31 [ SCRD KrisB ] >< [6c 0c 21 80 36 30 34 38 38 35 36 38 30 38] >< 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) '6048856808' ] >< [70 0c 80 39 36 30 34 38 38 35 36 38 30 38] >< Called Number (len=14) [ Ext: 1 TON: Unknown Number Type (0) NPI: >Unknown Number Plan (0) '96048856808' ] > >Which has the textual ID in the 'Display' element... However I understand >from http://resource.intel.com/telecom/support/tnotes/tnbyos/2000/tn033.htm >that there is no definitive standard for transmitting the name. > >So, should even I be expecting Ast to put the name on the wire when it's >originating? > >Kris Boutilier >Information Systems Coordinator >Sunshine Coast Regional District > >_______________________________________________ >Asterisk-Users mailing list >Asterisk-Users@lists.digium.com >http://lists.digium.com/mailman/listinfo/asterisk-users >To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > >