XmsiMap Fails To Copy the VMSC Address
Last updated on OCTOBER 18, 2016
Applies to:Oracle Communications Network Charging and Control - Version 4.4.0 and later
Information in this document applies to any platform.
xmsiMap does not copy the VMSC address from the SCCP originating address.
When xmsTrigger receives an MO Forward SM, it sends the update to RIMS Cache with the VMSC address missing.
This can be witnessed in the xmsTrigger debug log:
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