This is part of a trace reading video series. The link below is to the main page of the video series.
Here are the logs if you want to download them: hold.zip
Here are the logs if you want to download them: hold_annotated.zip
Here is the NP++ language I am using for the CCM logs: ccm_notepad_language.zip
First we find the dialed digits for when Party A calls Party B using dd="<number dialed>"
Then we can find the Digit Analysis DmPidRes and get the PID for the called device, the first CI, and the CDCC.
Searching on the first CI we can get the second CI.
Going back to the search for CI 1 we can find the SIPCdpc for Party A and After we know the SipCdpc for party 1 we can search on it to quickly get the SIP Call-id for Party A's call leg.
Going to our search results for CI 2 we can get the SIP Call-id for Party B.
Once we have Rarty A and Party B SIP Call-id we can use regular expressions to search on both of them at the same time. This makes following the call easier. This is the string I searched on:
(Call-ID: e0d173e5-26520004-7ab4c4a2-12dd7138@14.48.38.35)|(Call-ID: 8d46c700-7d419aef-da31-626300e@14.48.38.6)
After making the regex search we can just walk through the logs and annotate them.
We also used MOH so we want to find how that was allocated and what MOH device was used. So we searched on the CI 1 because that is the party on hold. Within those search results we looked for the following items : InsertMediaReq, MrmAllocateMohResourceReq, and AllocateMohResourceRes.
NOTE: If you aren't doing Multicast MOH you can still use the same method above to find the Unicast MOH or Tone On Hold device.
Pro Tip: Look in the System Error and Messages documentation if you are every trying to determine enum values from and RTMT alert. It is also a good resource if you are just looking to confirm an enum value you find outside of an RTMT alert. This is what I did in the video; however, if you are pulling the enum value from somewhere other than an RTMT alert, you might not find what you are looking for in this guide.
Here is a screenshot of the media resource type enum values I showed in the video.
More information from the call can be gathered by going back through the search outputs of the CI's, SIPCdpc's, SIPStationCdfc's, and CDCC's.
