Lack Of Connection Routing For Active/Active Georedundant Installations
(Doc ID 1088037.1)
Last updated on FEBRUARY 19, 2019
Applies to:Oracle Communications Services Gatekeeper - Version 4.1.1 and later
Information in this document applies to any platform.
Customers need a way to route Mobile Originated (MO) SMPP messages and Delivery reports in a connection oriented fashion instead of using the Message ID.
This is the mechanism:
On each member of a cluster a native SMPP plugin is installed for each application served by that cluster.
Each plugin binds to two or more SMSCs.
In a geo-redundant installation, the two clusters (S1 and S2) are configured in the same way (one plugin per application per server).
Mobile Terminated (MT) messages are handled as usual; the application may choose to send a message to S1 or S2. Delivery Reports (DR) and MO messages are received by any member of S1 or S2. In particular, if an application submits a message through S1, OCSG must be prepared to receive its DR at S2.
When a plugin receives a MO or a DR, it will route that message to the application it is associated to (rather that using filters or correlating through the Message-ID, in case of DRs).
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document