Vg224 mgcp problem

Good morning, I've a callmanager 8.6.2.
All works well excepet a vg224 mcgp .
The vg is correctly registered via mgcp on callmanager, and I've configured one fxs port to connect to an analogic phone.
The problem is: if I start a call from analogic phone to ipphone the call wors well, but i I start a call from an ipphone to the analogic phone the call fails.
Eachone can help me?
in the attached file the vg 224 config
interface FastEthernet0/0
ip address 10.116.1.27 255.255.255.0
duplex auto
speed auto
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
ip default-gateway 10.116.1.1
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 10.116.1.1
no ip http server
control-plane
voice-port 2/0
voice-port 2/1
voice-port 2/2
voice-port 2/3
voice-port 2/4
voice-port 2/5
voice-port 2/6
voice-port 2/7
voice-port 2/8
voice-port 2/9
voice-port 2/10
voice-port 2/11
voice-port 2/12
voice-port 2/13
voice-port 2/14
voice-port 2/15
voice-port 2/16
voice-port 2/17
voice-port 2/18
voice-port 2/19
voice-port 2/20
voice-port 2/21
voice-port 2/22
voice-port 2/23
ccm-manager redundant-host 10.116.1.13
ccm-manager mgcp
no ccm-manager fax protocol cisco
ccm-manager music-on-hold
ccm-manager config server 10.116.1.22 10.116.1.13
ccm-manager config
mgcp
mgcp call-agent 10.116.1.22 2427 service-type mgcp version 0.1
mgcp rtp unreachable timeout 1000 action notify
mgcp package-capability rtp-package
mgcp package-capability sst-package
no mgcp package-capability res-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp rtp payload-type g726r16 static
mgcp bind control source-interface FastEthernet0/0
mgcp bind media source-interface FastEthernet0/0
mgcp profile default
dial-peer voice 99920 pots
service mgcpapp
port 2/0
dial-peer voice 99921 pots
service mgcpapp
port 2/1
dial-peer voice 99922 pots
service mgcpapp
port 2/2
dial-peer voice 99923 pots
service mgcpapp
port 2/3
dial-peer voice 99924 pots
service mgcpapp
port 2/4
dial-peer voice 99925 pots
service mgcpapp
port 2/5
dial-peer voice 99926 pots
service mgcpapp
port 2/6
dial-peer voice 99927 pots
service mgcpapp
port 2/7
dial-peer voice 99928 pots
service mgcpapp
port 2/8
dial-peer voice 99929 pots
service mgcpapp
port 2/9
dial-peer voice 999210 pots
service mgcpapp
port 2/10
dial-peer voice 999211 pots
service mgcpapp
port 2/11
dial-peer voice 999212 pots
service mgcpapp
port 2/12
dial-peer voice 999213 pots
service mgcpapp
port 2/13
dial-peer voice 999214 pots
service mgcpapp
port 2/14
dial-peer voice 999215 pots
service mgcpapp
port 2/15
dial-peer voice 999216 pots
service mgcpapp
port 2/16
dial-peer voice 999217 pots
service mgcpapp
port 2/17
dial-peer voice 999218 pots
service mgcpapp
port 2/18
dial-peer voice 999219 pots
service mgcpapp
port 2/19
dial-peer voice 999220 pots
service mgcpapp
port 2/20
dial-peer voice 999221 pots
service mgcpapp
port 2/21
dial-peer voice 999222 pots
service mgcpapp
port 2/22
dial-peer voice 999223 pots
service mgcpapp
port 2/23

Duplicate
https://supportforums.cisco.com/discussion/12245471/problem-vg224-mgcp

Similar Messages

VG224 MGCP can´t register to CUCM 8.6.2-20000-2

I have tried to register cisco VG224 to CUCM 8.6 like MGCP gateway but it fail to register, any idea why this issue?

