Примечания к выпуску для Cisco Cisco Unified Messaging Gateway Version 1.0

Скачать
Страница из 14
 
10
Release Notes for Cisco Unified Messaging Gateway Release 8.5
OL-23859-01
Caveats
Procedure
Step 1
Navigate to the Bug Toolkit URL:
Step 2
Log in to Cisco.com.
Step 3
Click Launch Bug Toolkit.
Step 4
Under Select Product Category, choose Voice and Unified Communications from the drop-down menu.
Step 5
Under Select Products, scroll down and highlight the following products depending on what license(s) 
you are running:
For SRSV, select Cisco Survivable Remote Site Voicemail
For E-SRST, select Cisco Enhanced Survivable Remote Site Telephony
For VPIM, select Cisco Unified Messaging Gateway.
Step 6
Choose the Cisco UMG version.
Step 7
(Optional) If you want to search the for keywords, enter the keyword or phrase.
Step 8
Click Use default settings.
Step 9
Click Search.
The Bug Toolkit displays a list of caveats that fit your search criteria.
Open Caveats for Cisco UMG Release 8.5.1
See the Bug Toolkit at 
 for the current 
open caveats.
CSCtj83109
Symptom: Provisioning fails when cnf-file location flash: is configured in CUCME.
Conditions: cnf-file location flash:
Workaround: Repeat provisioning of site.
CSCtj87653
Symptom: Provisioning a CUCME site will fail. 
Conditions: The issue occurs if the following conditions are met:
1.
Provisioning a CUCME site for the first time.
2.
Telephone-service is not configured in the CUCME.
3.
There are phones homed into the CUCME router. Once ESRST tries to provision the CUCME, there 
is a race condition in which after ESRST does a discovery of the CUCME configuration, the homed 
in phones registers to the CUCME. As a result the configuration discovery is outdated.
Workaround: The workaround is to retry the provisioning. The retry will then get an updated discovery 
of the CUCME configuration and provisioning will be successful. 
CSCtk00448
Symptom: If the provisioning end time is enabled and the Start or End times are either 12:XX a.m. or 
p.m., the provisioning does not stop at the End time.
Workaround: Do not enable the provisioning End time, or do not use 12:00, 12:15, 12:30, 12:45 a.m. 
or p.m. as either the start and/or end times.