Introduction

This document describes how to configure and troubleshoot wireless IP phones registration to Cisco Unified Communications Manager (CUCM).

The Cisco wireless IP phones are adaptable for users that require the ability to unplug the wired network connection and remain connected.

Contributed by Luis Segnini, and Kenny Araya, Cisco TAC Engineers.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

• Wireless architecture
• Wireless IP phones configuration
• CUCM basic configuration

Components Used

• Cisco Unified Communications Manager 8.6 or later
• Wireless IP phone models (792X, 9971, 8821)

The following guide is based on Cisco Unified 9971 IP phone model. Configuration might vary based on the IP phone model.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Configuration

Cisco Unified Wireless LAN Controller and Access Points

Wireless Local Area Network (WLAN) Settings

It is recommended to have a separate Service Set Identifier (SSID) for the IP phone. However, if there is an existing SSID configured to support voice capable Cisco Wireless LAN endpoints already, then that WLAN can be utilized instead.

The SSID to be used by the IP phone can be configured to only apply to a certain 802.11 radio type. 

It is recommended to have the IP phone operate on the 5 GHz band since it has many channels available and not as many interferers as the 2.4 GHz band.

Ensure that the selected SSID is not utilized by any other wireless LANs as that could lead to failures when powering on or during roaming; especially if a different security type is utilized.

In order to utilize Cisco Centralized Key Management (CCKM), enable Wi-Fi Protected Access (WPA) 2 policy with Advanced Encryption Standard (AES) encryption and 802.1x + CCKM for authenticated key management type when the IP phone is running firmware version 9.1(1) or later in order to enable fast secure roaming.

If the IP phone is running firmware version prior to 9.1(1), then enable WPA policy with Temporal Key Integrity Protocol (TKIP) encryption and 802.1x + CCKM for authenticated key management type in order to enable fast secure roaming.

The Wi-Fi Multimedia (WMM) policy should be set to "Required" only if the IP phone or other WMM enabled phones will be using this SSID. If there are none-WMM clients existing in the WLAN, it is recommended to put those clients on another SSID / WLAN. If non-other WMM clients must utilize the same SSID as the IP phone, then ensure the WMM policy is set to "Allowed".

Enable 7920 Access Point (AP) Call Admission Control (CAC) to advertise Quality of Service (QoS) Basic Service Set (QBSS) to the client.   

Configure Enable Session Timeout as necessary per your requirements.

It is recommended to either disable the session timeout or extend the timeout (e.g. 24 hours / 86400 seconds) to avoid possible interruptions during audio calls. If disabled it avoids any potential interruptions altogether, but session timeout can help to re-validate client credentials periodically to ensure that the client is using valid credentials.

Enable Aironet Extensions (Aironet IE), Peer to Peer (P2P) Blocking Action must be disabled. Configure Client Exclusion as necessary, Off Channel Scanning Defer can be tuned to defer scanning for certain queues as well as the scan defer time.  

The Maximum Allowed Clients per AP Radio can be configured as necessary.

Dynamic Host Configuration Protocol (DHCP) Address Assignment required must be disabled.

Management Frame Protection must be set to "Optimal" or "Disabled".

For optimal battery performance and quality, use a Delivery Traffic Indication Message (DTIM) period of 2 with a beacon period of 100 ms.

Ensure Client Load Balancing and Client Band Select are disabled.

Controller Settings

Ensure the Cisco Unified Wireless LAN Controller hostname is configured correctly.

Enable Link Aggregation (LAG) if utilizing multiple ports on the Cisco Unified Wireless LAN Controller.

Configure the desired AP multicast mode. In releases prior to 6.0, Aggressive Load Balancing was configured in the General Controller settings. In 6.0 and later, this is referred to as Client Load Balancing and is configurable under the WLAN configuration (SSID settings).

802.11 Network Settings

If using 5 GHz, ensure the 802.11a network status is "Enabled". Set the Beacon Period to 100 ms.

Ensure that Dynamic Transmit Power Control (DTPC) support is enabled. If using Cisco 802.11n Access Points, ensure ClientLink is enabled. With the current releases, Maximum Allowed Clients can be configured.

