This guide will provide step by step instructions for configuring CafeX interoperability with Avaya Systems Manager.
Supported Avaya Components
The Avaya interop and versions we have formally tested against are:
- Avaya Aura® Platform v6.2 FP4 is supported
- Avaya one-X® Agent (H.323) 2.5.5 Patch 1
- Avaya Media Client 1.0
Other Avaya components such as Avaya Voice Portal IVR are not required.
- The FCSDK Client is authenticated using the authentication application which generates a session token from the Web Gateway.
- The FCSDK client uses the Session token to connect to the Web Gateway via the Reverse Proxy.
- The Web Gateway connects to the Media Broker and creates the SIP offer
- The Web Gateway passes the SIP offer to the Avaya Aura Systems Manager which is routes it to the SIP Endpoint.
- SIP Endpoint receives the offer and provides a response. (H.323 is based on use of the Avaya one-X Agent Endpoint. Alternative endpoints may differ.)
- The SIP answer is passed back to the Media Broker which negotiates an RTP stream for the SIP Endpoint.
- Media Broker passes a SIP response to the FCSDK Client via the Web gateway.
- The FCSDK examines the SIP message which contains connection details for RTP/SRTP
- FCSDK Client sends RTP to the external Media Broker Address on the firewall.
- RTP is sent on from the Media Broker to the SIP Endpoint.
System Manager Configuration
Configuring the Avaya System Manager to work with FAS and FCSDK involves several steps:
- Add the Web Gateway as a SIP Entity linked to the Session Manager and/or Security Module (Depending on requirements).
- Create the Session Manager and/or Security Module's node name
- Create the Signaling Group's far-end node name and domain
- Create Network Region and trunk details (if required)
- Create Endpoint configuration and Ports
- Enable outbound SIP servers in the Web Gateway.
Navigate to the Avaya Aura System Manager Web UI. Go to Routing
Go to SIP Entities and click New
Enter details for your Web Gateway, the Type must be set as Other e.g.
Scroll down to Entity Links and click Add
Enter details to link your Gateway to the appropriate interface. Depending on your configuration you may need two connections:
- Sip Entity 1 Session Manager, TCP, 5060. SIP entity Two Gateway, 5060, TCP. Trusted
- Sip Entity 1 Security Module TLS 5061. SIP Entity Two: Gateway, 5061 and TLS. Trusted.
Configure the Session Manager / Secure Module IP in current Node Names.
Configure the Signaling Group's Far-end Node Name (as Session Manager or Security Module Node Name), Near End Node Name (Processor Ethernet Interface) and Far End Domain (SIP Domain).
Add an IP Network Region for the SIP Domain, enable IP-IP Direct Audio and disable IP Audio Hairpinning.
Create a SIP Trunk between the SM and the signaling group.
Go to Manage endpoints:
Enable IP Video Softphone and Direct IP-IP Audio Connections for each agent softphone endpoint to be used.
Ensure adequate port availability for softphones
Web Gateway Configuration
The Web gateway will need to have it's Outbound SIP Server configured to point at the Security Module of your Avaya Aura system. e.g.