Optimizing VoIP orig routing to exploit Verizon VoIP TDM interconnections
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
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 else? 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 some ideas. -Ryan 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 https://puck.nether.net/mailman/listinfo/voiceops
The Verizon originated calls from the PSTN to our network tend to already be optimized. For example, our Orlando numbers tend to get media from Orlando, our DC area ones come from Cleveland, our San Francisco ones come from San Francisco. We don't interconnect in these cities. So the Verizon proxies manage the inbound quite well. If you're doing outbound local, the same occurs no matter where you send the call. Inter and Intra state isn't the same, its random as to where the media comes from. These observations obviously only apply if you don't proxy media. ~Jared On Wed, Dec 11, 2013 at 11:07 AM, Ryan Delgrosso <ryandelgrosso at gmail.com>wrote:
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 else?
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 some ideas.
-Ryan
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 https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
I've tried to noodle up a plan for that kind of thing in the past... However, I can't convince myself that I know enough about the current/future carrier topology to raise the confidence level up to where it seems actionable. My biggest latency problems (by hundreds of milliseconds) have been algorithmic (transcoding, huge buffers, etc), not distance. Does anyone have a switch on either coast? It'd be interesting to see if someone in NYI or OneWil has issues that seem weighted one way or the other. Thanks, David -----Original Message----- From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Mark Lindsey Sent: Wednesday, December 11, 2013 10:54 To: voiceops at voiceops.org Subject: [VoiceOps] Optimizing VoIP orig routing to exploit Verizon VoIP TDM interconnections 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 https://puck.nether.net/mailman/listinfo/voiceops This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
I have switches in both One Wil and in Boston but the motivation to do this was largely for bandwidth optimization so I didn't clog up my cross country circuits with RTP that didn't need to be there. The quality gain is there but i wouldn't consider it the selling point of undertaking a project like this since most people cant tell the difference between a call I hot-potatoed off the network locally vs one I back-hauled across the country, at least until the cross country link starts to saturate.... I showed a 63% decrease in network utilization when I switched to steering terminating calls by SDP C line. Again on the orig side its harder to control depending on how your customers expect to receive calls. Here is a link to the paper. http://www.transnexus.com/index.php/geo-intelligent-routing-improves-quality... On 12/11/2013 11:21 AM, Hiers, David wrote:
I've tried to noodle up a plan for that kind of thing in the past... However, I can't convince myself that I know enough about the current/future carrier topology to raise the confidence level up to where it seems actionable.
My biggest latency problems (by hundreds of milliseconds) have been algorithmic (transcoding, huge buffers, etc), not distance.
Does anyone have a switch on either coast? It'd be interesting to see if someone in NYI or OneWil has issues that seem weighted one way or the other.
Thanks,
David
-----Original Message----- From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Mark Lindsey Sent: Wednesday, December 11, 2013 10:54 To: voiceops at voiceops.org Subject: [VoiceOps] Optimizing VoIP orig routing to exploit Verizon VoIP TDM interconnections
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 https://puck.nether.net/mailman/listinfo/voiceops
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Nice! This method does not presuppose knowledge other than IP address location, which can be readily (1) determined and (2) refreshed. David -----Original Message----- From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Ryan Delgrosso Sent: Wednesday, December 11, 2013 11:32 To: voiceops at voiceops.org Subject: Re: [VoiceOps] Optimizing VoIP orig routing to exploit Verizon VoIP TDM interconnections I have switches in both One Wil and in Boston but the motivation to do this was largely for bandwidth optimization so I didn't clog up my cross country circuits with RTP that didn't need to be there. The quality gain is there but i wouldn't consider it the selling point of undertaking a project like this since most people cant tell the difference between a call I hot-potatoed off the network locally vs one I back-hauled across the country, at least until the cross country link starts to saturate.... I showed a 63% decrease in network utilization when I switched to steering terminating calls by SDP C line. Again on the orig side its harder to control depending on how your customers expect to receive calls. Here is a link to the paper. http://www.transnexus.com/index.php/geo-intelligent-routing-improves-quality... On 12/11/2013 11:21 AM, Hiers, David wrote:
I've tried to noodle up a plan for that kind of thing in the past... However, I can't convince myself that I know enough about the current/future carrier topology to raise the confidence level up to where it seems actionable.
My biggest latency problems (by hundreds of milliseconds) have been algorithmic (transcoding, huge buffers, etc), not distance.
Does anyone have a switch on either coast? It'd be interesting to see if someone in NYI or OneWil has issues that seem weighted one way or the other.
Thanks,
David
-----Original Message----- From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Mark Lindsey Sent: Wednesday, December 11, 2013 10:54 To: voiceops at voiceops.org Subject: [VoiceOps] Optimizing VoIP orig routing to exploit Verizon VoIP TDM interconnections
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 https://puck.nether.net/mailman/listinfo/voiceops
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
participants (4)
-
David.Hiers＠adp.com -
jared＠compuwizz.net -
lindsey＠e-c-group.com -
ryandelgrosso＠gmail.com