Red Box

[wpetilli]

Anyone using Red Box recording to an Avaya AES? Would appreciate sharing any configs. Not having luck with CM stations registering to AES. Not finding where the config break is, as everything looks fine.

 

[DAVIDPAYNE]

I am not familial with Redbox, but any 3rd party recorder using AES would need TSAPI and DMCC lic.

 

[wpetilli]

I have plenty of those and configuring extensions on CM w/softphone and then a device in AES is doing nothing. Not registering and doing a list trace ras shows nothing on the CM station I'm trying to register.

 

[kyle555]

Usually needs to be enabled for IP Softphone on the station form. Otherwise, the DMCC part is pretty straightforward. if you can 'stat aes c' and 'stat aes i' and 'stat aes l' and everything's up, then you're good from CM to AES

Frequently, 3rd party application vendors use Avaya's DMCC and TSAPI SDKs installed on their Windows servers and have their application hook in to those. To say as an exmaple, when AES's demo cert expired in January, to install the SMGR authority cert in a call recorder, I just had to go into c:\Avaya\tsapi SDK\certs or something and paste in the contents of the SMGR CA cert into 'trustedCAs.pem'

They usually have some configuration be it by text file or gui to tell the application how to connect up to AES. Perhaps it's requiring secure connections?

 

[wpetilli]

They are using some text file to input the station / virtual station identifiers, along with the AES server IP. There is an established DMCC session from their recorder, which connects using the account created in AES. The stations themselves or devices created on AES are sitting idle w/no gatekeeper IP address. There's full connectivity from CM. Stat of the AES links and CTI connections are both established.

 

[mattKnight]

They are using some text file to input the station / virtual station identifiers, along with the AES server IP

Somewhere you will need to configure the ACM gatekeeper address too.

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[DAVIDPAYNE]

Again I dont know anything about Rebbox. But you will still have to have a IP station built in CM, and the application server would need to know those extension and the password for those extension. The AES should only be creating the LINK between the CM and the application.

 

[bankingguy]

Have you tried testing the DMCC and TSAPI service if its working? There is a tool in AES to do that. This tool allows you to make a call from one station to the other station that you want to reach. you have to input the username and password you created for the redbox. During the testing, if all inputs are correct ( CTI username, password, source station, target station), the target station should ring.