$G Is Present In The Failed Mapping Table Entry

(Doc ID 2407653.1)

Last updated on JUNE 12, 2018

Applies to:

Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.


While testing a configuration change on a development system, the following scenario was noticed:

When a recipient is found in the 'general.txt' file, the mapping successfully adds the desired conversion tag and everything works the way it is expected.

However, the slave-debug logs show that when the user is not in the 'general.txt' file, the source channel name gets added as a conversion tag while it shouldn't.

Example from the tcp_local_slave.log-nnnnn:

As expected, "visexempt|dummytestuser@otherdomain.com" did not exist in the 'general.txt', and so the ${ } lookup failed.

But why did it add conversion tag "tcp_scanner"?




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