[cisco-voip] SIP trunk failover question

[Erick Wellnitz]

When I started my design I realized I had to use multiple RG for the RL and
that actually solves the problem on the 'global' side of the CUBE when
using the busy/unreachable service parameters.

SIP ping will solve the problem on the local side if routing gets botched
or some other issue disrupts connectivity to the CUBE.

Thanks Ryan and Robert.  I learned a thing or two about making my SIP
trunks a bit more resilient today.


On Tue, May 14, 2013 at 1:32 PM, Ryan Ratliff <rratliff at cisco.com> wrote:

> You may also want to look at the behavior available to you by having
> multiple route groups in a route list vs multiple devices in the RG.
>
> http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_0_1/ccmsys/a03rp.html#wp1045311 does
> a decent job of covering this.
>
>
> -Ryan
>
> On May 14, 2013, at 1:00 PM, Erick Wellnitz <ewellnitzvoip at gmail.com>
> wrote:
>
> Looks like this isn't going to happen until our upgrade.  It's waited this
> long already...
>
>
> On Tue, May 14, 2013 at 9:54 AM, Erick Wellnitz <ewellnitzvoip at gmail.com>wrote:
>
>> Great!  That's exactly what I was looking for but didn't know what it was
>> called.
>>
>>
>> On Tue, May 14, 2013 at 9:46 AM, Robert Kulagowski <rkulagow at gmail.com>wrote:
>>
>>> On Tue, May 14, 2013 at 9:27 AM, Erick Wellnitz <ewellnitzvoip at gmail.com>
>>> wrote:
>>> > I use top down distribution.  Are there any other settings I need to
>>> make
>>> > sure that the calls don't fail when the SIP trunk is unavailable for
>>> any
>>> > reason?
>>>
>>> Depending on the version of CM that you're using, you may want to
>>> check "SIP PING".
>>>
>>
>>
> _______________________________________________
> 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/20130514/fc60d363/attachment.html>