Cisco Cisco StadiumVision Mobile Streamer Maintenance Manual
© 2012 Cisco Systems, Inc. All rights reserved.
Page 71 of 83
Log information for Local Control is dispersed across a number of different log files as follows:
/var/log/httpd/access_log: Contains the incoming http request from the IP phone
/opt/sv/servers/control/logs/sv_external.log: A summary of the communications from Cisco
StadiumVision Director to phone.
StadiumVision Director to phone.
/opt/sv/servers/control/logs/sv_phone_xml.log: Shows the raw XML that is returned by Cisco
StadiumVision Director to the phone.
StadiumVision Director to the phone.
/opt/sv/servers/control/logs/sv_debug.log: Shows the internal processing as a phone request is
handled by Cisco StadiumVision Director.
handled by Cisco StadiumVision Director.
Step 1: Use the Service button on the phone to bring up the main menu of the SV application. Check
the Apache logs to confirm that this results in an http GET message being received by Cisco
StadiumVision Director:
the Apache logs to confirm that this results in an http GET message being received by Cisco
StadiumVision Director:
[root@user-svd1 httpd]# pwd
/var/log/httpd
[root@user-svd1 httpd]# grep 10.10.99.3 access_log
10.10.99.3 - - [31/Oct/2011:17:27:19 -0600] "GET
/StadiumVision/images/phone/phone/phoneImages/saved/SEP0026CBC01B64_homePage.png
HTTP/1.1" 200 15606 "-" "Allegro-Software-WebClient/4.34"
/StadiumVision/images/phone/phone/phoneImages/saved/SEP0026CBC01B64_homePage.png
HTTP/1.1" 200 15606 "-" "Allegro-Software-WebClient/4.34"
Step 2: Check sv_external.log to see the requests that have been received from the phone and
processed. Log snippet below reflects the following sequence of buttons being pressed on the phone:
processed. Log snippet below reflects the following sequence of buttons being pressed on the phone:
1. Service button pressed. Bring up SV main menu – ListServices
2. TV/Volume key pressed. Bring up display selection screen – DisplaySelect
3. TV/DMP with IP addr 10.10.99.29 selected. Display channel guide – Device
4. Channel 3 selected. Channel
5. Volume down key pressed. VolumeDown
6. Screen returns to main SV menu after timeout – ListServices
[root@user-svd1 logs]# pwd
/opt/sv/servers/control/logs
[root@user-svd1 logs]# grep 10.10.99.3 sv_external.log | cut -c25-110
10.10.99.3}d2a4c282}Sports}Boulder1}ListServices}}}}}}}Duration 134
10.10.99.3}cebe23bd}VideoControl}Boulder1}DisplaySelect}}}}}OK}}Duration 124
10.10.99.3}be0d5d69}VideoControl}Boulder1}Display}Device[#167:10.10.99.29]|}}}}OK}10.10.99.3}80
ecc133}VideoControl}Boulder1}Channel}null|3|}}}}OK}}Duration 253
ecc133}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
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