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
  • Setting up a SIP Interface
  • What if you are getting no time out?

Was this helpful?

  1. Basic Switch Configuration

Configuring SIP Registration

PreviousGoogle Cloud SetupNextConfiguring LRN

Last updated 2 years ago

Was this helpful?

You can create SIP user and use this SIP user/password to authenticate your inbound traffic by adding as many SIP User and Password combination in the Ingress Trunk section:

In the "Authoized" dropdown, select "Authorized by SIP Registration."

Then, you will see the table below with one column for SIP Username and one for SIP Password. Thisis where you can create as many SIP user as you need.

Setting up a SIP Interface

The standard SIP Interface only supports IP authorization. To support SIP Registration, you need to create a new SIP Interface.

You can click on "VoIP Gateway" to do that.

By default, you would see one VoIP gateway setup with port 5060 for your SIP traffic. The default VoIP Gateway has "Require authentication" turned off, meaning that there is no need for SIP Registration.

To turn on SIP Register on any one of the Ingress trunk, you need to create another VoIP Gateway that has "Require authentication" set to "true". Here is an example how it should look:

With this configuration, your SIP client can point to the same IP but port 5080 to perform SIP registration.

Setting SIP username and password in SIP trunk does not work unless you also have a VoIP Gateway that can handle "Authorization."

What if you are getting no time out?

If your sip client is getting no response from dnl_softswitch, then, it is likely that it is firewall issue. You can use sngrep or Live Call page from UI to check the SIP register signal flow:

If you see that your SIP Register is not getting response, then you can run the following commands to open up port 5080:

firewall-cmd --add-port=5080/udp --permanent

firewall-cmd --reload