[cisco-voip] Solution required for SIP Trunk resilience

[Wes Sisk]

I have not seen any solutions offered so going to suggest 2:

1. use an MGCP gateway with 2xT1-PRI and a crossover cable.  Add one of 
the PRI's in the RG or in a 2nd RG with the SIP trunk.  This works well 
but it limits to 23 calls (24 if you use CAS) and it costs $$ for the 
hardware.

2. create an h323 gateway that points to the ipaddress of the local cm.  
add this to the RG or in a 2nd RG.  This is the same approach as above 
only use h323 so the hairpin happens in IP.  This generally "works" 
however it is not well supported.  We have identified leaks associated 
with this call flow. It is not a typically recommended config so 
limitations will not be fixed.  All that said, it's adequate when push 
comes to shove or possibly enough to get you through an outage window on 
other equipment.

/Wes

Boon wrote:
> Hi,
>  
> I have to integrate a 3rd party IVR system with my CUCM7 via a SIP 
> Trunk. This IVR will front the entire contact centre which is also 3rd 
> party (dont ask!!). Although these systems appear to integrate ok I'm 
> a little concerned that I wont have an automatic process of routing 
> calls and bypassing the IVR SIP trunk directly to the contact centre 
> if the IVR server experienced an outage.
>  
> If I'm routing the calls to the SIP trunk via a route pattern the only 
> options I can see are route lists/groups. The contact centre entry 
> points are CTI Route Points which I cannot insert into the route 
> list/groups.
>  
> Does anyone have any ideas how I can provide resilliency or am I 
> better off creating a seperate partition with the contact centre/IVR 
> numbers and manually inserting that into the ISDN gateway's inbound 
> CSS during an IVR outage?
>  
> Any help would be highly appreciated.
>  
> Thanks
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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/20101109/d696d7a3/attachment.html>