Avaya CM - Reason codes for IP Events
Reason codes for IP Events
Enable IP Events you need to enable IP logging levels
To record events to log files:
In CM you must set LOG IP Registrations and events: y
change logging-levels Page 2 of 2
LOGGING LEVELS
Log All Submission Failures: y
Log PMS/AD Transactions: y
Log IP Registrations and events: n
Log CTA/PSA/TTI Transactions: y
Below is an example (we need to use sudo to access ipevt)
cgzz@labacm> sudo logc -r --view ipevt | more
20230404:162659000:295944:lxsys:MED:labacm logmanager: IPEVT IPT_TCP_UP board=PROCR ip=10.123.123.10 net_reg= 1 ext= 1336035 the 1st ip=10.10.169.180;13926 the 2nd ip=0.0.0.0; 0 net_reg= 1 reason=switch_request
20230404:162658000:295943:lxsys:MED:labacm logmanager: IPEVT IPT_TCP_DOWN board=PROCR ip=10.123.123.10 net_reg= 1 ext= 1336035 the 1st ip=10.10.169.180;13926 the 2nd ip=0.0.0.0; 0 net_reg= 1 reason=00000
20230404:162658000:295942:lxsys:MED:labacm logmanager: IPEVT IPT_TCP_UP board=PROCR ip=10.123.123.10 net_reg= 1 ext= 1339100 the 1st ip=10.10.175.169;13926 the 2nd ip=0.0.0.0; 0 net_reg= 1 reason=switch_request
20230404:162657000:295941:lxsys:MED:labacm logmanager: IPEVT IPT_REG board=PROCR ip=10.123.123.10 net_reg= 1 ext= 1339100 ip= 10.10.175.169; 1024 net_reg= 1 reason=normal
20230404:162645000:295940:lxsys:MED:labacm logmanager: IPEVT IPT_UNREG board=PROCR ip=10.123.123.10 net_reg= 1 ext= 4095312 ip= 10.10.175.92; 1024 net_reg= 1 reason=2012
20230404:162643000:295938:lxsys:MED:labacm logmanager: IPEVT IPT_TCP_UP board=PROCR ip=10.123.123.10 net_reg= 1 ext= 1336021 the 1st ip=10.10.170.14;13926 the 2nd ip=0.0.0.0; 0 net_reg= 1 reason=switch_request
20230404:162642000:295937:lxsys:MED:labacm logmanager: IPEVT IPT_REG board=PROCR ip=10.123.123.10 net_reg= 1 ext= 1336021 ip= 10.10.170.14; 1024 net_reg= 1 reason=normal
20230404:162635000:295935:lxsys:MED:labacm logmanager: IPEVT IPT_TCP_UP board=PROCR ip=10.123.123.10 net_reg= 1 ext= 1338647 the 1st ip=10.10.169.137;13926 the 2nd ip=0.0.0.0; 0 net_reg= 1 reason=switch_request
20230404:162635000:295933:lxsys:MED:labacm logmanager: IPEVT IPT_REG board=PROCR ip=10.123.123.10 net_reg= 1 ext= 1338647 ip= 10.10.169.137; 1024 net_reg= 1 reason=move-user
20230404:162635000:295932:lxsys:MED:labacm logmanager: IPEVT IPT_UNREG board=PROCR ip=10.123.123.10 net_reg= 1 ext= 1338647 ip= 10.10.171.41; 1024 net_reg= 1 reason=2009
In the previous example we can find an IP_UNREG event 2009, code 2009 = Force Unregistration Request. Extension is already registered, but received a forced login registration request (RRQ). Send a URQ to the existing extension.
User is trying to register with an extension that is already register
| 2000 |
Unregistration Request rejected because no station user record exists for unregistering user (internal software error). |
| 2002 |
Unregistration Request rejected because of failure to build an unregistration request confirm (UCF) message (internal software error). |
| 2004 |
Unregistration Request rejected because the no station user record exists for the unregistering user (internal software error). |
| 2007 |
Force Unregistration Request. Unregister user because there is no signaling connection. RAS is alive, but the signaling connection has gone down (user cannot make calls). Re-register the endpoint. |
| 2008 |
Force Unregistration Request. Unregister associated H.323 user because there is no signaling connection. Re-register the endpoint. |
| 2009 |
Force Unregistration Request. Extension is already registered, but received a forced login registration request (RRQ). Send a URQ to the existing extension. |
| 2010 |
Forced Unregistration Request. The Gatekeeper is unregistering the endpoint because its call signaling connection has closed. |
| 2011 |
Force Unregistration Request. After an endpoint registers it should initiate the TCP connection and send a SETUP message. The SETUP message has not been received from the endpoint, and no Q931 Call object exists. The endpoint cannot make calls, so unregister it. |
| 2012 |
Force Unregistration Request. Unregister endpoint that has aged out. Endpoint's time to live (TTL) expired without receiving a keep-alive request (RRQ). |
| 2015 |
Forced Unregistration Request. Unregister user because the extension has been removed. |
| 2017 |
Forced Unregistration Request. Unregister the endpoint if there are no station user-records remaining. |
| 2018 |
Forced Unregistration Request. The release command was run on the extension or port. |
| 2019 |
Forced Unregistration Request. The release command was run on the Remote Office extension or port. |
| 2021 |
Custom Selection of VIP Direct Inward Dialing numbers feature is not active. |
| 2022 |
Announcement present but not administered. |
| 2023 |
Announcement present but no announcements administered for the board. |
| 2024 |
Registration rejected because unable to create an entry in the MTM complex table. 2025 Registration rejected because the option chosen by the endpoint in the RRQ for the emergency call does not match the option administered on the station form. |
| 2026 |
Xmobile offhook request rejected because Xmobile station has been taken out of service. |
| 2027 |
User attempted to play announcement and file was not found on board. |
| 2028 |
User attempted to play announcement and file had bad format. |
| 2029 |
Gatekeeper Request rejected because the Non Standard Data (NSD) from the registered application has an invalid object ID. |
| 2030 |
Gatekeeper Request rejected because of failure to decode Non Standard Data (NSD) element. |
| 2031 |
Gatekeeper Request rejected because of unexpected Non Standard Data (NSD) message from the registered application endpoint. |
| 2032 |
Force Unregistration Request. Instruct the RAS manager to cleanup a User ID which had just been registered prior to a system restart. This event is not logged, but only passed in the URQ. |
| 2033 |
Force Unregistration Request. Reset ip-stations was executed from the SAT to force unregister endpoints. |
| 2038 |
Getting the calling party number from the incoming side of the call failed. |
| 2039 |
Keep Alive Registration Request. Registration rejected because no endpoint identifier was provided. |
| 2040 |
Gatekeeper Request rejected because no resources available for signaling connection. |
| 2041 |
Registration Request rejected because no Digital Signal Processor (DSP) resources are available. |
| 2042 |
Registration Request rejected because no Digital Signal Processor (DSP) resources are available. |
| 2043 |
ARQ rejected because srcInfo and destinationInfo contents indicate the multipoint ept (VSX) is calling itself. |
| 2047 |
Registration rejected because it was received from unauthorized media platform. |
| 2048 |
Registration rejected because it is not ready for a media gateway re-registration. |
| 2049 |
VOIP Resources unavailable. |
| 2050 |
No gateway resource available |
| 2051 |
Remote Office invalid request (GRQ) No Sig Group available. |
| 2052 |
Remote Office invalid registration request (RRQ) No Sig group available. |
| 2053 |
MGKeepAlive: Wakeup() media platform heartbeat missed, indicates lackof traffic from specified platform. |
| 2054 |
UMSocket: SockWrite() Congestion on the Signaling Link due to PCD buffer exhaustion. |
| 2055 |
Reset the media platform Signaling Link due to error in Sending packets. |
| 2058 |
IncomingMsg. Null caps received on terminating end of H323 trunk. |
| 2059 |
Change of security code through Feature Access Code not supported for IP. |
| 2061 |
Post message digit timeout. |
| 2062 |
Post message too many digits. |
| 2063 |
Post message not station user. |
| 2064 |
Registration rejected because of failure to encode Non-standard Data (NSD) message. |
| 2070 |
Media gateway attempted registration with “warm start” condition, but the controller needs “cold start” data. |
| 2071 |
Media gateway attempted to register with a different serial number. |
| 2072 |
Conference or transfer 2 Meet-me conference call. |
| 2073 |
User attempted to download firmware to a station. User does not have console permission. |
| 2074 |
Attempt to record an announcement while that announcement is playing. |
| 2075 |
User does not have console permissions |
| 2076 |
IP Registration Rejection (RRJ) because of no call present on the switch side. But there is a call present on the ept. |
| 2077 |
Force Unregistration Request. Unregister endpoint whose call preservation timer (H323 link loss delay timer) expires. |
| 2078 |
OPTIM Extend Call via extend call button press was denied. |
| 2079 |
Registration rejected because set in wrong state (for example on call, Out of Service (OOS)). |
| 2081 |
IP Softphone in shared control configuration with DCP is forced unregistered because softphone switched to invalid state. |
| 2082 |
A TLS socket was rejected because of the constraint on the maximum number of TLS peers. |
| 2073 |
A peer cert was rejected by common name checking. |
| 2084 |
Handshake failed, for example due to no common cipher suite. |
| 2085 |
An expired certificate was returned and rejected. |
| 2088 |
Bad Record Max. For example, an attacker does not have the correct private key, which can go undetected until the MAC of the exchange is checked. |
| 2089 |
Bad Record Max. For example, an attacker does not have the correct private key, which can go undetected until the MAC of the exchange is checked. |
| 2090 |
TLS shutdown received. Listen socket could not be created. |
| 2092 |
Post message invalid Station Security Code (SSC). |
| 2093 |
Cannot start announcement. |
| 2094 |
Establish a socket on an IP trunk. The far end might be mis-administered |
No Comments