Accepted Solutions
You’ll need to pass the call via one translation pattern where you set the option to route on calling number and then pass it through another translation pattern that matches on the calling number. This article describes how this works Blocking Inbound calls to Cisco Unified Communications Manager based on Caller ID
Even if it’s for a blocking setup, the concept is the same for routing.
That isn’t a viable option. You can route based upon calling number with translation pattern(s), but not route pattern(s).
You’ll need to pass the call via one translation pattern where you set the option to route on calling number and then pass it through another translation pattern that matches on the calling number. This article describes how this works Blocking Inbound calls to Cisco Unified Communications Manager based on Caller ID
Even if it’s for a blocking setup, the concept is the same for routing.
The optimal solution is to modify the calling number in the Route pattern or strip the number from the calling party on the trunk using translation. Calling party transformation can also be used in this case.
Thank you @Roger Kallberg and @Nithin Eluvathingal for your inputs.
I found that I wasn't checking this box "Route next hop By Calling Party Number" to force the call to route based on calling party.
After checking this box, my problem was resolved.
Glad to hear that. Apart from this you probably do not want to have Provide Outside Dial Tone checked on this TP.
