Incomming Caller Name Display

[Simplysmith]

I have a IP 403 with a NI2 pri from At&T. I get incomming number display however I do not get any incomming name display The telco has said it is on, However I have not been able to prove what the problem is.

Anyone have any information that can help

 

[TivoNut]

Open a monitor session and watch a call come in, see if you see the name coming from the carrier. If you do, check with Avaya to see why they're not doing anything with it.

 

[bwilch]

You're probably not getting the name from the circuit provider. I have a circuit which I didn't realize name was on until it pop'd up on the display. I didn't have to set anything specific on the IP Office, it just showed caller name and number.

 

[Simplysmith]

What trace option should I be looking at? I have tried various options, however I don't see informaton that relates to the incomming CLID. I have pasted a sample of what im tracing.

Line: type=NoLine 0 Call: PhoneModel TelephonyHandler Invoke
PM TelephonyHandler KeyNum=32 Method=0 displayParam=100 type=123
110752mS CMExtnRx: v=2700, p1=11
CMTransfer
Line: type=NoLine 0 Call: lid=0 id=-1 in=0
110752mS CMExtnCutEvt: v=11 State, new=None old=CutThru,0,0,
110753mS CMMap: a=3.13 b=0.0 R0
110753mS CD: CALL: 0.12204.0 BState=Ringing Cut=0 Music=2.1 Aend="Reception(2700)" (3.13) Bend="Doug(2666)" [Doug] (0.0) CalledNum=2666 () CallingNum=7804966118 () Internal=1 Time=1432 AState=Ringing
110754mS PRN: CallLost cause=126
110754mS CMExtnTx: v=2700, p1=11
CMReleaseComp
Line: type=DigitalExtn 3 Call: lid=0 id=12203 in=0
UUI type=Local [....] [0x02 0x00 0x00 0x04 ]
Timed: 14/06/05 10:23
110756mS CMExtnRxC: v=25
CMInformation
Line: type=NoLine 0 Call: lid=0 id=12205 in=0
Keypad[%]
110757mS CMExtnTx: v=2666, p1=25
CMInformation
Line: type=DigitalExtn 3 Call: lid=0 id=12205 in=0
Keypad[%]
UUI type=Local [.] [0x01 ]
Timed: 14/06/05 10:23
110759mS CMMap: a=1.2 b=0.0 H0
110759mS PRN: T1 DSP: Slot A: Gains Chan 1 Tx 10 Rx 10
110759mS CMMap: a=1.2 b=0.0 R1
110759mS CMCallEvt: v=3 State, new=Ringing old=Connected,0,0,BState
110760mS CD: CALL: 1.3.1 BState=Ringing Cut=1 Music=2.1 Aend="Line 1" (1.2) Bend="Doug(2666)" [Doug] (0.0) CalledNum=2666 () CallingNum=7804966118 () Internal=0 Time=5680 AState=Connected
110760mS CMCallEvt: v=12204 State, new=Idle old=Ringing,0,0,BState
110761mS CMExtnTx: v=2700, p1=11
CMCallStatus
Line: type=DigitalExtn 3 Call: lid=1 id=3 in=1
State=126,
Timed: 14/06/05 10:23
110761mS PRN: CALL: 0.12204.0 Deleted leaving 4 CMCall objects
110761mS CMCallEvt: v=12204 State, new=Idle old=Ringing,0,0,Astate
110762mS CMCallEvt: v=12204 State, new=Idle old=Idle,0,0,BState
110762mS CALL:2005/06/1410:23,00:00:00,000,2700,O,2666,2666,Reception,,,1,,""
110762mS CMExtnCutEvt: v=11 State, new=None old=None,0,0,
110763mS CMExtnEvt: v=11 State, new=PortRecoverDelay old=Alerting,0,0,
110763mS CMExtnTx: v=2700, p1=11
CMReleaseComp
Line: type=DigitalExtn 3 Call: lid=0 id=12204 in=0
UUI type=Local [....] [0x03 0x00 0x00 0x0e ]
Cause=126, Transfer(IPO)
Timed: 14/06/05 10:23

 

[NuggiFirst]

Look for "calling number", i guess that should be a name instead of a number. In this region it's not possible to get text from the providers.. So it's just a guess ;-)

 

[Simplysmith]

