Genesys TServer to Avaya AES integration

[Gert]

Hi All

It's a little dificult reading this post, but I can say that TSAPI is the newest protocol used by Avaya

1. I cannot believe that there is still customers using MAPD, it's end of life and not been used in the last two years. After mapd cards Avaya started using C-Lan and this should be used if you have any capacity issues.

That said TSAPI is alot cheaper than DLG you unfortunaly require the advanced license NOT the basic. We have done two installs on two seperate corporates and it works well.

One install was done on CM3 and the other on CM5

If some would like more info or battle with something feel free to ask.

[SimonAt]

OK guys, a little bit more info....

- Genesys T-Server R8 onwards will support TSAPI. Prior to that it's got to be DLG.
- AES TSAP Capacity is anywhere between 2000-4000 dependant on your config.
- MAPD's are still in use on some Avaya platforms although it's only "officially" not supported on CM5.x
- If you use TSAPI on Genesys you will need the advanced not basic to enable adjunct routing.

Hope these points help.

[craigr]

You only need 1 advanced license. All other licenses for stations and ACD queues can be basic licenses. Be careful which version of the Avaya TSAPI client you are using and also set TSAPI driver / buffer sizes in Avaya TSAPI T-server options to avoid link flooding / CTI flow control problems.

[SimonAt]

If you want to use TSAPI you must be on a minimum of T-Server R7.6.x & AES 5.x. It's alsow roth noting that if you want to use adjunct routing you will need to purchase enhanced TSAPI licenses (type-B). The maximum number of licenses is based on the number of simultaeneous connections. The AES will only allow 2500 per server but you need to consider how many CLAN's are configured & how many monitored endpoints (and possible VDN's etc) you are likely to use.