SHT FAQ
Contents
- 1 Does the analog voice board come with an audio jack for direct playback through a headset or sound speaker?
- 2 What purpose does the external power supply on the analog board serve?
- 3 Analog Trunk Channel:
- 3.1 What is the difference between DTMF and FSK CallerIDs (calling-party numbers)?
- 3.2 Why could the trunk or recording channel on the analog board not receive CallerID?
- 3.3 Why do two adjacent trunk modules sometimes receive the same CallerID at the same time?
- 3.4 Why does a channel repeatedly receive the same CallerID?
- 3.5 Why does the record or trunk channel receive gibberish when trying to retrieve CallerID?
- 3.6 Why do the trunk channels sometimes appear engaged, without response, or crossed lines between two adjacent channels (i.e. both lines appear to have received a call when in fact only one has)?
- 3.7 How to properly configure tone analysis parameters for an analog board?
- 3.8 Why does the analog trunk channel sometimes undesirably pick up busy tones?
- 3.9 Why does the application fail to invoke the function SsmAutoDial to dial a number from the trunk channel?
- 3.10 How does an analog trunk channel detect pickup from remote phone in a dial-up process?
- 3.11 Why does the analog trunk channel sometimes fail to detect hangup from remote end?
- 3.12 How does the analog trunk module detect connection drop on a line?
- 3.13 Is it possible for driver to make a misjudgment when PBX plays prompt tones in a call from the analog trunk channel to a mobile phone?
- 3.14 Why does an analog trunk channel switch from "idle" to "ringing" only after two rings have been detected?
- 3.15 Why does an analog trunk channel take a longer time to determine a ringback tone when calling out?
- 3.16 When a remote phone places a call to an analog trunk channel, the phone cannot hear anything played by the channel, or hears only a short section before it is cut off. Why?
- 3.17 What to do if a station on analog boards can hear echoes from itself?
- 3.18 Can multiple analog trunk channels share the same called party number?
- 4 Station Channel:
Does the analog voice board come with an audio jack for direct playback through a headset or sound speaker?
Yes. There is an audio jack which plays signals from Channel 0 through a connected headset or sound speaker.
What purpose does the external power supply on the analog board serve?
The purpose is to provide feed power for station modules. The feed power for 16-/8-channel B-type boards is 48V, for Version 2.0 of 16-/8-channel B-type boards is 40V, for 16-/8-channel C-type boards is 40V, and for 16-channel D-type boards is 12V. Each B-/C-type board has an external power interface which is used for connecting the external feed power and the ringing current power. For 16-channel D-type boards, multiple power supply schemes are available to provide the 12V feed power: one is to connect the P4 D-type hard disk power plug of the computer, and another is to short the S17 pin header and obtain the power via the PCIe slot (see the figure below). When the power supply inside the computer is insufficient, a 12V power adapter externally connected can work as a substitute. For more information, refer to the corresponding hardware manual on our website.
We strongly advise users to buy the power supply from Synway, and not to use any power supply with uncertain voltage or polarity, or it might cause damage to the voice board.
Note: Ensure that polarity is correct and only establish the connection with power off.
Analog Trunk Channel:
What is the difference between DTMF and FSK CallerIDs (calling-party numbers)?
DTMF CallerID is transmitted in DTMF mode before the first ring, whereas FSK CallerID is transmitted in FSK mode between the first and second rings.
Why could the trunk or recording channel on the analog board not receive CallerID?
1) Input connection to board is broken.
2) Certain PBXs do not support CallerID transmission.
3) PBX side does not open incoming call display function to relative phone line.
4) PBX side did not send CallerID on this occasion.
5) Poor grounding may also cause a CallerID to be missed.
6) Incorrectly set receiving mode for CallerID (DTMF or FSK mode) in configuration file or application program.
7) When in FSK mode, the application could have tried to retrieve CallerID when the driver has detected the first ring or even earlier. It is suggested that the application retrieves CallerID only after the second ring is detected.
8) When there is a high volume of incoming calls at one time, it can happen that one caller calls the voice board and hangs up while the PBX is sending its CallerID to the voice board. If another caller now calls in before the previous PBX has completely sent CallerID of the first call, and the voice board picks up this second call, the result could be that the voice board receives no CallerID or that of the first call, or gibberish. We suggest that when expecting high call volumes, the voice board should be set to pick up calls immediately upon receipt of CallerID, and not wait for ring-detection in its receiving procedure.
9) When in DTMF mode, it could be due to:
A. Sensitivity for DTMF reception is too low. This can be adjusted in the configuration file.
B. Received CallerID is less than 4 digits, while the driver is configured to filter out numbers that are less than 4 DTMF digits. This case only occurs for SynCTI Ver. 5.3.0.1 and below versions. For versions above Ver. 5.3.0.1, the driver is configured to filter out numbers that are less than 1 digit.
C. CallerID is sent between the first and second rings but retrieved after detection of the send ring.
Why do two adjacent trunk modules sometimes receive the same CallerID at the same time?
It is mostly due to permanent or transient short-circuiting between the two modules.
Why does a channel repeatedly receive the same CallerID?
The driver does not automatically clear the CallerID buffer. It is suggested that the application program is set to clear the buffer upon the retrieval of each CallerID, or the previous CallerID will be read.
Why does the record or trunk channel receive gibberish when trying to retrieve CallerID?
This is often due to poor line quality or poor grounding.
Why do the trunk channels sometimes appear engaged, without response, or crossed lines between two adjacent channels (i.e. both lines appear to have received a call when in fact only one has)?
1) Possible reasons for line-engagement or no-response on certain channels:
A. RJ11 jack might not be properly plugged in.
B. Outgoing phone line might have been short-circuited or faulty.
C. Modules might be loose, which resulted in bad connection
2) Line-crossing is usually a result of the 4 pins of the input RJ11 jack touching one another, thereby creating short-circuit among them.
How to properly configure tone analysis parameters for an analog board?
Tone is a rhythmic audio signal usually used for indicating line status, such as calling/called party's hang-up, line-engagement, etc. A standard tone is often a single-sine wave signal of 450Hz. However, certain smaller PBXs or key telephone systems might use other frequencies or even dual-tones. The Synway driver platform endows each channel with 2 independent tone-detectors, allowing them to analyze 2 different tones at one time.
1) Correctly define frequency characteristics (i.e. center frequency and bandwidth) of the tone.
The Synway driver platform supports detection and analysis of single and dual tones of any frequency. Single tone mode requires the predetermination of a center frequency and a bandwidth. Similar settings can be used for handling dual tones whose frequencies are close to each other, so long as the center frequency and bandwidth covers that of the two. Dual tone mode, however, requires two sets of predetermined center frequencies and bandwidths.
2) Correctly set characteristics of the wave form of the tone.
A. Dial Tone:
This is a continuous tone. Set the shortest continuous time duration for the tone, which is generally above 1.5.seconds.
B. Busy Tone:
The periodic duty ratio is 1:1 (i.e. equal duration for tone and silence). Set busy tone period and busy tone count threshold (to prevent misjudgment, the driver concludes that the tone is indeed a busy tone only when the successive ring count exceeds the threshold parameter).
C. Ringback Tone:
The periodic duty ratio is 1:4 (i.e. tone-to-silence ratio is 1:4). Set the continuous time duration for the tone (high LEV) and for silence (low LEV).
Misjudgment of tones is usually due to incorrect configuration of the above parameters. Analyze the tones using ShTA.exe under the driver installation directory (Refer to ShTA_UserManual.chm under the same directory). If this tool failed to analyze the tones, record the unknown tones, analyze their characteristics such as frequency and wave form with editing tools like Cooledit, then enter the correct parameters into the configuration file accordingly. Thus the system can judge the tone accurately.
Why does the analog trunk channel sometimes undesirably pick up busy tones?
Normal voice, when under the influence of poor lines and poor grounding might generate noise. Illusive busy tones that resemble the characteristics of a genuine busy tone can sometimes be found among these noises. The consequent effect can be minimized by increasing busy tone’s count threshold to filter out the illusive busy tones.
Why does the application fail to invoke the function SsmAutoDial to dial a number from the trunk channel?
The function SsmAutoDial only performs dial operation upon correct detection of dial tones on the analog trunk channel. Hence, the absence of dial tones, or failure to detect dial tones will result in the function call to be unsuccessful.
How does an analog trunk channel detect pickup from remote phone in a dial-up process?
When the remote end picks up the call, the trunk channel state will switch from ‘pickup’ to ‘connected’ in a dial-up process. If the telephone line connected with the trunk channel has customized the polarity reverse service, the function SsmGetPolarRvrsCount can be invoked to judge whether the remote end has picked up or not. The return value 1 indicates the pickup of the remote end.
Why does the analog trunk channel sometimes fail to detect hangup from remote end?
There might be two reasons for failure to detect remote hangup.
1) Fails to detect busy tones on the line. Refer to Question 7 “How to properly configure tone analysis parameters for an analog board?” in this chapter for busy-tone settings.
2) PBX has not sent busy tones.
How does the analog trunk module detect connection drop on a line?
To detect whether the connection on a line is normal or not, the analog trunk channel can invoke the function SsmGetLineVoltage and examine the voltage obtained by. If the line is ok, the voltage will be normal too.
Is it possible for driver to make a misjudgment when PBX plays prompt tones in a call from the analog trunk channel to a mobile phone?
Yes, the driver may misconclude that the analog trunk channel is in a ‘connected’ state.
Why does an analog trunk channel switch from "idle" to "ringing" only after two rings have been detected?
This has been set so in the item ‘AlwaysToRingingOnRingCntX’ of the configuration file ‘Shconfig.ini’, and can be modified for the same action to happen after one ring or multiple rings.
Why does an analog trunk channel take a longer time to determine a ringback tone when calling out?
A trunk channel will not return ‘ringback’ values before a full-cadence ringback tone is detected. i.e. it will determine a ringback tone only after the first ring from remote end has ended or the second ring starts.
When a remote phone places a call to an analog trunk channel, the phone cannot hear anything played by the channel, or hears only a short section before it is cut off. Why?
This happens if the trunk channel is set to stop playback upon detection of barge-in and the caller interrupts playback by talking. The option can be turned off.
What to do if a station on analog boards can hear echoes from itself?
Echoes are cancelled at the end they are produced. Therefore, for echoes produced at the end of analog boards, you can cancel them by changing the board model to SHT-16C-CT/PCI/EC or SHT-8C/PCI/EC which supports echo cancellation in hardware.
This can be done through an application to the telecoms office.