I can't confirm the impact of lack of licensing in your organization. While I was typing this Anthony was answering you as well , here's what I pecked out
The administration guide says:
You must install new licenses within 60 days of installation or upgrade. If you do not install new licenses within 60 days, the Emergency Responder system stops tracking and updating the Phone Location.
If you're in non compliance I believe it just tracks up to the number of devices it can track and not beyond that which is also not ideal. I *believe*.
Phone tracking does locate the switchport the phone is on so that it can take an action based on this. It can also track by subnet, or manual definition.
If you're looking at it from this perspective:
[cid:image001.png@01D57EAF.1E18DC60]
The item on the left prescribes the treatment for a call, from the device(s) tracked here, that route through CER. Clicking on that shows you the ELIN it will attempt to masquerade the call as, and any onsite alerting needs.
"ALI Details" should match what is in the PS/ALI database for your purposes, but it doesn't cause it to do so unless you go and have it changed there.
Your telecom group should be able to tell you what MSAG data is applied to the ELIN you are outpulsing when an emergency call is made from that number. Or your service provider. In many implementations you need to do something to be able to even send something other than your lead billing telephone number which would just result in the street address that the service is established at being seen for all calls.
The CER administration guide explains most of this in reasonable detail, and, if you have the VMWare resources for it, you can install the software in demo licensing mode for 60 days to play with it and see what it does.
It is important to make sure that all the pieces work here for the safety of those involved, but, you'll do that best if you have a moment to look at the documentation for CER to see what it does, and then build your onion out from that to try and figure out which calls get to CER when, and where they go after CER redirects the call to some route pattern somewhere else.
More or less:
1) Phone makes a call to a number like any other phone call it can make
2) UCM says "ah that number goes to CER". This can be any number or many numbers.
3) CER says "Oh boy, an emergency call. Let me see if that phone is somewhere I know about due to tracking, manual, subnet, etc"
4) If CER knows where the phone is, it uses the ERL (location) treatment to:
a. Masquerade the number, if configured to do so.
b. Forward the call on to a specific pattern
c. Alert On Site Security
5) If CER doesn't know where the phone is, it uses the _default_ ERL to apply the above treatment, but, your on site will not know where the caller is, and it is likely wherever that call forwarded off to, public safety will not get a lot of useful detail.
CER is not complicated but it adds a lot of new acronyms to be aware of that's for sure, and a bunch of moving pieces have to be aligned.
The admin guide prescribes setting the system up with some specific pattern and partition names to minimize complication and so that others will understand what you've done after it is setup. Hopefully, whomever set yours up followed the same conventions to make it somewhat easy to decipher.
Adam
