www.nordicmessaging.se

EMG 5.3.2 - User's Guide

Table of ContentsPreviousNextIndex

15. Proxy mode

EMG 5.2 introduced the possibility to use EMG in proxy mode when using UCP ESMEs toward one or more SMPP SMSC.

Proxy mode cannot currently be used with any other protocols than UCP and SMPP.

15.1 Overview

The default behavior of EMG is to receive a message, acknowledge it to the client, and then route and forward it. That is, the client receives the response before the message is forwarded and therefore whether the message could be forwarded is not known. Usually the final status of a message is reported back by requesting a delivery report.

In proxy mode an outgoing SMPP connector will follow the state of an incoming UCP connector (session tracking). When a client connects via UCP the UCP instance allocated will be mapped to a corresponding SMPP instance.

15.2 Scenarios

15.2.1 Normal mode

The diagram below shows how EMG handles submit operations in normal mode.

15.3 Proxy mode

The diagram below shows how EMG handles submit operations in proxy mode.

123

15.4 Configuration

In order to enable proxy mode you simply add the connector keyword "PROXY" to the incoming UCP connector. The keyword must specify the SMPP connector(s) that will be used in proxy mode.

Connectors used in proxy mode should not be defined as static connectors as that will break the session tracking. The number of instances on the SMPP connector must not be less than the number of instances on the UCP connector.

15.4.1 One-to-one mapping

CONNECTOR ucp-in1 <
...
TYPE=INCOMING
INSTANCES=5
PROXY=smpp-out1
...
>

CONNECTOR smpp-out1 <
...
TYPE=OUTGOING
INSTANCES=5
...
>

15.4.2 One-to-many mapping (fail-over)

CONNECTOR ucp-in1 <
...
INSTANCES=10
PROXY=smpp-out1,smpp-out2
...
>

CONNECTOR smpp-out1 <
...
TYPE=OUTGOING
INSTANCES=10
...
>

CONNECTOR smpp-out2 <
...
TYPE=OUTGOING
INSTANCES=10
...
>

15.4.3 One-to-many mapping (load balancing)

CONNECTOR ucp-in1 <
...
PROXY=smpp-out1,smpp-out2/LB
...
>

Table of ContentsPreviousNextIndex