<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>I've heard that one of the ILECs is looking to productize SIP interconnect for tandems and such. M&A may change those plans, however.</div><div><br></div><div data-marker="__SIG_PRE__"><br><br>-----<br>Mike Hammett<br>Intelligent Computing Solutions<br>http://www.ics-il.com<br><br><br><br>Midwest Internet Exchange<br>http://www.midwest-ix.com<br><br></div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>"BackUP Telecom Consulting" <marylou@backuptelecom.com><br><b>To: </b>"Nick Olsen" <nick@141networks.com><br><b>Cc: </b>"Mike Hammett" <voiceops@ics-il.net>, "Voiceops" <voiceops@voiceops.org><br><b>Sent: </b>Tuesday, September 24, 2024 5:17:23 PM<br><b>Subject: </b>Re: [VoiceOps] Onvoy CO Buildout<br></div><div><br></div><div data-marker="__QUOTED_TEXT__">
<p>As of yet I am not aware of any RBOCs or ILECs that will interconnect via SIP transport. The whole problem with the industry is that the big guys bought up all the copper transport providers back in 2017/2018. Then as soon as they bought them up they stopped offering copper transport. The RBOCs and ILECs act like they are totally incapable of interconnecting via SIP (which we all know is BS). Yet in the last year they upped the price of TDM transport by 50% so now even the big CLECs are hurting as a result. The RBOCs and ILECs are the only carriers in the industry that refuse to connect via SIP transport.</p>
<p>The FCC is totally guilty of looking the other way and acting as if they are completely clueless through all this. I've complained about it to them on multiple occasions and I know others have as well. The FCC never does anything so they clearly know but don't care. Actions speak louder than words! </p>
<div>
<p>MARY LOU CAREY <br>BackUP Telecom Consulting <br>Office: 615-791-9969 <br>Cell: 615-796-1111</p>
</div>
<p><br></p>
<p>On 2024-09-23 07:10 PM, nick via VoiceOps wrote:</p>
<blockquote style="padding:0 0.4em;border-left:#1010ff 2px solid;margin:0">
<div style="font-family:'arial';font-size:14px">
<div>TDM is getting harder and harder to come by. It's possible that they were either kicked off, or perhaps priced off their previous TDM transport into the LATA, instead electing to install some kind of TDM over IP transport gear in leased Colo. Assuming they didn't physically house a switch in the LATA and just transported it to some nearby POP. I've had to do this in several places, and I've heard of some big names doing the same (As well as pulling out of a given LATA due to transport costs).</div>
<div> </div>
<div> </div>
<div> </div>
<hr id="previousmessagehr">
<div><strong style="font-weight:bold">From</strong>: "Mike Hammett via VoiceOps" <voiceops@voiceops.org><br><strong style="font-weight:bold">Sent</strong>: 9/23/24 3:56 PM<br><strong style="font-weight:bold">To</strong>: Voiceops <voiceops@voiceops.org><br><strong style="font-weight:bold">Subject</strong>: [VoiceOps] Onvoy CO Buildout<br></div>
<div> </div>
<div style="font-family:'arial' , 'helvetica' , sans-serif;font-size:10pt;color:#000000">I see a space in one of our COs (it is a tandem site) marked out for deployment by Onvoy (I'm assuming it's all of Inteliquent and not just Onvoy). Now, Inteliquent has had a presence in our LATA for years, so what all are they doing with this buildout? They weren't present in this CO before.<br><br>
<div><br><br>-----<br>Mike Hammett<br>Intelligent Computing Solutions<br><a style="color:#006693;text-decoration:underline" href="http://www.ics-il.com" rel="noopener noreferrer nofollow noopener noreferrer" target="_blank">http://www.ics-il.com</a><br><br><br><br>Midwest Internet Exchange<br><a style="color:#006693;text-decoration:underline" href="http://www.midwest-ix.com" rel="noopener noreferrer nofollow noopener noreferrer" target="_blank">http://www.midwest-ix.com</a><br><br><br></div>
</div>
</div>
<br>
<div class="pre" style="margin:0;padding:0;font-family:monospace">_______________________________________________<br> VoiceOps mailing list<br> <a href="mailto:VoiceOps@voiceops.org" target="_blank" rel="nofollow noopener noreferrer">VoiceOps@voiceops.org</a><br> <a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noopener noreferrer nofollow noopener noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></div>
</blockquote><br></div></div></body></html>