[cisco-voip] Caller ID restrictions and Unity Connection

Kenneth Hayes kennethwhayes at gmail.com
Tue Nov 6 12:35:19 EST 2012


I know on the hunt pilot you can play around with Caller ID stuff but I
don't know if that's helpful or not.

Sent from my iPhone
Thanks,
Kenneth W. Hayes


On Nov 6, 2012, at 12:26 PM, Eric Pedersen <PedersenE at bennettjones.com>
wrote:

  They are calls from the PSTN into CUCM and route to the Unity hunt list
so there is no route list involved.



*From:* Kenneth Hayes [mailto:kennethwhayes at gmail.com<kennethwhayes at gmail.com>]

*Sent:* 06 November 2012 10:17 AM
*To:* Eric Pedersen
*Cc:* cisco-voip at puck.nether.net
*Subject:* Re: [cisco-voip] Caller ID restrictions and Unity Connection



Do have the restriction set on the route list?

Sent from my iPhone

Thanks,

Kenneth W. Hayes




On Nov 6, 2012, at 12:13 PM, Eric Pedersen <PedersenE at bennettjones.com>
wrote:

 Is there a way to get calls to Unity Connection to obey calling line ID
presentation restrictions? We're setting a dummy calling number of
999-999-9999 on our gateways (SIP) for calls coming in on our PRIs with no
calling number. I did this because we need to filter calls in CUCM based on
calling number, and the SIP gateways by default seem to set the caller to
"anonymous" when there is no calling number. Without the gateway
translation to set this dummy number, these calls were not making it
through the calling number translation patterns.



On the matching calling number translation pattern I set the calling line
ID presentation to Restricted and it correctly shows Private on phones but
the voicemail shows the dummy calling number. The CUCM logs show that it is
sending the calling number to CUCX.



The dummy number translations on the gateway are a bit convoluted to me so
if there is a better way to do this, please let me know.



This is CUCM and CUCX 8.6 with a SCCP integration.



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
https://puck.nether.net/mailman/listinfo/cisco-voip

 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20121106/8b7a2499/attachment.html>


More information about the cisco-voip mailing list