Pre-requisites

Core Module must be v41.2.2 or higher.

Step-by-step procedure

Note: For configuration files and throughout this guide we are using YOURNSSIP as a placeholder. YOURNSSIP needs to be replaced with the IP address or domain name of your NSS that SNAP will query.

Also YOURPBXIP with the IP of your SNAP system.

Setup the connection

To set up the connection with the NSS, import the connection_import.csv file into the Connections section within the Core Module Admin UI (Connections > Connections).

Enable SIP Identity header

Navigate to System>Settings>Advanced>Properties. Add/Edit Parameter SipBlockIdentity with the value "no".

Edit Dial Translation Plan

You will need to insert a new Default STIR SHAKEN table in-between the Forward Blocking and Default dial translations in your dial translation chaining order. If your chaining order is different DO NOT import the new data as-is. Adjust for your specific configuration.

Importing the "Dial Translation Plan" import file (SHAKEN_Plan.csv) and "Dial Rules" import file. (SHAKEN_Rules.csv) will make all the necessary changes needed. Note: Import the dial translation plan file FIRST and then the dial rules file next.

Forwarding Dial Translations

Edit the forwarding dial translations: In the Default dial translation table, there are rules that match a number without sip: or @*. Expect there to be 2-3 forwarding rules for 7/10/11 digit dialing; for example, [1-9][0-9][0-9][0-9][0-9][0-9][0-9]. Change the application to the "add header" variant (for example if using To Connection then change it to To Device w/VM - Add Header) and in the Application Parameter field enter:

X-User-ID: @

Call Routing

Navigate to Dial Planning> Call Routing and import the route skeleton (Routing-SHAKEN-Skeleton.csv) and route connections (Routing-SHAKEN-Connections.csv) to create the call routing rules to handle calls after getting SHAKEN. Note: Import the route skeleton file FIRST and then the route connections file next.

The destination connections in the SHAKEN route must be edited. Click on the number 1 in the #1 column and for the first entry edit the host to your primary termination carrier, leaving the user as [!!!!!!]. Create entries 2 and onwards for your existing termination carriers with the user always as [!!!!!!], as shown in the screenshot below:

Test Setup w/Call Route

To test outbound calling SHAKEN setup, in Call Routing create a rule for the preferred test number to be dialed; for example, sip:18587542200@*. Then click the click the 0 in the #con column rule for this route. Click Update Connection, then for the host select $YOURNSSIP from the dropdown menu and then click Create.

Make a call to the test number and then review the trace. There should be an INVITE to NSS, a 302, then an INVITE to the terminating carrier; as shown below. In the INVITE to the terminating carrier, there should be a new Identity header. Once testing is complete, optionally delete the test call route that was created.

Final setup

If everything went well and once ready to go live, modify the existing sip:1??????????@* rule; in Call Routing, click the number in the #con column, and set the FIRST CONNECTION's host to be YOURNSS. Keep any existing connections in place for position 2 and onwards, just in case.