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

Was this helpful?

  1. Installation
  2. Distributed Architecture
  3. Switch Server

dnl_softswitch

This is the main switch service that you need to configure for call routing. Here is how you confgure:

cd /opt/denovo_v6/dnl_softswitch/conf
vi dnl_softswitch.conf

Each one of the dnl_softswtich instance must have a unique identifier. This switch_name needs to be changed on every next switch, it can be changed on all, but it is not requirement for first one. it is because each switch on each server needs to have its unique name in order to function properly.

switch_name = class4 

This following parameter is to be changed to the ip address where database is installed:

[db]
db_host = 127.0.0.1

This needs to be changed to the ip address accessible to the UI and api ( it may be private ip if servers have private network established).

[CLI]
cli_listen_ip = 127.0.0.1

This needs to be changed to the ip address on which dnl_livecall is set to listen to (also can be from private ip range if there is such setup)

[livecall] 
livecall_server_ip = 127.0.0.1

This username is also unique and needs to be changed on each additional switch. Also for this to work after change is done, new user needs to be inserted into database in the table c4_livecall_users.

livecall_login_user = class4  

After you finish configuring dnl_softswitch, you can restart it with the following command:

systemctl restart dnl_softswitch

You can check if the switch is running with the following command:

systemctl status dnl_softswitch

Then, you should check if dnl_softswitch is listening on port 5060:

netstat -anp |grep 5060

Binding dnl_softswitch to port 5060

When dnl_softswitch is first started, it does not automatically listen on port 5060 for SIP traffic. You need to configure it in the UI.

To do so, you first go to the VoIP Gateway page:

Inside VoIP Gateway, you will see the live instance of VoIP switch:

As you can see, initially, this dnl_softswitch is not having any SIP Profile.

You need to click on the + icon to add SIP Profile in order for this swtich to start listening on the defined SIP IP and port for traffic:

Previousdnl_livecallNextdnl_watchdog

Last updated 3 years ago

Was this helpful?

You can see in the above image that this setup has one dnl_softswitch instance running. You need to add SIP Profile under this instance by clicking on icon. Each SIP Profile represents the SIP IP that dnl_softswitch is listening on. Each instance of dnl_softswitch can be listening to many SIP IP ( SIP Profile ).