Solved North America / 911 Requirements / 1 Location, remote workers

Status
Not open for further replies.

fgc92210

Customer
Advanced Certified
Joined
Oct 28, 2020
Messages
185
Reaction score
29
Greetings all,

There was a law that passed a little while ago, requesting that in building offices, 911 shall be reachable without limitation, and without trunk seizure prefix.
I read the documentation about 911 and understand how to set it up in the PBX so it can be dialed out without prefix.

I have the following question regarding this scenario though:
- Multiple 800 incoming numbers
- About 20 agents working from home
- When an agent calls out, the main number shall be displayed
- If an agent needed to dial 911 from their soft phone, how would we in this case only display their cell phone number as a caller ID instead of the main number, knowing that there is no sub account available with our carrier.

I was able to go in the trunk outbound parameters, and switch the From: User Part to OriginatorCallerID.
When doing this, I can go to the previous screen, and use a CallerID Outboud rule with (.*) = xxxxx
But when I change the (.*) to (100) for extension 100, then the Default caller ID shows up.
If this works (catch-all .*) , I'd assume that I should put my extension in there instead, but apparently no.
Is the Outbound Source Pattern of an extension calling, its own extension number?

I'm not looking for an answer like "tell agents to use their cell phones" or "change carrier".
I'm looking for a solution -if it exists- in this particular scenario, where if 911 is dialed, then outgoing caller ID becomes user cell phone.

Thank you all.
 

Thank you Cobarltit.
Unless if I missed something, I don't see anything that can help in my scenario though, without adding the 3CX Emergency 3rd party at the end, and even that is inconvenient. On other legacy systems that we sell, I can simply setup rules where IF a user dial 911, THEN user this caller ID, which is a match to a record in the PSAP file..
 
It seems to be an exact fit for your scenario. You create rules and you tell it what CID to use when that extension or group calls out? Isn't that what you wanted? Although I don't think that's what you want or even necessarily legal. For one many providers either don't let you push offnet numbers for 911 or charge you for that ability. So you probably want to find out what capability your provider has and design around that. The other option is to add service from another provider strictly for e911. For your scenario you'd want to get a DID for each location to register for e911. You would push that DID for e911 and we can configure a separate number (in your case, the cell number) for callback should they get disconnected.
 
I'm sorry but I read the whole thread again, and I see nowhere how this correlate to a solution to my scenario: User calls 911, then his cell phone caller ID is used. My SIP Carrier apparently let me user P-Asserted ID to push a callerID which is not part of my DIDs, but I can't get it to work with 3CX using the outbound rules.

Like I said I was able to change the outgoing callerID with P-AssertedID using trunk caller ID Outbound rule, but using (.*) as a source patter. Can someone from support jump in and explain what I should use in order to match extension ID? I tried to use (100) but it didn't work. There must be a way if (.*) work.

If this ^ works, then it's going to be a piece of cake:
Register a new SIP Trunk
Setup 911 to use this SIP Trunk
Add as many outbound rules as there are user, changing the outgoing caller ID depending on their extension.

Then everybody can call out using the company ID, and if they dial 911 their cell phone show up.

Thank you
 
  • Haha
Reactions: StefanW
It is. My apologies, I don't understand how I missed this column.
Tested and approved. Thank you. I'll get out and get better glasses lol.
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet