[cisco-voip] Send Calling Name over MGCP PRI (NI2)

[Norton, Mike]

Bill, that is true in the U.S., but most of the world is not in the U.S. :)

In Canada, the norm is for the telcos to take the calling name you provide them and pass it on.

--
Mike Norton
I.T. Support
Peace Wapiti School Division No. 76
Helpdesk: 780-831-3080
Direct: 780-831-3076


From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Bill
Sent: May-04-10 7:11 AM
To: 'Bill'; george.hendrix at l-3com.com; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Send Calling Name over MGCP PRI (NI2)

Well you can send it they just don't care about it. :)


________________________________
From: Bill [mailto:bill at hitechconnection.net]
Sent: Tuesday, May 04, 2010 8:11 AM
To: 'george.hendrix at l-3com.com'; 'cisco-voip at puck.nether.net'
Subject: RE: [cisco-voip] Send Calling Name over MGCP PRI (NI2)

You can't send Calling name to the Telco Only number.

________________________________
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of george.hendrix at l-3com.com
Sent: Tuesday, May 04, 2010 8:02 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Send Calling Name over MGCP PRI (NI2)

Hello everyone,

  We have a CUCM 7.1 cluster connected to 3 PRI trunks using NI2 and they are configured as MGCP trunks in CUCM.  We have a requirement for "calling name" to be sent from the internal Cisco CUCM to the Telco.  From what I have read, we simply need to do the following:

On the MGCP gateway:
Interface Serial0/0/0:23
isdn supp-service name calling
isdn outgoing ie facility

I have already checked the "Send Calling Name In Facility IE" checkbox on the MGCP endpoint configurations.

Is there something else I am missing to make this work?  The Telco has said that we simply need to configure our system to send the calling name info.  The PRI trunks to them are NI2.

Thanks,

Bill Hendrix
george.hendrix at l-3com.com<mailto:george.hendrix at l-3com.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100504/ce4a3b23/attachment.html>