Starting with Callmanager 9, the System Diagnostic Interface (SDI) traces are now recorded within the Signaling Distribution Layer (SDL) trace files. To date, the documentation doesn't mention this new way of logging traces:
It is vaguely mentioned but doesn't go into detail:
RTMT still shows the option to run real time traces from the System Diagnostic Interface (SDI), which will result in the following error message:
"Trace not found for service name "Cisco CallManager" and trace type "sdi". Please check if this service is running and try again."
To work around this, just select SDL during the setup wizard:
Same thing applies if you need to collect SDI traces and don't find the option through the Remote Browse option:
In such case, download the SDL traces since they will contain all of the signaling you would expect from SDI files.
Does SDL has the same level of tracing that was independently written in old SDI, pre 9.x? It seems like not all trace line that were part of pre 9.x in SDI made it to SDL. Are their special settings or flag that need to be enabled to get same level of SDI tracing into SDL in 9.x?
Do you have an example of things missing from last version? Interleaved traces do inted to reduce the amount of lines per event so... That might be the situation you are experiencing.
this combination is pain. can't see anything legid in this sdl file
which traces do we need to have enabled so we can trace the call, debug sip etc
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: