CME 9.1 and converting SCCP 6945 to SIP 6945 ?

[Jason Aarons]

I have a customer with SCCP 6945s registered to CallManager Express 9.1.  I want to convert the 6945s from SCCP to SIP (to match some SIP only 8971s).

How do I get these 6945s to switch from SCCP to SIP?

[acampbell]

Jason,

Have a look in the CME Admin Guide.

Section SCCP: Converting Phone Firmware to SIP

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmeinstl.html#wp1065072

Regards,
Alex.
Please rate useful posts.

[Jason Aarons]

The Admin Guide didn't work.  Seems to be more focused on 79xx phones.  I also tried a factory reset on 6945, debug attached of phone booting, and a show run.

[acampbell]

Jason,

Looks like phone is still able to retrieve it config file

From your TFTP trace

Apr  9 15:04:53.110: TFTP: Looking for SEP8875567AF7FF.cnf.xml

Apr  9 15:04:53.110: TFTP: Opened flash:/its/SEP8875567AF7FF.cnf.xml, fd 4, size 4218 for process 15

Apr  9 15:04:53.110: TFTP: Sending block 1 (retry 0), len 512, socket_id 0x2E751AF8

Apr  9 15:04:53.112: TFTP: Received ACK for block 1, socket_id 0x2E751AF8

Apr  9 15:04:53.112: TFTP: Sending block 2 (retry 0), len 512, socket_id 0x2E751AF8

Apr  9 15:04:53.110: TFTP: Looking for SEP8875567AF7FF.cnf.xml

Apr  9 15:04:53.110: TFTP: Opened flash:/its/SEP8875567AF7FF.cnf.xml, fd 4, size 4218 for process 15

Apr  9 15:04:53.110: TFTP: Sending block 1 (retry 0), len 512, socket_id 0x2E751AF8

Apr  9 15:04:53.112: TFTP: Received ACK for block 1, socket_id 0x2E751AF8

Apr  9 15:04:53.112: TFTP: Sending block 2 (retry 0), len 512, socket_id 0x2E751AF8

etc etc etc

Can you confirm that you have deleted the SCCP ephone

!

no ephone xx

!

Then can you try to delete the cnf file

!

telephony-service

no create cnf-files

!

Now try resetting the phone by re-inserting the cat5 lead

See how this goes

Regards,
Alex.
Please rate useful posts.

[Jason Aarons]

Spent 2 hours with case TAC 625498511 and they couldn't get a 6945 SCCP to switch to SIP using Express.  I finally used a CallManager to get it to switch to SIP.  Then the SIP 6945 couldn't register to CME, we spent 2 hours troubleshoting/debuging/tracing and gave up.  I went back to SCCP 6945.  Then I hit several SCCP 6945 CME 9.1 bugs like DND doesn't update on display, dtmf not working wo Unity Express 8.6, etc.

I'm thinking the 6945 wasn't a good choice.

[acampbell]

Hi Jason

Sometimes you just wonder if you would be better with

2 cans and a tight string

Up the 7960

Regards,
Alex.
Please rate useful posts.