Warning: Undefined array key "kkmods_kkpostslider" in /home/clients/bb1b7c38f63c1b363aa0114be7911e68/web/collaboration/wp-content/plugins/kk-divi-mods/kk_divi_mods.php on line 67
Written Theory | Cisco Collaboration

SDI/SDL Call Manager Traces

For call processing under the CUCM , you can find 2 types of traces :

  • System Diagnostic Interface (SDI) : SDI informations are traces from services and logs from run-time event.
  • System Diagnostic Layer (SDL) : SDL informations are traces from services as CUCM , CTI Manager and it stores logs state transitions between the node.

Most of the time , SDI traces will be the traces where you can find all stimuli and all interesting call processing traces regarding your phones. With a little knowledge ,it is not very difficult to read these traces

SDL traces are the transition states between the nodes and they are used more by Cisco TAC

Route Plan Hierarchy

Just a little reminder to say that the logical decision to route a call  is based on the following order:

Route Pattern => Route List => Route Groups => Gateway .

But take also in mind that the configuration order is the reverse path.

PVID0 Specifications

As we have already seen it before , if the voice gateway is unable to match an inbound leg for the call , your call will take the properties of the PVID0 .

Don’t forget that you can’t update any properties if the PVID0 is hitted .

Let’s review then the specificities of this default dial-peer:

For POTS dial-peer

  • No IVR applications possible

For VOIP dial-peer

  • Any codec
  • fax-rate voice
  • ip precedence 0
  • No Resource Reservation Protocol ( RSVP)
  • VAD enabled

Outbound Dial Peer leg matching order

As seen with the inbound dial-peer matching , outbound matching is much easier as the dial-peer matches on the destination-pattern expression.
Then the outbound will be selected with the port if you have a POTS dial-peer or will take the session-target in you have a VOIP dial-peer