RasDial multithreading application problem

[Guest]

Hi,
I and my team are developing a software that using a multiconnection
device (Dialogic Diva Server) with 8 ISDN Modem. This device give us 8 Com
ports and we use RasDial API Method (VS2005 c#) to open connection with the
modems to test some thousands apparatus.

Now we have a problem beacause we need to use that connections in the same
time with a multithreding application to have the best performance.
The problem is that the 8 modems (Ras Connection) open the thelephone
connections at the same time, but the chap authentication happen in sequence.
I explain better, the first connection (or one Ras connection) require 15
sec to make the thelephone call and the chap authentication, the second Ras
connection make the call at once, but wait the finish of the first connection
authentication chap to begin its. The results are that the 8th connection
require more than 2 minutes instead 15 sec.

We now also use, for the same application, a linux pc with the same device
(with the ppd and chat) and this machine don't have this problem, the
connections and authentication happen at the same time for all the lines.

The our system need also a web portal, a web service and other service that
we have already develop in C# (Server 2003) and we prefer to use a Microsoft
Server for the connections, in prediction to expand the system at 30
thelephone lines (PRI ISDN Connection).
Now we exchange data between a 2003 Server and Linux by a proprietary xml
protocol.

The questions are, is this Ras API problem a configuration or a native
problem?
Is it possible to find a solution?
Is Ras Dial API the only windows method to do this job (Thelephone call +
authentication)?
Is it not possible to separate the call and the authentication whithout put
our hands in a PPP protocol?

Regards

Marco Calvi

 

[Guest]

Hello,

We are having the same problem in a similar environment. We are using RAS
API to dial out to 10 other systems at once (10 for testing, plan to dial
many more in production). The COM ports being used by RAS are redirected
using DialOut/EZ software thru a Cisco AS5350 with one attached PRI (23 phone
lines). Server is Windows 2003 Server.

When we RasDial() all the connections, they "modem connect" quickly, but
once they begin PPP authentication/negotiation the remainder of the connect
process seems to be serialized by RAS/Windows and the time to connect for
each dial out session is longer and longer just as described below.

I look forward to seeing replies to your original post that are also
applicable to my situation discussed above.

Thanks,
mlk

 

[Guest]

I opened a support request with Microsoft.

Their response was:

This is a known bug in RAS that will be addressed in Service Pack 3. Dates
of availability are currently unknown. There is no external documentation on
the problem. They will not discuss details. They do not have any
recommended work around at this time.


The above was their response, use information as you see fit but do not rely
on it without verifying it for yourself.