Avaya ошибка лицензии

Доброго времени суток всем.

1. Переустановил станцию S8400. Подгружаю лицензию *.lic
Станция пишет.

License file downloaded to the server

Installing License file…
License installation successful
loadlicense: Install completed successfully
WARNING: The license installation requires a restart of the web server. Please wait 15 seconds for the restart to finish before clicking another link.

2. далее при проверке лицензии в течении получаса висит сообщение

The License File Web page allows installation of Avaya license files.

CommunicaMgr License Mode Not available due to recent system restart.
26 minutes left before License Audit runs.
Network used for License: NONE
License Serial Number is 071613402830 on NONE

CommunicaMgr License Mode Not available due to recent system restart.
26 minutes left before License Audit runs.

Enterprise Wide Licensing Not Activated

3. По истечении получаса примерно на минуту полторы выдает сообщение.

The License File Web page allows installation of Avaya license files.

CommunicaMgr License Mode: Normal
Network used for License: NONE
License Serial Number is 071613402830 on NONE

CommunicaMgr License Mode: Normal

Enterprise Wide Licensing Not Activated

4. через минуту выдает нижеследующую инфу.

The License File Web page allows installation of Avaya license files.

CommunicaMgr License Mode: License Error
System Administration Will Be Blocked in Approximately 30 days.
Contact Your Service Representative Immediately.
Serial Number Mismatch
Network used for License: NONE
License Serial Number is 071613402830 on NONE

CommunicaMgr License Mode: License Error
System Administration Will Be Blocked in Approximately 30 days.
Contact Your Service Representative Immediately.
Serial Number Mismatch

Enterprise Wide Licensing Not Activated

Походу не та лицензия ? Или с настройками IPSI и сервера не то?

Avaya Virtualization Platform: AVP entering license error mode

Categories:

Alarms/Error Codes, Avaya Aura® Appliance Virtualization Platform, Avaya Aura® System Manager, Break/Fix, Maintenance, Troubleshooting

Details

