Audio Issues
...
Log into your NSG Gateway webgui by typing the IP address of NSG Gateway in a web browser.
Select Reports > Network Capture
uncheck 'All Network Interfaces' and select the ethernet interface that has a cable connected to it going to your sip side device
Click the Capture button at the bottom to begin tracing on the sip side
Reproduce your issue
Stop the wireshark trace by click on the Stop Capture
Download the wireshark trace to your local machine by clicking on the Download button
The downloaded file will be called prot-capture.tgz
Open the archived file which will show you the wireshark trace you captured.
it will be called 'prot-capture-eth0.pcap'
To open your wireshark trace, make sure you have wireshark on your local system then double click on the file which will open up in wireshark
If you don't have wireshark, you can download it from here: https://www.wireshark.org/download.html
...
Highlight each row that shows up (each row is one leg of the call) by holding the the CTRL key on your keyboard as you click on them:
Click on Play Streams located at the bottom of the window
You will now be presented with the audio streams of your call.
...
| Info |
|---|
If your audio stream contains G729, please use the following guide to decode G729 audio streams: |
Ftdm Trace
NSG Gateway has a built-in feature to capture an audio trace from within the software. This audio trace is called Ftdm trace. Taking an Ftdm trace is useful to verify if there is bad audio coming from the SS7 telco lines or anywhere between the cables connected to NSG up to the NSG Software.
...
If you are unable to identify which channel the call is being made on, you can block all the channels accept the one in question. To do this follow the procedural commands found here: Channel Based Operation#Blocking/UnblockingVoiceCICs
Analysing Recordings using Audacity
...
Type the following command to begin a trace
-> wan_ec_client wanpipe1 monitor <channel number>
<channel number> is a channel number obtained by viewing the TDM Status: Operating the Gateway#TDMStatuswanpipe1 is port 1. If the call is on port 2, replace with wanpipe2 (and so on..).
the utility wan_ec_client will save an audio record inside the local directory (where you ran the trace)
If your audio issues requires a longer trace to be taken, use the 2 minute trace, seen below:
To record for 2 minutes run:
-> wanpipe1 monitor120 <channel number>
The details of the above syntax is the same as for the 15 second trace
Verifying NSG Gateway System Status
...
To verify cable strength navigate to Overview > TDM Status
Hover the mouse over the port you wish to check. For example, hover the mouse over port 1 and a small window will pop up to display line strength status
The line stength is indicated at the bottom where it says Rx Level :> -2.5db. If the line strength says anything different than 2.5 db, this can be the cause of your audio issues. To fix this, try to re-make the cable by crimping an new rj45 connector to it and re-test
...
System cannot handle the voice 10ms interrupt load
System is misconfigured. Kernel does not support the chipset.
Run:
-> cat /proc/interrupts
-> Check that all interrupts are running as IO-APIC.
Make sure there are no X-PIC interrupts.
...