Solution for you
To Download RTMT IN UCCX
Download RTMT.
— NS Team
Follow the below steps to install the RTMT.
Step 1:
Step 2:
1.Plugins download page will open.
2.Select Cisco Unified Serviceability Real-Time Monitoring Tool.
3.Click save file and Install.
An annunciator, an SCCP device that uses the Cisco Media Streaming Application service, enables Cisco Unified Communications Manager to play prerecorded announcements (.wav files) and tones to Cisco Unified IP Phones and gateways.
The system automatically displays the preconfigured server (servers get added at installation).
Cisco Unified Communications Manager automatically provides a set of prerecorded annunciator announcements when you activate the Cisco IP Media Streaming Application service. An announcement or a tone is played for the following conditions:
You cannot change the default prerecorded annunciator announcements or add additional announcements.
Prerecorded Annunciator Announcements
| Condition | Announcement |
|---|---|
| An equal or higher precedence call is in progress. | Precedence access limitation has prevented the completion of your call. Please hang up and try again. This is a recording. |
| A precedence access limitation exists. | Precedence access limitation has prevented the completion of your call. Please hang up and try again. This is a recording. |
| Someone attempted an unauthorized precedence level. | The precedence used is not authorized for your line. Please use an authorized precedence or ask your operator for assistance. This is a recording. |
| The call appears busy, or the administrator did not configure the directory number for call waiting or preemption. | The number you have dialed is busy and not equipped for call waiting or preemption. Please hang up and try again. This is a recording. |
| The system cannot complete the call. | Your call cannot be completed as dialed. Please consult your directory and call again or ask your operator for assistance. This is a recording. |
| A service interruption occurred. | A service disruption has prevented the completion of your call. In case of emergency call your operator. This is a recording. |
Tone Description
| Type | Description |
|---|---|
| Busy tone | A busy tone is heard when the dialed number is busy. |
| Barge tone | A conference barge-in tone is heard before the participant joins an ad hoc conference. |
| Ring back tone | An alert tone is heard for the following scenarios:When you transfer a call over the PSTN through an IOS gateway.When you transfer a call over an H.323 intercluster trunk.When you transfer a call to the SIP client from an SCCP phone. |
A media termination point (MTP) is an entity that accepts two full-duplex media streams. It bridges the streams together and allows them to be set up and torn down independently. The streaming data received from the input stream on one connection is passed to the output stream on the other connection, and vice versa.
An MTP can be used to transcode G.711 a-law audio packets to G.711 mu-law packets and vice versa, or it can be used to bridge two connections that utilize different packetization periods (different sample sizes).
MTPs extend supplementary services, such as call hold, call transfer, call park, and conferencing, that are otherwise not available when a call is routed to an H.323 endpoint. Some H.323 gateways may require that calls use an MTP to enable supplementary call services, but normally, Cisco IOS gateways do not.
MTP Types
Software MTP provided by the Cisco IP Voice Media Streaming App service on Cisco Unified Communications Manager:
Software MTP configured on Cisco IOS routers:
Hardware MTP configured on Cisco IOS routers:
A transcoder is a device that performs codec conversion, converting an input stream from one codec into an output stream that uses a different codec.
For example, a transcoder can take a G.711 stream and convert it to a G.729 stream in real time. When the two endpoints in a call use different voice codecs, Cisco Unified Communications Manager invokes a transcoder into the media path.
The transcoder converts the data streams between the two incompatible codecs so that communication can occur. The transcoder is invisible to either the user or the endpoints that are involved in a call.
Transcoder resources is managed by the Media Resource Manager (MRM).
Configure Transcoder in call manager:
Step 1: Log into Cisco Unified CM Administration and choose Media Resources > Transcoder.
Step 2: Click Find and select an existing transcoder. Click Add New.
Step 3: Select the Transcoder Type.
Step 4: Enter all the necessary fields.
Step 5: Assign a Device Pool from the drop-down menu.
Step 6: Click Save.
Add Transcoder to Media Resource Group
Step 1: Choose Media Resources > Media Resource Group.
Step 2: Click Find to display the list of configured Media Resource Groups.
Step 3: Click on the required Media Resource Group.The Media Resource Group Configuration window displays.
Step 4: Select the transcoder from the list of available media resources and add it to the Selected Media Resources list.
Step 5: Click Save.
Step 6: Navigate to Media Resources > Media Resource Group.
Step 7: In the Find and List Transcoders window, check the check boxes next to the transcoders that you want to synchronize. To choose all transcoders in the window, check the check box in the matching records title bar.
Step 8: Click Apply Config to Selected.The Apply Configuration Information dialog box displays and click OK.
Command to register in VG
!
dspfarm profile 10 transcode
codec g729abr8
codec g729ar8
codec g711alaw
codec g711ulaw
codec pass-through
maximum sessions 20
associate application SCCP
!
!
sccp ccm group 999
associate ccm 1 priority 1
associate ccm 2 priority 2
associate ccm 3 priority 3
associate profile 10 register Chola-xcode-vg1
keepalive retries 5
switchover method immediate
switchback method immediate
switchback interval 15
!
!
Partition:
Partitions can be seen as a collection of route patterns.
Directory numbers, route patterns, and translation patterns can all belong to specific partitions.
CSS(Calling Search Space):
CSS’es are an ordered list of route partitions and they determine which partitions calling devices must search when they attempt to complete a call. In order to reach a certain destination, the called party’s partition must belong to the calling party’s CSS.
When you attempt to make a call, Cisco CallManager looks into the CSS of the calling party and checks if the called party belongs to a partition within the CSS. If it does, the call is placed or the translation pattern is executed. If not, the call is rejected or the translation pattern is ignored.
For a better understanding, providing a example below.
In an organisation, we are having three teams, say IT Team, Business Team and Internal Team and we are having calling condition as below.
Partition Needs to be created:
CSS Needs to be created:
CSS and PT Mapping:
Mapping of CSS, PT for Teams.
Sample CSS, Partition creation and mapping
Partition Creation:
Navigate to Call Routing –> Class of Control –> Partition
Add new -> Give a name and click on save.
CSS Creation and partition mapping:
Navigate to Call Routing –> Class of Control –> calling search space.
Add New-> GIve name, Description and associate the partition in it-> save
Mapping of partition and CSS in phones:
Navigate to line page of the phone->Select partition and CSS–> Save
CUCM uses Informix as its database , and there is no native access to it, other then through AXL queries and queries via CLI. (Unless you are a Cisco TAC engineer, in which case a local hash value gets put into a hash value, which will the generate temporary root access).
If db replication breaks, there are many symptoms such as phones registered on call manager group A are unable to call phones on call manager group B, or when logging into extension mobility on Subscriber A, when DB replication is bad another, phone registered on Subscriber B might not be able to complete a call to the newly logged in user.
We can check the DB replication status of the call manager in three ways.
CLI
Step1: Open CUCM CLI via Putty.
Step2: Put the command “utils dbreplication runtimestate”.
1: This lets you know the last action performed and the time of the action. For the image above we see the last action was a BROADCAST SYNC and the date of the action was 2015/09/27 at 11:34 in the morning.
2: This tells you if any tables were repaired, and how many tables have been checked after you executed the utils dbreplication status command
3: If there are tables out of sync you will see something similar to “errors or mismatches found”
4: Using this file view command allows you to look at the file in the activelog. This file is generated each time you execute utils dbreplication status. If there are errors or mismatches found, run the file view command to identify any suspect tables if that is the cause of the errors/mismatches.
5: This is the database version. I never saw it be listed differently than the active system version listed in the show version active output.
6: This is the replication timeout for all the nodes.
7: This is the ping time between the servers.
8: This lets you know if the DB, RPC, and DBMon services are working fine.
DB = A Cisco DB
RPC = A Cisco DB Replicator
DbMon = Cisco Database Layer Monitor
9: This shows how many bytes of replication data in queue to be sent to a particular node. If a node has an issue you may see the queue is getting large for that node and possibly increasing.
10: This shows the node id. g_# with the number being the node id. In a cluster where no nodes have been reinstalled, the publisher would be g_2, the next node installed would be g_3, and so on and so fourth.
11: This shows the RTMT states for database replication. There are 5 states.
| Value | Meaning | Description |
|---|---|---|
| 0 | Initialization State | This state indicates that replication is in the process of trying to setup. Being in this state for a period longer than an hour could indicate a failure in setup. |
| 1 | Number of Replicates not correct | This state is rarely seen in 6.x and 7.x but in 5.x can indicate its still in the setup process. Being in this state for a period longer than an hour could indicate a failure in setup. |
| 2 | Replication is good | Logical connections have been established and tables match the other servers on the cluster. |
| 3 | Tables are suspect | Logical connections have been established but we are unsure if tables match. In 6.x and 7.x all servers could show state 3 if one server is down in the cluster. This can happen because the other servers are unsure if there is an update to a user facing feature that has not been passed from that sub to the other device in the cluster. |
| 4 | Setup Failed / Dropped | The server no longer has an active logical connection to receive database table across. No replication is occurring in this state. |
GUI
Step1: Login CUCM admin page and navigate to “Cisco Unified reporting”.
Step2: Click on unified database status.
Under Unified CM database status, you can find the replication status for all the nodes.
RTMT Tool
Step1: Login RTMT using call manager IP.
Step2: Navigate to Call manager -> Service -> Database Summary.
Restarting a server closes all the processes that are running and starts them again. Restart of server is necessary for the system to reduce the failure that is due to long term running of servers/Services.
Ensure that the restart happens at a time only when the server is being scheduled for maintenance.
There are two ways to restart the Call Manager.
Step1: Login Call Manager through CLI.
Step2: Put the Command “Utils System restart”.
Step3: Press Enter.
2. GUI
Step1: Open Call Manager GUI and navigate to “Cisco Unified OS Administration” in the upper right corner.
Step2: click on Settings -> Version.
Step3: click on reboot.
The best way to restart the call manager is from CLI, because once the server is up you can see the service status of the call manager through the command “utils service list”.
There are logs in call Manager for each service running on it. The logs will be used to trace the cause for the issue, malfunction or abnormality in the server and its services. We have to be specific in the time frame of issue, so that we can collect the logs for the time frame to narrow down the issue
Step1: Login Call manager through RTMT Tool.
Step2: Click on Trace & log Central -> Collect files -> Select the required services for its log.
Step3: Click Next.
Step4: Select DateTime for log Collection and the path where the logs to be stored.
Step5: Click finish. The collected logs will be stored in mentioned folder.
The Network Time Protocol (NTP) is a protocol used to synchronize computer system clock automatically over a networks .
The synchronization of time on computers and networks is often vitally important. A mechanism is required to disseminate accurate time around a network to computers and network devices in order to maintain order.
For Cisco Servers, cisco recommends not to use windows servers as a NTP server, and we can probably use Cisco Routers as the NTP Server for other Cisco servers.
To check the NTP status and stratum in Call manager, follow the below steps.
Step1: Login Call manager in CLI (Using Putty).
Step2: Put Command utils ntp status and will be getting data as below.
The NTP Stratum (St) should below 5 then only the NTP client can be synced properly with the NTP server.
Step1: Login RTMT with CUCM IP.
Step2: Click on Device Summary and check the status of number of devices in each category.
Step 1: Navigate to Cisco Unified Serviceability
Step 2 : Click on Tab Tools and select CDR Management
Step 3: Add New
Step 4: Add Billing Application Server information
Step 5: Enter the details
Step 6 Click Update
Network Solutions