Master DNL Class4
  • Introduction
  • Configure a new Class 4 instance
    • Setup Admin Access
    • First Time Login
    • Setup SIP Switch
  • Your First Call with Class 4 Fusion
    • Create Vendor Rate Table
    • Create Termination Vendor
    • Create Egress Trunk
    • Create Dynamic Route
    • Create Routing Plan
    • Create Client Rate Table
    • Create Termination Client
    • Create Ingress Trunk
    • Simulate Your Call
  • Support Contact
  • eLearning
  • Bug Reporting Process
  • Hardware Sizing
  • Licensing
  • Installation
    • Install with Tarball
    • Install with RPM
      • Step by Step Guide
    • Install with AWS
    • Install with Google Cloud
    • Distributed Architecture
      • Switch Server
        • dnl_live_monitor
        • dnl_tool
        • dnl_livecall
        • dnl_softswitch
        • dnl_watchdog
        • dnl_cloud
      • Web UI
        • dnl_web_helper
    • Troubleshoot Your Installation
    • Setup SSL on Web UI
    • LAN IP Setup for Virtual Machine
    • Change IP/MAC Address
    • Validate Your Installation
      • Check dnl_softswitch log
    • Configuring DNL softswitch
    • Setup Selinux
  • Configuring Stir/Shaken
    • Generating Certificate with Peeringhub.io
  • Upgrade an Existing Installation
    • Update an Existing Installation
      • Update with Tarball
      • Update with RPM
  • Stir Shaken
    • Introduction
    • Configure Class 4
    • Configure Stir Shaken in DB
    • Configure Ingress Trunk
    • Configuring Egress Trunk
    • Basic Configuration Example
    • Validation of Stir/Shaken Setup
    • Setup External AS/VS connectivity
  • Basic Switch Configuration
    • Integrate Class 4 to Google SMTP
    • Customize your logo
    • Customize Domain Name
    • Customize email template
    • Customize invoice template
    • Configuring Payment Gateway
      • Stripe Configuration
      • Paypal Configuration
    • Configuring CDR and PCAP Backup
      • Google Cloud Setup
    • Configuring SIP Registration
    • Configuring LRN
  • Quick Setup for Termination Traffic
    • Create Termination Vendor
      • Specify IP to send to egress
    • Create Termination Route
      • Routing Plan
      • Static Route
      • Dynamic Route
    • Create Termination Client
    • Test with Call Simuation
    • Test Calls with SIP Client
    • Check CDR
  • Quick Setup for Origination Traffic
    • Introduction
    • Create DID Vendors
    • Create DID Billing Plan
    • Create DID Clients
    • DID Repository
    • Assign DID to Client
    • Test Calls with Call Simulation
    • Setup for your client to buy DIDs from portal
  • Data Access
    • Postgres Database
      • Obtain Report Data from DB
      • Obtain CDR from DB
    • Raw Switch Data
      • CDR Data
        • Release Cause Definition
      • PCAP Data
      • Auto Data Cleanup
  • System Administration
    • Modules
    • Start and Stop
    • Logging
    • Software Updates
    • Setup additional dnl_softswitch
    • Add Additional IP to Switch
    • Configure SIP Cause Code and Q850 Mapping
    • Enable Media Proxy
  • Class 4 API
    • Authorization
    • Class4 API
  • Troubleshooting
    • Calls are failure
    • Change Q850 in 4xx/5xx
    • One-way Audio with SIP Client Testing
      • Using Zoiper to resolve NAT issue
  • Automatic Call Blocking
    • Introduction
    • Youmail Blocking
    • DNC Blocking
    • LERG Blocking
Powered by GitBook
On this page
  • Stir/Shaken setting in Ingress Trunk
  • Re-sign calls on ANI/DNIS replacement
  • Attestation Setting
  • Stir/Shaken ANI Group
  • Un-sign Call Handling

Was this helpful?

  1. Stir Shaken

Configure Ingress Trunk

PreviousConfigure Stir Shaken in DBNextConfiguring Egress Trunk

Last updated 2 years ago

Was this helpful?

Class 4 provides built-in functionalities to verify stir/shaken identity header and sign call using stir/shaken certificate.

By default, class 4 automatically pass the stir/shaken identity header from ingress trunk to egress trunk. Class 4 can also be provisioned to sign calls that don't have stir/shaken header. To enable Class 4 to sign call, you will need to configure Stir/Shaken in both ingress trunk and egress trunk.

Stir/Shaken setting in the ingress trunk defines what attestation is to be used to sign call. Stir/Shaken setting in the egress trunk defines whether a call should be signed when it is being passed to the egress trunk.

Stir/Shaken setting in Ingress Trunk

The ingress trunk setting for Stir/Shaken is shown as follows:

Under Signing Policy, you can see the following options:

Signing Policy
Description

Do not sign calls

This option means the switch should not sign any calls from this ingress trunk.

Sign only US numbers

This option means that the switch should only sign calls with valid US numbers as the ANI.

Sign any phone numbers

This option means that the switch should sign all calls.

Sign only numbers from the Stir/Shaken ANI group

This options means that the switch should sign calls with ANI defined in the Stir/Shaken ANI Group. You can create Stir/Shaken ANI Group from Configuration menu.

Re-sign calls on ANI/DNIS replacement

In the next option, you can turn on / off "Re-sign calls on ANI/DNIS replacement."

When turned on, Class 4 will regenerate a new Identity header if the ANI or DNIS is modified using Digit Manipulation or Digit Replacement.

Attestation Setting

This section defines what attestation level to use according to the ANI of the call.

You must set a default Attestation if you want to turn on signing of calls.

Stir/Shaken ANI Group

To create new Stir/Shaken ANI Group, you can select Stir/Shaken under Configuration menu:

After you create a Stir/Shaken ANI Group, you can click into the ANI Group and then you can upload numbers into the ANI Group.

Un-sign Call Handling

This option let you define how to handle a call from ingress trunk if there is no Stir/Shaken identity header included in it.

If you select Pass Through, it means you want to let the calls to go through and use the other options to define whether to sign and how to sign a call.

You can also choose to reject a call if the Stir/Shaken identity header is missing from the ingress side.

In some cases, the Stir/Shaken may exist but it is invalid, then you can also choose to reject calls that has invalid Stir/Shaken Identity header.