Getting CME working on a 2801...

ptlinva

I'm at the point in my studies that I'm ready to get CME working for the 1st time.

I have cme-full-7.1.0.0.tar which I'm currently extracting (using the archive command) to the Compact Flash from the TFTP Server.

However, I also have a file by the name of "cme-124-24T.zip" that I'm not sure if it's needed.

What exactly is this file and is it needed to get CME running?

I'm currently running "c2801-adventerprisek9-mz.124-24.T.bin" on my 2801.

Thanks in advance for your time and comments!

Your friend in Virginia,
Paul L.

tha_dub

CME is actually part of the IOS which is already installed on your router so in theory you are good to go. The tar file you have should contain the phone firmware and the GUI files.

Get those uploaded and setup your routers tftp server for the correct files. Also there are a few commands to get the web gui going to.

As far as cme-124-24T.zip I would open the zip file and post what files are packed up in it.

If you have the IIUC cisco press book I'd suggest going through the setup step by step with the book which is what I did and all this will become clear.

ptlinva

Okay, I noticed using the 'archive' command, it successfully extracted all the files out of the cme-full-7.1.0.0.tar file. However, it's a bit different than Jeremy's videos where he's doing cme 4.x and there was NO /phone directory with all the firmware.

In the cme-124-24T.zip file that I have are the following files (below)... It looks as though it contains the phone files but it's no where near as clean as what the 4.x extracted out for Jeremy.

I'm a bit lost at the moment. I think I will get the Cisco IIUC book you recommended...

Thanks again for your time!
-Paul L.

---

Directory of C:\Users\Tommy\Desktop\Cisco\cme\cme-124-24T
12/05/2010 11:35 PM <DIR> .
12/05/2010 11:35 PM <DIR> ..
01/19/2009 04:34 PM 6,884,864 7906-7911-sccp.8-4-2S.tar
01/19/2009 04:34 PM 7,273,472 7906-7911-sip.8-4-2S.tar
01/19/2009 05:13 PM 6,879,232 7931-sccp.8-4-2S.tar
01/19/2009 04:31 PM 7,086,080 7941-7961-sccp.8-4-2S.tar
01/19/2009 04:32 PM 7,475,200 7941-7961-sip.8-4-2S.tar
01/19/2009 04:30 PM 7,035,904 7942-7962-sccp.8-4-2S.tar
01/19/2009 04:31 PM 7,426,048 7942-7962-sip.8-4-2S.tar
01/19/2009 04:30 PM 7,165,952 7945-7965-sccp.8-4-2S.tar
01/19/2009 04:29 PM 7,555,072 7945-7965-sip.8-4-2S.tar
01/24/2009 09:42 AM 5,237 7970-71-75-Background-readme-v1.txt
01/20/2009 05:01 PM 641,024 7970-71-75-backgroundsv1.tar
01/19/2009 04:28 PM 7,290,880 7970-7971-sccp.8-4-2S.tar
01/19/2009 04:29 PM 7,678,464 7970-7971-sip.8-4-2S.tar
01/19/2009 04:28 PM 7,165,440 7975-sccp.8-4-2S.tar
01/19/2009 04:27 PM 7,555,072 7975-sip.8-4-2S.tar
03/28/2008 11:14 AM 7,892,498 apps37sccp.1-2-1-0.bin
01/04/2006 04:02 PM 279,194 ATA030203SCCP051201A.zup
11/11/2008 01:34 PM 146,463 B015-1-0-3.SBN
11/11/2008 01:33 PM 165,355 B016-1-0-3.SBN
05/29/2009 01:02 PM 2,034,176 cme-bacd-3.0.0.2.tar
05/29/2009 12:59 PM 829,440 cme-gui-124-24T.tar
01/28/2009 03:48 PM 800,768 cme-gui-7.1.0.0.tar
05/29/2009 01:05 PM 11,075,107 cme-tsp-2.2.0.5.zip
02/27/2008 10:55 AM 1,382,912 cmterm-3951-sip.8-1-1.tar
02/26/2008 11:04 PM 1,155,568 cmterm_7920.4.0-03-02.bin
06/30/2008 01:24 PM 1,849,756 cmterm_7936.3-3-16-0.bin
05/02/2007 04:56 PM 14,987,470 cmterm_7985.4-1-4-0.bin
08/17/2006 05:15 PM 331,693 CP7902080002SCCP060817A.sbin
08/17/2006 05:15 PM 339,307 CP7905080002SCCP060817A.sbin
08/17/2006 05:16 PM 338,891 CP7905080002SCCP060817A.zup
04/09/2007 04:02 PM 341,023 CP7912080003SCCP070409A.sbin
01/12/2009 10:02 AM 10,967,040 CP7921G-1.2.1.TAR
01/20/2009 01:09 PM 9,543,680 CP7925G-1.3.1.TAR
01/09/2009 01:42 AM 593,920 cucme-mlpp.tar
03/29/2004 11:40 AM 496,521 music-on-hold.au
02/27/2008 11:05 AM 969,728 P00308000500.tar
01/19/2009 04:33 PM 349,794 P00405000700.bin
01/19/2009 04:33 PM 350,198 P00405000700.sbn
08/29/2006 10:33 AM 2,029,545 P00503021500.bin
07/02/2007 12:37 PM 2,146 RingTones Readme.txt
07/02/2007 12:35 PM 326,144 ringtones.tar
04/23/2007 09:56 AM 49,986 S00105000300.sbn
42 File(s) 164,746,264 bytes
2 Dir(s) 109,244,940,288 bytes free
C:\Users\Tommy\Desktop\Cisco\cme\cme-124-24T>

tha_dub

Also keep in mind cme 4.3 and 7 are the same thing. Cisco renamed it to 7 to match up with their CUCM line.

chmorin

ptlinva wrote: »

Okay, I noticed using the 'archive' command, it successfully extracted all the files out of the cme-full-7.1.0.0.tar file. However, it's a bit different than Jeremy's videos where he's doing cme 4.x and there was NO /phone directory with all the firmware.

In the cme-124-24T.zip file that I have are the following files (below)... It looks as though it contains the phone files but it's no where near as clean as what the 4.x extracted out for Jeremy.

I'm a bit lost at the moment. I think I will get the Cisco IIUC book you recommended...

Well the tar ball you extracted will put all of the files into your flash in the format that it was in the tar ball. Jeremy's might have been different, but you stil have all of your files there. When you set up your tftp server make sure you use the path that YOU have in YOUR router, and you will be fine.

If your 2801 IOS has CME installed, you are on the right track. Where/why are you lost?

EDIT:

Also, the tar ball is not required for CME to function, it is requried if you want physical phones to be able to install firmware and function. If you use, say, an IP Communicator from Cisco, you don't actually need to install the CME files. It is also needed if you want to use the web gui for CME configurations (which no one will suggest).

mikearama

chmorin wrote: »

It is also needed if you want to use the web gui for CME configurations (which no one will suggest).

Quite right... however, for the sake of the exam, you will want to have access to the cme gui.

In my install, this url gets me into the gui: http://192.168.1.100/ccme.html

Do a dir on your 2801... you'll know instantly if you're CME-ready if there's about 30 files present, on top of your IOS bin file.

When I checked the Feature Navigator for your IOS version, it has CME included, up to version 4.0(3). The cme-124-24T.zip file that you mentioned should be the CME files from within your TAR file... if you didn't have them (IE, deleted them), this file would replace them. So if you have cme-full-7.1.0.0.tar, you might try archiving it into flash. I don't think it'll run, as again, 12.4-24T would seem to only support up to CME 4.0(3), but hey, give it a shot.

ptlinva

Thank you both for your time. I find techexams so encouraging when things get a bit frustrating...

Just a quick overview... I'm watching Jeremy's IIUC videos so my lab duplicates what he is doing.

DHCP is on a seperate router from CME. The CME is hosting the TFTP Server.

I can see all (4) phones on my 3550 switch. I can see (4) IP addresses consumed from the DHCP Server with "show ip dhcp bindings".

The phones go from Configuring VLAN to Configuring IP and stay there. I've tried using some debug commands but I'm finding it hard to debug this type of lab.

I'm assuming that they ARE getting an IP and I do have option 150 set on the DHCP. I feel that my problem is with the TFTP/CME router. Is there a way to see request for CME/TFTP?

One last thing worth noting... I was able to load the Cisco IP communicator on my laptop and plug my laptop into the ethernet port on the phone. It obtained a correct IP from the DHCP server (different pool on a different vlan) and successfully registered on the CME.

I was able to do a "show ephone" and see...

ephone-1[0] Mac:0016.36F2.42BD TCP socket:[1] activeLine:0 whisperLine:0 REGISTERED in SCCP ver 15/12 max_streams=5
mediaActive:0 whisper_mediaActive:0 startMedia:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0 caps:10
IP:172.16.2.11 55215 CIPC keepalive 1 max_line 8 available_line 8
Preferred Codec: g711ulaw

However, I have (1) 7960 and (3) 7912's and they are all saying configuring IP and not showing up with the ephone command. I've also reset the 7960 to the factory defaults.

Is there a way to see requests coming into CME/TFTP? I do see...

Dec 10 00:09:02.125: %IPPHONE-6-REG_ALARM: 14: Name=SEP001636F242BD Load= 7.0.2.0 Last=UCM-closed-TCP
Dec 10 00:09:02.325: %IPPHONE-6-REG_ALARM: 14: Name=SEP001636F242BD Load= 7.0.2.0 Last=UCM-closed-TCP
Dec 10 00:09:02.325: %IPPHONE-6-REG_ALARM: 14: Name=SEP001636F242BD Load= 7.0.2.0 Last=UCM-closed-TCP
Dec 10 00:09:02.329: %IPPHONE-6-REGISTER_NEW: ephone-1:SEP001636F242BD IP:172.16.2.11 Socket:1 DeviceType:Phone has registered.

