Network Loops with Home Routed MAP MtFwSM
(Doc ID 2551621.1)
Last updated on OCTOBER 09, 2019
Applies to:Oracle Communications Network Charging and Control - Version 6.0.1 and later
Oracle Communications Convergent Charging Controller - Version 6.0.1 and later
Information in this document applies to any platform.
In Oracle Communications Network Charging and Control (NCC) version 6.0.1, Messaging Manager (MM) is a messaging system for mobile networks. It acts as a Virtual Message Point (VMP) for a variety of different messaging traffic (for example: Session Initiation Protocol (SIP), Email, and Short Message Service).
MM integrates advanced routing and protocol delivery options with extended service control, in order to support all forms of traditional Mobile Originating (MO) SMS and Mobile Terminating (MT) SMS services while retaining flexible support for new types of messaging.
In the current issue, several network loops were encountered with home-routed Mobile Application Part (MAP) MT Forward SMS' (MtFwdSM). From the snoop traces it appears that MM has placed its own Global Title (GT) address in Signalling Connection Control Part (SCCP) Called Party Address (CdPA) when relaying it back to network.
Scenario looks like this:
1. MM receives MtFwdSM (containing delivery report).
2. MM tries to find the routing information from Messaging Manager Navigator (RIMS) cache.
3. RIMS cache returns the information.
4. MM is building MtFwdSM toward Mobile Switching Center (MSC) and here the GT is getting set as Service Logic Controller GT (SLC GT) and not the Virtual MSC (VMSC) address which is returned by RIMS.
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