Accepted Solutions
That’s one of the original design criteria’s for back when this function in CUCM was built. Hence no it can’t natively be turned off. You’d need to fool the system to not match the remote destination number with the presented mobile number. But still have configuration in place to be able to extend the call to the remote destination number, that now isn’t the true mobile number anymore. For example you could add any digits infront of the + sign, assuming you have the RD in +E.164 format, then in the reroute CSS you can either have a translation pattern that removes the prefixed value or a route pattern that does the same prior to sending it to the route list.
May I ask why you’d want to do this? It would negate the true intent of Single Number Reach.
That’s one of the original design criteria’s for back when this function in CUCM was built. Hence no it can’t natively be turned off. You’d need to fool the system to not match the remote destination number with the presented mobile number. But still have configuration in place to be able to extend the call to the remote destination number, that now isn’t the true mobile number anymore. For example you could add any digits infront of the + sign, assuming you have the RD in +E.164 format, then in the reroute CSS you can either have a translation pattern that removes the prefixed value or a route pattern that does the same prior to sending it to the route list.
May I ask why you’d want to do this? It would negate the true intent of Single Number Reach.
