 CHAPTER 3 & 4  Understanding the Cisco IP Phone Concepts and Registration  Getting Familiar with CME Administration

Connecting to the Network:

Connecting the Phone to the Network: Ports: RS232 – Connects to an expansion module 10/100 SW – Connect to the network via a switch or integrated switch 10/100 PC – Connect to a Co-located PC

Power over Ethernet (PoE) or Inline Power (Cisco): A Cisco phone can be powered by either Power over Ethernet, Inline power or power brick. Inline power was Cisco’s pre-standard answer to providing power.  Switch send a Fast link Pulse (FLP) to device.  Cisco pre-standard would loop FLP signal back  When switch receives FLP back it applies six point three watts (6.3W) to the line  Device boots and uses Cisco Discovery Protocol (CDP) to communicate with Cisco Devices

Power over Ethernet (PoE) or Inline Power (Cisco) continued: Power over Ethernet (PoE) or IEEE 802.3af  Constant small DC current applied to lines  When compatible device is connected a precession resistor feeds back current to PoE supply device.  When feedback is detected a specific amount of power is supplied to the device.  Class to W, allocated 15.4W  Class to 3.84W, allocated 4.0W  Class to 6.49W, allocated 7.0W  Class to 12.95W, allocated 15.4W

Power over Ethernet (PoE) or Inline Power (Cisco) continued: A power brick or separate power source can be used to supply power by a separate power connection to phone. Not normally supplied with phone. Power patch panel may be used to augment non-PoE switches or devices An in-line coupler may be used for each device to inject power into the Ethernet connection. A Cisco phone with a sidecar module added to support additional lines will exceed the 802.3af power supplied and need a power brick adapter.

Power over Ethernet (PoE) or Inline Power (Cisco) continued: Cisco Power Patch Panel: Cisco Power Brick:

Power over Ethernet (PoE) or Inline Power (Cisco) continued: PoE in-line injector:

Power over Ethernet (PoE) or Inline Power (Cisco) continued:

Using Virtual LAN’s (VLAN’s) to Subdivide Switch: A VLAN = a Broadcast Domain = An IP Subnet A virtual division of the switch. Routers are used to interconnect VLAN’s Benefits:  Increased performance  Improved manageability  Physical topology independence  Increased security

Switch Trunking: Switches can be interconnected via a single connection Uses either IEEE 802.1Q (Standard) or Inter- Switch Link protocol (ISL) a Cisco proprietary. Native VLAN carries all management information All frames are “Tagged” to cross the trunk link except for the native VLAN frames. Tagging adds bits onto frame which are removed prior to exiting the switch on any line not a trunk Tagging adds delay Tagging saves physical ports VLAN’s are distributed to all switches via Virtual Trunking Protocol (VTP)

Virtual Trunking Protocol: Switches exchange VLAN information automatically VTP Domain Names and passwords are case sensitive VTP Modes are server, client or transparent VTP Server allows the creation or deletion of VLAN’s throughout system. VLAN information is saved in switch memory VTP Client allows only the acceptance of VLAN’s from the server. Information is not stored in memory. VTP Transparent mode allows the creation or deletion of VLAN’s of local significance only. VLAN information is stored in switch memory. Will pass VTP information to other switches within the same domain.

Vlan Tagging: Frames are “Tagged” to identify what vlan they are associated with prior to being trunked. The “Tag” is removed when the frame exits the switch via an assess port.

Vlan Tagging: When an attached computer or device, sends data to the switch via the Cisco IP Phone it is not tagged and in the vlan associated with the Access Port. All VoIP traffic entering the port from the Cisco IP Phone is “tagged” with the appropriate Voice Vlan tag.

Creating VLAN’s on a Switch: Switch(config)#vlan 10 Switch(config-vlan)#name DATA Switch(config-vlan)#vlan 50 Switch(config-vlan)#name VOICE Switch(config-vlan)#exit Switch(config)#int fa0/1 Switch(config-if)#switchport trunk encap dot1q Switch(config-if)#switchport mode trunk Switch(config-if)#switchport trunk native vlan 1 Switch(config-if)#int fa0/2 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 10 Switch(config-if)#switchport voice vlan 50 Switch(config-if)#end Switch#

Assigning ports to VLAN’s on a Switch: Switch(config)#interface range fa0/2-24 Switch(config-if-range)#switchport mode access Switch(config-if-range)#switchport access vlan 50 Switch(config-if-range)#switchport voice vlan 10 Switch(config-if-range)#spanning-tree portfast Switch(config-if-range)#end Switch# Note: It is now recommended to configure switch ports as Access ports rather then Trunk ports!

