Sweet! Thanks<br><br><div class="gmail_quote">On Fri, Nov 16, 2012 at 4:35 PM, Adam Frankel (afrankel) <span dir="ltr"><<a href="mailto:afrankel@cisco.com" target="_blank">afrankel@cisco.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">
<div style="font-family:Arial;font-size:13px" text="#000000" bgcolor="#FFFFFF">
<div style="font-family:Arial;font-size:13px"><span>
<h3><a href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/trunks.html#wp1123287" target="_blank">http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/trunks.html#wp1123287</a><br>
</h3>
<h3>
SIP OPTIONS Ping
</h3>
<p>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. <b>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. </b>
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.
</p>
</span><br>
HTH,<br>
Adam<br>
<br>
<br>
<span>
<div>
<hr><font style="font-size:x-small" face="Tahoma"><b>From:</b>
Ted Nugent <a href="mailto:tednugent73@gmail.com" target="_blank"><tednugent73@gmail.com></a><br>
<b>Sent:</b> Thu, Nov 15, 2012 5:58:11 PM<br>
<b>To:</b> Ryan Ratliff <a href="mailto:rratliff@cisco.com" target="_blank"><rratliff@cisco.com></a><br>
<b>CC:</b> Cisco VoIPoE List
<a href="mailto:cisco-voip@puck.nether.net" target="_blank"><cisco-voip@puck.nether.net></a><div class="im"><br>
<b>Subject:</b> Re: [cisco-voip] CUCM SRV records
CSCth25928<br>
</div></font><br>
</div>
</span><div><div class="h5">
<blockquote style="border:currentColor!important;padding-right:0px!important;padding-left:0px!important;font-size:medium;margin-right:0px!important;margin-left:0px!important" type="cite">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?<br>
<br>
<div class="gmail_quote">
On Thu, Nov 15, 2012 at 10:15 AM, Ted Nugent <span dir="ltr"><<a href="mailto:tednugent73@gmail.com" target="_blank">tednugent73@gmail.com</a>></span>
wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">
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!
<div>
<div><br>
<br>
<div class="gmail_quote">On Thu, Nov 15, 2012 at 9:29
AM, Ryan Ratliff <span dir="ltr"><<a href="mailto:rratliff@cisco.com" target="_blank">rratliff@cisco.com</a>></span>
wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">
<div style="word-wrap:break-word">
<blockquote style="border:currentColor!important;padding-right:0px!important;padding-left:0px!important;margin-right:0px!important;margin-left:0px!important" type="cite">Status:
Open(Assigned)<br>
</blockquote>
<div><br>
</div>
Not resolved yet. Use A records as a workaround.
<div><br>
<div>
<span style="text-transform:none;text-indent:0px;letter-spacing:normal;word-spacing:0px;white-space:normal;border-collapse:separate">-Ryan</span>
</div>
<br>
<div>
<div>
<div>
<div>On Nov 14, 2012, at 6:19 PM, Ted
Nugent <<a href="mailto:tednugent73@gmail.com" target="_blank">tednugent73@gmail.com</a>>
wrote:</div>
<br>
<div>Is it possible this is still
unresolved or maybe been resolved in a
duplicate bug id? HOPEFULLY!</div>
<div>Does anyone know if this was resolved
by 8.6.2?</div>
<div> </div>
<div><strong>CSCth25928 Bug Details</strong></div>
<form onsubmit="return window.confirm("You are submitting information to an external page.\nAre you sure?");" method="post" name="13b0b26163f2fa8e_13b04a3e151c952a_13b0479aba8b7a4e_btkAlternateDataForm" target="_blank">
<input name="appContext" value="/Support/BugToolKit" type="hidden">
<div>
<table border="0" cellspacing="2" cellpadding="5" width="100%">
<tbody>
<tr>
<td style="padding:8px;font-size:88%" colspan="2"><span><strong>
Change the behavior for
invoking additional DNS
SRV queries </strong></span></td>
</tr>
<tr>
<td style="padding:0px 8px 8px;font-size:88%" valign="top"><span><b>Symptom:</b><br>
When the Primary server is
down CM does not try the
second server mentioned in<br>
the SRV record.<br>
Even when the timer expires
it resets the timer and
again starts sending the<br>
NOTIFY request to Primary
DNS SRV record.</span></td>
</tr>
</tbody>
</table>
</div>
</form>
<div>
<table border="0" cellspacing="2" cellpadding="5" width="100%">
</table>
</div>
</div>
</div>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
<br>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
cisco-voip mailing list
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</div></div></div>
</div>
</blockquote></div><br>