VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- 14 participants
- 10512 messages
STIR for intra-net calls
by nathana@fsr.com
What's the consensus on signing calls that don't leave your own network? Are operators bothering with this, or generally only computing & attaching PASSporTs to calls that terminate off-net?
Thanks,
-- Nathan
June 27, 2022
anyone from charter ?
by igoldstein@telego.net
A supervisor reached out to me today,
He advised me that, with the new setup spectrum where a customers is
provided a 2 equipment solution when they have static IP,
1 modem, 1 router that handles the static IP
The static IP is only for incoming traffic
Outgoing traffic is seen as a DHCP assigned IP address
And this causes issues in SIP and with VPN?s
On Thu, Jun 23, 2022 at 17:37 Izzy Goldstein - TeleGo <igoldstein at telego.net>
wrote:
> Anyone from charter that can reach out to me? off list is ok
>
> i am facing an issue with VoIP/SIP
>
> pockets from my datacenter to a specific IP are not making it to the
> destination,
> 1 HOP before the Default gateway sends the packets to another destination
> perhaps ?
>
>
>
> --
>
> Izzy Goldstein
>
> Chief Technology Officer - DevOps Master
>
> Main: (212) 477-1000 x 2085 <(212)%20477-1000>
>
> Direct: (929) 477-2085
>
> Website: www.telego.com <http://www.telego.net/>
>
>
>
>
> Confidentiality Notice: This e-mail may contain confidential and/or
> privileged information. If you are not the intended recipient or have
> received this e-mail in error please notify us immediately by email reply
> and destroy this e-mail. Any unauthorized copying, disclosure or
> distribution of the material in this e-mail is strictly forbidden. Any
> views or opinions presented in this email are solely those of the author
> and do not necessarily represent those of TeleGo (T). Employees of TeleGo
> are expressly required not to make defamatory statements and not to
> infringe or authorize any infringement of copyright or any other legal
> right by email communications. Any such communication is contrary to TeleGo
> policy and outside the scope of the employment of the individual concerned.
> TeleGo will not accept any liability in respect of such communication, and
> the employee responsible will be personally liable for any damages or other
> liability arising.
>
>
> TeleGo Hosted PBX <https://youtu.be/DaT8YAZ4V0w>
>
--
Izzy Goldstein
Chief Technology Officer - DevOps Master
Main: (212) 477-1000 x 2085 <(212)%20477-1000>
Direct: (929) 477-2085
Website: https://telego.com/
Confidentiality Notice: This e-mail may contain confidential and/or
privileged information. If you are not the intended recipient or have
received this e-mail in error please notify us immediately by email reply
and destroy this e-mail. Any unauthorized copying, disclosure or
distribution of the material in this e-mail is strictly forbidden. Any
views or opinions presented in this email are solely those of the author
and do not necessarily represent those of TeleGo (T). Employees of TeleGo
are expressly required not to make defamatory statements and not to
infringe or authorize any infringement of copyright or any other legal
right by email communications. Any such communication is contrary to TeleGo
policy and outside the scope of the employment of the individual concerned.
TeleGo will not accept any liability in respect of such communication, and
the employee responsible will be personally liable for any damages or other
liability arising.
TeleGo Hosted PBX <https://youtu.be/DaT8YAZ4V0w>
June 27, 2022
anyone from charter ?
by mark.wiater@greybeam.com
We have had great success using TLS to bypass Spectrum silliness
On 6/23/2022 5:37 PM, Izzy Goldstein - TeleGo wrote:
> Anyone from charter that can reach out to me? off list is ok
>
> i am facing an issue with VoIP/SIP
>
> pockets?from my datacenter to a specific IP are not making it to the
> destination,
> 1 HOP before the Default gateway sends the packets to
> another?destination perhaps ?
>
June 23, 2022
anyone from charter ?
by igoldstein@telego.net
Anyone from charter that can reach out to me? off list is ok
i am facing an issue with VoIP/SIP
pockets from my datacenter to a specific IP are not making it to the
destination,
1 HOP before the Default gateway sends the packets to another destination
perhaps ?
--
Izzy Goldstein
Chief Technology Officer - DevOps Master
Main: (212) 477-1000 x 2085 <(212)%20477-1000>
Direct: (929) 477-2085
Website: www.telego.com <http://www.telego.net/>
Confidentiality Notice: This e-mail may contain confidential and/or
privileged information. If you are not the intended recipient or have
received this e-mail in error please notify us immediately by email reply
and destroy this e-mail. Any unauthorized copying, disclosure or
distribution of the material in this e-mail is strictly forbidden. Any
views or opinions presented in this email are solely those of the author
and do not necessarily represent those of TeleGo (T). Employees of TeleGo
are expressly required not to make defamatory statements and not to
infringe or authorize any infringement of copyright or any other legal
right by email communications. Any such communication is contrary to TeleGo
policy and outside the scope of the employment of the individual concerned.
TeleGo will not accept any liability in respect of such communication, and
the employee responsible will be personally liable for any damages or other
liability arising.
TeleGo Hosted PBX <https://youtu.be/DaT8YAZ4V0w>
June 23, 2022
Devices that may violate NDAA
by peeip989@gmail.com
*' Sec. 889(a)(1)(A) required the federal government, as of August 13,
2019, to not ?procure or obtain or extend or renew a contract to procure or
obtain any equipment, system, or service that uses covered
telecommunication equipment or services as a substantial or essential
component of any system, or as critical technology as part of any
system.?' *
I am curious how you're handling CPE (i.e. handsets), for which you are
responsible, that are already in the field that is from, *or contain
components* (more pertinent to our situation) of the prohibited
manufacturers (Huawei, ZTE, Hytera, Hikvision, and Dahua).
Are you notifying customers? Replacing or recommending replacement?
Handling differently for private enterprise than for the government?
Thanks,
Pete
June 22, 2022
Peerless issues this morning
by dovid@telecurve.com
Anyone having issues with SIP traffic to Peerless? We had an issue where it
seems that they were not getting any of our 200 OK', ACK's etc. With most
of our ISP's the packets were not flowing. With one smaller upstream
carrier which uses L3 upstream it is working. Peerless NOC answered and
told me they had a network issue in Chicago and that's about it.
June 20, 2022
Comcast rejecting port requests for 4 months
by ross@tajvar.io
Ah, didn't know that. Well, with any luck those guys still work there, just
in a different physical location.
On Thu, Jun 16, 2022 at 6:30 PM Nate Burke <nate at blastcomm.com> wrote:
> Not sure about the people, but I live in Naperville, and Comcast has left
> that building (all their signage is down)
>
> On 6/16/2022 5:21 PM, Ross Tajvar wrote:
>
> At Comcast, when you file an FCC complaint, it goes to these people (as of
> a couple years ago, might be different people now):
>
> William Landis | Engineer 3, Business Escalations
> 1415 West Diehl Road, Naperville, IL 60563
> Office: (331) 814-3041
> william_landis at comcast.com
>
> his boss:
> Jeff Cox | Manager, Business Escalations
> Operations
> 1415 West Diehl Road, Naperville, IL 60563
> Office: (331) 401-5525
> jeffery_cox at comcast.com
>
>
> 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.
>
> 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.
>
> Best of luck,
> Ross
>
> On Thu, Jun 16, 2022 at 5:58 PM Shawn L <shawn at rmrf.us> wrote:
>
>> 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.
>>
>> On Thu, Jun 16, 2022 at 5:41 PM Shawn L <shawn at rmrf.us> wrote:
>>
>>> 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.
>>>
>>> Contacting the state PSC helped for a month or 2, then they went back to
>>> their 'normal ways' and blame it on staffing shortages.
>>>
>>>
>>> On Thu, Jun 16, 2022 at 4:49 PM <adam at plexicomm.net> wrote:
>>>
>>>> Comcast sounds scary.
>>>>
>>>> I?ve worked with Verizon, Time Warner, Frontier, and Spectrum. I think
>>>> the longest I spent on a port was 8 months.
>>>>
>>>>
>>>>
>>>> *From:* VoiceOps <voiceops-bounces at voiceops.org> *On Behalf Of *Paul
>>>> Timmins
>>>> *Sent:* Thursday, June 16, 2022 4:39 PM
>>>> *To:* voiceops at voiceops.org
>>>> *Subject:* Re: [VoiceOps] Comcast rejecting port requests for 4 months
>>>>
>>>>
>>>>
>>>> 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.
>>>>
>>>>
>>>>
>>>> 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.
>>>>
>>>>
>>>>
>>>> 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.
>>>>
>>>>
>>>>
>>>> -Paul
>>>>
>>>>
>>>>
>>>> On 6/16/22 16:33, Aaron de Bruyn wrote:
>>>>
>>>> Comcast flat-out won't let customers talk to the team that accepts or
>>>> rejects ports.
>>>>
>>>>
>>>>
>>>> -A
>>>>
>>>>
>>>>
>>>> On Thu Jun 16, 2022, 08:20 PM GMT, adam at plexicomm.net wrote:
>>>>
>>>> I try to get all stake holders on a conference call. New carrier, old
>>>> carrier, you, and the customer.
>>>>
>>>>
>>>>
>>>> -Adam
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *From:* VoiceOps <voiceops-bounces at voiceops.org>
>>>> <voiceops-bounces at voiceops.org> <voiceops-bounces at voiceops.org> *On
>>>> Behalf Of *Aaron de Bruyn
>>>> *Sent:* Thursday, June 16, 2022 4:09 PM
>>>> *To:* <voiceops at voiceops.org>voiceops at voiceops.org
>>>> *Subject:* [VoiceOps] Comcast rejecting port requests for 4 months
>>>>
>>>>
>>>>
>>>> Hey everyone,
>>>>
>>>>
>>>>
>>>> We have a large SIP trunk with Comcast with around 275 numbers attached.
>>>>
>>>>
>>>>
>>>> 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.
>>>>
>>>>
>>>>
>>>> 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.
>>>>
>>>>
>>>>
>>>> One is for the EDI circuit.
>>>>
>>>> One is for the AdTran.
>>>>
>>>> One is for the SIP Trunk
>>>>
>>>> One is for "master billing"
>>>>
>>>> One is a "hierarchy account"
>>>>
>>>>
>>>>
>>>> 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...
>>>>
>>>>
>>>>
>>>> Every time I even mention "porting out" to a Comcast rep, they say "FCC
>>>> regulation prevents us from talking about it".
>>>>
>>>> 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."
>>>>
>>>>
>>>>
>>>> Of course calling the Comcast porting number gives you a short recorded
>>>> message about "due to COVID, use some portal *click*".
>>>>
>>>>
>>>>
>>>> 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.
>>>>
>>>>
>>>>
>>>> It's been absolute *hell*. 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.
>>>>
>>>>
>>>>
>>>> -A
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>>
>>>> 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
>>>>
>>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>
>
> _______________________________________________
> VoiceOps mailing listVoiceOps at voiceops.orghttps://puck.nether.net/mailman/listinfo/voiceops
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
June 16, 2022
Comcast rejecting port requests for 4 months
by nate@blastcomm.com
Not sure about the people, but I live in Naperville, and Comcast has
left that building (all their signage is down)
On 6/16/2022 5:21 PM, Ross Tajvar wrote:
> At Comcast, when you file an FCC complaint, it goes to these people
> (as of a couple years ago, might be different people now):
>
> William Landis | Engineer 3, Business Escalations
> 1415 West Diehl Road, Naperville, IL 60563
> Office: (331) 814-3041
> william_landis at comcast.com <mailto:william_landis at comcast.com>
>
> his boss:
> Jeff Cox | Manager, Business Escalations
> Operations
> 1415 West Diehl Road, Naperville, IL 60563
> Office: (331) 401-5525
> jeffery_cox at comcast.com <mailto:jeffery_cox at comcast.com>
>
>
> 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.
>
> 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.
>
> Best of luck,
> Ross
>
> On Thu, Jun 16, 2022 at 5:58 PM Shawn L <shawn at rmrf.us
> <mailto:shawn at rmrf.us>> wrote:
>
> 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.
>
> On Thu, Jun 16, 2022 at 5:41 PM Shawn L <shawn at rmrf.us
> <mailto:shawn at rmrf.us>> wrote:
>
> 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.
>
> Contacting the state PSC helped for a month or 2, then they
> went back to their 'normal ways' and blame it on staffing
> shortages.
>
>
> On Thu, Jun 16, 2022 at 4:49 PM <adam at plexicomm.net
> <mailto:adam at plexicomm.net>> wrote:
>
> Comcast sounds scary.
>
> I?ve worked with Verizon, Time Warner, Frontier, and
> Spectrum. I think the longest I spent on a port was 8
> months.
>
> *From:* VoiceOps <voiceops-bounces at voiceops.org
> <mailto:voiceops-bounces at voiceops.org>> *On Behalf Of
> *Paul Timmins
> *Sent:* Thursday, June 16, 2022 4:39 PM
> *To:* voiceops at voiceops.org <mailto:voiceops at voiceops.org>
> *Subject:* Re: [VoiceOps] Comcast rejecting port requests
> for 4 months
>
> 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.
>
> 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.
>
> 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.
>
> -Paul
>
> On 6/16/22 16:33, Aaron de Bruyn wrote:
>
> Comcast flat-out won't let customers talk to the team
> that accepts or rejects ports.
>
> -A
>
> On Thu Jun 16, 2022, 08:20 PM GMT, adam at plexicomm.net
> <mailto:adam at plexicomm.net> wrote:
>
> I try to get all stake holders on a conference
> call. New carrier, old carrier, you, and the
> customer.
>
> -Adam
>
> *From:* VoiceOps <voiceops-bounces at voiceops.org>
> <mailto:voiceops-bounces at voiceops.org> *On Behalf
> Of *Aaron de Bruyn
> *Sent:* Thursday, June 16, 2022 4:09 PM
> *To:* voiceops at voiceops.org
> <mailto:voiceops at voiceops.org>
> *Subject:* [VoiceOps] Comcast rejecting port
> requests for 4 months
>
> Hey everyone,
>
> We have a large SIP trunk with Comcast with around
> 275 numbers attached.
>
> 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.
>
> 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.
>
> One is for the EDI circuit.
>
> One is for the AdTran.
>
> One is for the SIP Trunk
>
> One is for "master billing"
>
> One is a "hierarchy account"
>
> 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...
>
> Every time I even mention "porting out" to a
> Comcast rep, they say "FCC regulation prevents us
> from talking about it".
>
> 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."
>
> Of course calling the Comcast porting number gives
> you a short recorded message about "due to COVID,
> use some portal /click/".
>
> 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.
>
> It's been absolute /hell/. 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.
>
> -A
>
>
>
> _______________________________________________
>
> VoiceOps mailing list
>
> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
>
> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org <mailto: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
June 16, 2022
Comcast rejecting port requests for 4 months
by ross@tajvar.io
At Comcast, when you file an FCC complaint, it goes to these people (as of
a couple years ago, might be different people now):
William Landis | Engineer 3, Business Escalations
1415 West Diehl Road, Naperville, IL 60563
Office: (331) 814-3041
william_landis at comcast.com
his boss:
Jeff Cox | Manager, Business Escalations
Operations
1415 West Diehl Road, Naperville, IL 60563
Office: (331) 401-5525
jeffery_cox at comcast.com
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.
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.
Best of luck,
Ross
On Thu, Jun 16, 2022 at 5:58 PM Shawn L <shawn at rmrf.us> wrote:
> 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.
>
> On Thu, Jun 16, 2022 at 5:41 PM Shawn L <shawn at rmrf.us> wrote:
>
>> 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.
>>
>> Contacting the state PSC helped for a month or 2, then they went back to
>> their 'normal ways' and blame it on staffing shortages.
>>
>>
>> On Thu, Jun 16, 2022 at 4:49 PM <adam at plexicomm.net> wrote:
>>
>>> Comcast sounds scary.
>>>
>>> I?ve worked with Verizon, Time Warner, Frontier, and Spectrum. I think
>>> the longest I spent on a port was 8 months.
>>>
>>>
>>>
>>> *From:* VoiceOps <voiceops-bounces at voiceops.org> *On Behalf Of *Paul
>>> Timmins
>>> *Sent:* Thursday, June 16, 2022 4:39 PM
>>> *To:* voiceops at voiceops.org
>>> *Subject:* Re: [VoiceOps] Comcast rejecting port requests for 4 months
>>>
>>>
>>>
>>> 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.
>>>
>>>
>>>
>>> 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.
>>>
>>>
>>>
>>> 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.
>>>
>>>
>>>
>>> -Paul
>>>
>>>
>>>
>>> On 6/16/22 16:33, Aaron de Bruyn wrote:
>>>
>>> Comcast flat-out won't let customers talk to the team that accepts or
>>> rejects ports.
>>>
>>>
>>>
>>> -A
>>>
>>>
>>>
>>> On Thu Jun 16, 2022, 08:20 PM GMT, adam at plexicomm.net wrote:
>>>
>>> I try to get all stake holders on a conference call. New carrier, old
>>> carrier, you, and the customer.
>>>
>>>
>>>
>>> -Adam
>>>
>>>
>>>
>>>
>>>
>>> *From:* VoiceOps <voiceops-bounces at voiceops.org>
>>> <voiceops-bounces at voiceops.org> *On Behalf Of *Aaron de Bruyn
>>> *Sent:* Thursday, June 16, 2022 4:09 PM
>>> *To:* voiceops at voiceops.org
>>> *Subject:* [VoiceOps] Comcast rejecting port requests for 4 months
>>>
>>>
>>>
>>> Hey everyone,
>>>
>>>
>>>
>>> We have a large SIP trunk with Comcast with around 275 numbers attached.
>>>
>>>
>>>
>>> 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.
>>>
>>>
>>>
>>> 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.
>>>
>>>
>>>
>>> One is for the EDI circuit.
>>>
>>> One is for the AdTran.
>>>
>>> One is for the SIP Trunk
>>>
>>> One is for "master billing"
>>>
>>> One is a "hierarchy account"
>>>
>>>
>>>
>>> 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...
>>>
>>>
>>>
>>> Every time I even mention "porting out" to a Comcast rep, they say "FCC
>>> regulation prevents us from talking about it".
>>>
>>> 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."
>>>
>>>
>>>
>>> Of course calling the Comcast porting number gives you a short recorded
>>> message about "due to COVID, use some portal *click*".
>>>
>>>
>>>
>>> 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.
>>>
>>>
>>>
>>> It's been absolute *hell*. 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.
>>>
>>>
>>>
>>> -A
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> 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
>>>
>> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
June 16, 2022
Comcast rejecting port requests for 4 months
by shawn@rmrf.us
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.
On Thu, Jun 16, 2022 at 5:41 PM Shawn L <shawn at rmrf.us> wrote:
> 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.
>
> Contacting the state PSC helped for a month or 2, then they went back to
> their 'normal ways' and blame it on staffing shortages.
>
>
> On Thu, Jun 16, 2022 at 4:49 PM <adam at plexicomm.net> wrote:
>
>> Comcast sounds scary.
>>
>> I?ve worked with Verizon, Time Warner, Frontier, and Spectrum. I think
>> the longest I spent on a port was 8 months.
>>
>>
>>
>> *From:* VoiceOps <voiceops-bounces at voiceops.org> *On Behalf Of *Paul
>> Timmins
>> *Sent:* Thursday, June 16, 2022 4:39 PM
>> *To:* voiceops at voiceops.org
>> *Subject:* Re: [VoiceOps] Comcast rejecting port requests for 4 months
>>
>>
>>
>> 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.
>>
>>
>>
>> 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.
>>
>>
>>
>> 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.
>>
>>
>>
>> -Paul
>>
>>
>>
>> On 6/16/22 16:33, Aaron de Bruyn wrote:
>>
>> Comcast flat-out won't let customers talk to the team that accepts or
>> rejects ports.
>>
>>
>>
>> -A
>>
>>
>>
>> On Thu Jun 16, 2022, 08:20 PM GMT, adam at plexicomm.net wrote:
>>
>> I try to get all stake holders on a conference call. New carrier, old
>> carrier, you, and the customer.
>>
>>
>>
>> -Adam
>>
>>
>>
>>
>>
>> *From:* VoiceOps <voiceops-bounces at voiceops.org>
>> <voiceops-bounces at voiceops.org> *On Behalf Of *Aaron de Bruyn
>> *Sent:* Thursday, June 16, 2022 4:09 PM
>> *To:* voiceops at voiceops.org
>> *Subject:* [VoiceOps] Comcast rejecting port requests for 4 months
>>
>>
>>
>> Hey everyone,
>>
>>
>>
>> We have a large SIP trunk with Comcast with around 275 numbers attached.
>>
>>
>>
>> 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.
>>
>>
>>
>> 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.
>>
>>
>>
>> One is for the EDI circuit.
>>
>> One is for the AdTran.
>>
>> One is for the SIP Trunk
>>
>> One is for "master billing"
>>
>> One is a "hierarchy account"
>>
>>
>>
>> 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...
>>
>>
>>
>> Every time I even mention "porting out" to a Comcast rep, they say "FCC
>> regulation prevents us from talking about it".
>>
>> 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."
>>
>>
>>
>> Of course calling the Comcast porting number gives you a short recorded
>> message about "due to COVID, use some portal *click*".
>>
>>
>>
>> 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.
>>
>>
>>
>> It's been absolute *hell*. 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.
>>
>>
>>
>> -A
>>
>>
>>
>> _______________________________________________
>>
>> 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
>>
>
June 16, 2022