911 and 933 but not 999 outbound rule

Status
Not open for further replies.

Davdi

Platinum Partner
Advanced Certified
Joined
Aug 10, 2018
Messages
28
Reaction score
6
Hey all,

I recently had an issue where the 3cx voicemail system extension didn't register. The frightening thing is that when the client pushed their voicemail button, they heard that they were being connected to the 911 operator. I opened a ticket with our trunk provider and they informed me that any call out on the emergency trunk that isnt obviously something else will get routed to 911, even if the original call was to 999.

i have a standard emergency outbound rule

starts with a 9
3 digits in length
allow through to emergency trunk
override outbound caller ID to that locations 911 registered DID
1637352522465.png

I really do not want to change the rule to start with 911 because that would not allow 933 calls through and we would have to dial 911 in order to test anything. I also do not want to create a second outbound rule that also routes 933 calls to the emergency trunk because i don't want an accidental difference in the two rules to not be caught with a test call to 933.

Does anyone know how to program a single outbound route that will allow calls to 933 and 911 and NOT 999?
 
Create outbound rule with prefix 999 and do not select any sip trunks , move these rule to the top of the list

Have you change the default 3cx voicemail from 666 to 999 ?
 
Thanks for the suggestion, I will try creating a route for 999 that goes nowhere. When I install 3CX it defaults to 999 as the voicemail extension.
 
You may want to change the voicemail number from 999

General > General Settings > Voicemail settings

If you make this change , you will have to reprovision each phone
 
  • Like
Reactions: Evolute IT
I really do not want to change the rule to start with 911 because that would not allow 933 calls through and we would have to dial 911 in order to test anything. I also do not want to create a second outbound rule that also routes 933 calls to the emergency trunk because i don't want an accidental difference in the two rules to not be caught with a test call to 933.
You had created a very vague rule... 3 digits long, starting with 9, yet you only want the numbers 911 and 933 (for testing) to route out on the emergency trunk. Why would you not simply create the two specific rules, as your current rule was allowing any 9XX number to route out on the trunk. Two rules would only allow the two numbers, you would not have to go to the trouble of blocking anything. If you leave the current rule in place, then dialing 923, for example, would still attempt to route out on the trunk. It may fail, but probably because of your provider rejecting it ,rather than 3CX preventing the call from being sent in the first place

Perhaps you could clarify the second sentence above.
 
Last edited:
You had created a very vague rule... 3 digits long, starting with 9, yet you only want the numbers 911 and 933 (for testing) to route out on the emergency trunk. Why would you not simply create the two specific rules, as your current rule was allowing any 9XX number to route out on the trunk. Two rule would only allow the two numbers, you would not have to go to the trouble of blocking anything. If you leave the current rule inplace, then dialing 923, for example, would still attempt to route out on the trunk. It may fail, but probably because of your provider rejecting it ,rather than 3CX preventing the call from being sent in the first place

Perhaps you could clarify the second sentence above.
They can also do Prefix "911,933", Length 3. And both will work.
 
I would ditch the outbound rules and go more of the Emergency Numbers portion of 3CX. This is under Settings > General . You then can also do notifications based on if a emergency number has been dialed or not
1637379179333.png
 

Attachments

  • 1637379165836.png
    1637379165836.png
    8.7 KB · Views: 8
I also do not want to create a second outbound rule that also routes 933 calls to the emergency trunk because i don't want an accidental difference in the two rules to not be caught with a test call to 933.
I do not understand this. Create the rules and test them out so you know they work and do not leave anything to chance. This will solve both your issues.

They can also do Prefix "911,933", Length 3. And both will work.
This will also work
 
Status
Not open for further replies.

Members Online Now

Forum statistics

Threads
111,832
Messages
589,285
Members
164,662
Latest member
DejanMDS