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
CUCM | Cisco Collaboration

DHCP TFTP Options

by | Feb 23, 2010 | CCME, CUCM, IOS, Lab, Non classé, Written Theory

In order to your DHCP to give the TFTP address to your phones , the common configuration is to use the option 150 which is the main and the more expanded concept used for providing your TFTP. It can provide an IP Address as well an array of IP Address.

This is also the code which you are using under IOS configurations.

But in some old implementation , you can find also the option 66 to give the TFTP to the phones . Option 66 is different in the meaning that you must provide a server name so you need to have DNS enabled . Also you can only pass one parameter!!!

So don’t be too disturbed if you see this option 🙂

SDI/SDL Call Manager Traces

by | Feb 22, 2010 | CUCM, Lab, Non classé, Trace/Monitoring, Written Theory

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

by | Feb 21, 2010 | CUCM, Lab, Non classé, Written Theory

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.