I have been informed by the carrier that calling name is being delivered. I will look at the logs again. This one has been a uphill battle from the start. I just added another bit of the monitor results here as well in case anyone in here can help crack the case!

80705mS CMCallEvt: v=12186 State, new=Dialling old=LocalDial,0,0,Astate
480706mS CMCallEvt: v=12186 State, new=Dialled old=Dialling,0,0,Astate
480707mS KLP: Call::CallTargetingSequenceBegin(targetListSize=1)
480707mS KLP: Appearance::CallEndpointAdded(call=Call{id=6026},
480708mS KLP: endpoint=Line{lineId=1, timeslot=2, state=InUseConnected, isAvailable=true},
480708mS KLP: state=InUseConnected):
480708mS KLP: CallAppearance{
480708mS KLP: Appearance{button=1,
480708mS KLP: InternalEndpoint{phone=Rich,
480709mS KLP: Endpoint{id=0-12186-0, state=InUseDialing}}}}
480709mS KLP: AppearanceGroup::CallEndpointAdded(call=Call{id=6026},
480709mS KLP: endpoint=Line{lineId=1, timeslot=2, state=InUseConnected, isAvailable=true},
480709mS KLP: state=InUseConnected):
480710mS KLP: CallAppearanceGroup{state=InUseDialing,
480710mS KLP: callAppearance=CallAppearance{
480710mS KLP: Appearance{button=1,
480710mS KLP: InternalEndpoint{phone=Rich,
480710mS KLP: Endpoint{id=0-12186-0, state=InUseDialing}}}}}
480711mS KLP: Call::CallTargetingSequenceEnd()
480713mS ISDNL3Evt: v=1 stacknum=1 State, new=Initiated, old=NullState id=12187
480713mS ISDNL3Tx: v=1 peb=1
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0064(Remote)
Message Type = Setup
InformationElement = BearerCapability
0000 04 03 90 90 a2 .....
InformationElement = CHI
0000 18 03 a9 83 82 .....
InformationElement = CallingPartyNumber
0000 6c 0c 00 80 37 38 30 39 39 30 32 36 38 31 l...7809902681
InformationElement = CalledPartyNumber
0000 70 08 80 34 35 32 32 32 38 38 p..4522288
480713mS ISDNL2Tx: v=1 peb=1
0000 00 01 36 a4 08 02 00 64 05 04 03 90 90 a2 18 03 ..6....d........
0010 a9 83 82 6c 0c 00 80 37 38 30 39 39 30 32 36 38 ...l...780990268
0020 31 70 08 80 34 35 32 32 32 38 38 1p..4522288
480718mS ISDNL1Tx: v=1 peb=1
0000 00 01 36 a4 08 02 00 64 05 04 03 90 90 a2 18 03 ..6....d........
0010 a9 83 82 6c 0c 00 80 37 38 30 39 39 30 32 36 38 ...l...780990268
0020 31 70 08 80 34 35 32 32 32 38 38 1p..4522288
480725mS ISDNL1Rx: v=1 peb=1
0000 00 01 01 38 ...8
480725mS ISDNL2Rx: v=1 peb=1
0000 00 01 01 38 ...8
480965mS ISDNL1Rx: v=1 peb=1
0000 02 01 a4 38 08 02 80 64 02 18 03 a9 83 82 ...8...d......
480965mS ISDNL2Rx: v=1 peb=1
0000 02 01 a4 38 08 02 80 64 02 18 03 a9 83 82 ...8...d......
480965mS ISDNL3Rx: v=1 peb=1
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0064(Local)
Message Type = CallProceeding
InformationElement = CHI
0000 18 03 a9 83 82 .....
480966mS ISDNL3Evt: v=1 stacknum=1 State, new=Proceeding, old=Initiated id=12187
480966mS ISDNL2Tx: v=1 peb=1
0000 02 01 01 a6 ....
480967mS ISDNL1Tx: v=1 peb=1
0000 02 01 01 a6 ....
480969mS KLP: Appearance::CallEndpointAdded(call=Call{id=6026},
480969mS KLP: endpoint=Line{lineId=1, timeslot=2, state=InUseConnected, isAvailable=true},
480969mS KLP: state=InUseConnected):
480969mS KLP: CallAppearance{
480969mS KLP: Appearance{button=1,
480970mS KLP: InternalEndpoint{phone=Rich,
480970mS KLP: Endpoint{id=0-12186-0, state=InUseDialing}}}}
480970mS KLP: AppearanceGroup::CallEndpointAdded(call=Call{id=6026},
480971mS KLP: endpoint=Line{lineId=1, timeslot=2, state=InUseConnected, isAvailable=true},
480971mS KLP: state=InUseConnected):
480971mS KLP: CallAppearanceGroup{state=InUseDialing,
480971mS KLP: callAppearance=CallAppearance{
480971mS KLP: Appearance{button=1,
480972mS KLP: InternalEndpoint{phone=Rich,
480972mS KLP: Endpoint{id=0-12186-0, state=InUseDialing}}}}}
480972mS CMCallEvt: v=12186 State, new=Dialled old=Idle,0,0,BState
481808mS ISDNL1Rx: v=1 peb=1
0000 02 01 a6 38 08 02 80 64 01 1e 02 80 88 ...8...d.....
481808mS ISDNL2Rx: v=1 peb=1
0000 02 01 a6 38 08 02 80 64 01 1e 02 80 88 ...8...d.....
481809mS ISDNL3Rx: v=1 peb=1
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0064(Local)
Message Type = Alerting
InformationElement = PI
0000 1e 02 80 88 ....
481809mS ISDNL3Evt: v=1 stacknum=1 State, new=Delivered, old=Proceeding id=12187
481810mS ISDNL2Tx: v=1 peb=1
0000 02 01 01 a8 ....
481810mS ISDNL1Tx: v=1 peb=1
0000 02 01 01 a8 ....
481812mS CMCallEvt: v=12186 State, new=Ringing old=Dialled,0,0,BState
481812mS CMCallEvt: v=12186 State, new=Ringing old=Dialled,0,0,Astate
481813mS KLP: AppearanceGroup::CallEndpointChanged(call=Call{id=6026},
481813mS KLP: endpoint=CallAppearance{
481813mS KLP: Appearance{button=1,
481813mS KLP: InternalEndpoint{phone=Rich,
481814mS KLP: Endpoint{id=0-12186-0, state=InUseRingback}}}},
481814mS KLP: oldState=InUseDialing, newState=InUseRingback):
481814mS KLP: CallAppearanceGroup{state=InUseDialing,
481814mS KLP: callAppearance=CallAppearance{
481815mS KLP: Appearance{button=1,
481815mS KLP: InternalEndpoint{phone=Rich,
481815mS KLP: Endpoint{id=0-12186-0, state=InUseRingback}}}}}

 

