Re: Future or TAPI

Tech-Archive recommends: Speed Up your PC by fixing your registry

Andreas,

what should we learn from it? Some modems support
call progress detection in data mode and some don't?

Maybe it's the inf files that make the diference?

At some point in time we should really try to get one
of the developers of Unimodem for a chat, to clear
some of the many questions we are always speculating
about. Shouldn't cost too much resources at MS and
would really help us a lot! What do you think?


Best regards,

Matthias Moetje
-------------------------------------
TERASENS GmbH
Ackermannstraße 3
80797 München
-------------------------------------
Fon: +49 89 143370-0
Fax: +49 89 143370-22
e-mail: moetje at terasens dot de
www: www.terasens.de
-------------------------------------



"Andreas Marschall [MVP TAPI]" <Andreas.Marschall@xxxxxxxxxx> wrote in
message news:%23IACPvUYFHA.1384@xxxxxxxxxxxxxxxxxxxxxxx
> "Matthias Moetje" <moetje@xxxxxxxxxxxxxxxxxxx> schrieb im Newsbeitrag
> news:%23Q4FNjUYFHA.3840@xxxxxxxxxxxxxxxxxxxxxxx
> > Andreas,
> >
> > I have tried on my XP notebook now with internal modem.
> > I don't get a connected state either here. (see logs below)
> >
> > From your logs I can see 3s between ATDT and the
> > response OK. There are also 3s between the call state
> > proceeding and connect. If the OK was just to confirm
> > the reception of the ATDT command it wouldn't take 3s,
> > so your modem might report OK instead of CONNECT
> > and the negotiation might be very quick...
>
>
> Matthias,
> no the negotiated isn't quick (taking over 10 sec) and it hasn't even
begun
> because I haven't done a lineAnswer() at the called side at this time.
>
>
> > My modem doesn't respond to the CONNECT command,
> > too. After 31s (meanwhile I had picked up and down the
> > phone) it responds with a busy and the event cause is
> > even CEC_DISCONNECT_BUSY!
> >
> > Can you try to call a phone instead of a modem, don't
> > take the call and see if you receive CONNECT?
>
>
> Sure, here are the logs for modem making data call to phone (optiPoint,
both
> attached to a HiPath 3000):
> it's the same result (_CONNECTED altough not answered).
>
> TB20:log:
> 18:55.38.646 : Calling lineInitializeEx
> lphLineApp=x2356d0
> hInstance=x1000000
> lpfnCallback=x10158d7
> lpszFriendlyAppName=x6f66c
> lpdwNumDevs=x6f644
> lpdwAPIVersion=x6f6d8
> ->dwAPIVersion=x20002
> lpInitExParams=x6f62c
> ->dwOptions=x3
> 18:55.38.656 : lineInitializeEx returned SUCCESS
> num line devs = 47
> 18:55.44.745 : Calling lineOpen
> hLineApp=x800003ee
> dwDeviceID=x0
> lphLine=x2356e8
> APIVersion=x20002
> dwExtVersion=x0
> dwCallbackInstance=x0
> dwPrivileges=x6
> dwMediaModes=x10
> lpCallParams=x0
> 18:55.45.355 : lineOpen returned SUCCESS
> 18:55.49.682 : Calling lineMakeCall
> hLine=x10081
> lphCall=x2357b0
> lpszDestAddress=x6f5e4
> dwCountryCode=x0
> lpCallParams=x0
> 18:55.49.682 : lineMakeCall returned x1002b
> 18:55.49.692 : received LINE_REPLY
> device=x0
> cbInst=x0
> param1=x1002b,
> param2=x0,
> param3=x103c5,
> 18:55.49.692 : received LINE_CALLSTATE
> device=x103c5
> cbInst=x0
> param1=x10, DIALING
> param2=x0,
> param3=x0,
> 18:55.49.702 : received LINE_CALLSTATE
> device=x103c5
> cbInst=x0
> param1=x200, PROCEEDING
> param2=x0,
> param3=x0,
> 18:55.52.746 : received LINE_CALLSTATE
> device=x103c5
> cbInst=x0
> param1=x100, CONNECTED
> param2=x0,
> param3=x0,
>
> ModemLog:
> 05-25-2005 18:55:44.755 - File: F:\WINNT\system32\unimdm.tsp, Version
> 5.0.2195 - Retail
> 05-25-2005 18:55:44.755 - File: F:\WINNT\system32\unimdmat.dll, Version
> 5.0.2195 - Retail
> 05-25-2005 18:55:44.755 - File: F:\WINNT\system32\uniplat.dll, Version
> 5.0.2195 - Retail
> 05-25-2005 18:55:44.755 - File: F:\WINNT\system32\drivers\modem.sys,
Version
> 5.0.2195 - Retail
> 05-25-2005 18:55:44.755 - File: F:\WINNT\system32\modemui.dll, Version
> 5.0.2195 - Retail
> 05-25-2005 18:55:44.765 - Modemtyp: 56K PCI Voice Modem SF-1156IV+ R9A
> 05-25-2005 18:55:44.765 - Pfad für Modeminformationsdatei: oem0.inf
> 05-25-2005 18:55:44.765 - Abschnitt in Modeminformationsdatei: Modem
> 05-25-2005 18:55:45.355 - Opening Modem
> 05-25-2005 18:55:45.355 - 115200,8,N,1, ctsfl=1, rtsctl=2
> 05-25-2005 18:55:45.355 - Modem initialisieren
> 05-25-2005 18:55:45.355 - DSR ist niedrig während der
Modeminitialisierung.
> Stellen Sie sicher, dass das Modem eingeschaltet ist.
> 05-25-2005 18:55:45.366 - Senden: AT<cr>
> 05-25-2005 18:55:45.386 - Empfangen: <cr><lf>OK<cr><lf>
> 05-25-2005 18:55:45.386 - Interpretierte Antwort: OK
> 05-25-2005 18:55:45.396 - Senden:
AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W0<cr>
> 05-25-2005 18:55:45.416 - Empfangen: <cr><lf>OK<cr><lf>
> 05-25-2005 18:55:45.416 - Interpretierte Antwort: OK
> 05-25-2005 18:55:45.426 - Senden:
ATS7=60L0M1+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr>
> 05-25-2005 18:55:45.446 - Empfangen: <cr><lf>OK<cr><lf>
> 05-25-2005 18:55:45.446 - Interpretierte Antwort: OK
> 05-25-2005 18:55:45.446 - Auf Anruf warten
> 05-25-2005 18:55:45.456 - Senden: at+vcid=1<cr>
> 05-25-2005 18:55:45.486 - Empfangen: <cr><lf>OK<cr><lf>
> 05-25-2005 18:55:45.486 - Interpretierte Antwort: OK
> 05-25-2005 18:55:45.496 - Senden: ATS0=0<cr>
> 05-25-2005 18:55:45.516 - Empfangen: <cr><lf>OK<cr><lf>
> 05-25-2005 18:55:45.516 - Interpretierte Antwort: OK
> 05-25-2005 18:55:49.682 - TSP(0000): Making call
> 05-25-2005 18:55:49.682 - Wählen
> 05-25-2005 18:55:49.682 - 115200,8,N,1, ctsfl=1, rtsctl=2
> 05-25-2005 18:55:49.682 - TSP(0000): LINEEVENT: LINECALLSTATE_DIALING
> 05-25-2005 18:55:49.682 - TSP(0000): LINEEVENT: LINECALLSTATE_PROCEEDING
> 05-25-2005 18:55:49.692 - Senden: at+fclass=#<cr>
> 05-25-2005 18:55:50.543 - Empfangen: <cr><lf>OK<cr><lf>
> 05-25-2005 18:55:50.543 - Interpretierte Antwort: OK
> 05-25-2005 18:55:50.553 - Senden: at+vls=#<cr>
> 05-25-2005 18:55:50.583 - Empfangen: <cr><lf>OK<cr><lf>
> 05-25-2005 18:55:50.583 - Interpretierte Antwort: OK
> 05-25-2005 18:55:50.593 - Senden: at+vrn=#<cr>
> 05-25-2005 18:55:50.613 - Empfangen: <cr><lf>OK<cr><lf>
> 05-25-2005 18:55:50.613 - Interpretierte Antwort: OK
> 05-25-2005 18:55:50.633 - Senden: at+vtd=##<cr>
> 05-25-2005 18:55:50.653 - Empfangen: <cr><lf>OK<cr><lf>
> 05-25-2005 18:55:50.653 - Interpretierte Antwort: OK
> 05-25-2005 18:55:50.663 - Senden: at+vsm=###,####,#,#<cr>
> 05-25-2005 18:55:50.673 - Empfangen: <cr><lf>OK<cr><lf>
> 05-25-2005 18:55:50.673 - Interpretierte Antwort: OK
> 05-25-2005 18:55:50.683 - Senden: at+vit=#<cr>
> 05-25-2005 18:55:50.693 - Empfangen: <cr><lf>OK<cr><lf>
> 05-25-2005 18:55:50.693 - Interpretierte Antwort: OK
> 05-25-2005 18:55:50.703 - Senden: ATDT###<cr>
> 05-25-2005 18:55:52.736 - Empfangen: <cr><lf>OK<cr><lf>
> 05-25-2005 18:55:52.736 - Interpretierte Antwort: OK
> 05-25-2005 18:55:52.736 - TSP(0000): LINEEVENT: LINECALLSTATE_CONNECTED
>
>
> --
> Best Regards
> Andreas Marschall
> Microsoft MVP for TAPI / Windows SDK
> TAPI / TSP Developer and Tester
> http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm
> * Please post all messages and replies to the newsgroup so all may
> * benefit from the discussion. Private mail is usually not replied to.
> * This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
>


.

Relevant Pages

  • Re: Modem question
    ... That's the retail price. ... distribution cost was a substantial part of the sale price. ... dollars used (as opposed to the $100 I spent on my 1200baud modem, ...
    (comp.os.linux.misc)
  • Re: ITBasicCallControl::Answer Fail
    ... Here I paste the ModemLog generated by "Incoming" example of SDK when the ... - Retail ... 11-22-2004 00:28:25.906 - Initializing modem. ... Where are TAPI errors codes defined? ...
    (microsoft.public.win32.programmer.tapi)
  • Re: lineDrop - state does not return to idle...
    ... Modem stays on-hook in both cases. ... 9:56.48.249: Calling lineInitializeEx ... 9:56.51.583: lineInitializeEx returned SUCCESS ... - Retail ...
    (microsoft.public.win32.programmer.tapi)
  • Re: Why Outgoing sample program disconnected after making a call?
    ... So the modem log was in Japanese and I have translated it ... - Retail ... 02-15-2005 23:24:57.138 - Command echo ... >> I tried using TAPI browser, ...
    (microsoft.public.win32.programmer.tapi)
  • Re: TAPI/Modem Error Code
    ... No other app is accessing the port. ... modem using TAPI: "Modem Initialization failed with error 00000020". ... - Retail ... Is the modem being used by another app (non TAPI) in parallel so that the COM ...
    (microsoft.public.win32.programmer.tapi)