VG224 error ACTIVE_IN_PROGRESS - Cause Code: CCM_REGISTER_FAILED

[rajesh.kumar]

I have CUCM 6.1(4a)SU2 on production.

There are 20 number of VG224, None of the VG224 are getting registerd with CallManager.

Day before CUCM version was 6.1(2) some Analog Phones are not getting registered and sometime few VG224 was not getting registered

We upgraded the CUCM to 6.1(4a)SU, after upgrade none of the VG224 are getting registered.

Tried, restarting VG224 and tried no sccp and sccp, also tried restarting CUCM, but no use.

VG224 Version 124-2.T6
CallManager Version - 6.1(4a)SU2

SCCP Admin State: UP
Gateway IP Address: 10.200.0.124, Port Number: 2000
IP Precedence: 5
User Masked Codec list: None
Call Manager: 10.207.0.6, Port Number: 2000
                Priority: N/A, Version: 3.1, Identifier: 10
Call Manager: 10.207.0.5, Port Number: 2000
                Priority: N/A, Version: 3.1, Identifier: 12

Alg_Phone Oper State: ACTIVE_IN_PROGRESS - Cause Code: CCM_REGISTER_FAILED
Active Call Manager: 10.207.0.6, Port Number: 2000
TCP Link Status: NOT_CONNECTED, Device Name: AN1C58C9804D400
Reported Max Streams: 1, Reported Max OOS Streams: 0
Supported Codec: g711ulaw, Maximum Packetization Period: 20
Supported Codec: g711alaw, Maximum Packetization Period: 20
Supported Codec: g729ar8, Maximum Packetization Period: 220
Supported Codec: g729br8, Maximum Packetization Period: 220
Supported Codec: g729r8, Maximum Packetization Period: 220
Supported Codec: NSE VBD, Maximum Packetization Period: 20
-----------------------------------------------------------

[asharsidd]

I had the same issue where I was getting error like below from both Call Managers configured on the Gateway under sccp

May 7 09:11:48.017: SCCP(ANAXXXX2E4405)rcvd RegisterRejectMessage
May 7 09:11:48.017: sccp_appl_service_stop_timer: Stop 657C1904 timer
May 7 09:11:48.017: sccp_parse_control_msg_v1: rcvd register rej, reason: Security Error

The Analog Gateway was working fine before and then stopped working with Registration Rejected on all ports.

Later I found that the device pool configured on the ports has a CCM group which is different than the ones configured on the Gateway! This must match!! I removed the config from GW (no sccp/ no ccm group 1) and pointed the sccp config to the Call Managers which are in device pool and viola all ports registered back happily!