I am on the vector/sonus network.<div><br></div><div><br clear="all">Peter Fabian | Senior Voice Engineer | Telesphere | P: 4803857059 | F: 4803857079<br><br>
<br><br><div class="gmail_quote">On Wed, Sep 1, 2010 at 3:09 PM, Geoff Mina <span dir="ltr"><<a href="mailto:gmina@connectfirst.com">gmina@connectfirst.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Interesting. Are both of you on the Vector /Sonus network? I
know for a fact Sonus switches can do what I’m asking… so I’m not sure why they
wouldn’t choose to use that feature.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#1F497D">Geoff MINA <br>
--------------------------------- <br>
Chief Technical Officer</span><span style="color:#1F497D"></span></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#1F497D">Connect First Inc. <br>
P: 678.905.0671</span></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#1F497D">T: 888.410.3071</span><span style="font-size:11.0pt;color:#1F497D"></span></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#1F497D">F: 678.265.1158</span><span style="font-size:11.0pt;color:#1F497D"></span></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#1F497D">E: <a href="mailto:gmina@connectfirst.com" target="_blank"><span style="color:#1F497D">gmina@connectfirst.com</span></a><br>
--------------------------------- <br>
</span><span style="font-size:11.0pt;color:#1F497D"><a href="http://www.connectfirst.com/" target="_blank"><span style="font-size:7.5pt;color:#1F497D">www.connectfirst.com</span></a></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><img border="0" width="169" height="19" src="cid:image001.jpg@01CB49F8.73CA35A0" alt="cf_logo"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt">
<a href="mailto:voiceops-bounces@voiceops.org" target="_blank">voiceops-bounces@voiceops.org</a> [mailto:<a href="mailto:voiceops-bounces@voiceops.org" target="_blank">voiceops-bounces@voiceops.org</a>] <b>On
Behalf Of </b>Peter Fabian<br>
<b>Sent:</b> Wednesday, September 01, 2010 4:33 PM<br>
<b>To:</b> Alex Balashov<br>
<b>Cc:</b> <a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a><br>
<b>Subject:</b> Re: [VoiceOps] Level3 Vector Network - Inbound Failover</span></p>
</div><div><div></div><div class="h5">
<p class="MsoNormal"> </p>
<p class="MsoNormal">I have been fighting this same thing for the last month or
so. L3 has told me that the only option that they have is the hard set 25
second timer with BNA. They have also told me that they do not support
rerouting on 503's. As for the BNAO settings, I was told they had
attempted to implement a better solution but it did not work well and so they
are back to the process of evaluating alternate methods</p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br clear="all">
Peter Fabian | Senior Voice Engineer | Telesphere | P: 4803857059 | F: 4803857079<br>
<br>
<br>
</p>
<div>
<p class="MsoNormal">On Wed, Sep 1, 2010 at 1:27 PM, Alex Balashov <<a href="mailto:abalashov@evaristesys.com" target="_blank">abalashov@evaristesys.com</a>>
wrote:</p>
<p class="MsoNormal">They should be able to fail over on a 503. But not a
603, for the reason that 6xx-class errors are semantically different.</p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
On 09/01/2010 03:01 PM, Geoff Mina wrote:</p>
</div>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I am currently setting up
Level3 as a provider of SIP Toll-Free<br>
services. I am hearing from my account team that they don’t have any<br>
option other than their BusyNoAnswer option to failover from one SIP IP<br>
(on my side) to another. If I send back a 486 or there is a timeout they<br>
can failover to a second trunk. Unfortunately, they can’t decouple the<br>
486 and timeout scenarios… and that doesn’t work, because 486 is a<br>
normal non-error condition on my network and I wouldn’t want the call to<br>
be re-presented to another location just because the first location sent<br>
a BUSY.<br>
<br>
I have asked them if they can failover on 5XX errors or internally<br>
generated 408, but they seem to think they are unable to do anything<br>
like this.<br>
<br>
Anyone have any experience with Level3 in this scenario?<br>
<br>
Thanks,<br>
<br>
Geoff<br>
<br>
<br>
</p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></p>
</blockquote>
<p class="MsoNormal"><br>
<br>
-- <br>
Alex Balashov - Principal<br>
Evariste Systems LLC<br>
1170 Peachtree Street<br>
12th Floor, Suite 1200<br>
Atlanta, GA 30309<br>
Tel: +1-678-954-0670<br>
Fax: +1-404-961-1892<br>
Web: <a href="http://www.evaristesys.com/" target="_blank">http://www.evaristesys.com/</a><br>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></p>
</div>
<p class="MsoNormal"> </p>
</div>
</div></div><p><span style="font-size:10.0pt">No virus
found in this incoming message.<br>
Checked by AVG - <a href="http://www.avg.com" target="_blank">www.avg.com</a><br>
Version: 8.5.441 / Virus Database: 271.1.1/3103 - Release Date: 09/01/10
06:34:00</span></p>
</div>
</div>
</blockquote></div><br></div>