🚀 go-pugleaf

On Mon, 25 Aug 2003 18:14:31 +0200, "eric67" <myfantasy@libero.it> wrote:

>> AFAIK, Dialogic boards support TAPI, but IMHO it's far better to use
>> GlobalCall API or one or more specific technology API (ISDN
>(PRI/BRI, Voice,
>> etc etc).
>
>Can you give me more details about GlobalCall API?

GlobalCall APIs they forms a layer which would have to isolate you from
technology details of the various Dialogic's boards which uses different
technologies. For example, there are: 

 o Global Call E-1/T-1 CAS/R2 Technology
 o Global Call IP over Embedded Stack Technology
 o Global Call IP over Host-Based Stack Technology
 o Global Call ISDN Technology 
 o Global Call SS7 Technology 
 o Others Global Call Technologies

For more detailed infos, have a look at here:

http://resource.intel.com/telecom/support/documentation/learnabout/sr5_win/gcdevsw.htm

There are two SDK available from Intel: the release 5.11 which is free and the
version 6 which, as far as I know, it isn't free and supports only Compact PCI
boards.

I've used the SDK 5.11 because I've a PCI board, but I have had some problems
using the GlobalCall layer with BCB. So, mainly because I've obtained a design
pretty instable, I've bypassed the GlobalCall layer and I've used directly
some underlying technologies: ISDN, Voice, digital and (simulated) analog
channels routing, SRL (Standard Runtime Library), etc. It's possible that
(with GlobalCall) has been a my fault, however, now, the application works
well, it's solid rock, it's very stable and it are running very well without
major bugs. The application is a HIVR, a Human Interactive Voice Response
system and it's up and running, until now, for about three months. I've used
the ISDN technology because I have a Springware board D300-JCT-E1; it's a PRI
(primary) ISDN board which receives a 2Mbits flow in order to serve 30 ISDN
channels. 

The aforesaid application uses several principal threads (the main service
thread, the logging thread(s), the RDBMS thread, the monitor thread, etc...),
and creates one or more threads for each incoming call, because I've used an
Asynchronous Model. All things are running under a Win2K Server platform with
minimal overhead. In fact, there's no certification for Windows platforms
different both from Win2K or NT4.

However, if you want to learn about various Intel/Dialogic technologies
(including GlobalCall) you can use this link:

http://resource.intel.com/telecom/support/documentation/learnabout/

To have a look at Intel/Dialogic documentation (sr 5.11) you can go here:

http://resource.intel.com/telecom/support/releases/winnt/sr511fp1/onldoc/htmlfiles/

To join the forums:

http://membersresource.intel.com/wbproxy/wbpx.dll/~Solutions

If you need for further detailed informations about the my unique experience
with Intel/Dialogic product and Borland C++ Builder, let me know.

Giuliano