[cisco-voip] Site Code -- Dial Plan

[Tim Smith]

Hi Akaal,

If your doing it over IP then you will need to configure Inter Cluster
Trunks
Are the CallManager clusters similiar versions?

In a small environment, you can use static route patterns to point to these
trunks in each cluster anyway.
On the inbound CSS you can have translation patterns to strip the 31 and
deliver it to the 4 digit extension
Be careful to preserve calling party number across the trunks as well, so
the other end can dial back.

In larger environments you would use a gatekeeper controlled ICT.

Cheers,

Tim



On 7/8/08, Akaal singh <akaalvoip at googlemail.com> wrote:
>
> Plan is to do it over IP and use the PSTN if we need to. simple answer is
> to use 31xxxx for extension but the business have decided they want 4 digit
> extension as most users are use to it dialing 4 number. So we have to work
> do all the background work.
>
> I am thinking of using translation patterns, just want to have a feel of
> what others are doing. would this be the best way is they a simple method to
> all of this.
>
> Thanks alot
>
>
>  On Tue, Jul 8, 2008 at 3:57 PM, Robert Kulagowski <rkulagow at gmail.com>
> wrote:
>
>>  Akaal singh wrote:
>>
>>> Hi,
>>>
>>> We have a few clusters cross the global, within each site we are using 4
>>> digit extension. We want to call each site using extension, 4 digit will
>>> not
>>> work for us. so thinking of using Site code for each location. So if I
>>> have
>>> a exterension 5568 in location A to call it from location B I would dial
>>> 315568. 31 will be the site code for location A. How would I go by
>>> setting
>>> this up.
>>>
>>
>>
>> Are you going to route your calls over IP or over the PSTN?
>>
>> If it's over IP, then couldn't you renumber your phones at site 31 to be
>> 31xxxx?
>>
>> If it's over PSTN, then what we did was setup translation patterns.  In
>> our case we have 31.XXXX as a TP, where we do Discard Digits PreDot and
>> Prefix Digits as 91212987
>>
>> That way if you dial 315568 your outgoing number becomes 912129875568 and
>> it's handled by your normal route patterns.
>>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080708/ba8365bd/attachment.html>