AACC AMS Licencing

[tmerkouris]

Hi,
We have completed a new installation of AACC 6.2 with latest patches in a co-resident environment. A plds license has been successfully deployed on License Server, but on Element Manager of AMS we get critical alarm with description: ¨MAS instance is not licensed¨ and when we try some test calls we get ¨486 Busy error message¨.

Do we need to get a separate license for AMS?
On documentation is stated that for co-resident environments there is no need.
Any idea why is this happen?
Thanks.

[phemming]

Does the license you installed include
__sip-conf __sip-dialog & __sip-annc & inst::auth?

They are the AMS licenses I believe

[tmerkouris]

Hi Phemming,

Thanks for your reply.

Actually the plds xml license includes __sip-conf & __sip-annc.
The __sip-dialog isn´t included. Is this mandatory for AMS to work?

Also what is the inst::auth?

[stphnwd]

For AACC 6.2 SP4 and above you now need the inst::auth license, you need one per AMS. This is the license to run the AMS server itself, the MAS Instance.

You must specify that you've upgraded to SP4 or SP5 which gets you to AACC 6.2 so you can get your inst:auth license.

The AMS licenses...

inst::auth - The MAS instance licnese

__sip-conf::sess - This is for your callers. This license issued to anchor the inbound caller to the AMS.

__sip-annc::sess - This is for your one way annoucnemnts to the caller, RAN, Music, Ringback, Busy, etc...

The above three are mandatory and are included without any additional order order codes.

__sip-dialog::sess - This is for two dialog between the caller and AACC. GIVE IVR is when this license is used or PLAY PROMPT. You can collect digits. Also when programming you can use the IVR block in OD to play prompts instead of using RAN. I personally believe this is a more flexible way to play prompts to the caller.

[tmerkouris]

Thanks a lot stphnwd,
You were right, it was an AMS license issue.
When upgraded from AACC 6.0 to 6.2, an additional AMS instance license should be obtained.