Cisco CP-8861 "Phone is Registering"

[julianparras]

Hi All.

I am trying to get a Cisco CP-8861 working on my CME although it is just stuck on Phone is registering. It has a correct IP from DHCP as well as the proper TFTP, DNS and Default Gateway from DHCP.

Versions of our hardware are as follows:
IOS 15.7
CME 12.0
Phone Firmware sip88xx.11-5-1-18

CME Config 

voice register global
mode cme
source-address 192.168.2.17 port 5060
max-dn 500
max-pool 100
authenticate register
tftp-path flash:
file text
create profile sync 0053538241525337
conference hardware
auto-register

voice register dn 10
number 6010

voice register pool 10
busy-trigger-per-button 2
id mac B000.B4BA.2AB2
type 8861
number 1 dn 10

Status Messages

TFTP error : AppDialRules.xml
Error Updating Network Locale
Error Updating User Locale
VPN not configured
SEPB000B4BA2AB2.cnf.xml(TFTP)
No Trust list installed

Does anyone have any thoughts?

[Mohammed al Baqari]

Hi,

You are using 'authenticate register' without a username/pass on your voice
pool. If the phone is in the same subnet as the CME, remove this command >
create profile and power cycle the phone.

[julianparras]

Hi, I just tried removing Authenticate register although i still am having the same issues. I have attached a debug.

The phones are usually on a X.X.12.X subnet and the cme is on a X.X.2.X subnet although we have put the phone on a X.X.2.X subnet for testing purposes but still we are getting the same result.

[Pavel Herc]

here in the logs i do not see any IP. 

<String name="UnifiedCMIPAddress"></String>

i am not working with the cme almost at all but is the ip of the cucm reachable and are ports 5060 or 5061 opened ?  U can try to open the telnet connection from the phones subnet towards the cucm on that port...

[Mohammed al Baqari]

Hi,

Do you have the following config in your CME

voice service voip
sip
registrar
bind source all x/x

[julianparras]

Hi Mohammed,

Yes we do our current config is 

voice service voip
ip address trusted list
ipv4 x.x.x.x
ipv4 x.x.x.x
ipv4 x.x.x.x
ipv4 x.x.x.x
ipv4 x.x.x.x
clid network-provided
dtmf-interworking standard
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
supplementary-service h450.12
no supplementary-service sip moved-temporarily
no supplementary-service sip refer
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
h323
h225 id-passthru
h225 connect-passthru
sip
bind control source-interface GigabitEthernet0/1
bind media source-interface GigabitEthernet0/1
registrar server expires max 600 min 60

Thank you for your ongoing help.

[Maren Mahoney]

The <Enum name="ReasonForOutOfService">14</Enum> indicates that the registration message from the phone is malformed. That could be because it is misconfigured in CME, it could be missing a component (in a more sophisticated environment), or that the profile is out of date.

When you removed the 'authenticate register' did you also recreate the profiles and then reset the phone?

Maren

[julianparras]

Hi Maren,

Yes after removing the "Authenticate register" We tried the "Create Profile" although it still just hung on the "Device is registering screen"

regards

[julianparras]

Hi Thank you for your message, We are using CME not CUCM and the ports are open.