[cisco-voip] CUCM SRV records CSCth25928

[Justin Steinberg]

if I recall it seems to round robin to the IPs.   I would recommend using
multiple SIP trunks in CM and controlling your routing via RL/RG.

On Thu, Nov 15, 2012 at 5:58 PM, Ted Nugent <tednugent73 at gmail.com> wrote:

> Does anyone know (have tested) that the multiple hosts on the SIP trunk
> will actually provide failover if the primary host goes done? If that's the
> case then no need to make a-records right?
>
>
> On Thu, Nov 15, 2012 at 10:15 AM, Ted Nugent <tednugent73 at gmail.com>wrote:
>
>> That's what I was afraid of... Was allowing multiple host entries in the
>> SIP trunk configuration put in place to get around this at least in
>> a failover configuration? This "enhancement" has been open for WELL over a
>> year!
>>
>>
>> On Thu, Nov 15, 2012 at 9:29 AM, Ryan Ratliff <rratliff at cisco.com> wrote:
>>
>>> Status: Open(Assigned)
>>>
>>>
>>> Not resolved yet.  Use A records as a workaround.
>>>
>>> -Ryan
>>>
>>> On Nov 14, 2012, at 6:19 PM, Ted Nugent <tednugent73 at gmail.com> wrote:
>>>
>>> Is it possible this is still unresolved or maybe been resolved in a
>>> duplicate bug id? HOPEFULLY!
>>> Does anyone know if this was resolved by 8.6.2?
>>>
>>> *CSCth25928 Bug Details*
>>>  * Change the behavior for invoking additional DNS SRV queries * *
>>> Symptom:*
>>> When the Primary server is down CM does not try the second server
>>> mentioned in
>>> the SRV record.
>>> Even when the timer expires it resets the timer and again starts sending
>>> the
>>> NOTIFY request to Primary DNS SRV record.
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>
> _______________________________________________
> 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/20121115/5a9cae37/attachment.html>