# Modem won't answer or call out

**URL:** <https://boards.straightdope.com/t/modem-wont-answer-or-call-out/476234>\
**Category:** Factual Questions\
**Created:** [December 8, 2008, 1:35pm UTC](https://boards.straightdope.com/t/modem-wont-answer-or-call-out/476234 "2008-12-08T13:35:58Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![CookingWithGas](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/cookingwithgas/32/485_2.png) [@CookingWithGas](https://boards.straightdope.com/u/CookingWithGas)\
**Post date:** [December 8, 2008, 1:35pm UTC](https://boards.straightdope.com/t/modem-wont-answer-or-call-out/476234/1 "2008-12-08T13:35:58Z")

</div>

I have a fax/voice modem that ships with telephone answering maching (TAM) software. I have loaded latest drivers, confirmed that everything shows properly after setup, but the modem just won’t answer incoming calls, or dial out when I try to send a fax.

I will never use it as a modem; I got it just as a fax send/receive and for TAM. I am using it on a Vista Home Premium x64 system. The drivers are advertised to work with Vista.

It seems to respond appropriately to all AT commands, and queries from the software confirm voice capability. There is a dial tone on the line. I have a phone plugged into it and the phone rings when there is an incoming call, but it doesn’t answer. Outgoing faxes fail and are queued for resend.

Tech support has been completely useless, simply sending me screen shots of how to install and run the software, rather than diagnosing the problem.

I bought it from Newegg and could return it for a 15% restocking fee but it was so cheap it isn’t worth paying the shipping to do that.

Any ideas?

---

<div class="post-metadata">

**Author:** ![sailor](https://avatars.discourse-cdn.com/v4/letter/s/a587f6/32.png) [@sailor](https://boards.straightdope.com/u/sailor)\
**Post date:** [December 8, 2008, 2:12pm UTC](https://boards.straightdope.com/t/modem-wont-answer-or-call-out/476234/2 "2008-12-08T14:12:18Z")

</div>

Here is what I would do: Start Hyperterminal and communicate with the modem. Select communicate directly with Comm Port #X. Send AT and you should get OK. Now, does the modem send RING when the phone rings?

---

<div class="post-metadata">

**Author:** ![CookingWithGas](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/cookingwithgas/32/485_2.png) [@CookingWithGas](https://boards.straightdope.com/u/CookingWithGas)\
**Post date:** [December 9, 2008, 2:56am UTC](https://boards.straightdope.com/t/modem-wont-answer-or-call-out/476234/3 "2008-12-09T02:56:43Z")

</div>

> [@sailor](#):
>
> Here is what I would do: Start Hyperterminal and communicate with the modem. Select communicate directly with Comm Port #X. Send AT and you should get OK. Now, does the modem send RING when the phone rings?

Hmm. Vista dropped Hyperterminal. Their Help page refers me to Phone and Modem options but it doesn’t appear to have a function to send codes to the modem. Will continue to research…

---

<div class="post-metadata">

**Author:** ![sailor](https://avatars.discourse-cdn.com/v4/letter/s/a587f6/32.png) [@sailor](https://boards.straightdope.com/u/sailor)\
**Post date:** [December 9, 2008, 4:02am UTC](https://boards.straightdope.com/t/modem-wont-answer-or-call-out/476234/4 "2008-12-09T04:02:02Z")

</div>

Maybe the modem program would have the option of communicating directly with the modem.

It’s too bad Vista does not have several useful programs which came with XP. That is keeping me back from buying a computer.

---

<div class="post-metadata">

**Author:** ![hekk](https://avatars.discourse-cdn.com/v4/letter/h/50afbb/32.png) [@hekk](https://boards.straightdope.com/u/hekk)\
**Post date:** [December 10, 2008, 12:39am UTC](https://boards.straightdope.com/t/modem-wont-answer-or-call-out/476234/5 "2008-12-10T00:39:50Z")

</div>

Hyperterminal is MIA in Vista? Wow.

I use ZOC Terminal, because of its nifty scripting capabilities. I think it’s shareware, but nag screens don’t show up for awhile. Try downloading it to see if your modem is communicating correctly.

---

<div class="post-metadata">

**Author:** ![CookingWithGas](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/cookingwithgas/32/485_2.png) [@CookingWithGas](https://boards.straightdope.com/u/CookingWithGas)\
**Post date:** [December 10, 2008, 2:08am UTC](https://boards.straightdope.com/t/modem-wont-answer-or-call-out/476234/6 "2008-12-10T02:08:13Z")

</div>

FYI here are the diagnostics from the log from the Vista modem configuration tool:

12-08-2008 21:57:48.830 - Modem type: PCI SoftV92 Modem  
12-08-2008 21:57:48.830 - Modem inf path: oem25.inf  
12-08-2008 21:57:48.830 - Modem inf section: Modem3  
12-08-2008 21:57:48.830 - Matching hardware ID: pci\ven\_14f1&dev\_2f30&subsys\_205114f1  
12-08-2008 21:57:49.107 - 115200,8,N,1, ctsfl=1, rtsctl=2  
12-08-2008 21:57:49.107 - Initializing modem.  
12-08-2008 21:57:49.124 - DSR is low while initializing the modem. Verify modem is turned on.  
12-08-2008 21:57:49.141 - Send: AT\<cr\>  
12-08-2008 21:57:49.143 - Recv: AT\<cr\>  
12-08-2008 21:57:49.143 - Command Echo  
12-08-2008 21:57:49.143 - Recv: \<cr\>\<lf\>OK\<cr\>\<lf\>  
12-08-2008 21:57:49.143 - Interpreted response: OK  
12-08-2008 21:57:49.154 - Send: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2\<cr\>  
12-08-2008 21:57:49.310 - Recv: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2\<cr\>  
12-08-2008 21:57:49.311 - Command Echo  
12-08-2008 21:57:49.311 - Recv: \<cr\>\<lf\>OK\<cr\>\<lf\>  
12-08-2008 21:57:49.311 - Interpreted response: OK  
12-08-2008 21:57:49.322 - Send: ATS7=60S30=0M1+ES=3,0,2;+DS=3;+DS44=3;+IFC=2,2;X4\<cr\>  
12-08-2008 21:57:49.323 - Recv: \<cr\>\<lf\>OK\<cr\>\<lf\>  
12-08-2008 21:57:49.323 - Interpreted response: OK  
12-08-2008 21:57:49.343 - Passthrough On  
12-08-2008 21:57:50.091 - Passthrough Off  
12-08-2008 21:57:50.091 - Session Statistics:  
12-08-2008 21:57:50.091 - Reads : 833 bytes  
12-08-2008 21:57:50.091 - Writes: 138 bytes  
ATQ0V1E0 - OK  
AT+GMM - +GMM: PCI SoftV92 Modem  
AT+FCLASS=? - 0,1,8,80  
AT#CLS=? - COMMAND NOT SUPPORTED  
AT+GCI? - +GCI: B5  
AT+GCI=? - +GCI: (00,01,02,03,04,05,06,07,09,0A,0B,0C,0D,0E,0F,10,11,12,13,14,15,16,19,1A,1B,1C,1D,1E,1F,20,21,22,23,24,25,26,27,28,29,2A,2B,2C,2D,2E,2F,30,31,32,33,34,35,36,37,38,39,3A,3B,3C,3D,3E,40,41,43,44,  
45,46,47,48,49,4B,4C,4D,4E,4F,50,51,52,53,54,55,56,57,58,59,5A,5B,5C,5E,5F,60,61,62,63,64,65,66,67,68,69,  
6A,6B,6C,6D,6E,6F,70,71,72,73,74,75,76,77,78,79,7A,7B,7C,7D,7E,7F,80,81,82,83,84,85,86,87,88,89,8A,8B,8C,  
8D,8E,8F,90,92,93,94,96,97,98,99,9A,9B,9C,9D,9E,9F,A0,A1,A2,A3,A4,A5,A6,A7,A8,A9,AA,AB,AC,AD,AE,AF,B0,B1,  
B2,B3,B4,B5,B6,B7,B8,B9,BA,BB,BC,BD,BE,BF,C1,C2,C3,C4,C5,C7,C8,C9,CA,CB,CC,CD,CE,CF,D0,D1,D2,D3,D4,D5,  
D6,D7,D8,D9,DA,DB,DC,DD,DE,DF,E0,E1,E2,E3,E4,E5,E6,E7,E8,EB,EC,ED,EE,EF,F0,F1,F2,F3,F4,F5,F7,F8,F9,FA,FB,  
FC,FE)  
ATI1 - 255  
ATI2 - OK  
ATI3 - SoftK56V\_B2.1\_V7.60.00.50  
ATI4 - PCI SoftV92 Modem  
ATI5 - 181  
ATI6 - SoftK56  
CModem Version 12  
Rksample Version 342  
ATI7 - 255

---

<div class="post-metadata">

**Author:** ![sailor](https://avatars.discourse-cdn.com/v4/letter/s/a587f6/32.png) [@sailor](https://boards.straightdope.com/u/sailor)\
**Post date:** [December 10, 2008, 10:46am UTC](https://boards.straightdope.com/t/modem-wont-answer-or-call-out/476234/7 "2008-12-10T10:46:36Z")

</div>

> [@](#):
>
> 12-08-2008 21:57:48.830 - Modem type: PCI SoftV92 Modem  
> 12-08-2008 21:57:48.830 - Modem inf path: oem25.inf  
> 12-08-2008 21:57:48.830 - Modem inf section: Modem3  
> 12-08-2008 21:57:48.830 - Matching hardware ID: pci\ven\_14f1&dev\_2f30&subsys\_205114f1  
> 12-08-2008 21:57:49.107 - 115200,8,N,1, ctsfl=1, rtsctl=2  
> 12-08-2008 21:57:49.107 - Initializing modem.  
> 12-08-2008 21:57:49.124 - DSR is low while initializing the modem. Verify modem is turned on.  
> 12-08-2008 21:57:49.141 - Send: AT\<cr\>  
> 12-08-2008 21:57:49.143 - Recv: AT\<cr\>  
> 12-08-2008 21:57:49.143 - Command Echo  
> 12-08-2008 21:57:49.143 - Recv: \<cr\>\<lf\>OK\<cr\>\<lf\>  
> 12-08-2008 21:57:49.143 - Interpreted response: OK  
> 12-08-2008 21:57:49.154 - Send: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2\<cr\>  
> 12-08-2008 21:57:49.310 - Recv: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2\<cr\>  
> 12-08-2008 21:57:49.311 - Command Echo  
> 12-08-2008 21:57:49.311 - Recv: \<cr\>\<lf\>OK\<cr\>\<lf\>  
> 12-08-2008 21:57:49.311 - Interpreted response: OK  
> 12-08-2008 21:57:49.322 - Send: ATS7=60S30=0M1+ES=3,0,2;+DS=3;+DS44=3;+IFC=2,2;X4\<cr\>  
> 12-08-2008 21:57:49.323 - Recv: \<cr\>\<lf\>OK\<cr\>\<lf\>  
> 12-08-2008 21:57:49.323 - Interpreted response: OK  
> 12-08-2008 21:57:49.343 - Passthrough On  
> 12-08-2008 21:57:50.091 - Passthrough Off  
> 12-08-2008 21:57:50.091 - Session Statistics:  
> 12-08-2008 21:57:50.091 - Reads : 833 bytes  
> 12-08-2008 21:57:50.091 - Writes: 138 bytes

That exchange shows the modem is responding. For some reason the format of the exchange now changes and both the command and the response appear on the same line from now on.

> [@](#):
>
> ATQ0V1E0 - OK  
> AT+GMM - +GMM:**(Request Model Identification)** PCI SoftV92 Modem  
> AT+FCLASS=?**(Report service classes supported)** - 0,1,8,80 **(data, FAX, voice, VoiceView) \*\*  
> AT#CLS=?**(Report if configured for data, fax, or voice)\*\* - COMMAND NOT SUPPORTED

Uh oh. Command AT#CLS will select data, fax, or voice so AT#CLS=? is asking how the modem is currently configured, data, fax, or voice, but this last command does not seem to be widely supported. It may be that the driver you are using is not exactly matched to the hardware. It could also be that this error has no consequences.

> [@](#):
>
> AT+GCI? - +GCI: B5  
> AT+GCI=? - +GCI: \<snip\>

This command seems to be modem-specific and asking to report internal configuration

> [@](#):
>
> ATI1 - 255 **(Return hardware variation code)**  
> ATI2 - OK **(Report internal code)**  
> ATI3 - SoftK56V\_B2.1\_V7.60.00.50 **(Driver version)**  
> ATI4 - PCI SoftV92 Modem **(modem identifier)**  
> ATI5 - 181 **(country code)**  
> ATI6 - SoftK56 , CModem Version 12 , Rksample Version 342 **(Data pump model & internal code revision)**  
> ATI7 - 255 **(DAA code)**

Initially that single error looks like it may be unimportant and the rest of the exchange looks fine. We would need to see the rest of the exchange in order to diagnose the problem. You are sure the driver is for that modem? Or are you using a generic Windows driver? I would try looking into finding a driver that works.

---

<div class="post-metadata">

**Author:** ![Quartz](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/quartz/32/267_2.png) [@Quartz](https://boards.straightdope.com/u/Quartz)\
**Post date:** [December 10, 2008, 2:00pm UTC](https://boards.straightdope.com/t/modem-wont-answer-or-call-out/476234/8 "2008-12-10T14:00:58Z")

</div>

Is this a winmodem or a full hardware modem? The line ‘PCI SoftV92 Modem’ makes me worry. Winmodems were the spawn of hell when I last dealt with them. So, can you tell us the exact model name?

---

<div class="post-metadata">

**Author:** ![sailor](https://avatars.discourse-cdn.com/v4/letter/s/a587f6/32.png) [@sailor](https://boards.straightdope.com/u/sailor)\
**Post date:** [December 10, 2008, 2:03pm UTC](https://boards.straightdope.com/t/modem-wont-answer-or-call-out/476234/9 "2008-12-10T14:03:56Z")

</div>

Yup that looks like a Win (soft) modem. They got a bad reputation but I never had serious problems with them. They were cheap and worked ok.

---

<div class="post-metadata">

**Author:** ![CookingWithGas](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/cookingwithgas/32/485_2.png) [@CookingWithGas](https://boards.straightdope.com/u/CookingWithGas)\
**Post date:** [December 10, 2008, 10:56pm UTC](https://boards.straightdope.com/t/modem-wont-answer-or-call-out/476234/10 "2008-12-10T22:56:14Z")

</div>

I am using a driver from the manufacturer’s web site, which was an update from the one it shipped with.

I’m pretty sure it’s a winsoft modem.

The manufacturer is Rosewill model RC-403. After some research I discovered this is Newegg’s private brand manufactured by third parties.

It’s based on the Conexant CX11252-41Z chipset. [Newegg description](http://www.newegg.com/Product/Product.aspx?Item=N82E16825164001). Now discontinued. I can guess why :rolleyes:

---

<div class="post-metadata">

**Author:** ![Quartz](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/quartz/32/267_2.png) [@Quartz](https://boards.straightdope.com/u/Quartz)\
**Post date:** [December 10, 2008, 11:18pm UTC](https://boards.straightdope.com/t/modem-wont-answer-or-call-out/476234/11 "2008-12-10T23:18:45Z")

</div>

Try and borrow a hardware modem like [this USR modem](http://www.newegg.com/Product/Product.aspx?Item=N82E16825104135) or [this Zoom modem](http://www.newegg.com/Product/Product.aspx?Item=N82E16825115001) (I still have my Hayes Accura somewhere) and see if that works any better. Chances are it will.

---

<div class="post-metadata">

**Author:** ![sailor](https://avatars.discourse-cdn.com/v4/letter/s/a587f6/32.png) [@sailor](https://boards.straightdope.com/u/sailor)\
**Post date:** [December 11, 2008, 1:23am UTC](https://boards.straightdope.com/t/modem-wont-answer-or-call-out/476234/12 "2008-12-11T01:23:59Z")

</div>

Even though I have not used one in ages I still install modems in every system I build, if only for fax. External modems are much more expensive and I would not justify their cost. External modems also are often not as suited to voice applications. I would try to get this modem to work before buying another one.

---

<div class="post-metadata">

**Author:** ![Derleth](https://avatars.discourse-cdn.com/v4/letter/d/b9e5f3/32.png) [@Derleth](https://boards.straightdope.com/u/Derleth)\
**Post date:** [December 11, 2008, 2:02am UTC](https://boards.straightdope.com/t/modem-wont-answer-or-call-out/476234/13 "2008-12-11T02:02:50Z")

</div>

> [@sailor](#):
>
> Yup that looks like a Win (soft) modem. They got a bad reputation but I never had serious problems with them. They were cheap and worked ok.

That’s the problem: They’re great when they work but impossible to diagnose when they don’t. It’s like magic, in a way: When it works, it’s magic. When it doesn’t, it’s magic.
