Incoming Caller ID Name not coming through but # does 3

[FunWithNortel]

Need some guidance

Scenario

Incoming calls display number on the ip sets but no name.

Pretty sure I need to configure the CUCM to allow name to display

not sure where this configuration is done.

Think it might be under
Translation pattern
calling name presentation

options are allow; restrict; or default.

Then again then might not be the right spot at all.

Thanks!

 

[spunkysus]

Don't know for sure ,but seem like this would be more of a Gateway issue.May want to take a look at the gateways and ensure you have the Call Routing Information-Inbound settings correct.I have mine set to allow "all" significant digits

 

[whykap]

Also make sure that you are receiving calling name along with the number from the provider.
Is the protocol on the PRI mgcp or h323?

 

[FunWithNortel]

Gateway
interface: PRI NI
inbound is set to: all via destination pattern .T
Gateway voice class is set to: h323

CUCM
Gateway
Significant digits: all

**Did notice that Transmit UTF-8 for Calling Party Name is unchecked

If you could help me figure this out that would be great. Thanks!!!

 

[MitelInMyBlood]

Does the user see callerID Name presentation once they answer the call?

If so, is the Nortel still acting as your PRI gateway, using Q.Sig possibly? That's what this problem sounds like. If that's your setup, it should fix itself once your PRIs are moved over to the Cisco gateway.

Q.Sig intermachine trunking between Cisco and competing PBXs is not a full subset of the signalling protocol. We've run into the exact same problem migrating a Mitel SX2000 over to Cisco. According to Cisco TAC it's a known problem with no fix.

We've swung a couple PRIs over and indeed, everything that now inbounds through the PRIs directly to the Cisco now work correctly.



Original MUG/NAMU Charter Member

 

[FunWithNortel]

Not running through Nortel but will be doing another site where this will come up.

PRI's originating from the PSTN.

Going to try some config changes on the gateway nest week that I hope will resolve the issue.

This is where we are at currently...

Caller ID name is sent by your telco (if you pay for the service) and this capability does not exist within CallManager.

If the carrier/telco is sending the caller ID name, it will be displayed on the IP phones.

However, if you are using H323 gateway, and your carrier is sending you the name on the Facility IE Message, inbound caller name does not get displayed on the IP phone.


H323 does not support Facility IE; only MGCP supports it.
These are the possible solutions for MGCP Gateway:

1. In order to allow the gateway to detect the calling name on the Facility IE please enter the following on the serial interface generated by the pri-group statementwhich is the D channel)

interface serialx/x/x:23
isdn supp-service name calling


2. Request the Telco to send the Calling Name Identification Delivery (CNID) as Display Information Element in the ISDN setup message

3. Configure the gateway as MGCP and register it to the CUCM.




Possible Solution for H323 Gateways
H.323 Name Display

Calling name display information may be populated in ISDN messages in the Display Information Element (IE) of a Q.931 Setup or Notify message, or in the Facility IE of a Q.931 Setup or Facility message.

The Cisco IOS gateway places this information into the same field of the corresponding H.323 message.

Cisco Unified Communications Manager (CUCM) interprets calling name information (for purposes of name display on IP phones registered with CUCM) only in the Display IE of the H.323 Setup and Notify messages.

Name display information delivered in an H.323 Facility message is not interpreted by CUCM.

Some ISDN switch types (for example, NI2) send a "name-to-follow" indication in the Q.931 Setup message and deliver the calling name subsequently in the Facility IE of a Q.931 Facility message.

When a Cisco IOS gateway is connected to such an ISDN switch, and interoperating with CUCM using the H.323 protocol, CUCM is unable to display calling name on the IP phones.

Beginning with Cisco IOS Release 12.4(11)XW, two new modes of operation are introduced on the Cisco IOS gateways:

When a Q.931 Setup message with a "name-to-follow" indication is received from an ISDN switch, an H.323 Setup message with no name information is sent to CUCM.

When the subsequent Q.931 Facility message is received with calling name information, it is mapped by the gateway to an H.323 Notify Display IE so that CUCM can interpret it correctly and display it on the IP Phone

When a Q.931 Setup message with a "name-to-follow" indication is received from an ISDN switch, the gateway can buffer the setup message until the subsequent Q.931 Facility message with calling name information is received.

The name information from the Q.931 Facility message is now placed into the H.323 Setup message Display IE and sent to CUCM. If the buffer timer expires before the Q.931 Facility message is received, an H.323 Setup is sent with no name information and, if it subsequently arrives, the information is sent on using an H.323 Notify message.

This software operation is transparent to CUCM and works with all releases, although CUCM 4.2 or later is recommended.

To enable the H.323 Display feature without buffering for ISDN trunks that use the Facility message to deliver Name Display information, configure thefollowing:


At the voice service level:
voice service voip
h323
h225 display-ie ccm-compatible

At the voice class level:
voice class h323 1
h225 display-ie ccm-compatible [system]


To enable the H.323 Display feature with buffering for ISDN trunks that use the Facility message to deliver Name Display information, additionally configure the following:


At the voice service level:
voice service voip
h323
h225 timeout ntf <50-5000>
isdn supp-service name calling

At the voice class level:
voice class h323 1
h225 timeout ntf <50-5000>
isdn supp-service name calling

Information was found on another Cisco forum. WIll try soon and let everyone know the results.

 

[FunWithNortel]

Was able to get it working...

Had provider switch calling name from setup to facility

Then changed the gateway for the following

In order to allow the gateway to detect the calling name on the Facility IE please enter the following on the serial interface generated by the pri-group statementwhich is the D channel) For MGCP and H.323 both input the following below.

interface serialx/x/x:23
isdn supp-service name calling


For H.323 Gateway
To enable the H.323 Display feature with buffering for ISDN trunks “Name to Follow” that use the Facility message to deliver Name Display information, additionally configure the following:

At the voice service level:
voice service voip
h323
h225 timeout ntf <50-5000> (we used 500 successfully)
h225 h225 display-ie ccm-compatible

Hope this helps others. Need latest IOS for these new commands.

What you are doing basically is taking the name display furnished by the CO in the facility information element and mappiong it via the cisco gateway to the display information element that the cisco cucm can use to display name on the ipt :0)