MGCP tftp download failed

jpedrocarvalho · ‎07-16-2008

Hi,

We have 2 Cisco 2801 configured with MGCP that register ok but always give "TFTP dowanload failed".

When I debug "ccm-manager config-download" its says

*Jul 16 10:39:11.795: cmapp_xml_tftp_download_file: Unable to read file tftp://1

0.0.5.250/EAA_AERO_R1.euroatlantic.aero.cnf.xml, rc=-2

*Jul 16 10:39:11.795: cmapp_xml_get_xml_file: Could not read file tftp://10.0.5.

250/EAA_AERO_R1.euroatlantic.aero.cnf.xml, len = 0

*Jul 16 10:39:11.795: cmapp_xml_tftp_download_file: Unable to read file tftp:///

EAA_AERO_R1.euroatlantic.aero.cnf.xml, rc=-2

*Jul 16 10:39:11.795: cmapp_xml_get_xml_file: Could not read file tftp:///EAA_AE

RO_R1.euroatlantic.aero.cnf.xml, len = 0

*Jul 16 10:39:11.795: cmapp_xml_tftp_download_file: Unable to read file tftp:///

EAA_AERO_R1.euroatlantic.aero.cnf.xml, rc=-2

*Jul 16 10:39:11.795: cmapp_xml_get_xml_file: Could not read file tftp:///EAA_AE

RO_R1.euroatlantic.aero.cnf.xml, len = 0

*Jul 16 10:39:11.795: cmapp_xml_exec_fsm: New state = CMAPP_XML_FILE_DNLD, ep =

65A32798

Our main office Cisco 2851 has no problem with this.

Can somenone help me with this?

tristan.delsol · ‎07-18-2008

How does you config look like? Especially the ccm-manager part.

Ayodeji Okanlawon · ‎07-18-2008

Hi,

Make sure that IP address in your

ccm-manager config server 171.69.103.225

points to the ip address of your tftp server/publisher

In the above example, 171.69.103.225 is my tftp server/publisher

Please rate all useful posts

andymclaughlin · ‎05-31-2018

Always remember - if you have loopback addresses as bind interfaces for MGCP you may also have ACL's/FW's preventing voice subnets from accessing data network segments for security purposes, Remember to use the command:

ip tftp source-interface Loopback(#)

Or you may get tftp / config-download issues as the outbound traffic from the Voice Gateway will use the outbound interface of the router for TFTP and from potentially a non Voice IP address as the source IP (rather than an binded MGCP loopback for signalling / rtp). This also is a cause of "registration rejected" in CUCM.

This is very typical on ISR routers that are not only used as a voice gateway when you want other network ranges to use for EIGRP / OSPF / BGP neighbour addressing and separate ranges for voice for easy QoS management.

And of course the most common MGCP registration issue is ensuring hostname + domain matches in sh ccm-manager: (MGCP Domain Name: HOST.domain first line of output) in CUCM.