It is recommended to set 12 Mbps as the mandatory (basic) rate and 18 - 24 or 18 - 54 Mbps as supported (optional) rates; however some environments may require 6 Mbps to be enabled as a mandatory (basic). 36 - 54 Mbps can optionally be disabled, if there are not applications that can benefit from those rates (e.g. video).

Enable CCX Location Measurement.

Configure the Cisco Unified IP Phone 9971

To configure the Wi - Fi settings on the IP phone, use the keypad and touch screen to navigate to Applications Button > Administrator Settings > Network Setup > WLAN Setup.

Wireless LAN Settings

Use the following guidelines to configure the wireless LAN profile.

• Ensure that Wireless is set to "On".
• WLAN Sign in Access can be set to On to give shortcut access in the Applications menu in order to update the username or password.
• Enter the SSID for the voice wireless LAN, which is case sensitive.

The Cisco Unified IP Phone 9971 supports a single wireless LAN profile that allows a single SSID.

Three different 802.11 modes are available.

• Auto
• 802.11a
• 802.11b/g

Auto mode will scan both 2.4 and 5 GHz channels and attempt to associate to the access point with a 5 GHz signal if the configured network is available.

802.11a mode will only scan 5 GHz channels and 802.11b/g mode will only scan 2.4 GHz channels, then will attempt to associate to an access point if the configured network is available.

Configure your IP phone to use Open with Wired Equivalent Privacy (WEP) or Shared Key for the security mode, enter the static WEP key information that matches the access point configuration.

• In the IPv4 Setup, select whether to use DHCP or configure static IP information.
• If option 150 or 66 is not configured to provide the Trivial File Transfer Protocol (TFTP) server’s IP address via the network’s DHCP scope, then set Alternate TFTP to "Yes" and enter the IP address of the TFTP Server.

Configure Cisco Unified Communications Manager

Step 1. Configure the proper Phone button Template for the IP phone.

 Step 2. Add the IP Phone to CUCM.

 Step 3. Complete the required fields.

 Step 4. Assign the newly created Phone Button Template and Softkey template.

 Step 5. Use a non-secure Profile for the IP phone.

Security profiles can be utilized to enable authenticated mode or encrypted mode, where signaling, media and configuration file encryption is then enabled. The Certificate Authority Proxy Function (CAPF) must be operational in order to utilize a Locally Signed Certificate (LSC) with a security profile. The Cisco Unified Wireless IP Phone 7925G, 7925G - E X, and 7926 G have a Manufacturing Installed Certificate (MIC), which can be utilized with a security profile as well.

Verification

Collect Console Logs from the IP phone. We can see the different messages being exchanged between the IP Phone and Access Point.

The IP phone starts scanning the media for an available SSID.

09039 08-10 09:33:32.750 649 668 INF wlanmgr : [1298@wm_drv_mrvl.c] State change(1542), DISCONNECTED -> SCANNING
09040 08-10 09:33:32.750 685 2805 DEB LibWifi : wifi_wait_for_event(CTRL-EVENT-STATE-CHANGE id=0 state=3)
09041 08-10 09:33:32.750 685 2805 DEB LibWifi : wifi_wait_for_event()
09042 08-10 09:33:35.390 1063 2652 INF Unknown : VVMService: Waiting for 39961 ms before attempting to reconnect.
09043 08-10 09:33:35.468 685 807 DEB StateMachine: handleMessage: E msg.what=401431
09044 08-10 09:33:35.468 685 807 DEB StateMachine: processMsg: AdapterConnectedState
09045 08-10 09:33:35.468 685 807 VBS EthernetStateMachine: AdapterConnectedState{ what=401431 when=-1ms }
09046 08-10 09:33:35.468 685 807 DEB StateMachine: handleMessage: X
09047 08-10 09:33:36.617 649 664 INF wlanmgr : [1298@wm_drv_mrvl.c] State change(1559), SCANNING -> INACTIVE
09048 08-10 09:33:36.617 210 313 INF SWMAN : nl_ipThrd():recvmsg() len=56 
09049 08-10 09:33:36.617 210 313 INF SWMAN : NL event: 16 found; device idx:6 flag :0x1002
09050 08-10 09:33:36.617 210 313 INF SWMAN : Got a messge NEW_LINK message!!!
09051 08-10 09:33:36.617 685 2805 DEB LibWifi : wifi_wait_for_event(CTRL-EVENT-STATE-CHANGE id=0 state=2)
09052 08-10 09:33:36.617 685 2805 DEB LibWifi : wifi_wait_for_event()
09053 08-10 09:33:36.617 685 804 DEB EthernetStateMachine: Interface mlan0 LinkStateChanged: down

