<div dir="auto">Honestly as a rural ilec I’d love to interconnect via sip. But AT&T won’t hear of it. It’s TDM or nothing with them. And usually a DS0 on a in-used ds1 with old school channel banks on their part. . Even though we have a fiber interconnect. </div><div dir="auto"><br></div><div dir="auto">I was once in a conference call wit AT&T about a 911 ds0 being down. We had the switch people and the CO people on the phone who all agreed it was a bad channel on a channel bank. But depspite everyone who needed to change things being on the call and agreeing, an order needed to be submitted and approved. And the same people needed to go back out 2 weeks later to make the changes. Why is AT&T still around?</div><div dir="auto"><br></div><div dir="auto">Aso in an unrelated point. One of our SS7 links was down for a week while AT&T “investigated”. Even the Ss7 folks reached out to me to let me know it was down. Again. But unfortunately the SS7 folks are apparently unable to talk to the plant folks to get it fixed. We tried switching to intelliquent. But they built tdm ds1s to metro Detroit office buildings. Then tried to charge us for their mistake. </div><div dir="auto"><br></div><div dir="auto">At some point something will give. But it’s probably the rural folks. Rant over. </div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Oct 2, 2024 at 5:15 PM Mike Hammett via VoiceOps <<a href="mailto:voiceops@voiceops.org">voiceops@voiceops.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><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><br><br>-----<br>Mike Hammett<br>Intelligent Computing Solutions<br><a href="http://www.ics-il.com" target="_blank">http://www.ics-il.com</a><br><br><br><br>Midwest Internet Exchange<br><a href="http://www.midwest-ix.com" target="_blank">http://www.midwest-ix.com</a><br><br></div><div><br></div><hr id="m_940297280645079359zwchr"><div><b>From: </b>"BackUP Telecom Consulting" <<a href="mailto:marylou@backuptelecom.com" target="_blank">marylou@backuptelecom.com</a>><br><b>To: </b>"Nick Olsen" <<a href="mailto:nick@141networks.com" target="_blank">nick@141networks.com</a>><br><b>Cc: </b>"Mike Hammett" <<a href="mailto:voiceops@ics-il.net" target="_blank">voiceops@ics-il.net</a>>, "Voiceops" <<a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>><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>
<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></div></div></div><div><div style="font-family:arial,helvetica,sans-serif;font-size:12pt;color:#000000"><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="m_940297280645079359previousmessagehr">
<div><strong style="font-weight:bold">From</strong>: "Mike Hammett via VoiceOps" <<a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>><br><strong style="font-weight:bold">Sent</strong>: 9/23/24 3:56 PM<br><strong style="font-weight:bold">To</strong>: Voiceops <<a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>><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 style="margin:0;padding:0;font-family:monospace">_______________________________________________<br> VoiceOps mailing list<br> <a href="mailto:VoiceOps@voiceops.org" rel="nofollow noopener noreferrer" target="_blank">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></div>_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote></div></div>