It will depend on where you collected the logs from. If you collected them from CUCM via RTMT, make sure you are selecting all servers in the cluster, less you might miss the actual server used for the outbound call. If you want to avoid using different servers for this, make sure to check the "run on all active cm nodes" check box on your route lists and sip trunks in cucm (requires RL and SIP Trunk resets to take affect).
Also, if the call failed, then the most likely scenario is the TCP handshake never happened from CUCM to SONUS, and thus no higher layer traces to be found, because they never happened. If this is a routing issue, you will need to do a packet capture on the network or just ask the route/switch guys to help. If this is a SIP issue, the SONUS might be setup to not support incoming TCP requests and instead requires you to use UDP.
You can switch from TCP to UDP in CUCM for outgoing SIP calls on the SIP Trunk Security Profile you have assigned to the SIP Trunk in CUCM (requires a SIP Trunk reset). Note that resetting a RL does not drop active calls, but resetting a SIP Trunk does.
