We had an interesting issue where a user accidentally called “9118884000”. It completely bypasses our CER setup. We didn’t get an alert for it. And the user didn’t realize they accidentally called. And the police showed up and there was a lot of confusion.
Do people typically put in safeguards to prevent this? (ie a pattern that matched 911* and rewrites it as 911 so it gets properly alerted and routed).
In most, if not all, national dialing plans there is no possible overlap with emergency services. For example in the United States, 911 has no possible conflicts - that NPA is reserved - and toll calls require a trunk prefix of one (1). When you dial 911 on a landline in the USA there is nothing else you can dial so the CO switch stops accepting input and routes the call immediately.
The same approach is typically used in CUCM call routing design: build specific Route Patterns (or Route Filters if that’s your thing) that do not accept additional digits after the emergency services pattern. In your case, by the time the user dials the third digit “911” CUCM should ideally have only one possible matched pattern: your CER CTI RP. This is possible because both the NPA and NXX must start with 2-9. As such “911”, “9[2-9]XX[2-9]XXXXXX”, and “91[2-9]XX[2-9]XXXXXX” are all non-overlapping. In contrast, “9911” may overlap in seven-digit local dialing areas or ten-digit areas that include an NPA starting with nine. The typical approach is to use Urgent Priority, forcing CUCM to not accept additional digits once that fixed-length pattern is matched.
Reminder that Kari’s Law now mandates support of straight “911” in the USA; you cannot require the user dial “9911”.
hi Team, we are planning to deploy Multi-Factor Authentication for Jabber. The main requirement is to use MFA over internet (MRA).Is it possible to deploy MFA just for MRA and don't touch impact any on-prem existing setup?Can someone please guide on ...
Looking to expand your professional network? Interested in gaining an edge with exclusive technology insights? Engage with Cisco experts, share feedback on products and connect with peers from across the globe. Cisco Champion 2021 applications are open fo...
UCCX does not natively protect HTTP Triggers.
I wanted to come up with a solution to handle HTTP cookie based authentication.
There is a zip file for this project attached to this article. It was written on UCCX 12.5...
CUCM can backup the manually or have sehchduler to backup the configuration and historical reports from the server diester recovery systemStep 1. Navigate to CUCM > Disaster Recovery System > Backup > Manual Backup as shown in the...