ATS$ on DSP's console(chdev mdm x, x=1..n) shows this: S77 Bit Mapped V.92 Contol 1 = V.92 Feature Disable 2 = V.92 PCM Upstream Disable 4 = V.92 Quick Connect P1 Disable 8 = V.92 Quick Connect P2 Disable Try to set S77=15. It will disable all V.92 activity. 15 = (8+4+2+1) S78 V.92 Modem On Hold Timeout Setting S78=0 will disable v.92 moh. Maybe this can help you. Adam Barnhill wrote:
We currently utilize DNIS to service users with 2 numbers. Both numbers roll to the same trunk group and are setup via DNIS AT commands. A v.90/v.92 and a v.34 line. The V.34 number is used when due to firmware or other factors it's better for them to get a stable V.34 connect than trial with the v.90 handshakes.
We do this by setting our V.90 number with AT&N0, and our V.34 with AT&N14&U1. Since V.92 has been turned on, these floor/ceiling values no longer work, and a v.92 53.3 connection is successfully connected on the V.34 line. These ceiling values weren't intended to work with V.92. It notes in the documentation that it only refers to x2/v90.
So in order to bypass this little issue, I want to disable V.92 (on V.34 number) and therefore reenable the Ceiling values. According to TCM, S77.0 Register controls V.92 Master setting. On (1) Default Disabled (2)
Unfortunately ATs77.0=2 causes the modem not to answer. Tacking on autoanswer s0=0 or s0=1 doesn't help.
Does anybody know an AT command to disable V.92 on HiperDSPs? The S-registers apparently don't work, is there a +PIG or & type command to do this?
-- Adam Barnhill
------------------------------------------------------------------------
_______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc
-- alex, ICQ# 219089461, Current status