Opt out from CH going to wrong destination

[Yort Mantup]

I am encountering an intermittent issue where when callers to one site (Call Handler) press 0 during the greeting, are instead of going to that sites operator they are going to another sites operator.  I double checked and the zero out is programmed correctly.  This happens intermittently so it is not an issue that can be easily recreated.

I did run a CDR report on one call that experienced this.  It showed the caller DID calling to the correct sites Call Handler and using the correct gateway.  The next line item shows the same DID calling the other sites CH.  Very strange.

36	Transfer	2 3354624	2 1	46540156 46540159	7176694790 null	52950 AllPhones	52950 AllPhones	52950 AllPhones	null null null null
37	Transfer	2 3354624	2 2	46540156 33172072	7176694790 null	26350 AllPhones	26350 AllPhones	8000 AllPhones	null null null null

                Are their other tools I can use to pull more information to see why this occurs so randomly?

Thanks

Running CUCM, Connections 8.5

[Tapan Dutt]

For a start we need to capture a failed/incorrectly routed call. Then we can gather CUCM SDI traces to compare a working and a non-working call.

Tapan

[Yort Mantup]

I have limited experience gathering SDI traces but can manage that.  What method would be best to capture a failed routed call?  I was looking at the Analyze call path option in RTMT.