e911 management

[c-kunz]

Hello, we have been using Webex for about 5 years now.  We are integrated with RedSky for our e911.  Our normal setup is each location is based on it's IP address and one specific number that is presented to RedSky and thus 911 operator.  Then if the 911 operator had to call the location back it would ring into a hunt group which would ring all the phones (some phones only have extensions).  This has been fine and has worked without issue.  My problem now is that I might have a user with two phones, one at one location and one at another location with the same extension.  If there is a 911 emergency at the one location and this person is at his other location and a 911 calls should come into the office, he could potentially take the call at the other location which could cause delays etc.  Any thoughts on how to get around this... the only thing I can think of is to not include that user in the huntgroup but not much of a solution.  Thanks in advance for any help.

Chris

[MichaelRalston0900]

I haven't run into this specific scenario for 911 purposes, but what I've done in the past for similar situations with a user that has phones at multiple sites is to set the user up with their true DID/extension. Then have two virtual lines, one for each location. You can then add the virtual extension for Site1 to their phone physically at Site1, then the same for the virtual extension for Site2. Then you can have the site specific hunt groups ring those new virtual lines instead of the user directly. 

It definitely adds complexity since now this user has 3 extensions instead of 1, but allows you to dictate which one will ring from which hunt group. 

[Jonathan Schulenberg]

Do these users have DIDs? If yes you can just set the user's DID as their ECBN instead of the Hunt Group and PSAP callbacks would route direct to that user's line.

If not, and these users are ESN only, you should run this past your Cisco account team to understand what roadmap items may help in the future. I can't discuss the roadmap here since it requires an NDA. The CUCM+CER equivelent feature was ELINs though. CER would remember which ELIN it used for an outgoing emergency call and route any incoming calls to that DID back to the CUCM DN for four hours or until it was forced to recycle that ELIN for another outgoing emergency call, whichever came first.

[c-kunz]

Yes DIDs would be easy..  this would be a user with just an extension.  I'll reach out to our Cisco account rep to see what can be determined.  Thanks