As far as i know, the loop detection was based on Call TAG... at least this was the official information that i had, that this call tag was inserted to be able to use the loop detection feature and avoid to process the same call again. This is on training material.
I think that this behaviour that you mencion is related to send or not to send the call back to the zone that the call came from, and not the ability of a VCS to identify that a call was already processed and avoid the loop.
If my memory is right, this behaviour was not on X5.2 (i cannot test right now)
Please, could you double check your information and confirm this?
If your information is correct, i need to interact with training developers to include this on CAG.
OK Alok, i didn´t realized that it is an "meet all" in the sentence on X7 Admin Guide (this wasn´t on older versions)
To be more confused, check this text on the same X7 Admin Guide:
The Call Tag also helps identify loops in your network - it is used as part of the automatic call loop detection
feature, and you can also search the Event Log for all events relating to a single call tag. Loops occur when a query is sent to a neighbor zone and passes through one or more systems before being routed back to the original VCS. In this situation the outgoing and incoming query will have different Call Serial Numbers and may even be for different destination aliases (depending on whether any transforms were applied). However, the call will still have the same Call Tag.
If a call with different protocol it is not considered the same call, and so it is not a loop, if we leave interworking On, there always will be a looped call on VCS C <-> VCS E enviroment with any alias on both sides... except if we search locally before (as instructed on manuals). I´ll do more tests latter.
Hi Martin, thanks for your tips. I´m aware of them.
I´m not just trying to solve this customer problem (i alread did before to post here), what i´m trying to do is to let it more clear, to prevent others and to confirm the behaviour to teach correctly. If the behaviour generates to many trouble, we send a Feature Request to Cisco.
For example, the guides instructs to use any alias to traversal on both sides, this obviously will cause a loop, specially if a migration mode is in use (to strip a domain for SIP to reach e164 and to add a domain to legacy e164 reach URI). The loop don´t happen only because the VCS will find the destination locally before to try on traversal zone.
With this new interface that let users to make rules based on source, destination and protocol, we can expect that customers will do a lot of mistakes with dial plan (new interface beacause most of it was already available with CPLs).
*The test was made in lab environment, based on the customer problem.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...