[TivoNut]

I'm running 3.0 on my 412 here, it's direct-connected to my corp Definity PBX. It's connected with NI-2 PRIs. When my Definity sends name, it's clear the IPO is receiving it in the monitor session below, but it also appears it doesn't like it and doesn't know what to do with it. But comparing to your logs, I don't see a name anywhere. The name in mine below is "Computer Room". I would again verify that they are sending you name and do a test call from a line you know will deliver name. You should see it in the monitor session. Then once you are seeing it, if it's not going through to the phones or being ignored, talk to Avaya. We don't use name on our IPO so we don't have a need for it. But from my test, it's not clear the IPO supports receiving name over PRI.


63081mS CMLineRx: v=1
CMSetup
Line: type=Q931Line 1 Call: lid=1 id=2 in=1
Called[3800] Type=National (2) SndComp Calling[949XXXXXXX] Type=National (2)
BC: CMTC=3K1Audio CMTM=Circuit CMTR=64 CMST=Default CMU1=ULaw
BChan: slot=33 chan=1
IE CMIESupplementaryService (5)
Interpretation APDU
rejectAnyUnrecognisedInvokePdu
.Invoke
invokeId 2880
0000 80 0d 43 6f 6d 70 75 74 65 72 20 52 6f 6f 6d 6e ..Computer Roomn
0010 0d 43 6f 6d 70 75 74 65 72 20 52 6f 6f 6d 1e 02 .Computer Room..
0020 81 83 ..
IE CMIEProgressIndicator (30) cs=CMCSITUT (4634880), loc=CMLPrivateNetLocalUser (1), pd=CMPDOrigNotISDN (1562371)
63081mS CD: CALL: 1.2.1 BState=Idle Cut=1 Music=0.0 Aend="Line 1" (33.2) Bend="" [] (0.0) CalledNum=3800 () CallingNum=949XXXXXXX () Internal=0 Time=0 AState=Idle
63082mS PRN: AdjustCount 1,0 -> cur=1 out=0 v=1 d=0

 

