Sign in with
Sign up | Sign in
Your question

Agere soft modem won't send FAXes

Last response: in Windows XP
Share
July 26, 2005 8:27:40 PM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

I'm having a hard time getting the FAX driver built into my XP Pro SP2
ssystem to send FAXes. I have an Agere Softmodem. It will dial, but not from
the FAX driver. Receiving works fine.

Hardware manager tells me: This device is working properly.
I can query it from the Diagnostics tab.
I can set up a dial-up internet connection and it will dial the number.
But it will not dial from the FAX driver.
I have tried to FAX from MS Office and also directly from the FAX console.
On other computers, the FAX Monitor will pop up and show progress, but not
on this PC.

What's wrong?
(I've read other posts in this forum, butnothing seems to fit)
I'm at my wits end.

Thanks,
Kay
July 26, 2005 8:34:02 PM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Here is the tail end of the modem's log:

07-26-2005 12:04:47.406 - Recv: <cr><lf>RING<cr><lf>
07-26-2005 12:04:47.406 - Interpreted response: Ring
07-26-2005 12:04:47.421 - TSP(0000): LINEEVENT: LINE_NEWCALL
07-26-2005 12:04:47.421 - TSP(0000): LINEEVENT: LINECALLSTATE_OFFERING
07-26-2005 12:04:47.421 - TSP(0000): LINEEVENT: LINEDEVSTATE_RINGING(0x1)
07-26-2005 12:04:59.421 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
07-26-2005 12:04:59.421 - TSP(0000): Closing Call
07-26-2005 14:15:49.046 - 115200,8,N,1, ctsfl=1, rtsctl=2
07-26-2005 14:15:49.062 - Initializing modem.
07-26-2005 14:15:49.078 - Send: AT<cr>
07-26-2005 14:15:49.203 - Recv: <cr><lf>OK<cr><lf>
07-26-2005 14:15:49.203 - Interpreted response: OK
07-26-2005 14:15:49.218 - Send: AT &F E0 &C1 &D2 V1 S0=0\V1<cr>
07-26-2005 14:15:49.218 - Recv: <cr><lf>OK<cr><lf>
07-26-2005 14:15:49.218 - Interpreted response: OK
07-26-2005 14:15:49.234 - Send: ATS7=60S30=0L3M1\N3%C1&K3B0B15B2X4<cr>
07-26-2005 14:15:49.234 - Recv: <cr><lf>OK<cr><lf>
07-26-2005 14:15:49.234 - Interpreted response: OK
07-26-2005 14:15:49.234 - Waiting for a call.
07-26-2005 14:15:49.250 - Send: ATS0=0<cr>
07-26-2005 14:15:49.250 - Recv: <cr><lf>OK<cr><lf>
07-26-2005 14:15:49.250 - Interpreted response: OK
07-26-2005 15:11:56.859 - 115200,8,N,1, ctsfl=1, rtsctl=2
07-26-2005 15:11:56.875 - Initializing modem.
07-26-2005 15:11:56.875 - Send: AT<cr>
07-26-2005 15:11:57.015 - Recv: <cr><lf>OK<cr><lf>
07-26-2005 15:11:57.015 - Interpreted response: OK
07-26-2005 15:11:57.015 - Send: AT &F E0 &C1 &D2 V1 S0=0\V1<cr>
07-26-2005 15:11:57.031 - Recv: <cr><lf>OK<cr><lf>
07-26-2005 15:11:57.031 - Interpreted response: OK
07-26-2005 15:11:57.031 - Send: ATS7=60S30=0L3M1\N3%C1&K3B0B15B2X4<cr>
07-26-2005 15:11:57.046 - Recv: <cr><lf>OK<cr><lf>
07-26-2005 15:11:57.046 - Interpreted response: OK
07-26-2005 15:11:57.046 - Waiting for a call.
07-26-2005 15:11:57.046 - Send: ATS0=0<cr>
07-26-2005 15:11:57.046 - Recv: <cr><lf>OK<cr><lf>
07-26-2005 15:11:57.046 - Interpreted response: OK
07-26-2005 15:15:34.406 - Recv: <cr><lf>RING<cr><lf>
07-26-2005 15:15:34.406 - Interpreted response: Ring
07-26-2005 15:15:34.406 - TSP(0000): LINEEVENT: LINE_NEWCALL
07-26-2005 15:15:34.406 - TSP(0000): LINEEVENT: LINECALLSTATE_OFFERING
07-26-2005 15:15:34.406 - TSP(0000): LINEEVENT: LINEDEVSTATE_RINGING(0x1)
07-26-2005 15:15:40.468 - Recv: <cr><lf>RING<cr><lf>
07-26-2005 15:15:40.468 - Interpreted response: Ring
07-26-2005 15:15:40.468 - TSP(0000): LINEEVENT: LINEDEVSTATE_RINGING(0x1)
07-26-2005 15:15:40.765 - TSP(0000): Entering Passthrough Mode
07-26-2005 15:15:40.765 - Passthrough On
07-26-2005 15:15:40.765 - TSP Completing Async Operation(0x00010189) Status
0x00000000
07-26-2005 15:15:40.765 - TSP(0000): LINEEVENT: LINECALLSTATE_CONNECTED
07-26-2005 15:16:23.906 - TSP(0000): Dropping Call
07-26-2005 15:16:23.906 - Passthrough Off
07-26-2005 15:16:23.906 - 115200,8,N,1, ctsfl=1, rtsctl=2
07-26-2005 15:16:23.906 - Initializing modem.
07-26-2005 15:16:23.906 - Send: AT<cr>
07-26-2005 15:16:23.921 - Recv: <cr><lf>OK<cr><lf>
07-26-2005 15:16:23.921 - Interpreted response: OK
07-26-2005 15:16:23.937 - Send: AT &F E0 &C1 &D2 V1 S0=0\V1<cr>
07-26-2005 15:16:23.937 - Recv: <cr><lf>OK<cr><lf>
07-26-2005 15:16:23.937 - Interpreted response: OK
07-26-2005 15:16:23.953 - Send: ATS7=60S30=0L3M1\N3%C1&K3B0B15B2X4<cr>
07-26-2005 15:16:23.953 - Recv: <cr><lf>OK<cr><lf>
07-26-2005 15:16:23.953 - Interpreted response: OK
07-26-2005 15:16:23.953 - Waiting for a call.
07-26-2005 15:16:23.968 - Send: ATS0=0<cr>
07-26-2005 15:16:23.968 - Recv: <cr><lf>OK<cr><lf>
07-26-2005 15:16:23.968 - Interpreted response: OK
07-26-2005 15:16:23.968 - TSP(0000): LINEEVENT:
LINECALLSTATE_DISCONNECTED(0x1)
07-26-2005 15:16:23.968 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
07-26-2005 15:16:23.968 - TSP Completing Async Operation(0x00010178) Status
0x00000000
07-26-2005 15:16:23.968 - TSP(0000): Closing Call
Anonymous
July 28, 2005 9:57:42 PM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Is this modem listed in the Windows XP Hardware Compatibility list
(http://www.microsoft.com/whdc/hcl/default.mspx) and do you have the latest
drivers for it? Unfortunately, Windows XP Fax has proven to be incompatible
with many common modems and drivers, particularly older ones, even if the
manufacturers claim they are "compatible" with Windows XP. Modem
incompatibility is not apparent during installation or the initial setup. It
only becomes apparent when you first try to send or receive a fax. The Fax
Service will dial or will answer an incoming fax but then fail with any of a
number of unhelpful error messages such as "Line is busy," "There is no
answer," or "Reception error." There will be nothing in Event Viewer to
give a clue as to where the problem might lie.

These errors have been nearly impossible to track down. To do so requires
enabling both PSS and debug logging of fax transmissions, both of which
require fairly extensive registry changes. For the time being, the best
advice is to attempt to use XP Fax only if you have a modem that is listed
on the Windows XP Hardware Compatibility List and using the latest drivers.

Hal
--
Hal Hostetler, CPBE -- hhh@kvoa.com
Senior Engineer/MIS -- MS MVP-S/U -- WA7BGX
http://www.kvoa.com -- "When News breaks, we fix it!"
KVOA Television, Tucson, AZ. NBC Channel 4
Still Cadillacin' - www.badnewsbluesband.com

"Kay" <Kay@discussions.microsoft.com> wrote in message
news:3870E1C5-89A8-45BD-B6E2-DEC76428DC06@microsoft.com...
> I'm having a hard time getting the FAX driver built into my XP Pro SP2
> ssystem to send FAXes. I have an Agere Softmodem. It will dial, but not
from
> the FAX driver. Receiving works fine.
>
> Hardware manager tells me: This device is working properly.
> I can query it from the Diagnostics tab.
> I can set up a dial-up internet connection and it will dial the number.
> But it will not dial from the FAX driver.
> I have tried to FAX from MS Office and also directly from the FAX console.
> On other computers, the FAX Monitor will pop up and show progress, but not
> on this PC.
>
> What's wrong?
> (I've read other posts in this forum, butnothing seems to fit)
> I'm at my wits end.
>
> Thanks,
> Kay
Related resources
July 29, 2005 2:46:01 AM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Hi Hal,

Thank you for the sober response. Yes, the Agere SoftModem is in the MSHCL.
http://testedproducts.windowsmarketplace.com/results.as...
The driver is dated June 2005 and is signed by MSHCL. For more information,
here is output from the Sandra program regarding the modem. It queries
devices and reports on them. Perhaps it points to a solution.


SiSoftware Sandra

Communication Device Setup
Model : Agere Systems PCI Soft Modem

Driver Information
Port : COM3
Maximum Baud Rate : 115K baud
Data Bits : 8-bit
Stop Bits : 1
Parity : Disabled
Transmission Mode : Binary
CTS Output Flow Control : Yes
DSR Output Flow Control : No
DSR Input Flow Control : No
DTR Flow Control Type : Enabled
RTS Flow Control Type : Handshake
XON/OFF Input Flow Control : No
XON/OFF Output Flow Control : No
XOFF Continues Transmission : No
Error Replacement Enabled : No
Null Stripping Enabled : No
Abort On Errors : No

Device Information
Manufacturer : ERROR
Model : ERROR
Version : ERROR
Full Name : Agere SoftModem Version 2.1.56
Device ID : United States
Configuration Settings : PCI
Transmit/Receive Buffers : ERROR
Product ID : Agere SoftModem Version 2.1.56
Memory Checksum : OK
Self Diagnostic Result : OK
Modem Settings : Built on 06/30/2005 13:16:22
NVRAM Settings 1 : 2.1.56, PCI, PerLite, 19
Diagnostics Results : OK
Dialling Information : PerLite
Link Diagnostics Results : No Previous Call

FAX Information
Classes Supported : 0,1,8
Receive Capabilities : 3,24,48,72,96,73,74,97,98,121,122,145,146
Transmit Capabilities : 3,24,48,72,96,73,74,97,98,121,122,145,146
Receive HDLC Capabilities : 3,24,48,72,96,73,74,97,98,121,122,145,146
Transmit HDLC Capabilities : 3,24,48,72,96,73,74,97,98,121,122,145,146

Connection Test
Return : CONNECT 2400 NoEC


"Hal Hostetler [MVP S/U]" wrote:

> Is this modem listed in the Windows XP Hardware Compatibility list
> (http://www.microsoft.com/whdc/hcl/default.mspx) and do you have the latest
> drivers for it? Unfortunately, Windows XP Fax has proven to be incompatible
> with many common modems and drivers, particularly older ones, even if the
> manufacturers claim they are "compatible" with Windows XP. Modem
> incompatibility is not apparent during installation or the initial setup. It
> only becomes apparent when you first try to send or receive a fax. The Fax
> Service will dial or will answer an incoming fax but then fail with any of a
> number of unhelpful error messages such as "Line is busy," "There is no
> answer," or "Reception error." There will be nothing in Event Viewer to
> give a clue as to where the problem might lie.
>
> These errors have been nearly impossible to track down. To do so requires
> enabling both PSS and debug logging of fax transmissions, both of which
> require fairly extensive registry changes. For the time being, the best
> advice is to attempt to use XP Fax only if you have a modem that is listed
> on the Windows XP Hardware Compatibility List and using the latest drivers.
>
> Hal
> --
> Hal Hostetler, CPBE -- hhh@kvoa.com
> Senior Engineer/MIS -- MS MVP-S/U -- WA7BGX
> http://www.kvoa.com -- "When News breaks, we fix it!"
> KVOA Television, Tucson, AZ. NBC Channel 4
> Still Cadillacin' - www.badnewsbluesband.com
>
> "Kay" <Kay@discussions.microsoft.com> wrote in message
> news:3870E1C5-89A8-45BD-B6E2-DEC76428DC06@microsoft.com...
> > I'm having a hard time getting the FAX driver built into my XP Pro SP2
> > ssystem to send FAXes. I have an Agere Softmodem. It will dial, but not
> from
> > the FAX driver. Receiving works fine.
> >
> > Hardware manager tells me: This device is working properly.
> > I can query it from the Diagnostics tab.
> > I can set up a dial-up internet connection and it will dial the number.
> > But it will not dial from the FAX driver.
> > I have tried to FAX from MS Office and also directly from the FAX console.
> > On other computers, the FAX Monitor will pop up and show progress, but not
> > on this PC.
> >
> > What's wrong?
> > (I've read other posts in this forum, butnothing seems to fit)
> > I'm at my wits end.
> >
> > Thanks,
> > Kay
>
>
>
July 29, 2005 3:00:02 AM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Hal,

I just rolled back the driver to see if that worked, but it did not fix the
problem. The new Sandra listing appears below. The MSWHCL isting is here:
http://testedproducts.windowsmarketplace.com/results.as...

SiSoftware Sandra

Communication Device Setup
Model : Agere Systems PCI Soft Modem

Driver Information
Port : COM3
Maximum Baud Rate : 115K baud
Data Bits : 8-bit
Stop Bits : 1
Parity : Disabled
Transmission Mode : Binary
CTS Output Flow Control : Yes
DSR Output Flow Control : No
DSR Input Flow Control : No
DTR Flow Control Type : Enabled
RTS Flow Control Type : Handshake
XON/OFF Input Flow Control : No
XON/OFF Output Flow Control : No
XOFF Continues Transmission : No
Error Replacement Enabled : No
Null Stripping Enabled : No
Abort On Errors : No

Device Information
Manufacturer : ERROR
Model : ERROR
Version : ERROR
Full Name : Agere SoftModem Version 2.1.51
Device ID : United States
Configuration Settings : PCI
Transmit/Receive Buffers : ERROR
Product ID : Agere SoftModem Version 2.1.51
Memory Checksum : OK
Self Diagnostic Result : OK
Modem Settings : Built on 03/04/2005 12:02:16
NVRAM Settings 1 : 2.1.51, PCI, PerLite, 19
Diagnostics Results : OK
Dialling Information : PerLite
Link Diagnostics Results : No Previous Call

FAX Information
Classes Supported : 0,1,8
Receive Capabilities : 3,24,48,72,96,73,74,97,98,121,122,145,146
Transmit Capabilities : 3,24,48,72,96,73,74,97,98,121,122,145,146
Receive HDLC Capabilities : 3,24,48,72,96,73,74,97,98,121,122,145,146
Transmit HDLC Capabilities : 3,24,48,72,96,73,74,97,98,121,122,145,146

Connection Test
Return : CONNECT 2400 NoEC


"Hal Hostetler [MVP S/U]" wrote:

> Is this modem listed in the Windows XP Hardware Compatibility list
> (http://www.microsoft.com/whdc/hcl/default.mspx) and do you have the latest
> drivers for it? Unfortunately, Windows XP Fax has proven to be incompatible
> with many common modems and drivers, particularly older ones, even if the
> manufacturers claim they are "compatible" with Windows XP. Modem
> incompatibility is not apparent during installation or the initial setup. It
> only becomes apparent when you first try to send or receive a fax. The Fax
> Service will dial or will answer an incoming fax but then fail with any of a
> number of unhelpful error messages such as "Line is busy," "There is no
> answer," or "Reception error." There will be nothing in Event Viewer to
> give a clue as to where the problem might lie.
>
> These errors have been nearly impossible to track down. To do so requires
> enabling both PSS and debug logging of fax transmissions, both of which
> require fairly extensive registry changes. For the time being, the best
> advice is to attempt to use XP Fax only if you have a modem that is listed
> on the Windows XP Hardware Compatibility List and using the latest drivers.
>
> Hal
> --
> Hal Hostetler, CPBE -- hhh@kvoa.com
> Senior Engineer/MIS -- MS MVP-S/U -- WA7BGX
> http://www.kvoa.com -- "When News breaks, we fix it!"
> KVOA Television, Tucson, AZ. NBC Channel 4
> Still Cadillacin' - www.badnewsbluesband.com
>
> "Kay" <Kay@discussions.microsoft.com> wrote in message
> news:3870E1C5-89A8-45BD-B6E2-DEC76428DC06@microsoft.com...
> > I'm having a hard time getting the FAX driver built into my XP Pro SP2
> > ssystem to send FAXes. I have an Agere Softmodem. It will dial, but not
> from
> > the FAX driver. Receiving works fine.
> >
> > Hardware manager tells me: This device is working properly.
> > I can query it from the Diagnostics tab.
> > I can set up a dial-up internet connection and it will dial the number.
> > But it will not dial from the FAX driver.
> > I have tried to FAX from MS Office and also directly from the FAX console.
> > On other computers, the FAX Monitor will pop up and show progress, but not
> > on this PC.
> >
> > What's wrong?
> > (I've read other posts in this forum, butnothing seems to fit)
> > I'm at my wits end.
> >
> > Thanks,
> > Kay
>
>
>
!