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

[Nicholas Samios]

Use HTTP - thanks Wes ☺

http://myccmserver:6970/SEPmacaddress.cnf.xml

https://puck.nether.net/pipermail/cisco-voip/2011-February/019958.html
https://supportforums.cisco.com/message/3153749#3153749
--
Nicholas Samios
Systems Engineer
[cid:image001.gif at 01CC881E.B96A0030]
Level 2, 293 Camerbwell Road, Camberwell VIC 3124
ph: (08) 9213 1316 mob: 0411 618 835 fax: (08) 9221 4539
email: nsamios at staff.iinet.net.au<mailto:nsamios at staff.iinet.net.au>
[cid:image002.jpg at 01CC881E.B96A0030][cid:image003.jpg at 01CC881E.B96A0030][cid:image004.jpg at 01CC881E.B96A0030] [cid:image005.jpg at 01CC881E.B96A0030]

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Anthony Holloway
Sent: Tuesday, October 11, 2011 1:28 PM
To: Bruno Takahashi
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] How to get a Phone's .cnf.xml file from CUCM

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<mailto: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<mailto: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/20111011/f79dd3d3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 1824 bytes
Desc: image001.gif
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20111011/f79dd3d3/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 24708 bytes
Desc: image002.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20111011/f79dd3d3/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 25290 bytes
Desc: image003.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20111011/f79dd3d3/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 25338 bytes
Desc: image004.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20111011/f79dd3d3/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.jpg
Type: image/jpeg
Size: 27151 bytes
Desc: image005.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20111011/f79dd3d3/attachment-0003.jpg>