[Morrack]

I've battled over this one plenty. Find out if your carrier is using a DMS or a 5ESS; I would bet that they are using a DMS. In the Nortel Universe the only kind of PBX equipment that exists is Nortel, they are a standard unto themselves and ignore industry standards for many things, including what ISDN layer3 info packet to send the name info in. Their answer to me on this issue is that if my (dippy) equipment isn't up to Nortel standards then it's up to the manufacturer (Avaya) to make it so.

Having said all that, I agree with TivoNut - looking at your monitor trace I would say that the carrier isn't sending caller id name at all. It should appear in your layer3 information packets....

Actually looking more closely at your trace I believe you have provided a trace of an OUTGOING call. Could you post a trace of an incoming call? The easiest way to do this is after hours when you can be sure you're capturing the call you mean to. And call in on your cell, don't place an outgoing call from the IPO to the IPO...



Peter Sherwood

Morrack Consulting

http://www.morrack.com

 

[mforrence]

Just to add to the mix, after reading this post I looked at the layer 3 ISDN trace of a recent IP Office install - using NI2 PRI. Inbound name works fine, but I don't see that name as text on the trace. I DO see the inbound number on the trace in easily readable text...

Peter - hadn't seen you post in some time - I had wondered if we had made you mad...

MIKE

 

[Simplysmith]

here is the latest trace screen, I have now been told that NI2 here in Canada (All-Stream Carrier formally AT&T) does not support calling name on a NI-2 configuration. I am having the PRI programmed for DMS-100 hopefully that will solve this issue.


