[cisco-voip] How to get a Phone's .cnf.xml file from CUCM

[Anthony Holloway]

On Windows you can just pop open a command prompt window and type:

C:\>tftp <cucm_tftp_server> get SEP<MACADDRESS>.cnf.xml


Example:

C:\>tftp 10.1.1.1 get SEP0000DEADBEEF.cnf.xml


Source:
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/tftp.mspx?mfr=true

NOTE: Win7 users may need to turn on TFTP command line client from within
Add/Remove programs first.

On *nix systems: 'man tftp' should tell you what you need to know.

You may also want to SPAN the switch port the phone is on, and look at the
traffic.  Perhaps the .cnk.xml file is not even making it to the phone, or
perhaps there are missing packets.  TFTP is UDP after all, and therefore has
no re-transmits.

-Anthony

On Mon, Oct 10, 2011 at 6:29 PM, Bruno Takahashi <brunots at gmail.com> wrote:

> Hello all,
>
> We ran into a problem where it seems the .cnf.xml file of the phones is
> corrupted so the phone does not registers.
> If you change any detail on the device configuration (i.e. add a "-" on
> description) the phone registers back.
> I assume it works because a new file is generated and the phone gets this
> new, non-corrupted file from TFTP and is able to register.
>
> What I wanted to do is to get the .cnf.xml file from a phone that is not
> working, then "fix" it and get the new file again to compare and see if
> something can be found to indicate why this happened.
>
> Does anyone knows how can I get the .cnf file or knows any additional
> details on this issue?
>
> Thanks!
>
> --
> *Bruno*
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20111010/990332c5/attachment.html>