Use the following procedure to create a subscriber flow. The procedure is explained by using Subscriber_Flow_1 as a sample.
Procedure
Log in to the EMS web interface with administrator credentials.
From the Device menu, click the SBC name to administer.
Navigate to Network & Flows > End Point Flows.
The EMS server displays the End Point Flows page.
In the Subscriber Flows tab, click Add.
The EMS server displays the Add Flow window.
Create a User Agent.
In the Flow Name field, type Subscriber_Flow_1.
Unless the customer has special requirements, use the default values for the URI Group, User Agent, Source Subnet, Via Host, and Contact Host options.
In the Signaling Interface field, select the external interface towards the endpoint.
Click Next.
The system displays the second Add Flow window.
Set the Source option to Subscriber.
Do not administer the Methods Allowed before REGISTER option.
In the Media Interface field, select the corresponding media interface towards the endpoint.
In the Secondary Media Interface field, select None.
In the End Point Policy Group field, select the endpoint policy created earlier.
Note:
If RTP is needed use default low or avaya-def-low-encoding (for SRTP) depending on the endpoints.
In the Routing Profile field, click the name of the routing profile that points toward the Avaya call server.
Select FQDN Support checkbox to use the FQDN for SBC address instead of IP address for headers added by SBC. By default FQDN support is disabled.
If checkbox is not selected, SBC adds IP address in message
If checkbox is selected, SBC adds FQDN value to message instead of IP.
In the FQDN field, type a FQDN value. FQDN field is applicable only when FQDN support is enabled.
If you require TLS transport, select the desired TLS profile in the TLS Client Profile field.
In the Presence Server Address field, enter the Presence server IP address or FQDN.
Avaya SBC does not rewrite the Presence Subscription URI if Remote Workers use FQDN instead of the external Avaya SBC IP address in the Presence Server Address field. This change is required to support the endpoints that implement Presence Services Communication Profile, such as Avaya Workplace Client 3.0. For these endpoints, Request-URI of a presence SUBSCRIBE request is in the form user@domain.com and must not be changed by the Subscriber Flow. This change permits the concurrent deployment of older and new endpoints in the same solution. Presence service to the Remote Workers does not work if the private FQDN used to reach Avaya SBC is not resolvable in the enterprise network.
Optional If you type an FQDN instead of an IP address in the Presence Server Address field, do one of the following:
Configure Split DNS to ensure that the private FQDN can be resolved within the enterprise network.
Create a Regular Expression in Session Manager for Presence, and use the Regular Expression in the Routing Policy for the Presence Server.
This step is relevant only to older endpoints that are administered with an FQDN for Presence Services address. This step is not required for Avaya Workplace Client 3.0.
In the IP / URI Blocklist Profile field, select desired profile.
In the Trusted Address field, enter the trusted server IP address.
The trusted IP address identified by the Admin are not blocked.