Switch>ena Switch#config t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#vlan 10 Switch(config-vlan)#name VOICE Switch(config-vlan)#vlan 50 Switch(config-vlan)#name DATA Switch(config-vlan)#int range fa0/2-24 Switch(config-if-range)#switchport mode access Switch(config-if-range)#switchport access vlan 50 Switch(config-if-range)#switchport voice vlan 10 Switch(config-if-range)#end Switch# show vlan brief VLAN Name Status Ports default active Fa0/1, Gi0/1, Gi0/2 10 VOICE active Fa0/2, Fa0/3, Fa0/4, Fa0/5 Fa0/6, Fa0/7, Fa0/8, Fa0/9 Fa0/10, Fa0/11, Fa0/12, Fa0/13 Fa0/14, Fa0/15, Fa0/16, Fa0/17 Fa0/18, Fa0/19, Fa0/20, Fa0/21 Fa0/22, Fa0/23, Fa0/24 50 DATA active Fa0/2, Fa0/3, Fa0/4, Fa0/5 Fa0/6, Fa0/7, Fa0/8, Fa0/9 Fa0/10, Fa0/11, Fa0/12, Fa0/13 Fa0/14, Fa0/15, Fa0/16, Fa0/17 Fa0/18, Fa0/19, Fa0/20, Fa0/21 Fa0/22, Fa0/23, Fa0/ fddi-default act/unsup 1003 token-ring-default act/unsup 1004 fddinet-default act/unsup 1005 trnet-default act/unsup Switch#

Creating Dynamic Host Control Protocol (DHCP) on a Router: Router(config)#ip dhcp pool DATA Router(dhcp-config)#network Router(dhcp-config)#default-router Router(dhcp-config)#dns-server Router(dhcp-config)#ip dhcp pool VOICE Router(dhcp-config)#network Router(dhcp-config)#default-router Router(dhcp-config)#dns-server Router(dhcp-config)#option 150 ip Router(dhcp-config)#exit Router(config)#ip dhcp excluded-address Router(config)#ip dhcp excluded-address Router(config)#end Router#

NTP (Network Time Protocol): Synchronize all devices to an atomic clock Will display time and date on Cisco Phones Will date and messages etc… Can use router clock as a time source (not accurate) Router#clock set 14:32:27 23 September 2011 Router(config)#ntp server Router(config)#clock timezone WARWICK -5 Router(config)#clock summer-time EST recurring 2 Sunday March 02:00 1 Sunday November 02:00 Router(config)#end Router# Stratum 1: Atomic clock directly attached Stratum 2: Receives it’s time from a Stratum 1 NTP server Stratum 3: Receives it’s time from a Stratum 2 device

NTP (Network Time Protocol) continued: Router#show ntp associations

IP Phone Boot: 1. IP Phone connects to switchport 2. Switchport senses and supplies PoE 3. Via CDP phone receives voice VLAN information 4. Phone sends DHCP request on voice VLAN and receives IP address, Mask and default-Gateway 5. Once addressed the phone contacts TFTP server (Option 150) and downloads configuration files 6. Phone contacts first call processing center (CME Router) and registers. If unable to contact will contact additional centers as listed in configuration Phone will use either the SIP (Session Initiation Protocol) or SCCP (Skinny Client Control Protocol) SIP will replace SCCP

IP Phone Protocol: Phone will use either the SIP (Session Initiation Protocol) or SCCP (Skinny Client Control Protocol) SIP will replace SCCP Phone protocol and CUCME manager protocol must match Once loaded, the CUCME protocol cannot be changed Phone operating systems can be changed with firmware from Cisco (Must have a CCO account)

Voice_HM(config)#ip http server Voice_HM(config)#ip http secure-server Voice_HM(config)# *Sep 23 17:35:30.149: %PKI-4-NOAUTOSAVE: Configuration was modified. Issue "writ e memory" to save new certificate Voice_HM(config)#username Admin privilege 15 secret cisco Voice_HM(config)#ip http authentication local Voice_HM(config)#line vty 0 4 Voice_HM(config-line)#login local Voice_HM(config-line)#transport input telnet ssh Voice_HM(config-line)#int fa0/0 Voice_HM(config-if)#ip address Voice_HM(config-if)#ip dhcp excluded-address Voice_HM(config)#ip dhcp pool OUTSIDE Voice_HM(dhcp-config)#network Voice_HM(dhcp-config)#default-router Voice_HM(dhcp-config)#exit Voice_HM(config)# Setting up HTTP/HTTPS access for Cisco Configuration Professional:

End of Chapter 3 & 4