by Olivier | Feb 25, 2010 | CUCM, Lab, Non classé, SCCP, SIP, Written Theory
Regarding security endpoints, you have 2 opportunities :
- Newer phones are using more an existing Mafufacturing Installed Certificate , this is the MIC
- Meanwhile , old phones will use a Locally Significant Certificate ( LSC) which will be installed by the Certificate Authority Proxy Function (CAPF)
As LSC must be a transaction between the Ip phone and the CAPF , here is the process as it is issued :
- IP Phone generates a public/private key pair
- A TLS Session is established with the CAPF Service and the keys and identity are sent from the phone to CAPF
- The CAPF Service creates and sends an LSC to the phone
- The IP Phone installs the LSC
Also for info, the CAPF Service must be in the phone CTL file , which is downloaded from the TFTP when the phone boots .
by Olivier | Feb 24, 2010 | CUCM, Lab, Non classé, Written Theory
Cast is the protocol used into the conversation between the webcam and your IP Phone.
It uses TCP/4224 in both direction ( easy to implement if you are firewalling your networks).
Pay also attention that the communication is only between the IP Phone and the webcam . CUCM is not involved at all in that “conversation” except for the TFTP config download.
by Olivier | 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 🙂
by Olivier | Feb 23, 2010 | CUCM, Non classé, SCCP, Trace/Monitoring, Written Theory
In the CUCM traces , you can find a lot of StationInit and StationD .
What are they corresponding ?
(more…)
by Olivier | Feb 22, 2010 | CUCM, Lab, Non classé, Trace/Monitoring, Written Theory
Real-Time Monitoring Tool (RTMT) runs as a client-side application and uses HTTPS with TCP to monitor device status,system performance,device discovery and CTI Applications in the cluster
by Olivier | 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
