CTS System - Phone Midlet debugging

The following article describe the steps needed to verify IP phone internal modules when Midlet is being loaded.

In cases with new versions and when configuration has been already verified, TAC and Engineering require deep debug levels to verify software behavior.

Requirements

- IP Phone load 8.3.4 and up
- CUCM Version 7.0 and up
- CTS 1.5.0(1879) and up

Supported Models

Model Display Navigation Touchscreen Notes
7921 Color 4-way plus Select No
7941/61 Grayscale 2-way (vertical) No
7942/62 Grayscale 2-way (vertical) No
7945/65 Color 4-way plus Select No
7970/71 Color 4-way Yes
7975 Color 4-way plus Select Yes

* Verify TelePresence documentation for supported models

IP Phone

- Collect via Web IP Phone console logs
- For more detail debugging we can collect logs via SSH

By default, System.out and System.err output does not get sent to the phone's default console output, so it won't show up on the phone's serial port or on SSH shell sessions unless
it is specifically enabled.

To enable Java output on the console for testing and debugging purposes, perform the following:

Connect to IP Phone using the procedure outlined here:

http://mytelepresence.blogspot.com/2010/04/telepresence-system-debugging-with.html


Enable following debugs:

debug auth
debug jvm ALL
debug jvm MIDP-MIDlet
debug jvm MIDP-MIDletSuite
debug jvm MIDP-IO
debug jvm Services
debug jvm Security
debug jvm XML
debug ui