Cisco Cisco StadiumVision Mobile Reporter 维护手册
© 2011 Cisco Systems, Inc. All rights reserved.
Page 26 of 76
Implementation Summary
This section provides a high-level overview of what must be configured in support of
local TV control.
local TV control.
Graphic Specifications
The graphics (or images) used in the deployment of a luxury suite are stored in
different locations and have different specifications.
different locations and have different specifications.
Graphic
Location
Specifications
IP Phone Desktop background
CUCM
Supplied with StadiumVision Director
IP Phone 7975: 320x216x16
IP Communicator: 320x212x12
Welcome Message example
StadiumVision Director
Supplied with StadiumVision Director
DMP 4310: 1920x1080
DMP 4305: 1366x768
Channel icons used in channel
lineup on the IP Phone
lineup on the IP Phone
StadiumVision Director
Must be supplied locally with network
approval.
approval.
IP Phone: 24x24, PNG
3
rd
party: 40x40, PNG
Team logo used in channel
lineup on the TV
lineup on the TV
StadiumVision Director
Must be supplied locally.
DMP 4310: 300x180, PNG or JPEG
DMP 4305: 218x128, JPEG
IP Phone Services background
Bullets and service icons used
on IP Phone services pages
on IP Phone services pages
CUAE
Supplied with StadiumVision Director
Information about how to load these files on the various devices is provided in
subsequent sections.
subsequent sections.
Note on Changing the Phone Background
Stadium Vision Director includes the ability to deploy IP Phone Backgrounds.
However, this method of deployment is not recommended for the following reasons:
However, this method of deployment is not recommended for the following reasons:
It requires that all phones are associated to a user in CUCM.
It requires that the Settings button on the IP Phones be enabled (security risk).
It requires that the IP Phone be in a speciUic state at the time of launch or it will
not work.
It uses simulated key presses to execute the background change, which is
invasive as each press is visible on the phone as it is being executed (screen
changes, etc).
changes, etc).
Each time it is executed, it stores a copy of the image on the phone, even if the
same image was already pushed. We are unaware of the limit or behavior once
the limit is exhausted.
the limit is exhausted.