[cisco-voip] RDNIS and Original Called Number IE

Jason Aarons (AM) jason.aarons at dimensiondata.com
Thu Jun 21 13:48:42 EDT 2012


You can use TCL to preserve the RDNIS across a PRI that doesn't support Redirecting IE.  Search this page for RDNIS.  You need a cisco.com login. This is a difficult task but can be done. Both far and near end gateways need it, usually I dedicate a inbound DID just for SRST with this on the Unity side that matches the SRST side's call-manager-fallback voicemail number.

http://developer.cisco.com/web/vgapi/resources


From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ted Nugent
Sent: Thursday, June 21, 2012 1:27 PM
To: Eric Pedersen
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] RDNIS and Original Called Number IE


In my experience with this all providers from the remote site to the Unity pilot  location ALL need to support RDNIS, which is not always feasible.
It's been a while but I would look into sending the digits inband

 dial-peer voice 10 pots
 destination-pattern 19195551212
 port 0/0/0:23
 forward-digits extra inband
On Thu, Jun 21, 2012 at 12:06 PM, Eric Pedersen <PedersenE at bennettjones.com<mailto:PedersenE at bennettjones.com>> wrote:
We're running CUCM 8.6(2).21900-5.

When one of our remote sites goes into SRST, I would like to be able to have voicemail survivability by forwarding no-answer/busy to the Unity pilot number at our central site.  We're using DMS-100 PRIs at both locations and I can see in the ISDN debugs that the redirect number is getting correctly passed by the telco in the ISDN Setup Original Called Number IE.  CUCM however is not passing on the Original Called Number IE contents to Unity Connection.  I have "Redirecting Number IE Delivery - Inbound" checked on the GW config, but that's not the IE that's being used in the Setup; I assume that's because it's a DMS-100 PRI.

The remote GW is SIP so as an experiment I tried forwarding a call there. This GW correctly takes the contents of the Original Called Number IE and puts it in the Diversion Header which CUCM uses as the RDNIS so it looks like I have a problem with my central MGCP GW.

Am I missing something in my configuration, or does CUCM not support the Original Called Number IE?

Thanks,
Eric

The contents of this message may contain confidential and/or privileged

subject matter. If this message has been received in error, please contact

the sender and delete all copies. Like other forms of communication,

e-mail communications may be vulnerable to interception by unauthorized

parties. If you do not wish us to communicate with you by e-mail, please

notify us at your earliest convenience. In the absence of such

notification, your consent is assumed. Should you choose to allow us to

communicate by e-mail, we will not take any additional security measures

(such as encryption) unless specifically requested.



_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip



itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120621/7682c5c0/attachment.html>


More information about the cisco-voip mailing list