Binary SMS UDHI is always set in submit_sm
(Doc ID 2534311.1)
Last updated on OCTOBER 17, 2019
Applies to:Oracle Communications Services Gatekeeper - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.0.0]
Information in this document applies to any platform.
On OCSG 7.0 when sending binary SMS, in submit_sm, message is being fragmented even though useMessagePayload is set to false.
UDHI is being set in the message, causing the message fragmentation resulting in a 140 byte payload being split into one 134 byte packet and another 6 byte packet. Each are being encapsulated in 2 separate submit_sm messages. This breaks carrier's 1 TPS SLA, as well as increases SMS cost.
It's required messages within the standard supported payload size to be delivered in a single submit_sm. For this, UDHI should be set to 00 but cannot locate configuration other than useMessagePayload to drive this setting. This is causing double cost for SMS and there is severe financial impact. Previous OCSG version 18.104.22.168 did not function this way.
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