" /> Genesys description - Genesys CTI User Forum

Author Topic: Genesys description  (Read 7762 times)

Pawel

  • Guest
Genesys description
« on: January 01, 1970, 12:00:00 AM »
Advertisement
Hello,
I'm going to install one of the Intergraph application which
will be integrated with Genesys 5.1.616. Since I'm not current
Genesys customer I'm not able to get any technical materials regarding TServer and I'm not sure if there could appear any
problems between TLib and Microsoft TAPI.
Could you help, please?
Regards
Pawel



Pawel

  • Guest
Genesys description
« Reply #1 on: January 01, 1970, 12:00:00 AM »
Hello Jeff,

Thanks for your response. I have an application which has to communicate with PBX. I only know for sure that I have Alcatel
4400, Genesys, TLib and TAPI available. I'm not sure how to
integrate them. TAPI was the first thing I thought about, but
I think your suggetstion is very interesting. What do you mean by thirdparty application? Is there any SDK available for this purpose. From where can I get technical description of TLib and
some demo applications.

I would be very gratefull if you could answer above questions.

Best regards,

Pawel



Marked as best answer by on March 28, 2025, 03:47:08 AM

Shiva

  • Guest
Genesys description
« Reply #2 on: January 01, 1970, 12:00:00 AM »
  • Undo Best Answer
  • Hello Pawell,

    If I understand correctly, the basic problem you have is,
    you have an Intergraph application.
    This application needs to talk to 4400.

    To talk to 4400, you need a CTI application, and you are looking at Genesys for this purpose.

    If my above understanding is incorrect or incomplete, do let me know.
    Else,
    If you are developing the application,
    Option 1 :
    Use Genesys 'TServer for Alcatel 4400'
    Use the TLib API calls in the application that has to talk to the switch.
    Option 2 :
    Use TAPI
    Use TAPI Server for 4400
    Develop your application using TAPI to talk to the switch
    Option 3 :
    Use Genesys 'TServer for Alcatel 4400'
    Use optional API module available from Genesys from TAPI.
    (Genesys provides optional interfaces modules for industry standards like TAPI, CORBA, OLE etc.)
    Develop your application using TAPI to talk to the switch. The optional module will do the translation.
    If you have an already existing application which is using TAPI, then
    Option 2 and Option 3 should be considered.

    As Jeff says, a third party translator between TAPI and TLib may be used. That will correspond to Option 3 above.

    Hope this helps.

    Regards

    Shiva

    Victor

    • Guest
    Genesys description
    « Reply #3 on: January 01, 1970, 12:00:00 AM »
    Hi, Pawel,

    what are you trying to accomplish? Before we try to think of an even more complex way of wreaking havoc on your CTI department, why not try to determine if there is a need at all for TAPI and TLib. What do you want to do?

    Vic

    Jeff

    • Guest
    Genesys description
    « Reply #4 on: January 01, 1970, 12:00:00 AM »
    I would recommend adding some additional information to your post, because the question you are asking is rather broad. Do you simply want to know if TLib and TAPI work together? If so, then, yes, it can be made to work together, but you will need to use a thirdparty application or write your own to tie the events from TLib with TAPI.

    I suggest using TLib to invoke PBX telephony capabilities directly if you can, because TAPI by design is rather unstable and requires a high degree of upkeep and maintenance.

    Jeff The TAPI Crasher