SMSC – Advanced Settings SS7

SS7 Settings

SMSC Global Title

Using CLI

You can set the ‘SMSC Gobal Title’ by issuing the command smsc set scgt with appropriate parameters as described below. You can verify this by issuing the command smsc get scgt which will display the value set for this property.

Name
        smsc set scgt

SYNOPSIS
        smsc set scgt &lt;globalTitle&gt;

DESCRIPTION
        This command is used to set a value for SMSC Global Title.

Using GUI

Procedure 6.12. Set SMSC Global Title using the GUI

In the GUI Management Console for SMSC Gateway, click on ‘Server Settings’ in the left panel.
The main panel will display the existing Settings, segregated into four horizontal tabs: Properties, SS7 Settings, Cassandra and Scheduler. Switch to the ‘SS7 Settings’ tab in the GUI.
You can specify the SMSC Global Title by entering the value in the text field ‘SMSC Gateway Global Title’. For more details of this parameter, please refer to the description of the CLI command for the same in the preceding section.
You must click on the button ‘Apply Changes’ at the top of the window to save your settings. If there is an error in setting the value, then you will find the details of the error in the Management Console Log section below.

SMSC Sub System Number (SSN)

Using CLI

You can set the ‘SMSC SSN’ by issuing the command smsc set scssn with appropriate parameters as described below. You can verify this by issuing the command smsc get scssn which will display the value set for this property.

Name
        smsc set scssn

SYNOPSIS
        smsc set scssn &lt;smscSubSystemNumber&gt;

DESCRIPTION
        This command is used to set the value of SMSC Sub System Number (SSN). Issuing 
        this command in CLI will set the SSN value but you must ensure that the SSN number
        is properly configured in the TCAP Stack in the xml descriptor file
        "telscale-smscgateway-version/jboss-5.1.0.GA/server/default/deploy/
        telscale-smsc-server/META-INF/jboss-beans.xml".

Using GUI

Set SMSC Sub System Number (SSN) using the GUI

In the GUI Management Console for SMSC Gateway, click on ‘Server Settings’ in the left panel.
The main panel will display the existing Settings, segregated into four horizontal tabs: Properties, SS7 Settings, Cassandra and Scheduler. Switch to the ‘SS7 Settings’ tab in the GUI.
You can specify the SMSC Sub System Number (SSN) by entering the value in the text field ‘SMSC Gateway subsystem number’. For more details of this parameter, please refer to the description of the CLI command for the same in the preceding section.
You must click on the button ‘Apply Changes’ at the top of the window to save your settings. If there is an error in setting the value, then you will find the details of the error in the Management Console Log section below.

HLR Sub System Number (HLR SSN)

Using CLI

You can set the ‘HLR SSN’ by issuing the command smsc set hlrssn with appropriate parameters as described below. You can verify this by issuing the command smsc get hlrssn which will display the value set for this property.

Name
        smsc set hlrssn

SYNOPSIS
        smsc set hlrssn &lt;hlrSubSystemNumber&gt;

DESCRIPTION
        This command is used to set the value of HLR Sub System Number (SSN).

Using GUI

Set HLR Sub System Number (SSN) using the GUI

In the GUI Management Console for SMSC Gateway, click on ‘Server Settings’ in the left panel.
The main panel will display the existing Settings, segregated into four horizontal tabs: Properties, SS7 Settings, Cassandra and Scheduler. Switch to the ‘SS7 Settings’ tab in the GUI.
You can specify the HLR Sub System Number (SSN) by entering the value in the text field ‘HLR subsystem number’. For more details of this parameter, please refer to the description of the CLI command for the same in the preceding section.
You must click on the button ‘Apply Changes’ at the top of the window to save your settings. If there is an error in setting the value, then you will find the details of the error in the Management Console Log section below.

MSC Sub System Number (SSN)

Using CLI

You can set the ‘MSC SSN’ by issuing the command smsc set mscssn with appropriate parameters as described below. You can verify this by issuing the command smsc get mscssn which will display the value set for this property.

Name
        smsc set mscssn

SYNOPSIS
        smsc set mscssn &lt;mscSubSystemNumber&gt;

DESCRIPTION
        This command is used to set the value of MSC Sub System Number (SSN).

Using GUI

Set MSC Sub System Number (SSN) using the GUI

In the GUI Management Console for SMSC Gateway, click on ‘Server Settings’ in the left panel.
The main panel will display the existing Settings, segregated into four horizontal tabs: Properties, SS7 Settings, Cassandra and Scheduler. Switch to the ‘SS7 Settings’ tab in the GUI.
You can specify the MSC Sub System Number (SSN) by entering the value in the text field ‘MSC subsystem number’. For more details of this parameter, please refer to the description of the CLI command for the same in the preceding section.
You must click on the button ‘Apply Changes’ at the top of the window to save your settings. If there is an error in setting the value, then you will find the details of the error in the Management Console Log section below.

MAP Application Context version

Using CLI

You can set the ‘MAP Application Context version’ by issuing the command smsc set maxmapv with appropriate parameters as described below. You can verify this by issuing the command smsc get maxmapv which will display the value set for this property.

Name
        smsc set maxmapv

SYNOPSIS
        smsc set maxmapv &lt;version-number&gt;