The IP phone starts associating with the SSID.

09054 08-10 09:33:36.718 649 668 INF wlanmgr : [1293@wm_drv_mrvl.c] State change(2221), "", INACTIVE -> ASSOCIATING
09055 08-10 09:33:36.718 649 668 INF wlanmgr : [2226@wm_drv_mrvl.c] Connecting to "lcorream Wireless", a0:55:4f:c2:ec:eb, chan 56, rssi -56, load 4
09056 08-10 09:33:36.718 685 2805 DEB LibWifi : wifi_wait_for_event(CTRL-EVENT-STATE-CHANGE id=-1 state=5)
09057 08-10 09:33:36.718 685 2805 DEB LibWifi : wifi_wait_for_event()
09058 08-10 09:33:36.734 2348 2348 VBS Settings.AccessPoint: refresh: for SSID lcorream Wireless
09059 08-10 09:33:36.734 2348 2348 VBS Settings.CiscoWifiModifiable: Translating Wifi modifiable state 0 for SSID: "lcorream Wireless"

The IP phone successfully associates with the Access Point.

09093 08-10 09:33:38.835 649 664 INF wlanmgr : [1293@wm_drv_mrvl.c] State change(2479), "lcorream Wireless", ASSOCIATING -> ASSOCIATED
09094 08-10 09:33:38.835 210 313 INF SWMAN : nl_ipThrd():recvmsg() len=112 
09095 08-10 09:33:38.835 210 313 INF SWMAN : NL event: 16 found; device idx:6 flag :0x1003
09096 08-10 09:33:38.835 210 313 INF SWMAN : Got a messge NEW_LINK message!!!
09097 08-10 09:33:38.835 210 313 INF SWMAN : nl_ipThrd():recvmsg() len=80 
09098 08-10 09:33:38.835 210 313 INF SWMAN : NL event: 16 found; device idx:6 flag :0x1003
09099 08-10 09:33:38.835 210 313 INF SWMAN : Got a messge NEW_LINK message!!!
09100 08-10 09:33:38.835 210 313 INF SWMAN : nl_ipThrd():recvmsg() len=80 
09101 08-10 09:33:38.835 210 313 INF SWMAN : NL event: 16 found; device idx:6 flag :0x1003
09102 08-10 09:33:38.835 210 313 INF SWMAN : Got a messge NEW_LINK message!!!
09103 08-10 09:33:38.835 210 313 INF SWMAN : nl_ipThrd():recvmsg() len=132 
09104 08-10 09:33:38.835 210 313 INF SWMAN : NL event: 16 found; device idx:6 flag :0x1003
09105 08-10 09:33:38.835 210 313 INF SWMAN : Got a messge NEW_LINK message!!!
09106 08-10 09:33:38.835 210 313 INF SWMAN : nl_ipThrd():recvmsg() len=68 
09107 08-10 09:33:38.835 210 313 INF SWMAN : NL event: 16 found; device idx:6 flag :0x1003
09108 08-10 09:33:38.835 210 313 INF SWMAN : Got a messge NEW_LINK message!!!
09109 08-10 09:33:38.835 685 804 DEB EthernetStateMachine: Interface mlan0 LinkStateChanged: down
09110 08-10 09:33:38.843 685 804 DEB EthernetStateMachine: Interface mlan0 LinkStateChanged: down
09111 08-10 09:33:38.843 685 2805 DEB LibWifi : wifi_wait_for_event(CTRL-EVENT-STATE-CHANGE id=1 state=6)
09112 08-10 09:33:38.843 685 804 DEB EthernetStateMachine: Interface mlan0 LinkStateChanged: down

The IP phone starts extended authentication.

