Release Notes for Hosted Unified Communications Services, Release 5.1b
Available Languages
Table Of Contents
Release Notes for Cisco Hosted Unified Communication Services Release 5.1(b)
Support for Cisco Unified Communications Manager 5.1(3)
Cisco Unified MeetingPlace Integration
Automated Cisco Unity Integration
Co-Existence of IP Unity and Cisco Unity
Dial Plan Enhancements and Support for the US Dial Plan
Support for Countries Without Area Codes
Support for SIP and SCCP Endpoints
Limitations in Netwise Automated Provisioning
Co-Existence of IP Unity and Cisco Unity
Dial Plan Enhancements and Support for the US Dial Plan
Support for Countries Without Area Codes (Danish Dial Plan)
Unresolved Caveats in HUCS Release 5.1(b)
Unresolved Caveats in BVSM Release 3.1.8
Caveats Resolved in HUCS Release 5.1(b)
Caveats Resolved in BVSM Release 3.1.8
Caveats Resolved in HUCS Release 1.6.1
Obtaining Documentation, Obtaining Support, and Security Guidelines
Cisco Product Security Overview
Release Notes for Cisco Hosted Unified Communication Services Release 5.1(b)
February 4, 2008
These release notes describe updated information, caveats and known issues for the Cisco Hosted Unified Communication Services (HUCS) Release 5.1(b).
Contents
These release notes provide the following information:
•
New Features and Enhancements
•
Related Documentation
The following related documentation is available for Cisco HUCS Release 5.1(b).
Getting Started with Cisco Hosted Unified Communications Services, Release 5.1(b)
The Getting Started with Cisco Hosted Unified Communications Services guide provides a high-level overview of the HUCS platform and describes how to configure and apply static configuration to the platform components. This guide summarizes the options provided by VisionOSS BVSM for configuring and managing the platform components, explains how to use BVSM to load bulk data during initial configuration of the components, and how to backup, restore, and clear the platform components. To view this document, see the following URL:
http://www.cisco.com/en/US/docs/voice_ip_comm/hucs/5_1b/english/user/guide/HUCS_bk.pdf
Solution Reference Network Design for Cisco Hosted Unified Communications Services, Release 5.1(b)
The Solution Reference Network Design (SRND) document provides a detailed description of the Cisco HUCS product design and architecture. The document describes the product components used to build the Cisco HUCS solution, both Cisco products and partner products, and the suite of services that are provided by this solution. It describes the network architecture, including call scenarios, legacy PBX integration, and geographic redundancy.
The document also defines the supported Cisco HUCS deployment models, provides guidelines regarding the required network infrastructure, and describes how the solution fulfills regulatory requirements, such as service provider requirements.
To obtain a copy of the Solution Reference Network Design document for Cisco Hosted Unified Communications Services, Release 5.1(b), contact your Cisco representative.
Software Matrix for Cisco HUCS, Release 5.1(b)
This document provides a comprehensive list of the software and hardware components that are supported for the Cisco HUCS, Release 5.1(b). To view this document, see the following URL:
New Features and Enhancements
This section contains new and changed features introduced in Cisco HUCS, Release 5.1(a) and 5.1(b). It includes the following topics:
•
•
•
•
•
•
•
Support for Cisco Unified Communications Manager 5.1(3)
Support for Cisco Unified Communications Manager 5.1(2) was introduced in HUCS Release 5.1(a), which was an internal maintenance release created for testing purposes. HUCS Release 5.1(b) introduces support for Cisco Unified Communications Manager 5.1(3)
•
•
•
•
•
Note
Automated Netwise Integration
This feature provides automated provisioning with BVSM for integrating Netwise Attendant Console into the HUCS Release 5.1(b) platform.
Cisco Unified MeetingPlace Integration
This feature provides support for MeetingPlace Audio Conferencing and web collaboration facilities, including access to a server from any phone in the network and management of MeetingPlace user accounts with BVSM.
Automated Cisco Unity Integration
This feature provides automated provisioning of Cisco Unity for integration into the HUCS platform. This integration allows support of multiple instances of Cisco Unity and its components, with Cisco Unity configured in any of its deployment modes:
•
•
•
Co-Existence of IP Unity and Cisco Unity
This feature provides support for the co-existence of both IP Unity and Cisco Unity platforms within single and multi-tenant HUCS deployments.
Dial Plan Enhancements and Support for the US Dial Plan
This feature provides enhanced support for the existing North American dial plan within the HUCS platform. The following are the supported enhancements to the dial plan:
•
Previously, the Cisco PGW Legacy PBX ingress dial plan statically assigned national and international prefixes of 0 and 00 respectively. This was not compliant with other country dial plans including the standard US dial plan.
•
•
–
–
•
Previously, the call forwarding patterns in the dial plan model were commented out.
•
–
–
Support for Countries Without Area Codes
This feature lets the HUCS solution support a country dial plan that has no intra-national long-distance dialing (only international long-distance dialing), such as the Danish dial plan.
Important Notes
This section includes the following topics related to HUCS Release 5.1(b) features:
•
Support for SIP and SCCP Endpoints
Table 1 summarizes the Unified Communications Manager features that are supported with SIP and SCCP endpoint in HUCS Release 5.1(b):
Table 1 Feature Support for SIP/SCCP Endpoints in Release 5.1(b)
Abbreviated dial
Yes
Yes
Answer and answer release
Yes
Yes
Auto-answer and intercom
Yes
Yes
Barge
No
No
Call connection
Yes
Yes
Call coverage
Yes
Yes
Call forward-All (off net and on net), busy, and no answer
Yes
Yes
Call hold and retrieve
Yes
Yes
Call park and pickup
Yes
Yes
Call waiting and retrieve
Yes
Yes
Calling line identification (CLID) and calling party name identification (CNID)
Yes
Yes
(View) Conference list and drop any party (impromptu conference)
Yes
Yes
Direct inward dial (DID) and direct outward dial (DOD)
Yes
Yes
Directories-Missed, placed, and received calls list stored on selected IP phones
Yes
Yes
Extension mobility support
Yes
Yes
Hands-free, full-duplex speakerphone
Yes
Yes
Last number redial (on and off net)
Yes
Yes
Multiple calls per line appearance
Yes
Yes
Multiple line appearances per phone
Yes
Yes
Music on hold
Yes
Yes
Mute capability from speakerphone and handset
Yes
Yes
On-hook dialing
Yes
Yes
Privacy
No
No
K-factor
Yes
No 1
Recent dial list-Calls to phone, calls from phone, autodial, and edit dial
Yes
Yes
Service URL-single-button access to IP phone service
No
No
Speed dial-Multiple speed dials per phone
Yes
Yes
Station volume controls (audio and ringer)
Yes
Yes
Transfer-Blind, consultative, and direct transfer of two parties on a line
Yes
Yes2
1 Not supported in Unified Communications Manager 5.1x.
2 Direct transfer not supported in SIP.
Product Provisioning Method
Table 2 outlines the supported product model for the Cisco HUCS Release 5.1(b); the provisioning method per product is specified.
Table 2 Product Provisioning Method for Cisco HUCS Release 5.1(b)
Cisco Unified Communications Manager 4.1
Yes
Cisco Unified Communications Manager 4.2
Yes
Cisco Unified Communications Manager 5.1
Yes
Cisco Unified IP Phones
Yes
Cisco Analog Telephone Adaptors
Yes
Cisco IP Communicator
Yes
Cisco Unified Personal Communicator
X
Cisco Unified Video Advantage
Yes
Cisco Unity 4.2 1
Yes
Cisco Unity 5.0
X
Cisco Unity Connection
X
Cisco Unity Express
X
Cisco Unified MeetingPlace
Yes
Cisco Unified MeetingPlace Express
X
Cisco Unified Hosted Contact Center
Yes
Cisco Unified Presence
X
Cisco Unified Mobile Communicator
X
Cisco Unified Application Environment
X
Cisco Unified CallConnector Mobility
X
Cisco Unified Videoconferencing System 4.2
X
Cisco Unified Operations Manager 2.0
Yes
Cisco Unified Service Monitor 2.0
Yes
Cisco WebEx
X
Cisco Unified Communications Manager Express
X
Cisco Unified Communications 500 Series for Small Business
X
Cisco Unified Conferencing for Telepresence
X
Cisco Fax Server
X
Cisco PGW 2200 Softswitch
Yes
Cisco Gatekeeper
Yes
Cisco Unified Survivable Remote Site Telephony (SRST )
Yes
Cisco H.323 Signaling Interface (HSI)
Yes
Cisco PSTN Gateways (central gateway)
Yes
Cisco PSTN Gateways (local gateway)
Yes
Cisco Emergency Responder
X
Cisco Billing and Measurements Server (BAMS)
Yes
Cisco Integrated Services Routers
Yes
Cisco ASA/PIX/FWSM
Yes
IP Unity VM
Yes
IP Unity UM
X
IP Unity Conferencing
X
IP Unity Web Collaboration
X
IBM Voicerite VM
Yes
X
Netwise Attendant Console
Yes
ARC Attendant Console
Yes
Yes
1 Cisco Unity 4.2 Integrates with Cisco Unified Communications Manager 4.2 or 5.1. The Integration is provisioned automatically on the Cisco Unified Communications Manager, but has to be manually provisioned on Cisco Unity. Exchange users can also be automatically provisioned.
Limitations and Restrictions
This section describes the limitations and restrictions that generally affect the HUCS Release 5.1(b) platform and that affect specific new features in this release. This section includes the following topics:
•
•
•
General Observations
•
Note
•
•
•
•
•
•
check progress indicator before establishing media
This prevents interoperability issues between HSI and Unified CM, to prevent timeout issues establishing the media path. This flag affects scenarios where IP Phone-to-IP Phone calls are forwarded on NO Answer to SS7 phones. If the SS7 phone waits for 6 seconds before answering the call, the call is dropped.
•
•
•
•
•
–
Outcome: Calls are possible between the two Cisco PGWs because the set transactions are executed in both directions. However, the Legacy gateway cannot be connected to a PBX because of an internal error in BVSM. BVSM tries to do set transactions on the remote Cisco PGW and fails.
–
Outcome: It is not possible for a Provider to introduce a new Cisco PGW or Unified CM into the same Country. The PGW can be added under another Provider and the EISUP transit links should be manually provisioned along with other set transactions on both Unified CM and PGW.
–
Outcome: Legacy gateway can be connected to the PBX. However, calls are possible in only one direction (from PGW1 to PGW2) because the set transactions are executed on one PGW. Calls do not work from PGW2 to PGW1.
•
Netwise Integration
This section describes the limitations and restrictions affecting Netwise integration into the HUCS Release 5.1(b) platform. This section includes the following topics:
•
Netwise Product Defects
•
–
–
–
•
Queue overflow, redirected to Voicemail box, cannot be configured because direct drop to voicemail is done by prefixing extension number with **.
Limitations in Netwise Automated Provisioning
The Netwise provisioning in HUCS has only partially been automated by BVSM. Most of the configuration in Netwise CTC and CMG servers is done by BVSM, except adding pilot numbers on the CMG server and adding the operator users in CTC. However, this does not complete the provisioning required on the Unified CM side (CTI Port, CTI Route Points, TAPI/JTAPI users, assign class of service to operator phone).
Route Patterns in Netwise
When the operator calls an extension at a local location, the call will be routed by the RoutePattern AllowAttendantCallsX. This route partition identifies the call as a call originating from an attendant. The route partition amends the A number with 070 before the site code and extension. The 070 is recognized as a unique Call Type within the Cisco PGW. As a result, the destination extension sees the published number of the location as the CLID and the operator sees the FINT number of the destination with a 7 in the beginning.
When the Netwise application does a passive-redirect or a call overflow, Unified CM uses the CSS of the last device to control the call (usually the Unified CM Trunk) to make the second leg of the call. In normal HUCS architecture the external trunk does not have COS to dial any E164 numbers and can only reach internal DNs. An extra partition has been added to Unified CM, Netwise-Divert, which is added to an Incoming to Cluster Calling Search Space (CSS).
This partition matches 999999+CPID+RID+SLC on a translation partition; 999999+CPID+RID+SLC is prefixed before all E164 numbers redirected from the Netwise application. The translation pattern strips the 999999+CPID+RID+SLC prefix and applies a relevant CallForward CSS to the call and routes using the normal dial plan. This means that to use this features on external queues, it must be entered on the Netwise overflow/passive redirect configuration.
MeetingPlace Integration
Based on current limitations, Unified MeetingPlace cannot work with multiple IP Gateways. The IOS Gatekeeper rejects any duplicate registration request made by a second IP gateway trying to register with the same e.164 number. This is mainly because the MeetingPlace gateway registers as an end-point and not as a gateway.This problem could be resolved if a tech-prefix is configurable on the IP Gateway. At the time this was tested, no support for tech-prefix could be found on the IP Gateway.
Cisco Unity
BVSM automates the Unified CM side of Unity provisioning, but not the Unity server side. You must create a new integration on the Unity server, with the required number of ports and specify the prefix name to use. The Message Waiting Indication (MWI) on/off numbers also must be provisioned manually in both Unified CM and Unity.
Although voicemail subscribers can automatically be created by BVSM, you must manually verify on the Unity server that the user has correctly been added. If the name of the subscriber was already an Active Directory user, the subscriber will not be added correctly. This situation will occur if a subscriber is deleted and then re-added. You must first remove the name from the Active Directory server before adding it again. Also, after creating a subscriber, you must associate each subscriber to the correct switch in the Unity configuration that was created manually during Unity provisioning.
A different driver is required for creating the VMPorts in Unified CM 5.1(3) and 4.2(3). As a workaround, lines 1897 and 1898 of the Unified CM model should be changed and reloaded according to the Unified CM version for which you are creating the VM Service. For Unified CM 5.1(3), the fields Caller Name, Caller Number, Redirected Number and Dialed Number should be blank and for 4.2(3) the value should be false.This will be an issue for any customer deployment where there is more than one Unified CM version in use.
Co-Existence of IP Unity and Cisco Unity
The following affects the operation of IP Unity and Cisco Unity when integrated into a single HUCS platform:
•
•
•
Dial Plan Enhancements and Support for the US Dial Plan
The following summarizes restrictions affecting the Dial Plan Enhancements and Support for the US Dial Plan in HUCS Release 5.1(b):
•
•
•
•
•
•
•
•
A call from a PSTN phone using a local gateway trunk to a Unified CM SIP or SCCP phone is CFU to a third PSTN phone through a local gateway trunk. The second call leg is routed through a central gateway trunk. However, if the central gateway trunk is not available, the call fails.
Support for Countries Without Area Codes (Danish Dial Plan)
For any location or site, the PSTN access prefix chosen must match the BVSM default for the country in which the location is created. Failure to do so will result in corrupted calling party number displays. For example, in Denmark the default PSTN access prefix is 0.
Caveats
This section describes the open and resolved caveats affecting HUCS Release 5.1(b) and BVSM Release 3.1.8. This section contains the following topics:
•
•
•
•
•
Using the Bug Toolkit
You can search for problems by using the Cisco Software Bug Toolkit. To access Bug Toolkit, you need the following:
•
•
•
To use the Software Bug Toolkit, complete the following steps:
Procedure
Step 1
Step 2
Step 3
Step 4
Unresolved Caveats in HUCS Release 5.1(b)
The following tables list defects that are unresolved in Cisco HUCS Release 5.1(b). For more information about an individual defect, you can access the online record for the defect by clicking the Identifier (CSC caveats). You must be a registered Cisco.com user to access this online information.
Defect status frequently changes, so these tables list the defects that were unresolved at the time of the release of HUCS Release 5.1(b). To view a current list of unresolved defects, use the Bug Toolkit as described in the "Using the Bug Toolkit" section. Table 3 lists the defects that are unresolved in HUCS Release 5.1(b).
Unresolved Caveats in BVSM Release 3.1.8
Table 4 lists the defects in BVSM 3.1.8 that were unresolved and affected HUCS Release 5.1(b) at the time of release. For details and information about the current status of these defects and for any workaround available, contact VisionOSS.
Netwise Unresolved Caveats
Table 5 provides a listing of the Netwise caveats affecting HUCS Release 5.1(b) that were unresolved at the time of the release.
Caveats Resolved in HUCS Release 5.1(b)
Table 6 lists one caveat, resolved in HUCS Release 5.1(b), that affected an earlier release.
Caveats Resolved in BVSM Release 3.1.8
Table 7 provides a numeric listing of the caveats resolved in BVSM Release 3.1.8 that affected an earlier release.
Caveats Resolved in HUCS Release 1.6.1
Table 8 lists the defects in BVSM that were resolved in Cisco HUCS Release 1.6.1.
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Cisco Product Security Overview
This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html. If you require further assistance please contact us by sending email to export@cisco.com.
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0705R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2008 Cisco Systems, Inc. All rights reserved.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)