GW/Trunk selection based on partition

[Valentine Sondoyi]

Hi All

Is it possible to have a scenario where the CUCM checks a dialed pattern and places the call based on the partition?

The scenario is as follows;

We are migrating form Avaya IPO to Cisco CUCM. We have Cisco CUCM talking to Avaya PBX via SIP trunk. Extensions on CUCM can call avaya exteensions and vice versa. We can also make offnet calls via SIP to Avaya. As we migrate extensions, we have a situation where the extension pattern 2XXX exists on both Cisco and Avaya. To call extensions on Avaya, we are having to add an extra digit, eg 92XXX. This is however, not a good user experience and we have been advised to drop the 9, so that users should not be confused.

The plan now is to place all extensions still existing on the Avaya in a partition separate from the local CUCM extension partition. The question is how do we route calls to extensions in this avaya partition? if we create a pattern 2xxx and route to the SIP trunk, will this work if the that pattern is not on the local partition? if not how do we best do this?

Many thanks

VKS

[saif musa]

Hi,

What about the case when you need to call from Avaya to CUCM on extensions 2xxx? did that work?

[Valentine Sondoyi]

Yes... Avaya to Cisco works fine. 

[Mohammed al Baqari]

Hi,

I am assuming that you delete the extension from Avaya when you configure it in CUCM. If you do so then you can have RP for 2XXX as Jaime mentioned in the same partition as internal CUCM DNs.

When the user call an extension, for example 2002, CUCM will lookup in DN database for 2002. If its not a DN, the RP 2XXX will be matched as fallback and the call will be sent to Avaya.

The key is that you delete the DNs from Avaya when you configure them in CUCM.

[saif musa]

Hi,

Besides the comments of fellow experts to your post here, Personally. I would not recommend using the same user extension DNs in both PBX and any call control system like CUCM or other. different hardware requires different user extension numbers. That's my first rule inside my voice network.

Regards

[Jaime Valencia]

This all comes down to CSS, partitions and best match routing.

if you move the DN 2002 to CUCM, and have a RP set to 2xxx that points to a SIP trunk, if you dial 2002, you will reach the DN, not the RP.

[HARIS_HUSSAIN]

So let us say we have 2001 extension in CUCM PT_Internal and we have 2001 in Avaya.

So Case1 :-  Phone with Both PT_Internal and PT_Avaya Partition

CSS_Phone

 PT_Internal (Contain 2001 Extension)

 PT_Avaya (Contains 2xxx Route Pattern)

:======> We can reach 2001 DN in Cisco but  we cannot reach 2001 on avaya. To facilitate that we must use 92XXX route patten

Case 2 :- Phone with Only PT_Avaya Partition

CSS_Phone

PT_Avaya (contain RP 2xxx)

====> So phone can reach 2001 in Avaya but cannot reach 2001 in Cisco)

Case 2 :- Phone with only PT_Internal

CSS_Phone

 PT_Internal (Contain 2001 DN)

======> So Phone can reach 2001 in Internal but not on Avaya.

To conclude with overlapping number we must use some kind of prefix for reachability  and of course user training is required for that!!

Hope that helps

Please rate and mark correct posts

Thanks

Haris