[cisco-voip] ASA PhoneProxy TFTP error on Publisher/TFTP server

[c3voip]

I think I figured it out, but am not sure that I understand.  Why should the
proxy be requesting tftp files with the Internet address of the phone client
if it is "proxying" for it?  I missed the part where the ASA has to be in
path with traffic to the Internet from the CallManager.  I thought a proxy
would act on behalf of  the phones and the phones would show up on the LAN
with the ASA's Inside interface address.  I had to add a host route on my
CCM/TFTP server to get TFTP to work.

 

I'm confused.

 

-C

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of c3voip
Sent: Friday, October 31, 2008 4:01 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] ASA PhoneProxy TFTP error on Publisher/TFTP server

 

I am trying to get the ASA Phone Proxy feature up and working with CCM
4.1.3, but I am getting the following tftp error messages when the cnf.xml
file is requested by the ASA for the phone:

 

10/31/2008 15:50:13.656 TFTP|
CTftpConnect::sendFileUsingIOCP[4760:Internet_IP:49180] Timeout Occurred
[size 512, block 1, timeout 25]|<CLID::Cluster><NID::CCM_IP>

10/31/2008 15:50:13.656 TFTP|
CTftpConnect::serve[0A016B30],[4760:Internet_IP:49180] Call to sendFile
failed inside tftp() [SEP0021D8BA87D8.cnf.xml]|<CLID::Cluster><NID::CCM_IP>

10/31/2008 15:50:17.656 TFTP|
CTftpConnect::sendFileUsingIOCP[4792:Internet_IP:49180] Timeout Occurred
[size 512, block 1, timeout 25]|<CLID::Cluster><NID::CCM_IP>

10/31/2008 15:50:17.656 TFTP|
CTftpConnect::serve[0A0185F8],[4792:Internet_IP:49180] Call to sendFile
failed inside tftp() [SEP0021D8BA87D8.cnf.xml]|<CLID::Cluster><NID::CCM_IP>

 

The phone boots and loads fine when on the local LAN, but it errors when the
ASA requests the same file.

 

Any ideas on what this means, do I need to turn on more detailed traces?

 

Thanks,

-C

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081103/e9e0e8dd/attachment.html>