Avaya H.323 Endpoint Registration
The 3 steps to consider and understand.
In this post, “Avaya H.323 Endpoint Registration”, see which mechanisms are responsible for allowing the registration process of the H.323 Endpoints, how network elements work in conjunction with the Avaya Core servers providing the necessary services, and components to maintain each device connected, updated, and registered to its gatekeeper.
Recently, I was assisting a customer troubleshoot H.323 registration problems with a group of IP Phones, where the servers were failing to complete sending the last registration message. Learn how issues like this one can be solved by following these three steps=
- 1.- Network considerations
- 2.- Networking Services
- 3.- Registration Process
1.- Network Considerations
Once the Voice Topology has been designed on both Avaya Core Servers and Network elements, the next step is setting up the DHCP Scopes, setup the HTTPs servers delivering the Firmware and phone setup files.
HQ or Remote/Local – H.323 Endpoints can obtain their registration from a Local Survivable Gateway, where they can use limited resources until the WAN link to the Core gets established.
Survivable GK Node Name – It is used to allow H.323 Endpoints to follow the specify Media Gateway as the primary registration point if the WAN is broken.
2.- Networking Services
Endpoints, like any other network component require services and protocols that allow VoIP to coexist over the Data network sharing similar hardware. UDP is the primary protocol suite used, and TCP mostly used for signaling and Call-Setup messages.
3.- Registration Process
When endpoint first boots up and goes through its VLAN and Firmware verification, sending a GRQ (Gatekeeper Request) message to its registration/Call Server, the server will reply with GCF (Gatekeeper Confirm) message telling the phone it has received the first request.
Registration Request – After the Gatekeeper has established communication with the endpoint, the registration process starts when the Call Server receives an RRQ (Registration Request) from the endpoint, the server will send a final RCF (Registration Confirm) message back to the endpoint to complete its registration.
Other registration messages and Denial Events – For those registered endpoints that will send duplicated RRQ, the system sends a UCF (Unregistration Request) message to that particular endpoint prior to start the registration process all over again.
Denial Event (DE) 2011 – This message is generated when the endpoint fails to receive the RCF message and instead it receives a IP-FURQ (IP Forced Unregistration Request) to terminate the session. This is followed by signaling SETUP messages the endpoint failed to send to the registration server (Q.931). Avaya has some KBs that recommends turning on/off the “Near-End TCP Signaling Socket” in the third page of the Network Region, where these services are provided from.
DE 1934: IP RRJ-Ext already reg – This denial event is produced when the Call Server sends a RRJ (Registration Rejected) message to the endpoint. Resetting the IP Port Station Assignment is the best way to solve this issue.
Bad registration
14:50:06 rcv GRQ ext 132154
endpt [172.1.1.101]:49301
switch [172.1.2.5]:1719
14:50:06 snd GCF ext 132154
endpt [172.1.1.101]:49301
switch [172.1.2.5]:1719
14:50:07 rcv RRQ ext 132154
endpt [172.1.1.101]:49301
switch [172.1.2.5]:1719
14:50:07 denial event 1926: IP RRJ-Authenticatn fail (User entered wrong password)
endpt 172.1.1.101 data0:0x85c7
14:50:07 snd RRJ ext 132154
========
Good Registration
=======
14:50:16 rcv GRQ ext 132154
endpt [172.1.1.101]:49302
switch [172.1.2.5]:1719
14:50:16 snd GCF ext 132154
endpt [172.1.1.101]:49302
switch [172.1.2.5]:1719
14:50:16 rcv RRQ ext 132154
endpt [172.1.1.101]:49302
switch [172.1.2.5]:1719
14:50:16 snd RCF ext 132154
endpt [172.1.1.101]:49302
switch [172.1.2.5]:1719
14:50:16 endpt MAC addr: 2C:F4:B0:55:2E:05 Ver 0.
Question – When deploying H.323 Endpoints, what type of issues have you encountered?
Other references
Please note: I reserve the right to delete comments that are offensive or off-topic.