[cisco-voip] Redudant Call Routing in case of AA-CUE fails

[Matthew Saskin]

I think under 'sip-ua' you'll want to play around with the different 
timers available.  Off the top of my head, I'm not sure what specifically.

-matt

Anthony Kouloglou wrote:
> Hi,
> well that is what i did with no luck thow!
> 
>     * Dial-peer pointing to AA is SIP with preference 0.
> 
>     * 2nd Dial-peer with preference 1 is h323 pointing to local numbers
>       (i apply with success a Translation Profile).
> 
> When CUE module is OFFLINE or reloading or anyway unreachable, first 
> dial-peer is always active.
> I have debugged the voip ccapi to see that after 60 seconds, when 
> rec-timer-exp (102) expires, the call is routed to the second dial-peer 
> and all work fine.
> I would know how to solve this problem if it was H323 dial-peer: with 
> voice class and "h225 timeout tcp establish 3"
> But what can be done know that it is a SIP dial-peer?
> Thanks for your time,
> 
> Kind Regards
> Anthony
> 
> Matthew Saskin wrote:
>> Well, you'd need to have somewhere else to route those calls, then a 
>> dial-peer with the same pattern but a different preference should do 
>> the trick.
>>
>> -matt
>>
>> Anthony Kouloglou wrote:
>>> Hi, is it possible to provide redudancy in a cme 7.0 - CUE-AIM 3.2 
>>> for the AutoAttendant?
>>> I have configured the appropriate dial-peerd for triggering the AA 
>>> and it works fine, but what happens if the AIM fails or need to be 
>>> rebooted?
>>> For example, changing the NTP, requires a system reboot!!
>>> What must be done in the CME config to provide this redudancy?
>>>
>>> Thanks
>>> Akoul
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>