[SOLVED] Ip Phone vpn SSL - Common Phone Profile Issue

Daniele Visaggio · ‎02-02-2012

Hi all,

i'm trying to configure an SSL vpn from a 7965 ip phone to an ASA appliance. Cucm version is 8.6.2.20000-2 and I tried several phone firmware versions:

SCCP45.9-1-1SR1S, SCCP45.9-2-1S, SCCP45.9-2-3S.

The ASA configuration is ok, my problem is about the phone configuration.

Simply put, after having applied a specific common phone profile (containing the vpn informations, profile and vpn group) to my phone, I loose control over it. The only action I can perform is to reset the phone from cucm but I cannot, for example, disable the video capability from it.

On the phone status messages I can see "error verifying config info" and on the phone console logs I read the following output (among other, please see log attached):

6363: NOT 17:12:41.238005 JVM: Startup Module Loader|cip.cfg.t:? - Config handleTftpResponse, status=0 for file=ram/SEP0023339D0947.cnf.xml

6364: WRN 17:12:41.239629 JVM: Startup Module Loader|cip.xml.ap:parse - Encoding Updated to UTF-8

6365: WRN 17:12:41.241938 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'name' in element '/device/devicePool' (line=16)

6366: WRN 17:12:41.243609 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'name' in element '/device/devicePool/dateTimeSetting' (line=18)

6367: WRN 17:12:41.245228 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'name' in element '/device/devicePool/callManagerGroup' (line=34)

6368: WRN 17:12:41.246840 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'tftpDefault' in element '/device/devicePool/callManagerGroup' (line=35)

6369: WRN 17:12:41.248492 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'mgcpPorts' in element '/device/devicePool/callManagerGroup/members/member/callManager/ports' (line=45)

6370: WRN 17:12:41.250244 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'mgcpPorts' in element '/device/devicePool/callManagerGroup/members/member/callManager/ports' (line=61)

6371: WRN 17:12:41.251912 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'name' in element '/device/devicePool/srstInfo' (line=72)

6372: WRN 17:12:41.253505 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'userModifiable' in element '/device/devicePool/srstInfo' (line=74)

6373: WRN 17:12:41.255133 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'mlppDomainId' in element '/device/devicePool' (line=89)

6374: WRN 17:12:41.256807 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'mlppIndicationStatus' in element '/device/devicePool' (line=90)

6375: WRN 17:12:41.258441 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'preemption' in element '/device/devicePool' (line=91)

6376: ERR 17:12:41.260819 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Exception: name expected (position:START_TAG <null>@131:2 in java.io.InputStreamReader@5066f3) (line=131)

6377: ERR 17:12:41.262415 JVM: Startup Module Loader|cip.cfg.t:? - ERROR PARSING CONFIG file:ram/SEP0023339D0947.cnf.xml

6378: NOT 17:12:41.264742 JVM: Startup Module Loader|cip.cfg.t:? - Config processConfigNoError() result code=CONFIG_FILE_BAD_FORMAT

It seems that, after applying the vpn-enabled common phone profile, the phone cannot parse correctly its xml configuration file, as you can see above. Thus it retains the old valid configuration file and for this reason all subsequent modifications are not understood by the phone. If I revert to the standard common phone profile, the problem suddenly disappears and I can perform any action on it.

Did someone experience this behaviour? How can I fix this?

Thank you in advance,

Daniele

Daniele Visaggio · ‎02-03-2012

Ok, problem fixed. As I thought, the problem was the bad format of the phone xml configuration file generated by cucm.

The log shows this in the following line:

6376: ERR 17:12:41.260819 JVM: Startup Module Loader|cip.xml.ap:  - XML Parser Exception: name expected (position:START_TAG @131:2 in java.io.InputStreamReader@5066f3)  (line=131)

Line 131 in phone xml config file contains:

130

131 <>null<>null<>null<>null[ ... ]

There are many more "<>null" in the file, and this causes the interpretation error.

Workaround: flag somthing in the Common phone profile applied to the phone (e.g. I disabled USB support). This simple action fixed the xml file format (<>null tags disappeared), see https://supportforums.cisco.com/thread/2075361

Then I rebooted the phone and the error in the phone console logs was disappeared. So I regain full control of the device.

At this point it's also possible to revert to the original common phone profile ( I re-enabled USB support). The xml file was no longer impacted.

This is clearly a bug.

Hope this helps!

Regards,

Daniele

Simon Carron · ‎02-07-2014

Hello,

We encountered this issue last week... After more than one week of investigation we finaly found out the root cause.

When you click twice with a fast manner on the save button under the Common phone profile config page. CUCM will generate this corrupt XML config. (...)

It seems that this issue occurs for all CUCM version from 5 to 9. This issue has been fixed in version 10.

Reagrds