DESCRIPTION
        This command is used to set the value of MAP Application Context version. The
        version number set here will be used for SMS messages exchanged. Telscale SMSC
        Gateway supports version negotiation. So if you set this to a higher version (say
        for example version 3, however your network only understands version 2), the SMSC Gateway
        will automatically do the version negotiation and exchange V2 messages when V3
        exchange fails. However this causes additional messages to be exchanged and
        increases the overall load on the system. Therefore it is advisable to always set
        the correct version.

Using GUI

Set MAP Application Context version using the GUI

In the GUI Management Console for SMSC Gateway, click on ‘Server Settings’ in the left panel.
The main panel will display the existing Settings, segregated into four horizontal tabs: Properties, SS7 Settings, Cassandra and Scheduler. Switch to the ‘SS7 Settings’ tab in the GUI.
You can specify the MAP Application Context version by entering the value in the text field ‘MAP version supported’. For more details of this parameter, please refer to the description of the CLI command for the same in the preceding section.
You must click on the button ‘Apply Changes’ at the top of the window to save your settings. If there is an error in setting the value, then you will find the details of the error in the Management Console Log section below.

MAP Version Cache

TelScale SMSC Gateway caches the negotiated MAP Version for each network node. Cache stores the Global Title of SCCP address of the network node. Every MT SMS sent to this node will use the cached Version. This will help in reducing the MAP Version negotiation duration everytime and hence improve the performance.

Using CLI

You can set the ‘MAP Version Cache’ value by issuing the command smsc mapcache set with appropriate parameters as described below. You can verify this by issuing the command smsc mapcache get which will display all the cached values. Alternatively you can retrieve the cached value for a specific node by issuing the command smsc mapcache get <node_digits>. You can clear the cache by issuing the command smsc mapcache clear.

Name
	smsc mapcache set

SYNOPSIS
	smsc mapcache set &lt;node_digits&gt; &lt;version&gt;

DESCRIPTION
	This command is used to set the version for the specific node digits. SMSC Gateway
	caches the negotiated MAP Version for each network node. Every MT SMS sent to this
	node will use the cached Version.

Using GUI

Procedure 6.17. Managing MAP Version Cache value using the GUI

In the GUI Management Console for SMSC Gateway, click on ‘MAP Version Cache’ in the left panel.
You can specify the MAP Application Context version for every node by entering the value for Node Digits and choosing the Version for MAP MtForwardSm operation.
You must click on the button ‘Update’ to save your settings. If there is an error in setting the value, then you will find the details of the error in the Management Console Log section below.
To view the cached version value for a specific node, enter the node digits (under View Cache) and click on the “View” button. The cached value will be displayed in the log.
To clear all the cached values, click on the “Clear Cache” button.

Max Message Length Reducer

Using CLI

You can set the ‘Max Message Length Reducer’ value by issuing the command smsc set maxmessagelengthreducerwith appropriate parameters as described below. You can verify this by issuing the command smsc get maxmessagelengthreducer which will display the value set for this property.

Name
	smsc set maxmessagelengthreducer

SYNOPSIS
	smsc set maxmessagelengthreducer &lt;max-message-length-reducer&gt;

DESCRIPTION
	This command is used to set an integer value for max-message-length-reducer.
	The recommended value is 6. Possible values are numbers from 0 to 12. 

	Empty TC-BEGIN will be used if the message length is greater than the maximum
	possible message length minus the value specified for max-message-length-reducer.

	(message-length &gt; max-possible-message-length - max-message-length-reducer) 

	Empty TC-BEGIN is used in MAP Version 2 and 3 for forwardSM and Mt-ForwardSM 
	requests. In MAP Version 2 the dailog portion
	(ApplicationContextName, MAPOpenInfo primitive) and the component portion 
	(forwardSM and mt-ForwardSM requests) may both together be too long to fit within 
	a MTP message. In Empty TC-BEGIN case, it first sends the dailog portion in 
	TC-BEGIN followed by the component portion in the next TC-CONTINUE. 
	Whether empty TC-BEGIN is used or not depends on the length of a message and the 
	length of SCCP addresses. This option increases the guarantee of delivery of a 
	message  to some network.

EXAMPLES
	smsc set maxmessagelengthreducer 6

Using GUI

Set Max Message Length Reducer using the GUI

In the GUI Management Console for SMSC Gateway, click on ‘Server Settings’ in the left panel.
The main panel will display the existing Settings, segregated into four horizontal tabs: Properties, SS7 Settings, Cassandra and Scheduler. Switch to the ‘SS7 Settings’ tab in the GUI.
You can specify the Max Message Length Reducer by entering the value in the text field ‘Max Message Length Reducer’. For more details of this parameter, please refer to the description of the CLI command for the same in the preceding section.
You must click on the button ‘Apply Changes’ at the top of the window to save your settings. If there is an error in setting the value, then you will find the details of the error in the Management Console Log section below.

The post SMSC – Advanced Settings SS7 appeared first on Telestax Docs Online.

SS7 Settings

SMSC Global Title

Using CLI

Using GUI

SMSC Sub System Number (SSN)

Using CLI

Using GUI

HLR Sub System Number (HLR SSN)

Using CLI

Using GUI

MSC Sub System Number (SSN)

Using CLI

Using GUI

MAP Application Context version

Using CLI

Using GUI

MAP Version Cache

Using CLI

Using GUI

Max Message Length Reducer

Using CLI

Using GUI

Trending Articles