VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
August 2009
- 77 participants
- 440 messages
Geographic redundancy
by jvanick@spruce.oaknet.com
> > No, not sure how you got this idea, you think every mid-sized ISP in the
> > '90s had connections to the service control points? For a CLEC to get a
> > lot of the O/T benefits SS7 interconnection would be desirable, but not
> > required.
>
> That's true. I was assuming we were talking about telephony here
> strictly.
>
> There are a few uses ISPs have for CLEC licenses that have nothing to do
> with phone. One is rights-of-way for network build-out, pole
> attachment, etc. Another is getting UNE rates on leased circuits
> instead of wholesale access rates. That still required interconnection
> and/or CO colocation for aggregation, but not SS7.
There were 2 other good reasons to have a clec license, at least in the
rate-center type latas... (Chicago/Lata 358 comes to mind)...
1. was to play the reciprocal comp game with the ILEC... At least one CLEC's
entire business model was nearly completely based on this early on (Focal Communications)
2. was to have a folded modem pool where all the rate centers terminated into one
large modem pool. It was easy to turn up a few ds3s to a few tandem switches to receive
inbound calls from a large portion of the lata. After you got up and running and found the
'hot spots' you'd then turn up end-office trunks to each of those rate centers to take
advantage of the more favorable termination rates for #1.
Ah the good 'ol days of the Dial-up isp biz... I remember 20+ Ascend Max TNT's each humming
along with 16 inbound PRI's of dial-up...
If I remember correctly tho, in order to connect to the tandems you had to be able to provide
ss7 services. We got all of our ports out of a DMS500, but I do remember people using something
from cisco to emulate a switch (SCC maybe?) and back end all the dial traffic into 5800's....
-J
Aug. 12, 2009
Geographic redundancy
by abalashov@evaristesys.com
David Birnbaum wrote:
> I think perhaps we're using "interconnection" differently.
Yeah; perhaps connection to ILEC tandems should be deemed
Interconnection with a capital I. :-)
A lot of ITSPs that don't actually touch the LEC side of things don't
know this, so, you're absolutely right. Peering is exchanging traffic
with another carrier in some sort of bidirectional settlement
arrangement explicitly for that purpose (analogous to settlement-free IP
peering, but not necessarily settlement-free as we know - recip. comp.
and all that), and access is buying origination or termination from
another carrier.
Access is really what ITSPs as well as CLECs buying inter-LATA LD from
IXCs do. If you're a VoIP provider and buy VoIP or TDM trunks from a
CLEC, you're buying access; you're not on horizontal footing with them,
you're not a "peer" - you're a customer.
Peering, I think, should be reserved for CLECs that connect to each
other for the purpose of passing traffic directly and getting around the
Bell tandems.
> However, if you want to connect directly to the tandems for the purposes
> of owning number blocks, registering an LRN, porting numbers natively,
> etc. there is no way to do that with IP.
Well, it depends on what is meant by "directly." One could argue that
there's nothing "indirect" about taking SIGTRAN from a third party. You
still signal ISUP and/or TCAP, just over IP. The only difference is
that the physical A-links aren't coming to you and that your point codes
are physically homed somewhere else. The switch CLLI and the
accompanying LRNs and number blocks and so on are still pointing to your
equipment; you can port numbers natively, do LNP dips natively, etc.
It's just that there's a network element in the middle doing some
protocol conversion.
> If you peer with another carrier who does the IP/TDM interconnection at
> the tandems on your behalf, you are still beholden to the actual CLEC
> that owns your numbers. To me, that's the true difference (which is
> both technical as well as regulatory) between a CLEC and a
> facilities-based reseller.
I agree. There is a whole pile of things you have to do and facilities
you have to own and operate as a CLEC that you do not have to as an
ITSP/reseller of an underlying carrier.
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Aug. 12, 2009
Geographic redundancy
by davidb@pins.net
I think perhaps we're using "interconnection" differently.
Obviously, you can SIP peer and "interconnect" via various IP<->SS7 gateways for
the purposes of exchanging signaling traffic. As you point out, there's a whole
pile of technologies available with various pros and cons.
However, if you want to connect directly to the tandems for the purposes of
owning number blocks, registering an LRN, porting numbers natively, etc. there
is no way to do that with IP. If you buy media gateways to do the TDM -> IP
conversion, then you are now in the TDM world with all that implies; I don't
prejudice against running an "IP backplane" with distributed media gateways vs.
a more traditional DMS or 5E. That's how I run my network, after all, but
that's semantics from the PSTN perspective. One man's "media gateway" is
another man's switch. The SS7 call control and the PSTN interconnection are
already separate.
If you peer with another carrier who does the IP/TDM interconnection at the
tandems on your behalf, you are still beholden to the actual CLEC that owns your
numbers. To me, that's the true difference (which is both technical as well as
regulatory) between a CLEC and a facilities-based reseller. This may change at
some point (actually, I'm sure it WILL change at some point) but that's at least
a couple of years out, I'm guessing.
Cheers,
David.
-----
On Wed, 12 Aug 2009, Alex Balashov wrote:
> David Birnbaum wrote:
>
>> I don't believe it's possible to interconnect with IP anywhere as a CLEC
>> since the PSTN infrastructure doesn't exist outside of the SS7 environment
>> for all practical purposes. (Obviously, you can peer with IP but that's
>> not the same as interconnection from a PSTN perspective).
>
> Sure it is. That's basically what SIGTRAN is; SS7 mapped onto IP.
>
> I don't know if VeriSign still offers their interconnection product (forget
> what it was called), but it used to be until very recently that you could get
> them to take your point codes and send you the signaling out the back side as
> SIGTRAN, over Internet VPN.
>
> I've seen many DIY switches built that way, usually for cheap CLECs created
> to support the back side of some VoIP product who don't want to shell out for
> a real switch. Common technique there is to purchase a SIGTRAN to
> H.248/MEGACO and/or MGCP signaling gateway and drive media gateways with that
> controller. So, your physical bearer IMTs can come from the local ILEC to
> your MGWs but your SS7 can come from somewhere else over the Internet
> indirectly.
>
> Squire makes a product that does this
> (http://www.squire-technologies.co.uk/) and I'm sure there are others. Last
> I heard none of them do TCAP/LNP yet, though, which is obviously going to be
> something of a crippling factor if you're interconnecting in a pooling area
> (most markets at this point). And I understand them to have other problems,
> as well. Nevertheless, it is possible.
>
> Level3 famously built their own signaling gateway for the Lucent TNT Max via
> H.248 in their pre-Viper platform, although I do not know whether the other
> side of that was SS7 or ISDN Q.931 or whatnot. But it did work.
>
> -- Alex
>
> --
> Alex Balashov
> Evariste Systems
> Web : http://www.evaristesys.com/
> Tel : (+1) (678) 954-0670
> Direct : (+1) (678) 954-0671
>
Aug. 12, 2009
Geographic redundancy
by abalashov@evaristesys.com
Robin Rodriguez wrote:
> On Aug 12, 2009, at 1:37 AM, Kenny Sallee wrote:
>
>> OK I see - from a CLEC perspective - is it a legal requirement to do
>> so? I've read some of this tonight:
>> http://www.voip-info.org/wiki/view/How+to+start+a+Clec and although
>> it's mentioned a bit I'm not clear on if it's a legal requirement of a
>> CLEC (or just implied because in 1996 that's just the way it was)
>>
>> ITSP vs CLEC redundancy sounds like it's quite different then - if you
>> must have SS7 links.
>
> No, not sure how you got this idea, you think every mid-sized ISP in the
> '90s had connections to the service control points? For a CLEC to get a
> lot of the O/T benefits SS7 interconnection would be desirable, but not
> required.
That's true. I was assuming we were talking about telephony here
strictly.
There are a few uses ISPs have for CLEC licenses that have nothing to do
with phone. One is rights-of-way for network build-out, pole
attachment, etc. Another is getting UNE rates on leased circuits
instead of wholesale access rates. That still required interconnection
and/or CO colocation for aggregation, but not SS7.
>> Along those lines - I'm reading up on BW and geographical
>> HA...http://www.broadsoft.com/products/broadworks/platform/#network-geograp…
>> -- anyone out there actually who has actually implemented it - if so
>> what's your experiences if you can share on list?
>>
> Sounds like linux-HA style workings to me, but I have no exposure to
> broadsoft products.
Yep. All these devices pretty much work on the same principle, although
even the Linux-based ones have proprietary failover technologies and
don't use Linux-HA.
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Aug. 12, 2009
Geographic redundancy
by rrodriguez@ifbyphone.com
On Aug 12, 2009, at 1:37 AM, Kenny Sallee wrote:
> OK I see - from a CLEC perspective - is it a legal requirement to do
> so? I've read some of this tonight: http://www.voip-info.org/wiki/view/How+to+start+a+Clec
> and although it's mentioned a bit I'm not clear on if it's a legal
> requirement of a CLEC (or just implied because in 1996 that's just
> the way it was)
>
> ITSP vs CLEC redundancy sounds like it's quite different then - if
> you must have SS7 links.
No, not sure how you got this idea, you think every mid-sized ISP in
the '90s had connections to the service control points? For a CLEC to
get a lot of the O/T benefits SS7 interconnection would be desirable,
but not required.
>
> From an ITSP perspective - redundancy sounds like it comes down to
> IP latency between signalling entities and their capabilities,
> hardware, and cash (like mentioned below).
What you are describing is QoS from an ITSP perspective, redundancy
from an ITSP perspective would entail things like anycast, service
records, bgp announcements across diverse circuits, and geographic
diversity of POPs
>
> Along those lines - I'm reading up on BW and geographical HA...http://www.broadsoft.com/products/broadworks/platform/#network-geograp…
> -- anyone out there actually who has actually implemented it - if
> so what's your experiences if you can share on list?
>
Sounds like linux-HA style workings to me, but I have no exposure to
broadsoft products.
>
>
>
> On Tue, Aug 11, 2009 at 11:14 PM, Alex Balashov <abalashov at evaristesys.com
> > wrote:
> Kenny Sallee wrote:
>
> On a curiosity note - why would you even need to interconnect with
> SS7 to the PSTN when you can SIP peer to all the major carriers?
> There can be an argument for backup to SIP peering that makes
> sense. Maybe it's cheaper? But outside of those what other
> benefits are there (don't misread my tone here - I'm really asking)?
>
> If you're just an ITSP, you may not need to, strictly speaking. But
> if you're a CLEC, you do, and the original question seemed to be
> heavily concerned with making CLEC facilities redundant.
>
> Beyond that, it's a matter of opinion. My experience has been that
> SIP peering isn't terribly mature; reliability and interop issues
> abound. I've had a number of high-volume customers that gave up and
> went to TDM access circuits after they realised that their top tech
> people spend 90% of all days dealing with SIP issues from their O/T
> providers.
>
> It's the usual litany of crap. formatting differences (E.164 vs.
> ten-digit), buggy in-band DTMF, very buggy RFC2833 (out-of-band)
> DTMF, caller ID and CNAM (From vs. Remote-Party-ID vs. P-Asserted-
> Identity), QoS, one-way audio, dropped calls, DSP bugs in ISDN<-
> >VoIP gateways, etc. When they move to TDM these problems seem to
> magically go away.
>
> But I have other customers that just don't seem to have a lot of
> these problems, either. It's a coin toss.
>
>
> --
> Alex Balashov
> Evariste Systems
> Web : http://www.evaristesys.com/
> Tel : (+1) (678) 954-0670
> Direct : (+1) (678) 954-0671
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
--
Robin D. Rodriguez
rrodriguez at ifbyphone.com
Aug. 12, 2009
Geographic redundancy
by abalashov@evaristesys.com
Kenny Sallee wrote:
> OK I see - from a CLEC perspective - is it a legal requirement to do
> so? I've read some of this tonight:
> http://www.voip-info.org/wiki/view/How+to+start+a+Clec and although it's
> mentioned a bit I'm not clear on if it's a legal requirement of a CLEC
> (or just implied because in 1996 that's just the way it was)
First, that document is a bit simplistic and dated. There's no such
thing as a "pure-resale" CLEC any longer; that's what UNE-P was, and it
went away in 2003. You can resell things from the ILEC (albeit, not
especially profitably), but you still have to have facilities. It is no
longer possible to rent and resell ports on an ILEC switch. There were
a lot of arbitrage/resale plays that died when that ruling came down.
Otherwise, in your question, are you referring to SS7 interconnection
with the incumbent?
I don't believe it's necessary to have any physical interconnection
active in order to have a CLEC license and do nothing with it.
Interconnection is just a practical requirement of operating as a CLEC;
it's part of the definition of a facilities-based CLEC that it
connects to the ILEC, because the CLEC is entitled to take advantage of
some of the ILEC's physical plant, network, and various other
facilities. CLECs lease copper services in order to build circuits to
customers that the ILEC's plant can reach, to colocate in ILEC central
offices, are eligible for certain types of special rates for access
products, etc.
But even if you're not colocating in COs or generating UNE circuits, you
still have to pass traffic to the ILEC because a majority of intra-LATA
subscribers are going to be ILEC customers in your local rate center, or
reachable via the ILEC's one or more tandem offices. IXCs also
traditionally land at the tandem, although it is possible to connect to
some of them directly with access circuits or VoIP peering. Other
competitive carriers operating in the same LATA are also met at the ILEC
tandem, and so on. There are some alternatives to ILEC tandem access
such as Neutral Tandem, but these aren't substitutes for the ILEC tandem
- they just get you a cheaper way to meet the same players in your LATA
and bypass some tandem access charges.
The other thing you have to keep in mind is regulatory obligations faced
by CLECs. For example, as a CLEC you're required to provide equal
access to any IXC (long-distance/inter-LATA carrier) the customer wants
to use via 1010 dial-around or PIC. How are you going to allow them to
use *any* CAC if you're only directly connected to two IXCs? You can
only hit up the rest at the Bell tandem. Same for emergency calls:
hitting PSAPs requires going through special 911 trunk groups on your
SS7 IMT to special 911 tandems run by the ILEC. Add number portability,
directory services, number pooling, and a bunch of other good things,
and, there's not really a way to participate without connecting to the
ILEC.
So, yes, in practice, you have to interconnect with the ILEC if you are
a competitive carrier, and SS7 is the only way to do that. Using some
ILEC facilities is part of what it means to be a competitive carrier.
If you have a free and clear monopoly on a small town of a few thousand
people in rural Minnesota, plant and all, that may be small-town telco,
but that's not "competitive," as conceived by TRA96.
If you don't want to connect via physical SS7 link circuits, see my most
about SIGTRAN. But you still need physical TDM trunks for the bearer
portion of the interconnect. You can get away with having someone else
convert those trunks into VoIP and do the signaling to the ILEC for you,
but, someone's gotta do it.
> ITSP vs CLEC redundancy sounds like it's quite different then - if you
> must have SS7 links.
It is. But, beyond the SS7 stuff, it can be remarkably similar
depending on how "soft" and/or IP-oriented the core equipment in use is.
> From an ITSP perspective - redundancy sounds like it comes down to IP
> latency between signalling entities and their capabilities, hardware,
> and cash (like mentioned below).
Latency actually isn't that big of a deal unless you're talking halfway
around the world. It's reliability, really.
-- Alex
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Aug. 12, 2009
Geographic redundancy
by rrodriguez@ifbyphone.com
On Aug 12, 2009, at 1:37 AM, Kenny Sallee wrote:
> OK I see - from a CLEC perspective - is it a legal requirement to do
> so? I've read some of this tonight: http://www.voip-info.org/wiki/view/How+to+start+a+Clec
> and although it's mentioned a bit I'm not clear on if it's a legal
> requirement of a CLEC (or just implied because in 1996 that's just
> the way it was)
>
> ITSP vs CLEC redundancy sounds like it's quite different then - if
> you must have SS7 links.
No, not sure how you got this idea, you think every mid-sized ISP in
the '90s had connections to the service control points? For a CLEC to
get a lot of the O/T benefits SS7 interconnection would be desirable,
but not required.
>
> From an ITSP perspective - redundancy sounds like it comes down to
> IP latency between signalling entities and their capabilities,
> hardware, and cash (like mentioned below).
What you are describing is QoS from an ITSP perspective, redundancy
from an ITSP perspective would entail things like anycast, service
records, bgp announcements across diverse circuits, and geographic
diversity of POPs
>
> Along those lines - I'm reading up on BW and geographical HA...http://www.broadsoft.com/products/broadworks/platform/#network-geograp…
> -- anyone out there actually who has actually implemented it - if
> so what's your experiences if you can share on list?
>
Sounds like linux-HA style workings to me, but I have no exposure to
broadsoft products.
>
>
>
> On Tue, Aug 11, 2009 at 11:14 PM, Alex Balashov <abalashov at evaristesys.com
> > wrote:
> Kenny Sallee wrote:
>
> On a curiosity note - why would you even need to interconnect with
> SS7 to the PSTN when you can SIP peer to all the major carriers?
> There can be an argument for backup to SIP peering that makes
> sense. Maybe it's cheaper? But outside of those what other
> benefits are there (don't misread my tone here - I'm really asking)?
>
> If you're just an ITSP, you may not need to, strictly speaking. But
> if you're a CLEC, you do, and the original question seemed to be
> heavily concerned with making CLEC facilities redundant.
>
> Beyond that, it's a matter of opinion. My experience has been that
> SIP peering isn't terribly mature; reliability and interop issues
> abound. I've had a number of high-volume customers that gave up and
> went to TDM access circuits after they realised that their top tech
> people spend 90% of all days dealing with SIP issues from their O/T
> providers.
>
> It's the usual litany of crap. formatting differences (E.164 vs.
> ten-digit), buggy in-band DTMF, very buggy RFC2833 (out-of-band)
> DTMF, caller ID and CNAM (From vs. Remote-Party-ID vs. P-Asserted-
> Identity), QoS, one-way audio, dropped calls, DSP bugs in ISDN<-
> >VoIP gateways, etc. When they move to TDM these problems seem to
> magically go away.
>
> But I have other customers that just don't seem to have a lot of
> these problems, either. It's a coin toss.
>
>
> --
> Alex Balashov
> Evariste Systems
> Web : http://www.evaristesys.com/
> Tel : (+1) (678) 954-0670
> Direct : (+1) (678) 954-0671
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
--
Robin D. Rodriguez
rrodriguez at ifbyphone.com
Aug. 12, 2009
Geographic redundancy
by kenny.sallee@gmail.com
OK I see - from a CLEC perspective - is it a legal requirement to do so?
I've read some of this tonight:
http://www.voip-info.org/wiki/view/How+to+start+a+Clec and although it's
mentioned a bit I'm not clear on if it's a legal requirement of a CLEC (or
just implied because in 1996 that's just the way it was)
ITSP vs CLEC redundancy sounds like it's quite different then - if you must
have SS7 links.
>From an ITSP perspective - redundancy sounds like it comes down to IP
latency between signalling entities and their capabilities, hardware, and
cash (like mentioned below).
Along those lines - I'm reading up on BW and geographical HA...
http://www.broadsoft.com/products/broadworks/platform/#network-geographic
-- anyone out there actually who has actually implemented it - if so what's
your experiences if you can share on list?
On Tue, Aug 11, 2009 at 11:14 PM, Alex Balashov
<abalashov at evaristesys.com>wrote:
> Kenny Sallee wrote:
>
> On a curiosity note - why would you even need to interconnect with SS7 to
>> the PSTN when you can SIP peer to all the major carriers? There can be an
>> argument for backup to SIP peering that makes sense. Maybe it's cheaper?
>> But outside of those what other benefits are there (don't misread my tone
>> here - I'm really asking)?
>>
>
> If you're just an ITSP, you may not need to, strictly speaking. But if
> you're a CLEC, you do, and the original question seemed to be heavily
> concerned with making CLEC facilities redundant.
>
> Beyond that, it's a matter of opinion. My experience has been that SIP
> peering isn't terribly mature; reliability and interop issues abound. I've
> had a number of high-volume customers that gave up and went to TDM access
> circuits after they realised that their top tech people spend 90% of all
> days dealing with SIP issues from their O/T providers.
>
> It's the usual litany of crap. formatting differences (E.164 vs.
> ten-digit), buggy in-band DTMF, very buggy RFC2833 (out-of-band) DTMF,
> caller ID and CNAM (From vs. Remote-Party-ID vs. P-Asserted-Identity), QoS,
> one-way audio, dropped calls, DSP bugs in ISDN<->VoIP gateways, etc. When
> they move to TDM these problems seem to magically go away.
>
> But I have other customers that just don't seem to have a lot of these
> problems, either. It's a coin toss.
>
>
> --
> Alex Balashov
> Evariste Systems
> Web : http://www.evaristesys.com/
> Tel : (+1) (678) 954-0670
> Direct : (+1) (678) 954-0671
>
Aug. 12, 2009
Geographic redundancy
by abalashov@evaristesys.com
Kenny Sallee wrote:
> On a curiosity note - why would you even need to interconnect with SS7
> to the PSTN when you can SIP peer to all the major carriers? There can
> be an argument for backup to SIP peering that makes sense. Maybe it's
> cheaper? But outside of those what other benefits are there (don't
> misread my tone here - I'm really asking)?
If you're just an ITSP, you may not need to, strictly speaking. But if
you're a CLEC, you do, and the original question seemed to be heavily
concerned with making CLEC facilities redundant.
Beyond that, it's a matter of opinion. My experience has been that SIP
peering isn't terribly mature; reliability and interop issues abound.
I've had a number of high-volume customers that gave up and went to TDM
access circuits after they realised that their top tech people spend 90%
of all days dealing with SIP issues from their O/T providers.
It's the usual litany of crap. formatting differences (E.164 vs.
ten-digit), buggy in-band DTMF, very buggy RFC2833 (out-of-band) DTMF,
caller ID and CNAM (From vs. Remote-Party-ID vs. P-Asserted-Identity),
QoS, one-way audio, dropped calls, DSP bugs in ISDN<->VoIP gateways,
etc. When they move to TDM these problems seem to magically go away.
But I have other customers that just don't seem to have a lot of these
problems, either. It's a coin toss.
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Aug. 12, 2009
Geographic redundancy
by kenny.sallee@gmail.com
Or just tell your clients that cool technology comes at a cost - that cost
is more downtime due to other problems mentioned earlier in this thread and
the inherint problems of sharing voice and data on the same
medium....Actually, it's an interesting problem to solve from both the core
and cpe perspectives that all revolve around which vendors you use, business
requirements, and cash (with cash being the first variable)...
On a curiosity note - why would you even need to interconnect with SS7 to
the PSTN when you can SIP peer to all the major carriers? There can be an
argument for backup to SIP peering that makes sense. Maybe it's cheaper?
But outside of those what other benefits are there (don't misread my tone
here - I'm really asking)?
Kenny
On Tue, Aug 11, 2009 at 6:45 PM, David Birnbaum <davidb at pins.net> wrote:
> Kenny,
>
> A number of different options exist for redundancy, but they all depend on
> your underlying network architecture and connectivity options. The newest
> switches tend to have call agents and media gateways that are separate, so
> you can have redundancy across your hardware and call control
> geographically. Some older switches are more monolithic, so you have more
> redundancy in your network since that has to survive more.
>
> You also find the world changes pretty dramatically when you go from
> Asterisk (which I use generically to refer to any small-scale solution of
> under 2k endpoints or so) to Big Iron - you pay a lot more money for all
> sorts of redundancy and scalability, and as a result you solve problems very
> differently (and have different options to solve problems). Right now
> Asterisk can't exist without the big iron (5E, MetaSwitch, Broadsoft, etc.)
> because it can't handle the call routing, SS7 interop, etc. One can think
> of the smaller VoIP providers as basic class 5 switches providing the
> traditional end-user connectivity and not worrying about the bigger issues
> that will bedevil people as they head into the interconnection world.
>
> If you can split your call control and media between geographical
> locations, then you can set up as a CLEC in two colocations, and
> interconnect to the necessary tandems to exchange traffic with two unrelated
> circuits, and then have lots of room to lose one half of your network
> without affecting core call control (how you get to your customers is a
> different problem, of course). Switches can also function in an
> emergency-standalone world as well. SS7 already has all of the redundancy
> options via multiple A-links to the outside world. I don't believe it's
> possible to interconnect with IP anywhere as a CLEC since the PSTN
> infrastructure doesn't exist outside of the SS7 environment for all
> practical purposes. (Obviously, you can peer with IP but that's not the
> same as interconnection from a PSTN perspective).
>
> If you can't split your call control, then you use SONET and other
> self-healing architecture to buttress your network as much as possible
> against fiber cuts, MUX outages, and other crashes with the hope that you
> never lose both ends of your ring at the same time.
>
> Cheers,
>
> David.
>
> ------------------------------
>
> Kenny Sallee wrote:
>
> Yes IP makes it easier but you still have to 'plugin' to the PSTN
> somewhere and in some fashion correct? Unless you have nothing but SIP
> peering it does get a little more complicated (although I'm new to the VoIP
> world and do not know SS7). Then you still have to worry about your call
> processing platform: can it live with being greater than x ms apart from
> it's redundant pair? What about CDR's and reporting - how do you merge
> those coming from multiple sources? I would think there's also rate center
> and latency issues as well with outbound routing of calls (send calls out
> the cheapest carrier that will allow it). I don't think any of it's
> impossible, but the presence of IP doesn't remove all complexity.
>
> I like David's idea of a VoiceOps working group to help define options.
> Sounds like fun
> Kenny
>
>
>
> On Tue, Aug 11, 2009 at 7:23 AM, Alex Balashov <abalashov at evaristesys.com>wrote:
>
>> Seems to me like one of the main arguments for moving to IP infrastructure
>> - alongside the numerous arguments telco people have against it - is that it
>> makes this type of redundancy a lot more achievable and cost-effective.
>>
>> --
>> Alex Balashov
>> Evariste Systems
>> Web : http://www.evaristesys.com/
>> Tel : (+1) (678) 954-0670
>> Direct : (+1) (678) 954-0671
>> Mobile : (+1) (678) 237-1775
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>
> ------------------------------
>
> _______________________________________________
> VoiceOps mailing listVoiceOps at voiceops.orghttps://puck.nether.net/mailman/listinfo/voiceops
>
>
Aug. 12, 2009