CIPT1 Notes Cont'd


Types of End Points
  • SCCP
  • SIP
  • H323
  • 3rd Party SIP
  • Audio
  • Video


Phone Startup Process
  1. Phone obtains power from switch or powerblock
  2. Phone loads locally stored image(PhoneLoad)
  3. If no local voice VLAN ID is configured the Cisco IP Phone sends out a CDP frame with a VOIP VLAN query
  4. If the Cisco switch has a voice VLAN configured it will send out a CDP frame with the VLAN ID for the phone
  5. If DHCP is enabled it requests IP and TFTP server information otherwise it uses static
  6. Phone connects to TFTP and requests files in the following order
    1. CTLSEP(MAC).tlv
    2. SEP(MAC).cnf.xml (SCCP)
    3. SIP(MAC).cnf (SIP)
  1. If none of the previously requested configuration files was found the phone requests a default config called XMLDefault.cnf.xml
  2. Cisco IP phone compares its installed phone load version with the load version defined within received configuration file. If the load version is different it requests the new load version from the TFTP server and reboots
  3. The phone tries to register at the Unified Communications Manager call-processing node
  4. If the phone is already configured within CUCM it will successfully register and will be intrstucted by SCCP messages to set the display
  5. If localization or customer ringers are configured for the phone, additional files will be downloaded
  6. If phone is not configured
    1. Autoregistration enabled - phone will be created dynamically
    2. Autoregistration disabled - phone will be rejected for registration


SCCP and SIP

SIP Phones get all their configs from a configuration file. SIP configuration is much larger than SCCP

H323 ENDPOINT
Multiple lines
Voice or Video
Phones don’t register to CUCM only known by IP address
Phones need to have their own dial plan and act as a peer to CUCM
H323 client consumes two DLU's


H323 phones support only a few features compared with Cisco IP phones using SCCP or SIP The features not supported are:
  • MAC
  • Phone button template
  • Softkey template

H323 Phone Configuration Requirements
  • Configure the H323  CUCM Manager with an IP and CUCM


Third Party SIP Phone Support
Configuration is performed on the CUCM and phone itself

SIP Digest Authentication
Digest authentication provides authentication of SIP messages by a username and a keyed MD5 hash
Digest authentication is based on client server model
Used to identify third party SIP since no MAC address is provided in the registration message

Location is where you can configure CAC for centralized call processing

Can setup Device Templates based on device pool to apply to all devices in that pool

Softkey template configures softkey layouts that are assigned to an IP Phone ( idivert)


Common Phone Profile you can set items like Do not Disturb


Autoregistration
Autoregisration only affects new phones that are added to the system.
CUCM Bat can be used after Auto-Registration of Phones

Auto registration needs to define which signaling protocol you will be using. Autoregistration is enabled only on one CUCM based on groups

Steps for Configuring Auto Registration
  1. Verify auto reg phone protocol
  2. Verify that the desired CM group is enabled
  3. For each CUCM of the group enabled or disabled auto-reg
  4. Manual reconfiguration or BAT can be used for changes after

****Enterprise Parameters hold the configuration for signaling protocol of Auto-Registration



Comments

Post a Comment

Popular posts from this blog

HULC LED PROCESS - 3750 High CPU

Image
If you're looking at a switch and you see the HULC LED Process running high. The HULC LED process does some of the following tasks: 1. Check link status on every port 2. If the switch supports POE, it checks to see if there is a power device 3. Transceiver checks 4. Fan status updates 5. Set LED ports 6. Check on temperature status Overall the HULC LED Process is a monitoring process running. During looking into this I turned off all non-used ports since it checks the link status. Then I made sure the environment was good. Two Cisco Bugs: http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsi78581 http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtn42790
Read more

Cisco Tomcat High CPU Utilization 99 percent

Image
So a client was experience slow web interface usage to their calling node. As well RTMT was shooting off the alert. The alert is for Call Process CPU Node Pegging.  The culprit tomcat! Cisco Tomcat Service -  In enterprise edition this is a web server service. In the business edition (BE Servers) this uses the web server and unity utilizes the service as well. Log in to each call manager node and issue the following command: show process load cpu **OUTPUT** top - 08:55:48 up 340 days, 4:03, 1 user, load average: 4.64, 3.25, 2.98  Tasks: 142 total, 2 running, 140 sleeping, 0 stopped, 0 zombie  Cpu(s): 16.3%us, 3.4%sy, 0.0%ni, 80.1%id, 0.1%wa, 0.0%hi, 0.2%si, 0.0%st  Mem: 4016964k total, 3856400k used, 160564k free, 29904k buffers  Swap: 2064280k total, 1664k used, 2062616k free, 598124k cached  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND  8065 tomcat 25 0 2317m 1.9g 22m S 99.4 50.4 358084:37 tomcat  1 root 15 ...
Read more