09146 08-10 09:33:39.039 649 664 INF wlanmgr : [3492@wm_drv_mrvl.c] Supplicant event: EAP-STARTED EAP authentication started
09147 08-10 09:33:39.039 649 664 INF wlanmgr : [3492@wm_drv_mrvl.c] Supplicant event: EAP-PROPOSED-METHOD vendor=0 method=25
09148 08-10 09:33:39.039 649 664 INF wlanmgr : [3492@wm_drv_mrvl.c] Supplicant event: EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
09149 08-10 09:33:39.046 225 225 INF PAE : paeGetPort(): recvd macAddress: a0:55:4f:c2:ec:eb
09150 08-10 09:33:39.046 210 749 INF SWMAN : mdk_get_source_port(): mac = a0:55:4f:c2:ec:eb
09151 08-10 09:33:39.046 210 749 INF SWMAN : get_source_port(): START, MAC=0xa0554fc2eceb
09152 08-10 09:33:39.054 210 749 INF SWMAN : get_source_port(): DONE, cdk_port = -1, port = -1, index = 2
09153 08-10 09:33:39.054 210 749 INF SWMAN : mdk_get_source_port(): rc = 0, port = -1
09154 08-10 09:33:39.054 225 225 INF PAE : paeGetPort(): 340 bytes rcvd from SWMAN, rcvLen: 340
09155 08-10 09:33:39.054 225 225 INF PAE : paeGetPort(): port obtained = -1 
09156 08-10 09:33:39.054 225 225 WRN PAE : PAE rcv: msg received from unknown port, drop...
09157 08-10 09:33:39.125 225 225 INF PAE : paeGetPort(): recvd macAddress: a0:55:4f:c2:ec:eb
09158 08-10 09:33:39.125 2348 2348 VBS Settings.AccessPoint: refresh: for SSID lcorream Wireless
09159 08-10 09:33:39.125 2348 2348 VBS Settings.CiscoWifiModifiable: Translating Wifi modifiable state 0 for SSID: "lcorream Wireless"
09160 08-10 09:33:39.125 2348 2348 VBS Settings.CiscoWifiModifiable: wifi configuration modifiable state value= 0 internal string value: local
09161 08-10 09:33:39.125 210 749 INF SWMAN : mdk_get_source_port(): mac = a0:55:4f:c2:ec:eb
09162 08-10 09:33:39.125 210 749 INF SWMAN : get_source_port(): START, MAC=0xa0554fc2eceb

The IP phone checks server's certificate for PEAP.

09163 08-10 09:33:39.132 649 664 INF wlanmgr : [3492@wm_drv_mrvl.c] Supplicant event: EAP-PEER-CERT depth=0 subject='/CN=CUCM-Srv-01.cucm.cotac.com'
09164 08-10 09:33:39.132 210 749 INF SWMAN : get_source_port(): DONE, cdk_port = -1, port = -1, index = 2
09165 08-10 09:33:39.132 649 664 INF wlanmgr : [3492@wm_drv_mrvl.c] Supplicant event: EAP-PEER-CERT depth=0 subject='/CN=CUCM-Srv-01.cucm.cotac.com'
09166 08-10 09:33:39.132 210 749 INF SWMAN : mdk_get_source_port(): rc = 0, port = -1
09167 08-10 09:33:39.132 225 225 INF PAE : paeGetPort(): 340 bytes rcvd from SWMAN, rcvLen: 340
09168 08-10 09:33:39.132 225 225 INF PAE : paeGetPort(): port obtained = -1 
09169 08-10 09:33:39.132 225 225 WRN PAE : PAE rcv: msg received from unknown port, drop...
09170 08-10 09:33:39.132 225 225 INF PAE : paeGetPort(): recvd macAddress: a0:55:4f:c2:ec:eb
09171 08-10 09:33:39.132 649 664 INF wlanmgr : [3492@wm_drv_mrvl.c] Supplicant event: EAP-PEER-CERT depth=0 subject='/CN=CUCM-Srv-01.cucm.cotac.com'
09172 08-10 09:33:39.140 210 749 INF SWMAN : mdk_get_source_port(): mac = a0:55:4f:c2:ec:eb
09173 08-10 09:33:39.140 210 749 INF SWMAN : get_source_port(): START, MAC=0xa0554fc2eceb
09174 08-10 09:33:39.148 210 749 INF SWMAN : get_source_port(): DONE, cdk_port = -1, port = -1, index = 2
09175 08-10 09:33:39.148 210 749 INF SWMAN : mdk_get_source_port(): rc = 0, port = -1
09176 08-10 09:33:39.148 225 225 INF PAE : paeGetPort(): 340 bytes rcvd from SWMAN, rcvLen: 340
09177 08-10 09:33:39.148 225 225 INF PAE : paeGetPort(): port obtained = -1

