The "Emergency Code" feature of 3CX seems to break the ability to route incoming calls using an exception. For example, we have our incoming calls kinda' setup like this: During Business Hours ---------- Call is routed to Extension 900 900 - Call Routing Exception From * 5:30am - 8:00am route to Ring Group 1 From * 8:00am - 5:00pm route to Ring Group 2 From * 5:00pm - 5:30am route to Digital Receptions 1 After Business Hours/Holidays ---------- Call is routed to Digital Receptionist 1 So, in theory, when we use the "Emergency Code" feature to allow incoming calls after hours or during a holiday, it "should" route all incoming calls to extension 900 first. From there, depending on the time of day, the exception should route the call to the appropriate ring groups. However, instead of being routed properly via the exception, ALL calls route to rule 1. Our workaround for glitch was to reorganize the rules so that rule 1 is the one we wanted to use, but it would be nice to have this issue addressed in future updates. We have one of our phones hooked up to a PA and don't want the phone ringing off the hook and bothering the neighborhood at 5:30am.