[cisco-voip] CUCM SRV records CSCth25928

[Ted Nugent]

Sweet! Thanks

On Fri, Nov 16, 2012 at 4:35 PM, Adam Frankel (afrankel) <afrankel at cisco.com
> wrote:

>
> http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/trunks.html#wp1123287
>  SIP OPTIONS Ping
>
> The SIP OPTIONS Ping feature can be enabled on the SIP Profile associated
> with a SIP trunk to dynamically track the state of the trunk's
> destination(s). When this feature is enabled, each node running the trunk's
> SIP daemon will periodically send an OPTIONS Request to each of the trunk's
> destination IP addresses to determine its reachability and will send calls
> only to reachable nodes. *A destination address is considered to be "out
> of service" if it fails to respond to an OPTIONS Request, if it sends a
> Service Unavailable (503) response or Request Timeout (408) response, or if
> a TCP connection cannot be established. * The trunk state is considered
> to be "in service" when at least one node receives a response (other than a
> 408 or 503) from a least one destination address. SIP trunk nodes can send
> OPTIONS Requests to the trunk's configured destination IP addresses or to
> the resolved IP addresses of the trunk's DNS SRV entry. Enabling SIP
> OPTIONS Ping is recommended for all SIP trunks because it allows Unified CM
> to dynamically track trunk state rather than determining trunk state on a
> per-call and timeout basis.
>
> HTH,
> Adam
>
>
>  ------------------------------
> *From:* Ted Nugent <tednugent73 at gmail.com> <tednugent73 at gmail.com>
> *Sent:* Thu, Nov 15, 2012 5:58:11 PM
> *To:* Ryan Ratliff <rratliff at cisco.com> <rratliff at cisco.com>
> *CC:* Cisco VoIPoE List <cisco-voip at puck.nether.net><cisco-voip at puck.nether.net>
>
> *Subject:* Re: [cisco-voip] CUCM SRV records CSCth25928
>
>  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 listcisco-voip at puck.nether.nethttps://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20121116/d15e9908/attachment.html>