Extended authentication passes successfully.

09226 08-10 09:33:39.312 649 664 INF wlanmgr : [3492@wm_drv_mrvl.c] Supplicant event: EAP-SUCCESS EAP authentication completed successfully
09227 08-10 09:33:39.312 210 749 INF SWMAN : mdk_get_source_port(): mac = a0:55:4f:c2:ec:eb
09228 08-10 09:33:39.312 210 749 INF SWMAN : get_source_port(): START, MAC=0xa0554fc2eceb
09229 08-10 09:33:39.320 649 664 INF wlanmgr : [3492@wm_drv_mrvl.c] Supplicant event: CONNECTED - Connection to a0:55:4f:c2:ec:eb completed (auth) [id=0 id_str=]

Connection is successful.

09230 08-10 09:33:39.320 649 664 INF wlanmgr : [1293@wm_drv_mrvl.c] State change(2592), "lcorream Wireless", ASSOCIATED -> CONNECTED
09231 08-10 09:33:39.320 210 749 INF SWMAN : get_source_port(): DONE, cdk_port = -1, port = -1, index = 2
09232 08-10 09:33:39.320 649 664 INF wlanmgr : [56@wm_util.c] Wifi connected[lcorream Wireless]: a0:55:4f:c2:ec:eb, co-cucm, Ch: 56, RSSI: -57
09233 08-10 09:33:39.320 210 749 INF SWMAN : mdk_get_source_port(): rc = 0, port = -1
09234 08-10 09:33:39.320 225 225 INF PAE : paeGetPort(): 340 bytes rcvd from SWMAN, rcvLen: 340
09235 08-10 09:33:39.320 225 225 INF PAE : paeGetPort(): port obtained = -1 
09236 08-10 09:33:39.320 225 225 WRN PAE : PAE rcv: msg received from unknown port, drop...
09237 08-10 09:33:39.320 225 225 INF PAE : paeGetPort(): recvd macAddress: a0:55:4f:c2:ec:eb
09238 08-10 09:33:39.320 685 804 DEB EthernetStateMachine: Interface mlan0 LinkStateChanged: up
09239 08-10 09:33:39.320 210 313 INF SWMAN : nl_ipThrd():recvmsg() len=1012 
09240 08-10 09:33:39.320 210 313 INF SWMAN : NL event: 16 found; device idx:6 flag :0x11043
09241 08-10 09:33:39.320 210 313 INF SWMAN : Got a messge NEW_LINK message!!!

The IP phone looks for a DHCP lease.

09588 08-10 09:33:39.703 3246 3246 DEB dhcpcd : broadcasting for a lease of 192.168.110.236
09589 08-10 09:33:39.703 3246 3246 DEB dhcpcd : Starting to send message numberof message=0 
09590 08-10 09:33:39.703 3246 3246 DEB dhcpcd : REQUESTING SENT 
09591 08-10 09:33:39.703 3246 3246 DEB dhcpcd : STATE_RENEWING STATE_REBINDING mlan0 
09592 08-10 09:33:39.703 3246 3246 DEB dhcpcd : *sending DHCP_REQUEST with xid 0xc89244e9, next in 3.57 seconds
09593 08-10 09:33:39.703 3246 3246 DEB dhcpcd : get_tos_byte() = 96
09594 08-10 09:33:39.703 3246 3246 DEB dhcpcd : Set ToS byte for DHCP to configured value of [96]
09595 08-10 09:33:39.703 2348 2348 VBS Settings.AccessPoint: onBindView: [lcorream Wireless] modifiable state was empty, setting visibility to gone
09596 08-10 09:33:39.710 2348 2348 VBS Settings.AccessPoint: onBindView: [lcorream Wireless] modifiable state was empty, setting visibility to gone
09597 08-10 09:33:39.718 2348 2348 VBS Settings.AccessPoint: onBindView: [lcorream Wireless] modifiable state was empty, setting visibility to gone
09598 08-10 09:33:39.726 2348 2348 VBS Settings.AccessPoint: onBindView: [CUCM-PEAP] modifiable state was empty, setting visibility to gone
09599 08-10 09:33:39.734 2348 2348 VBS Settings.AccessPoint: onBindView: [CUCM-LAB] modifiable state was empty, setting visibility to gone
09600 08-10 09:33:39.742 2348 2348 VBS Settings.AccessPoint: onBindView: [Kemirand] modifiable state was empty, setting visibility to gone
09601 08-10 09:33:39.750 2348 2348 VBS Settings.AccessPoint: onBindView: [Flex_Guest] modifiable state was empty, setting visibility to gone
09603 08-10 09:33:39.765 2348 2348 VBS Settings.AccessPoint: onBindView: [ASA5506W-A] modifiable state was empty, setting visibility to gone
09604 08-10 09:33:39.906 3246 3246 DEB dhcpcd : in handle_dhcp_packet... 
09604 08-10 09:33:39.906 3246 3246 DEB dhcpcd : 
09605 08-10 09:33:39.906 3246 3246 DEB dhcpcd : in handle_dhcp 

