GlobalCall Pros/Cons

From: "David Clark" <david451@comcast.net>

From: Gedaliah Friedenberg

-I am designing a telephony system from scratch. Here are a few questions
that should be easy for experienced Dialogic programmers to answer:
1) Since the SDK (SR 5.1.1 and GlobalCall) are C++ libraries, can I assume
that everyone building their own applications are programming in C++?
Yes that is what I am using...I know others use different languages but I
think they bring in other libraries to do that.
2) Does everyone use GlobalCall as an interface between your application
and the call control libraries? If not, why?
No I do not use GlobalCall. I do analog which is simple. T1 wink start
which is not much more complex and ISDN PRI
for which I use the cc_ library API. GlobalCall I have seen in the past
to be a pain to install and configure but I have
just never used it.
3) Are there any "cons" to using GlobalCall? (I believe that GlobalCall
only exists for the Windows platform.)
Yes you have to learn the GlobalCall interface.
4) If all telephony logic is built on top of GlobalCall, will this ease the
transition from low-density analogic cards to high-density (T1/E1) digital
cards?
Do not know.
Thanks!!!
GF

To reply: mailto:General.26272@pysdiscussext.py.intel.com
To start a new topic: mailto:General@pysdiscussext.py.intel.com
To login: http://members.support.dialogic.com/wbproxy/wbpx.dll/~general
Received on Tue Nov 04 23:03:25 2003