78126442mS CMLineTx: v=1
CMSetup
Line: type=Q931Line 1 Call: lid=0 id=13678 in=0
Called[4642700] Type=Default (100) Calling[7809902672] Type=Default (100) Pres= (101)
BC: CMTC=3K1Audio CMTM=Circuit CMTR=64 CMST=Default CMU1=ULaw
BChan: slot=0 chan=4
Cause=16, Normal call clearing
Locale: enu
78126444mS ISDNL3Evt: v=1 stacknum=1 State, new=Initiated, old=NullState id=13678
78126444mS ISDNL3Tx: v=1 peb=1
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=006E(Remote)
Message Type = Setup
InformationElement = BearerCapability
0000 04 03 90 90 a2 .....
InformationElement = CHI
0000 18 03 a9 83 83 .....
InformationElement = CallingPartyNumber
0000 6c 0c 00 80 37 38 30 39 39 30 32 36 37 32 l...7809902672
InformationElement = CalledPartyNumber
0000 70 08 80 34 36 34 32 37 30 30 p..4642700
78126444mS ISDNL2Tx: v=1 peb=1
0000 00 01 fc 7e 08 02 00 6e 05 04 03 90 90 a2 18 03 ...~...n........
0010 a9 83 83 6c 0c 00 80 37 38 30 39 39 30 32 36 37 ...l...780990267
0020 32 70 08 80 34 36 34 32 37 30 30 2p..4642700
78126449mS ISDNL1Tx: v=1 peb=1
0000 00 01 fc 7e 08 02 00 6e 05 04 03 90 90 a2 18 03 ...~...n........
0010 a9 83 83 6c 0c 00 80 37 38 30 39 39 30 32 36 37 ...l...780990267
0020 32 70 08 80 34 36 34 32 37 30 30 2p..4642700
78126456mS ISDNL1Rx: v=1 peb=1
0000 00 01 01 fe ....
78126456mS ISDNL2Rx: v=1 peb=1
0000 00 01 01 fe ....
78126641mS CMExtnRx: v=2672, p1=17
CMShortCode
Line: type=NoLine 0 Call: lid=0 id=-1 in=0
ShortCode GetCallInfo (108) = []
78126641mS CMExtnTx: v=2672, p1=17
CMShortCode
Line: type=DigitalExtn 4 Call: lid=0 id=-1 in=0
ShortCode GetCallInfo (108) = []
BChan: slot=4 chan=19
UUI type=User2User [C......5m.] [0x43 0x00 0x00 0x00 0x00 0x00 0x00 0x35 0x6d 0x00 ]
Timed: 15/06/05 09:58
78126709mS ISDNL1Rx: v=1 peb=1
0000 02 01 7e fe 08 02 80 6e 02 18 03 a9 83 83 ..~....n......
78126709mS ISDNL2Rx: v=1 peb=1
0000 02 01 7e fe 08 02 80 6e 02 18 03 a9 83 83 ..~....n......
78126709mS ISDNL3Rx: v=1 peb=1
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=006E(Local)
Message Type = CallProceeding
InformationElement = CHI
0000 18 03 a9 83 83 .....
78126710mS ISDNL3Evt: v=1 stacknum=1 State, new=Proceeding, old=Initiated id=13678
78126710mS ISDNL2Tx: v=1 peb=1
0000 02 01 01 80 ....
78126711mS CM: CMProceeding
Line: type=Q931Line 1 Call: lid=0 id=13678 in=0
BChan: slot=0 chan=3
78126711mS ISDNL1Tx: v=1 peb=1
0000 02 01 01 80 ....
78126713mS CMLineRx: v=1
CMProceeding
Line: type=Q931Line 1 Call: lid=0 id=13678 in=0
BChan: slot=1 chan=3
78126713mS CMCallPkt: v=13677
CMProceeding
Line: type=Q931Line 1 Call: lid=0 id=13678 in=0
BChan: slot=1 chan=4
78126714mS CMMap: a=4.19 b=1.4 M1
78126714mS CD: CALL: 0.13677.0 BState=Idle Cut=3 Music=0.0 Aend="Roual(2672)" (4.19) Bend="Line 1" [Line 1] (1.4) CalledNum=4642700 () CallingNum=2672 () Internal=0 Time=6845 AState=Dialled
78126714mS CMCallEvt: v=13677 State, new=Dialled old=Idle,0,0,BState
78126715mS CD: CALL: 0.13677.0 BState=Dialled Cut=3 Music=0.0 Aend="Roual(2672)" (4.19) Bend="Line 1" [Line 1] (1.4) CalledNum=4642700 () CallingNum=2672 () Internal=0 Time=6845 AState=Dialled
78126715mS CMExtnRxC: v=17
CMProceeding
Line: type=Q931Line 1 Call: lid=0 id=13677 in=0
Called[4642700] Type=Default (100)
BChan: slot=4 chan=19
Display [4642700]
78126715mS CMExtnEvt: v=17 State, new=Proceeding old=Dialling,0,0,
78126716mS CMExtnCutEvt: v=17 State, new=CutThru old=CutThru,0,0,
78126716mS CMExtnTx: v=2672, p1=17
CMProceeding
Line: type=DigitalExtn 4 Call: lid=0 id=13677 in=0
Called[4642700] Type=Default (100)
BChan: slot=4 chan=19

 

[Morrack]

Mike, no I haven't been driven mad quite yet, but getting there Just been SUPER busy lately with launching the consulting business, etc.

SimplySmith, you are in Canada too eh? Don't you believe that hogwash about inbound name not working on NI2 in the Great White North, it's simply not true. What IS true is that NORTEL cannot manage to follow industry standards (believing themselves to be a standard unto themselves), and send the name in a proprietary manner that only nortel PBX's can relate to.

If you switch to a 5ESS running NI2 your IPO will receive names just fine. I have a client in downtown toronto with just such a config and they are working fine.



Peter Sherwood

Morrack Consulting

http://www.morrack.com

 

[Simplysmith]

Thanks, Morrack. I know that is true and the case here, however getting a telco to admit it is another issue

I have since had the PRI programming changed to NI1 and have programmed it to operate as DMS100 on the 406 Unit.

 

[Morrack]

And that worked??

... and what are you talking about? Teleco's in Canada are open, honest, and the first ones to admit when the problem is at their end... NOT!!!! LOL

step 1: you're sending the info in the wrong packet according to industry standards
step 2: We're sending it according to Nortel standards
step 3 repeat step 1



Peter Sherwood

Morrack Consulting

http://www.morrack.com