Call Party Name Display 3

[srmega41]

Being new to the Avaya world, I feel some of my questions I should know, but I will ask (I spent 11 years working on Nortel).

I just ordered Call Party Name Delivery on my PRI's terminating to a CM2.1 system. Everything I have found does NOT indicate I need to do anything, and my vendor has said the same thing. My issue is I am not getting the Name delivery, and my service provider (Qwest), assures me the order was complete. On the Nortel side, I had to set up a number of messaging options to get this to work, but I am unclear if there is anything I need to do now in the Avaya world.

In the documentation I have (Feature Description and Implementation for Avaya Communication Manager), it states the name will be presented if provided from the utside world, so I am not sure what I am missing.

Thanks in advance for any help.

Scott M.

 

[TivoNut]

On page 2 of your PRI trunk group screen set this field to "Y".

US NI Delayed Calling Name Update? y

 

[srmega41]

This is now set to yes, but it did not change anything. I still get:
a= Call From
720-555-xxxx
on the display.

I am using a 6408D+ just to provide a little more info. Thanks for the response, any other ideas??

Scott M.

 

[asripuram]

Hi,

In my experience, I have never seen a name appear from an outside caller.

Your trunk provider will only allow a number to come through.

The calling party name field on Page 2 is for Avaya switches which are connected to each other not for outside callers.

Ash

 

[srmega41]

asripuram,

Qwest does offer the feature, and at my previous job I had set up my connection to the CO (into a Nortel Option 81) with a total of 8 PRI's, all with CPND. In the feature document on Digital CO trunks, I found this statement:

Caller ID on digital trunks
In the US, a CO can send the calling party name and the calling party number over digital trunks
for display on digital telephones. The display of the calling party name and the calling party
number works with all Communication Manager Digital Communications Protocol (DCP) and
Basic Rate Interface (BRI) digital telephones that have either a 40-character or a 32-character
alphanumeric display.

Still at a loss, and I appreciate all the help. Any idea if there are non-DCP digital sets?

Scott M.

 

[jgideon]

Are the PRI's NI-2 protocol? NI-2 is the only standard that supports name.

 

[srmega41]

That is what Qwest "says" they are. Oh what fun!!

Thanks for the sanity check. Is there any way I can look at the actual D-Channel messages in the PBX? On the Nortel, I could enable messages on a D-Channel, and see every call setup, teardown, redirect message and the like. Can I do that on the Avaya? I have not seen anything, but my research of documentation may not be complete.

Thanks,

Scott M.

 

[maverick2689]

I agree with jgideon, I just installed 72 NI-2 PRI trunks in my Definity g3v9.5, so I have to believe you're all set.

Double check things with your provider on that NI provisioning info.

We must all hang together, or assuredly we shall all hang separately.

 

[TivoNut]

Try a couple of things:

1)
Verify you are running NI2 protocol. Look on your DS1 screen for "Protocol Version: b" b=NI, a=AT&T

Use "display ds1 01a16", replace 01a16 with the correct card number in your switch.

2)
"list trace tac XXX" where xxx is the TAC code from your trunk group screen (upper right corner) This will trace activity on the trunk group. You'll see something like:

08:52:58 Calling party trunk-group 3 member 1 cid 0x11e
08:52:58 Calling Number & Name 562477xxxx NO-CPName
08:52:58 active trunk-group 3 member 1 cid 0x11e
08:52:58 dial 3047
08:52:58 ring station 3047 cid 0x11e
08:53:04 active station 3047 cid 0x11e

I replaced full number with x's for this post, but note there was no name on the incoming call in this example "NO-CPName" Interestingly on my switch (CM2.2) it does not show the incoming name in the trace (shows NO-CPName) but I am receiving the name from telco and it is displaying on my 6400 series sets. Perhaps it's a bug, but something to try on your switch.

I never had to do anything special to make this work, except set the "US NI Delayed Calling Name Update? y" as I mentioned before. It should just work if you're on NI.

Note: You will not receive name on every call on which you do receive a number. If the CO receives the number but doesn't have a name to match it to, it will just send the number. This is most common when, say, and SBC number calls into Qwest territory, and vice-versa.

