Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
Determining Source of Dropped CM Calls
In today’s Unified Communications environments, communication is critical.When calls drops are reported, it is important to determine why the calls dropped and where the disconnect occurred.In order to achieve this, we will use TripleCombo to quickly analyze CCM traces for call disconnect scenarios including MGCP controlled PRI, H323, and SIP Trunks.
CM (any version)
MGCP Gateways with PRI Interfaces
SIP Trunks (CM 4.1.3 or later)
A reference for setting and collecting CM Traces can be found here:
For SIP trunk calls, under CCM Traces, select only SIP and DA (digit analysis).This will filter the CCM Traces and display only SIP and DA messages in the Debug portion of Triple Combo.Drag and drop the CCM SDI trace file(s) into the top pane of the Triple Combo window.Triple Combo will take some time to parse these files depending on the volume of data.
Triple Combo View:
DA and SIP messages are displayed in the Debug section of TC.Next, we find the called party for our disconnected call.Choose Edit -> Find, or CTRL+F.
Find called number:
The called party for this example is entered, 9725558007.
Here we see the DA for the call that is disconnected.We can right click on the initial SIP Invite and select Filter This (or press CTRL+L).
After filtering just this SIP call-id, we see all of the SIP messages for the call of interest.Next, we look at the BYE message in more detail.
Notice the direction of the BYE message.The RX <- 10.128.105.170 indicates that this message is received by the CM node from the destination of the SIP trunk, in this case 10.128.105.170.With this message, we know to turn our investigation towards the SIP device 10.128.105.170.The Q.850 cause code for this BYE message is 16, which is normal call clearing.
For a listing of Q.850 cause codes, please reference: