OCSG Does Not Filter On Address Range For Native SMPP Connected CP Receiving MO Messages
(Doc ID 1966422.1)
Last updated on AUGUST 24, 2020
Applies to:Oracle Communications Services Gatekeeper - Version 5.1.0 and later
Information in this document applies to any platform.
When native SMPP is configured with a few different Application instances with different address ranges, the first Connection Point (CP) that establishes a BIND to OCSG will receive all the MOs independent on the address in the SMS.
E.g. Application instance SMPPuser1 using address range 5205 and Application instance SMPPuser2 using address range 5301.
If SMPPuser1 establishes a BIND first and SMPPuser2 establishes a bind second, then all future MO SMS' will go the SMPPuser1 independent of the address specified in the SMS (either 5205 or 5301).
The SMSC knows that both SMPPuser1 and SMPPuser2 are associated with OCSG. Why does it happen?
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