The IP phone gets an ack from the DHCP server.

09606 08-10 09:33:39.906 3246 3246 DEB dhcpcd : acknowledged 192.168.110.236 from 192.168.110.122.
09607 08-10 09:33:39.906 3246 3246 DEB dhcpcd : cont_init_retry = OLD:0 NEW:0
09608 08-10 09:33:39.976 3246 3246 DEB dhcpcd : handle_timeout:ifname mlan0 state: 9 
09609 08-10 09:33:40.046 3246 3246 DEB dhcpcd : checking 192.168.110.236 is available on attached networks
09610 08-10 09:33:40.046 3246 3246 DEB dhcpcd : DBG:checking 192.168.110.236 is available on attached networks

The IP phone sends a gratuitous ARP to confirm that the IP is indeed available.

09611 08-10 09:33:40.046 3246 3246 DEB dhcpcd : sending ARP probe (1 of 2), next in 1.94 seconds
09612 08-10 09:33:40.468 685 807 DEB StateMachine: handleMessage: E msg.what=401431
09613 08-10 09:33:40.468 685 807 DEB StateMachine: processMsg: AdapterConnectedState
09614 08-10 09:33:40.468 685 807 VBS EthernetStateMachine: AdapterConnectedState{ what=401431 when=-5ms }
09615 08-10 09:33:40.468 685 807 DEB StateMachine: handleMessage: X
09616 08-10 09:33:41.992 3246 3246 DEB dhcpcd : handle_timeout:ifname mlan0 state: 9 
09617 08-10 09:33:41.992 3246 3246 DEB dhcpcd : sending ARP probe (2 of 2), next in 2.00 seconds
09618 08-10 09:33:43.992 3246 3246 DEB dhcpcd : handle_timeout:ifname mlan0 state: 9 
09619 08-10 09:33:43.992 3246 3246 DEB dhcpcd : binding the DHCP IP address Probe=2
09620 08-10 09:33:43.992 3246 3246 DEB dhcpcd : startup 0 lease of 600
09621 08-10 09:33:43.992 3246 3246 DEB dhcpcd : get_option2addr: 2054072512 
09622 08-10 09:33:43.992 3246 3246 DEB dhcpcd : get_option2addr: 134744072 
09623 08-10 09:33:43.992 3246 3246 DEB dhcpcd : leased 192.168.110.122 for 600 seconds....server 192.168.110.122
09624 08-10 09:33:43.992 3246 3246 DEB dhcpcd : Check values : state=3 mlan0 192.168.110.122 300/600 192.168.110.236
09625 08-10 09:33:43.992 3246 3246 DEB dhcpcd : executing `/system/etc/dhcpcd/dhcpcd-run-hooks', reason BOUND
09626 08-10 09:33:43.992 3246 3246 DEB dhcpcd : Enterning configure_env....

The IP phone receives a DHCP options message.

09627 08-10 09:33:43.992 3246 3246 DEB dhcpcd : option 1*: new_subnet_mask=255.255.255.0
09628 08-10 09:33:43.992 3246 3246 DEB dhcpcd : option 150*: new_cisco_tftp_server=192.168.110.86
09629 08-10 09:33:43.992 3246 3246 DEB dhcpcd : option 3*: new_routers=192.168.110.1
09630 08-10 09:33:43.992 3246 3246 DEB dhcpcd : option 6*: new_domain_name_servers=192.168.110.122 8.8.8.8
09631 08-10 09:33:43.992 3246 3246 DEB dhcpcd : option 15*: new_domain_name=cucm.cotac.com
09632 08-10 09:33:43.992 3246 3246 DEB dhcpcd : option 51*: new_dhcp_lease_time=600
09633 08-10 09:33:43.992 3246 3246 DEB dhcpcd : option 53*: new_dhcp_message_type=5
09634 08-10 09:33:43.992 3246 3246 DEB dhcpcd : option 54*: new_dhcp_server_identifier=192.168.110.122
09635 08-10 09:33:44.257 3246 3246 DEB dhcpcd : configure: mlan0 adding IP address 192.168.110.236
09636 08-10 09:33:44.265 3246 3246 DEB dhcpcd : adding route to 0.0.0.0/0 via 192.168.110.1
09637 08-10 09:33:44.265 3246 3246 DEB dhcpcd : Writing lease file: /dataRoot/.system/misc/dhcp/dhcpcd-mlan0.lease
09638 08-10 09:33:44.265 3246 3246 DEB dhcpcd : executing `/system/etc/dhcpcd/dhcpcd-run-hooks', reason BOUND
09639 08-10 09:33:44.265 3246 3246 DEB dhcpcd : Enterning configure_env....
09640 08-10 09:33:44.265 3246 3246 DEB dhcpcd : option 1*: new_subnet_mask=255.255.255.0
09641 08-10 09:33:44.265 3246 3246 DEB dhcpcd : option 150*: new_cisco_tftp_server=192.168.110.86
09642 08-10 09:33:44.265 3246 3246 DEB dhcpcd : option 3*: new_routers=192.168.110.1
09643 08-10 09:33:44.265 3246 3246 DEB dhcpcd : option 6*: new_domain_name_servers=192.168.110.122 8.8.8.8
09644 08-10 09:33:44.265 3246 3246 DEB dhcpcd : option 15*: new_domain_name=cucm.cotac.com
09645 08-10 09:33:44.265 3246 3246 DEB dhcpcd : option 51*: new_dhcp_lease_time=600
09646 08-10 09:33:44.265 3246 3246 DEB dhcpcd : option 53*: new_dhcp_message_type=5
09647 08-10 09:33:44.265 3246 3246 DEB dhcpcd : option 54*: new_dhcp_server_identifier=192.168.110.122
09648 08-10 09:33:44.265 214 241 INF NETSD : nl_ipThrd():recvmsg() len=60 
09649 08-10 09:33:44.265 210 313 INF SWMAN : nl_ipThrd():recvmsg() len=56 
09650 08-10 09:33:44.265 210 313 INF SWMAN : NL event: 16 found; device idx:6 flag :0x11043
09651 08-10 09:33:44.265 210 313 INF SWMAN : Got a messge NEW_LINK message!!!
09652 08-10 09:33:44.265 685 2805 DEB LibWifi : wifi_wait_for_event(CTRL-EVENT-SCAN-RESULTS Ready)
09653 08-10 09:33:44.265 685 2805 DEB LibWifi : wifi_wait_for_event()
09654 08-10 09:33:44.265 685 804 DEB EthernetStateMachine: Interface mlan0 LinkStateChanged: up
09655 08-10 09:33:44.398 685 3245 INF dhcp_utils: DHCP is started OK
09656 08-10 09:33:44.398 685 3245 DEB NetUtils: android_net_utils_runDhcpCommon() Ipver:4 IP address = 192.168.110.236
09657 08-10 09:33:44.398 685 3245 DEB NetUtils: android_net_utils_runDhcpCommon() Ipver:4 Gateway = 192.168.110.1
09658 08-10 09:33:44.398 685 3245 DEB NetUtils: android_net_utils_runDhcpCommon() Ipver:4 DNS 1 = 192.168.110.122
09659 08-10 09:33:44.398 685 3245 DEB NetUtils: android_net_utils_runDhcpCommon() Ipver:4 DNS 2 = 8.8.8.8
09660 08-10 09:33:44.398 685 3245 DEB NetUtils: android_net_utils_runDhcpCommon() Ipver:4 Server Address = 192.168.110.122
09661 08-10 09:33:44.398 685 3245 DEB NetUtils: android_net_utils_runDhcpCommon() Ipver:4 Vendor Info = 
09662 08-10 09:33:44.398 685 3245 DEB NetUtils: android_net_utils_runDhcpCommon() Ipver:4 Domain Name = cucm.cotac.com
09663 08-10 09:33:44.398 685 3245 DEB NetUtils: android_net_utils_runDhcpCommon() Ipver:4 TFTP 1 = 192.168.110.86
09664 08-10 09:33:44.398 685 3245 DEB NetUtils: android_net_utils_runDhcpCommon() Ipver:4 TFTP 2 = 
09665 08-10 09:33:44.398 685 3245 DEB DhcpStateMachine: DHCP succeeded on mlan0 IPv4
09666 08-10 09:33:44.398 685 3245 DEB DhcpStateMachine: RunningState: 4

