Guest

Preview Tool

Cisco Bug: CSCup05880 - SCCP Phone pulls TFTP configuration when failing over

Last Modified

Feb 14, 2018

Products (1)

  • Cisco Unified IP Phone 7900 Series

Known Affected Releases

9.3(1.6)

Description (partial)

Symptom:
Reproduction steps from the lab:
Assigned SCCP phone to a CM group with multiple Call Managers. 
Failed the network connection between primary CUCM and phone. 
Observed phone pulling a new configuration file from the TFTP server when it should not. SIP configuration for this same phone does not pull a TFTP config.

Conditions:
In Lab test phone SEP64A0E7F7EAA.pcapng: 7962 SCCP phone with load sccp42.9-3-1SR2-1s. Here's the IP info:

Test center cluster: uc95v3x1
phone IP: 10.231.179.57
sub1: 10.248.167.56
sub2: 10.224.174.56
TFTP server: 10.251.230.100

At around 09:50 on this Wireshark trace, communication to the phones primary sub1 (10.248.167.56) is blocked by an ACL on the router. When the keepalives to 10.248.167.56 are lost, the phone will send an XMLAlarmMessage to the secondary sub2 (10.224.174.56) and exchange Registration messages with this sub. After that, phone request its configuration file from TFTP server, which is not needed. Same problem exists when phone fallback to sub1.


failover:
#1323: XMLAlarmMsg
#1325: phone -> sub2: RegisterMessage
#1329: sub2 -> phone: RegisterAckMessage
#1383: phone -> tftp server: http get config.xml.sgn <== problem here

fallback:
#1466: phone -> sub1: RegisterMessage
#1467: sub1 -> phone: RegisterAckMessage
#1523: phone -> tftp server: http get config.xml.sgn <== problem here

++ In 7962_ConsoleLogs9.3.1ES27S_1.zip, the phone load is the latest 9-3-1ES27S on 7962.

we captured both sniffer from PC port of phone and console logs with below debug turned on:
debug jvm Http DEBUG

Same behavior seen from sniffer for failover:

phone: 14.84.109.221
TFTP server: 10.6.6.30
UCM sub2: 10.6.134.12

#38: phone -> UCM sub2: RegisterMessage
#40: UCM sub2 -> phone: RegisterAckMessage
#107: phone -> TFTP server: HTTP GET configuration file <== problem here

Console logs:

6865: NOT 16:15:49.851996 JVM: Startup Module Loader|cip.midp.pushregistry.e:? - setAcceptConnections - ENABLED
6866: NOT 16:15:49.853476 JVM: Startup Module Loader|cip.midp.midletsuite.InstallerModule:? - propertyChanged - device.settings.fullyregistered value=true
6867: NOT 16:15:49.854901 JVM: Startup Module Loader|cip.midp.midletsuite.InstallerModule:? - FULLY_REGISTERED - Resetting retry installer interval
6868: NOT 16:15:49.856362 JVM: Startup Module Loader|cip.midp.pushregistry.e:? - setAcceptConnections - ENABLED
6869: NOT 16:15:49.908007 JVM: Startup Module Loader|cip.midp.midletsuite.InstallerModule:? - propertyChanged - device.callagent.messages.0 value=0
6870: NOT 16:15:49.909398 JVM: Startup Module Loader|cip.cfg.t:? - Requesting CONFIG file from TFTP Service(1)
6871: NOT 16:15:49.911474 JVM: Startup Module Loader|cip.cfg.ConfigManager:? - --->ConfigManager PropertyChanged: device.callagent.callcount


Wireshark attached as Lab test phone SEP64A0E7F7EAA
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.