PE> Binkley 2.60 should operate the same as BTPE 4.00 in that respect, as
BG> Well it doesn't, and it costs me 12c every time it recycles too.
PE> You don't actually know, since you've never tried Binkley 2.60. I
PE> bet I am right.
BG> Oh come on Paul, the modem dials, the remote answers, it hears the STD
BG> pips, it drops carrier and redials. Every time it does that, Telstra
BG> charges me a 12c connection fee. It soon adds up, too. That's with BTPE
Read what I said. "You don't actually know, since you've never tried
Binkley 2.60". You said above "it doesn't behave like Binkley 2.60".
I don't believe you. I bet I am right, and you will have the same
problem with Binkley 2.60.
BG> 4.0, which I thought was your recompile of Binkley 2.60. If not, what is
BG> it?
It is. And I bet it behaves identically. If you try out 2.60, and
it does the same thing, can you ask the question in BINKLEY, as a
problem with 2.60, so that you might get the proper answer.
BG> Dunno, I'd be more inclined to go back to 2.59 with EMSI connects if I
BG> can't figure out how to get ModemTrans to work properly.
PE> That should be fine, although you miss the Afterconnect then.
BG> I don't normally use that function anyway. I do use Aftercall though.
What a shame that YOU asked me to WRITE that then.
PE> Just disable busy-detect for all calls in the meantime anyway,
PE> why do you care? Binkley will redial anyway. BFN. Paul.
BG> But only after the modem times out, say 60 seconds. I want it to recognise
Sounds like the end of the world to me.
BG> BUSY and redial immediately, just like a decent modem should. Only hppens
A decent modem would detect BUSY.
BG> when dialling STD via your exchange too. Other STD calls work just fine.
A decent mdoem would detect BUSY. Anyhow, I thought you were switching
to Optus? Optus doesn't have pips. BTW, you were very lucky relying
on the V32b. I sent in a message to my NC to get V34 added, which he
seems to have done without disabling V32b. Very lucky indeed.
BFN. Paul.
@EOT:
---
* Origin: X (3:711/934.9)
|