[VoiceOps] Level3 Vector Network - Inbound Failover

[Peter Fabian]

I am on the vector/sonus network.


Peter Fabian | Senior Voice Engineer | Telesphere | P: 4803857059 | F:
4803857079



On Wed, Sep 1, 2010 at 3:09 PM, Geoff Mina <gmina at connectfirst.com> wrote:

>  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.
>
>
>
> Geoff MINA
> ---------------------------------
> Chief Technical Officer
>
> Connect First Inc.
> P: 678.905.0671
>
> T: 888.410.3071
>
> F: 678.265.1158
>
> E: gmina at connectfirst.com
> ---------------------------------
> www.connectfirst.com
>
>
>
> [image: cf_logo]
>
>
>
> *From:* voiceops-bounces at voiceops.org [mailto:
> voiceops-bounces at voiceops.org] *On Behalf Of *Peter Fabian
> *Sent:* Wednesday, September 01, 2010 4:33 PM
> *To:* Alex Balashov
> *Cc:* voiceops at voiceops.org
> *Subject:* Re: [VoiceOps] Level3 Vector Network - Inbound Failover
>
>
>
> 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
>
>
>
>
> Peter Fabian | Senior Voice Engineer | Telesphere | P: 4803857059 | F:
> 4803857079
>
>
>  On Wed, Sep 1, 2010 at 1:27 PM, Alex Balashov <abalashov at evaristesys.com>
> wrote:
>
> They should be able to fail over on a 503.  But not a 603, for the reason
> that 6xx-class errors are semantically different.
>
>
>
> On 09/01/2010 03:01 PM, Geoff Mina wrote:
>
>  I am currently setting up Level3 as a provider of SIP Toll-Free
> services.  I am hearing from my account team that they don’t have any
> option other than their BusyNoAnswer option to failover from one SIP IP
> (on my side) to another. If I send back a 486 or there is a timeout they
> can failover to a second trunk. Unfortunately, they can’t decouple the
> 486 and timeout scenarios… and that doesn’t work, because 486 is a
> normal non-error condition on my network and I wouldn’t want the call to
> be re-presented to another location just because the first location sent
> a BUSY.
>
> I have asked them if they can failover on 5XX errors or internally
> generated 408, but they seem to think they are unable to do anything
> like this.
>
> Anyone have any experience with Level3 in this scenario?
>
> Thanks,
>
> Geoff
>
>
>   _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
>
> --
> Alex Balashov - Principal
> Evariste Systems LLC
> 1170 Peachtree Street
> 12th Floor, Suite 1200
> Atlanta, GA 30309
> Tel: +1-678-954-0670
> Fax: +1-404-961-1892
> Web: http://www.evaristesys.com/
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.441 / Virus Database: 271.1.1/3103 - Release Date: 09/01/10
> 06:34:00
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20100901/dc86a6c1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 3418 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20100901/dc86a6c1/attachment.jpg>