PE> It would be nice to know who it was that called at this time...

MP>  I think it was me.

Well done!  Certainly the calling sequence you described matches.

PE> 6. Major problem - modem failed to connect and then failed to hang
PE> up!  Here is the log:

MP>  I rang the bbs the first time with MNP-10 enabled but my modem never
MP> connected. The second call I disasbled MNP-10 but your modem still
MP> connected with MNP-10. After connecting, binkley on my end sent its

Perhaps you didn't disable MNP-10 properly, or your modem has a bug
there?  Someone else might like to jump in and verify that the calling
modem should be able to disable MNP-10 from their end, it's not 
something that the called modem is allowed to force on you (of course
it can't force that on you, you may not support MNP-10!).  Yeah, it
definitely has to be either you made a typo, or you have a bug.  Have
you played with that before?

How about we agree on 12pm-2pm on Saturday and Sunday is the time where
you can try to break my modem again.  I would like to see any MNP-10
theories you have to be applied in full.  Basically, as I say below in
my modified Netcomm problem 6 below, I want anyone who has MNP-10 to
give it a go.  Using afterconn would be nice too.

MP> afterconn string to get stats after my modem went back online my end
MP> never got a YooHoo and in the end binkley hung up. On my next call I
MP> disabled the afterconn but I could never get through to you as it was
MP> busy the whole time. Later that night I connected perfectly. BTW I've

Was that the first time you used MNP10 and the first time you used
afterconn or what?

MP> got about 200k of detailed logs of my calls if you want them but none
MP> of the dates or times are correct in them.

Not related to Nostradamus by any chance?  :-)  I don't have a use
for the stats at the moment (I don't know what to do with them), so
no, I don't need them at the moment.  If you want to detail problems
you are having connecting to my Netcomm, that's a different story.
You've noted one already, failure to connect when having MNP-10
enabled.  If you can give me more info, like 30% of your calls fail,
that would be good.  BFN.  Paul.


6. Major problem - modem failed to connect and then failed to hang
up!  Here is the log:

+ 30 Mar 11:14:04.50   Sent-Z/32 c:\binkley\Outbound\02c703a6.pnt\0000ffe2.sa0
* 30 Mar 11:14:04.78   Session with 3:711/934.30 Time: 00:01:11 Cost: $0.00
# 30 Mar 11:14:06.53   Disconnect reason = 2:0
> 30 Mar 11:14:14.00   ATS42?
# 30 Mar 11:14:14.00   002 00000010
# 30 Mar 11:14:14.00   OK
> 30 Mar 11:14:14.00   AT%L
# 30 Mar 11:14:14.03   050

# 30 Mar 13:08:20.46   RING
> 30 Mar 13:08:20.62   ATA
# 30 Mar 13:08:22.43   Initialise.. 00003mS
# 30 Mar 13:08:23.03   Offhook.. 00599mS
# 30 Mar 13:08:23.06   Connect Auto.. 00604mS
# 30 Mar 13:08:54.84   Failed to connect within S7 time 32607mS
# 30 Mar 13:08:55.93   NO CARRIER
# 30 Mar 13:08:55.96   Disconnect reason = 8:0
# 30 Mar 13:10:09.15   RING
> 30 Mar 13:10:09.31   ATA
# 30 Mar 13:10:11.03   Initialise.. 00003mS
# 30 Mar 13:10:11.62   Offhook.. 00599mS
# 30 Mar 13:10:11.65   Connect Auto.. 00604mS
# 30 Mar 13:10:23.28   Auto OK.. 0047 12339
# 30 Mar 13:10:23.31   RLSD UP 12342mS
# 30 Mar 13:10:23.34   CTS UP 12346mS
# 30 Mar 13:10:23.37   Connected at 0047 12352
# 30 Mar 13:10:23.40   Initial EQM = 0049 12358
# 30 Mar 13:10:23.43   ARQ Start 00000
# 30 Mar 13:10:23.46   V.42 attempt 00000
# 30 Mar 13:10:24.75   SYN detected: extended MNP timeout 01380
# 30 Mar 13:10:24.84   Waiting for LR 01500
# 30 Mar 13:10:24.87   LR Received..
# 30 Mar 13:10:24.90   Length=043
# 30 Mar 13:10:24.93   Type=001
# 30 Mar 13:10:24.96   Link level=002
# 30 Mar 13:10:25.03   1: Protocol ID parameter 001 006 001 000 000 000 000 255
# 30 Mar 13:10:25.06   2: MNP framing mode=003sync
# 30 Mar 13:10:25.09   3: Window size=008
# 30 Mar 13:10:25.12   4: Packet size=00064
# 30 Mar 13:10:25.18   8: Fixed Header Sizes   Max data size = 256   MNP10 requested
# 30 Mar 13:10:25.25   14: V.42bis capable with table size: 02048  Max
string length: 00064
# 30 Mar 13:10:25.28   9: MNP5 disabled
# 30 Mar 13:10:25.34   12: MNP10 paramsSYN detected: extended MNP timeout 01580
# 30 Mar 13:10:25.46   =04 433D00FE Microcom
# 30 Mar 13:10:25.56   Unknown parameter 013 045 001 002 001 006 001 000
000 000 000 255 002 001 003 00
# 30 Mar 13:10:25.62   3 001 008 004 002 064 000 008 001 147 014 004 003
008 000 064 009 001 001 012 00
# 30 Mar 13:10:25.65   4 067 061 000 254 013 002 038 040 017 001 000
# 30 Mar 13:10:25.68   Return response LR 01640
# 30 Mar 13:10:25.71   Wait for LA 01680
# 30 Mar 13:10:25.75   Another LR received 01680
# 30 Mar 13:10:25.78   Return response LR 01680
# 30 Mar 13:10:25.81   Wait for LA 01720
# 30 Mar 13:10:25.84   Another LR received 01720
# 30 Mar 13:10:25.87   Return response LR 01720
# 30 Mar 13:10:25.90   Wait for LA 01760
# 30 Mar 13:10:27.09   LA Time Out 03760
# 30 Mar 13:10:28.03   Another LR received 04720
# 30 Mar 13:10:28.15   Return response LR 04720
# 30 Mar 13:10:28.18   Wait for LA 04740
# 30 Mar 13:10:28.21   Another LR received 04840
# 30 Mar 13:10:28.28   Return response LR 04840
# 30 Mar 13:10:28.31   Wait for LA 04880
# 30 Mar 13:10:28.34   LA rx 04940
# 30 Mar 13:10:28.37   MNP succeed 04940
> 30 Mar 13:17:48.50   dropping DTR
> 30 Mar 13:30:04.06   dropping DTR
> 30 Mar 13:41:13.65   dropping DTR
> 30 Mar 13:52:01.25   dropping DTR
> 30 Mar 14:04:49.81   dropping DTR
> 30 Mar 14:17:01.31   dropping DTR

Note that 6 hours later, when I discovered the modem still off-hook,
the Carrier Detect light was not on, but the "On hook" light was on.
I dropped DTR several times and the modem refused to hang up.  
I tried going "+++", but I was not expecting that to work, because I
have that disabled.  I had to physically switch the modem off!!!  I
NEED DTR to work properly, or at least I need the modem to HANG UP
if it fails to connect.  An ISP that I know (Matra) has reported the
same problem.  Oh, I am running with AT\V6 now, as you can tell from
the detailed stats.  The ISP says that when the problem happens for
them, and someone tries to ring, the line appears as not-answering,
as opposed to engaged.  I did not think to try this myself at the 
time.  Also, when I typed the "+++" etc to the modem, I did not take
careful note of the modem lights, but I *think* the TD light flashed
with the characters.

I sent out a general broadcast to my users about this problem, and
got the following response:

*******************************************************************
Date:   1996-04-01 17:10:30
From:   Matthew Parker
To:     Paul Edwards
Subj:   modem problem
Attr:   recvd 
Area:   LOCSYSOP                      

On Mar 30 22:10, 1996, Paul Edwards of 3:711/934.9 wrote:

PE> It would be nice to know who it was that called at this time...

 I think it was me.

PE> 6. Major problem - modem failed to connect and then failed to hang
PE> up!  Here is the log:

 I rang the bbs the first time with MNP-10 enabled but my modem never
connected. The second call I disasbled MNP-10 but your modem still
connected with MNP-10. After connecting, binkley on my end sent its
afterconn string to get stats after my modem went back online my end
never got a YooHoo and in the end binkley hung up. On my next call I
disabled the afterconn but I could never get through to you as it was
busy the whole time. Later that night I connected perfectly. BTW I've
got about 200k of detailed logs of my calls if you want them but none
of the dates or times are correct in them.
Matthew
*******************************************************************

The user is using a Microcom Deskporte Fast 28.8.  This "afterconn"
that he is talking about is a feature whereby after he gets a
CONNECT string, he can send "+++" then do some stats, e.g. AT%L or
something.  It could be that, or it could be the very unusual MNP10,
or it could be something else.  I will see if I can get some more
MNP data.  Perhaps the solution to this problem could be to disable
MNP10 on my Netcomm.  I will inform the ISP to have a go at doing
that.
@EOT:

---