Configuration of Call Signing Endpoints

Navigation: Settings >> STIR/SHAKEN Endpoints

Endpoints will be configured as a list wherein users can create an unlimited number of endpoints, each with its own IP or FQDN. (UDP protocol is required currently)

In most cases, there will be a separate endpoint for each attestation level (A, B, C). Some implementations might also use dynamic endpoints which will assign attestation levels based on criteria they determine during the dip itself.

Customer/Termination Trunk Group Configuration

We have added the ability for 46 Labs customers to sign calls on behalf of their customers if no token is included in the SIP Identity Header of the outbound call. We also provide the ability to block customer/termination attempts if the customer is supposed to sign their own calls but does not. 

• The STIR/SHAKEN "Treatment” drop-down on customer/termination trunk groups allow users to identify how the attempts will be handled. This is a required field for customer/termination trunk groups. Configuration options include:

• No Treatment - This will simply send the attempt through the routing module without any kind of blocking or signing. (Default Setting)

• Block Unsigned - This feature will be used if the originator is supposed to sign their own calls. If an attempt is received without a token, it will be blocked with “503 / Missing SS token.”

• Sign Unsigned Calls - This option will be used if the 46 Labs platform is supposed to sign calls for the customer using a selected STIR/SHAKEN endpoint. It will not alter calls that have already been signed.

• The STIR/SHAKEN "Endpoint” drop-down will allow the user to select a STIR/SHAKEN signing endpoint configured in the Call Signing Endpoints page. This field is required if STIR/SHAKEN Treatment = “Sign Unsigned Calls”. If STIR/SHAKEN Treatment is “No Treatment” or “Block Unsigned” then this drop-down is not required.

Invite/Response Example