for the CIPC but I don't see any of the other phones ever making it that far...

Any suggestions you might offer?
<head bowing down to you cisco gods>

Your Cisco friend in Virginia,
Paul L

peanutnoggin

Is your tftp-server sharing the files the phones need? I believe the syntax is:

tftp-server flash:phone/7960/file.loads alias file.loads (I don't have my lab equipment so I can't set it up... this should get you started on the right path)!

Try using the "debug tftp event". That will show what files the phones are looking for from the tftp server. HTH.

-Peanut

chmorin

You could also show dhcp leases to see if your dhcp server is working properly. To see if it is giving out addresses properly, make an access port set to your voice vlan and plug a computer in it. If the computer gets the proper IP Address information, the issues probably lies in the TFTP server.

The CIPC does not need to pull any firmware, so this confirms that you know how to set up ephone's properly. So the issue probably lies in pulling firmware (as said above).

As said above, have you told the TFTP server where the particular files are? The phones will request a specific name, you need to map that name to the actual path of the file in the router. If you watch Jeremies videos I know he goes over this in detail.

ptlinva

Thank you gentlemen!

Well, I'm rebuilding the CME/TFTP router again. Each time I do, I seem to learn a little bit more. I did notice that I had (2) cme files... cme-full-7.1.0.0.tar and cme-full-7.0.0.1.tar.

According to the links you've posted and my IOS version, I should be running the 7.1. However, I was using the 7.0 version... not sure if that made any difference but I always seem to enjoy doing a 'wr er' and 'format flash:' ...

I'll post back later with the results... I just wanted to do a quick reply to thank you both! Chat with you soon...

Your friend,
Paul L.

peanutnoggin

That's the best way to learn... I like to call it... "rinse and repeat"!!

-Peanut

ptlinva

Hi Everyone,

Wow, this one has been a doosey (is that a word?)!

I haven't posted back because I really feel better when I WORK at something before asking questions... However, I tried again and I'm still having issues - same symptom and I feel as if it's something simple.

Just as a reminder, I've been watching Jeremy's IICU videos and also going through the Cisco Voice IICU Official Exam Certification Guide. Jeremy does this as well because the labs are exactly the same. (2) switches, (2) routers, (4) phones, same names, etc.

My phones turns on, states Configuring VLAN, and then stays on "Configuring IP".

I can go to the dhcp router and see (4) IP's within the VOICE dhcp scope assisned to the macs on the phone. If I plug a PC into the phone, I also see an IP get issued out of the DATA scope. If I issue debug tftp on the CME router (which is also the TFTP server), I see nothing.

What happens from the time a phone gets an IP to the time it starts to issue requests from the TFTP server?

Is there a way to debug this process? How about manually configuring the IP on the phones (7960's and 7912's) to see if it can reach the TFTP server? Maybe a routing issue? I'm ready to try anything...

Any suggestions or comments would be greatly appreciated.

Your Cisco Friend in Virginia

mikej412

Sounds like a job for the Troubleshooting IP Phone Registration in Cisco Unified CME PDF AND Wireshark.

You can always try the "One Beer, One Troubleshooting Step" method. It may never solve your problem, but after a bunch of troubleshooting steps you don't care anymore.

Did you verify the phone has an IP by pinging it from somewhere else?

Wireshark should let you see what the phone is getting and then if it's really looking for the tftp server.

What's your configuration? Did you run the max-ephone, max-dn, ip source-address, and create cnf-files commands?

ptlinva

I took your advice and tried pinging the phones directly... no go...

I was assuming that since IP's were being "binded" on the DHCP router that they were ACTUALLY BEING ASSIGNED to the phones. However, the phones were NOT accepting/receiving the IP.

My laptop connected TO THE PHONE received an IP and it worked just fine. I could ping all over the place from the laptop through the phone... Hmm...

If an IP was dedicated/given on the DHCP, what would keep the phone from actually using that IP? Hmm... I'll have to look into this... Maybe I should be doing CCNP Route/Switch before CCNA Voice...

Anyway, I moved the DHCP server to my CME router... and BINGO!

Everything registered with CME IMMEDIATELY! In fact, all (4) phones AND IP Communicator came right up!

Awesome! Thank you Mike (um, Mr. Cisco Santa)... and EVERYBODY ELSE!.. Thank you...

Have a wonderful Christmas!

Your Cisco Friend in Virginia,
Paul L.

...on to the next chapter...

tha_dub

I assume you are using a separate voice vlan config on your switch?

My guess is that whatever router you have setup to do ROAS does not have the IP helper-address command configured to point the voice vlan dhcp requests to the dhcp server...

Just a guess.