[cisco-voip] Phone Load Error

Wes Sisk wsisk at cisco.com
Thu May 8 16:04:16 EDT 2008


Steven,

Informix traffic would affect communication between CM servers.  This 
would cause your database replication to appear broken.  it shouldn't so 
much affect TFTP or SCCP signaling to the phone device though.

/Wes

STEVEN CASPER wrote:
> Thanks for the info, at the moment it looks like the firewall is SCCP 
> aware and doing packet inspection. It is blocking the load complaining 
> that the traffic is Informix, which I guess makes  sense since this is 
> CCM 6. We have opened a case with the firewall vendor.
>  
> Steve
>
> >>> "Wes Sisk" <wsisk at cisco.com> 5/8/2008 1:16 PM >>>
> Steven,
>
> A packet capture from the back of hte phone would be much more 
> informative.  I believe the message below indicates the phone 
> attempted to TFTP download a file and the TFTP transaction failed.  
> This is a common fialure through firewalls because of CM's TFTP behavior:
>
> 1. phone sends TFTP GET from phone UDP port (p1) to CM on TFTP well 
> known port (p2)
> 2. CM sends TFTP datapackets sourced from random UDP source port (p3) 
> to phone (p1)
> 3. phone sends TFTP ACK for every datapacket from phone port (p1) to 
> CM port (p3)
>
> the change in port numbers on the CM side is a problem for most firewalls.
>
> you may want to test TFTP transactions through your firewall.  windows 
> includes a tftp client:
>
> C:\>tftp /?
>
> Transfers files to and from a remote computer running the TFTP service.
>
> TFTP [-i] host [GET | PUT] source [destination]
>
>   -i              Specifies binary image transfer mode (also called
>                   octet). In binary image mode the file is moved
>                   literally, byte by byte. Use this mode when
>                   transferring binary files.
>   host            Specifies the local or remote host.
>   GET             Transfers the file destination on the remote host to
>                   the file source on the local host.
>   PUT             Transfers the file source on the local host to
>                   the file destination on the remote host.
>   source          Specifies the file to transfer.
>   destination     Specifies where to transfer the file.
>
>
> C:\>tftp -i 172.18.110.38 GET XMLDefault.cnf.xml
> Transfer successful: 5626 bytes in 1 second, 5626 bytes/s
>
>
> Otherwise, a packet capture of all phone traffic would be very helpful.
>
> /Wes
>
> STEVEN CASPER wrote:
>>  Trying to get a 7940 to load on Call Manager 6.1.1 via a firewall. 
>> No problem having 7940's connect on non-firewalled sites.  Receiving 
>> this error:
>>  
>>  
>>  Date: May 8 09:25:37
>> Machine Name: mparkn02ccmpub6
>> Severity: Error
>> App ID: Cisco CallManager
>> Message:  ccm: 250: May 08 13:25:37.336 UTC :  
>> ÃŒM_CALLMANAGER-CALLMANAGER-3-StationEventAlert: Station alert. 
>> Protocol:SCCP TCP ProcessID:1.100.7.318 Device Text:6: 
>> Name=SEP001646682753 Load=8.0(8.0)File Not Found Param1:2369 
>> Param2:1409476618 Cluster ID:StandAloneCluster Node ID:mparkn02ccmpub6
>>  
>> This seems to indicate that the actual phone type and the phone type 
>> in the database do not match but it is a 7940 and shows up as 
>> auto-registered in Call Manager but it will not load. I can not find 
>> much detail on this error. Any ideas?
>>  
>> Thanks!
>> Steve
>>
>> ************************************
>> This email may contain privileged and/or confidential information 
>> that is intended solely for the use of the addressee. If you are not 
>> the intended recipient or entity, you are strictly prohibited from 
>> disclosing, copying, distributing or using any of the information 
>> contained in the transmission. If you received this communication in 
>> error, please contact the sender immediately and destroy the material 
>> in its entirety, whether electronic or hard copy. This communication 
>> may contain nonpublic personal information about consumers subject to 
>> the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley 
>> Act. You may not directly or indirectly reuse or disclose such 
>> information for any purpose other than to provide the services for 
>> which you are receiving the information.
>> There are risks associated with the use of electronic transmission. 
>> The sender of this information does not control the method of 
>> transmittal or service providers and assumes no duty or obligation 
>> for the security, receipt, or third party interception of this 
>> transmission.
>> ************************************
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>   
>
> ************************************
> This email may contain privileged and/or confidential information that 
> is intended solely for the use of the addressee. If you are not the 
> intended recipient or entity, you are strictly prohibited from 
> disclosing, copying, distributing or using any of the information 
> contained in the transmission. If you received this communication in 
> error, please contact the sender immediately and destroy the material 
> in its entirety, whether electronic or hard copy. This communication 
> may contain nonpublic personal information about consumers subject to 
> the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley 
> Act. You may not directly or indirectly reuse or disclose such 
> information for any purpose other than to provide the services for 
> which you are receiving the information.
> There are risks associated with the use of electronic transmission. 
> The sender of this information does not control the method of 
> transmittal or service providers and assumes no duty or obligation for 
> the security, receipt, or third party interception of this transmission.
> ************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080508/1c49ac13/attachment.html 


More information about the cisco-voip mailing list