Cannot send simultaneously

[Torben Frandsen]

I have developed a small test app with the, erm, non-extended library and
run it on a Win2k machine with two devices on one ISDN board. Both devices
are recognized and set to send. If I submit a job while another one is being
sent on the first device, it's queued up and sent on the same device when
the other job is done. I would expect the server to start sending the second
job immediately on the second device.

Can anyone give me a hint as to what I should be looking for?

Torben

 

[Manoj K Jain]

This answer assumes you are using the Fax solution that ships with the OS.

This queueing happens only
a) if the faxes are sent to the same number.
b) if outbound rules are setup which make the particular device the
preferred one for those two numbers.

Otherwise it will send them parallely.

--
Manoj K Jain[MSFT]
Microsoft Printing, Imaging and Faxing
This posting isprovided "AS IS" with no warranties and confers no rights.
Please do not send mail directly to this aloas. This alias is for newsgroup
purposes only.

 

[Torben Frandsen]

This answer assumes you are using the Fax solution that ships with
the OS.

Which I am not. I've written my own code that talks to the API.

This queueing happens only
a) if the faxes are sent to the same number.
b) if outbound rules are setup which make the particular device the
preferred one for those two numbers.

Otherwise it will send them parallely.

Neither of the above apply, so I'm still puzzled.

Torben

 

[Vibha Rathi [MSFT]]

We have tried your scenario at our end using two modems on a win2k server.
It does send simultaneously.
There seems to be some problem with your test app. If you could share the
code of the test app, we could dig further into this.
Vibha Rathi
Microsoft Printing, Imaging and Fax Team

This posting is provided "AS IS" with no warranties, and confers no rights.

Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

 

[Torben Frandsen]

We have tried your scenario at our end using two modems on a win2k
server.

Mine is a Win2kPro. Don't know if that makes a difference.

It does send simultaneously.

Can it have anything to do with the two modems being on the same board? Mine
is an AVM B1 PCI v4.0.

There seems to be some problem with your test app. If you could share
the code of the test app, we could dig further into this.

There's really nothing mysterious about my code. Except, perhaps, that it's
written in VB.Net. It goes like this:

Function SendFax(ByVal GUID As SqlGuid, ByVal FilePath As String, _
Byval FaxNumber As String) As Integer
Dim Id As Integer
Dim Doc As FAXCOMLib.FaxDoc
Dim Server As FAXCOMLib.FaxServer = New FAXCOMLib.FaxServer
Server.Connect("Fax1")

Try
Doc = Server.CreateDocument(FilePath)
With Doc
.FaxNumber = FaxNumber
Id = .Send()
End With
Catch ex As Runtime.InteropServices.COMException
SetText(ex.Message) ' Notify the UI thread
Finally
Server.Disconnect()
Doc = Nothing
Server = Nothing
Return Id
End Try
End Sub

Call this twice in a short time, and the Jobs should be sent simultaneously,
don't you think?

Torben

 

[Juris Sitcs]

OS - Win2kPro. Two external fax modems. The same problem observed -
one device is sending only even the second one is idle and available.
Both configured for sending only. Multiple jobs to different
destinatinations in queue.
Messages generated by code very similar to one above.

Does somebody knows a work-around?

Juris

 

[Torben Frandsen]

OS - Win2kPro. Two external fax modems. The same problem observed -
one device is sending only even the second one is idle and available.
Both configured for sending only. Multiple jobs to different
destinatinations in queue.
Messages generated by code very similar to one above.

Does somebody knows a work-around?

Nope, but my machine has decided to send simultaneously now. I haven't
changed a single setting on it, and I haven't changed the code that submits
jobs to the queue.

Don't we all just *love* intermittent errors?

Torben

 

[Juris Sitcs]

There is something misteriuos! Both devices started to work
simultaneously on next day without any changes in setup. So - the
answer is - just wait a day...

Juris.