01-12-2016 11:56 PM - edited 03-18-2019 05:25 AM
Guys,
I have created 2 search rules with different priority, and both have (continue) on successful match, when i am dialing URI of registered endpoint example@example.com the goes to TP server but not to the end point, is it because of priority of search rule?
01-13-2016 09:53 AM
Can you provide a copy of your VCS search rules as well as a search history for the failed called? You might have a rule that is misconfigured or priority wrong.
01-14-2016 11:11 AM
your Search Rules need to be checked. The call is most likely going to your MCU because of the Fallback Alias Setting which is probably set to the alias of your MCU.
01-14-2016 11:45 PM
Hi Lawrence, The thing is i am dialing a URI of and endpoint registered on vcs, but what is happening here when dialing the URI call goes to TP server, but when i am increasing the priority of search rule which is match on every thing then call goes to the ENDPOINT registered.
01-15-2016 04:06 AM
There two possible things happening.
1. You have overlapping dialplans
2. Your search rules are not properly configured. Your local search rule should have a higher priority to any external search rule because you want VCS to search locally before it sends the call to an external destination
01-15-2016 07:08 AM
To help figure out what's going, as I mentioned, can you provide a copy of your VCS search rules and a search history for the failed call? It could be that the two search rules are too closely configured and matching both called addresses.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide