the issue is that no people want surprise, especially for those non technical people. OBIHAI should provide an configuration for business people and non-technical people to use.
OBIHAI support is excellence, but you need to be very technical in order to isolate the problem. In fact, i have many issues with OBI110, include the voice quality issue. sound issue. The hardware design is really outdated (no automatic voice gain control?, slow CID detection, even need to verify the CID format.. we are in 2010 now). The whole design should leverage latest cloud technology and strong computing power instead of 10 year ago design concept. Why bother to config within the device as long as it connect to internet or computer is very generally available now. Look at the reply, i need to find my way to solve an problem and still not know what is the side effect....
The following is reply from OBIHAI support,
Since you are calling in/out through FXO port for the conference call, it is very likely the long silence detection (default 60 seconds) kicked in and terminated your call. It will happen when either side keeps silence over 60 seconds or presses “mute” button on the phone over 60 seconds. The setting you might look into is:
Physical Interface à LINE port à PSTN Disconnect Detection à DetectFarEndLongSilence & SilenceTimeThreshold & SilenceDetectSensitivity .
- DetectFarEndLongSilence à disabled (turn off long silence detection completely)
- SilenceTimeThreshold à increase this period (60 seconds à 600 seconds, for example)
- SilenceDetectSensitivity à lower this value
Adjust these parameters to see if you can solve the call drop issue. |
發表於 2011-4-11 13:55
|