[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Re: Remote Desktop --> Zoom Modem for CLI and Voice
Hi Rob
Hopefully this is on-topic sufficiently to stay on list :-)
Yes - I've applied the inf changes for CLID - that works fine. An using
Cortex auto-dialler I can get Cortex to ring my mobile and deliver a speech
synth message perfectly well. But I can't get the modem/Cortex to
automatically answer the phone. If I manually answer there is the
crackly/hissy noise - also heard on phone attached to the passthrough port
of the modem and on the mobile which initiated the call.
Gooling gets mixed reports for this modem, it seems to work with some apps
for some people. Zoom position seems to be they only support the
CommunicateLite program and there was a suggestion that this was not TAPI.
But google is not an oracle, so I am not totally convinced.
The modem log shows the modem generates an error during the process -
obviously doesn't like something ... always seems to be the at+vls=1, but I
wodner if something else is not initialisedcorrectly ...so I did wonder if
there is some way to modify the .inf to get different strings. I either
need
to try using hyperterm - which means closing Cortex, or via TAPI browser,
if that allows resource sharing. Or may be some other application handling
voicemail.
Here's a section of the log from just after the CLID string accepted :-
10-13-2007 17:42:53.500 - TSP(0000): LINEEVENT: LINE_NEWCALL
10-13-2007 17:42:53.500 - TSP(0000): LINEEVENT: LINECALLSTATE_OFFERING
10-13-2007 17:42:55.265 - TSP(0000): Answering Call
10-13-2007 17:42:55.265 - TSP(0000): LINEEVENT: LINECALLSTATE_ACCEPTED
10-13-2007 17:42:55.265 - Answering the call.
10-13-2007 17:42:55.265 - 115200,8,N,1, ctsfl=1, rtsctl=2
10-13-2007 17:42:55.281 - Send: at+fclass=8<cr>
10-13-2007 17:42:55.281 - Recv: <cr><lf>OK<cr><lf>
10-13-2007 17:42:55.281 - Interpreted response: OK
10-13-2007 17:42:55.296 - Send: at+vtd=10<cr>
10-13-2007 17:42:55.296 - Recv: <cr><lf>OK<cr><lf>
10-13-2007 17:42:55.296 - Interpreted response: OK
10-13-2007 17:42:55.312 - Send: at+vsm=130,8000,0,0<cr>
10-13-2007 17:42:55.312 - Recv: <cr><lf>OK<cr><lf>
10-13-2007 17:42:55.312 - Interpreted response: OK
10-13-2007 17:42:55.328 - Send: at+vit=6<cr>
10-13-2007 17:42:55.328 - Recv: <cr><lf>OK<cr><lf>
10-13-2007 17:42:55.328 - Interpreted response: OK
10-13-2007 17:42:55.343 - Send: at+vls=1<cr>
10-13-2007 17:42:55.500 - Received DLE Raw= 82, Meaning is Ring.
10-13-2007 17:43:02.234 - Recv:
<cr><lf>ERROR<cr><lf>
10-13-2007 17:43:02.234 - Interpreted response: Error
10-13-2007 17:43:02.234 - Hanging up the modem.
10-13-2007 17:43:02.250 - Send: ATH<cr>
10-13-2007 17:43:14.609 - Timed out waiting for response from modem
10-13-2007 17:43:14.609 - Send: ATH<cr>
10-13-2007 17:43:15.312 - Recv: <cr><lf>OK<cr><lf>
10-13-2007 17:43:15.312 - Interpreted response: OK
10-13-2007 17:43:15.312 - 115200,8,N,1, ctsfl=1, rtsctl=2
10-13-2007 17:43:15.312 - Initializing modem.
10-13-2007 17:43:15.312 - DSR is low while initializing the modem. Verify
modem is turned on.
10-13-2007 17:43:15.328 - Recv: <cr><lf>OK<cr><lf>
10-13-2007 17:43:15.328 - Interpreted response: OK
10-13-2007 17:43:15.328 - Send: AT<cr>
10-13-2007 17:43:15.328 - Recv: <cr><lf>OK<cr><lf>
10-13-2007 17:43:15.328 - Interpreted response: OK
10-13-2007 17:43:15.375 - Send:
AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W0<cr>
10-13-2007 17:43:15.515 - Recv: <cr><lf>OK<cr><lf>
10-13-2007 17:43:15.515 - Interpreted response: OK
10-13-2007 17:43:15.515 - Send:
ATS7=60M1+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr>
10-13-2007 17:43:15.531 - Recv: <cr><lf>OK<cr><lf>
10-13-2007 17:43:15.531 - Interpreted response: OK
10-13-2007 17:43:15.531 - Waiting for a call.
10-13-2007 17:43:15.531 - Send: at+vcid=1<cr>
10-13-2007 17:43:15.968 - TSP(0000): Dropping Call
10-13-2007 17:43:16.375 - Recv: <cr><lf>OK<cr><lf>
10-13-2007 17:43:16.375 - Interpreted response: OK
10-13-2007 17:43:16.390 - Send: ATS0=0<cr>
10-13-2007 17:43:16.390 - Recv: <cr><lf>OK<cr><lf>
10-13-2007 17:43:16.390 - Interpreted response: OK
10-13-2007 17:43:16.390 - TSP Completing Async Operation(0x00010099) Status
0x80000048
10-13-2007 17:43:16.390 - TSP(0000): LINEEVENT:
LINECALLSTATE_DISCONNECTED(0x1)
10-13-2007 17:43:16.390 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
10-13-2007 17:43:16.390 - TSP Completing Async Operation(0x00010088) Status
0x00000000
10-13-2007 17:43:16.437 - TSP(0000): Closing Call
10-13-2007 17:43:50.250 - Session Statistics:
10-13-2007 17:43:50.250 - Reads : 36 bytes
10-13-2007 17:43:50.250 - Writes: 96 bytes
10-13-2007 17:43:50.359 - File: C:\WINDOWS\system32\tapisrv.dll, Version
5.1.2600
10-13-2007 17:43:50.359 - File: C:\WINDOWS\system32\unimdm.tsp, Version
5.1.2600
10-13-2007 17:43:50.359 - File: C:\WINDOWS\system32\unimdmat.dll, Version
5.1.2600
10-13-2007 17:43:50.359 - File: C:\WINDOWS\system32\uniplat.dll, Version
5.1.2600
10-13-2007 17:43:50.359 - File: C:\WINDOWS\system32\drivers\modem.sys,
Version 5.1.2600
10-13-2007 17:43:50.359 - File: C:\WINDOWS\system32\modemui.dll, Version
5.1.2600
10-13-2007 17:43:50.359 - File: C:\WINDOWS\system32\mdminst.dll, Version
5.1.2600
10-13-2007 17:43:50.359 - Modem type: Zoom V.92 PCI Voice Faxmodem
10-13-2007 17:43:50.359 - Modem inf path: oem15.inf
10-13-2007 17:43:50.359 - Modem inf section: Modem
10-13-2007 17:43:50.359 - Matching hardware ID:
pci\ven_14f1&dev_10b4&subsys_9300141d
On 10/14/07, Rob Iles <rob.iles@xxxxxxx> wrote:
>
> The default (supplied) driver (.inf) file needs modifying for
callerID
> to
> work properly - - I assume you've already found and applied these
changes
> -
> if not, let me know, and I'll try to dig them out - - it's a fairly
subtle
> change to the expected message format.
>
> Are you using Cortex (and nothing else) to control the dial out/speech
> synth/dtmf functionality?
>
>
>
[Non-text portions of this message have been removed]
UKHA_D Main Index |
UKHA_D Thread Index |
UKHA_D Home |
Archives Home
|