<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>When you say level3 does not support options ping, do you mean they won’t ping you for failover, or they don’t allow you to send it to them? Only two messages and the lack of any response will busy the endpoint, anything else if good enough for CUBE.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><img width=287 height=186 style='width:2.9916in;height:1.9416in' id="Picture_x0020_1" src="cid:image001.png@01D49850.4C5C9AD0"><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> cisco-voip <cisco-voip-bounces@puck.nether.net> <b>On Behalf Of </b>Ryan Huff<br><b>Sent:</b> Thursday, December 20, 2018 10:35 AM<br><b>To:</b> Erik Anderson <erik.anderson.85@gmail.com>; cisco-voip voyp list <cisco-voip@puck.nether.net><br><b>Subject:</b> Re: [cisco-voip] SIP Fail over<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt;color:black'>Couldn't you just use voice class sip options/keepalives to mark when the ITSP is down, so CUCM marks the trunk out of service and fails to the next route group member immediately (ideally, your secondary CUBE)? Seems like thats a more natural way of doing it versus using IP SLAs...<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p></div><div id=signature><div id=divtagdefaultwrapper><p class=MsoNormal style='background:white'><span style='font-size:12.0pt;color:black'>Thanks,<o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='font-size:12.0pt;color:black'>- Ryan<o:p></o:p></span></p></div></div><div class=MsoNormal align=center style='text-align:center'><hr size=3 width="98%" align=center></div><div id=divRplyFwdMsg><p class=MsoNormal><b><span style='color:black'>From:</span></b><span style='color:black'> cisco-voip <<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>> on behalf of Erik Anderson <<a href="mailto:erik.anderson.85@gmail.com">erik.anderson.85@gmail.com</a>><br><b>Sent:</b> Thursday, December 20, 2018 12:03 PM<br><b>To:</b> cisco-voip voyp list<br><b>Subject:</b> [cisco-voip] SIP Fail over</span> <o:p></o:p></p><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal>Morning Folks, <o:p></o:p></p><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><p>We have implemented a new SIP solution with Level 3 and found that we have outbound calling failover issues. When a CUBE loses its ability to talk to its Level 3 Peer, but can still talk to CUCM outbound calls will still connect to the CUBE, but fail connecting to Level 3. In turn CUCM still thinks the call is connected since the CUCM SIP trunk remains up to the CUBE.<o:p></o:p></p><p> <o:p></o:p></p><p>Architecture Notes:<o:p></o:p></p><p> <o:p></o:p></p><p>4 Locations with 1 CUBE Each<o:p></o:p></p><p>4 CUCM SIP Trunks with each connecting to one of the 4 CUBEs<o:p></o:p></p><p>4 CUCM Route Groups with Various CUBE/SIP Trunks assigned a Distribution Algorithm of <i>Top Down</i><o:p></o:p></p><p>Each CUBE has 2 SIP Peers<o:p></o:p></p><p>Each CUBE can only talk to its respective SIP peer via its local Level 3 Transport to reduce call control latency by not allowing it to use the DMVPN backup network<o:p></o:p></p><p>Level 3 does not support SIP Options Ping<o:p></o:p></p><p>CUCM Trunks have SIP Options Ping enabled<o:p></o:p></p><p> <o:p></o:p></p><p>Call Flows:<o:p></o:p></p><p> <o:p></o:p></p><p style='margin-left:27.0pt'>Working Flow:<o:p></o:p></p><p> <o:p></o:p></p><p style='margin-left:27.0pt'>Phone ----> SLRG ----> Route Group Member #1 ----> CUBE SIP TRUNK ----> CUBE ----> Level 3 Transport ----> Level 3 SIP Peer #1/#2 ----> Call Completes<o:p></o:p></p><p style='margin-left:3.75in'> <o:p></o:p></p><p style='margin-left:3.75in'> <o:p></o:p></p><p style='margin-left:27.0pt'>CUBE Failure:<o:p></o:p></p><p> <o:p></o:p></p><p style='margin-left:27.0pt'>Phone ----> SLRG ----><o:p></o:p></p><p style='margin-left:81.0pt'> Route Group Member #1 ----> CUBE SIP TRUNK --X--> CUBE (CUCM Cant Reach CUBE)<o:p></o:p></p><p style='margin-left:135.0pt'> <o:p></o:p></p><p style='margin-left:81.0pt'> CUCM Routes Call to Next Route Group Member<o:p></o:p></p><p style='margin-left:135.0pt'> <o:p></o:p></p><p style='margin-left:27.0pt'> Route Group Member #2 ----> CUBE SIP TRUNK ----> CUBE ----> Level 3 Transport ----> Level 3 SIP Peer #1/#2 ----> Call Completes<o:p></o:p></p><p style='margin-left:27.0pt'> <o:p></o:p></p><p style='margin-left:27.0pt'>Level 3 Transport Failure/SIP Server Failure:<o:p></o:p></p><p> <o:p></o:p></p><p style='margin-left:27.0pt'>Phone ----> SLRG ----><o:p></o:p></p><p style='margin-left:81.0pt'> Route Group Member #1 ----> CUBE SIP TRUNK ----> CUBE --X--> Level 3 Transport (CUBE Cant Reach Level 3 SIP Server)<o:p></o:p></p><p style='margin-left:135.0pt'> <o:p></o:p></p><p style='margin-left:81.0pt'> CUCM Thinks Call Connects since the CUBE accepts the call, Phone gets dead air, never tries the next RG Member<o:p></o:p></p><p style='margin-left:135.0pt'> <o:p></o:p></p><p> <o:p></o:p></p><p>My idea to fix this is to use an IPSLA to ping the pingable address on the Level 3 SIP Servers. If both address are unreachable then shutdown the CUCM Dial-Peers. This doesn’t sounds like the best way of fixing it, but it should work. <o:p></o:p></p><p> <o:p></o:p></p><p>If any has any other better ideas please let me know.<o:p></o:p></p></div><p class=MsoNormal>-- <o:p></o:p></p><div><p class=MsoNormal>Erik Anderson<o:p></o:p></p></div></div><div><p class=MsoNormal>Telecom Manager<o:p></o:p></p></div><div><p class=MsoNormal>Some Random Corp.<o:p></o:p></p></div></div></div></div></body></html>