Cisco Cisco StadiumVision Mobile Streamer Maintenance Manual
© 2011 Cisco Systems, Inc. All rights reserved.
Page 74 of 83
10.10.99.3}be0d5d69}VideoControl}Boulder1}Display}Device[#167:10.10.99.29]|}}}}
OK}10.10.99.3}80ecc133}VideoControl}Boulder1}Channel}null|3|}}}}OK}}Duration
253
OK}10.10.99.3}80ecc133}VideoControl}Boulder1}Channel}null|3|}}}}OK}}Duration
253
10.10.99.3}5f69c8c7}VideoControl}Boulder1}VolumeDown}120|}}}}OK}}Duration 92
10.10.99.3}cb581289}Sports}Boulder1}ListServices}}}}}}}Duration 146
Step 3: In the previous step notice how each log message in sv_external.log
contains an 8 digit log message ID immediately following the phone IP address. This
ID can be used to find related messages in the other log files in the same directory.
In the following example log messages with ID f2eecb6f can be found in 5 different
log files. Notice how the timestamps are within one second of each other,
emphasizing that they are all part of the same transaction:
contains an 8 digit log message ID immediately following the phone IP address. This
ID can be used to find related messages in the other log files in the same directory.
In the following example log messages with ID f2eecb6f can be found in 5 different
log files. Notice how the timestamps are within one second of each other,
emphasizing that they are all part of the same transaction:
[user@svd1 logs]$ grep f2eecb6f * | cut -c1-80
sv_debug.log:2011-10-31 17:17:26,984 [TP-Processor6] f2eecb6f ERROR
com.cisco.sv
com.cisco.sv
sv_dev_debug.log:2011-10-31 17:17:26,982 [TP-Processor6] f2eecb6f INFO
com.cisc
com.cisc
sv_dev_debug.log:2011-10-31 17:17:26,984 [TP-Processor6] f2eecb6f ERROR
com.cisc
com.cisc
sv_dev_debug.log:2011-10-31 17:17:26,990 [TP-Processor6] f2eecb6f INFO
com.cisc
com.cisc
sv_external.log:1}2011-10-31 17:17:27,108}10.10.99.3}f2eecb6f}VideoControl}Bould
sv_external.log.2011-09-08:3}2011-10-31
17:17:27,107}10.10.99.3}f2eecb6f}page=VD
17:17:27,107}10.10.99.3}f2eecb6f}page=VD
sv_msg_trace.log:2011-10-31 17:17:27,269 [I/O dispatcher 13] f2eecb6f DEBUG
svlo
svlo
sv_phone_xml.log:2011-10-31 17:17:27,107 [TP-Processor6] f2eecb6f DEBUG
svlog.ph
svlog.ph
Step 4: Check the sv_phone_xml.log to perform a sanity check of the XML returned
to the phone. The XML in the example below corresponds to the be0d5d69 entry in
sv_external.log in step 2 above. That is display the channel guide. The XML below
describes two channels (KGO-HD and LIVEWELL HD) and for each defines the X,Y
touch area and the channel change URL that is fired when touched.
to the phone. The XML in the example below corresponds to the be0d5d69 entry in
sv_external.log in step 2 above. That is display the channel guide. The XML below
describes two channels (KGO-HD and LIVEWELL HD) and for each defines the X,Y
touch area and the channel change URL that is fired when touched.
The format of the XML is documented at:
http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/all_models/xsi/7_1_3/xmlo
bjects.html
http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/all_models/xsi/7_1_3/xmlo
bjects.html