Voice routes
When a Lync user dials a phone number, we must match it with an object in E.164 format defined in Lync (such as a user, a call park orbit, or an unassigned number) or we need to have a corresponding voice route. If the aforementioned configuration is not true, we will have a SIP error 404, meaning a "No matching rule" in this scenario. Regular expressions (that we have already seen) are used also in voice routes to specify the numbers the route will apply using the following options:
We can use the Build a pattern to match function to generate a regular expression
Or we can write it manually
These options are shown in the following screenshot:
This way, we have created a voice route for the U.K. – London zone, and then typing the phone number, we have automatically applied the normalization rule.
The match tool allows two types of pattern matching: starting digits for numbers that you want to allow or exceptions. We can also select Suppress caller ID, if we want to hide the ID of...
