<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2853" name=GENERATOR>
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
        COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
        COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
        COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
        COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
        COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
        page: Section1
}
</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 vLink=purple link=blue bgColor=#ffffff>
<DIV><FONT face=Arial size=2>I wonder if anyone has any thoughts on
this. Using continue on fail works fine for failover but to the best
of my knowledge it only works if you do not get an answer or session
progress. The trouble with this is if you are calling cell phones etc, it
can take up to 12 seconds to get the messages. I would like to explore if
failover could be instituted by not receiving a Trying message. This is
usually returned immediately and does stop the freeswitch from sending more
invites. That way, a 4 second timer could be used and switch to an
alternate route early and still give reasonable completion times.
</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>The tcap trace below shows a typical call to a cell
in our area, the trying is almost immediate while the cell in this case
took 5.5 seconds. I have seen this quite frequently take as long as 12
seconds.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Also, when calling internationally, longer times
are quite common.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Perhaps this is already implemented but I have not
been able to find it.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>449.776291 SIP/SDP Request: INVITE
sip:1613802xxxx@xxx.xxx.xxx.xx, with session description<BR>449.782429 SIP
Status: 100 Trying<BR>456.211562 SIP/SDP Status: 183 Session Progress,
with session description<BR><BR></FONT></DIV>
<DIV><FONT face=Arial size=2>Darcy Primrose</FONT></DIV>
<DIV><FONT face=Arial size=2>voice2net</DIV></FONT></BODY></HTML>