All other Skinny phones with CDP support, with the exception of ATA devices
These phones do not require special Cisco ER configuration. However, ensure that you enable CDP (Cisco Discovery Protocol) on the switches.
Note Cisco ER 1.2 displays the phone type for the Cisco IP Phone models 7902, 7905G, and 7912 as "OTHER."
Note Although ATA phones support CDP and SCCP, Cisco ER cannot automatically track them. You can add ATA phones manually and assign them to an ERL. Cisco ER will route calls from ATA phones based on the assigned ERL.
Phones automatically tracked using CAM tables
Cisco IP SoftPhone 1.2 and 1.3
Cisco IP Phone models 12 SP+ and VIP 30
To automatically track these phones, you must enable CAM tracking when you add the switches to the Cisco ER configuration. Phones that do not use CDP are tracked using the CAM table on all supported switch platforms for Native and AUX Vlans.
Phones that you can track using IP subnet
Wireless phones, such as Cisco Wireless IP Phone 7920 and Cisco IP SoftPhones running on 802.11b
Supported Cisco IP Phones connected to Cisco or third-party switches that are not discovered or recognized by Cisco ER
To track these phones, you must configure the subnet and then assign ERLs to the configured subnets.
Phones that you can manually define
Analog phones, for example, phones connected to VG248 and ATA devices
Generic H.323 or SIP endpoints
Any phone otherwise supported for automatic tracking that is connected to an unsupported switch port
These phones are only supported if their calls are routed by Cisco CallManager.
So to understand you correctly. If I have 7902, 7912, 7940, and 7960 phones, as long as I have CDP enabled on the switches there is no additional configuration requirements. As long as I have CTI ports available then I am ok.
As Tommer indicated be careful when you add new switches, as there is a procedure for assigning the switchports to the correct ELIN etc. But if you are just adding new phones to an existing infrastructure you should be good to go. Here is some info on what the CTI ports are used for and some other procedures to look at after the phones have been added;
Creating the Required CTI Ports
Cisco Emergency Responder (Cisco ER) uses CTI ports to call onsite alert (security) personnel when someone makes an emergency call. You should have enough CTI ports so that each person assigned to an ERL can receive a call. The number of ports you configure is the number of simultaneous calls Cisco ER can make to these personnel. It does not relate to the number of emergency calls Cisco ER can handle or forward to the PSAP?there is no configurable limitation to the number of simultaneous emergency calls that Cisco ER can handle.
Before You Begin
Cisco ER requires that the CTI port extension numbers be in succession, so you must find a block of unused extensions. For example, if you want to create four CTI ports starting at 3001, then 3001, 3002, 3003, and 3004 must all be available.
Make sure that you have a look at the following after you have added a large number of phones to make sure everything is working as expected;
Identifying Unlocated Phones
If Cisco Emergency Responder (Cisco ER) cannot locate a phone, it places the phone in the Default ERL and puts it in a list of unlocated phones. Using this list, you can reassign the phones to a different ERL, or you can use the list to help identify the problems that are preventing Cisco ER from locating the phones.
These are some things that can prevent Cisco ER from locating a phone:
The phone is attached to a switch that is not defined in Cisco ER.
The phone is connected to an unsupported device, such as a router port, a hub connected to a router, or an unsupported switch.
The switch to which the phone is connected is currently unreachable, for example, it does not respond to SNMP queries.
The phone has moved to a switch served by a different Cisco ER group. If this is the case, the Cisco ER group name is shown for the phone in the unlocated phones list.
No IP subnet is configured for the phone.
Because Cisco ER cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Cisco ER from locating these phones on your network. If you cannot resolve the problems by defining switches in Cisco ER, or by moving phones to supported switch ports, you can manually assign a phone to an ERL.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...