🚀 go-pugleaf

In article <06qlpUAF6Fj5EwQW@jessikat.fsnet.co.uk>, Robin Becker 
<robin@jessikat.fsnet.co.uk> wrote:
>In article <Fyts1M.4Er@dgsys.co.uk>, Dan Glover <news@dangl.demon.co.uk>
>writes

>>If you have a voice modem it *may* be able to detect speech and return
>>a suitable result which can be trapped by your chat script or equivalent.
>>
>>Alternatively contact BT and ask them why they don't have sufficient
>>capacity to route your call to Energis.  I still get through first
>>time, every time, calling from 01634-land.

>It's a bit odd since it was aok for three weeks and went bad
>thurs/friday only this week. I looked in the source and wvdial seems to
>suggest it can detect voice lines, but I have no idea how to set up the
>modem US Robotics 56k EXT to do the check and looking through the
>tech_ref.pdf that came with it I'm not certain it can do so.

Afraid I can't help with the specifics of the USR modem, on my Pace 56k
internal it looks like AT#CLS=8 makes it return VCON if it thinks
there's speech.  Not yet tested in "live" operation though.  No doubt
a full manual of "AT" codes for your modem is available somewhere
(website, perhaps?).

As to why the problem has only recently started: fault reducing capacity
between BT and Energis?  There have been a handful of such things
reported/fixed over the past few weeks.  Freeserve/Energis do eventually
seem to escalate the problem if they get enough reports.  Including your
dialling code is essential, given the geographical nature of things.

Dan

-- 
Dan Glover (dan@dangl.demon.co.uk)