[ASTPPCOM-253] Feature Request: Set callerid when specific number is dialled (emergency services) Created: 01/Nov/17  Updated: 08/Nov/19

Status: To Do
Project: ASTPP Community
Component/s: None
Affects Version/s: None
Fix Version/s: v5.0

Type: New Feature
Reporter: Samir Doshi Assignee: Samir Doshi
Resolution: Unresolved Votes: 0
Labels: Feature
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners

 Description   

This would be a really good addition to the customer tab.

The ability to set emergency services numbers (EG: 911, 999, 112, etc) and next to these numbers the ability to set the callerid for this customer.

In the UK it is a legal requirement to send a valid callerid when anyone dials the emergency services and while most customers pbx's are configured correctly, we have had instances where there has been a misconfiguration and an invalid callerid has been presented when they've called the emergency services.

Having the ability to be able to force a callerid for that customer when they dial emergency numbers would be good as a catchall to prevent any problems.

We can force callerid on the customer globally, but that breaks DID presentation so is not ideal.

So, add a tab to the customers called emergency numbers.

this has a table that has two fields (or three, will elaborate in two examples)
Two field example.

Field 1. Emergency number
Field 2. Forced Caller ID

Three field example.

Field 1. Emergency number
Field 2. Forced Caller ID
Field 3. Outbound Trunk

The three field option may be the most flexible if people have multiple sip providers on their billing platform.

Would be good to hear from other UK users to see how they handle this.

Request created on behalf of "Spacey".

 Comments   
Comment by Samir Doshi [ 01/Nov/17 ]

Interesting feature. If we get many request to implement this feature, then we will do and release under open source.

Comment by spacejelly [ 01/Nov/17 ]

This will be really useful, not only for emergency services but quite possibly for other uses too. As said, UK, it's a legal requirement so this will be a very positive addition that I believe will be unique for these types of billing platforms

Comment by kristapsdravnieks [ 01/Nov/17 ]

This is legar requirement in Ireland too.
+1 from me for this feature

Comment by jeffik1300 [ 10/Dec/17 ]

This would be helpful for US and Canada. We have two services, 911 and 311.
911 is emergency; fire police ambulance. Would be great to send calls to specific number and specific trunk because since we use multiple providers for outbound but the 911 service is linked to a DID so for 911 to work for a customer I have to use same inbound provider that has the 911 look up to send all calls out for that customer. This defeats the purpose of least cost routing. Also if we give customers actual phone number (non 911) to Emergency service, calls would have to go out on local provider trunk since if lcr is used calls may go out over provider in different country and proper caller ID information may not be sent accurately. So forced trunk for 911 calls would be great.
311 in many cities is the main number to reach City Services. This would be similar because calls to 311 need to go out on a local provider. It would be a similar situation to 911 in that if call was send to least cost route and call went out on US provider and customer in Toronto dials 311 they may get City of Detroit or New York. I suspect it would be random.
These are not legal requirements in US and Canada, but you have to inform customers that 911 is not supported.

Comment by luigialb [ 26/Oct/18 ]

i agree also Canada and USA. A MUST!

Generated at Sat Feb 10 07:15:31 CET 2024 using Jira 8.13.3#813003-sha1:22ebedbb75c99b147c66f14e031dd8a2d214753a.