| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | USR Courier |
david, at 21:26 on Feb 26 1996, you wrote to Bill Grimsley... db>> 'cept me - I'm getting "Connect 28800/Lap-M/V.42Bis/V.34" each and db>> every time now, with no failed connections. BG> BG> With NetComm to NetComm, I'd expect nothing else. :) db> Oh YEAH?!?! ;-) Of course! I'd expect that any two modems of the same type should give better results than two totally different models. BG> It could indeed be related to his lines. Seen my aftercall stats yet? db> Yep - whilst some of 'em are obvious, let's actually start *explaining* 'em db> in *detail* so that we can see *precisely* what's going on. I'm just db> guessing when I look at those since I don't have a USR modem, nor am I used db> to getting such detailed line information out of a modem. These figures are the easiest to interpret... # 25 Feb 09:58:12.16 Freq Level # 25 Feb 09:58:12.16 150 40 # 25 Feb 09:58:12.19 300 29 # 25 Feb 09:58:12.19 450 27 # 25 Feb 09:58:12.22 600 27 # 25 Feb 09:58:12.25 750 27 # 25 Feb 09:58:12.25 900 27 # 25 Feb 09:58:12.28 1050 28 # 25 Feb 09:58:12.28 1200 28 # 25 Feb 09:58:12.31 1350 29 # 25 Feb 09:58:12.35 1500 30 # 25 Feb 09:58:12.35 1650 31 # 25 Feb 09:58:12.38 1800 31 # 25 Feb 09:58:12.38 1950 32 # 25 Feb 09:58:12.41 2100 33 # 25 Feb 09:58:12.41 2250 34 # 25 Feb 09:58:12.44 2400 35 # 25 Feb 09:58:12.47 2550 35 # 25 Feb 09:58:12.47 2700 36 # 25 Feb 09:58:12.50 2850 37 # 25 Feb 09:58:12.50 3000 38 # 25 Feb 09:58:12.53 3150 39 # 25 Feb 09:58:12.53 3300 41 # 25 Feb 09:58:12.56 3450 44 # 25 Feb 09:58:12.60 3600 50 # 25 Feb 09:58:12.60 3750 59 Basically, once the level drops below around -35dBm for a given frequency (could be marginally higher at -33dBm, I'm not sure), the modems should shift down to the next highest freq/level pair, and the above stats indicate that the highest carrier frequency for a successful link is around 2250Hz, say 21600 or 24000 bps (or a step higher on modems supporting 64-state trellis coding). db> BTW, I just confirmed with NetComm today that the M34F upgrade to V.34bis db> (their title, not mine - I asked about "V.34+") The "V.34+" was basically USR's own working name for what will soon be ratified as V.34bis by the ITU-TSS (July 1996 is the expected date). db> will definitely require a Rockwell chipset replacement. Gloat mode "on"... db> ;-) That was common knowledge, so no surprises there at all. No gloating either, although now that USR are about to release their latest Courier flash-ROM which now supports such goodies as carrier loss redial, distinctive ring, and Caller ID, one could certainly be tempted... :) BG> Just as long as somebody walks away with his M34F... :) db> What, no sacrificial ropeless bungee from the window?!?! ;-) No, I'm not that cruel. Unless, of course, you meant for Paul... :) Regards, Bill --- Msgedsq/2 3.20* Origin: Logan City, SEQ (3:640/305.9) SEEN-BY: 640/305 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.