XMS Transcoding is Using a Different Alphabet Than the One Configured at the Adapter Level (Doc ID 2228579.1)

Last updated on FEBRUARY 01, 2017

Applies to:

Oracle Communications Network Charging and Control - Version 6.0.0 and later
Information in this document applies to any platform.

Symptoms

We have the following scenario: An SMS-MO is coming in through MAP interface, using the GSM7bit coding alphabet, and triggers a control plan; based on the destination, it will select a different SMPP route.

In the xmsTrigger.conf the following configuration is defined for the outbound adapter:

 

Changes

 

Cause

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