Overview: IP Endpoint registration and subscription (Console)
Console > Account > IP Endpoints > Overview: IP Endpoint registration and subscription Console)
In Console, the Endpoint Registration and Endpoint Subscription containers at the top of every IP Endpoint configuration page show the current registration and subscription status of the IP Endpoint.
Note that these containers are primarily informational; they’re not used for configuring the endpoints. They’re used for showing information about how the endpoint is registered and who is subscribed to the endpoint.
Endpoint registration
You can view the current registration and subscription status of an IP Endpoint at the top of the endpoint’s configuration page.
In Avaya.cx, endpoint registration represents a connection between a physical endpoint (like a desk phone) and the Avaya.cx SIP server (Session Initiation Protocol), also known as a SIP proxy.
In other words, an endpoint registration allows the Avaya.cx system to recognize and manage a physical IP endpoint, including making, receiving, and ending phone calls.
Once registered, the IP endpoint communicates with Avaya via the Avaya.cx SIP server. The Avaya.cx SIP server manages all of the inbound and outbound calls for the IP endpoint.
The IP Endpoints workspace in Console displays certain pieces of information related to the registration in the Endpoint Registration container, including:
ID: The unique identifier of the endpoint registration
Proxy: The IP address of the SIP server the endpoint is registered to.
Transport: Specifies what security protocol is being used for the connection to the IP Endpoint. This value is either:
ws (Web Socket)
tls (Transport Layer Security)
User Agent: The identity of the IP endpoint as registered with the SIP server.
In short, endpoint registration allows you to connect an IP endpoint with the Avaya.cx network, seamlessly integrating your device with Avaya.
Endpoint subscription
An endpoint subscription is a relationship between a registered IP endpoint and Avaya.cx via the SIP proxy (described in the section above).
There can be multiple subscriptions on a single endpoint. This is accomplished with line groups, where multiple physical endpoints are grouped together on the same line. This container can be used to see which users are subscribed to a particular endpoint.
The IP Endpoints workspace in Console displays certain pieces of information related to the subscription in the Endpoint Subscription container, including:
ID: The unique identifier of the endpoint subscription
User Agent: The identity of the IP endpoint as registered with the SIP server.
Type: The type of subscription.
This is usually “message-summary”, which means that the endpoint is requesting from the SIP proxy authentication.
The Avaya.cx SIP proxy sets an expiration date (a week from the initial subscription) for the endpoint (described in the Expires Date UTC column)
When the subscription expires, the endpoint sends another subscription request to the SIP proxy to revalidate.
Resource: The unique identifier of the user associated with the endpoint.