[VoiceOps] Optimizing VoIP orig routing to exploit Verizon VoIP TDM interconnections
ryandelgrosso at gmail.com
Wed Dec 11 14:07:48 EST 2013
I think the better question is if this is origination what is the
endpoint its touching down on? Will that be an IP endpoint or something
If its an IP endpoint is it going to be geographically homed?
I struggled with this for some time and finally concluded that what I
was chasing with orig had very little gain on the orig side due to load
balancing from my carriers etc, so I proceeded with termination since I
could control it much more tightly. If you are dealing with trunking
traffic where your customer side is statically defined then you might
try what I did for term though and do your steering based on the C line
in the SDP, and make sure your customers peer with BOTH locations so you
can avoid the back-haul.
TransNexus and I did a whitepaper on the topic maybe it will give you
On 12/11/2013 10:54 AM, Mark Lindsey wrote:
> I'm trying to plan a US nationwide georedundant SIP interconnect with
> Verizon for origination and termination. I want to minimize delay
> between parties, and heuristically I'll pretend people tend to talk
> more to other people who are local.
> So it seems smart to get my "western" origination traffic to my
> Western SBC primarily, and my "eastern" traffic to my Eastern SBC.
> Does anyone have a good method for deciding which side of the country
> it makes sense to send traffic to?
> For example, when I port a Minneapolis number to Verizon, is it any
> better to have Verizon send it west, or east?
> Or does it make no difference at all?
> My current method is simply to use the Mississippi River. But I'll bet
> if I had full visibility into Verizon's network and their TDM local
> access tandem interconnects, the answer might be different.
>>>> mark at ecg.co +12293160013 http://ecg.co/lindsey
> VoiceOps mailing list
> VoiceOps at voiceops.org
More information about the VoiceOps