We've recently started using ARS Digit Conversion to prevent folks from unknowingly using the PSTN when they could have dialed a 4 digit extension for a user in another office in our enterprise. We're essentially trying to make the system smarter than the user. I'm sure many of you have been through this already.
My question is this... What can I do to proactively address the potential for an occasional WAN outage scenario where a user dials 11 digits and it would have completed if ARS Digit Conversion hadn't stripped 7 digits to redirect it to a 4-digit extension, which isn't reachable due to the WAN outage?
We're just worried about the occasional complaint: "I can't call Joe User in Location X while the WAN is out. Even if I dial his entire number, the system converts it to 4 digits and the call fails."
Is there a contingency for a scenario such as this? A feature I have not yet discovered?
Or would we have to login to the isolated LSP and change its ARS Digit Conversion translation during the outage?
My question is this... What can I do to proactively address the potential for an occasional WAN outage scenario where a user dials 11 digits and it would have completed if ARS Digit Conversion hadn't stripped 7 digits to redirect it to a 4-digit extension, which isn't reachable due to the WAN outage?
We're just worried about the occasional complaint: "I can't call Joe User in Location X while the WAN is out. Even if I dial his entire number, the system converts it to 4 digits and the call fails."
Is there a contingency for a scenario such as this? A feature I have not yet discovered?
Or would we have to login to the isolated LSP and change its ARS Digit Conversion translation during the outage?