 |
Modemsite's Forum56 - The Modem Board Main | profile | register | search | help | Ad-free Login |
| Forums | Other (Public) | Call-back with Win2000 Standard Modem Driver? | Watch |
| Author | Topic |
| Dirk Tl Posts: 8 Germany | Posted - 5/19/2005 5:49:14 AM    With Win95/98 I used a Standard 28000 bps Modem Driver for Data Connections with a "hard" configured ISDN terminal adapter (TA) "Phillips TA mini+" and it worked very fine. On Win2000 it works basically, but the call-back does not effect. In the modem log I can see that the incomming call with a "RING" was correctly interpreted as an incoming call, but no answer (ATA) follows. Since the Data connection with an usual modem with it`s specific driver is working with call-back, I think, this is a problem of the Win2000 standard modem driver. The Driver version is 10/29/1999, 5.00.2167.1 |
| v.Richard Tl Posts: 6222 USA | Posted - 5/20/2005 9:50:51 AM  Please describe your setup more completely. If you have a system that you have set up to accept Remote Access connections with callback, and there is no answer, I would suspect the setup of your connectoids/remote access properties etc. Aloha! Richard. |
| Dirk Tl Posts: 8 Germany | Posted - 5/23/2005 7:20:43 AM Hi Richard, please excuse my bad English. I am using the Windows2000-own Dial-Up client (Programms>Accessories>Communications>Dial-Up Networking) to make an IP connection with a Cisco Access Router. There is a pop-up window, that is writing "Waiting for Call-Back" (analogous, translated from German). In the modem log You can see the incoming call ("RING"), but the driver never "picks up the phone": 05-17-2005 15:49:42.044 - Auf Anruf warten ; =Awaiting Call, Dirk 05-17-2005 15:49:42.054 - Senden: ATS0=0<cr> 05-17-2005 15:49:42.054 - Empfangen: <cr><lf>OK<cr><lf> 05-17-2005 15:49:42.054 - Interpretierte Antwort: OK 05-17-2005 15:49:42.054 - TSP(0000): LINEEVENT: LINECALLSTATE_DISCONNECTED(0x1) 05-17-2005 15:49:42.054 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE 05-17-2005 15:49:42.054 - TSP(0000): Dropping call 05-17-2005 15:49:42.054 - TSP(0000): Closing Call 05-17-2005 15:49:52.279 - Empfangen: RING 05-17-2005 15:49:52.279 - Interpretierte Antwort: Ring 05-17-2005 15:49:52.279 - TSP(0000): LINEEVENT: LINE_NEWCALL 05-17-2005 15:49:52.279 - TSP(0000): LINEEVENT: LINECALLSTATE_OFFERING 05-17-2005 15:49:52.279 - TSP(0000): LINEEVENT: LINEDEVSTATE_RINGING(0x1) 05-17-2005 15:50:04.286 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE 05-17-2005 15:50:04.286 - TSP(0000): Closing Call With an 3Com U.S.Robitics 56K Voice Modem and the type-special Windows driver it works very fine with call-back. Are You living in Hawaii? |
| v.Richard Tl Posts: 6222 USA | Posted - 5/24/2005 8:00:34 PM The command, ats0=0 turns auto-answer off; you need to have the modem initialized with ats0=1 - You should be able to configure this with the connectoid/modem properties (set to autoanswer); or, by adding s0=1 'extra setting' initialization string - www.modemsite.com/56k/initmagic.asp
Aloha! Richard. |
| Dirk Tl Posts: 8 Germany | Posted - 5/25/2005 12:32:03 AM Thanks, Richard, I`ve done it soon. If I initialize the "modem" with Auto-Answer (ATS0=1) the "modem" will pick up the incoming call and the router will be showing the line as "Up", but the driver doesn`t take notice of that and the laptop is always awaiting incoming call. I think that there is ab bug in the Windows2000 standard modem driver (since it is working with other modems and their drivers) and I am looking for a newer (or another) generic driver for Win2k. Regards |
| Dirk Tl Posts: 8 Germany | Posted - 5/27/2005 3:35:08 AM I just realized that the probleme bases on the signals of the serial interface between PC and terminaladapter ("modem") like DTR and CTS. |
| v.Richard Tl Posts: 6222 USA | Posted - 5/29/2005 10:02:44 AM Do you have it working now? Aloha! Richard. |
| Dirk Tl Posts: 8 Germany | Posted - 5/30/2005 7:27:20 AM :( No, It have tried a lot of things, but my driver (or the apllication?) don`t want to take the incoming call. The present interface settings of my terminaladapter MUST be o.k.: DTR/C mode: "DTReady 108.2" (same as AT&D2) DSR mode: "DSR=ON" (same as AT&S0) RTS/CTS mode: "RTS->CTS" (same as AT&R1) DCD/I mode: "Ready for Data" (same as AT&C1) |
| v.Richard Tl Posts: 6222 USA | Posted - 5/31/2005 10:37:21 AM The standard modem "driver" is only an .inf file that defines the modem's command set and responses and causes appropriate registry entries to be made when installed. (This holds true for other modem drivers designed for modems that are hardware-controller based; it is not the case for soft or host-controller modems). Since the .inf file is a text file, you can load, edit, experiment using Notepad or text editor; Does your TA accept & respond to standard 'AT' commands? Perhaps need to see more of the modem log; Aloha! Richard. |
| Dirk Tl Posts: 8 Germany | Posted - 6/1/2005 5:14:23 AM Thank You, Richard, now I see the problem more clearly. I tried the procedure with an U.S.Robotics modem (with analog line) once again. It worked fine like I estimated. Than I compared the modemlog of this with the modemlog of my unfortunate trial with the TA. I`ve seen the following: 1. Analog modem: The driver gets a RING from the Modem. It continues waiting. Only after the second RING (after 5 seconds) the driver takes the call by sending ATA. There is no possibility to configure the TA to wait for more than one Ring. The relevant register is read-only. Regards |
| Dirk Tl Posts: 8 Germany | Posted - 6/2/2005 7:18:24 AM Additional remark: For ATS0=n the TA doesn`t accept values greater than 1. For example the command ATS0=5 does effect a value of S0=1. |
Click Here To Close Thread, Administrators & Moderators Only.
Show All Forums |