Table of Contents

 

 

Document Overview

This document provides a configuration guide for Ribbon Solution (SBC/PSX) with NEUSTAR ATIS Server.

This document outlines the configuration:

  • with PSX: Configuring Ribbon PSX for HTTPS service
  • with EMA: Configuring STI profile on the SBC

Scope

This document provides the Ribbon Solution (SBC/PSX) Core configuration with NEUSTAR ATIS for documented products and their versions. This is a general reference document that requires user input during the configuration. For PSX/SBC configurations, the screen captures in this document are limited to only necessary provisioning areas.

Non-Goals

This document does not provide the test cases details, the success criteria, processes and execution steps of testing that were performed. Also, this document does not focus on general EMA/PSX configurations and provisioning areas for the NEUSTAR ATIS server. 

Introduction

STIR/SHAKEN Interop testing is performed between Ribbon’s Solution (SBC/PSX) and NEUSTAR ATIS AS/VS servers. This document outlines the SBC and PSX configurations required to achieve this purpose.

Audience

This is a technical document intended for telecommunications engineers with the purpose of configuring both the Ribbon SBC and PSX. Navigating the third-party product as well as the Ribbon SBC Command Line Interface (CLI) is required. Understanding the basic concepts of TLS/TCP/UDP, IP/Routing, and SIP/SRTP is also necessary to complete the configuration and any required troubleshooting.

Requirements

The sample configuration uses the following equipment and software:

Requirements

Product

Equipment

Software Version

Ribbon Solutions

Ribbon SBC

Ribbon PSX

V07.02.00-R000

V11.02.00-R000

Reference Configuration

The following figure illustrates connectivity between the NEUSTAR ATIS SVS and Ribbon PSX.

High-Level Architecture For Neustar Testbed - PSX Interop - Scenario 1

                                                                     

High-Level Architecture For Neustar Testbed - PSX Interop - Scenario 2

                                                                       


High-Level Architecture For Neustar Testbed - PSX Interop - Scenario 3

                                                                       



SBC Configuration

This section provides an SBC configuration used for STIR/SHAKEN interop only. For any other configurations, please refer standard configuration guide.

Note

For this feature to work, it is mandatory to enable the External PSX for Routing.

 

Global Configuration

Profile

Enable the STI services under the profile.

set profiles services stiProfile stiProfile1 state enabled
commit

Trunk Group

Configure all the Trunk Groups that require STI services with the previously mentioned STI profile.

set addressContext default zone <zone> sipTrunkGroup <TG> services stiProfile stiProfile1
commit

PSX Configuration

This section provides the configuration aspects required for STIR/SHAKEN interop only. For any other configurations, please refer the standard configuration guide.

Note
 Either Signing Service or Verification Service can be executed if the PSX is installed as a standalone Master. To achieve both the services without any service impact, install the PSX in Master-Slave mode.

DNS Related

Configure the DNS zone and LWRESD profiles. These are required for DNS resolution towards the NEUSTAR ATIS Server.

DNS Creation

  


Softswitch Device

Check the Softswitch Device has the following devices created.

Softswitch Device

 

STI Server Device

Create a STI Server device. 

Note
The FQDN should be exactly the same as the configured entry in the DNS server.

STI Server Device

Process Configuration

Update the Process Configurations for HTTPC, SLWRESD, and PES.

Process Configuration

 

 

Process Management

Activate the httpc and slwresd process under the Process Management used by Softswitch. Set the log level to 4 if all logging is required. The argument "-C 1" is an optional argument required for curl log generation

Note
  • PSX processes are restarted once Process Manager is saved.
  • Enabling log levels might impact system performance.

Process Management


Number Translation Criteria

Create Number Translation Criteria tables with the Lookup Type set to either Signing or Verification.

Create Number Translation Criteria

  

Trigger Type Priority

Check the Trigger Type Priority table. If the Call Processing Element Type used in Number Translation Criteria is not present, then add an entry in this table.

Trigger Type Priority

 

Error Mapping Profile

Create the Error Mapping Profile with Error code, corresponding SIP reason code, and Reason Text. 

Error Mapping Profile

STI Service Definition

Create Service Definitions for Signing and Verification. Set Error Mapping Profile if required.

STI Service Definition

STI Profile

Create the STI Signing and Verification profiles and add them to the corresponding Egress Trunk Groups.

STI Profiles

Routing Label

Create a routing label with either the Signing or Verification flag enabled.

Routing Label

Trunk Group

Select the corresponding STI Profile under the Trunk Group.

Trunk Group

 

IP Signaling Profile

Enable the P-Asserted-ID under Privacy for the IPSP that is used by the Trunk Group triggering Signing Request.

IP Signaling Profile

 

Packet Service Profile

If the "Fingerprint" attributes need to be processed, enable the flags "Enable DTLS" and "Relay DTLS SRTP".

Packet Service Profile

 

Conclusion

This document describes the configuration steps required for the Ribbon Solution to successfully test interop with NEUSTAR ATIS AS/VS.  All feature and serviceability test cases were completed and passed.