- Joined
- Aug 20, 2019
- Messages
- 1,131
- Reaction score
- 1,252
Hi 3CX Strategy Team,
Is it possible to consider the option Import and export in CSV format of Emergency Numbers (Emergency OutboundRules) please? (Similar solution to Inbound Rules)
Refer : Emergency numbers rules duplication
Depending on the countries of the callers and the CIDs to be displayed, it is necessary to create several "Emergency Numbers" rules to cover.
You have to be careful not to forget any.
Although the numbers are not emergency response numbers, there are several other services with short numbers that may conflict with extension numbers.
Creating them in Emergency Number ensures that no inadvertent extension is created that conflicts with a short number.
Good Example list posted by @aws2p in other thread

Another example for North America ; https://cnac.ca/other_codes/n11/n11_codes.htm + https://globalnews.ca/news/9097268/canada-to-launch-988-mental-health-crisis/
I am convinced that there are several other examples in other countries
Maybe then you could transpose solution for (normal) outbound rules, if the development is "easy" to adapt, but that's not the main focus, at least Emergency Numbers would be nice.
Personally, I use solution Import "Inbound Rules" every time I create a new PBX ( DIDs are automatically created on trunk, it's great )
What do you think of the idea?
Can you please consider ?
thx
Guillaume
Is it possible to consider the option Import and export in CSV format of Emergency Numbers (Emergency OutboundRules) please? (Similar solution to Inbound Rules)
Refer : Emergency numbers rules duplication
Depending on the countries of the callers and the CIDs to be displayed, it is necessary to create several "Emergency Numbers" rules to cover.
You have to be careful not to forget any.
Although the numbers are not emergency response numbers, there are several other services with short numbers that may conflict with extension numbers.
Creating them in Emergency Number ensures that no inadvertent extension is created that conflicts with a short number.
Good Example list posted by @aws2p in other thread

Another example for North America ; https://cnac.ca/other_codes/n11/n11_codes.htm + https://globalnews.ca/news/9097268/canada-to-launch-988-mental-health-crisis/
I am convinced that there are several other examples in other countries
It is true, in some parts of the world there is not one global emergency number like we have in the USA. In some countries there are separate emergency numbers for fire, poison control, police, etc.
I think perhaps what is needed is the ability to add multiple emergency phone numbers to an emergency group -- perhaps a comma separated list? That would reduce the number of rules needed. Unfortunately, today, there is not an option to import rules, or add multiple numbers to each group.
We could build a solution with the Call Control API, but I don't expect this is a common enough, or big enough, challenge to justify the effort. This sounds like a fairly easy "idea" for 3CX to tackle.
Maybe then you could transpose solution for (normal) outbound rules, if the development is "easy" to adapt, but that's not the main focus, at least Emergency Numbers would be nice.
Personally, I use solution Import "Inbound Rules" every time I create a new PBX ( DIDs are automatically created on trunk, it's great )
What do you think of the idea?
Can you please consider ?
thx
Guillaume
Last edited:
Upvote
12