CUCM call routing
I have two different versions of CUCM at two different offices. Let’s call them Office A and Office B.
Office A - (USA, Version 8.6, MGCP Gateway, 2 x PRIs)
Office B - (UK, Version 8.0, H323 Gateway, 2 x PRIs)
Inter-cluster trunk is configured on both CUCM meaning we can call local extensions at both offices. The long term goal is to upgrade CUCM at Office B to match Office A version then add Office B to CUCM group at Office A. The issue we currently have is that when the 2 PRIs at office B are down, external calls are not possible until the provider rectifies the ISDN issue.
The question is during the PRI outage - how do we route calls originating from Office B out of the CUCM/MGCP gateway in office A (tail end hop off)? What would be ideal is to apply CSS to each line which then routes the calls out of Office A.
At the moment, users are having to dial a different prefix i.e. 8 + number i.e. 8 + 001 646 xxx xxxx for tail end hop off which works. 9 + 001 646 xxx xxxx would be best utilizing a CSS which points to the CUCM/MGCP at office A.
Any help/ideals would be helpful.
Office A - (USA, Version 8.6, MGCP Gateway, 2 x PRIs)
Office B - (UK, Version 8.0, H323 Gateway, 2 x PRIs)
Inter-cluster trunk is configured on both CUCM meaning we can call local extensions at both offices. The long term goal is to upgrade CUCM at Office B to match Office A version then add Office B to CUCM group at Office A. The issue we currently have is that when the 2 PRIs at office B are down, external calls are not possible until the provider rectifies the ISDN issue.
The question is during the PRI outage - how do we route calls originating from Office B out of the CUCM/MGCP gateway in office A (tail end hop off)? What would be ideal is to apply CSS to each line which then routes the calls out of Office A.
At the moment, users are having to dial a different prefix i.e. 8 + number i.e. 8 + 001 646 xxx xxxx for tail end hop off which works. 9 + 001 646 xxx xxxx would be best utilizing a CSS which points to the CUCM/MGCP at office A.
Any help/ideals would be helpful.
ASKER
Correct. 99% of calls at office B are outbound.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This is already in place:
What you need is to configure a route group with the PRIs in office B inside, then you assign this RG to a route list.
When I create the RG, don't see the ICT listed as an available device...I tried searching for it but it doesn't come up. Does that mean I need to create a new ICT as well...assuming the existing ICT is already in use (dependency records show the existing ICT is in use by 12 route patterns)
What you need is to configure a route group with the PRIs in office B inside, then you assign this RG to a route list.
When I create the RG, don't see the ICT listed as an available device...I tried searching for it but it doesn't come up. Does that mean I need to create a new ICT as well...assuming the existing ICT is already in use (dependency records show the existing ICT is in use by 12 route patterns)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
feedback next week
ASKER
Worked like a charm...there were digits manipulation needed at both ends but the suggestions by willlywilburwonka was very helpful as usual. Thanks.
Welcome
You could have Office A provide a SIP trunk to Office B, then add that another route. Similar to how you would handle PRI 1 and 2 and each site,