AVP license error mode (host could be hosting any appliance

System Manager shows AVP license error when logging in to system manager web page. (see attachment)

—————————————————
System MAnager 7.1.3.2 shows AVP license error notification in the dashboard.

Problem Clarification

AVP entering license error mode. Using SDM or Utility Server to enable SSH on AVP. From AVP shell /opt/avaya/bin/statuslicense it will summarize the License Mode, Type, and WebLM address.

For example this license is in Normal Mode:

/opt/avaya/bin # ./statuslicense

AVP License Mode: Normal

License requested: Maximum AVP dual CPU Common Servers

WebLM Server used for License: https://fakeweblm.company.com:52233/WebLM/LicenseServer

The type is determined by the hardware that AVP is installed on.

Note: To enable ssh use command AVP_SSH enable

 —————————————————————————-
System MAnager 7.1.3.2 shows AVP license error notification in the dashboard.

Solution

Click Sign in to view full article.

Avaya Breeze™ servers and some snap-ins require license files. A properly
licensed Avaya Breeze™ server or a snap-in is in the License Normal Mode. A major
alarm is raised if a Avaya Breeze™ server or a licensed snap-in has a license error. The
server or the snap-in enters License Error Mode with the 30-day license
grace period. While in License Error Mode, the Avaya Breeze™ servers and the licensed snap-ins provide full functionality.

If the license error has not been corrected before the 30-day license
grace expires, a critical alarm is raised and the server or the snap-in
enters License Restricted Mode. In the case of an Avaya Breeze™ server in License Restricted Mode, the server goes to
the Deny New Service state. The server automatically returns to service
when the license error is resolved. In the case of a snap-in in License
Restricted Mode, the snap-in is uninstalled from all the clusters.
You cannot reinstall the snap-in before the license error is resolved.
You must manually install the snap-in after the license error is resolved,
and the snap-in returns to License Normal Mode.

LIC-ERR (License-Error Mode)

MO Name (in

Alarm Log)

Alarm Level

LIC-ERR

MAJOR

NOTE:

The License-Error Mode maintenance object (LIC-ERR) is a non-traditional

MO. As a result, there are no associated tests or commands that are

executed in the traditional manner.

Maintenance object LIC-ERR works in concert with maintenance object NO-LIC to

look for any errors/violations associated with the License File. Once a License File

error occurs, maintenance object LIC-ERR logs the error, raises an alarm, and

starts a timer that is associated with the error. When the timers threshold has

been exceeded, MO NO-LIC will cause call processing to be restricted. All call

origination will be restricted to outgoing emergency numbers, incoming calls will

be restricted to an Administration (Attendant Console) number.

The license file is loaded onto a switch during initialization of the switch software,

restore of translations, and periodically. After initialization, a query is made to a

software module called the License Server. This module reads the license file,

compares a serial number in the license file to a serial number in hardware,

compares the software version in the license with the running software version,

and if a match occurs, delivers permission to run to the Avaya MultiVantage

Software along with a new feature mask. The feature mask controls

revenue-associated options.

Error Log Entries and Test to Clear Values

Table 325. LIC-ERR Error Log Entries

Error

Aux

Type

Data

1(a)

513(b)

769(c)

1281(d)

1.

These Error Types can be cleared by providing the correct License File per local instructions.

555-233-119

Initial Command to Run

NONE

Associated Test

Alarm Level

MAJOR

None

MAJOR

None

MAJOR

None

MAJOR

Full Name of MO

License-Error Mode

On/Off

Board

Test to Clear Value

OFF

See footnote

OFF

See footnote

OFF

See footnote

OFF

See footnote

Issue 5 October 2002

1

1

1

1

1331

Please read carefully information below if you have problems with using Avaya Integration module.

If you need any assistance from us then let’s have skype call or teamviewer session. My skype is andrew.uymin
Please tell me date and time range when we can communicate (please send your time range in UTC)

For self-diagnosis, please see tips below.

General problem with Avaya Integration:

1. Avaya license
2. TAPI. It’s the most common issue!
3. Firewalls and PBX-connector server accessible issue
4. Module license

1. Avaya license issue

There is a list with installed licenses In Avaya administration panel.
Please make sure you have installed valid license for
a. Avaya CTI Link Pro
b. Avaya VoiceMailPro (only if you want to have audio recording in phone call log)

2. TAPI issues

To make sure you don’t have problems with TAPI please do the following:
2.1. Please try to use TAPI softphone http://office.vedisoft.ru/__files/Phone.exe
Just run this application on your PBX-connector server. This softphone use the same TAPI protocol in the same manner as our module does.
When you run this softphone you should be able to choose one of TAPI-lines in dropdown.
If you will not see TAPI-lines in that softphone then you have problem with TAPI connection/TAPI driver/TAPI license. Please go to paragraph #2.2 and #2.3 below.
If you will see TAPI lines, then please choose one of them and try to call somewhere. If you call successfully please go to paragraph #3 below.
2.2. Please go to windows system-log. Please find events with TAPI and review them (there should be info about connected TAPI lines).
2.3. Please replace exe file inside folder with our module on that one http://office.vedisoft.ru/files/All-In-One_CTI_Avaya.exe. This file has extended log for TAPI events. Start this application and send us TAPI log.

3. Firewalls and PBX-connector server accessible issue

Copy-paste into new tab in your browser the URL from host parameter of All-In-One CTI Configuration in Administration in SugarCRM. It looks like ws://YOUR_PBX_CONNECTOR_SERVER:port For example ws://192.168.0.6:10150
Before you open URL in new tab please replace ws with http (or if you use wss, then replace it with https).
You should get URL like http://YOUR_PBX_CONNECTOR_SERVER:port For example http://192.168.0.6:10150
You should get 403 error (Forbidden). If you get this error then it means your PBX-connector is running. If you don’t get 403 error and you get error 500 (server is not found), then your PBX-connector is not running OR you can’t access PBX-connector server from your computer (pay attention your computer should have access to PBX-connector server by TCP on specified port).

4. Module license issue

Check what you have in module’s log file. Log files are located according to your settings in config.txt. File config.txt locates in your installation directory (by default — C:Program FilesVedisoftAll-In-One CTI – Avaya). If you see “License is expired” in log file then
• Make sure you put correct license into config.txt. Required license is not the license you get on SugarOutfitters or SuiteCRM Store. You should get license directly from us. If you didn’t get license from us please send us email.
• Your PBX-connector server does not have access to our license server. Our license sever address is https://license.prostiezvonki.ru (port 443 on your PBX-connector server should be open for that address).

If you still can’t make it work, then please send your problems to:
— a@vedisoft.ru
— or into skype: andrew.uymin