Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Setting up AES cost/licensing
- Thread starter anon0101
- Start date
- Thread starter
- #3
Yeah, I've seen that they're positioning AES for the new sales force thing. I saw some diagram of it somewhere. I don't know if that's a current thing or something they're shooting for in a service pack or something.
I've only seen AES integrate to CM for 3rd party applications.
But the licensing model for AES is generally pay enterprise top dollar for a number of instances for a certain API that you're licensing. Or, you get "named application licenses" which Avaya prices according to whatever other offer they're providing you and it's bundled in that price.
To say, on the enterprise side, to use Avaya WFO (rebranded Verint call recorder), you can get named application licenses that are exclusively for Avaya WFO. You couldn't hookup a Verint Witness that's the same product with the same licenses. The licenses you have are exclusively for Avaya WFO. If you want Verint proper, you'd need to buy a number of sessions for each function it needs (DMCC and TSAPI to be specific).
*That's the shakedown. They can discount their versions of things that use DMCC and TSAPI or whatever on named apps vs whatever competing product has to use the most expensive and basically pay the "not using Avaya" tax if you get a competing version.
To say, AES is a relatively small footprint OVA and the licensing pricing would be tied to the offer of the application. So, probably give or take the same as what it cost before.
I've only seen AES integrate to CM for 3rd party applications.
But the licensing model for AES is generally pay enterprise top dollar for a number of instances for a certain API that you're licensing. Or, you get "named application licenses" which Avaya prices according to whatever other offer they're providing you and it's bundled in that price.
To say, on the enterprise side, to use Avaya WFO (rebranded Verint call recorder), you can get named application licenses that are exclusively for Avaya WFO. You couldn't hookup a Verint Witness that's the same product with the same licenses. The licenses you have are exclusively for Avaya WFO. If you want Verint proper, you'd need to buy a number of sessions for each function it needs (DMCC and TSAPI to be specific).
*That's the shakedown. They can discount their versions of things that use DMCC and TSAPI or whatever on named apps vs whatever competing product has to use the most expensive and basically pay the "not using Avaya" tax if you get a competing version.
To say, AES is a relatively small footprint OVA and the licensing pricing would be tied to the offer of the application. So, probably give or take the same as what it cost before.
- Thread starter
- #5
- Thread starter
- #7
They point at your AES and use protocols to register to it.
Call recorders, for example, connect to AES and register say 12 softphones to the PBX. With TSAPI, it can learn an agent is on a call worth recording and with DMCC device media and call control, it'll virtually press the key remotely observe the agent in question and a speech path is setup from the media gateway to the call recroding server.
You can build a phone into whatever you like.
Call recorders, for example, connect to AES and register say 12 softphones to the PBX. With TSAPI, it can learn an agent is on a call worth recording and with DMCC device media and call control, it'll virtually press the key remotely observe the agent in question and a speech path is setup from the media gateway to the call recroding server.
You can build a phone into whatever you like.
dbuxton101
IS-IT--Management
What about a 3rd party app. A quick google search returns this -
- Status
Similar threads
- Locked
- Question