<div dir="ltr"><div dir="ltr">Ah, didn't know that. Well, with any luck those guys still work there, just in a different physical location.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 16, 2022 at 6:30 PM Nate Burke <<a href="mailto:nate@blastcomm.com">nate@blastcomm.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
Not sure about the people, but I live in Naperville, and Comcast has
left that building (all their signage is down) <br>
<br>
<div>On 6/16/2022 5:21 PM, Ross Tajvar
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">At Comcast, when you file an FCC complaint, it goes
to these people (as of a couple years ago, might be different
people now):
<div>
<div><br>
</div>
</div>
William Landis | Engineer 3, Business Escalations<br>
1415 West Diehl Road, Naperville, IL 60563<br>
Office: (331) 814-3041<br>
<a href="mailto:william_landis@comcast.com" target="_blank">william_landis@comcast.com</a>
<div><br>
</div>
<div>his boss:<br>
Jeff Cox | Manager, Business Escalations<br>
Operations<br>
1415 West Diehl Road, Naperville, IL 60563<br>
Office: (331) 401-5525<br>
<a href="mailto:jeffery_cox@comcast.com" target="_blank">jeffery_cox@comcast.com</a></div>
<div><br>
</div>
<div><br>
</div>
<div>They've been helpful to me in the past even without an FCC
complaint, and one time even without being a customer (I kept
getting business advertisements at my house). You could
probably save some time by reaching out to them directly.</div>
<div><br>
</div>
<div>As a sidenote, I've usually been able to request a CDR via
the winning carrier and then build the ports based on the info
the losing carrier provided. But it sounds like you're past
those kinds of efforts at this point.</div>
<div><br>
</div>
<div>Best of luck,</div>
<div>Ross</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Jun 16, 2022 at 5:58
PM Shawn L <<a href="mailto:shawn@rmrf.us" target="_blank">shawn@rmrf.us</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">I just wanted to add (after I saw Aaron's
comment which got stuck in my spam) -- when you contact the
state Public Service Commission, the carrier jumps. When I
did it last, senior Spectrum management reached out to me
within a day or two and fixed the current issue, gave me
porting escalation contacts (which I already had and had
contacted) and wanted to do whatever it took to fix the
issue. Unfortunately, it didn't last. </div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Jun 16, 2022 at
5:41 PM Shawn L <<a href="mailto:shawn@rmrf.us" target="_blank">shawn@rmrf.us</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">Pretty much every time we port from
Spectrum (ie ~ 90%) I have to open a ticket with them
the next day to actually get the numbers removed from
their switch. They always port the number to our LRN,
but then no Spectrum customers can call it once that's
done. Even after Spectrum removes their CPE equipment,
they don't remove the numbers or routing and their
customers can't complete a call to the ported numbers.
Normally, I'd say it's their problem, but when the
company who just ported calls and says "I can't call my
office from my house, you need to fix it", I open a
ticket and 4-24 hours later they reply with a
resolution.
<div><br>
</div>
<div>Contacting the state PSC helped for a month or 2,
then they went back to their 'normal ways' and blame
it on staffing shortages.</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Jun 16, 2022
at 4:49 PM <<a href="mailto:adam@plexicomm.net" target="_blank">adam@plexicomm.net</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div>
<p class="MsoNormal">Comcast sounds scary. </p>
<p class="MsoNormal">I’ve worked with Verizon,
Time Warner, Frontier, and Spectrum. I think
the longest I spent on a port was 8 months. </p>
<p class="MsoNormal"> </p>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b> VoiceOps
<<a href="mailto:voiceops-bounces@voiceops.org" target="_blank">voiceops-bounces@voiceops.org</a>>
<b>On Behalf Of </b>Paul Timmins<br>
<b>Sent:</b> Thursday, June 16, 2022 4:39 PM<br>
<b>To:</b> <a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a><br>
<b>Subject:</b> Re: [VoiceOps] Comcast
rejecting port requests for 4 months</p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">Absolutely. The team that
does it is startek in the Philippines anyway
last I knew. They work on a different schedule
than the continental US, and aren't empowered
to solve most problems.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">If you think being
persistent matters, it doesn't. They won't
even let you get to a human to complain. The
PUC and FCC is the only thing they care about
because they don't want to get fined.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">To be fair, when their
process works, it works. When it breaks down,
there's no real way to work it out of process.
They're simply too big, and their roles too
bifurcated to actually let someone work
something they aren't typically able to
address.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">-Paul</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">On 6/16/22 16:33, Aaron de
Bruyn wrote:</p>
</div>
<blockquote style="margin-top:5pt;margin-bottom:5pt">
<div>
<div>
<p class="MsoNormal">Comcast flat-out won't
let customers talk to the team that
accepts or rejects ports.</p>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">-A</p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">On Thu Jun 16, 2022,
08:20 PM GMT, <a href="mailto:adam@plexicomm.net" target="_blank">adam@plexicomm.net</a>
wrote:</p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 4pt;margin-left:4pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">I try to get all
stake holders on a conference call.
New carrier, old carrier, you, and the
customer. </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">-Adam</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b>
VoiceOps <a href="mailto:voiceops-bounces@voiceops.org" target="_blank"></a><a href="mailto:voiceops-bounces@voiceops.org" target="_blank"><voiceops-bounces@voiceops.org></a>
<b>On Behalf Of </b>Aaron de
Bruyn<br>
<b>Sent:</b> Thursday, June 16,
2022 4:09 PM<br>
<b>To:</b> <a href="mailto:voiceops@voiceops.org" target="_blank"></a><a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a><br>
<b>Subject:</b> [VoiceOps] Comcast
rejecting port requests for 4
months</p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">Hey everyone,</p>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">We have a large
SIP trunk with Comcast with around
275 numbers attached.</p>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">We've been
trying to port about 200 of those
numbers to another provider for
the past 4 months to do some geeky
things that Comcast doesn't
support.</p>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">Due to reasons
only known to Comcast, there are 5
different account numbers vaguely
associated with those phone
numbers and I keep getting wildly
different answers from Comcast
staff.</p>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">One is for the
EDI circuit.</p>
</div>
<div>
<p class="MsoNormal">One is for the
AdTran.</p>
</div>
<div>
<p class="MsoNormal">One is for the
SIP Trunk</p>
</div>
<div>
<p class="MsoNormal">One is for
"master billing"</p>
</div>
<div>
<p class="MsoNormal">One is a
"hierarchy account"</p>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">The winning
carrier has submitted the requests
with every possible combination of
account number and 'CPNI code'
(Comcast's account PIN) we have
along with all our addressing
information, copies of bills,
etc...and Comcast keeps rejecting
it with zero useful information.
i.e. bad address, bad PIN, bad
account number, etc...</p>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">Every time I
even mention "porting out" to a
Comcast rep, they say "FCC
regulation prevents us from
talking about it".</p>
</div>
<div>
<p class="MsoNormal">The winning
carrier has had so much trouble,
they finally sent me the "port
order number" and said "call
Comcast and talk to them about it.
Good luck."</p>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">Of course
calling the Comcast porting number
gives you a short recorded message
about "due to COVID, use some
portal <i>click</i>".</p>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">I'm technically
a contractor for the end-user and
not a phone service provider, so I
don't have access to whatever
portal they are talking about.</p>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">It's been
absolute <i>hell</i>. Any
thoughts on how I can get Comcast
to get their crap together? I've
never had so much trouble porting
numbers away from a carrier.</p>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">-A</p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><br>
<br>
</p>
<pre>_______________________________________________</pre>
<pre>VoiceOps mailing list</pre>
<pre><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a></pre>
<pre><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></pre>
</blockquote>
<p> </p>
</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>
</blockquote>
</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>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
VoiceOps mailing list
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a>
</pre>
</blockquote>
<br>
</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>