Skip to end of metadata
Go to start of metadata

Problem

Scenario:

Analog PSTN > Vega 50 FXO > IP-PBX(or other sip device) 

 
Symptom:

Static, breaking sound, echoing, all being heard on the SIP side. Below is a sample of bad audio when calling Sangoma's IVR (1-905-474-1990 )

 

Sample Bad Audio.wav

 

The following resolution steps are only available on our latest hardware releases (serial numbers with a '2', 00505820xx).  If your vega has a '1' (00505810xx), your Vega cannot use the below steps.

Solution

Once you have verified that this symptom is not being caused by your network, attempt to resolve this issue by upgrading your Vega50 using the latest build. 

Software upgrade instructions and the latest build are available here:   Firmware Download

(Please make sure to backup your Vega configuration prior to upgrading as the unit will have all user configuration back to factory settings)

After the update is completed, please log in to the Vega and proceed to CLI command line, and type in the following command: set ._advanced.pots.fxo.1.full_scale=1, then Apply and Save. This will basically apply the "Full scale" feature.

If the audio on the SIP side becomes very loud after the update, please follow the below instructions to normalize:

  1. type in the CLI command line the following: set ._advanced.pots.fxo.1.digital_rx_gain=0 (or -3 if the setting was already 0). Then Apply and Save

  2. Sometimes customers might report an echo on the SIP side(meaning they can hear themselves while talking). The following command in the CLI can help to reduce the echo: set ._advanced.pots.fxo.1.digital_tx_gain=-3(negative 3), and then Apply and Save.

  3. It's also worth to increase the echo tail from the default 32, to 64 or 128, in Expert Config > Media > TDM Profiles > Echo Tail Size > change it to 64 or 128

If only some of your FXO ports are having the above Symptom, then follow the below steps:

For example on Vega 50 4 FXO, only ports 1 and 4 have the audio issue symptom.

Follow the above steps to upgrade to the latest build, then:

 1.We'll need to create an additional FXO hardware profile (this can only be created through a CLI, not the GUI), and call it fxo2 profile

 2. To create the profile, please type the following command in the CLI: cp ._advanced.pots.fxo.2  and then Apply and Save

 3. Please make the settings of fxo.2 equal to fxo.1 profiles( to avoid different behavior).   Navigating to Expert Config > POTS > FXO Port Hardware Profiles:

 Then Apply and Save.

4. Once we set both FXO profiles, we would need to apply this "boosted" profile to the problematic FXO ports. Let's say that in this case as you can see the Full Scale feature is enabled on fxo.1 profile ( this change to the Ffull scale feature from the GUI instead of the CLI command line)

5. Navigate to Expert Config > POTS > POTS Configuration, and change the "good" ports FXO 2 and FXO 3 to profile fxo.2 (the one that does not have the Full scale boost option enabled):

 

 

 Then Submit, Apply and Save.

6. This will allow us to have some flexibility on a deviation between two profiles on port based performance.