Table Of Contents
Release Notes for Cisco Hosted Unified Communications Services, Release 6.1(a)
February 16, 2009
These release notes describe updated information, caveats and known issues for the Cisco Hosted Unified Communications Services (Hosted UCS), Release 6.1(a).
These release notes provide the following information:
The following related documentation is available for Cisco Hosted Unified Communications Services, Release 6.1(a).
Getting Started with Cisco Hosted Unified Communications Services, Release 6.1(a)
Provides a high-level overview of the Hosted UCS platform and describes how to configure and apply static configuration to the platform components. This guide summarizes the options provided by VisionOSS Business Voice Services Manager (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:
Solution Reference Network Design for Cisco Hosted Unified Communications Services, Release 6.1(a)
Provides a detailed description of the Hosted UCS product design and architecture. The document describes the product components used to build the Hosted UCS 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 Hosted UCS 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 6.1(a), contact your Cisco representative.
Software Matrix for Cisco Hosted Unified Communications Services, Release 6.1(a)
Provides a comprehensive list of the software and hardware components that are supported for the Cisco Hosted Unified Communications Services, Release 6.1(a). To view this document, see the following URL:
Provisioning Guide for Cisco Hosted Unified Communications Services, Release 6.1(a)
Describes how to use VisionOSS BVSM to provision the components of the Hosted UCS platform. To view this document, see the following URL:
New Features and Changes
This section contains new and changed features introduced in Cisco Hosted UCS, Release 6.1(a). It includes the following topics:
Cisco Unified Communications Manager 6.1 Support
Cisco Hosted Unified Communications Services, Release 6.1(a) introduces support for Cisco Unified Communications Manager 6.1.
•The 6.x Cisco Unified Communications Manager BVSM driver can now be used to successfully add configurations to Cisco Unified Communications Manager 6.1.
•The Softkey Templates configured in Cisco Unified Communications Manager can be imported into BVSM, and then used when you are provisioning the IP Phone.
Shared Building Feature
Shared Building feature is useful to small and medium business (SMB) customers who have sites in business centres/shared buildings.
The shared building feature enables the Hosted UCS customer to significantly reduce the required number of PGWs and Cisco Unified CM clusters by providing a more efficient application of the current configuration.
Inter-tenant Lawful Intercept
When Lawful Intercept is required/used, the routing of the Hosted UCS calls made by dialing the full E.164 number are carried out over a Primary Rate ISDN (PRI) loop. These forced On-Net calls can be intercepted at this point by an LI mediation device. Calls from an endpoint in the Hosted UCS deployment destined to the PSTN and incoming PSTN calls can be subject to voice intercept. The LI mediation device is a third-party product, not verified by Hosted UCS.
Note Please note that this implementation of LI into Hosted UCS is not compliant with certain LI standards, including CALEA and Russian specifications, since it was designed, implemented and tested for a specific customer and they accepted to be in compliance with the country standard.
Movius AutoAttendant Integration
The Movius AutoAttendant integration feature enables PGW and Cisco Unified Communications Manager to route calls to the Movius AutoAttendant from any PSTN or Hosted UCS phone. After selecting an option on a menu, these calls can be transferred to another Hosted UCS or PSTN phone.
The Movius voicemail dial plans were updated to enable making and receiving calls to and from Movius AutoAttendant. A new trunk was added to Cisco Unified CM, for Movius voicemail calls, to allow using a media termination point for the AutoAttendant calls.
Unified Contact Center Hosted (UCCH) Integration
Cisco Unified Contact Center Hosted (UCCH) integration in Hosted UCS as a service that provides a common provisioning interface to enable provisioning of both agent and standard business phones. The BVSM UCCH Service manages standard lines and extension mobility lines assignment for UCCH agent usage, and also the PGW provisioning for call routing to and from the Contact Center system. Other UCCH set-up and configuration requirements are managed using the standard UCCH tools such as the Cisco Unified Contact Center Management Portal (Unified CCMP).
SIP Trunking and PGW to Microsoft OCS Telephony Service
Hosted UCS to interwork with the Microsoft Office Communication Server (OCS) telephony service using the OCS stand-alone deployment model.
Note Be aware that the provisioning must be performed manually because BVSM does not provision any of the Hosted UCS components.
In the stand-alone model, the dial plan gets partitioned between OCS users and Hosted UCS users. This means that users either have a Cisco Hosted UCS or OCS endpoint, but not both. An OCS mediation server provides the interconnect between the Cisco Hosted UCS and OCS environment. From the OCS perspective, the Hosted UCS environment is viewed as an IP-PBX connected directly via SIP and from the Hosted UCS perspective, the OCS environment is viewed as a Legacy PBX.
The following call flows are supported between the two environments:
•Call Hold and Retrieve
•Call Forward (All, Busy and No Answer)
•Call Transfer (Blind and Consultative)
To achieve the above, these two new dial plans are required:
•OCS—Mediation Server Dial plan
•PGW—Dial plan based on existing Legacy PBX dial plan
Cisco Emergency Responder
In Hosted UCS 6.1(a), Cisco Emergency Responder (Cisco ER) can be used to manage emergency calls in the telephony network so that it is possible to respond to these calls effectively. This enables the service provider to comply with local ordinances concerning the handling of emergency calls.
It is possible to provision some locations to handle emergency calls via the default Cisco Hosted UCS method and provision others to use Cisco ER. For the locations provisioned to use Cisco ER, emergency calls are sent to the PSTN with the Calling Party Number being replaced with the Emergency Location Identification Number (ELIN) which enables the Public Safety Answering Point (PSAP) operator to correctly identify the location of the caller. Cisco ER also enables the PSAP operator to call the emergency caller back.
Local PSTN Breakout Support With and Without SRST and Cisco Unified Communications Manager 6.1
In Hosted UCS 6.1(a), the administrator can provision local gateways with or without SRST support. Calls to and from PSTN can be routed via PRI or BRI interfaces. The format of the calling and called party number and Nature of Address (NOA) can now be configured in various ways. Additionally, calls to and from PSTN from one location can be routed via a single trunk, or optionally, the administrator can provision two trunks to separate local and national/international calls. Finally, on the Local Gateway, a number of TCL applications developed by Cisco are used to take over the role of the default application.
Note The default application is used to control voice dial-peers in IOS, which is part of the built-in call control of IOS that basically binds two call legs whose characteristics are defined by the configured voice dial-peers.
These applications are then configured on each voice dial peer and each peer verifies on each voice call whether calling and/or called number needs to be translated in the same way as the voice translation rules did in the previous Hosted UCS releases. Using the TCL applications, (maximum number of locations connected to one local gateway) x (Number of E.164 number to internal number associations for all locations connected to that local gateway) has been increased from 13 to 150. For example, if every location has one "E.164 number to Internal number association" a total of 150 locations can use one local gateway for Local PSTN Breakout.
Forced Off-Net Provisioning
In Hosted UCS 6.1(a), it is possible to use BVSM to configure the PGW to analyze outgoing PSTN calls and to force all Off-Net calls out of the Hosted UCS environment, even if the destination is that of a user in the Hosted UCS environment.
In Hosted UCS 5.1(b) Maintenance Release 1 (MR1), this feature was available, but it was not possible to provision this feature via BVSM. Hosted UCS 6.1(a) introduces the option to provision this feature via BVSM.
Phone XML Services Support
In Hosted UCS 6.1(a), XML services on Hosted UCS phones can be provisioned via BVSM.
Per-Customer "Block Off-Net to Off-Net Call Transfer" Feature Support
The Block Off-Net to Off-Net Call Transfer (BO2OCT) feature blocks all transfers made by Cisco Unified CM phones from external incoming calls to outgoing external calls. In order to do this, a new trunk was introduced on the Cisco Unified CM in order to differentiate OffNet and OnNet calls.
In Hosted UCS 5.1(b) MR1, this feature could only be configured for a whole Cisco Unified CM cluster. In Hosted UCS 6.1(a), this feature can be enabled or disabled for each customer.
BRI Support for Local PSTN Breakout
Hosted UCS 6.1(a) supports routing to and from PSTN via BRI interfaces for local PSTN breakout.
Full Number Translations with TimesTen Database Support
The Full Number Translations feature provides a large-scale, number translation function on the Cisco PGW. This feature enhances the current PGW database query mode, which is used for local number portability (LNP) and CLI screening, by handling contiguous ranges of numbers with analysis and modification capabilities. The Full Number Translations feature supports large-scale changes of individual numbers. The full number replacement mechanism adds a general number replacement result type, NUM_TRANS, available for A-number and B-number analysis. In addition, a Times Ten query and full number translation table are also added. The existing Times Ten database is used to store the dial plan numbers.
Hosted UCS 6.1(a) introduces the Full Number Translation with TimesTen Database feature. This means that the association of E.164 numbers to internal numbers will use this feature instead of configuring via MML. To use this feature, an internally developed script is uploaded on the PGW.
Migration from Hosted UCS 5.1(b) MR1 to Hosted UCS 6.1(a)
You can migrate an environment provisioned in Hosted UCS 5.1(b) MR1 to Hosted UCS 6.1(a). Once the environment is fully migrated, you can make changes to upgraded customers via BVSM.
This section includes the following topics related to Hosted UCS Release 5.1(b) features:
Change in Static Configuration
This section compares the static configuration in Cisco Hosted UCS 6.1(a) to the previous releases of Cisco Hosted UCS, and lists the changes:
•In previous Hosted UCS releases, for each Cisco Unified Communications Manager Publisher or Subscriber server that was configured to be used as the Music On Hold (MOH) server, the MOH server name had to be changed to MOH_<server_short_host_name> (for example: MOH_e4c1p).
In Hosted UCS 6.1(a), this is not required because BVSM retrieves the MOH server name from the Unified CM server. This information is then used when configuring Media Resource Groups.
•In previous Hosted UCS releases, the Roaming Login/Logout Services Service URL for Unified CM 5.x was configured as: http://<BVSM_Virtual_IP_Address>:8080/bvsmweb/bvsmroaming.cgi?device=#DEVICENAME
In Hosted UCS 6.1(a), this should be replaced with:
•The Cisco Unified IP Phone XML Services Service URL for Unified CM 5.x was configured as: http://<BVSM_Virtual_IP_Address>:8080/bvsmweb/bvsmservices.cgi?device=#DEVICENAME
In Hosted UCS 6.1(a), this should be replaced with:
•In previous Cisco Hosted UCS releases, Softkey_Basic and Softkey_Advanced templates had to be configured in Unified CM as part of the static configuration.
In Hosted UCS 6.1(a), Softkey Templates are not configured in BVSM; instead, the configured Softkey Templates in Unified CM are imported into BVSM.
•In previous Cisco Hosted UCS releases, the trunk group property on the PGW for each HSI were configured with "FAXsupport"=1. Additionally, the ILGW dial plan was created as:numan-add:dialplan:custgrpid="ICCM", OVERDEC="NO"
In Cisco Hosted UCS 6.1(a), "FAXsupport" property should be removed, and ILGW should be created as: numan-add:dialplan:custgrpid="ILGW", OVERDEC="YES"
•Cisco Hosted UCS 6.1(a) introduces the Full Number Translation with TimesTen Database feature. In order to use this feature a "Hosted UCS 6.1(a) Full Number Translation - TimesTen DB" package containing a HUCSprovx10 application and a 64-bit Java package should be uploaded and installed on the PGW as part of the Static Configuration.
•In previous Cisco Hosted UCS releases, the gatekeeperId HSI RAS parameter and the Gatekeeper local zone name was configured with "GL_ZONE". In Hosted UCS 6.1(a) this should be replaced with "HUCS_ZONE".
Support for SIP and SCCP Endpoints
Table 1 summarizes the Unified Communications Manager features that are supported with SIP and SCCP endpoints in Cisco Hosted Unified Communications Services Release 6.1(a):
Table 1 Feature Support for SIP and SCCP Endpoints in Cisco Hosted Unified Communications Services, Release 6.1(a)
Cisco Unified Communications Manager Feature Name Support for SCCP Endpoints in Cisco Hosted UCS 6.1(a) Support for SIP Endpoints in Cisco Hosted UCS 6.1(a)
Answer and answer release
Auto-answer and intercom
Call forward-All (off net and on net), busy, and no answer
Call hold and retrieve
Call park and pickup
Call waiting and retrieve
Calling line identification (CLID) and calling party name identification (CNID)
(View) Conference list and drop any party (impromptu conference)
Direct inward dial (DID) and direct outward dial (DOD)
Directories-Missed, placed, and received calls list stored on selected IP phones
Extension mobility support
Hands-free, full-duplex speakerphone
Last number redial (on and off net)
Multiple calls per line appearance
Multiple line appearances per phone
Music on hold
Mute capability from speakerphone and handset
Recent dial list-Calls to phone, calls from phone, autodial, and edit dial
Service URL-single-button access to IP phone service
Speed dial-Multiple speed dials per phone
Station volume controls (audio and ringer)
Transfer-Blind, consultative, and direct transfer of two parties on a line
1 Not supported in Cisco 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 Hosted Unified Communications Services, Release 6.1(a); the provisioning method per product is specified. For supported releases of each component and product, refer to the Software Compatibility Matrix at the following URL:
* For Cisco Emergency Responder Integration into Cisco Hosted UCS Unified CM, PGW and Cisco Integrated Services Routers are provisioned via BVSM to enable correct routing of emergency calls.
Limitations and Observations
This section describes the limitations and restrictions that generally affect Hosted UCS and that affect specific new features in each release. This section includes the following topics:
Limitations and Observations In Release 6.1(a)
This section includes observations about the features and enhancements introduced in Cisco Hosted Unified Communications Services, Release 6.1(a). It includes the following topics:
Limitations and Observations in Support for Shared Building
This section describes the limitations and observations affecting the shared building feature in Cisco Hosted Unified Communications Services, Release 6.1(a)
•Standard customers with a location in a Shared building are currently not supported.
•Inter-site dialling is not permitted for Shared building customers. Only E.164 numbers and extension dialing inside a location are supported, apart from retrieving Voicemail, for which users would normally access VM via a message button on the phone. Customers within a building can only dial each other using full E.164 numbers.
•You can create shared building locations either from the Building menu or by using the traditional method of creating customers/locations by just moving the location to the building.
Note For ease of provisioning, Cisco recommends using the Building menu for creating shared building locations.
•Each user in a Shared building has a unique SLC. Therefore, users who have the current Hosted UCS implementation and try to access voicemail, must provide Site Location Code (SLC) + Extension (EXTN) to identify the voicemail box. Customers in a Shared building must also be informed about the passcode that they should use with their extension number to identify their voicemail box.
•Feature groups can be created at the Building level or at the customer level. Customers can use their own feature group or use a generic feature group used by all customers in the building.
Note Cisco recommends that you have one voicemail service per building and all customers in the building should use this service.
•When Hosted UCS customers use call forwarding extensions, the SLC+EXTN is displayed. This is an enhancement for shared building customers and only the correct extension for both forwarded from/to fields are displayed on the terminating phone. The same behavior applies for calls from PSTN to IP Phones in shared building locations.
Limitation and Observations in Movius AutoAttendant Support
This section describes the limitations and observations affecting Movius AutoAttendant Support in Cisco Hosted Unified Communications Services, Release 6.1(a):
•BVSM cannot create the MWI On and MWI Off devices in Cisco Unified CM due to AXL API limitations. At present this has to be performed manually.
•Movius AutoAttendant provisioning is primarily performed manually on the Movius side. PGW is provisioned by BVSM and AutoAttendant is enabled in the Voicemail organization by BVSM, but the rest of the configuration on Movius (creating the AutoAttendant on the organization, adding the Keys for the AA Pilot and configuring the AA menus) must be performed manually by the system integrator due to a restriction on Movius, which lacks support for these configurations via XML.
•Movius AutoAttendant is configured to monitor all the calls, that is, call flow requires two media ports throughout the duration of the call. Some call flows may fail, for example, forwarding calls transferred by the AutoAttendant. For this reason an MTP is required on the voicemail trunk on Unified CM.
•Movius AutoAttendant feature can transfer calls by AA to Hosted UCS and PSTN phones using the central gateway breakout. However, presently, calls cannot be routed out through a local gateway due to bugzilla 4139.
•If the AA transfers a call using site code and extension, the destination will see the number of the initiator of the call. If it uses the full E164 number, the caller ID presented to the destination will be the pilot number of the AA.
•For Movius AutoAttendant to be able to transfer calls, it is recommended to disable the numbering plan on Movius servers. For Movius Voicemail, it is recommended to disable the unwanted voicemail prompts and unsupported Hosted UCS voicemail prompts. Please refer to the Static Configuration section of Movius integration in the Hosted UCS 6.1(a) Provisioning Guide
•In order to create an AutoAttendant pilot for a location, at least one location should have a voicemail service configured.
•If the same Movius server is used for multiple Providers, the Movius organizations can be provisioned with an incorrect Call Agent ID, which is required for routing MWI and Outgoing calls. To provision the correct Call Agent ID a new variable is required when adding a VoiceMail Pilot number. As a workaround, the Call Agent ID for MWI and Outgoing calls handling of the newly provisioned Organization should be modified manually. BVSM bugzilla 3523 was raised to address this issue.
•It is not possible to add an end user with the same username on two different customers, divisions, resellers or providers. A workaround is to use unique usernames when creating end users regardless of the customer, division, reseller or provider. This is considered an area that will raise usability issues from customers. BVSM bugzilla 3552 has been raised to address this issue, but VisionOSS have indicated that this is how BVSM was designed.
Limitations and Observations in Cisco Unified Contact Center Hosted Integration
This section describes the limitations and restrictions affecting Cisco Unified Contact Center Hosted Integration in Cisco Hosted UCS Release 6.1(a):
•Unified CCMP imports directory numbers provisioned by BVSM on the Cisco Unified CM. Those directory numbers are in FINT format so there is no way to avoid showing FINT number format in CCMP and in the Intelligent Contact Management (ICM) system. CCMP and ICM administrators must understand FINT format.
•Contact Center labels have fixed length (32 digits) and FINT have variable length of approximately 15-16 digits or more. There might be an issure in manipulating those digits in the ICM system (for example if a label needs to carry both an A number and a B number).
•Pilot numbers need to be provisioned in E.164 number format in order to be correctly routed from the PGW to Customer Voice Portal.
•Presently, you cannot associate IP phones to application users via BVSM because the BVSM platform works via thick AXL SOAP transaction. Also, the complete management of application user on the Cisco Unified CM via thick AXL SOAP transaction will be available only in a later release of Cisco Unified Communications Manager.
Note Be aware that this is not a BVSM limitation but a limitation in Cisco Unified Communications Manager versions 4.X, 5.X, and 6.X.
•CCMP can associate IP phones to an application user (as it uses SQL tiny transactions connecting directly to Cisco Unified CM database) but requires Cisco Unified CM to be provisionable from CCMP. Setting Cisco Unified CM provisionable from CCMP allows CCMP to make other changes on Cisco Unified CM.
Note Cisco does not recommend limiting administrator rights on CCMP, becasue by allowing even the minimum required privileges will enable the administrator to manage objects. This includes the entire IP phone configuration, which could eventually lead to significant problems in trying to maintain data integrity on both the products. Consequently, the only suggested workaround is to perform the association on Cisco Unified CM itself.
Cisco IP IVR must configure to Unified CM. However, this can then lead to data integrity issues. Cisco IP IVR is not a product that is at the moment integrated within Hosted UCS, and therefore can not be provisioned via BVSM. To integrate Cisco IP IVR while avoiding any possible conflict on IP IVR/BVSM, the Cisco Hosted Unified Communications Services, 6.1(a) Provisioning Guide will carry a suggested convention that can be followed to configure CTI ports and CTI route points. In addition, the method to allocate directory numbers via BVSM that can be used for CTI ports and CTI route point will get reported.
Limitations and Observations in Cisco Emergency Responder Integration
This section describes the limitations and observations affecting Cisco Emergency Responder Integration in Cisco Hosted Unified Communications Services, Release 6.1(a):
•There is only one instance of a Default ERL within Cisco ER which must be used by all Cisco Unified CM clusters regardless of the end customer for each site. Similarly, the Default Onsite security number is a number within the Service Providers network which is answered by a Service Provider representative. There can only be one number defined in the PSAP callback route point and this number needs to be used by all Cisco Unified CM clusters regardless of the end customer for each site. Since there is only one instance of a Default ERL within Cisco ER, this makes the Default ERL non-multi tenant and therefore not completely E911 compliant since 'ideally' there should be a Default ERL instance per customer.
•Since the Hosted UCS architecture does not support inter-cluster trunks, inter-group Cisco ER communication is not supported in this Hosted UCS release.
•In Hosted UCS 6.1(a), CAMA trunks cannot be configured.
•Cisco ER server is manually configured. There is no interaction between BVSM and the Cisco ER server.
•For the integration of Cisco ER into Hosted UCS, it is necessary to disable the modification of the Calling Party Number via Cisco ER. Instead, the modification of the CgPN is done on the Route Point on Cisco Unified CM. In Cisco ER version 1.3(2), it was possible to disable the Calling Party Modification on Cisco ER via the Cisco ER Group Settings Page, by not selecting the "Enable Calling Party Modification" option. However this was not possible in Cisco ER version 2.0(3). CDETS CSCsu86507 was opened to address this issue, and a patch was provided for disabling Calling Party Modification in Cisco ER. CSCsu86507 is integrated in Cisco ER 2.0(4).
•BVSM cannot provision the "Cisco ER Cisco Unified CM" user in Cisco Unified CM due to AXL API limitations. The administrator must manually create the "Cisco ER Cisco Unified CM" user in Cisco Unified CM.
•BVSM cannot add additional partitions to an existing CSS. Because of this, the administrator needs to manually add the created Cisco ER partition (for example EUSA), to the IncomingToCluster CSS.
•If a user makes an emergency call and Cisco ER is not available or the phone is unallocated in Cisco ER, the call will be sent out of the PGW Central gateway trunk towards the PSAP operator servicing the Default ERL (CdPN: 911, CgPN: ELIN for the Default ERL). Because there is only one configurable number for the Default ERL, this number will have to be sent out as the Calling Party Number for all Hosted UCS customers. If the PSAP operator tries to call back, the call will be routed to an SP representative servicing the Default ERL.
•If a user makes an emergency call and the PSAP operator answers the call and after that the PSAP operator calls back, but then Cisco ER (the PSAP callback CTI Route Point) is unavailable, the call will be routed to the SP representative servicing the Default Onsite security, which will be the ELIN for the Default ERL (CdPN will be the SP representative E.164 number (ELIN for the Default ERL), and the CdPN will be the PSAP operator number).
•Enhanced emergency handling in SRST mode is currently not supported in Hosted UCS.
Limitations and Observations in Local PSTN Breakout Support
This section describes the limitations and observations affecting Local PSTN Breakout support in Cisco Hosted UCS Release 6.1(a):
•When the IP phones are in SRST mode, the FINT (full internal number representation for DNs) on the phone display when the phone is Onhook. Also when an IP-to-IP call is connected, the FINT is shown on the originating phone.
•When the IP phones are in SRST mode, the user can only dial the full E.164 number to make calls as configured; however, it may be possible to add the necessary dial patterns to allow extension dialing.
•Within the Hosted UCS architecture, Cisco Unified SIP phones are not supported when local gateways are in SRST mode (this is not true outside of the Hosted UCS architecture).
•All outgoing National/International calls to PSTN via local gateway in SRST mode have ANOA/BNOA set to unknown, regardless of the settings (NOA, NoNOA) made in BVSM during configuration of the voice trunks for the local gateways.
•Call forwarding in SRST mode is not supported when the forwarding number is set to an E.164 number. Currently this feature only works when calls are forwarded to FINTs. (CSCsm78612).
•When the IOS driver is invoked to provision an IOS device, there is no procedure to save the IOS configuration before and after the transaction.
•Central gateway support for local calls (NOA=SUBSCRIBER setting/handling) is provisioned manually. There are scenarios in which the Cisco PGW may be connected to the PSTN and BVSM does not have the required information. The system integrator must customize the Ingress and Egress PSTN dial plans to enable this feature.
•Cisco Unified IP phones (SIP) are not supported when local gateways are in SRST mode.
•The following call flow is not supported: CFU (Call Forward Unconditional) to the PSTN for calls coming from PSTN when central gateways are not available.
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.
Limitations and Observations in Migration from Hosted UCS 5.1(b) MR1 to Hosted UCS 6.1(a)
This section describes the limitations and observations affecting migration from Hosted UCS 5.1(b) MR1 to Hosted UCS 6.1(a) in Cisco Hosted UCS Release 6.1(a):
•If a new VoiceMail Service Profile is required at the location level, the administrator needs to re-add the VoiceMail Pilot Number, which means that all Location VoiceMail services must also be deleted and added again.
•If a location has been upgraded manually (DisassociateFNN and AssociateFNN was not invoked via BVSM), and you want to delete a location, you must perform the following procedure after all the phones are unregistered and Extension Mobility profiles deleted:
Step 1 Set the PGW to Manual mode.
Step 2 DisassociateFNN.
Step 3 AssociateFNN.
Step 4 Set the PGW out of Manual mode.
Step 5 DisassociateFNN.
•If an upgraded or newly provisioned customer requires Movius AA support, the existing "Movius VM server - PGW - Unified CM" hardware group cannot be modified to add the Movius AA server. As a workaround, you can create a new hardware group with all the components.
•As soon as all locations are upgraded, the DisassociateFNN mml scripts should be removed from the BVSM database.
•If the customers wish to show the National Area Code on the External Phone Number Mask, the parameter for showing National Area Code on the External Phone Number Mask should be modified in the Dial Plan Construction page before any new number ranges are added to BVSM.
•Loading the Cisco Unified CM model into BVSM can cause disruption to end users (for example, the users might not be able to log into their phones).
Note Cisco recommends that loading Cisco Unified CM into BVSM is performed during non-peak hours.
•If "Forced" OffNet was provisioned in Hosted UCS 5.1(b) MR1 first by replacing the PGW transaction used for the "Forced" Central PSTN Breakout feature in the PGW model, with the PGW transaction required for the "Forced" OffNet feature, and then by utilising the BVSM screen for provisioning "Forced" Central PSTN Breakout, you should delete this configuration before upgrading to Hosted UCS 6.1(a).
Note Once upgraded to Hosted UCS 6.1(a) you must re-provision the previously configured numbers using the provisioning steps described in the Cisco Hosted Unified Communications Services Release 6.1(a) Provisioning Guide.
•If Block Off-Net to Off-Net Call Transfer Support feature is required in Hosted UCS 6.1(a) and was not provisioned in Hosted UCS 6.1(a), all OffNet Unified CM Route Patterns for all locations provisioned in Hosted UCS 5.1(b) MR1 must be indicated as OffNet before the feature can be used. This is so because the locations created in Hosted UCS 5.1(b) MR1 have all Route Patterns set to OnNet. Bugzilla 3711 [Sev Major] was raised after the Hosted UCS 5.1(b) MR1 to address this issue.
•The Block Off-Net to Off-Net Call Transfer trigger on the PGW was set to OffNet by Default in Hosted UCS 5.1(b) MR1. In BVSM the setting is set to Disabled by default (since the default setting of the trigger on the PGW in Hosted UCS 6.1(a) is set to OnNet). Therefore, the administrator must enable or disable this feature for all upgraded customers to ensure that the PGW and BVSM configurations are synchronized.
This section describes the general limitations and observations from previous Hosted UCS releases that affect Hosted UCS 6.1(a).
•If both Cisco Unified CM 4.X and 5.X are deployed, a number of phone button templates need to be statically added to the Cisco Unified CM 4.X clusters. VisionOSS BVSM defect 1919 was opened to address this issue.
Note VisionOSS uses Bugzilla for tracking defects, while Cisco uses DDTS/CDETS.
•There is no mechanism in BVSM to roll back the Cisco Unified CM configuration if a Cisco Unified CM transaction fails. If a Cisco Unified CM transaction fails in BVSM, anything configured on the Cisco Unified CM before the transaction failed will not be deleted from Cisco Unified CM by BVSM.
•BVSM cannot create an SRST reference in Cisco Unified CM because the Cisco Unified CM AXL API does not currently support this.
•When using a collection of various types of phones on Cisco Unified CM 5.1 or 6.1, the system parameter that indicates Advertise G.722 Codec should be disabled to prevent issues where phones may not support this codec.
•On Cisco Unified CM 5.1 or 6.1, set the following system parameter as part of the static configuration:
check progress indicator before establishing media
This prevents interoperability issues between HSI and Cisco Unified CM, to prevent timeout issues when 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 six seconds before answering the call, the call is dropped.
•When a user picks up a local (intrasite) call, the destination sees the FINT of the called party.
•When the list of conference parties is invoked on the phone, the conference initiator number is displayed as an FINT number (DDTS CSCsj72325).
•A transit link between Cisco PGWs prevents successful PBX calls. The problems are described as follows:
–A transit set is created between PGW1 and remote PGW2 via BVSM and then a legacy PBX is introduced into the Provider network.
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.
–Customer tries to introduce a new Cisco PGW or Cisco Unified CM into the network.
Outcome: It is not possible for a Provider to introduce a new Cisco PGW or Cisco 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 Cisco Unified CM and PGW.
–Provider has local PGW1, remote PGW2 and legacy PBX in the network and provisions the legacy PBX before placing an EISUP link to the remote 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.
•Because the Cisco PGW does not allow modification of connected numbers (CSCsj68610), Cisco Unified CM sends FINTs (full internal number representation for DNs) for connected numbers. Because these cannot be modified by the Cisco PGW, connected number updates are prevented at the calling phone by setting the flag NotifyMsgEnable to false on the HSI. However, this also prevents any mid-call events (CLI updates due to call transfer, call forwarding, and so forth) from being received by the Cisco PGW.
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.
BVSM automates the Cisco 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 Cisco 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 Cisco Unified CM 5.1(3) and 4.2(3). As a workaround, lines 1897 and 1898 of the Cisco Unified CM model should be changed and reloaded according to the Cisco Unified CM version for which you are creating the VM Service. For Cisco 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 Cisco Unified CM version in use.
Support for Countries Without Area Codes
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.
This section describes the open and unresolved caveats affecting Cisco Hosted UCS Release 6.1(a), 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:
•Cisco.com user ID and password
To use the Software Bug Toolkit, complete the following steps:
Step 1 To access the Bug Toolkit, go to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.
Step 2 Log on with your Cisco.com user ID and password.
Step 3 Click the Launch Bug Toolkit hyperlink.
Step 4 To look for information about a specific problem, enter the bug ID number in the "Enter known bug ID" field and click Search.
The following tables list defects that are unresolved in Cisco Hosted UCS Release 6.1(a). 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 Cisco Hosted UCS Release 6.1(a). To view a current list of unresolved defects, use the Bug Toolkit as described in the "Using the Bug Toolkit" section.
This section describes the resolved caveats affecting Cisco Hosted UCS Release 6.1(a), 5.1(b) and BVSM Release 3.1.8. This section contains the following topics:
Resolved Caveats in Cisco Hosted Unified Communications Services, Release 6.1(a)
Table 3 lists defects that that affected an earlier release and were resolved in Cisco Hosted Unified Communications Services Release 6.1(a).
Resolved Caveats in Cisco Hosted Unified Communications Services, Release 5.1(b), Maintenance Release 1
Table 4 lists defects that affected an earlier release and were resolved in Cisco Hosted Unified Communications Services, Release 5.1(b), Maintenance Release 1.
Resolved Caveats in Cisco Hosted Unified Communications Services, Release 5.1(b)
Table 5 lists defects that affected an earlier release and were resolved in Cisco Hosted Unified Communications Services Release 5.1(b).
Resolved Caveats in BVSM, Release 18.104.22.168
Table 6 provides a numeric listing of the caveats that affected an earlier release and were resolved in BVSM Release 22.214.171.124.
Resolved Caveats in BVSM, Release 126.96.36.199
Table 7 provides a numeric listing of the caveats resolved in BVSM, Release 188.8.131.52 that affected an earlier release.
Resolved Caveats in BVSM, Release 3.1.8
Table 8 provides a numeric listing of the caveats that affected an earlier release and were resolved in BVSM Release 3.1.8.
Resolved Caveats in Cisco Hosted Unified Communications Services, Release 1.6.1
Table 9 lists the unregistered defects that affected an earlier release and were resolved in Cisco Hosted Unified Communications Services, Release 1.6.1.
This section lists defects that are unresolved in Cisco Hosted Unified Communications Services,release 6.1(a). Additional tables list VisionOSS BVSM defects that are unresolved in Hosted UCS Release 6.1(a), at the time of release.
Note 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.
Note Be aware that defect status frequently changes, these tables list the defects that were unresolved at the time of the release of Cisco Hosted Unified Communications Services, Release 6.1(a). To view a current list of unresolved defects, use the Bug Toolkit as described in the "Using the Bug Toolkit" section.
Note For details and information about the current status of these defects, and for any workaround available, contact VisionOSS.
This section contains the following topics:
Unresolved Caveats in Cisco Hosted Unified Communications Services, Release 6.1(a)
Table 10 lists the defects that are unresolved in Hosted UCS Release 6.1(a).
Unresolved Caveats in Cisco Hosted Unified Communications Services, Release 5.1(b), Maintenance Release 1
Table 11 lists the defects that were unresolved in Cisco Hosted Unified Communications Services, Release 5.1(b), Maintenance Release 1 and affect Cisco Hosted Unified Communications Services, Release 6.1(a).
Unresolved Caveats in Cisco Hosted Unified Communications Services, Release 5.1(b)
Table 12 lists the defects that were unresolved in Cisco Hosted Unified Communications Services, Release 5.1(b) and affect Hosted UCS Release 6.1(a).
Unresolved Caveats in BVSM, Release 184.108.40.206
Table 13 lists the defects in BVSM 220.127.116.11 that were unresolved and affect Cisco Hosted Unified Communications Services, Release 6.1(a).
Unresolved Caveats in BVSM, Release 18.104.22.168
Table 14 lists the defects in BVSM 22.214.171.124 that were unresolved in Cisco Hosted Unified Communications Services, Release 5.1(b), Maintenance Release 1 and affect Cisco Hosted Unified Communications Services, Release 6.1(a).
Unresolved Caveats in BVSM Release 3.1.8
Table 15 lists the defects in BVSM 3.1.8 that were unresolved in Cisco Hosted Unified Communications Services, Release 5.1(b) and affect Cisco Hosted Unified Communications Services, Release 6.1(a).
Unresolved Caveats in Netwise
Table 16 provides a listing of the Netwise caveats affecting HUCS Release 5.1(b) that were unresolved at the time of the release.
Table 16 Unresolved Netwise Caveats Affecting HUCS Release 5.1(b)
Netwise Identifier Headline
Passive redirect is not activated when all ACD Attendants are blacklisted.
QueueEntryPoint overflow/pasv.redir number cannot contain *#.
Unresolved Caveats in Hosted UCS Release 1.6.1
Table 17 lists the defects that were unresolved in Cisco Hosted Unified Communications Services, Release 1.6.1 and affected Cisco Hosted UCS Release 6.1(a).
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:
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 ` Alaws, 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 email@example.com.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo 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. (0809R)
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.
© 2009 Cisco Systems, Inc. All rights reserved.