1 / 10

Unity 5.0 Logging & Licensing Changes Summary

Explore changes, licensing details, and port support for Unity 5.0 system. Learn about new logging formats, licensing requirements, and port support configurations.

arroyo
Download Presentation

Unity 5.0 Logging & Licensing Changes Summary

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Unity 5.0 TOI

  2. Logging changes Licensing changes 144 port support • Michael McCann • mrmccann@cisco.com

  3. Logging changes – tempu.log • CSCed26347 was resolved to address some problems with the tempu.log. The main change is that the tempu.log will be stored in \Commserver\Logs instead of %temp% directory. Other notable changes: • Format of file name is changed to tempu_<date>_<time>.log • Log files are created in the temp directory first, and then moved to the \Commserver\logs directory after the destination directory path is picked in Setup. • Future tempu files will not append to the previous log since the log file name is unique now. Tempu files are not automatically deleted, they remain in the logs directory indefinitely for future reference. • One tempu file is created during Unity Setup and a second is created during the Service Configure Wizard. Both files follow the same conventions outlined above.

  4. Logging changes – AvSaDBConn traces • The traces for SA troubleshooting are logged differently. In previous Unity versions, AvSaDBConn diagnostic traces were written to diag_AvCsMgr*.txt files. In Unity 5.0 this has changed. • On Unity servers running Windows 2003, AvSaDBConn traces are logged to diag_w3wp*.txt files. • On Unity servers running Windows 2000, AvSaDBConn traces are logged to diag_inetinfo*.txt files.

  5. Logging changes – Conversation micro trace consolidation • In Unity 4.2(1) and earlier, conversation diagnostics were enabled by setting a number of different micro traces – Comm Voice Mail Conversation, Conv AMIS, Conv PhoneHandler, ConvPH Greeting, ConvPH Interview, ConvPH Transfer, Greetings Admin, Hospitality Conversation, Subscriber Conversation • As a serviceability improvement in Unity 5.0(1), the above traces have all been consolidated into the Conversation micro trace tree. • **Conv AMIS traces are set by enabling Conversation 19 – AMIS.

  6. Logging changes – Better exception handling event log error • CSCec45356 was resolved for Unity servers running Windows 2003. • When an exception occurs, the event log error will contain a more complete and accurate stack dump compared with previous versions of Unity. This will help pinpoint problems better using event logs, rather than requiring a User Dump. User Dumps will still be useful in troubleshooting some issues, however. • Documentation on how to use Microsoft tools to diagnose an exception/crash is located here:http://wwwin-eng.cisco.com/Eng/ECSBU/Serviceability/UserDump.dochttp://wwwin-eng.cisco.com/Eng/ECSBU/Serviceability/UnityADPlusDump.doc

  7. Licensing changes – Upgrade license • An upgrade license is required for a customer to upgrade from Unity 4.2(1) and earlier to Unity 5.0(1). The upgrade license is similar to an additional feature license in that the upgrade license is installed in addition to existing licenses. The upgrade license will simply activate the 4.x licenses on a Unity 5.x server. The setup process prompts for the installation of the upgrade license. • Note: In order to upgrade a Unity server running a demo license, the Unity 4.x demo license must be removed, and the Unity 5.x demo license must be installed.

  8. Licensing changes – License pooling • In order to use license pooling between Unity 5.0(1) systems and Unity 4.x systems, an ES must be applied to each Unity 4.x system that is sharing licenses. The following ESes will resolve this problem (documented in CSCsg49334). • CU4.1(1)_ES47 • CU4.2(1)_ES86 • CiscoUnity4.0(5)_ES92

  9. 144 port support requirements • Unity must be running on Windows 2003 • Integrations supported • – SCCP (Cisco Unified CM and Cisco Unified CM Express) • – SIP (including Cisco Unified CM and Cisco Unified CM Express) • - PIMG pending test completion, should be supported shortly after release • Windows 2003 must be installed on the Cisco Unity server. • The /3GB and userva switches must be added to the Boot.ini file. • The “Messaging - 72 or More Voice Ports - Enable Low-Fragmentation Heap” setting in the Advanced Settings Tool must be enabled. • If Exchange is the message store, the “Messaging - 72 or more voice ports - Number of MAPI Sessions per Exchange Server” setting in the Advanced Settings Tool must be set to the applicable value (see AST help for this value for more information).

More Related