" /> Genesys TServer & MAPD Integration - Genesys CTI User Forum

Author Topic: Genesys TServer & MAPD Integration  (Read 2787 times)

Offline amarceau

  • Newbie
  • *
  • Posts: 44
  • Karma: 0
Genesys TServer & MAPD Integration
« on: August 02, 2010, 06:47:16 PM »
Advertisement
Anyone out there still on Avaya MAPD?  :-[  (I know, I know -- old, old, old - but it is what it is)

I'm going through a new installation and our installers cannot get this connection working.

I've provided them with the IP, Port & CTI-Link number of the MAPD and they are indicating it's still not the correct information?

Just wondering if anyone else out there is still on this that could give me some feedback of how they have the Options on the TServer configured.

Thanks,

Offline gheart

  • Newbie
  • *
  • Posts: 1
  • Karma: 0
Re: Genesys TServer & MAPD Integration
« Reply #1 on: August 02, 2010, 08:04:43 PM »
Under the T-Server Options - define a link-tcp section with the following:

hostname = IP address of the MAPD i.e. "192.168.26.10"
link-number = CTI link number defined on the MAPD for T-Server communications (1-8) i.e. "5"
port = port of the MAPD i.e. "5678"
protocol = "tcp"

Offline spend

  • Newbie
  • *
  • Posts: 9
  • Karma: 0
Re: Genesys TServer & MAPD Integration
« Reply #2 on: August 03, 2010, 01:37:19 PM »
We're still on MAPD at most of our sites.

The key is to make sure your connection to the MAPD is hard coded at 10MB 1/2 duplex.

That and the configuration gheart listed should work, provided that your MAPD and avaya cti links are set up properly.

The first port on one of our cards just plain wouldn't work.  We changed ports and the issue cleared.

Good luck.

Offline amarceau

  • Newbie
  • *
  • Posts: 44
  • Karma: 0
Re: Genesys TServer & MAPD Integration
« Reply #3 on: August 09, 2010, 05:34:47 PM »
Thanks all!!  Issue resolved.  Our currently dialer's CTI-Link is configured as ADJNK and not ASAI.  Apparently Genesys needs ASAI.  I deleted the CTI-Link and re-added as Type=ASAI and Voila!  It all worked and connected fine  ;D

Much appreciated all the feedback....

Now onto the second issue of getting LDAP external authentication to work... arrrgggg :)