Versions Compared

Old Version 1

changes.mady.by.user Nathaniel Halbrooks

Saved on

compared with

New Version Current

changes.mady.by.user Kelli Higdon

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

How to Restart NBE Gateway

...

  • Open the NetBorder Express Gateway Web Manager in your web browser

  • Go the Status and Controls tab, select the Logging tab

  • Change the Mode property from PRODUCTION to DEVELOPMENT

  • Click the Apply button to activate development logging (logs by default to GatewayDebug.log in the /logs folder)

  • Restarting the gateway will revert the logging mode to the default value set in the configuration, the changes made in this panel is not permanent.

  • All call logs will be saved in NBE_root: /logs/call-logs/  where calls will be organized by date and time (SEND THIS TO SUPPORT!)

    Note: Changing Mode from Development back to Production and then reverting it back to Development mode is quick and easy way to reset the GatewayDebug.log file.

...

There are two types of channel name formats:

Digital channel name format

...

  • Click on "Start -> All Programs -> Netborder Express Gateway -> Configuration -> Edit Global Configuraiton File"

  • In the file that is opened search (ctrl+f) for "netborder.gw.recordCalls.enabled=false"...

  • Set the value to true and save the file

  • The location of the recordings is defined by the "netborder.gw.recordCalls.directory" property. The default value is logs/recording/

  • Restart the NBE Gateway...see "How to restart NBE Gateway"

 

Dynamically Enable/Disable Call recording

...

Code Block
netborder-oam-cmd localhost:18086 set-config-param netborder.gw.recordCalls.enabled false

 

...

How does IP

...

Addressing working in NBE

There are 3 parameters (located in the gw.properties file in the config folder of the installation directory) that control the IP Addresses assignment of the gateway:

...

  1. Clocking - You can change the clocking in NBE as shown in the picture below.

    21.jpg

  2. Signaling - You will need to change to network mode termination as shown in the picture below

    22.jpg

  3. Cabling - You will need a cross over cable if you are connecting back to back with NBE or another pbx. For pinouts go tohttphttps://wikisangomakb.sangoma.com/Pinouts#A101/2/4%20Crossatlassian.net/wiki/spaces/TC/pages/50922195/Cable+Pinouts?search_id=1c7c658d-e973-410c-bcbe-e8bed04c9eae . Note this is different pinouts then a ethernet cross over cable.

...

 

Code Block
config/sip-client-registration.xml

<?xml version="1.0"?>

<client_registration_config>

<!-- Registration entry #1 -->
<registration_entry>
<address_of_record_uri>sip:sangoma1@10.10.2.76</address_of_record_uri>
<contact>
<uri>sip:sangoma1@10.10.2.76:5066</uri> <!-- If you modified the default sip port (5066), apply the change here -->
<transport>udp</transport>
</contact>
</registration_entry>

<!-- Registration entry #2 -->
<registration_entry>
<address_of_record_uri>sip:sangoma2@10.10.2.76</address_of_record_uri>
<contact>
<uri>sip:sangoma2@10.10.2.76:5066</uri> <!-- If you modified the default sip port (5066), apply the change here -->
<transport>udp</transport>
</contact>
</registration_entry>

<!-- Registrar -->
<registrar>
<uri>sip:10.10.2.100</uri>
<transport>udp</transport>
<retry_interval_sec>300</retry_interval_sec>
</registrar>

<expiration_sec>3600</expiration_sec>

</client_registration_config>

Code Block

 

Authentication

Below is how the authentication password is set per user defined in registration above. This is all done with the line "netborder.sip.digestCredentials" in config/gw.properties. 

...