GlobalCall Pros/Cons

From: Gerry Gilmore

On 11/4/2003 12:07:36 PM, Gedaliah Friedenberg wrote:
>
>-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++?

Actually, these are straight C libraries for the most part and you can use C; C++; Java; Delphi or just about anything to build the apps. If you use a higher-level interface, you just need to make sure that it has all of the features and openness that you need.

>
>2) Does everyone use
>GlobalCall as an interface
>between your application and
>the call control libraries?
>If not, why?

After having written apps both ways, I'm *never* going back to non-Global Call. If I *never* see another R2 implementation done "raw", it'll be too soon. :-) As with all things when you program to a higher layer, you trade off some degree of low-level control.

>
>3) Are there any "cons" to
>using GlobalCall? (I believe
>that GlobalCall only exists
>for the Windows platform.)

This is absolutely wrong! Global Call works *great* under Linux...Even better if I do say so... :-)

>
>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?

Yes, and that's the biggest benefit of using GC.

>
>Thanks!!!
>
>GF

-

To reply: mailto:General.26261@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 13:07:03 2003