cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
297
Views
0
Helpful
1
Replies

"REG authentication failed: ack timer" meaning and log

Clutz5250
Level 1
Level 1

on a 7841, in phone con logs I'm seeing this:

0753 DEB Sep 25 13:53:37.211280 (0-577) syslog-dbus_manager::Sleeping 60 seconds
0754 ERR Sep 25 13:54:08.500460 (1926-2497) JAVA-%REG authentication failed: ack timer
0755 NOT Sep 25 13:54:08.501223 (1926-2497) JAVA-SIPCC-SIP_TCP_MSG: sip_tcp_purge_entry: Socket fd: 55 closed for connid 0 with address: <REDACTED - sub IP>, remote port: 5060
0756 NOT Sep 25 13:54:08.502230 (1926-2496) JAVA-SIPCC-SIP_CC_PROV: ccsnap_gen_deviceEvent: event type : SERVER_TRANSPORT
0757 NOT Sep 25 13:54:08.502688 (1926-2497) JAVA-SIPCC-UI_API: ui_set_ccm_conn_status: ***********CUCM <REDACTED - Sub NAME>Not connected ***********
0758 NOT Sep 25 13:54:08.503299 (1926-2497) JAVA-set_active_ccm: ccm=SECONDARY_CCM port=<REDACTED>
0759 NOT Sep 25 13:54:08.503848 (1926-2496) JAVA-SIPCC-SIP_CC_PROV: ccsnap_gen_deviceEvent: event type : SERVER_STATUS
0760 NOT Sep 25 13:54:08.520878 (1926-2497) JAVA-SIPCC-PLAT_API: setUnregReason: setting unreg reason to=17
0761 NOT Sep 25 13:54:08.521153 (1926-2497) JAVA-SIPCC-PLAT_API: setUnregReason: value of first_oos_alarm_set=0
...<REDACTED UPDATED ALARM INFO>
0763 NOT Sep 25 13:54:08.557594 (1926-2497) JAVA-Thread-5|JPlatUi:setUnregReason - old-unregister-reason:25, new unregister-reason:17, cc-server-type:0
0764 NOT Sep 25 13:54:08.558052 (1926-2497) JAVA-Thread-5|JPlatUi:isThisFailureFromNewCause - old unregReason =25 newUnregReason=17
0765 NOT Sep 25 13:54:08.559090 (1926-2361) JAVA-configmgr MQThread|cip.cfg.Config: - [propertyChanged()] propName:"device.settings.config.sipprofile.local.sipunregreason"
0766 NOT Sep 25 13:54:08.571084 (1926-2497) JAVA-SIPCC-PLAT_API: setUnregReason: setting unreg reason to=17

Phone failsover to other sub, then later falls back.

Shouldn't there be multiple ACKs to determine timeout?

also, site has 4 phones, all with same shared line.


1 Reply 1

Jonathan Schulenberg
Hall of Fame
Hall of Fame

No, I would not expect repeated attempts to a SIP auth failure - but IP Phones don’t usually authenticate unless you have changed the security profile to use CAPF LSC or OAuth. A PCAP from the phone while it’s set to span traffic to the PC Port would be interesting. If it’s all four phones doing this I’d be very suspicious of an issue along the network path.