Call Ended ("16" Disconnect on your side, as expected since the call was transferred):
If you can get the device names and calling / called / transferred (final called) numbers that are involved in this call you can match them in the CDR record and give yourself a better idea what's going on. But like Manish said previously, the call signalling thinks this call was transferred as it was intended to. If the call was lost during transfer check the gateway / trunk the call was transferred to, most likley your problem is not call signalling on the call manager / cme that generated this CDR record.
And as far as the version of CME you are using, yes it is older, but CME went from 4.x to 8.x, which not as old as it may seem. If you're interested in upgrading, review the IOS you would like to move to, particularly the caveats associated with it, and if it's a good match upgrade.
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...