How To Configure MGCP With Digital Pri and Cisco Callmanager
How To Configure MGCP With Digital Pri and Cisco Callmanager
How To Configure MGCP With Digital Pri and Cisco Callmanager
CallManager
Document ID: 23966
Introduction
Prerequisites
Requirements
Components Used
Related Products
Conventions
Configure the Gateway
Network Diagram
Configurations
Verify the Gateway Configuration
Troubleshoot the Gateway Configuration
Configure Cisco CallManager
Configuration Steps
Verify the Cisco CallManager Registration Status
Troubleshoot Cisco CallManager
Verify
Debug Output for Outbound Calls from IP Phone to PSTN
Debug MGCP Packet from Gateway for the Same Call
Debug Output for Inbound Calls from PSTN
Debug MGCP Packet from Gateway
Troubleshoot
Cause i = 0x82B2 − Requested facility
Cause i = 0x80E5 − Message not compatible with call state
Related Information
Introduction
This document explains how to configure Media Gateway Control Protocol (MGCP) with PRI when you use
Cisco IOS® Software Release 12.4(5b). The document also demonstrates the registration process, successful
inbound and outbound calls from PSTN, as well as the debugs and Cisco CallManager trace for the calls.
Symptoms
You can potentially encounter these symptoms when you configure Cisco CallManager with Cisco IOS
MGCP gateways with PRI ports:
• MGCP gateway does not register with Cisco CallManager. Refer to MGCP Gateway Registration
Failure with Cisco CallManager for more information.
• MGCP PRI port does not register with Cisco CallManager. Ensure that the PRI port is connected to
the telco line with layer 1 and 2 in the active status.
Prerequisites
Requirements
Ensure that you meet these requirements before you attempt this configuration:
• Run Cisco IOS Software Release 12.4(5b) with Cisco IOS gateway with digital PRI and Cisco
CallManager 4.1.
Note: Cisco CallManager does not support the configuration or use of a fractional PRI when you use it with
MGCP. If fractional PRI is necessary you can use H.323 instead of MGCP.
Components Used
The information in this document is based on these software and hardware versions:
The information in this document was created from the devices in a specific lab environment. All of the
devices used in this document started with a cleared (default) configuration. If your network is live, make sure
that you understand the potential impact of any command.
Related Products
This setup can also use any of these Cisco IOS gateways: VG200, 2600, 3600, that run the same Cisco IOS
software release. Cisco CallManager version 3.1 or later supports this configuration.
Conventions
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Note: Use the Command Lookup Tool ( registered customers only) to find more information on the commands
used in this document.
Network Diagram
This section uses this network setup:
Configurations
This document uses this configuration:
• AV−2620−4
AV−2620−4
AV−2620−4#show run
version 12.4
no parser cache
no service single−slot−reload−enable
service timestamps debug datetime msec
service timestamps log datetime msec
service password−encryption
!
hostname AV−2620−4
!
logging rate−limit console 10 except errors
enable secret 5 xxxx
enable password 7xxxx
!
voice−card 1
!
ip subnet−zero
!
!
no ip domain−lookup
!
no ip dhcp−client network−discovery
mgcp
mgcp call−agent 172.16.240.124 2427 service−type mgcp version 0.1
ccm−manager mgcp
!
ccm−manager music−on−hold
ccm−manager config server 172.16.240.124
ccm−manager config
!
!
controller T1 1/0
framing esf
clock source internal
linecode b8zs
cablelength short 133
pri−group timeslots 1−24 service mgcp
!!
interface FastEthernet0/0
ip address 172.16.15.129 255.255.255.0
ip helper−address 172.16.15.10
no ip mroute−cache
duplex auto
speed auto
!
interface Serial0/2/0:23
no ip address
no logging event link−status
isdn switch−type primary−ni
isdn incoming−voice voice
isdn T310 10000
isdn bind−l3 ccm−manager
no cdp enable
!no ip http server
!
snmp−server community public RO
snmp−server community private RW
snmp−server packetsize 4096
!
voice−port 0/2/0:23
!
dial−peer cor custom
!
!
dial−peer voice 9991023 pots
application mgcpapp
port 0/2/0:23
!
!
line con 0
exec−timeout 0 0
line aux 0
line vty 0 4
exec−timeout 0 0
password 7 xxxx
login
line vty 5 15
login
!
!
end
Note: With MGCP, you cannot block incoming calls on the basis of the calling party Directory Number (DN).
However, you can do so if you use H323.
Note: After you make any configuration changes on the MGCP gateway, issue these two global commands in
sequence on the MGCP gateway for the changes to take effect.
no mgcp
mgcp
These mgcp commands in a similar sequence are used to reset MGCP in IOS gateways. If any of the MGCP
interfaces fail, reset the interface by issuing a shutdown and the a no shutdown command in the respective
interface configuration mode. Then reset MGCP in a similar manner on the gateway in order to solve the
issue.
The Output Interpreter Tool ( registered customers only) (OIT) supports certain show commands. Use the OIT to
view an analysis of show command output.
AV−2620−4#show ccm−manager
MGCP Domain Name: AV−2620−4
Priority Status Host
============================================================
Primary Registered 172.16.240.124
First Backup None Second Backup None
Current active Call Manager: 172.16.240.124
Backhaul/Redundant link port: 2428
Failover Interval: 30 seconds
Keepalive Interval: 15 seconds
Last keepalive sent: 00:45:31 (elapsed time: 00:00:04)
Last MGCP traffic time: 00:45:31 (elapsed time: 00:00:04)
Last failover time: None
Switchback mode: Graceful
MGCP Fallback mode: Not Selected
Last MGCP Fallback start time: 00:00:00
Last MGCP Fallback end time: 00:00:00
PRI Backhaul Link info:
Link Protocol: TCP
Remote Port Number: 2428
Remote IP Address: 172.16.240.124
Current Link State: OPEN
Statistics:
Packets recvd: 32
Recv failures: 0
Packets xmitted: 32
Xmit failures: 0
PRI Ports being backhauled:
Slot 1, port 0
Configuration Auto−Download Information
=======================================
No configurations downloaded
Current state: Automatic Configuration Download feature is disabled
Configuration Error History:
FAX mode: cisco
Interface T1 0/2/0
Note: Refer to Important Information on Debug Commands before you use debug commands.
• debug mgcp packet enables you to verify whether the gateway communicates with Cisco
CallManager.
Configuration Steps
Complete these steps to configure the gateway in Cisco CallManager:
4. Enter the Hostname of the router as the Domain Name, choose the Cisco CallManager Group,
choose the Installed Voice Interface Cards on the appropriate slot and click Insert.
5. Choose the T1 card for the subunit under the Installed Voice Interface Cards slots and click
Update. A dialog box appears that prompts you to reset the gateway. Click Ok and then click Reset.
Now, click Close in order to close the window.
6. Click on the Endpoint Identifier(in this example, 0/2/0).
7. Select the option T1−PRI.
1. Check the Status Monitor to see if the MGCP PRI gateway is registered. Go to Start > Programs >
Administrative tools > Performance.
2. Ensure that RIS Data Collector service is up. Go to Start > Programs > Administrative Tools >
Services.
Troubleshoot Cisco CallManager
Cisco CallManager Trace
Verify whether the gateway registers with Cisco CallManager. This trace is captured when the gateway
registers with Cisco CallManager. The important messages are highlighted in bold.
F: X, A, I |<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
<CT::1,100,58,8.1><IP::><DEV::>
01/24/2009 18:45:36.573 Cisco CallManager|MGCPHandler send MSG SUCCESSFULLY
to: 172.16.15.129 AUEP 303 S0/SU2/ds1−0/2@AV−2620−4 MGCP 0.1 F: X, A, I
|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124><CT::1,100,58,8.1>
<IP::><DEV::>
01/24/2009 18:45:36.573 Cisco CallManager|MGCPHandler send MSG SUCCESSFULLY
to: 172.16.15.129 AUEP 304 S0/SU2/ds1−0/3@AV−2620−4 MGCP 0.1 F: X, A, I
!−−− You see the same messages for each channel up to channel 23.
|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124><CT::1,100,58,8.1><IP::>
<DEV::>
01/24/2009 18:45:36.583 Cisco CallManager|MGCPHandler send MSG SUCCESSFULLY
to: 172.16.15.129 AUEP 324 S0/SU2/ds1−0/23@AV−2620−4 MGCP 0.1 F: X, A, I
|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124><CT::1,100,58,8.1><IP::>
<DEV::>
01/24/2009 18:45:36.633 Cisco CallManager|MGCPHandler received MSG from:
172.16.15.129
Cisco CallManager receives these messages from Gateway for each B channel. These are the port capabilities
of the gateway.
• ACK( I: ConnID
• X: ReqID
• L: LocalConnOpt( p: PktPeriod,
• a: CmprAlg,
• b: Bandwidth,
• e: EchoCancel,
• gc:GainControl,
• s: SilenceSupp,
• t: TypeOfService,
• r: ResourceResv,
• nt:TypeOfNetwork,
• v: EventPackages)
• M: sendonly, recvonly, sendrecv, inactive, loopback, conttest, netwloop netwtest)
200 302
L: p:10−20, a:PCMU;PCMA, b:64, e:on, gc:−6−14, s:on, t:00−FF, r:g, NT:IN;LOCAL,
v:L;G;D;T;H
L: p:10−220, a:G.729a;G.729b;G.729, b:8, e:on, gc:−6−14, s:on, t:00−FF, r:g,
NT:IN;LOCAL, v:L;G;D;T;H
L: p:10−110, a:G.726−16, b:16, e:on, gc:−6−14, s:on, t:00−FF, r:g, NT:IN;LOCAL,
v:L;G;D;T;H
L: p:10−70, a:G.726−24, b:24, e:on, gc:−6−14, s:on, t:00−FF, r:g, NT:IN;LOCAL,
v:L;G;D;T;H
L: p:10−50, a:G.726−32, b:32, e:on, gc:−6−14, s:on, t:00−FF, r:g, NT:IN;LOCAL,
v:L;G;D;T;H
M: sendonly, recvonly, sendrecv, inactive, loopback, conttest, netwloop, netwtest
|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124><CT::1,100,50,1.40686>
<IP::172.16.15.129><DEV::>
01/24/2009 18:45:36.633 Cisco CallManager|MGCPHandler received RESP header w/
transId= 302|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
<CT::1,100,50,1.40686><IP::172.16.15.129><DEV::>
01/24/2009 18:45:36.633 Cisco CallManager|<CLID::MCS−7822−SERVER−Cluster>
<NID::172.16.240.124><CT::1,100,50,1.40686><MN::MGCPEndPoint>
<MV::S0/SU2/ds1−0/1@AV−2620−4><DEV::S0/SU2/ds1−0@AV−2620−4>
01/24/2009 18:45:36.633 Cisco CallManager|MGCPHandler received RESP header w/
transId= 302 FOUND a match for AUED|<CLID::MCS−7822−SERVER−Cluster>
<NID::172.16.240.124><CT::1,100,50,1.40686><IP::172.16.15.129>
<DEV::S0/SU2/ds1−0@AV−2620−4>
01/24/2009 18:45:36.663 Cisco CallManager|MGCPHandler received MSG from:
172.16.15.129
200 303
L: p:10−20, a:PCMU;PCMA, b:64, e:on, gc:−6−14, s:on, t:00−FF, r:g, NT:IN;LOCAL,
v:L;G;D;T;H
L: p:10−220, a:G.729a;G.729b;G.729, b:8, e:on, gc:−6−14, s:on, t:00−FF, r:g,
NT:IN;LOCAL, v:L;G;D;T;H
L: p:10−110, a:G.726−16, b:16, e:on, gc:−6−14, s:on, t:00−FF, r:g, NT:IN;LOCAL,
v:L;G;D;T;H
L: p:10−70, a:G.726−24, b:24, e:on, gc:−6−14, s:on, t:00−FF, r:g, NT:IN;LOCAL,
v:L;G;D;T;H
L: p:10−50, a:G.726−32, b:32, e:on, gc:−6−14, s:on, t:00−FF, r:g, NT:IN;LOCAL,
v:L;G;D;T;H
M: sendonly, recvonly, sendrecv, inactive, loopback, conttest, netwloop, netwtest
|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124><CT::1,100,50,1.40687>
<IP::172.16.15.129><DEV::>
01/24/2009 18:45:36.663 Cisco CallManager|MGCPHandler received RESP header w/
transId= 303|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
<CT::1,100,50,1.40687><IP::172.16.15.129><DEV::>
01/24/2009 18:45:36.663 Cisco CallManager|<CLID::MCS−7822−SERVER−Cluster>
<NID::172.16.240.124><CT::1,100,50,1.40687><MN::MGCPEndPoint>
<MV::S0/SU2/ds1−0/2@AV−2620−4><DEV::S0/SU2/ds1−0@AV−2620−4>
01/24/2009 18:45:36.663 Cisco CallManager|MGCPHandler received RESP header w/
transId= 303 FOUND a match for AUED|<CLID::MCS−7822−SERVER−Cluster>
<NID::172.16.240.124><CT::1,100,50,1.40687><IP::172.16.15.129>
<DEV::S0/SU2/ds1−0@AV−2620−4>
01/24/2009 18:45:36.703 Cisco CallManager|MGCPHandler received MSG from:
172.16.15.129
!−−− You see the same message repeated for each channel.
Verify
Use this section to confirm that your configuration works properly.
To verify the configuration, make outbound calls to PSTN, and inbound calls from PSTN to Cisco IP phones.
Here is the debug output from inbound and outbound calls:
A Cisco IP Phone with the Directory number 2000 calls a PSTN phone with number 2012. This test uses a
4−digit number for the PSTN phone. However, keep in mind that outside of lab, PSTN phones have a fully
qualified North American Numbering Plan (NANP). The access code for the outside line is 8.
v=0
a=rtpmap:96 G.729a/8000/1
a=rtpmap:97 G.726−16/8000/1
a=rtpmap:98 G.726−24/8000/1
a=rtpmap:99 G.729b/8000/1
|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124><CT::1,100,50,1.40789>
<IP::172.16.15.129><DEV::>
01/24/2009 19:05:43.268 Cisco CallManager|MGCPHandler received RESP header
w/ transId= 325|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124><CT::1,
100,50,1.40789><IP::172.16.15.129><DEV::>
01/24/2009 19:05:43.278 Cisco CallManager|<CLID::MCS−7822−SERVER−
Cluster><NID::172.16.240.124><CT::1,100,50,1.40789><MN::MGCPEndPoint>
<MV::S0/SU2/ds1−0/23@AV−2620−4><DEV::S0/SU2/ds1−0@AV−2620−4>
01/24/2009 19:05:43.278 Cisco CallManager|MGCPHandler received RESP header
w/ transId= 325 FOUND a match for CRCX|<CLID::MCS−7822−SERVER−Cluster>
<NID::172.16.240.124><CT::1,100,50,1.40789><IP::172.16.15.129>
<DEV::S0/SU2/ds1−0@AV−2620−4>
01/24/2009 19:05:43.278 Cisco CallManager|MGCPHandler recv CRCX Ack with
RTP PortNum: 16526|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
<CT::1,100,50,1.40789><IP::172.16.15.129><DEV::S0/SU2/ds1−0@AV−2620−4>
01/24/2009 19:05:43.278 Cisco CallManager||<CLID::MCS−7822−SERVER−Cluster>
<NID::172.16.240.124>
01/24/2009 19:05:43.278 Cisco CallManager|Out Message −− PriSetupMsg −−
Protocol=PriNi2Protocol|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
01/24/2009 19:05:43.278 Cisco CallManager|Ie − Ni2BearerCapabilityIe IEData=
04 03 80 90 A2 |<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
01/24/2009 19:05:43.278 Cisco CallManager|Ie − Q931ChannelIdIe IEData= 18 03 A9
83 97 |<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
v=0
AV−2620−4
AV−2620−4# *Mar 1 00:35:23.919: MGCP Packet received from
172.16.240.124 −−−>
CRCX 337 S0/SU2/ds1−0/23@AV−2620−4 MGCP 0.1
C: D00000000100009d0000000000000002
M: inactive
AV−2620−4#
*Mar 1 00:35:57.955: send_mgcp_msg, MGCP Packet
sent to 172.16.240.124 −−−>
a=rtpmap:96 G.729a/8000/1
a=rtpmap:97 G.726−16/8000/1
a=rtpmap:98 G.726−24/8000/1
a=rtpmap:99 G.729b/8000/1
|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
<CT::1,100,50,1.40808><IP::172.16.15.129><DEV::>
01/24/2009 19:09:19.764 Cisco CallManager|MGCPHandler received RESP
header w/ transId= 330|<CLID::MCS−7822−SERVER−Cluster>
<NID::172.16.240.124><CT::1,100,50,1.40808><IP::172.16.15.129><DEV::>
01/24/2009 19:09:19.764 Cisco CallManager|<CLID::MCS−7822−SERVER−
Cluster><NID::172.16.240.124><CT::1,100,50,1.40808><MN::MGCPEndPoint>
<MV::S0/SU2/ds1−0/23@AV−2620−4><DEV::S0/SU2/ds1−0@AV−2620−4>
01/24/2009 19:09:19.764 Cisco CallManager|MGCPHandler received RESP
header w/ transId= 330 FOUND a match for CRCX|<CLID::MCS−7822−SERVER−
Cluster><NID::172.16.240.124><CT::1,100,50,1.40808>
<IP::172.16.15.129><DEV::S0/SU2/ds1−0@AV−2620−4>
01/24/2009 19:09:19.764 Cisco CallManager|MGCPHandler recv CRCX Ack
with RTP PortNum: 16476|<CLID::MCS−7822−SERVER−Cluster>
<NID::172.16.240.124><CT::1,100,50,1.40808><IP::172.16.15.129>
<DEV::S0/SU2/ds1−0@AV−2620−4>
01/24/2009 19:09:19.774 Cisco CallManager|
|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
01/24/2009 19:09:19.774 Cisco CallManager|Out Message −−
PriCallProceedingMsg −− Protocol= PriNi2Protocol
|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
01/24/2009 19:09:19.774 Cisco CallManager|Ie − Q931ChannelIdIe IEData=
18 03 A9 83 97 |<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
v=0
−− Protocol
= PriNi2Protocol
|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
01/24/2009 19:09:30.801 Cisco CallManager|MMan_Id= 0.
(iep= 0 dsl= 100 sapi= 0 ces= 0 IpAddr=810f10ac
IpPort=2427)|<CLID::MCS−7822−SERVER−Cluster>
<NID::172.16.240.124>
01/24/2009 19:09:30.801 Cisco CallManager|IsdnMsgData2=
08 02 80 08 5A |<CLID::MCS−7822−SERVER−Cluster>
<NID::172.16.240.124>
01/24/2009 19:09:30.801 Cisco CallManager|MGCPBhHandler −
Sending BhHdr: 0004 0000 0010 0100 0001 0005
|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
<CT::1,100,48,1.302><IP::172.16.15.129><DEV::>
01/24/2009 19:09:30.801 Cisco CallManager|Delete entries
from TransTable, now this table has 0 entries|
<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
<CT::1,100,48,1.302><IP::172.16.15.129><DEV::>
01/24/2009 19:09:30.801 Cisco CallManager|Delete entries
from CiCcp table, now this table has 0 entries|
<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
<CT::1,100,48,1.302><IP::172.16.15.129><DEV::>
01/24/2009 19:09:30.801 Cisco CallManager|MGCPHandler
send msg SUCCESSFULLY to: 172.16.15.129
DLCX 336 S0/SU2/ds1−0/23@AV−2620−4 MGCP 0.1
C: D00000000100009a0000000080000008
I: 3
X: 17
S:
|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
<CT::1,100,48,1.302><IP::172.16.15.129><DEV::>
01/24/2009 19:09:30.801 Cisco CallManager|Locations:
release: cdccPID=(1.13.78) no entry.|<CLID::MCS−7822−
SERVER−Cluster><NID::172.16.240.124>
01/24/2009 19:09:30.851 Cisco CallManager|MGCPHandler
received msg from: 172.16.15.129
250 336
P: PS=289, OS=46240, PR=288, OR=46080, PL=0, JI=512,
LA=0 |<CLID::MCS−7822−SERVER−Cluster>
<NID::172.16.240.124><CT::1,100,50,1.40814>
<IP::172.16.15.129><DEV::>
01/24/2009 19:09:30.851 Cisco CallManager|MGCPHandler
received RESP header w/ transId= 336|<CLID::MCS−7822−
SERVER−Cluster><NID::172.16.240.124>
<CT::1,100,50,1.40814><IP::172.16.15.129><DEV::>
01/24/2009 19:09:30.851 Cisco CallManager|<CLID::MCS−
7822−SERVER−Cluster><NID::172.16.240.124>
<CT::1,100,50,1.40814><MN::MGCPEndPoint>
<MV::S0/SU2/ds1−0/23@AV−2620−4><DEV::S0/SU2/ds1−0@AV−2620−4>
01/24/2009 19:09:30.851 Cisco CallManager|MGCPHandler
received RESP header w/ transId= 336 FOUND a match
for DLCX|<CLID::MCS−7822−SERVER−Cluster>
<NID::172.16.240.124><CT::1,100,50,1.40814>
<IP::172.16.15.129><DEV::S0/SU2/ds1−0@AV−2620−4>
01/24/2009 19:09:36.279 Cisco CallManager|MGCPHandler
received msg from: 172.16.15.129
NTFY 100 *@AV−2620−4 MGCP 0.1
X: 0
O:
|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
<CT::1,100,50,1.40815><IP::172.16.15.129><DEV::>
01/24/2009 19:09:36.279 Cisco CallManager
|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
<CT::1,100,50,1.40815><MN::MGCPEndPoint>
<MV::*@AV−2620−4><DEV::>
01/24/2009 19:09:36.289 Cisco CallManager|MGCPHandler
send msg SUCCESSFULLY to: 172.16.15.129
200 100
|<CLID::MCS−7822−SERVER−Cluster><NID::172.16.240.124>
<CT::1,100,50,1.40815><IP::172.16.15.129><DEV::>
Debug MGCP Packet from Gateway
AV−2620−4
AV−2620−4#debug mgcp packet
Media Gateway Control Protocol packets debugging is on
v=0
o=− 5 0 IN EPN S0/SU2/ds1−0/23@AV−2620−4
s=Cisco SDP 0
t=0 0
c=IN IP4 172.16.240.126
m=audio 29380 RTP/AVP 96
a=rtpmap:96 PCMU
AV−2620−4#und all
All possible debugging has been turned off
Troubleshoot
Cause i = 0x82B2 − Requested facility
In an ISDN PRI circuit configured as an MGCP gateway, outbound calls fail. The debug isdn q931 command
shows the disconnect cause code as Cause i = 0x82B2 − Requested facility not
subscribed.
When you view the debug isdn q931 Disconnect Cause Codes, it appears to be a problem that occurs at the
local Telco switch due to a requested facility that is not subscribed. In order to resolve this issue, uncheck
Sending calling name in Facility IE and Display IE on the Cisco CallManager Gateway Configuration page.
Refer to CallManager and Calling Party Name for more information.
Issue the no mgcp and then the mgcp command in global configuration mode on the MGCP gateway router
in order to reset the MGCP gateway from the Cisco CallManager.
By Default, when telco sends the full number (en−bloc mode), Cisco CallManager sends back the
SETUP_ACK waiting for more numbers (overlap mode) as the Overlap Receiving Flag is set to
True by default. In this case, the Cisco CallManager receives an ISDN STATUS message as a response to
the SETUP_ACK sent to the PSTN switch. The ISDN STATUS message is not recognized by Cisco
CallManager at this state of the call and hence the issue.
In order to resolve the issue, you need to set the Overlap Receiving Flag parameter in Cisco
CallManager to be FALSE. Then, Cisco CallManager does not send the SETUP_ACK and PSTN does not
reply back with the ISDN STATUS message.
Related Information
• Interworking of Cisco MGCP Voice Gateways and Cisco CallManager Version 3.1
• Release Notes for Cisco IOS Software Release 12.4(6)XT
• Voice Technology Support
• Voice and Unified Communications Product Support
• Recommended Reading: Troubleshooting Cisco IP Telephony
• Technical Support & Documentation − Cisco Systems