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_cloud

cd /opt/denovo_v6/dnl_cloud_tool/conf/
vi dnl_cloud_tool.conf:


# (M) String used to identify this server
server_name 	dnl-host-server ← Change this name for each server dnl_software is running on (for switching part and api/ui one) so it identifies every server that is running .
# Default: connect to Unix-domain socket

pgsql_hostaddr  127.0.0.1  ← address of the postgresql server

pgsql_user  	postgres     ← username for database

#pgsql_pass 	password   ← Password if required (also remove # from the line)

Dnl_cloud_tool also needs to be configured to the ip address accessible to the UI/api part For this at the time of writing this instructions, values in database table needs to be changed: Table name dnl_cloud_status, each running instance of dnl_cloud_tool will be shown here in the table along with some data, for example:

select * from dnl_cloud_status ;
   server_name   |  instance  | operation | is_online |  	upd_time   	| server_ip | server_port | server_use_ssl | switch_list
-----------------+------------+-----------+-----------+---------------------+-----------+-------------+----------------+-------------
 dnl-host-server | search 	|       	| t     	| 2021-12-02 07:05:54 | 127.0.0.1 |   	33502 | f          	| class4
 dnl-host-server | downloader |       	| t     	| 2021-12-02 07:05:54 | 127.0.0.1 |   	33501 | f          	| class4
 dnl-host-server | dbman  	|       	| t     	| 2021-12-02 07:05:54 | 127.0.0.1 |   	33500 | f          	| class4
(3 rows)

In this table server ip needs to be changed to the ip address that is accessible from the server which hosts api/UI.

Sql for this is update table dnl_cloud_status set server ip = ‘your ip’ where server_name = ‘server_name’ ; (in this example dnl-host-server, but this name is defined in the dnl_cloud_tool config and it should be different for each dnl_cloud_tool instance.

Previousdnl_watchdogNextWeb UI

Last updated 3 years ago

Was this helpful?