Yes I have configure the FQDN of the gateway in CUCM.
Debug logs Are:
VGALP01(config)#
*Mar 1 01:59:49.927: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_sys_msg(208):[lvl=0]MGCP sys msg: (EXTERNAL_EVENT)
*Mar 1 01:59:49.927: //-1/xxxxxxxxxxxx/MGCP/xlate_mgcp_sys_ev(69):[lvl=0]xlate sys msg: (EXTERNAL_EVENT, 63FE0988)
*Mar 1 01:59:49.927: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_sys_msg(217):[lvl=0]sys msg values: (INVALID MGCP EVENT, 0, , 3647, CALL_IDLE)
*Mar 1 01:59:49.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_handle_cmapp_event(442):[lvl=0]process
*Mar 1 01:59:49.927: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_by_ifn(1330):[lvl=0]Entered
*Mar 1 01:59:49.927: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_tree_link_by_ifn(1149):[lvl=0]Entered
*Mar 1 01:59:49.927: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_compute_key(198):[lvl=0]type -1 slot FFFFFFFF subunit 0000
*Mar 1 01:59:49.927: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_tree_link_by_ifn(1161):[lvl=0]computed key 0xF0000000
*Mar 1 01:59:49.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_cmapp_send_rsip(407):[lvl=1]Send-RSIP: Sending gw host is VGALP01.volcan.com, endpt is *
*Mar 1 01:59:49.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_root_get_profile(1905):[lvl=0]Entered
*Mar 1 01:59:49.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_send_rsip_msg(737):[lvl=0]Entered
*Mar 1 01:59:49.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_build_packet(864):[lvl=0]Entered
*Mar 1 01:59:49.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_estimate_msg_buf_length(496):[lvl=1]328 bytes needed for header
*Mar 1 01:59:49.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_estimate_msg_buf_length(785):[lvl=1]344 bytes needed after checking parameter lines
*Mar 1 01:59:49.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_estimate_msg_buf_length(808):[lvl=1]344 bytes needed after cheking SDP lines
*Mar 1 01:59:49.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_build_parameter_lines(9499):[lvl=0]Entered
*Mar 1 01:59:49.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_val_mandatory_parms(13005):[lvl=0]Entered
*Mar 1 01:59:49.931: //-1/xxxxxxxxxxxx/MGCP/mgcp_build_restart_method(12063):[lvl=0]Entered
*Mar 1 01:59:49.931: //-1/xxxxxxxxxxxx/MGCP/mgcp_build_restart_method(12085):[lvl=0]SUCCESS: Building Restart Method (RM:) OK
*Mar 1 01:59:49.931: //-1/xxxxxxxxxxxx/MGCP/mgcp_build_parameter_lines(9802):[lvl=0]SUCCESS: Building MGCP Parameter lines is OK
*Mar 1 01:59:49.931: //-1/xxxxxxxxxxxx/MGCP/mgcp_build_packet(1018):[lvl=1]SUCCESS: MGCP message building OK - END of building
*Mar 1 01:59:49.931: //-1/xxxxxxxxxxxx/MGCP/MGCP_NEDB_get_next_addr(1211):[lvl=1]
NOTIFY ENTITY = 10.24.130.11
next->10.24.130.11
*Mar 1 01:59:49.931: MGCP Packet sent to 10.24.130.11:2427--->
RSIP 957884407 *@VGALP01.volcan.com MGCP 0.1
RM: restart
<---
*Mar 1 01:59:49.931: //-1/xxxxxxxxxxxx/MGCP/mgcp_endpt_record_rsip(615):[lvl=0]Entered
*Mar 1 01:59:49.931: //-1/xxxxxxxxxxxx/MGCP/mgcp_send_rsip_msg(882):[lvl=1]Manually recroding RSIP method
*Mar 1 01:59:49.931: //-1/xxxxxxxxxxxx/MGCP/mgcp_endpt_record_rsip(615):[lvl=0]Entered
*Mar 1 01:59:49.931: //-1/xxxxxxxxxxxx/MGCP/mgcp_enq_retx_rsip_msg(396):[lvl=0]Entered
*Mar 1 01:59:49.931: //-1/xxxxxxxxxxxx/MGCP/mgcp_add_trans_id_rec(1137):[lvl=1]Add trans id (957884407, 646D36B8) record
*Mar 1 01:59:49.931: //-1/xxxxxxxxxxxx/MGCP/mgcp_stw_timer_start(393):[lvl=0]timer type 0, duration 500
*Mar 1 01:59:49.931: //-1/xxxxxxxxxxxx/MGCP/mgcp_stw_timer_start(393):[lvl=0]timer type 15, duration 20000
*Mar 1 01:59:49.935: //-1/xxxxxxxxxxxx/MGCP/mgcp_count_active_mgc_msg_stat(239):[lvl=1]MGC stat - 10.24.130.11, total=47, succ=0, failed=46
*Mar 1 01:59:49.935: MGCP Packet received from 10.24.130.11:2427--->
500 957884407
<---
*Mar 1 01:59:49.935: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_mgcp_msg(3536):[lvl=0] :
*Mar 1 01:59:49.935: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(312):[lvl=0]call mgcp_parse_header
*Mar 1 01:59:49.935: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(316):[lvl=0]out mgcp_parse_header
*Mar 1 01:59:49.935: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(326):[lvl=1]SUCCESS: - MGCP Header parsing was OK
*Mar 1 01:59:49.935: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(344):[lvl=2]SUCCESS: - END of Parsing
*Mar 1 01:59:49.935: //-1/xxxxxxxxxxxx/MGCP/mgcp_msg_ack(6687):[lvl=0]Entered
*Mar 1 01:59:49.935: //-1/xxxxxxxxxxxx/MGCP/mgcp_count_active_mgc_msg_stat(239):[lvl=1]MGC stat - 10.24.130.11, total=47, succ=0, failed=47
*Mar 1 01:59:49.935: //-1/xxxxxxxxxxxx/MGCP/mgcp_mp_get_not_entity(830):[lvl=2]Invalid parameter (pkt 0x640982F8 pkt->mgcp_parm_lines 0x00000000)
*Mar 1 01:59:49.935: //-1/xxxxxxxxxxxx/MGCP/mgcp_check_for_redirection(6548):[lvl=1]endpt * was not redirected
*Mar 1 01:59:49.935: //-1/xxxxxxxxxxxx/MGCP/mgcp_msg_ack(6759):[lvl=1]Removing msg : RSIP 957884407 *@VGALP01.demo.com MGCP 0.1
RM: restart
*Mar 1 01:59:49.935: //-1/xxxxxxxxxxxx/MGCP/mgcp_msg_ack(6831):[lvl=0] Received ACK for RSIP, setting the restart method to NONE
*Mar 1 01:59:49.935: //-1/xxxxxxxxxxxx/MGCP/mgcp_check_and_send_pending_rsip(2116):[lvl=0]Entered
*Mar 1 01:59:49.935: //-1/xxxxxxxxxxxx/MGCP/mgcp_check_endpt_ext_and_free_rsip_info(3320):[lvl=0]Entered
*Mar 1 01:59:49.939: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_socket(3647):[lvl=0]Entered
*Mar 1 02:00:19.927: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_sys_msg(208):[lvl=0]MGCP sys msg: (EXTERNAL_EVENT)
*Mar 1 02:00:19.927: //-1/xxxxxxxxxxxx/MGCP/xlate_mgcp_sys_ev(69):[lvl=0]xlate sys msg: (EXTERNAL_EVENT, 63FE099C)
*Mar 1 02:00:19.927: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_sys_msg(217):[lvl=0]sys msg values: (INVALID MGCP EVENT, 0, , 3647, CALL_IDLE)
*Mar 1 02:00:19.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_handle_cmapp_event(442):[lvl=0]process
*Mar 1 02:00:19.927: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_by_ifn(1330):[lvl=0]Entered
*Mar 1 02:00:19.927: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_tree_link_by_ifn(1149):[lvl=0]Entered
*Mar 1 02:00:19.927: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_compute_key(198):[lvl=0]type -1 slot FFFFFFFF subunit 0000
*Mar 1 02:00:19.927: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_tree_link_by_ifn(1161):[lvl=0]computed key 0xF0000000
*Mar 1 02:00:19.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_cmapp_send_rsip(407):[lvl=1]Send-RSIP: Sending gw host is VGALP01.volcan.com, endpt is *
*Mar 1 02:00:19.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_root_get_profile(1905):[lvl=0]Entered
*Mar 1 02:00:19.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_send_rsip_msg(737):[lvl=0]Entered
*Mar 1 02:00:19.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_build_packet(864):[lvl=0]Entered
*Mar 1 02:00:19.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_estimate_msg_buf_length(496):[lvl=1]328 bytes needed for header
*Mar 1 02:00:19.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_estimate_msg_buf_length(785):[lvl=1]344 bytes needed after checking parameter lines
*Mar 1 02:00:19.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_estimate_msg_buf_length(808):[lvl=1]344 bytes needed after cheking SDP lines
*Mar 1 02:00:19.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_build_parameter_lines(9499):[lvl=0]Entered
*Mar 1 02:00:19.927: //-1/xxxxxxxxxxxx/MGCP/mgcp_val_mandatory_parms(13005):[lvl=0]Entered
*Mar 1 02:00:19.931: //-1/xxxxxxxxxxxx/MGCP/mgcp_build_restart_method(12063):[lvl=0]Entered
*Mar 1 02:00:19.931: //-1/xxxxxxxxxxxx/MGCP/mgcp_build_restart_method(12085):[lvl=0]SUCCESS: Building Restart Method (RM:) OK
*Mar 1 02:00:19.931: //-1/xxxxxxxxxxxx/MGCP/mgcp_build_parameter_lines(9802):[lvl=0]SUCCESS: Building MGCP Parameter lines is OK
*Mar 1 02:00:19.931: //-1/xxxxxxxxxxxx/MGCP/mgcp_build_packet(1018):[lvl=1]SUCCESS: MGCP message building OK - END of building
*Mar 1 02:00:19.931: //-1/xxxxxxxxxxxx/MGCP/MGCP_NEDB_get_next_addr(1211):[lvl=1]
NOTIFY ENTITY = 10.24.130.11
next->10.24.130.11
*Mar 1 02:00:19.931: MGCP Packet sent to 10.24.130.11:2427--->
RSIP 957884409 *@VGALP01.demo.com MGCP 0.1
RM: restart
<---