The IP phone starts requesting Identity Trust List (ITL) and Certificate Trust List (CTL) files.

10276 08-10 09:33:47.632 3329 3329 INF dgetfile: GETXXTP [GT3329][src=CTLSEP00CCFC4ACCD2.tlv][dest=/data/data/cip.cfg/app_cip.tftp/CTLSEP00CCFC4ACCD2.tlv][serv=][serv6=][sec=0]
10277 08-10 09:33:47.632 3329 3329 INF dgetfile: In normal mode, call - > makeXXTPrequest (...)
10278 08-10 09:33:47.632 3329 3329 INF dgetfile: DTRACE [GT3329]makeXXTPrequest
10279 08-10 09:33:47.632 3329 3329 INF dgetfile: DTRACE [GT3329]parseEMCCConfig
10280 08-10 09:33:47.632 3329 3329 INF dgetfile: EMCC mode is false
10281 08-10 09:33:47.632 3329 3329 INF dgetfile: DTRACE [GT3329]parseDhcpInfoIntoTftpList
10282 08-10 09:33:47.632 3329 3329 INF dgetfile: Using WIRELESS interface for dhcp properties: ok
10283 08-10 09:33:47.632 3329 3329 INF dgetfile: cisco_tftp_server2 unavailable: 
10284 08-10 09:33:47.632 927 1611 ERR SQLiteLog: (1) table 'device' already exists

