Short Dials and E164 Design Question

[EYC]

All,

I have a design questions and wish to have as little CSS/PT/RPs as possible. We have configured E164 as DNs on the phones but would like to use 4 digit dials for calls within a site. Say both sites are using 1xxx as extensions, and would like to use Local Route Groups for PSTN calls. For Simplicity Sake, assume we only have 2 sites in Singapore. I would like to use a single SG PT/CSS/RP but due to the different E164 Prefixes, I have to configure 2 sets of PT/CSS. With all the discussion about E164, Global Dial Plan, Local Route Group and reduction of (n)(n+1) to just (n+1) CSS/PT/RPs, I am wondering if there is a clean way of doing this without creating a lot of repetitive configurations.

Site A DNs +65 6123 XXXX

Site B DNs +65 6234 XXXX

RP for outgoing to PSTN +65 [3689]XXX XXXX

I would configure  a Route Pattern for 9.[3689]XXXXXXX to LRG to the PSTN.

Due to the short dials within a site, We would need TP for each site to Translate 1XXX in each Site Partition to the Full E164. So in the end, I have SG_DN_PT, SiteA_Internal_PT, SiteB_Internal_PT, SiteA_PSTN_CSS, SiteB_PSTN_CSS, SiteA_Internal_CSS, SiteB_Internal_CSS and SG_PSTN_PT for the actual PSTN RP.

TP1 1XXX in SiteA_Internal_PT -> +656123 XXXX with SG_Internal_CSS

TP2 1XXX in SiteB_Internal_PT -> +656234 XXXX with SG_Internal_CSS

SG_Internal_CSS to include SG_DN_PT

Then each Phone in Site A will have SiteA_PSTN_CSS which Includes SiteA_Internal_PT, SG_DN_PT, SG_PSTN_PT and Phone in Site B will have SiteB_PSTN_CSS which Includes SiteB_Internal_PT, SG_DN_PT, SG_PSTN_PT. The more sites you have these PTs,CSS, RPs will increase exponentially. What is the cleanest way to configure this?

Thanks.

[Chris Deren]

In order to configure abbreviated dialing without a site or set of phones you need dedicated CSS for those phones/DNs as they need to have access to the abbreviating translation pattern only for their "pool". As to DP it is best practice to always have local DP. PSTN Route patterns, TPs and SLRG depending on your PSTN routing can be shared between sites fine, though my approach is always to have "country" specific global patterns plus local patterns (if needed) in site country specific/site specific partitions which again leads to needing dedicated CSSes, but all of the RPs can easily point to the same Route list using SLRG.

[Dennis Mink]

Sorry for potentially oversimplifying this,

but why dont you use the Enterprise alternate number (line configuration page) for this purpose?

and comletely separate them using the dedicated partition that you can assign to the alternate number, allowing overlap. If there is no overlap, put all alternate extensions in a single partition, so there is no need for Translation Patterns 

Please rate if this helps

[Chris Deren]

Dennis, you are correct this will definitely allow for the short dialing and I have used this method as well. This does not however change the strategy of CSSes, Device Pools, etc. plus you also need to ensure the voicemail users in Unity Connection have alternate extensions defined as the abbreviated extensions (normally desired).  +5 for good suggestion.