Change HTTP connection page field descriptions

Use this page to change the configuration of an HTTP connection.

Field or Button

Description

Zone

Select the name of the zone from the drop-down box.

Note:

The Zone drop-down box appears only when you create new zones. If you do not create any new zones, you do not see the drop-down box.

Changing Zone from the default zone to any other zone is not allowed. However, you may change the zone for connections for which the existing zone is not the default zone.

Name

The name of the HTTP connection.

	Note:
	This name cannot be modified

Enable

The options are:

Transport Protocol

The protocol used to send request to SMSC. Select the transport protocol from the drop-down list box. The options are:

	Note:
	For Avaya OneCloud CPaaS and AT&T Landline Texting connectors, select TLS.

Host Address

The IP address of the service provider or the Short Message Service Center (SMSC) server.

Enter the host address of the service provider.

	Note:
	For Avaya OneCloud CPaaS connector, the host address is https://%3Cregion%3E.cpaas.avayacloud.com/v2/accounts/overview.

Port

Enter the port number to be used for the connection.

Path

Enter the path of the URL to be used for communicating with the SMSC. The default is “ ”.

This is the portion of the URL which is after the host address and the port.

As an example if the URL is http://hostaddress:port/location, enter location here.

User Name

Enter the user name.

Note:

For Avaya OneCloud CPaaS connector, the user name is the Account SID on the OneCloud CPaaS Dashboard at https://%3Cregion%3E.cpaas.avayacloud.com/v2/accounts/overview.

This Account SID should only be used in one active connection. This means that you need to use only one EPM connection if multiple Avaya OneCloud CPaaS short codes or long numbers are associated with the same Account SID.

Password

The password for the user supplied by the service provider.

Enter the password.

	Note:
	For Avaya OneCloud CPaaS connector, the password is the Auth Token on the OneCloud CPaaS Dashboard at https://%3Cregion%3E.cpaas.avayacloud.com/v2/accounts/overview.

API ID

The user identifier supplied by the service provider.

Enter the Application Programming Interface (API) ID.

Note:

For Avaya OneCloud CPaaS connector, do not enter any value in the API ID field.

If you plan to share the same Account SID across multiple EP systems, then enter the API ID. To share the Account SID, enter a unique number as the API ID for each EP system. This unique API ID should be appended to the SMS Request URL that is configured at https://%3Cregion%3E.cpaas.avayacloud.com/v2/accounts/overview.

For example, if you enter 1 as the API ID for EP system 1, and 2 as the API ID for EP system 2, the SMS Request URL for an SMS number managed by EP system 1 would be: https://%3Cregion%3E.cpaas.avayacloud.com/v2/accounts/overview , and the SMS Request URL for an SMS number managed by EP system 2 would be: https://%3Cregion%3E.cpaas.avayacloud.com/v2/accounts/overview.

Connector

The HTTP mechanism supported through a connector.

The options are:

Avaya OneCloud CPaaS
AT&T Landline Texting
AOS SMS
Clickatell
i2SMS
ONE WAY SMS
WEBTEXT
Zipwhip

Note:

For AT&T Landline Texting and Zipwhip, the customer must obtain a Session Key from the Sales or Support team. The Session Key is specific to each SMS-enabled phone number, so one SMS connection is required on the EPM for each phone number.

The Session Key contains a : character. The characters to the left of the : character should be entered into the Username field of an EPM SMS Connection and the characters to the right should be entered into the Password field.

For example, a typical Session Key (obtained from AT&T Landline Texting or Zipwhip) looks like the following:

3d0f1dde-aaff-4ce8-b61a-af212a860abc:123456789

Where,

3d0f1dde-aaff-4ce8-b61a-af212a860abc is the Username.
123456789 is the Password.

Type

An HTTP Connector can be of two types. The options are:

Outgoing: The Outgoing connector is used for sending out SMS messages only. It is assigned to all SMS processors in the same zone.

Incoming and Outgoing: The Incoming and Outgoing connector is used for processing incoming SMS messages and also for sending out SMS messages. It needs to be assigned to a specific SMS processor.

	Note:
	This option is only available for connectors that support both incoming and outgoing SMS messages. By default, an HTTP connector can only be used for processing outgoing messages.

Note:

For Avaya OneCloud CPaaS connections, if you select Incoming and Outgoing to respond to incoming SMS messages, you must configure the SMS Request URL at https://<region>.cpaas.avayacloud.com/v2/accounts/overview to forward incoming SMS messages to the {}pubsub-<region>.cpaas.avayacloud.com{} server.

You can select the region based on the current location.

You need to log in to your https://%3Cregion%3E.cpaas.avayacloud.com/v2/accounts/overview account, click Numbers on the top of the OneCloud CPaaS dashboard, select Manage Numbers, and then click the purchased SMS telephone number.

For example,

https://us.cpaas.avayacloud.com/v2/accounts/overview

To support incoming MMS, use the same URL in the MMS Request URL field on the MMS tab for the OneCloud CPaaS SMS/MMS telephone number.

Note:

From Experience Portal 7.2.1, Avaya OneCloud CPaaS connections must be configured to use https. You may need to install the Baltimore CyberTrust Root certificate if the connections fail to connect with an SSL error.

You can download the certificate from https://www.digicert.com/CACerts/BaltimoreCyberTrustRoot.crt. To import the certificate, on the EPM web page, click Security > Certificates, and the click Import on the Trusted Certificates tab. Restart the EPM from the EPM Manager.

Use HTTP Proxy

The proxy setup to be used while sending the HTTP(s) request. Comma-separated values comprising of proxy protocol, proxy server, and proxy port.

The options are:

Proxy server

The proxy setup to be used while sending the HTTP(s) request. Comma-separated values comprising of proxy protocol, proxy server, and proxy port.

Enter the name of the proxy server.

Proxy Port

The proxy setup to be used while sending the HTTP(s) request. Comma-separated values comprising of proxy protocol, proxy server, and proxy port.

Enter the port number of the proxy server.

Short Code/Long Number

Organization

Enter the short code or the long number provided by the SMSC. Use the Additional Entry link to specify additional short codes or long numbers.

Select the relevant organization from the multi-select drop-down list. The options are:

<All> : All organizations can use this short code. If the administrator selects multiple options in the drop-down list, only <All> is saved.
<None>: None of the organizations can use this short code. The administrator can select other organizations in addition to <None>.
The other organizations that are enabled in the system.