Cisco Cisco StadiumVision Mobile Streamer Release Notes
© 2010-2011 Cisco Systems, Inc. All rights reserved.
Page 14 of 47
StadiumVision 2.2. The version of BulkDMP for release 2.2 is properly named to
match the version of Cisco StadiumVision Director reported in the Web UI. For
example, for SV Director 2.2.0-41, the bulk update tool would be at path
match the version of Cisco StadiumVision Director reported in the Web UI. For
example, for SV Director 2.2.0-41, the bulk update tool would be at path
http://director-ip:8080/download/bulk_update-2.2.0-41.zip
.
You should use the administrator user and role to upload bulk DMP information.
Features Added in Version 2.1
The following features have been added to Cisco StadiumVision version 2.1.
Commerce Integration
•
Support for Micros Systems, Inc.
In addition to Quest, Cisco StadiumVision Director now supports integration with
Micros as a point of sale system.
Micros as a point of sale system.
•
Simplified Configuration of Commerce Integration
A tab has been added in Cisco StadiumVision Director to allow for the
configuration of Point of Sale integration. Configuration of commerce integration
for the luxury suites previously required certain parameters to be configured in
the Management Dashboard. Those parameters can now be configured in the
SV Director main UI.
configuration of Point of Sale integration. Configuration of commerce integration
for the luxury suites previously required certain parameters to be configured in
the Management Dashboard. Those parameters can now be configured in the
SV Director main UI.
•
Luxury Suite ID now required only for Commerce Integration
In release 2.0, the luxury suite basic information included a field called “Ext Suite
ID.” This value was used to tie the suite to CUCM and was the parameter
passed in from the CUCM StadiumVision service. As of release 2.1, the "Ext
Suite ID" is no longer required by CUCM.
ID.” This value was used to tie the suite to CUCM and was the parameter
passed in from the CUCM StadiumVision service. As of release 2.1, the "Ext
Suite ID" is no longer required by CUCM.
However, the parameter is still used for Commerce Integration. Because of this,
the “Ext Suite ID” field was moved to the Commerce Integration tab. This field
must contain the suite ID used by either Micros or Quest.
the “Ext Suite ID” field was moved to the Commerce Integration tab. This field
must contain the suite ID used by either Micros or Quest.
In the case of Micros, there are actually two fields that should be set. The “Ext
Suite ID” field should be set to what Micros refers to as the "Suite ID" and the
“External suite name” should be set to what Micros refers to as the "Suite
Number".
Suite ID” field should be set to what Micros refers to as the "Suite ID" and the
“External suite name” should be set to what Micros refers to as the "Suite
Number".
•
Change to scheduled pull of PoS data
In release 2.0, to perform automatic (daily) pulls of data from the Quest server,
you used the Management Dashboard to schedule a task called
QuestDataTask. In release 2.1 (to accommodate different PoS systems), this
task has been renamed to PosGetMenuTask.
you used the Management Dashboard to schedule a task called
QuestDataTask. In release 2.1 (to accommodate different PoS systems), this
task has been renamed to PosGetMenuTask.
•
Multi customer support changes
In release 2.0, there was a registry entry called “multiCustSupport,” which
indicated whether one or multiple customers could order from a suite. In release
indicated whether one or multiple customers could order from a suite. In release