|Posted - 2/18/2002 8:48:42 AM |
I have the 5686D (Newest flash) It came even saying it was a V92 modem from the store. The diagnostics even show it saying v92. I currently use boo.net (innternet provider) all of their servers use v92. My modem connects only at v90 also even though I have compression turned on, when I hit the details after I connected it says compression (none).
What am I doing wrong??
Mobo - SH6 w/celeron 800 @ 1.14ghz (142x8)(Slotkit)
SDRAM - 192 pc 133
Video - Geforce 2 MX (32 megs)
Sound (on board)
Case - Generic (with front USB ports) + 400w power supply
USB - Everything (epson c60, Cannon scanner, zip 250, etc)
Modems - US Robotics 5686D & Sportster Voice 33.6
|Posted - 2/19/2002 9:19:16 AM |
Please post a modem log and you might check with your isp to see if they use another # for V92.Are you using any modem strings,if so remove them.
|Posted - 2/19/2002 9:28:24 AM |
|Posted - 2/19/2002 4:30:21 PM |
my modem log is as follows....
2-19-2002 19:15:44.741 - File: C:\WIN\System32\tapisrv.dll, Version 5.1.2600
02-19-2002 19:15:44.741 - File: C:\WIN\System32\unimdm.tsp, Version 5.1.2600
02-19-2002 19:15:44.741 - File: C:\WIN\System32\unimdmat.dll, Version 5.1.2600
02-19-2002 19:15:44.741 - File: C:\WIN\System32\uniplat.dll, Version 5.1.2600
02-19-2002 19:15:44.761 - File: C:\WIN\System32\drivers\modem.sys, Version 5.1.2600
02-19-2002 19:15:44.761 - File: C:\WIN\System32\modemui.dll, Version 5.1.2600
02-19-2002 19:15:44.761 - File: C:\WIN\System32\mdminst.dll, Version 5.1.2600
02-19-2002 19:15:44.761 - Modem type: U.S. Robotics 56K FAX EXT
02-19-2002 19:15:44.761 - Modem inf path: mdmusrgl.inf
02-19-2002 19:15:44.761 - Modem inf section: ModemUSR2082
02-19-2002 19:15:44.761 - Matching hardware ID: serenum\usr2082
02-19-2002 19:15:44.801 - 115200,8,N,1, ctsfl=1, rtsctl=2
02-19-2002 19:15:44.801 - Initializing modem.
02-19-2002 19:15:44.811 - Send: AT<cr>
02-19-2002 19:15:44.931 - Recv: <cr><lf>OK<cr><lf>
02-19-2002 19:15:44.931 - Interpreted response: OK
02-19-2002 19:15:44.941 - Send: AT&F&D2V1Q0E0S0=0&C1<cr>
02-19-2002 19:15:45.062 - Recv: <cr><lf>OK<cr><lf>
02-19-2002 19:15:45.072 - Interpreted response: OK
02-19-2002 19:15:45.082 - Send: AT&A3X4&B1<cr>
02-19-2002 19:15:45.202 - Recv: <cr><lf>OK<cr><lf>
02-19-2002 19:15:45.202 - Interpreted response: OK
02-19-2002 19:15:45.212 - Send: AT&A0<cr>
02-19-2002 19:15:45.332 - Recv: <cr><lf>OK<cr><lf>
02-19-2002 19:15:45.332 - Interpreted response: OK
02-19-2002 19:15:45.342 - Send: ATS7=60S19=0M1&M4&K1&H1&R2&I0B0X4<cr>
02-19-2002 19:15:45.472 - Recv: <cr><lf>OK<cr><lf>
02-19-2002 19:15:45.472 - Interpreted response: OK
02-19-2002 19:15:45.472 - Waiting for a call.
02-19-2002 19:15:45.482 - Send: AT#CID=1<cr>
02-19-2002 19:15:45.602 - Recv: <cr><lf>OK<cr><lf>
02-19-2002 19:15:45.602 - Interpreted response: OK
02-19-2002 19:15:45.612 - Send: ATS0=0<cr>
02-19-2002 19:15:45.733 - Recv: <cr><lf>OK<cr><lf>
02-19-2002 19:15:45.733 - Interpreted response: OK
02-19-2002 19:15:45.733 - 115200,8,N,1, ctsfl=1, rtsctl=2
02-19-2002 19:15:45.733 - Initializing modem.
02-19-2002 19:15:45.743 - Send: AT<cr>
02-19-2002 19:15:45.863 - Recv: <cr><lf>OK<cr><lf>
02-19-2002 19:15:45.863 - Interpreted response: OK
02-19-2002 19:15:45.873 - Send: AT&F&D2V1Q0E0S0=0&C1<cr>
02-19-2002 19:15:45.993 - Recv: <cr><lf>OK<cr><lf>
02-19-2002 19:15:45.993 - Interpreted response: OK
02-19-2002 19:15:46.003 - Send: AT&A3X4&B1<cr>
02-19-2002 19:15:46.123 - Recv: <cr><lf>OK<cr><lf>
02-19-2002 19:15:46.123 - Interpreted response: OK
02-19-2002 19:15:46.133 - Send: AT&A0<cr>
02-19-2002 19:15:46.253 - Recv: <cr><lf>OK<cr><lf>
02-19-2002 19:15:46.253 - Interpreted response: OK
02-19-2002 19:15:46.263 - Send: ATS7=60S19=0M1&M4&K1&H1&R2&I0B0X4<cr>
02-19-2002 19:15:46.394 - Recv: <cr><lf>OK<cr><lf>
02-19-2002 19:15:46.394 - Interpreted response: OK
02-19-2002 19:15:46.394 - Dialing.
02-19-2002 19:15:46.404 - Send: ATDT###########<cr>
02-19-2002 19:16:13.903 - Recv: <cr><lf>CONNECT 50666<cr><lf>
02-19-2002 19:16:13.903 - Interpreted response: Connect
02-19-2002 19:16:13.903 - Connection established at 50666bps.
02-19-2002 19:16:13.903 - Error-control off or unknown.
02-19-2002 19:16:13.903 - Data compression off or unknown.
02-19-2002 19:16:43.905 - Read: Total: 44016, Per/Sec: 1465, Written: Total: 9086, Per/Sec: 299
02-19-2002 19:18:43.908 - Read: Total: 432302, Per/Sec: 3235, Written: Total: 36358, Per/Sec: 227
02-19-2002 19:20:43.910 - Read: Total: 458801, Per/Sec: 220, Written: Total: 38530, Per/Sec: 18
02-19-2002 19:22:43.913 - Read: Total: 715822, Per/Sec: 2141, Written: Total: 79623, Per/Sec: 342
02-19-2002 19:24:43.915 - Read: Total: 736094, Per/Sec: 168, Written: Total: 85802, Per/Sec: 51
02-19-2002 19:26:43.918 - Read: Total: 782566, Per/Sec: 387, Written: Total: 88683, Per/Sec: 24
02-19-2002 19:28:43.921 - Read: Total: 782566, Per/Sec: 0, Written: Total: 88930, Per/Sec: 2
02-19-2002 19:30:43.913 - Read: Total: 948700, Per/Sec: 1396, Written: Total: 114894, Per/Sec: 218
posted by charles: http://www.usr.com/v92/v-upgrade.asp?patch=5686
I've already been there.... I downloaded all of the newest drivers and control center... still nothing..
Thanx... anything else to try?
|Posted - 2/19/2002 5:10:07 PM |
Unfortunately, I don't have first-hand experience with a USR V.92 modem, so my knowledge is limited; but...
I would suggest using Hyperterminal to dial test connections to your ISP (set up Hyperterminal as per:
Give the modem the init string
then try to dial;
I'm not 100% sure of what V.92-specific commands USR has, but see
Now, when you say you're not connecting at V.92, what exactly do you mean? There aren't any V.92 servers out (except in beta) that support PCM upstream, so the only things you can do with a V.92 server are Quick Connect and Modem on Hold. The actual modulation of the call will be V.90 - 56k downstream max and V.34 max up;
Both of these features require that the server side (and yours) be enabled for these features - it's entirely possible that your "V.92 server" doesn't have these enabled, but you should be able to determine that with Hyperterminal: on successive calls to the ISP, the handshake with Quick Connect should be completed in about half the time (10 seconds instead of 20); and, if you have 3-way calling, you should be able to put the modem in command mode after a connect ( +++ ) and give it the command to go on hold; or alternately, if you have caller id, to have someone ring your line (while connected but in command mode), and if you have given the modem proper commands to put modem-on-hold when a callwaiting comes in - it should work....
|Posted - 2/19/2002 6:03:00 PM |
I understand that I won't beable to use PCM but, I am not even using the new compression that is incorperated into v92. It doesn't connect any faster with the ISP (it takes about 20 sec)... I tried Hyperterminal and it says that I connected at v90....Have any other ideas??
|Posted - 2/19/2002 6:11:46 PM |
Also here is the Diagnostics that hyper terminal gave me:
U.S. Robotics 56K FAX EXT Link Diagnostics...
Carrier Freq (Hz) None/1920
Symbol Rate 8000/3200
Trellis Code None/64S-4D
Nonlinear Encoding None/ON
Preemphasis (-dB) 5/8
Recv/Xmit Level (-dBm) 22.6/8.7
Near Echo Loss (dB) 48.9
Far Echo Loss (dB) 0
Carrier Offset (Hz) 0
Round Trip Delay (msec) 7
Timing Offset (ppm) 5252
SNR (dB) 50.0
Speed Shifts Up/Down/Null 0/0/0
Status : uu,5,12N,12.1,-15,1N,000,50.1,-73.9,0
????????????? Whats next??
|Posted - 2/19/2002 6:56:47 PM |
New compression - V.44 isn't really part of V.92, although it is generally being introduced along with V.92.
USR Modems are the exception - their V.92 is V.92 only - no V.44; and, as you are experiencing, the V.92 that they've given you (Quick Connect & Modem-on-hold) has interoperability problems with at least some server-side modems.
My understanding is that USR is aware of problems, and there is later firmware that has not generally been released that may help....
I don't think there's too much you can do, but your diag results are incomplete - I would like to see results of
not just at i11 that you posted.
|Posted - 2/20/2002 10:56:50 PM |
I totally agree with Richard, most V.92 ISP can only
support MoH and QC at this moment, but some RAS servers
have those new features disabled by default
As to V.44, it seems that most RAS vendors already supported it earlier than V.92 new features like PCM
|Posted - 3/2/2002 9:27:48 PM |
USR modems do not support v44 at all. they are still working on it. I also had a 5686D. It is incompatible with practically EVERY server except 3com's in V92 mode. I completely agree with v.richard that USR isn't making the same quality product as before. By the way, KTDEVIL5, does controlcenter work on your modem? it doesn't work on mine.
|Posted - 3/13/2002 8:26:32 AM |
some of the modem will use a lucent chipset and some use the lucent chipset but as long as you are connecting at above 44,000 you are using the v.92 protocal, v.92 does not improve your connection speed it will just give you more features and you will have a more reliable connection.