Sure, Mike! Here's some tips that were e-mailed from your former desk:
----------------------------------------
Date: Tue, 18 Mar 1997 09:56:49 -0500
From: ablack@smtp.microcom.com (Allan Black)
To: Portmaster-Users@livingston.com
Subject: FW: Problem with Microcom ISPorte and Livingston PM2E
Sender: owner-portmaster-users@livingston.com
Reply-To: ablack@smtp.microcom.com (Allan Black)
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Description: cc:Mail note part
All,
Here are some basic fixes for ISPorte.
1. Update Firmware on your ISPorte Modems to ver. 1.1.18. There is
alot of old code out there and we know that 1.1.18 fixes alot of
disconnect issues. ISPorte firmware can be found at
FTP.microcom.com/pub/isporte/firmware.
2. A good init string is (AT&f$b115200%u1-o4Q2-j0-k0&d2*w)
3. Some optional AT commands that you might want to add.
at*Y2 - Microcom modems look for DTR to be HIGH in order to answer
the call. If the terminal server drops DTR, the caller
gets a ring-no-answer (note; this is a very common
problem). *Y2 will BUSY the modem if DTR is dropped and
the caller will get rolled over past the now BUSY port thus
cutting down the problems of ring-no-answer.
atS2=0 - Turns off +++ command mode to the modem thus preventing
users from changing modem settings.
at-H1 - Puts modem in DUMB Mode which means that the modem will not
take +++ command mode changes from the users and init
string commands from the terminal server. PortWatch would
be the only way to change settings on the modems therefore
making the system much less susceptible to problems caused
by modems being reinitialized.
Give these a try. I'm sure you will see good results.
Thanks,
Allan
______________________________ Forward Header __________________________________
Subject: FW: Problem with Microcom ISPorte and Livingston PM2E
Author: Mike Moss <mossm@sysexp.com> at smtp
Date: 3/17/97 6:24 PM
This is Larry from Mike's terminal. Looks like a possible answer.
------------------------------------------------------------------------
-----
SYSTEMS EXPRESS CORPORATION
Mike Moss - ISP Account Manager
10801 Southern Loop Blvd
Pineville, NC 28134-7384
v: 704-583-9911 ext.108 f: 704-583-9922
"Networking World Class Products"
Livingston, Cisco Enterprise, CiscoPro, Microcom, Adtran, Ascend,
Pairgain, BellSouth DSA
http://www.sysexp.com
mailto:moss@sysexp.com
------------------------------------------------------------------------
-----
>----------
>From: Ed Manaman[SMTP:edl@rock.spectra.net]
>Sent: Monday, March 17, 1997 1:19 PM
>To: Jason Fiset
>Cc: portmaster-users@livingston.com
>Subject: Re: Problem with Microcom ISPorte and Livingston PM2E
>
>
>I wouldn't rule out the telco, but you always want to make sure you're
>setup correctly. Here is a string I use, with all of my microcom modems
>including 60 someodd ISPORTE modems:
>
>"at&f&w\r^OK^at&c1&d2$b115200s0=1&w\r^OK"
>
>Our ComOs is 3.3.3.
>
>
>
>Ed
>
> -------------------------------------------
>| e-mail: elongstr@spectra.net |
>| WWW: http://www.spectra.net/~elongstr |
>| Voice: 607-798-7300 |
>| Fax: 607-798-8305 |
>| Data: |
> -------------------------------------------
>
>
>On Mon, 17 Mar 1997, Jason Fiset wrote:
>
>>
>> We have a livingston PM2E w/ ComOS3.5 and we have just recently aquired a
>> Microcom ISPorte with 8 modem ports. We are testing this setup because >>
we had numerous problems with disconnects using consumer-grade modems. >> It
turns out we still have the problem and we are getting rather >>frustrated.
>>
>> Is there an INIT string that someone has for this setup? I've spoken
>> with Livingston tech support and they said that it was most likely my
>> modems that were causing the disconnects (Lost-Carrier is the the
>> Acct-Terminate-Cause) which is why we are evaluating the Microcom ISPorte.
>> I've ruled out the telco - they have tested the lines and they claim
>> there are no problems.
>>
>> The only other thing I can think of doing is swapping out the PM2E and
>> put in a Computone PowerRack.
>>
>> Also note that I have a problem with a remote portmaster and so I'm
>> thinking that maybe there is a problem with the portmasters - I got both
>> of them at the same time.
>>
>>
>> ------------------------------------------------------------------------
>> Jason Fiset - RedHat 4.0 Based servers
>> Systems Manager - Mountain Internet - Secure Web Servers
>> jfiset@mountain-inter.net - Custom Programming
>> http://www.mountain-inter.net/~jfiset
>>
>Content-Type: text/plain; charset=US-ASCII; name="RFC822 message headers"
Content-Transfer-Encoding: 7bit
Content-Description: cc:Mail note part
Content-Disposition: inline; filename="RFC822 message headers"
Received: from sw.microcom.com (207.31.204.1) by smtp.microcom.com with SMTP
(IMA Internet Exchange 2.1 Enterprise) id 000094B3; Mon, 17 Mar 97 18:26:55
-0500
Received: from sw.microcom.com (root@localhost) by sw.microcom.com (8.7.5/8.7.3)
with ESMTP id SAA04525 for <ablack@smtp.microcom.com>; Mon, 17 Mar 1997 18:24:47
-0500 (EST)
Received: from sec.sysexp.com ([207.201.196.83]) by sw.microcom.com
(8.7.5/8.7.3) with SMTP id SAA04521 for <ablack@smtp.microcom.com>; Mon, 17 Mar
1997 18:24:46 -0500 (EST)
Received: by sec.sysexp.com with SMTP (Microsoft Exchange Server Internet Mail
Connector Version 4.0.993.5)
id <01BC3300.6E2B2870@sec.sysexp.com>; Mon, 17 Mar 1997 18:24:20 -0500
Message-ID: <c=US%a=_%p=Systems_Express_%l=SEC-970317232419Z-972@sec.sysexp.com>
From: Mike Moss <mossm@sysexp.com>
To: "'Allen Black'" <ablack@smtp.microcom.com>
Subject: FW: Problem with Microcom ISPorte and Livingston PM2E
Date: Mon, 17 Mar 1997 18:24:19 -0500
X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.993.5
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit