MGCP : Three steps configuration

-
Essentially only three steps are required to configure MGCP gateway.

R1(config)#mgcp
R1(config)#ccm-manager config
R1(config)#ccm-manager mgcp server <Primary TFTP IP address>
R1(config)#ccm-manager redundant-host <Secondary TFTP IP address> --- this command is optional, as suggests it provides secondary TFTP server as a redundant host.

A couple of important points to keep in mind :
1. Configure domain name on the gateway and configure gateway configuration on CUCM with the correct domain name.

2. Bind media with the source interface-
R1(config)#mgcp bind control source-interface <>
R1(config)#mgcp bind media source-interface <>

3. As soon as you configure pri-group timeslots with service mgcp under controller, it'll bind Lthe ayer 3 of the ISDN PRI interface of the MGCP voice gateway to the CUCM for PRI Q.931 signaling backhaul support

interface Serial0/0/0:23
isdn bind-l3 ccm-manager




Comments

  1. Joy kumar saha SEO expert 12 October 2012 at 08:31

    Hey, Sir,

    Right able guidelines about web page on debuggingvoip.blogspot.com.It is a highly effective web page for the area of person.This web page maintaining play a role significantly.Truly I like this web page. I am expecting to choose up more running a blog perform, too! I like to evaluation my The stress is on companies of all styles to improve earnings, cut expenses, and help preserve the earth. And movie Voip Business meetings allows you to do just that! But with so many services to select from; how do you determine which the best fit for your business is? Not to mention your budget.

    Many many thanks for the very good Article write-up.



    ReplyDelete

Post a Comment

Popular posts from this blog

Status: Local Agent is not responding. This may be due to Master or Local Agent being down.

-
If you have read my previous post , you would understand why LA and MA services are important for such a scenario and no component has backed-up, rather you get the above error message. Symptoms -   All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. Also, when you access the DRF admin pages, the above error message is received. Affected CM releases 6.1.5 and later. Resolution In order to resolve it, first, verify if the Certificate Serial Number in the keystore of Publisher is present in the Truststore of all Subscribers. Complete these steps: Log on to CUCM OS Administration page of Publisher server of the cluster setup. Choose Security > Certificate Management . The Certificate List window displays. You can use the Find controls in order to filter the certificate. Click on the ipsec.pem file and check the serial number of the certificate. Log on to CUCM OS Administr
Read more

Understanding code yellow

-
Understanding sample code yellow alert- Oct 3 01:00:10, cms01, Error, Cisco CallManager, ccm: 147896: Oct 03 05:00:10.616 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowEntry: CodeYellowEntry Expected Average Delay:362 Entry Latency:20 Exit Latency:8 Sample Size:10 Total Code Yellow Entry:14 High Priority Queue Depth:2 Normal Priority Queue Depth:12 Low Priority Queue Depth:70 Cluster ID:StandAloneCluster Node ID:cms01, 3652 The above alert is about code yellow entry, it shows the time when server enters code yellow state. There are no specifications to note at this alert, CM enters code yellow when it achieves the mentioned conditions for code yellow state as mentioned in service parameters. Oct 3 01:00:12, cms01, Error, Cisco CallManager, ccm: 147897: Oct 03 05:00:12.268 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowExit: CodeYellowExit Expected Average Delay:0 Entry Latency:20 Exit Latency:8 Sample Size:10 Time Spent in Code Yellow:2 Number of Calls Rejected Due to C
Read more