I guess the question was more focused around trying to avoid the management issues and cost of enabling 911 on a bunch of numbers. I'm not sure where regulations stand currently on things like this, particularly when you involve devices that WILL be roaming all the time. Also, the first customer doing this will be on 3CX, which gives us some limitations on what we can set. It's not like Asterisk where we already very easily do setvar=911CLID=602xxxxxxx by site or by phone. On Thu, Mar 7, 2019 at 11:36 AM Ryan Delgrosso <ryandelgrosso at gmail.com> wrote:
Im moving towards using the NG911 service from west specifically for this sort of case.
Essentially you provision an address and a number, but then in the invite to west, you can add an XML body with address information that will override the provisioned info (it still must be provisioned and validated but the relationships are fungible), so if, in this case your user is on their home ext you can detect that in your platform and send alternate info.
You can also provide detailed intra-building routing info for larger campuses and facilities such as floor, room etc. On 3/7/2019 10:03 AM, Carlos Alvarez wrote:
I'm wondering what people are doing, and their interpretation of the laws, with companies where they have large numbers of remote (home) users. So far we have only a few really, and we provide 911 for each phone's own CLID. Now we have a customer who wants to have a very large number, PLUS have an office handset, home handset, softphone on a computer, and softphone on a mobile. It makes little sense to put 911 service on each of these.
_______________________________________________ VoiceOps mailing listVoiceOps at voiceops.orghttps://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops