International Avaya Users Group : Forums : Asa Alternative For Mac
UCCX and IP IVR: Initially, I was quite confused about the relationship between UCCX and Cisco Unified IP IVR. Lots of official docs reviewing & self-research finally clearly state that they are exactly the same software product using same software codes, the only difference is that they need different licenses be activated, and so do their relevant subsystems. In other words, Unified CCX provides the software capabilities for not just Unified CCX, but also Cisco Unified IP IVR. A single physical server can run only one of the Unified CCX packages, either Unified CCX or Cisco Unified IP IVR. Below is a high-level overview of Cisco UCCX system in terms of Supported HW platform, product components as well as functional roles.
Filed under Tagged. I have recently finished on-site setup & initial integration of almost a Full Cisco UC suit (CUCM, RTX, Webex, UCCX) for one of our customers, and most of those products and software versions have just been officially released by Cisco. Cisco Webex Meeting Server (CWMS) 1.x, for example, is such an product which the majority of UC guys or even Cisco employees are not quite familiar with, and its installation is much more sophisticated and time-consuming than other UC systems from Cisco. Therefore, I record the key steps of CWMS setup here as detailed as possible hoping that it could be of some help for those who are about to conduct the same tasks. Overall Network Diagram: Filed underTagged.
Background Info& Problem Description:. CUCM 8.6.1.20000-1 Installed on VMware machine, up and running perfectly. successfully shut down CUCM under CLI by issuing command “utils system shutdown”, and the VMware host is powered off automatically.
International Avaya Users Group : Forums : Asa Alternative For Mac 2017
power on CUCM VMware host again and login CUCM Admin webpage, it fails with error message “Database Communication Error”. Possible Causes:. This issue can occur when you try to login to the server after changes are made in the Publisher server, such as changing the hostname or IP address either through CLI or the OS admin page. if issue exists with no change made to CUCM Pub, it might be caused by CUCM Sub & Pub DB Replication issues, in which scenario Sub is not able to contact Pub’s Database. Or Informix Database embedded in CUCM is not running. Reference URL:.
Filed underTagged. CM5.2.1 Setup & Basic Configure: Access Administration Interface of CM5.2.1: Firstly, make CM network reachable through either Enterprise LAN or direct network cable connection between you PC (192.11.13.5/30) and CM Service Port (192.11.13.6/30, Eth 1 by default, labeled as Port 2 on Hardware Platform). International food recipes: roxio crunch for mac. Then, take a pick of below 3 methods to access the Administrative Interface of CM:. Web Administrative Interface:.
Avaya Site Administration (ASA): Graphic User Interface Tool for CM maintenance and administration, which is installed on your laptop. ASA can be downloaded from Web Admin Interface of S8300 / S8400 / S8700 Series Server.ASA can work in 2 modes:. Terminal Emulation mode (similar to using SAT commands under SSH CLI).
Graphically Enhanced DEFINITY Interface (GEDI) &Data Import. An SSH or Telnet client: to access the SAT CLI of CM server, System Administration Terminal (SAT) interface. Privilege of various login User ID: init: User ID for vendor, highest privilege, able to update license info.
Dadmin: User ID for distributor / partner, for daily maintenance, troubleshoot, upgrade, configure. Craft: default User ID with default password of “craft01”. Remote: User ID for remote dial-in access Other User IDs can be further created by init or dadmin.
Filed underTagged. SIP as an Internet Application Protocol: In UC world, SIP is very often referred as an equivalent of H323 protocol, thus the majority UC guys believe that SIP is a multi-media communication protocol used in Telecom world, which is actually a misconception. As a matter of fact, SIP is natively an Internet Application Protocol which can be reflected in below 3 perspectives. SIP relies on other Internet Services such as DNS/TCP/IP/UDP etc.
SIP message structure is heavily inherited from HTTP and SMTP. For instance, SIP message can be break down into 3 parts: Start-line (request or response), Header Field and Payload or Body Field; which is the same as HTTP. Besides, format of SIP Request/Response line also is a duplicate of HTTP’s. Even the Status Codes of SIP response line are inherited from HTTP protocol. SIP also borrows From/To/Subject headers from SMTP protocol and Content-Type/Content-Length headers from HTTP protocol. Apart from multi-media communications which is prevalent in UC, SIP also support a wide variety of internet applications making use of Content-Type Header. SIP Terminology: A detailed Review of SIP message structure is as below, Filed under Tagged.
Background Info: Files in Router Flash for CME to work properly Cisco IOS: CME version depends on the IOS file version you installed. Refer to for identifying the correct IOS version to download. Normally, IOS already includes the phone firmware for most phone model to work properly. CME Basic Files: make sure to download correct version according to your IOS version as well as CME version. It usually includes firmware of specific phone models, GUI files, Ringtones files, Phone background images, MoH files etc.
Phone Firmware Files: most likely to be included in IOS file or CME Basic Files, it can be downloaded individually for each phone model though. For Early CME versions: (x – major version y – minor version) SCCP firmware—P003xxyy.bin SIP firmware—P0S3xxyy.bin For Later CME versions: SCCP firmware—P003xxyyzzww: x – major ver y – major subver z – maintenance ver w – maintenance subver SIP firmware—P0S3-xx-y-zz: x – major version y – minor version z – subversion For Cisco ATA, the firmware filename begins with AT, while the ones for Cisco IP phone 7002, 7905 and 7912 begins with CP. For Java-based IP phones, such as 7911, 7941, 7941GE, 7961, 7961GE, 7970, and 7971; the firmware consists of multiple files including JAR and tone files, which should be all downloaded through TFTP for phones to work fine.
When specifying the firmware version for the phones to download under CME CLI, only firmware file name is required, no suffix. Additionally, for Java-based phones, below naming conventions are used for SCCP firmware image (TERMnn.xx-y-z-ww SCCPnn.xx-y-zz-ww). Filed underTagged.
Background Info: Reasons to use ISR 7200: According to below URL, it is recommended to use 7200 router in GNS with IOS 12.4(24)T which enables you to simulate CME version 7.x, while all other routers with 12.4(15)T allow you to access CME 4.x and older versions. Only 7206 out of 7200 series Routers can be simulated in GNS3: It is clearly stated that only 7206 platform is supported on GNS3 in below URL.
So, make sure you download 7206 Router IOS. How to save start-up config, flash & NVRAM of a router in GNS3: In order to save all your work in a GNS lab and enable you to work on it later, you need to save it as a project: File-Save Project As, and tick both the checkbox of “ Save nvrams and virtual hard drivers” & “ Save IOS startup configurations”.
Note that your running-config is not saved as start-up config until you click File-Save (it will export config to a local file which is used for config importing for every reloading or power on) after the “write” command under IOS CLI, otherwise you config disappears just after you stop the router and start again in GNS. Useful Reference URLs are listed as below: Filed underTagged. CUCM Trace Types & Prerequisites for Trace Collection Trace Types: There are 2 kinds of trace to collect for CUCM troubleshooting; SDI (System Diagnostic Interface) and SDL (Signal Distribution Layer). SDI Trace: mostly used by general voice engineers for troubleshooting the majority of CUCM issues. Plus, it is easier to understand than SDL. SDL Trace: consists of large amount of low-level information (interactions of different state machines), normally used by Cisco TAC engineer to deeply investigate complex issues.
Prerequisites for Trace & Logs Collection:. Enterprise Parameters - Cisco Syslog Agent: Remote Syslog Server Name: 10.10.10.10 Syslog Severity For Remote Syslog messages: Alert / Critical / Error / Warning / Notice. Enterprise Parameters - Max Number of Device Level Trace: 12 (default) How many devices can be traced concurrently for device name-based trace. Enterprise Parameters - Trace Compression: Enable (Default: Disable) 【not confirm】. Enterprise Parameters For Log Compress: Begin with CUCM 8.0, Log compression is not configurable, and only CTI/CCM SDL&SDI traces are compressed. Compressed files (.gz extension) / compressed files being actively written (.gzo extension). Cisco RIS Data Collector Service - Service Parameter: TLC Throttling CPU Goal: 80 (up to 80% CPU for TLC) TLC Throttling IOWait Goal: 10 (up to 10% IO for TLC).
CallManager Service Parameter - SDL Trace: SDL Trace Flag: True (default) Filed underTagged, Post navigation.
Attention, Internet Explorer User Announcement: Jive has discontinued support for Internet Explorer 7 and below. In order to provide the best platform for continued innovation, Jive no longer supports Internet Explorer 7. Jive will not function with this version of Internet Explorer. Please consider upgrading to Internet Explorer 8, 9, or 10, or trying another browser such as Firefox, Safari, or Google Chrome. (Please remember to honor your company's IT policies before installing new software!).