OCSG Doesn't Consistently Validate AddressRange In NativeSMPP Transceiver And Receiver Bind Requests
Last updated on DECEMBER 20, 2017
Applies to:Oracle Communications Services Gatekeeper - Version 5.1.0 to 5.1.0 [Release 5.1]
Information in this document applies to any platform.
According to Oracle online documentation (http://docs.oracle.com/cd/E36135_01/doc.51/e37542/app_native.htm#autoId11) OCSG should check the address_range for both Transceiver and Receiver bind requests from an application, but this is not consistently validated by OCSG.
Setup the applicationSpecificSettings as follows, refer to http://docs.oracle.com/cd/E36135_01/doc.51/e37526/com_native_smpp.htm#autoId53 for more information:
Similar behaviour is observed with Transceiver bind.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms