SIP, PBX, E911 routing and teminology.
-
@JasGot said in SIP, PBX, E911 routing and teminology.:
I have an inhouse PBX that connects via SIP to a provider.
Here's my problem, I need to alter the outbound caller ID sent to the SIP provider for the deskphones; based on the phone number they are calling number they are calling. I don't know the right terminology to get started on this. I can explain it so that it is understood, but I need to contact several possible administrators for this phone system, and I don't want to go through the whole explanation with each one of them.
As a programmer, I would just use a regex statement to do this, but I don't know if that'll work in this particular PBX.
What I have found so far is that this is either unique, or over most of their heads.
It's an NEC SL2100
I assume that you actually mean that you need to send a specific Caller ID (CID) based on the location of the user.
With sites that have a need for a more detailed e911 configuration than a single outbound CID, I will always make it a point to group my extensions by some logical method in order to use a pattern match on the extension to determine the CID to use.
Some systems also have an emergency CID field for you to populate per extension, but that just means more paperwork. I like the pattern match method better.
I would assume that your system has something for the outbound call flow, as pretty every PBX ever, has had this functionality.
-
NEC is proprietary through a dealer network. so you have to go that route for support.
There is no obvious information on this functionality on the main resources link for the unit.
https://www.necsl2100.com/us/Resources/resources -
@JaredBusch said in SIP, PBX, E911 routing and teminology.:
NEC is proprietary through a dealer network. so you have to go that route for support.
There is no obvious information on this functionality on the main resources link for the unit.
https://www.necsl2100.com/us/Resources/resourcesyeah, this is the tough nut on this one. Unless someone on these forums is specifically a NEC phone tech, it's likely no one will be able to give you specific help.
-
@Dashrender said in SIP, PBX, E911 routing and teminology.:
@JaredBusch said in SIP, PBX, E911 routing and teminology.:
NEC is proprietary through a dealer network. so you have to go that route for support.
There is no obvious information on this functionality on the main resources link for the unit.
https://www.necsl2100.com/us/Resources/resourcesyeah, this is the tough nut on this one. Unless someone on these forums is specifically a NEC phone tech, it's likely no one will be able to give you specific help.
Right, and their terminology is likely just a little different for the same things compared to other solutions.
-
@JaredBusch said in SIP, PBX, E911 routing and teminology.:
I assume that you actually mean that you need to send a specific Caller ID (CID) based on the location of the user.
Ye. Because the PBX cannot send E911 data, I thought I would use DIDs at the SIP provider and set them appropriately. The issues comes where I need all outbound calls to show the main number as their caller ID unless they have dialed 911.
The provider is Skyetel, and they will not/can not re-write the outbound caller ID based on a calling plan/route. My first choice would be to have Skyetel re-write all outbound caller IDs to be the main number UNLESS the dialed number was "911".
I'm open to ideas.....@JaredBusch
-
@JasGot said in SIP, PBX, E911 routing and teminology.:
Because the PBX cannot send E911 data
PBX systems don't send e911 "data" at all. They send a CID that has the address information tied to it.
-
@JasGot said in SIP, PBX, E911 routing and teminology.:
The provider is Skyetel, and they will not/can not re-write the outbound caller ID based on a calling plan/route. My first choice would be to have Skyetel re-write all outbound caller IDs to be the main number UNLESS the dialed number was "911".
That is not the job of the provider. That is the job of the PBX.
-
@JaredBusch said in SIP, PBX, E911 routing and teminology.:
@JasGot said in SIP, PBX, E911 routing and teminology.:
The provider is Skyetel, and they will not/can not re-write the outbound caller ID based on a calling plan/route. My first choice would be to have Skyetel re-write all outbound caller IDs to be the main number UNLESS the dialed number was "911".
That is not the job of the provider. That is the job of the PBX.
FWIW - there are providers that do this (not us though). Its extremely expensive as you have to own all the phone numbers you are using, and the rates to do this are very high.
-
@JaredBusch said in SIP, PBX, E911 routing and teminology.:
@JasGot said in SIP, PBX, E911 routing and teminology.:
Because the PBX cannot send E911 data
PBX systems don't send e911 "data" at all. They send a CID that has the address information tied to it.
Exactly - if the send phone number doesn't have the correct address associated with it, 911 won't get the right information either.
-
@Skyetel said in SIP, PBX, E911 routing and teminology.:
@JaredBusch said in SIP, PBX, E911 routing and teminology.:
@JasGot said in SIP, PBX, E911 routing and teminology.:
The provider is Skyetel, and they will not/can not re-write the outbound caller ID based on a calling plan/route. My first choice would be to have Skyetel re-write all outbound caller IDs to be the main number UNLESS the dialed number was "911".
That is not the job of the provider. That is the job of the PBX.
FWIW - there are providers that do this (not us though). Its extremely expensive as you have to own all the phone numbers you are using, and the rates to do this are very high.
Yes, and no one wants that kind of lock in.
-
A certain carrier I used to use, lets call them Wind Scream, does this; however I spent nearly 6 MONTHS with their engineerig and support to finally get E911 working correctly withe correct re-write DID outbound when 911 is dialed. Good Grief never again!
-
@jt1001001 said in SIP, PBX, E911 routing and teminology.:
I spent nearly 6 MONTHS with their engineerig and support to finally get E911 working correctly
Good to know!
