If the NSG Gateway does not start, you will see the following screenshot from the NSG WebGUI control panel
Alternatively, within an SSH terminal, this will look like:
In most cases the Media Gateway will not start due to configuration issue.
In other rare cases, there is a hardware fault that causes the TDM Driver not to start, and thus the configuration not to load correctly.
Verify that the TDM Driver (or physical layer) started
If the TDM driver started correctly, but the 'Media Gateway' did not, then certainly there is an error in the TDM SS7 configuration.
As seen in the above diagrams the physical layer DID start correctly as 'Configuration interfaces' output shows 'done.' without any error
This also can be seen by navigate to the 'control panel' and select 'TDM Status'
As seen in the example below, the 'TDM Driver' started correctly but the Media Gateway did not. So the issue needs to be investigated within the TDM SS7 Configuration.
If the 'TDM Driver' did not start correctly, navigate to 'Advanced Logs', located under 'Reports->System'
Make sure the drop-down selected is 'messages', then scroll down the window to find your error.
An alternative method to verify the status of the physical layer, log into the NSG SS7 via SSH
Type 'wanrouter status' :
Reviewing TDM SS7 Configuration for the issue
After verifying the physical layer (TDM Driver) is started, review the TDM SS7 Configuration for the issue
Navigate to 'Reports' -> 'Gateway Logs' :
Alternatively, you can SSH into the NSG-SS7 and navigate to /var/log/nsg/sangomagw.log:
If NSG Fails to start, it is important to search for "ERROR" or "CRIT" messages from top to bottom of the file because the bottom of the file will always show the typical output when there is error above, which is not helpful
License error
The following information only applies to NSG Software installations.
If you have an NSG appliance, disregard the following information
The NSG Gateway will fail to start if the installed license does not match the MAC Address.
The MAC Address within the license must match any of the system's ethernet interfaces.
Also the MAC address within the license is case sensative.
Example of license failure from NSG-WebGUI:
Example of license failure from SSH terminal:
If you see the above, you will need to contact Sangoma Professional Services for new license at support.sangoma.com
Mismatched Sub-Service Field (SSF)
When configuring an SS7 Signaling link on a port, there are two sections where the SSF options must match. If they do not match, NSG-SS7 will not start.
Verify the two sections match:
MTP3 Information
SS7 ISUP Interface
If the SSF values are mis-matched, the log wills will show the following:
NSG-WebGUI Gateway logs ('Reports' -> 'Gateway Logs')
SSH terminal to /var/log/nsg/sangomagw.log:
