Contents

1   Description

This instruction describes how to create new local and remote Signaling Points, using the Ericsson Command-Line Interface (ECLI):

2   Procedure

2.1   Create Local Signaling Point

Prerequisites

• No documents are required.
• No tools are required.
• The following conditions must apply:
  • An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.
  • A Managed Object (MO) SignalingNetwork exists.

Steps

1. Navigate to the SignalingNetwork MO, for example:

   >ManagedElement=1,Ss7=1,SignalingNetwork=1

2. Enter Config mode:

   (SignalingNetwork=1)configure

3. Enter the name of new LocalSignalingPoint, for example:

   (config-SignalingNetwork=1)>LocalSignalingPoint=2

4. Set the point code, localSignalingPointCode, for example

   (config-LocalSignalingPoint=2)>localSignalingPointCode=200

5. Create an M3UA local application server (AS), LocalAs and tie it with the LocalSignalingPoint, for example:

   (config-LocalSignalingPoint=2)>ManagedElement=1,Ss7=1,M3ua=1,LocalAs=4,localSpc="ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=2"

   Note:  

   How to create LocalAs read in "Configure Basic M3-IETF IPSP - IPSP Configuration"

   
   
6. Commit the settings:

   (config-LocalSignalingPoint=2)>commit

2.2   Create SCCP Signaling Point

Note:  

Only one SccpSignalingPoint can be created during a transaction.

Prerequisites

• No documents are required.
• No tools are required.
• The following conditions must apply:
  • An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.
  • A Managed Object (MO) LocalSignalingPoint exists.

Steps

1. Navigate to the LocalSignalingPoint MO, for example:

   >ManagedElement=1,Ss7=1,SignalingNetwork=1,LocalSignalingPoint=2

2. Enter Config mode:

   (LocalSignalingPoint=2)configure

3. Enter the name of new SccpSignalingPoint, for example:

   (config-LocalSignalingPoint=2)>SccpSignalingPoint=Mercury

4. Check the default value for attributes:

   (config-SccpSignalingPoint=Mercury)>show -v

5. Change the value of attributes if required

   Note:  

   If nodeUsedByTcap is set to YES, then at least one LocalSap should be configured.

   
   
6. Commit the settings:

   (config-SccpSignalingPoint=Mercury)>commit

2.3   Create Remote Signaling Point

Prerequisites

• No documents are required.
• No tools are required.
• The following conditions must apply:
  • An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.
  • A Managed Object (MO) SignalingNetwork exists.

Steps

1. Navigate to the SignalingNetwork MO, for example:

   >ManagedElement=1,Ss7=1,SignalingNetwork=1

2. Enter Config mode:

   (SignalingNetwork=1)configure

3. Enter the name of new RemoteSignalingPoint, for example:

   (config-SignalingNetwork=1)>RemoteSignalingPoint=Mars

4. Set the point code, remoteSignalingPointCode, for example:

   (config-RemoteSignalingPoint=Mars500)>remoteSignalingPointCode=500

5. Commit the settings:

   (config-RemoteSignalingPoint=Mars500)>commit