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
>From my first message:
> Early termination would incur a ~$35,000 bill.
They're paying just over $2k/mo for service and have ~18 months left on the
contract. Apparently Comcast gives a slight discount from the normal
monthly cost if you terminate early, but it's not much.
-A
On Tue, Jan 4,
why not move that SIP trunk elsewhere? Like Intelepeer or Vonage or RNG
or Sangoma or anyone who would handle the E911?
On 1/4/2022 7:07 PM, Aaron C. de Bruyn via VoiceOps wrote:
When I handed Comcast a list of phone numbers years ago, they said
there would be no problem porting them over or
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
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
wrote:
> One of my clients has a large SIP trunk with
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
BulkVS offers E911 service to numbers not native to them. So you can
register your E911 DIDs for each office address and just send your 911
traffic to them. They also support the text/email notification needed for
when someone in the office dials 911. I think they are supporting Z axis
geo data
Sounds like this client is large enough to have a legal person/team on call
or on staff? They should write a letter putting the carrier on notice that
they are in violation of the law, and in violation of their contract, and
they have X days to rectify or the contract is void.
You have to give
Since this involves 911 service, I think it is past time to get the lawyers
involved.
On Tue, Jan 4, 2022 at 10:41 AM Aaron C. de Bruyn via VoiceOps <
voiceops@voiceops.org> wrote:
> One of my clients has a large SIP trunk with Comcast based out of
> Washington State.
>
> They have all their
This:
Maybe a separate service provider that can just handle 911 calls without
"owning" my client's phone numbers?
There are a number of VoIP 911 providers who handle and route calls to the
correct PSAP based either on the registered address or based on information
collected from the called on
Get a small SIP trunk from another provider. Order 1 DID from that provider
for each physical office location. Register appropriate 911 information for
the DID. Configure FreePBX to rewrite the CallerID to the appropriate DID for
outbound 911 calls. You may be able to get new DIDs from
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
12 matches
Mail list logo
