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
Misrouting 911 Calls?
by aaron@heyaaron.com
In my case, I doubt it. I'm not a phone company or VoIP provider.
I was simply called in to help them with their existing VoIP server (among
other things).
-A
On Sun, Jan 9, 2022 at 7:47 AM Mike Hammett <voiceops at ics-il.net> wrote:
> Are you potentially underestimating what you're required to do for 911?
>
>
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
>
>
> Midwest Internet Exchange
> http://www.midwest-ix.com
>
>
>
> ------------------------------
> *From: *"Aaron C. de Bruyn via VoiceOps" <voiceops at voiceops.org>
> *To: *"Mary Lou Carey" <marylou at backuptelecom.com>
> *Cc: *voiceops at voiceops.org
> *Sent: *Saturday, January 8, 2022 5:11:36 PM
> *Subject: *Re: [VoiceOps] Misrouting 911 Calls?
>
> I filed a complaint with the FCC about a year ago.
> The FCC reached out to Comcast and Comcast reached back out to me.
> Their response was that we would basically have to purchase ~200 numbers
> (one for each extension on our system), set our outbound 911 caller ID to
> those numbers, and then provide Comcast with a list of mappings between
> phone numbers and addresses.
> It would have added a huge tracking burden for IT as well as increased our
> bill by about $2,500 over the contract term.
>
> It's all moot now as BulkVS cost less than $50 to set up, we've already
> had one successful 911 call from an office that was continually misrouted
> by Comcast, and the contract is up "soon".
>
> -A
>
> On Sat, Jan 8, 2022 at 2:37 PM Mary Lou Carey <marylou at backuptelecom.com>
> wrote:
>
>> I was just going to say the same thing. If you give Comcast or any
>> carrier a chance to fix it and they can't/won't/don't, then you have to
>> escalate it above their heads.
>>
>> The 911 network has always operated separately from the PSTN world for a
>> reason. That's because misroutes can result in people dying! Carriers
>> can get in HUGE trouble if they don't address routing issues immediately
>> and VOIP carriers can also get in trouble if they don't allow the
>> customer a method of updating their location themselves.
>>
>>
>> MARY LOU CAREY
>> BackUP Telecom Consulting
>> Office: 615-791-9969
>> Cell: 615-796-1111
>>
>> On 2022-01-05 09:08 AM, Mike Hammett wrote:
>> > Escalate to the PUC and ETSBs.
>> >
>> > Unfortunately, with companies like that, honey doesn't work. You need
>> > vinegar.
>> >
>> > -----
>> > Mike Hammett
>> > Intelligent Computing Solutions
>> > http://www.ics-il.com
>> >
>> > Midwest Internet Exchange
>> > http://www.midwest-ix.com
>> >
>> > -------------------------
>> >
>> > From: "Aaron C. de Bruyn via VoiceOps" <voiceops at voiceops.org>
>> > To: "Paul Timmins" <paul at timmins.net>
>> > Cc: voiceops at voiceops.org
>> > Sent: Tuesday, January 4, 2022 6:07:52 PM
>> > Subject: Re: [VoiceOps] Misrouting 911 Calls?
>> >
>> > When I handed Comcast a list of phone numbers years ago, they said
>> > there would be no problem porting them over or using them.
>> > That was it.
>> >
>> > Then after the service was installed, someone mentioned "a few of the
>> > numbers will be RCF'd", but we wouldn't have a problem using them.
>> >
>> > Then 3 months into using the service (after our cancellation period
>> > expired and we were locked-in), we suddenly started having problems
>> > with the RCF'd numbers being re-written.
>> >
>> > No less than 30 calls to Comcast over the years has resulted in widely
>> > different responses including:
>> > * Ok, we just changed an option in the AdTran to allow you to specify
>> > your own caller ID, everything should work now (it doesn't)
>> > * Give us a list of phone numbers and associated addresses so we can
>> > update our e911 information (they respond with "done!", not "we can't
>> > set e911 for phone number xxx-yyy-zzzz)
>> > * I'm going to escalate this (followed by nothing happening and the
>> > case gets magically closed)
>> >
>> > After talking with Comcast this morning, I had a rep send me what they
>> > had listed for addresses associated with phone numbers...and
>> > unsurprisingly found that they had reset everything to the address of
>> > our SIP trunk service. None of our offices have valid 911 contact
>> > info.
>> >
>> > They're allegedly in the middle of updating the list again, but I'm
>> > not holding my breath.
>> >
>> > It's Comcast's job to provide phone service and 911 routing for this
>> > client. They shouldn't be re-writing anything. They weren't in the
>> > beginning, but I'm guessing it has to do with STIR/SHAKEN. I'm
>> > vaguely familiar with it, but I'm not a telco or a phone service
>> > provider. Just someone they hired to clean up their FreePBX phone
>> > mess. ;)
>> >
>> > -A
>> >
>> > On Tue, Jan 4, 2022 at 3:01 PM Paul Timmins <paul at timmins.net> wrote:
>> >
>> >> I'm going to be the unpopular one here, and point out that Comcast
>> >> is not really responsible to route 911 calls for you when you use
>> >> numbers that they don't provide. For the cost of an hour of an
>> >> attorney's time, you could just set up trunking to basically anyone
>> >> else to handle those offnet/off circuit numbers and the 911 routing
>> >> for those numbers.
>> >>
>> >> On 1/4/22 1:30 PM, Aaron C. de Bruyn via VoiceOps wrote:
>> >>
>> >>> One of my clients has a large SIP trunk with Comcast based out of
>> >>> Washington State.
>> >>>
>> >>> They have all their offices across Oregon and Washington hooked
>> >>> into a FreePBX phone server that is attached to the Comcast SIP
>> >>> trunk.
>> >>>
>> >>> 911 calls *constantly* get misrouted to the local PSAP where the
>> >>> SIP trunk lives.
>> >>>
>> >>> I must have called Comcast 30 times over the last few years to try
>> >>> and get this addressed, but Comcast flat-out refuses to fix the
>> >>> issue.
>> >>>
>> >>> The short answer is that Comcast refuses to fix it. In some (but
>> >>> not all) cases, our phone numbers are RCF'd numbers, so they don't
>> >>> actually exist on the trunk...and Comcast forcibly re-writes them
>> >>> to our 'main' number...and then routes the 911 call incorrectly.
>> >>> In other cases, we have provided Comcast with the e911
>> >>> information, they say it's updated, and then we find out months
>> >>> later (when an office dials 911 during an emergency) that it's
>> >>> still not correct.
>> >>>
>> >>> Not only does this affect 911 calls, but also customers who get
>> >>> the re-written caller ID and have no idea which office called
>> >>> them.
>> >>>
>> >>> The "easy" solution is to ditch Comcast and move to a provider
>> >>> that doesn't play the RCF and caller-ID-rewrite games.
>> >>> Unfortunately my client is locked into their Comcast contract for
>> >>> another ~18 months. Early termination would incur a ~$35,000
>> >>> bill.
>> >>>
>> >>> Is there a list of PSAP numbers somewhere so I can set up an
>> >>> internal redirect to the PSAP 10-digit number? I know those
>> >>> 10-digit numbers are guarded like Fort Knox, so I'm betting this
>> >>> option isn't very realistic.
>> >>>
>> >>> Maybe a separate service provider that can just handle 911 calls
>> >>> without "owning" my client's phone numbers?
>> >>>
>> >>> Any other thoughts on how I can route around Comcast brain damage?
>> >>>
>> >>> Thanks,
>> >>>
>> >>> -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 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
>
>
Jan. 10, 2022
Misrouting 911 Calls?
by aaron@heyaaron.com
On Sat, Jan 8, 2022 at 5:21 PM Mary Lou Carey <marylou at backuptelecom.com>
wrote:
> You shouldn't have needed a number for each extension. You can just
> associate each extension with a dedicated TN for that particular
> building. Any call that comes from that building would be routed to the
> same PSAP. You'd just want to provide the main desk in each building
> with the physical location of each TN within the building so when help
> arrives they know where to go.
>
Yup. That was Comcast's response to the FCC though.
> What you're describing is actually 2 different issues. The contract
> being up may fix the problem of getting the call to the correct PSAP,
> but it may not fix your address problem. If the location is routed to
> the right PSAP but identifies the wrong building in that PSAP area it's
> still an issue. My guess would be that Comcast had problems getting your
> addresses to validate in the ALI database so they listed the address
> associated with your SIP trunks instead because the system took that.
> What clients may not be aware of is that the address in the ALI database
> (used to identify locations for 911) doesn't always match the address
> that the customer was given by USPS.
>
I have a portal that I use for tracking my clients addresses. It has a
'street number' field, 'street name', and 'additional address info' field
(along with city, state, zip).
They basically get concatenated together to come up with the address.
Those fields also generate my e911 list that I hand to Comcast. I used the
same fields to programatically create the BulkVS 911 list. BulkVS had zero
problems validating every single address I threw at it. ;)
-A
Jan. 10, 2022
Misrouting 911 Calls?
by voiceops@ics-il.net
Are you potentially underestimating what you're required to do for 911?
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
----- Original Message -----
From: "Aaron C. de Bruyn via VoiceOps" <voiceops at voiceops.org>
To: "Mary Lou Carey" <marylou at backuptelecom.com>
Cc: voiceops at voiceops.org
Sent: Saturday, January 8, 2022 5:11:36 PM
Subject: Re: [VoiceOps] Misrouting 911 Calls?
I filed a complaint with the FCC about a year ago.
The FCC reached out to Comcast and Comcast reached back out to me.
Their response was that we would basically have to purchase ~200 numbers (one for each extension on our system), set our outbound 911 caller ID to those numbers, and then provide Comcast with a list of mappings between phone numbers and addresses.
It would have added a huge tracking burden for IT as well as increased our bill by about $2,500 over the contract term.
It's all moot now as BulkVS cost less than $50 to set up, we've already had one successful 911 call from an office that was continually misrouted by Comcast, and the contract is up "soon".
-A
On Sat, Jan 8, 2022 at 2:37 PM Mary Lou Carey < marylou at backuptelecom.com > wrote:
I was just going to say the same thing. If you give Comcast or any
carrier a chance to fix it and they can't/won't/don't, then you have to
escalate it above their heads.
The 911 network has always operated separately from the PSTN world for a
reason. That's because misroutes can result in people dying! Carriers
can get in HUGE trouble if they don't address routing issues immediately
and VOIP carriers can also get in trouble if they don't allow the
customer a method of updating their location themselves.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2022-01-05 09:08 AM, Mike Hammett wrote:
> Escalate to the PUC and ETSBs.
>
> Unfortunately, with companies like that, honey doesn't work. You need
> vinegar.
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
> Midwest Internet Exchange
> http://www.midwest-ix.com
>
> -------------------------
>
> From: "Aaron C. de Bruyn via VoiceOps" < voiceops at voiceops.org >
> To: "Paul Timmins" < paul at timmins.net >
> Cc: voiceops at voiceops.org
> Sent: Tuesday, January 4, 2022 6:07:52 PM
> Subject: Re: [VoiceOps] Misrouting 911 Calls?
>
> When I handed Comcast a list of phone numbers years ago, they said
> there would be no problem porting them over or using them.
> That was it.
>
> Then after the service was installed, someone mentioned "a few of the
> numbers will be RCF'd", but we wouldn't have a problem using them.
>
> Then 3 months into using the service (after our cancellation period
> expired and we were locked-in), we suddenly started having problems
> with the RCF'd numbers being re-written.
>
> No less than 30 calls to Comcast over the years has resulted in widely
> different responses including:
> * Ok, we just changed an option in the AdTran to allow you to specify
> your own caller ID, everything should work now (it doesn't)
> * Give us a list of phone numbers and associated addresses so we can
> update our e911 information (they respond with "done!", not "we can't
> set e911 for phone number xxx-yyy-zzzz)
> * I'm going to escalate this (followed by nothing happening and the
> case gets magically closed)
>
> After talking with Comcast this morning, I had a rep send me what they
> had listed for addresses associated with phone numbers...and
> unsurprisingly found that they had reset everything to the address of
> our SIP trunk service. None of our offices have valid 911 contact
> info.
>
> They're allegedly in the middle of updating the list again, but I'm
> not holding my breath.
>
> It's Comcast's job to provide phone service and 911 routing for this
> client. They shouldn't be re-writing anything. They weren't in the
> beginning, but I'm guessing it has to do with STIR/SHAKEN. I'm
> vaguely familiar with it, but I'm not a telco or a phone service
> provider. Just someone they hired to clean up their FreePBX phone
> mess. ;)
>
> -A
>
> On Tue, Jan 4, 2022 at 3:01 PM Paul Timmins < paul at timmins.net > wrote:
>
>> I'm going to be the unpopular one here, and point out that Comcast
>> is not really responsible to route 911 calls for you when you use
>> numbers that they don't provide. For the cost of an hour of an
>> attorney's time, you could just set up trunking to basically anyone
>> else to handle those offnet/off circuit numbers and the 911 routing
>> for those numbers.
>>
>> On 1/4/22 1:30 PM, Aaron C. de Bruyn via VoiceOps wrote:
>>
>>> One of my clients has a large SIP trunk with Comcast based out of
>>> Washington State.
>>>
>>> They have all their offices across Oregon and Washington hooked
>>> into a FreePBX phone server that is attached to the Comcast SIP
>>> trunk.
>>>
>>> 911 calls *constantly* get misrouted to the local PSAP where the
>>> SIP trunk lives.
>>>
>>> I must have called Comcast 30 times over the last few years to try
>>> and get this addressed, but Comcast flat-out refuses to fix the
>>> issue.
>>>
>>> The short answer is that Comcast refuses to fix it. In some (but
>>> not all) cases, our phone numbers are RCF'd numbers, so they don't
>>> actually exist on the trunk...and Comcast forcibly re-writes them
>>> to our 'main' number...and then routes the 911 call incorrectly.
>>> In other cases, we have provided Comcast with the e911
>>> information, they say it's updated, and then we find out months
>>> later (when an office dials 911 during an emergency) that it's
>>> still not correct.
>>>
>>> Not only does this affect 911 calls, but also customers who get
>>> the re-written caller ID and have no idea which office called
>>> them.
>>>
>>> The "easy" solution is to ditch Comcast and move to a provider
>>> that doesn't play the RCF and caller-ID-rewrite games.
>>> Unfortunately my client is locked into their Comcast contract for
>>> another ~18 months. Early termination would incur a ~$35,000
>>> bill.
>>>
>>> Is there a list of PSAP numbers somewhere so I can set up an
>>> internal redirect to the PSAP 10-digit number? I know those
>>> 10-digit numbers are guarded like Fort Knox, so I'm betting this
>>> option isn't very realistic.
>>>
>>> Maybe a separate service provider that can just handle 911 calls
>>> without "owning" my client's phone numbers?
>>>
>>> Any other thoughts on how I can route around Comcast brain damage?
>>>
>>> Thanks,
>>>
>>> -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 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
Jan. 9, 2022
Misrouting 911 Calls?
by marylou@backuptelecom.com
You shouldn't have needed a number for each extension. You can just
associate each extension with a dedicated TN for that particular
building. Any call that comes from that building would be routed to the
same PSAP. You'd just want to provide the main desk in each building
with the physical location of each TN within the building so when help
arrives they know where to go.
What you're describing is actually 2 different issues. The contract
being up may fix the problem of getting the call to the correct PSAP,
but it may not fix your address problem. If the location is routed to
the right PSAP but identifies the wrong building in that PSAP area it's
still an issue. My guess would be that Comcast had problems getting your
addresses to validate in the ALI database so they listed the address
associated with your SIP trunks instead because the system took that.
What clients may not be aware of is that the address in the ALI database
(used to identify locations for 911) doesn't always match the address
that the customer was given by USPS.
The ALI database gets its address options from the MSAG database. The
MSAG uses whatever the original carrier assigned. If the customer writes
their address as 123 Main Street, but the MSAG lists it as 123 Main St,
the address won't validate. It has to match EXACTLY! There are also many
instances where the street name or abbreviation for the city may be
different. For example, in my area you can take 50 mile stretch of road
that goes from Columbia TN all the way up to Nashville. In Columbia they
call it Nashville Highway. In Spring Hill they call it Main Street. In
Franklin they call it Columbia Ave, and in Nashville they call it
Highway 31. Just because the Post Office assigned someone's address as
Nashville Highway doesn't mean the phone company used the same address.
They may have listed it as Nashville Highway /Columbia Ave and if you
don't type it exactly that way, your address won't validate. If your
address doesn't validate, then you get fined! So even though carriers
are supposed to give their customers a way to update their address, they
don't want to give them direct access because the address the customer
thinks they have may not be the address in the ALI database.
Its crazy that anyone gets the service they need when something as
simple as an address is SO messed up!
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2022-01-08 05:11 PM, Aaron C. de Bruyn wrote:
> I filed a complaint with the FCC about a year ago.
> The FCC reached out to Comcast and Comcast reached back out to me.
> Their response was that we would basically have to purchase ~200
> numbers (one for each extension on our system), set our outbound 911
> caller ID to those numbers, and then provide Comcast with a list of
> mappings between phone numbers and addresses.
> It would have added a huge tracking burden for IT as well as increased
> our bill by about $2,500 over the contract term.
>
> It's all moot now as BulkVS cost less than $50 to set up, we've
> already had one successful 911 call from an office that was
> continually misrouted by Comcast, and the contract is up "soon".
>
> -A
>
> On Sat, Jan 8, 2022 at 2:37 PM Mary Lou Carey
> <marylou at backuptelecom.com> wrote:
>
>> I was just going to say the same thing. If you give Comcast or any
>> carrier a chance to fix it and they can't/won't/don't, then you have
>> to
>> escalate it above their heads.
>>
>> The 911 network has always operated separately from the PSTN world
>> for a
>> reason. That's because misroutes can result in people dying!
>> Carriers
>> can get in HUGE trouble if they don't address routing issues
>> immediately
>> and VOIP carriers can also get in trouble if they don't allow the
>> customer a method of updating their location themselves.
>>
>> MARY LOU CAREY
>> BackUP Telecom Consulting
>> Office: 615-791-9969
>> Cell: 615-796-1111
>>
>> On 2022-01-05 09:08 AM, Mike Hammett wrote:
>>> Escalate to the PUC and ETSBs.
>>>
>>> Unfortunately, with companies like that, honey doesn't work. You
>> need
>>> vinegar.
>>>
>>> -----
>>> Mike Hammett
>>> Intelligent Computing Solutions
>>> http://www.ics-il.com
>>>
>>> Midwest Internet Exchange
>>> http://www.midwest-ix.com
>>>
>>> -------------------------
>>>
>>> From: "Aaron C. de Bruyn via VoiceOps" <voiceops at voiceops.org>
>>> To: "Paul Timmins" <paul at timmins.net>
>>> Cc: voiceops at voiceops.org
>>> Sent: Tuesday, January 4, 2022 6:07:52 PM
>>> Subject: Re: [VoiceOps] Misrouting 911 Calls?
>>>
>>> When I handed Comcast a list of phone numbers years ago, they said
>>> there would be no problem porting them over or using them.
>>> That was it.
>>>
>>> Then after the service was installed, someone mentioned "a few of
>> the
>>> numbers will be RCF'd", but we wouldn't have a problem using them.
>>>
>>> Then 3 months into using the service (after our cancellation
>> period
>>> expired and we were locked-in), we suddenly started having
>> problems
>>> with the RCF'd numbers being re-written.
>>>
>>> No less than 30 calls to Comcast over the years has resulted in
>> widely
>>> different responses including:
>>> * Ok, we just changed an option in the AdTran to allow you to
>> specify
>>> your own caller ID, everything should work now (it doesn't)
>>> * Give us a list of phone numbers and associated addresses so we
>> can
>>> update our e911 information (they respond with "done!", not "we
>> can't
>>> set e911 for phone number xxx-yyy-zzzz)
>>> * I'm going to escalate this (followed by nothing happening and
>> the
>>> case gets magically closed)
>>>
>>> After talking with Comcast this morning, I had a rep send me what
>> they
>>> had listed for addresses associated with phone numbers...and
>>> unsurprisingly found that they had reset everything to the address
>> of
>>> our SIP trunk service. None of our offices have valid 911 contact
>>> info.
>>>
>>> They're allegedly in the middle of updating the list again, but
>> I'm
>>> not holding my breath.
>>>
>>> It's Comcast's job to provide phone service and 911 routing for
>> this
>>> client. They shouldn't be re-writing anything. They weren't in
>> the
>>> beginning, but I'm guessing it has to do with STIR/SHAKEN. I'm
>>> vaguely familiar with it, but I'm not a telco or a phone service
>>> provider. Just someone they hired to clean up their FreePBX phone
>>> mess. ;)
>>>
>>> -A
>>>
>>> On Tue, Jan 4, 2022 at 3:01 PM Paul Timmins <paul at timmins.net>
>> wrote:
>>>
>>>> I'm going to be the unpopular one here, and point out that
>> Comcast
>>>> is not really responsible to route 911 calls for you when you use
>>>> numbers that they don't provide. For the cost of an hour of an
>>>> attorney's time, you could just set up trunking to basically
>> anyone
>>>> else to handle those offnet/off circuit numbers and the 911
>> routing
>>>> for those numbers.
>>>>
>>>> On 1/4/22 1:30 PM, Aaron C. de Bruyn via VoiceOps wrote:
>>>>
>>>>> One of my clients has a large SIP trunk with Comcast based out
>> of
>>>>> Washington State.
>>>>>
>>>>> They have all their offices across Oregon and Washington hooked
>>>>> into a FreePBX phone server that is attached to the Comcast SIP
>>>>> trunk.
>>>>>
>>>>> 911 calls *constantly* get misrouted to the local PSAP where the
>>>>> SIP trunk lives.
>>>>>
>>>>> I must have called Comcast 30 times over the last few years to
>> try
>>>>> and get this addressed, but Comcast flat-out refuses to fix the
>>>>> issue.
>>>>>
>>>>> The short answer is that Comcast refuses to fix it. In some
>> (but
>>>>> not all) cases, our phone numbers are RCF'd numbers, so they
>> don't
>>>>> actually exist on the trunk...and Comcast forcibly re-writes
>> them
>>>>> to our 'main' number...and then routes the 911 call incorrectly.
>>>>> In other cases, we have provided Comcast with the e911
>>>>> information, they say it's updated, and then we find out months
>>>>> later (when an office dials 911 during an emergency) that it's
>>>>> still not correct.
>>>>>
>>>>> Not only does this affect 911 calls, but also customers who get
>>>>> the re-written caller ID and have no idea which office called
>>>>> them.
>>>>>
>>>>> The "easy" solution is to ditch Comcast and move to a provider
>>>>> that doesn't play the RCF and caller-ID-rewrite games.
>>>>> Unfortunately my client is locked into their Comcast contract
>> for
>>>>> another ~18 months. Early termination would incur a ~$35,000
>>>>> bill.
>>>>>
>>>>> Is there a list of PSAP numbers somewhere so I can set up an
>>>>> internal redirect to the PSAP 10-digit number? I know those
>>>>> 10-digit numbers are guarded like Fort Knox, so I'm betting this
>>>>> option isn't very realistic.
>>>>>
>>>>> Maybe a separate service provider that can just handle 911 calls
>>>>> without "owning" my client's phone numbers?
>>>>>
>>>>> Any other thoughts on how I can route around Comcast brain
>> damage?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> -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 list
>>> VoiceOps at voiceops.org
>>> https://puck.nether.net/mailman/listinfo/voiceops
Jan. 9, 2022
Misrouting 911 Calls?
by aaron@heyaaron.com
I filed a complaint with the FCC about a year ago.
The FCC reached out to Comcast and Comcast reached back out to me.
Their response was that we would basically have to purchase ~200 numbers
(one for each extension on our system), set our outbound 911 caller ID to
those numbers, and then provide Comcast with a list of mappings between
phone numbers and addresses.
It would have added a huge tracking burden for IT as well as increased our
bill by about $2,500 over the contract term.
It's all moot now as BulkVS cost less than $50 to set up, we've already had
one successful 911 call from an office that was continually misrouted by
Comcast, and the contract is up "soon".
-A
On Sat, Jan 8, 2022 at 2:37 PM Mary Lou Carey <marylou at backuptelecom.com>
wrote:
> I was just going to say the same thing. If you give Comcast or any
> carrier a chance to fix it and they can't/won't/don't, then you have to
> escalate it above their heads.
>
> The 911 network has always operated separately from the PSTN world for a
> reason. That's because misroutes can result in people dying! Carriers
> can get in HUGE trouble if they don't address routing issues immediately
> and VOIP carriers can also get in trouble if they don't allow the
> customer a method of updating their location themselves.
>
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
> On 2022-01-05 09:08 AM, Mike Hammett wrote:
> > Escalate to the PUC and ETSBs.
> >
> > Unfortunately, with companies like that, honey doesn't work. You need
> > vinegar.
> >
> > -----
> > Mike Hammett
> > Intelligent Computing Solutions
> > http://www.ics-il.com
> >
> > Midwest Internet Exchange
> > http://www.midwest-ix.com
> >
> > -------------------------
> >
> > From: "Aaron C. de Bruyn via VoiceOps" <voiceops at voiceops.org>
> > To: "Paul Timmins" <paul at timmins.net>
> > Cc: voiceops at voiceops.org
> > Sent: Tuesday, January 4, 2022 6:07:52 PM
> > Subject: Re: [VoiceOps] Misrouting 911 Calls?
> >
> > When I handed Comcast a list of phone numbers years ago, they said
> > there would be no problem porting them over or using them.
> > That was it.
> >
> > Then after the service was installed, someone mentioned "a few of the
> > numbers will be RCF'd", but we wouldn't have a problem using them.
> >
> > Then 3 months into using the service (after our cancellation period
> > expired and we were locked-in), we suddenly started having problems
> > with the RCF'd numbers being re-written.
> >
> > No less than 30 calls to Comcast over the years has resulted in widely
> > different responses including:
> > * Ok, we just changed an option in the AdTran to allow you to specify
> > your own caller ID, everything should work now (it doesn't)
> > * Give us a list of phone numbers and associated addresses so we can
> > update our e911 information (they respond with "done!", not "we can't
> > set e911 for phone number xxx-yyy-zzzz)
> > * I'm going to escalate this (followed by nothing happening and the
> > case gets magically closed)
> >
> > After talking with Comcast this morning, I had a rep send me what they
> > had listed for addresses associated with phone numbers...and
> > unsurprisingly found that they had reset everything to the address of
> > our SIP trunk service. None of our offices have valid 911 contact
> > info.
> >
> > They're allegedly in the middle of updating the list again, but I'm
> > not holding my breath.
> >
> > It's Comcast's job to provide phone service and 911 routing for this
> > client. They shouldn't be re-writing anything. They weren't in the
> > beginning, but I'm guessing it has to do with STIR/SHAKEN. I'm
> > vaguely familiar with it, but I'm not a telco or a phone service
> > provider. Just someone they hired to clean up their FreePBX phone
> > mess. ;)
> >
> > -A
> >
> > On Tue, Jan 4, 2022 at 3:01 PM Paul Timmins <paul at timmins.net> wrote:
> >
> >> I'm going to be the unpopular one here, and point out that Comcast
> >> is not really responsible to route 911 calls for you when you use
> >> numbers that they don't provide. For the cost of an hour of an
> >> attorney's time, you could just set up trunking to basically anyone
> >> else to handle those offnet/off circuit numbers and the 911 routing
> >> for those numbers.
> >>
> >> On 1/4/22 1:30 PM, Aaron C. de Bruyn via VoiceOps wrote:
> >>
> >>> One of my clients has a large SIP trunk with Comcast based out of
> >>> Washington State.
> >>>
> >>> They have all their offices across Oregon and Washington hooked
> >>> into a FreePBX phone server that is attached to the Comcast SIP
> >>> trunk.
> >>>
> >>> 911 calls *constantly* get misrouted to the local PSAP where the
> >>> SIP trunk lives.
> >>>
> >>> I must have called Comcast 30 times over the last few years to try
> >>> and get this addressed, but Comcast flat-out refuses to fix the
> >>> issue.
> >>>
> >>> The short answer is that Comcast refuses to fix it. In some (but
> >>> not all) cases, our phone numbers are RCF'd numbers, so they don't
> >>> actually exist on the trunk...and Comcast forcibly re-writes them
> >>> to our 'main' number...and then routes the 911 call incorrectly.
> >>> In other cases, we have provided Comcast with the e911
> >>> information, they say it's updated, and then we find out months
> >>> later (when an office dials 911 during an emergency) that it's
> >>> still not correct.
> >>>
> >>> Not only does this affect 911 calls, but also customers who get
> >>> the re-written caller ID and have no idea which office called
> >>> them.
> >>>
> >>> The "easy" solution is to ditch Comcast and move to a provider
> >>> that doesn't play the RCF and caller-ID-rewrite games.
> >>> Unfortunately my client is locked into their Comcast contract for
> >>> another ~18 months. Early termination would incur a ~$35,000
> >>> bill.
> >>>
> >>> Is there a list of PSAP numbers somewhere so I can set up an
> >>> internal redirect to the PSAP 10-digit number? I know those
> >>> 10-digit numbers are guarded like Fort Knox, so I'm betting this
> >>> option isn't very realistic.
> >>>
> >>> Maybe a separate service provider that can just handle 911 calls
> >>> without "owning" my client's phone numbers?
> >>>
> >>> Any other thoughts on how I can route around Comcast brain damage?
> >>>
> >>> Thanks,
> >>>
> >>> -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 list
> > VoiceOps at voiceops.org
> > https://puck.nether.net/mailman/listinfo/voiceops
>
Jan. 8, 2022
Misrouting 911 Calls?
by marylou@backuptelecom.com
I was just going to say the same thing. If you give Comcast or any
carrier a chance to fix it and they can't/won't/don't, then you have to
escalate it above their heads.
The 911 network has always operated separately from the PSTN world for a
reason. That's because misroutes can result in people dying! Carriers
can get in HUGE trouble if they don't address routing issues immediately
and VOIP carriers can also get in trouble if they don't allow the
customer a method of updating their location themselves.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2022-01-05 09:08 AM, Mike Hammett wrote:
> Escalate to the PUC and ETSBs.
>
> Unfortunately, with companies like that, honey doesn't work. You need
> vinegar.
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
> Midwest Internet Exchange
> http://www.midwest-ix.com
>
> -------------------------
>
> From: "Aaron C. de Bruyn via VoiceOps" <voiceops at voiceops.org>
> To: "Paul Timmins" <paul at timmins.net>
> Cc: voiceops at voiceops.org
> Sent: Tuesday, January 4, 2022 6:07:52 PM
> Subject: Re: [VoiceOps] Misrouting 911 Calls?
>
> When I handed Comcast a list of phone numbers years ago, they said
> there would be no problem porting them over or using them.
> That was it.
>
> Then after the service was installed, someone mentioned "a few of the
> numbers will be RCF'd", but we wouldn't have a problem using them.
>
> Then 3 months into using the service (after our cancellation period
> expired and we were locked-in), we suddenly started having problems
> with the RCF'd numbers being re-written.
>
> No less than 30 calls to Comcast over the years has resulted in widely
> different responses including:
> * Ok, we just changed an option in the AdTran to allow you to specify
> your own caller ID, everything should work now (it doesn't)
> * Give us a list of phone numbers and associated addresses so we can
> update our e911 information (they respond with "done!", not "we can't
> set e911 for phone number xxx-yyy-zzzz)
> * I'm going to escalate this (followed by nothing happening and the
> case gets magically closed)
>
> After talking with Comcast this morning, I had a rep send me what they
> had listed for addresses associated with phone numbers...and
> unsurprisingly found that they had reset everything to the address of
> our SIP trunk service. None of our offices have valid 911 contact
> info.
>
> They're allegedly in the middle of updating the list again, but I'm
> not holding my breath.
>
> It's Comcast's job to provide phone service and 911 routing for this
> client. They shouldn't be re-writing anything. They weren't in the
> beginning, but I'm guessing it has to do with STIR/SHAKEN. I'm
> vaguely familiar with it, but I'm not a telco or a phone service
> provider. Just someone they hired to clean up their FreePBX phone
> mess. ;)
>
> -A
>
> On Tue, Jan 4, 2022 at 3:01 PM Paul Timmins <paul at timmins.net> wrote:
>
>> I'm going to be the unpopular one here, and point out that Comcast
>> is not really responsible to route 911 calls for you when you use
>> numbers that they don't provide. For the cost of an hour of an
>> attorney's time, you could just set up trunking to basically anyone
>> else to handle those offnet/off circuit numbers and the 911 routing
>> for those numbers.
>>
>> On 1/4/22 1:30 PM, Aaron C. de Bruyn via VoiceOps wrote:
>>
>>> One of my clients has a large SIP trunk with Comcast based out of
>>> Washington State.
>>>
>>> They have all their offices across Oregon and Washington hooked
>>> into a FreePBX phone server that is attached to the Comcast SIP
>>> trunk.
>>>
>>> 911 calls *constantly* get misrouted to the local PSAP where the
>>> SIP trunk lives.
>>>
>>> I must have called Comcast 30 times over the last few years to try
>>> and get this addressed, but Comcast flat-out refuses to fix the
>>> issue.
>>>
>>> The short answer is that Comcast refuses to fix it. In some (but
>>> not all) cases, our phone numbers are RCF'd numbers, so they don't
>>> actually exist on the trunk...and Comcast forcibly re-writes them
>>> to our 'main' number...and then routes the 911 call incorrectly.
>>> In other cases, we have provided Comcast with the e911
>>> information, they say it's updated, and then we find out months
>>> later (when an office dials 911 during an emergency) that it's
>>> still not correct.
>>>
>>> Not only does this affect 911 calls, but also customers who get
>>> the re-written caller ID and have no idea which office called
>>> them.
>>>
>>> The "easy" solution is to ditch Comcast and move to a provider
>>> that doesn't play the RCF and caller-ID-rewrite games.
>>> Unfortunately my client is locked into their Comcast contract for
>>> another ~18 months. Early termination would incur a ~$35,000
>>> bill.
>>>
>>> Is there a list of PSAP numbers somewhere so I can set up an
>>> internal redirect to the PSAP 10-digit number? I know those
>>> 10-digit numbers are guarded like Fort Knox, so I'm betting this
>>> option isn't very realistic.
>>>
>>> Maybe a separate service provider that can just handle 911 calls
>>> without "owning" my client's phone numbers?
>>>
>>> Any other thoughts on how I can route around Comcast brain damage?
>>>
>>> Thanks,
>>>
>>> -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 list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Jan. 8, 2022
Legacy 5ESS en Telekek support options
by mmg@transtelco.net
Thanks Richard
Thanks for your reply. Yes, could you please contact me offline?
On Thu, Jan 6, 2022 at 10:50 AM Richard Jobson <richard at teraquant.com>
wrote:
> Hi Manuel
>
>
>
> As an Oracle Comms OEM, We can certainly help you with regard to the
> Tekelec (EAGLE 5).
>
>
>
> Would you like talk offline?
>
>
>
> Many Thanks & Best Regards,
>
>
>
> For your convenience, please click here
> <https://calendly.com/richard-406/15min> to schedule a time for us to
> talk.
>
>
>
> Richard Jobson
>
> Teraquant Corporation
>
> ph: 719 488 1003
>
> d/l: (719) 766-8523
>
> www.teraquant.com
>
> richard at teraquant.com
>
> https://www.linkedin.com/in/uc-expert-monitoring/
>
>
>
> Network Monitoring and Service Assurance - Speech Quality Experts
> (PESQ/POLQA) and Active Testing - Reporting ? HPBX - Session Border
> Controllers ? SASE and SD-WAN - Big Data Analytics, fraud detection and
> protection.
>
>
>
> --
>
> NOTICE: This electronic mail transmission may contain confidential
> information and is intended only for the person(s) named. Any use, copying,
> or disclosure by any other person is strictly prohibited. If you have
> received this transmission in error, please notify the sender via e-mail.
>
>
>
>
>
> *From: *VoiceOps <voiceops-bounces at voiceops.org> on behalf of Manuel
> Marin <mmg at transtelco.net>
> *Date: *Tuesday, January 4, 2022 at 10:38 PM
> *To: *"voiceops at voiceops.org" <VoiceOps at voiceops.org>
> *Subject: *[VoiceOps] Legacy 5ESS en Telekek support options
>
>
>
> Dear Voiceops community
>
>
>
> I'm looking for a company that can provide support for Lucent 5ESS
> switches and Tekelek (EAGLE 5) that is used for LNP and STP. Legacy gear
> that we will eventually replace but that we need to maintain while we
> migrate services to new generation SIP platforms. I would appreciate if
> someone can recommend me a company
>
>
>
> Thank you
>
>
>
>
>
>
--
Manuel Marin
Engineering
m <abc at transtelco.net>mg at transtelco.net
US +1 (915) 217-2232
MX +52 (656) 257-1109
CONFIDENTIALITY NOTICE: This message is intended only for the individual or
entity to whom it is addressed. If you are not the intended recipient you
are notified that disclosing, copying, distributing or taking any action in
reliance on the contents of this information is strictly prohibited.
AVISO DE CONFIDENCIALIDAD: Esta comunicaci?n es s?lo para el uso de la
persona o entidad a la que se dirige y puede contener informaci?n
privilegiada, confidencial y exenta de divulgaci?n bajo la legislaci?n
aplicable. Si no es el destinatario de esta informaci?n, se le notifica que
cualquier uso, difusi?n, distribuci?n o copia de la comunicaci?n est?
estrictamente prohibido.
Jan. 6, 2022
Legacy 5ESS en Telekek support options
by richard@teraquant.com
Hi Manuel
As an Oracle Comms OEM, We can certainly help you with regard to the Tekelec (EAGLE 5).
Would you like talk offline?
Many Thanks & Best Regards,
For your convenience, please click here<https://calendly.com/richard-406/15min> to schedule a time for us to talk.
Richard Jobson
Teraquant Corporation
ph: 719 488 1003
d/l: (719) 766-8523
www.teraquant.com<http://www.teraquant.com/>
richard at teraquant.com
https://www.linkedin.com/in/uc-expert-monitoring/
Network Monitoring and Service Assurance - Speech Quality Experts (PESQ/POLQA) and Active Testing - Reporting ? HPBX - Session Border Controllers ? SASE and SD-WAN - Big Data Analytics, fraud detection and protection.
--
NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying, or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.
From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Manuel Marin <mmg at transtelco.net>
Date: Tuesday, January 4, 2022 at 10:38 PM
To: "voiceops at voiceops.org" <VoiceOps at voiceops.org>
Subject: [VoiceOps] Legacy 5ESS en Telekek support options
Dear Voiceops community
I'm looking for a company that can provide support for Lucent 5ESS switches and Tekelek (EAGLE 5) that is used for LNP and STP. Legacy gear that we will eventually replace but that we need to maintain while we migrate services to new generation SIP platforms. I would appreciate if someone can recommend me a company
Thank you
Jan. 6, 2022
Misrouting 911 Calls?
by aaron@heyaaron.com
Thanks again everyone.
I ended up going with bulkvs.com.
They answered the phone when I called, didn't have voicemail saying they
were out for Christmas and would be back 2 days ago, their API made it
pretty simple to load ~270 phone numbers in a matter of minutes, and the
'922' test number allowed offices to run around and verify their address
info was correct.
Comcast finally responded to the issue and corrected our info for the 900th
time. The snippet of their response I found annoying was: "if any changes
are made to the account it will automatically revert back to the original
name of --redacted--, which is the name the SIP account was set up under".
In my experience, any change to the account doesn't just affect the "name",
it also resets all the PSAP information back to the location of their
SIP/EDI install. Anyways, that won't be a problem in ~18 months when we
ditch their incompetent service.
-A
On Tue, Jan 4, 2022 at 3:58 PM Aaron C. de Bruyn <aaron at heyaaron.com> wrote:
> Thanks to everyone who responded both on and off-list.
> I think I'm going to go with a 3rd-party provider for routing 911 calls
> and just count down the months until they can ditch Comcast.
>
> -A
>
> On Tue, Jan 4, 2022 at 10:30 AM Aaron C. de Bruyn <aaron at heyaaron.com>
> wrote:
>
>> One of my clients has a large SIP trunk with Comcast based out of
>> Washington State.
>>
>> They have all their offices across Oregon and Washington hooked into a
>> FreePBX phone server that is attached to the Comcast SIP trunk.
>>
>> 911 calls *constantly* get misrouted to the local PSAP where the SIP
>> trunk lives.
>>
>> I must have called Comcast 30 times over the last few years to try and
>> get this addressed, but Comcast flat-out refuses to fix the issue.
>>
>> The short answer is that Comcast refuses to fix it. In some (but not
>> all) cases, our phone numbers are RCF'd numbers, so they don't
>> actually exist on the trunk...and Comcast forcibly re-writes them to our
>> 'main' number...and then routes the 911 call incorrectly. In other cases,
>> we have provided Comcast with the e911 information, they say it's updated,
>> and then we find out months later (when an office dials 911 during an
>> emergency) that it's still not correct.
>>
>> Not only does this affect 911 calls, but also customers who get the
>> re-written caller ID and have no idea which office called them.
>>
>> The "easy" solution is to ditch Comcast and move to a provider that
>> doesn't play the RCF and caller-ID-rewrite games. Unfortunately my client
>> is locked into their Comcast contract for another ~18 months. Early
>> termination would incur a ~$35,000 bill.
>>
>> Is there a list of PSAP numbers somewhere so I can set up an internal
>> redirect to the PSAP 10-digit number? I know those 10-digit numbers are
>> guarded like Fort Knox, so I'm betting this option isn't very realistic.
>>
>> Maybe a separate service provider that can just handle 911 calls without
>> "owning" my client's phone numbers?
>>
>> Any other thoughts on how I can route around Comcast brain damage?
>>
>> Thanks,
>>
>> -A
>>
>
Jan. 6, 2022
VoIP is a restricted business?
by orenyny@gmail.com
Carlos,
The country is the US of course. I did not know that this list has people
from other countries.
The problem is not what category you choose but it is what THEY CHOOSE FOR
YOU.
Just by looking at the website, they decide that you are a VoIP company and
your account may be immediately canceled (Wise)
no questions asked and no way to get any person to speak with, or be
"restricted" (merchant account).
On Wed, Jan 5, 2022 at 10:49 AM Carlos Alvarez <caalvarez at gmail.com> wrote:
> I'm not aware of some VoIP banking issue in the US, but you didn't specify
> the country. I've never heard of Wise. But I don't think "VoIP" is an
> industry, category, or business type. We always choose "telecom" as the
> type. Paypal and Amex recently made a change where if you choose telecom
> as your industry, you cannot use Paypal enhanced payments (new system)
> along with Amex and with third party billing solutions. What a weird
> combo, and a pain. We appealed and have no response, but someone just told
> me yesterday that they paid with an Amex.
>
> Individual companies may have their own policies, like this. Wells Fargo
> and Chase, I can tell you from experience, is happy to have our business.
>
>
> On Wed, Jan 5, 2022 at 6:12 AM Oren Yehezkely <orenyny at gmail.com> wrote:
>
>> Hello,
>>
>> Happy New Year everyone.
>>
>> I recently became aware of the fact that banks (and financial
>> institutions) define any business that merely mentions the word VoIP as
>> restricted. Meaning they would not allow such a business to work with them.
>> As if VoIP is some kind of an illegal substance.
>> I am confident that when it comes to larger players they are not defined
>> as a VoIP business...
>>
>> One company (Wise/Wisetransfer) even claimed that their regulation
>> requires them to do that.
>>
>> I wonder if you have any more information and how do you deal with this.
>>
>> Thanks,
>> Oren
>> _______________________________________________
>> 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
>
Jan. 5, 2022