Your average RTT is outside of spec on CUCM 5.1. The maximum one way delay is 20ms (or 40ms round trip). You said that things worked fine when full-mesh. Now you are hub-spoke. If this is the only change in the network, it is good indication that the network latency is playing a role.
Is there something that leads you to believe that something else is the problem?
Have you tried have all phones involved in the transaction registered to the same CUCM? Is there a difference in behavior?
If you want to dive deeper to find which subprocess is introducing or impacted by the latency, then you will need to capture detail traces from a test call. I'd also grab sniffer traces is you can. If you grab sniffer traces from all parties, then you can construct the time line between transactions.
A 3 second delay will stand out like a sore thumb.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...