MGCP problem with Marconi Softswitch

I have a problem configuring MGCP on Ciscos Residential Gateway(IAD 2430)wit Marconi's Softswitch.I have two main issues with 2430. Ineed to know :
1- How can i set MGCP ver 0.1 with NCS 1.0 in IAD2430 as this is what is expected from Softswitch side.
2- How can i set MGCP endpoint Name on 2430 as per my own convention ?
I want to configure things on the residential gateway side and want to avoid any changes on my softswitch side.Can anyone shed some light on my problems ?
Thanx
Tanveer

This url shoul help you, It speaks about Cross-Platform Release Notes for Cisco IOS Release 12.2 T, Part 3: New Features and Important Notes:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/prod_release_note09186a0080087e11.html
Understanding prov-sync, prov-dply, and pom.dataSync and troubleshooting PGW standby OOS issues :
http://www.cisco.com/warp/public/788/products/prov_sync.html

MGCP problem with c881 voice

Hi,
I want to use a cisco "881 voice" with my CUCM v9.1.
This router, have a mgcp configuration and it's "ok", but i can't configure the BRI and the FXS with the CUCM.
It's possible to use the 881 with mgcp and configure fxs and bri?
Thanks.

Hi,
check these links
https://supportforums.cisco.com/discussion/11967296/cisco881v-c881-voice-bri-ports-remain-unregistered-cucm91
CUCM Add additional subunits to C887VA-V and C881VA-V SCCP gateway page
CSCul59124
-->
Description
Symptom:
Unable to add both the BRI and FXS ports on a C887VA-V SCCP voice gateway. When adding the FXS ports, the devicename is defined incorrectly, causing registration failure
Conditions:
CUCM 8.6.x, 9.x and 10.x
Cisco 887VA-V and 881VA-V voice gateway defined as SCCP controlled
Workaround:
Add the gateway under the 'Cisco 881/886/887' gateway entry. Add the FXS ports to 'Subunit 1'
Known Affected Releases:
(1)
9.1(2.12023.1
regds,
aman

Callmanager Inter cluster trunk - 6608 MGCP problem

Hi
We have two callmanager clusters linked together with an Inter cluster link and then there is a 6608 GW registered with one cluster here below is a logical ASCII drawing of the setup.
6608--Cluster1--Cluster2
Calls that are made to and from the Cluster1 that the GW is registered to work fine.
But calls that are made to and from the Cluster2 that is on the other end of the Inter cluster trunk ring once and are then disconnected.
I have gone over all codec settings for all the regions and they are all set to G711.
I also tried the same thing with a H323 GW like this.
H323GW--Cluster1--Cluster2
And then all calls work fine.
If anyone has any clue on this I would really appreciate some input.
Kind regards
Gudmundur Thor Johannsson

Sounds like MGCP is not supported on callmanager for inter-cluster gateway . Or it could be a bug. Any thoughts?????

VG224 standards based T38 fax support using MGCP

Hello,
All the documenation on fax support on the VG224 talks about using MGCP for standards based T38 support.
So does that mean that it uses protocol based T38 switchover?
In looking at the VG224 MGCP GW config on call manager it doesnt show much other than enabling T38.
On the VG224 MGCP config you can do the "no inhibit T38" but both call manager and the IOS config doesnt offer up much in what is being enabled and configured.
Also I am a little confused on using standards based passthrough fallback on the VG224 MGCP GW.
thanks

Hi Alex
thanks for the response
Sorry it took me a while to respond. I am having issues with the new site. I couldn't view this discussion from the new cisco site. I can only get to it by clicking on the email link.
I have looked at that link quite a few times over the last couple years.
So we have a SIP provider connection coming into CUBE which connects to CUCM via SIP. The VG224 is connected via MGCP.
The doc doesnt answer my question about is the VG224 using T38 protocol based switchover which is the standard. The VG224 config does not imply that and also the MGCP config in CUCM or on the VG224 doesnt imply that. Switchover using T38 NSE is supported in many Cisco products but is not considered standard from what I can see.
thanks

VG224 fax issue

Analog Phone->VG224(MGCP)--CCM4.1(3)--3725(MGCP)--PSTN
Analog works fine, can dial any PSTN number and from the PSTN can the analog phone. But when I connect a fax machine to the VG224, and try from IP Phone dial the fax number, there is no fax dial tone. When I try to send a fax, I can hear remote site site sending fax tone, and then about 10 seconds later the fax get comm error.
eptpos does not work either when connecting to VG224.
Here is the related configuration:
version 12.4
voice-port 2/0
echo-cancel coverage 32
cptone AU
timeouts call-disconnect 5
timeouts ringing 360
timeouts wait-release 5
impedance complex1
ccm-manager fallback-mgcp
ccm-manager redundant-host X.X.X.X
ccm-manager mgcp
ccm-manager config
mgcp
mgcp request timeout 2000
mgcp call-agent 10.103.0.132 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp rtp unreachable timeout 1000 action notify
mgcp modem passthrough voip mode nse
mgcp modem passthrough voip codec g711alaw
mgcp package-capability rtp-package
no mgcp package-capability res-package
mgcp package-capability sst-package
no mgcp timer receive-rtcp
mgcp sdp simple
no mgcp fax t38 ecm
mgcp fax t38 inhibit
mgcp profile default
dial-peer cor custom
dial-peer voice 200 pots
service mgcpapp
destination-pattern 8001
fax rate disable
direct-inward-dial
port 2/0
forward-digits all
Appreciate any advice.

This is a known issue with FoIP. You can get this to work by setting configuration at three locations, CallManager, VG224, and your 2800 gateway:
In CallManager VG224 "Product Specific Configuration Layout:
Modem Passthrough - Enable
Cisco Fax Relay - Disable
T38 Fax Relay - Enable
Enable
Disable
Disable
Disable
Enable
Enable
1000
0
Enable
On Voice Gateway Router:
voice service voip
fax protocol t38 version 0 ls-redundancy 2 hs-redundancy 0 fallback none
On VG224:
no ccm-manager fax protocol cisco
no mgcp
mgcp call-agent 10.68.192.10 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp rtp unreachable timeout 1000 action notify
mgcp modem passthrough voip mode nse
mgcp package-capability rtp-package
mgcp package-capability sst-package
mgcp default-package fxr-package
no mgcp package-capability res-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp fax rate 14400
mgcp rtp payload-type g726r16 static
mgcp
Hope that fixes it for you.

VG 224 and FAX

Hello There,
I configured a VG 224 with CallManager 4.2. Gateway itself and all ports are registered with CallManager, but when sending or receiving a Fax, it looks like it can not negotiage with Fax Machine and the output is not readable. Could you please advise what can I do to resolve this issue.
Thanks,
BT

Bahman,
Looking through your configs, you have the following commands in VG224.
mgcp modem passthrough voip mode nse
mgcp fax t38 inhibit
the first command enables fax passthrough for mgcp,
second command disable t38. So your vg224 is configured for Fax passthrough and not t38 fax relay.
You can leave the configs like this on the vg224 and match up the config on the cisco router that is your PSTN gateway. We need to enable the following commands on the router to match up with vg224 settings.
Cisco router - PSTn gateway :
no ccm-manager fax protocol cisco - (disable cisco fax relay)
mgcp modem passthrough voip mode nse - (enables mgcp modem passthrough)
mgcp fax t38 inhibit - (disables t38)
Cisco Vg224
add this command:
no ccm-manager fax protocol cisco - (disables cisco fax relay)
HTH
Sankar
PS: please remember to rate posts!

VG224 COMPACT FLASH PROBLEM

The problem is when the vg224 boots, the vg keeps on rommonitor and said: compact flash not present (already inserted in slot 0 with IOS), then on rommonitor I executed this command:
boot slot0:
And the vg comes up normally, I already point the the boot-system to: boot system slot0:vg224-i6s-mz.123-11.T8.bin
May be the compact-flash is corrupted?
Thanks

Perform a disaster recovery from rommon and get an IOS image from a local TFTP server into the internal flash.

Problems with MGCP

Im having some issues getting MGCP to register on our CCM (Version 8.6.2.21900-5) with an 800 series router (Specifically a C888SRST-W) if i bind the BRI interface to the CCM, Layer 2 will not activate. If I remove the binding command then the link activates as expected however I need this bound to the CUCM manager.
On the 888 router, the BRI port is known as BRI4 rather than the expected 0/0/0 format. On the CUCM the only options are 0/0/0 etc. Could this be the source of my problems? We have many 1800/2800/3800 series routers with BRI modules where this config works fine.
Thanks
Craig

If you add a pots dial peer with service mgcpapp and the port number it will work.

MGCP flow problem - ASA

The following is the setup and the problem we have:
* MGCP call agent -- ASA 5510 -- vpn tunnel -- linksys -- MGCP gateway
* VPN tunnel setup is in aggresive mode (initiated as needed from linksys).
* When MGCP call agent is up but the vpn tunnel is still down, MGCP traffic (udp/2427) tried to reach gateway and failed --> this is as expected.
* Next, linksys brings up the vpn tunnel
* Any other IP traffic can go through the tunnel, but not MGCP traffic from call agent to gateway.
* Checked from packet tracer: it passed phase 1 & 2 (checking the flow), it found existing flow and used that flow. Then it stuck there, looks like it didn't know where to go next (no ACL or route checking).
We noticed that the annoying following workaround will make the MGCP goes through.
* shutdown MGCP call agent
* disconnect vpn tunnel from linksys
* system reload the ASA5510
* after ASA5510 is up, linksys initiate the vpn tunnel
* after vpn is up, bring up MGCP call agent
* MGCP traffic goes through the tunnel
It seems like ASA MGCP flow table is not updated if there is status change in VPN tunnel. Any idea how to fix this ?

Thanks for the reply.
However that wasn't mgcp ispection issue, it was more on dynamic vpn configuration issue. The setup is dynamic vpn initiated from remote sites (aggresive mode).
Worked with Cisco TAC and got the workaround. Following is the summary, hope it's useful.
1. Previous dynamic vpn config was:
crypto dynamic-map outside_dyn_map 20 set transform-set VPNHigh
When the tunnel was down and the call agent (central) was sending traffic to the call gateway (remote), the ASA created a connection to send the traffic out in the clear as it didn't match any crypto access-list due to the tunnel being dynamic.
2. The call agent (cetral) continued to attempt to send traffic to the call gateway (remote), which kept the conn up, even when the tunnel came up.
3. When the tunnel came up, the ASA continued to use the existing conn and sent the traffic out in the clear.
4. This is very similar to bug: CSCse36327 - GRE Packets are no longer encrypted and are sent out in the clear
http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCse36327
Even though that mentions GRE, it's the same issue.
5. After the tunnel was up and "clear local-host " was issued, the conn was torn down and a new conn was built to go over the tunnel.
6. To avoid this situation, a crypto acl for this dynamic tunnel was created:
access-list dyn-mgcp line 1 extended permit ip
crypto dynamic-map outside_dyn_map 20 match address dyn-mgcp
crypto dynamic-map outside_dyn_map 20 set transform-set VPNHigh
crypto dynamic-map outside_dyn_map 40 set transform-set VPNHigh
Now, when the call agent (central) sends traffic to the call gateway (remote) when the tunnel is down, the ASA drops the packets and doesn't build a conn until the tunnel is brought up.
7. This was tested by bringing down the tunnel and watching incoming packets from the call agent (central) to the call gateway (remote) and verified they weren't being sent out in the clear. The tunnel up was brought up and traffic started being passed between the call agent and the call gateway.

MGCP Dialling Problem

I have a CCM 4.0 and an MGCP gateway cisco 1760 with VIC-2FXO. I can receive the calls from both IP network and PSTN but i am unable to call out to the PSTN. What could be the problem?

There could be several things causing this, here are the troubleshooting guides for callmanager:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_troubleshooting_guides_list.html

MGCP with FXO Problems

I have configured MGCP to access an FXO port used for our paging systems.
When I dial the access code, I get the Intercom Tone briefly then the audio goes away and I am showing connected. The voice port status even shows the interface as being up. When I hang up it shows idle.
Any Ideas?
We are running 12.2(15)T on the router. 2651

After alot of debugging, I found the problem, but it doesn't make sense. I had to change the route pattern to remove the digits predot.
Example *5.
It was sending the *5 to the Intercom.
Can anyone enlighten me to the below the command?
mgcp dtmf-relay voip codec all mode out-of-band
I thought this command on the router removed the digits sent to an MGCP Gateway?
If I am wrong, please explain. Any explaination would help me.
Jason

VG224 box & analog phones with CCM3.3 - call problem

Hi
We have CCM3.3 at central location & at remote location with 2mb leased line have router & connected to LAN then VG224, analog phoenes.
Initially VG224 not reg, then it got reg with use of h323 procol config at both CCM & VG end.
Now 2 analog ph are connected at VG end and tring to call IP phone number which is got reg with CCM3.3.
Result: from analog ph able ring IP Phone but Ip phone cannot. And one more is from analog to IP Phone is one way, call initiator is getting voice from IP Phone. but IP Phones not able to hear anything.
Need solution & troubleshoot for the same.
Regards
Naga.

Hi,
try removing voice-class and use "codec g711u" instead under DP 4000.
Hope this helps, please rate post if it does!

VG224 Ports - No Dial Tone

Every now and then a customer has a vg224 that the ports will just quit working. No dialtone. The workaround has been to reconfigure a new port and move the device but they will fail again eventually. Whomever set this vg224 up is using a combination og MGCP ports as well as SCCP ports. It seems the MGCP ports are the problem. But, I am running many vg224 with MGCP at many locations with no problems like this. Any suggestions? Thanks in advance.

When I run into that issue on a VG224 I put these commands with the port that has no dial tone and it corrects the issue. It is like if the VG224 does not hang up that port when the call is finished.
voice-port 2/0
no supervisory disconnect lcfo
disconnect-ack
no battery-reversal
Let me know if that helped.

Vg224 mgcp problem

Similar Messages

Maybe you are looking for