The IP phone looks for active CUCM servers to register to.

10361 08-10 09:33:47.640 1095 1540 INF ccservice-j: TelephonyManagerData: : fetchCallServerInfos svrHndls[1]=1584903492 mode=CCM status=ACTIVE CallServerInfo=[192.168.110.86, CCM, ACTIVE]
10362 08-10 09:33:47.640 1095 1540 DEB ccservice: SIPCC-SIP_CC_PROV: 0x5e77b5bc, CCAPI_DeviceInfo_getCallServerName: returned ipv4 192.168.110.84
10363 08-10 09:33:47.640 1095 1540 DEB ccservice: SIPCC-SIP_CC_PROV: 0x5e77b5bc, CCAPI_DeviceInfo_getCallServerMode: returned 02
10364 08-10 09:33:47.640 1095 1540 DEB ccservice: SIPCC-SIP_CC_PROV: 0x5e77b5bc, CCAPI_DeviceInfo_getCallServerStatus: returned 00
10365 08-10 09:33:47.640 1095 1540 INF ccservice-j: TelephonyManagerData: : fetchCallServerInfos svrHndls[2]=1584903612 mode=NONCCM status=NONE CallServerInfo=[192.168.110.84, NONCCM, NONE]

Troubleshoot

The Cisco Unified IP Phone 9971 provides device information, where network status, MAC address, version information, Unified Communications, Stream Statistics, WLAN Statistics are displayed. Browse to the web interface (http://x.x.x.x) of the IP phone and select the information you wan to check.

Device Information

Network Setup

WLAN Statistics

Streaming Statistics

Device Logs

Console logs, core dumps, status messages for troubleshooting purposes can be obtained from the web interface of the IP phone. Browse to the web interface (http://x.x.x.x) of IP phone, then select the necessary menu items under Device Logs to view this information.

WLAN Signal Indicator

As of the 9.0(2) release, the WLAN status indicator will be visible in all menus within Administrator Settings. In the initial release, the WLAN signal indicator was only visible in the WLAN Setup menu.