My Oracle Support Banner

Message Manager Does Not Send SMPP Unbind to SMSC During Shutdown/Restart (Doc ID 1923999.1)

Last updated on AUGUST 19, 2019

Applies to:

Oracle Communications Network Charging and Control - Version 5.0.0 and later
Oracle Solaris on SPARC (64-bit)


In all version of Network Charging and Control (NCC) Messaging Manager (MM), up to and including, a problem exists where MM does not explicitly send a Short Message Peer to Peer (SMPP) UNBIND message to Short Message Service Centres (SMSC) when shutting down or restarting.

As per the SMPP v5.0 specification, an SMPP UNBIND is described as:

The purpose of the SMPP unbind operation is to deregister an instance of an ESME from the MC and inform the MC that the ESME no longer wishes to use this network connection for the submission or delivery of messages.

This may lead to potentially hung/stuck resources on the SMSC that may require manual intervention to clear.

Some SMSCs are not affected by this lack of explicit deregistration, as typically they can interpret a TCP FIN, from the Service Logic Controller (SLC), as a termination of the connection between the two network nodes.


Adding a pre-open SMSC to MM's configuration to submit short messages to.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.