Is there a way to tell what Transform is actioned as part of the Call Search via a VCS?
We have several similar transforms in place on a VCS as part of the dial plan, but I can't see anything in the search history that tells me which actual transform is actioned as part of the call search. All I see is that the look up was transformed.
Basically, we have a RegEx transform that I don't believe is being actioned even though it is a higher priority than another transform that does look like it gets actioned. I'm not sure why this is as the constructed the way I want and passes the Pattern Check tool built into the VCS.
If you look at your search history, and even if you do a Locate (Maintenance > Tools), there should be a something like the below within the search history.
Just below that it will tell you what the alias has been transformed into, however I don't see where or if at all is specifies which transform it is using.
You could use Check pattern (Maintenance > Tools) to test transforms to see if you would get the desired results you're looking for. Also note, that you should think carefully about your transform priorities in relation to one another, as one transform might match before another and possibly prevent the later from even transforming the alias to what you want.
Thanks Patrick, but you have essentially paraphrased everything I wrote.
I know the search history shows the search has been transformed, but it doesn't say by which transform rule
I know that the RegEx is doing what I think it should be doing as I have already checked the Pattern Match Tool
I know that the priority is important and that other rules might get in the way. This is exactly what I am trying to establish. It appears that a later rule is affecting the search, rather than the RegEx I have inserted above. However, as shown in the point above, the pattern matches are correct.
I'm not quite sure how else I should write this (albiet, my poor English and Dyslexia got in the way of completeing a sensible last sentence).
Indeed, we are at a stage where we need to start implementing sub zones and search rules. Our initial roll out didn't require these, but as the complexity grows, so we are finding that we are running out to steam with things like transforms. We are also seeing other strange behaviors in that when trying to find an certain endpoints by initiating a Locate via the VCS Tools, a search is successful, yet when a call is placed, the search times out. Still this is only a rarity and something that was done a a quick test.
We shall be hitting the administrator guide again shortly.
As mentioned previously in my previous article and following the same idea of certificate pinning in Cisco Meeting Server, to demonstrate this concept added since version 3.0. I used two different CA to sign :1-The WebBridge certificate with CA's certific...
Certificate pinning is introduced on cisco meeting server starting in CMS 3.0 to help prevent man in the middle attack.But what is the Certificate Pinning?Traditionally, SSL Handshake consists on the validation of the server's certificate, let's say colla...
In a Clustering over the WAN deployment, securing the ICCS (Intra-Cluster Communication Signaling) traversing the WAN can be a requirement. The IPSEC VPN Policy between nodes can be configured to secure the ICCS Traffic.To quickly verify that the IPSEC is...
Attracted by the concept of dial plan and the passion of writing, I launched a challenge to write a workbook with practical scenarios covering in details this concept, the result is a workbook with 30 practice labs treating many components such route patt...