This chapter provides instructions on how to install and configure the HTTP Service
Provider connection for SMS messaging using the Ozeki NG SMS Gateway software.
Install and configure the HTTP Service Provider
The HTTP Service Provider is a template-based provider, which lets you to
send and receive HTTP Requests and delivery reports based on the schema that you
provide. You need to provide us a detailed description about your requests and
our developers will develop it based on your provided schema.
You can install and configure the HTTP Service Provider connection using
the graphical user interface of Ozeki NG SMS Gateway. To start installing and
configuring an HTTP Service Provider connection, click the Add button in the top
right-hand corner of the Service provider's panel on the Management page of the
Figure 1 - Add Service Provider connection
On the following page you can find the HTTP Service Provider connection.
Click on the Install button to create the new connection.
Figure 2 - Install HTTP Service Provider connection
On the configuration form of the service provider connection there are 4 tabs,
where you can configure the connection.
Under General tab, you need to specify the connection parameters for message
submission. These parameters have to be in the Post URL textbox that is provided
by your service provider.
In the textbox of Listen URL you need to write the IP address of your Ozeki NG -
SMS Gateway on which the Gateway will be listening for incoming SMS messages.
In the Template box you need the select the template, which has been created based
on your provided schema.
In the Encoding textbox you can specify the encoding options with the following
settings: If you check the "Use URL encoding in outgoing messages" checkbox your
outgoing messages will be URL encoded. The incoming messages will be URL decoded
if you check the"Use URL decoding in incoming messages"
Figure 3 - General settings of the HTTP Service Provider connection
In the Connection tab of the configuration form you can fill the form for
HTTP authentication. Client certificatecan also be set for HTTPS authentication.
Figure 4 - Connection tab of the HTTP Service Provider connection
In the Advanced tab you can specify which content types will be used for
outgoing requests and outgoing responses. In the Timeout box you can give the
timeout which will be used at sending and receiving HTTP requests. In the Additional
Headers textbox you can add additional header values seperated by semicolons.
Figure 5 - Advanced tab of the HTTP Service Provider connection
In the Logging tab you can choose whether to make the program write log
entries about sent and received messages in human readable format and/or log low
level communication. Choosing the second option the program produce logfiles
containing binary codes representing the communication data.
In the Log file settings section of the tab, you can give the Log directory, the
maximum log file size and the number of rotated logfiles. Log rotation saves disk
space, as it ensures that older logfiles will be automatically deleted from the
log directory. In the Maximum log file size text box you can specify the maximum
size of a logfile. Once this size is reached, a new logfile will be created.