PNIs need backups. Unlike most data, voice cares about latency, so if your 
Ashburn PNI fails, now you're routing via Dallas (for instance), which may be 
an unacceptable increase in latency, jitter, packet loss, etc. 


With SIP re-invite being fairly common, just because you have a PNI for your 
signaling doesn't mean your RTP follows the same path. 


NTT/Telia/Lumen/etc. won't peer with you over an IX because the traffic volumes 
to qualify for peering are enormous and usually inappropriate for IXes. Well, 
that and protectionism. Also, for them, the Internet *IS* the product. For a 
voice provider, the product is the voice service, the Internet is incidental. 
The primary concern of IP peering for voice providers is of data integrity, not 
cost avoidance. 




----- 
Mike Hammett 
Intelligent Computing Solutions 
http://www.ics-il.com 



Midwest Internet Exchange 
http://www.midwest-ix.com 



----- Original Message -----

From: "Ross Tajvar" <r...@tajvar.io> 
To: "Mike Hammett" <voice...@ics-il.net> 
Cc: "Paul Timmins" <p...@timmins.net>, "VoiceOps" <voiceops@voiceops.org> 
Sent: Monday, September 27, 2021 1:38:32 AM 
Subject: Re: [VoiceOps] Bandwidth East Coast Issues 



On Sun, Sep 26, 2021 at 5:24 PM Mike Hammett < voice...@ics-il.net > wrote: 





I have IXes in areas where Inteliquent and Peerless have POPs. They haven't had 
any interest. 


I don't understand. 




I understand. Serious customers will pay for a PNI. Industry partners (other 
large telcos with whom they exchange a lot of traffic) will get a PNI because 
it is more reliable/higher bandwidth/etc. An IX presence may help customers who 
send voice traffic over the internet, but I suspect those customers make up a 
small percentage of any given telco's revenue. So, there's no incentive. Same 
reason NTT/Telia/Lumen/etc. won't peer with you over an IX. Why would they, 
when they can sell you transit? 
_______________________________________________
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

Reply via email to