Well, it all depends on what you really want to do, where are you hoping off, is it another CCM cluster, a GW, CME?
Typically you will send all digits to the GK with or without the off-net access code (remember to prefix tech-prefix on the route list or RP, unless you are going to use default tech-prefix) and then simply use zone prefix to direct the call to desired location. For example assume you have CM and CME and you would like to hop-off from CM out of CME GW, so when user CM 1 dials 9.011485551234 it needs to go via GK out CME GW, you would have following config:
zone local HQ cisco.com 10.1.1.1
zone local CME cisco.com
zone prefix CME 9011*
On the CME GW, you might want to manipulate the incoming digits to strip the 01148, so the call goes out as a local call, to do that one way is to use translation rule as following:
voice translation-rule 1
rule 1 /^1#901148/ //
voice translation-profile 1
translate called 1
dial-peer voice 1 voip
incoming called-number 1#9011T
translation-profile incoming 1
The 1# is the tech-prefix which was prefixed on the CCM, and which CME registers with.
I am looking at sending the call, which would be international, from the main site, through gatekeeper, out through the CME as a local call, but the local call is NOT any of the registered E164 numbers?
Is this possble along the same guideline configs you referenced, and, if not, what needs to change. Also, would the RP still be something like: 9.011485551234
Thanks for the detail on the RP, translation rule and such. So, reading this translation rule, it would take this dial string from GK:
and change it to:
and hand it to an outgoing POTS dial peer for 7-digit dialing WITH the 9 access, as you described, such as this DP:
dial-peer voicp 10 pots
Is this accurate?
Also, is this regardless of whether the CME is E164 reg or reg with a tech-prefix?
One more thing.......(keep in mind I'm still trying to understand details of GK configs such as this, with the CME)...Is it possible for a CME and the CCM trunk to "share" the same tech-prefix or being registered with the same? From what I have researched and read, EACH device must register with a tech-prefix if "default-technology" is NOT used. Is this also the case for the CME, or is it just need to register with its E164 numbers?
This is one example, however you can share the tech-prefix and still not have to use the gw-priority. The gw-priority is only needed when you send the same calls to different GWs, in this example 2 CCM servers (SUB and PUB for example).
Consider the following config:
zone local CM abcd.com 10.1.1.1
zone local CME
zone prefix CM 7...
zone prefix CME 8...
Both CCM and CME can register with the same tech-prefix and yet based on the zone prefix you can send the calls to them appropriately.
Basically, there are the following ways GK can route calls:
1. Use default-tech-prefix
2. Use tech prefix
3. Use static alias, in CME case you can allow all ephone-dn to register with their e164 addresses, CCM cannot do that.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.