If it's still not working, open a service ticket with Qwest and make sure they're sending it. I've had it for more than two years here in SBC territory (Southern Cal) but others I know have had trouble getting it implemented. Not many people at telco seem to know it exists or how it works (via PRI.)

 

[jgideon]

one other point worth mentioning is that name won't be available for all calls. They should certainly be available for incoming 'local' calls from same provider. There is still feuding between different LEC's over the pricing of the database lookup for name (verizon vs sbc in KC comes to mind), and recently here in Verizon residential land, names from some CLEC accounts that used to show up have stopped.....

 

[wilsontec]

I am not sure but I remember that need enable special feature for transfer name to nortel.

 

[srmega41]

Something I was just told yesterday seems to be contrary to everything I have heard here, so I wanted to ask:

My vendor told me that PRI will ONLY work on a Definity G3 if the prototcal at the CO is set to Custom. Now everyone here has said NI2, and I have verified with my LEC we are at NI2, but the vendor says no, it is Custom. He even went so far as to say he called an old friend in the Translations group at Qwest to check, and even though the records show NI2, it is really set for Custom.

Any of this make sense? I am not very happy with my vendor, and I am continually finding issues with just about everything they say and do. I am interested in hearing your thoughts, since you guys are the experts on this platform, certainly not me.

Thanks for all your input and suggestions.

BTW, I saw the same type of data on my PRI with incoming calls; also showing NO-CPName.

Scott M.

 

[TivoNut]

You need to check your DS1 form (not trunk group) for the protocol version on your switch. The Definity supports both Custom (AT&T) and NI2. I run both on my switch now with different carriers.

On your DS1 that connects to Qwest, check the protocol version a=Custom (AT&T) b=NI2. Here's what my DS1 form looks like:

DS1 CIRCUIT PACK

Location: 01A16 Name: test
Bit Rate: 1.544 Line Coding: b8zs
Line Compensation: 1 Framing Mode: esf
Signaling Mode: isdn-pri
Connect: network
TN-C7 Long Timers? n Country Protocol: 1
Interworking Message: PROGress Protocol Version: b
CRC? n
Idle Code: 11111111
DCP/Analog Bearer Capability: speech

T303 Timer(sec): 4


Slip Detection? y Near-end CSU Type: integrated

Block Progress Indicator? n

 

[srmega41]

Thanks for this. I looked at mine, and it is using Custom

DS1 CIRCUIT PACK

            Location: 01D10                           Name: 102A1ZF
            Bit Rate: 1.544                    Line Coding: b8zs
   Line Compensation: 1                       Framing Mode: esf
      Signaling Mode: isdn-pri
             Connect: network
   TN-C7 Long Timers? n                   Country Protocol: 1
Interworking Message: PROGress            Protocol Version: a
                                                       CRC? n
           Idle Code: 11111111
                              DCP/Analog Bearer Capability: 3.1kHz

                                           T303 Timer(sec): 4


      Slip Detection? n                 Near-end CSU Type: other

Am I better off trying to change the protocol to NI-2, or see if the provider can send CPND using custom?

Thanks again,

Scott M.

 

[TivoNut]

You'll need to change to NI-2, but you'll need to coordinate with telco. Both ends need to be running the same. You also need to beat them upside the head and ask why they keep telling you you're running NI-2 when you're clearly not.

To change the protocol you have to busy out the trunk group and the board and the D channel, then you can change the DS1 protocol, then re-enable everything. And you need to do this with telco on the line so everything comes up.

Good luck with telco, I don't envy you!

 

[srmega41]

Not was I was hoping to hear, but I get it. I have been down this road before on the Nortel side, so I hope we can get this to work. I appreciate all the help, as well as the quick feedback and suggestions.

I am looking forward to more great support and interaction in this forum.

Scott M.

 

[maverick2689]

Just as a side note; if I have no problems with my CID name & number where my PRI's come in, and I want to pass that to my remote switches (also connected to the main node via PRI) do I have to be set to "b" to pass name in addition to number? Or does that matter on point-to-point?

We must all hang together, or assuredly we shall all hang separately.