Cisco callmanager ver 8x

[Kyle Albasha]

hello

we are running one cluster callmanager ver 8.65 among ver sites utilizing a ten digites dialing configuration on the IP phones. however the q how do you setup a 4 digites dilaing among all site within the same cluster?

utilizing a SIP configuration

[David Hailey]

Essentially you want to implement an abbreviated dialing solution within the cluster.  In order to do this effectively, you first need to consider whether or not there is overlap in the 4-digit extension ranges among the various DID and/or private number ranges assigned to the phones across sites.  There are also overlap considerations for offnet and/or or inter-office dialing patterns (such as if you use 9 as an offnet code but also have extensions in the 9XXX range, etc.).  In any case, you can use translation pattern to expand the 4-digit abbreviated dialing to the 10-digit numbers assigned to the phones.  Configuration will vary depending on the existing dial plan structure, overlap considerations, requirements, etc.

Hailey

[Kyle Albasha]

thx David

however currently we don't use a 9 or a 1 to make a call , also we use Intra-site, on-net abbreviated dialing within the sames site. all of our endpoint is configure as a 10 digits numbers

[David Hailey]

So you have a multi-tenant dial plan and do 4-digit abbreviated dialing at the tenant (site) level...do you have overlap between the extension ranges at each site?  If you do, then you won't be able to effectively implement 4-digit dialing at the cluster wide level.

Hailey

[Kyle Albasha]

Based on our sites DID ranges we currently don't have an overlap extension .  is it possible to set a location code perhaps + 4 digits dilaing ? if so

[David Hailey · Accepted solution]

You could do either - the premise would be the same.  You would use translation pattern(s) that expands 4-digit to 10-digit and those patterns would need to be visible by all of the tenant CSS within the cluster.  If you have ranges all over the place when it comes to 4-digit ranges and their expansion to 10-digit, then it might be cumbersome and the site code may be the best option there.  Either way the concept is the same.

For example:

Let's say you have a DID range for a DC site that is 202-555-1XXX then you would add a translation pattern of 1XXX and then prefix 202555 within the translation.  If every tenant has access to that pattern then you can now dial 1XXX within the cluster to reach the DC site.

Or - let's say you wanted to assign a site code of 100 to the DC site.  Then you would add a translation of 100.XXXX, strip pre-dot, and prefix 202555.  Again, if every tenant has access to that pattern then you can now dial 100XXXX and reach the DC site.

In every scenario, the main thing you need to consider is if (or where) you may introduce and/or run into overlap.

Hailey