I could see lots of IPT_TCP_DOWN message and IPT_UNREG with reason 2204.
IPT_TCP_DOWN means TCP signaling interface DOWN/CLOSED. And IPT_UNREG means IP Terminal unregistered, the reason 2204 means Force unregister the link bounce phone if its link loss delay timer expired and it is not on the call. IPT_UNREG is generally followed by IPT_TCP_DOWN if the phones that are facing the issue don’t receive packets from the PROCR for a prolonged period of time. This could be because of the PROCR or the switch that provides connection between the CM and the phone, or the path in between.
I suspect it could be caused by network issue. Packet Loss, Delays, Firewall ports blockage must be checked on network side.
Oct 2 12:14:42 MTL-HQ-ACMS-app logmanager: IPEVT IPT_TCP_DOWN board=PROCR ip=##.##.114.67 net_reg= 1 ext= 1806 the 1st ip=##.##.95.13; 6014 the 2nd ip=0.0.0.0; 0 net_reg= 1 reason=endpoint_request
Oct 2 12:14:46 MTL-HQ-ACMS-app logmanager: IPEVT IPT_TCP_DOWN board=PROCR ip=##.##.114.67 net_reg= 1 ext= 1786 the 1st ip=##.##.95.20; 5298 the 2nd ip=0.0.0.0; 0 net_reg= 1 reason=endpoint_request
Oct 2 12:14:46 MTL-HQ-ACMS-app logmanager: IPEVT IPT_TCP_DOWN board=PROCR ip=##.##.114.67 net_reg= 1 ext= 1776 the 1st ip=##.##.95.26; 4908 the 2nd ip=0.0.0.0; 0 net_reg= 1 reason=endpoint_request
Oct 2 12:15:53 MTL-HQ-ACMS-app logmanager: IPEVT IPT_UNREG board=PROCR ip=##.##.114.67 net_reg= 1 ext= 1828 ip= ##.##.95.11;49300 net_reg= 1 reason=2204
Oct 2 12:15:53 MTL-HQ-ACMS-app logmanager: IPEVT IPT_UNREG board=PROCR ip=##.##.114.67 net_reg= 1 ext= 1846 ip= ##.##.95.13;49300 net_reg= 1 reason=2204
Oct 2 12:15:53 MTL-HQ-ACMS-app logmanager: IPEVT IPT_UNREG board=PROCR ip=##.##.114.67 net_reg= 1 ext= 1827 ip= ##.##.95.14;49300 net_reg= 1 reason=2204
Oct 2 12:15:53 MTL-HQ-ACMS-app logmanager: IPEVT IPT_UNREG board=PROCR ip=##.##.114.67 net_reg= 1 ext= 1852 ip= ##.##.95.20;49300 net_reg= 1 reason=2204
Oct 2 12:15:53 MTL-HQ-ACMS-app logmanager: IPEVT IPT_UNREG board=PROCR ip=##.##.114.67 net_reg= 1 ext= 1821 ip= ##.##.95.21;49300 net_reg= 1 reason=2204
Scenario 2:
Along with this,if the IP endpoints are configured to register to a CLAN board, it is recommended to upgrade the CLAN board to the latest FW ( which as of January 2018 is FW 44), as it includes a fix provided in FW 38 that corrects an issue that could prevent phone registrations, along with many additional fixes. Here is the readme for the fix in FW 38 - ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/firmware/2020/tn799dp-h0-f38-2.txt.
Also, the maximum number of IP phone and media gateway registrations a given CLAN board can handle is a) 6 Media gateways and 200 to 250 IP stations for a call center scenario b) 8 media gateways and 250 to 300 IP stations for a non-call center environment.
Sniffer traces from endpoint and from CM will be helpfull to have a clue where the issue is.
