[Q] Enabling Outbound Caller-ID Only TO Specific External Numbers
Currently, our telephony provider blocks the sending of Caller-ID (CLID) information on outbound calls. We now have a requirement to be able to make calls to certain numbers without blocking our CLID. We are running Cisco Unified Communications Manager 7.1 (CUCM 7.x) with a Cisco 2811 gateway via H.323 and a Primary Rate ISDN (PRI).
After requesting the telephony provider to remove CLID blocking, my initial thought was to set up 2 destination patterns on the 2811 gateway; a default pattern which prefixes all numbers with 141 to withold caller id and another pattern that matches against specific dialled numbers that would not prefix 141 (I think this is the equivalent to *67 in the US). However, this would require us to have a known list of destination numbers and to make a change as and when new numbers are added.
I then thought it may a better idea may be to implement the equivalent of an access code so that any number dialled normally would have a prefix of 141 added but anyone that dialled a code (say 1234, for example) before the full number would have the access code stripped and no 141 prefixed to the called number thus enabling CLID to be displayed at the receiver's end.
I would appreciate any feedback on whether this is the best option and, if so, how I would write the translation patters and/or rules.
whatever you do you are going to need some logic that decides when to present the number and when not to.
1. Logic in a list (patterns etc..)
2. Logic with calling party (I prefer this)
you shouldn't have to use the 141 prefix, pick one users can remember to differentiate between sending cli and not, just set the calling party line id presentation to restricted and check to see if your line supplier honours it.
Pump both sets of calls through a translation pattern, one includes the prefix the other just catches everything.
in the translation pattern set calling party line id presentation to restricted or not depended on the translation patter (prefix or no prefix).
There may be a better way buts thats what I would do.
Cisco Meeting Server 3.2 supports the Blast Dial feature. With Blast Dial, you can add a predetermined list of participants to a space where you configure blast dial. When any participant dials in to the space, all the other participants are dialed out si...
Shortcut ActionCtrl+W Close Meeting CenterCtrl+T Transfer filesCtrl+Z Undo last actionCtrl+Y Redo last undone actionCtrl+Alt+F Display Font Formatting dialog boxCtrl+Alt+O Share presentation or documentCtrl+Alt+A Share applicationCtrl+Alt+D Share DesktopC...
Do you experience the following error on Cisco Unity Connection: Sometimes when you try to play or upload Audio Files for greetings in Unity Connection under the Call Handlers such as the System Call Handler Opening Greeting, in Standard/Closed/Holi...
When an Ad hoc conference is triggered by an endpoint to escalate a point-to-point call into a three-way call.HQ-CUCM sends an API request via HTTPS to the Cisco Meeting Server to set up a conference. You can see from the event log of CMS that API us...