BusinessPhone Communication Platform 7.0
Maintenance Instruction ASB 150 02

## ASB 150 02 Software key based licensing

### General

The ASB 150 02 Software key based licensing replaces the former hardware key based licensing concepts (FECU for internal applications and WIBU-Key for external applications such as BackStage and Call Center Assistant) as well as the BEA licensing.

The software key is represented by a license file which is stored on the compact flash card of the CPU‑D5/CPU-D5C if available. If this board type is not available (upgraded system based on a CPU-D4) it is possible to store the license file on the compact flash card of the MFU, IPU or VMU-HD board.

Compared to a hardware key, the software key provides a high flexibility regarding feature bundling (license steps), license updates (local or remotely via BMS) as well as offering a trial time period with unlimited functionality for most of the features requiring a license.

The central software controls the license handling towards the internal and external applications. In case of the external applications all license information is provided to the BusinessLink Server 3.1 (or higher), which acts itself also as License Server towards the external applications. The BusinessLink Server has full control about remaining trial time, total and current free license values as well as license updates.

The licenses can be ordered via the normal order process, each license step is represented by an own article number. For each ordered article number a Unique Pick Number (UPN) will be delivered. This UPN is used as an input for the License Administration tool which is located on the Ericsson Partner Network, in order to create the customer’s license files based on the bought features.

The former hardware key based licensing has been smoothly integrated into the software key based licensing. In case of upgrading an old ASB 150 02 system (Release 13 or older) to the latest Release and ordering one of the available licenses, the existing licenses defined by the FECU will be remapped into the proper software key based licenses (for further details see chapter Request a release update license).

Note

When upgrading an old ASB 150 02 system (with or without connected FECU) to the latest CSW Release due to bug fixing, you don‘t have the necessity to switch over to the software key based licensing when you want to keep the existing functionality.

In case of upgrading an existing application (e.g. BEA 3.0, BackStage 5.0 or CCA 3.0), the old licensing concepts (PC based or WIBU-Key) and the new software key based licensing concept can co-exist. The applications are always searching for both license concepts, which means that the total sum of licenses is available to the applications.

#### Introduction steps

- ASB 150 02 Release 14
  Replacement of the FECU licensing and introduction of a Basic, Mobile Extension, Unified Messaging, CTI, Networking and VoIP Gateway license
- ASB 150 02 Release 15, Revision R1A
  Replacement of the WIBU-Key licensing for BackStage and CCA
  Replacement of the BEA licensing
  Introduction of CPU-D5C license
- ASB 150 02 Release 15, Revision R3A
  The system automatically enables the full CTI license in conjunction with a Basic license. The same applies for the Networking green pack license if in addition to the Basic license an IPU board is installed.

### Pre-requisites

In order to use the software licensing concept, following minimum requirements have to be fulfilled.

#### Hardware configuration

Configuration | CPU-D4 | CPU-D5 | FECU | License carrier board
Alternative | Type | CPU-D5 | MFU or VMU‑HD or IPU
1 | New sales |  | X*) |  | X*) |
2 | R9-R12 upgrade to lastest Release | X |  | X |  | X
3 | R13 upgrade to lastest Release | X |  | X |  | X
| X | X | X |
4 | Repair CPU-D4 (R9-R13 ) to CPU‑D5 (with latest release) |  | X | X | X |
5 | Repair CPU-D4(with latest release) to CPU-D5 |  | X | X |  | X

*) or a CPU-D5C when using a BusinessPhone Compact

##### Hardware, Central software & Firmware revisions

- FECU KDUBS 130 06 / x (x = Package 1-10)
- CPU-D4 (ROF 157 5124/1)

  |  | R-state PCB |  | R2A |
  |  | HW-code |  | 3 |
  |  | Internal application licensing:
  |  | FW |  | RYS 102 533 R3G |
  |  | CSW |  | LZY 203 2234 (Release 14) |
  |  | Internal+ external application licensing:
  |  | FW |  | RYS 102 533 R4B |
  |  | CSW |  | LZY 203 2235 (Release 15) |

- CPU-D5 (ROF 157 5124/2)

  |  | R-state PCB |  | no limitations |
  |  | HW-code |  | no limitations |
  |  | Internal application licensing:
  |  | FW |  | RYS 102 548 R1A |
  |  | CSW |  | LZY 203 2234 (Release 14) |
  |  | Internal+ external application licensing:
  |  | FW |  | RYS 102 548 R1D |
  |  | CSW |  | LZY 203 2235 (Release 15) |

- CPU-D5C (ROF 157 5124/3)

  |  | R-state PCB |  | no limitations |
  |  | HW-code |  | no limitations |
  |  | Internal+ external application licensing:
  |  | FW |  | RYS 102 548 R1D |
  |  | CSW |  | LZY 203 2235 (Release 15) |

- IPU (ROF 157 5133/1 )

  |  | Internal application licensing:
  |  | FW |  | RYS 102 539 R4A |
  |  | Internal+ external application licensing:
  |  | FW |  | RYS 102 539 R5A |

- MFU (ROF 157 5132/_ )

  |  | Internal application licensing:
  |  | FW |  | RYS 102 538 R5A |
  |  | Internal+ external application licensing:
  |  | FW |  | RYS 102 538 R5E |

- VMU-HD (ROF 157 5133/_

  |  | Internal application licensing:
  |  | FW |  | RYS 102 526 R4A |
  |  | Internal+ external application licensing:
  |  | FW |  | RYS 102 526 R4E |

#### External application requirements

The license handling towards the external applications is done via the BusinessLink 3.1 Server (or higher). For the Installation of the BusinessLink see dedicated Technical guide on the Enterprise Application Suite CD-ROM (FASBS10220/CD)

Following external applications are supporting the software key based licensing

- BackStage 7.0 or higher
- BusinessPhone Extension Assistant 3.1 or higher *)
- Call Center Assistant 3.02 or higher

*) this application requires additionally an installed BusinessLink Client.

### Licensed features

Equal to the former FECU Index 1, there exists a Basic license entry in the license file, which covers all basic features up to the latest release. For a detailed feature overview see document
Facility description General, 15534‑ASB150 02 Uen.

On top of the Basic license entry there exists additional license entries for following features:

License Name | Introduced with Release
Mobile Extension | 14
Unified Messaging | 14
CTI | 14
Networking | 14
VoIP Gateway | 14
CPU-D5C *) | 15
BackStage **) | 15
Call Center Assistant | 15
BusinessPhone Extension Assistant | 15

*) only used for upgrading a CPU-D5C board to a CPU-D5.

**) the BackStage licensing was partly implemented already in Release 14 as two demo licenses were already included in the basic license.

### License modularity and order rules

The licensed features are available in different modularity steps. From commercial point of view, these modularity steps are defined by dedicated color packs which are available in green, orange and red color (see table below).

Functional area/Pack | Default | Basic | Green Pack | Orange Pack | Red Pack | Plus Pack | Maximum
Basic | not enabled | New sales: Basic enabled automatically Upgrade: Basic enabled by FALBS 102 51/B | - | - | - | - | Enabled | [Enabled (Yes/No)]
Mobile Extension | 0 | 2 | 5 FALBS 102 44/G | 20 FALBS 102 44/O | 40 FALBS 102 44/R | 5 FALBS 102 44/P | 100 | [Users]
Unified Messaging | 0 | 2 | 20 FALBS 102 45/G | 50 FALBS 102 45/O | 100 FALBS 102 45/R | 5 FALBS 102 45/P | 200 | [Users]
CTI *) | 0 | 2 | 5 FALBS 102 46/G | 80 FALBS 102 46/O | - | to 80 FALBS 102 46/P | 80 | [Users]
Networking | not enabled/0 | Full/ 2 Interface **) | Standard/unlimited FALBS 102 49/G **) | Full/32 FALBS 102 49/O | Full/unlimited FALBS 102 49/R | to Full/unlimted FALBS 102 49/P | Full/ unlimited | [feature level/trunks]
VoIP Gateway | not enabled | not enabled | Gateway enabled FALBS 102 50/G | - | - | - | Gateway enabled | [Enabled (Yes/No)]
CPU-D5C (BP Compact Upgrade) | 3 | - | - | - | Unlimited FALBS 102 64/R | - | Unlimited | [Maximum boards]
BackStage | 0 | 2 | 5 FALBS 102 60/G | 20 FALBS 102 60/O | 50 FALBS 102 60/R | 5 FALBS 102 60/P | 80 | [Users]
BEA | 0 | 10 | 50 FALBS 102 62/G | 100 FALBS 102 62/O | 200 FALBS 102 62/R | 25 FALBS 102 62/P | 250 | [Users]
CCA | 0 | 2 | 5 FALBS 102 63/G | 10 FALBS 102 63/O | 15 FALBS 102 63/R | 5 FALBS 102 63/P | 40 | [Users]

*) This license package is only relevant for an ASB 150 02 system with CSW Release14 - Release15 R2A. When using an ASB 150 02 system with CSW Release15 R3A or higher, 80 CTI users are automatically enabled in conjunction with a valid Basic license.

**) In conjunction with an installed IPU board, this license package is only relevant for an ASB 150 02 system with CSW Release14 - Release15 R2A. When using an ASB 150 02 system with CSW Release15 R3A or higher the Networking green pack license is automatically enabled in conjunction with a valid Basic license and an installed IPU board.

#### License combination

For each of the listed features one of the available color packs can be chosen. Packs from different features can be freely combined (modular concept), for instance, the Mobile Extension Green Pack (5 users) and the Unified Messaging Orange Pack (50 users).

Note

The license values defined in the Basic license are not added to the values in the colors packs respectively to the sum of color pack + plus pack(s). An exception to this rule are the BackStage and
CTI *) color packs, which adds the 2 licenses of the Basic license to the different color pack whereby the maximum number of 80 user remains.
*) only rlevant if CSW is older than R15 R3A.

#### Delivery

For each of the listed article numbers a Unique Pick Number will be delivered. This Unique Pick Number is used for the License Administration Tool within the Ericsson Partner Network (http:\\enterprise.ericsson.net) to create the customer’s license file with the bought features.

The License Administration Tool can be accessed via the top menu of Ericsson Partner Network portal.

#### Expansion of color packs

For the expansions of a color pack, only the dedicated plus pack can be added. If desired this can take place also in a multiple way, which will result in a delivery of multiple UPN numbers.

A plus pack can only be registered when following criteria’s are fulfilled:

- it will be used for new sales in combination with a color pack.
- it will be used for add on sales with a previously sold and installed color pack.
- it will be used for add on sales in conjunction with an installed FECU (Index 2 –10).

##### Exception

A Networking green pack license which has been automatically enabled due to the combination of a CSW Release15 R3A or higher and an installed IPU board can not be expanded by a plus pack. In this specific case the Networking orange or red pack has to be ordered.

#### Technical aspects versus sales objects

From technical point of view there exists no direct relation in ASB 150 02 between the licensed features, the licensed modularity, their dedicated article numbers nor to their defined commercial names. By using the BMS only the licensed features and the current license value can be read out (for details see the following chapter).

In order to give the sales people an accurate input for the ordering of feature enhancements at the customer site, use following rule of thumb in order to enhance a desired feature:

- A license entry exists: Order one or multiple plus packs
- A trial, a basic or a system enabled license entry exists: Order color packs in combination with plus packs
- A FECU license entry exists for the Networking feature: Order a plus pack

#### Special considerations

##### Unified Messaging license

The Unified Messaging license requires a CTI license in addition (for £ 20 Unified Messaging users, 5 CTI users are required, for >20 Unified Messaging users, 80 CTI users are required).

##### VOIP Gateway license

The VoIP Gateway license disables all other licenses (except the Basic and the CPU-D5C license entries) as well as all PBX functiones.

The software VoIP Gateway license is necessary to activate the corresponding IPU Gateway license (see chapter IPU - Software licensing.

##### BackStage and CTI-license:

Apart from the BackStage license, each BackStage Client consumes also a CTI license (= an activated CTI monitor). A CTI license is consumed also, if an extension is supervised in the busy lamp field of BackStage. However if this supervised extension is also active with the BackStage Client both processes are using the same CTI license.

##### BackStage, Call Center Assistant and BEA.

In case of upgrading an existing application (e.g. BEA 3.0, BackStage 5.0 or CCA 3.0), the old licensing concepts (PC based or WIBU-Key) and the new software key based licensing concept can co-exist.

Note

The applications and the BusinessLink have to be upgraded to fulfil the requirements of the new licensing concept. For the BEA the BusinessLink Server/Client has to be installed in addition.

The applications are always searching for both license concepts, which means that the total sum of licenses is available to the applications.

When ordering a new software key based license, a color pack is required before plus packs can be added, regardless of existing PC based or WIBU-Key based licenses.

### The license file

#### Definition

The base for any feature licensing in Release 14 (or higher) is the availability of a license file with valid license entries. Valid license entries are referring to features which were bought by the customer and registered in the License Administration Tool on the Ericsson Partner Network.

The license file can be stored on the CPU‑D5/CPU-D5C, MFU, IPU or VMU-HD Compact Flash card.

In case of new sales, the CPU-D5/CPU-D5C always contains a license file with a valid Basic license entry.

In case of an upgraded system (formally a FECU based Release 9-13 system), it is necessary to create a license file by using the BMS. This created license file is empty and provides temporary unlimited access to most of the Release 14 (or higher) features during the trial time. In order to change the status from temporary features to licensed ones and to remap the existing FECU feature level into the new license scheme, the license file has to be registered in the License Administration Tool on the Ericsson Partner Network (details see chapter Request a release update license).

All license entries in the license file are encrypted by the License Administration Tool by using a two key security mechanism based on the system ID of ASB 150 02 and the storage ID of the Compact Flash card.

- System ID
  The system ID is provided by a CPU-D5/CPU-D5C board or by a FECU, whereby the later one has the higher priority.
- Storage ID
  The storage ID is given by the unique serial number of the Compact Flash card.

This encryption makes it impossible to reuse the license file in multiple customer systems.

#### To create a license file

The creation of a license file is only necessary if a software upgrade from Release 9-13 to Release 14 or higher has taken place.

Note

When using the CPU-D5/CPU-D5C board in a new installed system with Release 14 or higher, a license file is already available. The file is not longer available if the CPU-D5 was formally used in an Release 13 system.
If the license file of the CPU-D5C has to be recreated due any fault reason, it is only possible to create the file on the CPU-D5C itself again, even though there might be proper other boards such as MFU or IPU installed in the system.

1. Connect the BMS to the system.
2. Keep the existing FECU plugged to the CPU-D4/CPU-D5.
3. Click on the system in the tree view.
4. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   The BMS detects automatically that there exists no license file in the system and propose all boards which can be used for the creation of a new license file.
5. Select the desired board and click on the ’Create license file’ button. The license file will be created.

### Trial time & Temporary features

#### Defintion

The trial time automatically starts after a coldstart or after a software release upgrade and lasts 1440 hours = 60 days. During this period most of the features which have no valid license entry in the license file, will be treated as temporary features. Temporary features are fully open (maximum license value) compared to the licensed features which are limited to customized license values.

#### Exceptions

The features VOIP Gateway and CPU-D5C will never be treated as temporary features and are therefore only be active in conjunction with valid license entries.

The feature CTI will not be treated as temporary feature, if CSW Release15 R3A(or higher) and a valid Basic license is installed, instead the full CTI license (80 users) will be enabled automatically however without any related entry in the license file.

#### Trial time expires

Once the trial time is expired, the license value of temporary features will be modified according to the following criteria’s:

- If there exists a Basic license entry all temporary features are modified to the license value which is defined by the Basic license.(see license table in chapter License modularity and order rules).
- If there exists a Basic license entry, a CSW of Release15 R3A or higher and a installed IPU board, the Networking green pack license (Standard digital networking with unlimited trunk interfaces) will be enabled automatically, however without any related entry in the license file.
- If there exist no valid license entries (upgraded FECU based system, formally running on Release 9-13), the feature level of the connected FECU will be used. All other features which require a license will be disabled. The trial time can be restarted once by importing at least a valid Basic license entry.

### The ASB 150 02 license dialog

The license of the system is controlled via the ASB 150 02 licensing dialog.

1. Connect the BMS to the system
2. Click on the system in the tree view
3. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.

##### Example 1:

- Upgraded system (formally R13 with FECU /10)
- No licensed feature
- Full Trial time

The parameter “(Trial)” indicates that the feature is not licensed however temporarily available until the trial time expires.

The features VOIP Gateway and CPU-D5C (only shown if a CPU-D5C is available in the system) will never be treated as temporary features and are therefore only be active in conjunction with valid license entries.

##### Example 2:

- Upgraded system
- (formally R13 with FECU /10)
- No licensed feature
- Trial time expired

The parameter “(FECU)” indicates that the feature is not licensed, however it is enabled based on the feature level which is defined by the connected FECU.

##### Example 3:

- Upgraded system to Release 15 R3A
- (formally R13 with FECU /1)
- IPU board installed
- Basic license
- Trial time expired

The parameter “(System enabled)” indicates that the feature is not licensed, however it is enabled based on the combination of:

- CSW Release15 R3A or higher + Basic license entry = CTI 80 Users
- CSW Release15 R3A or higher + Basic license entry + IPU board = Networking Standard/unlimited

##### Example 4:

- Upgraded system (formally R13 with FECU /10)
- Some licensed features
- Trial time expired

The parameter “(Basic)” indicates that the feature is not licensed and it is limited to the feature level which defined by the Basic license.

When ordering a license after the upgrade to Release 14 or higher, the existing feature level based on the connected FECU will automatically be re-mapped into the license file (see the CTI and Networking licenses in the screenshot above). See also chapter Mapping of the FECU Index into the license file.

##### Example 5:

- BP Compact cold started (Full trial time)

As a Basic license is available with every CPU-D5 the CTI license is automatically enabled by the system as far as the CSW R15 R3A or higher is installed.

##### Example 6:

- BP Compact (including CPU-D5C upgrade)
- Some licensed features
- Trial time not expired

##### Example 7:

The VOIP Gateway feature is licensed

The VOIP Gateway license has the highest priority which disables all other licenses (also temporary)

#### Buttons

- Export license file
  This button is used to fetch the license file from the board on which it is stored and to export it to a desired destination on the PC or LAN. For further details see chapter To export the license file.
- Import license file
  This button is used to import a license file, which was received from the Ericsson License Center, into the system to replace the existing one. For further details see chapter To import the license file.
- Show license file
  This button is used to view the content of the license file. For further details see chapter Show license file.
- Reload
  This button is used to refresh all indications from the license dialog.

#### License Status

The license status table provides read only information for following values:

- Licensing board
  States the board position which carries the license file
- Remaining trial time
  States the remaining operating hours for all features which have no valid entry in the license file. The counter will be decreased in 5 minutes steps.
- System ID
  States either the serial number of the connected FECU or the serial number the CPU-D5/CPU-D5C. If a CPU-D5/CPU-D5C is installed in the system with a connected FECU, then always the FECU serial number will be used as the system ID.

Note

The FECU serial number contains the dedicated software release as well as the FECU Index. The first digit on the left site describes the software release (0=R9/R10, 1=R11, 2=R12, 3=R13). The second digit on the left site describes the FECU-Index (1=Index 1, 2 =Index 2, ......A=Index10). According to the example above a FECU from R13 Index 10 is used.

- Serial Number of Flash Disk
  States the unique serial number of the storage media on which the license file is stored.
- LZY Information
  States article number and revision of the CSW

#### Licensed feature table

The table provides an overview of all features which are requiring a license:

- License Name
  States all the features (feature packages) which require a license entry.
- License value
  States the licensed number of the user or the feature level of the licensed feature. An additional parameter displayed in brackets, is a typical indication for a not licensed feature.

- (Trial)
  indicates that the feature is only available until the trial time expires.
- (Basic)
  indicates that the feature is limited to the feature level which defined by the Basic license.
- (FECU)
  indicates that the feature is limited to the feature level which defined by the connected FECU.
- (System enabled)
  indicates that the feature has been enabled due a certain combination of CSW, Basic license and installed HW.

#### Values in the ’Licensed feature’ table versus parameters in the license file:

Indication in the BMS |  | Indication in the license file | Comment
License Name | License value | Description | License entry | License value
Basic | No | Enabled (Yes/No) | - | - | after trial period if no appropriate license entry exists in the license file
Yes (Trial) | - | - | during trial period
Yes | BASIC_LICENSE | 1 | always available on CPU-D5/CPU-D5C boards
Mobile Extension | 0 | Users | - | - |
100 (Trial) | - | - | during trial period
2 (Basic) | - | - | defined by Basic license
5-100 | MOBILE_EXT_LICENSE | 5 -100 |
Unified Messaging | 0 | Users | - | - |
200 (Trial) | - | - | during trial period
2 (Basic) | - | - | defined by Basic license
20-200 | UNIFIED_MSG_LICENSE | 20 -200 |
CTI | 0 | Users | - | - | after trial period, if neither an appropriate entry in the license file nor an appropriate FECU is installed
80 (System enabled) | - | - | if CSW Release 15 R3A or higher and a Basic license entry exists in the license file; CTI license 80 is not installed
80 (Trial) ***) | - | - | during trial period
2 (Basic) **) | - | - | defined by Basic license
80 (FECU) | - | - | defined by connected FECU Index 6-10 - after trial period and no appropriate license file
7 **) | CTI_LICENSE | 7 | defined by appropriate CTI license entry
80 | CTI_LICENSE | 80 | defined by appropriate CTI license entry
Networking | Not enabled/0 | Feature level/Trunks | - | - | after trial period, if neither an appropriate entry in the license file nor a FECU is installed
| Full/Unlimited (Trial) | - | - | Full digital networking with unlimited trunk interfaces (during trial period)
| Full/2 (Basic) | - | - | Full digital networking with 2 trunk interfaces (defined by Basic license)
| Full/2 (FECU) | - | - | Full digital networking with 2 trunk interfaces (defined by FECU Index 1)
| Full/4 (FECU) | - | - | Full digital networking with 4 trunk interfaces (defined by FECU Index 6)
| Standard/32 (FECU) | - | - | Standard digital networking with 32 trunk interfaces (defined by FECU Index 2, 7)
| Standard/unlimted (FECU) | - | - | Standard digital networking with unlimited trunk interfaces (defined by FECU Index 3, 8)
| Full/32 (FECU) | - | - | Full digital networking with 32 trunk interfaces (defined by FECU Index 4, 9)
| Full/Unlimted (FECU) | - | - | Full digital networking with unlimited trunk interfaces (defined by FECU Index 5, 10)
| Standard/unlimited | NETWORKING | 3 | Standard digital networking with unlimited trunk interfaces
| Full/32 | NETWORKING | 4 | Full digital networking with 32 trunk interfaces
| Full/Unlimted | NETWORKING | 5 | Full digital networking with unlimited trunk interfaces
| Standard/unlimited (System enabled) | - | - | Standard digital networking with unlimited trunk interfaces (if CSW Release 15 R3A or higher, a Basic license entry in the license file exists and an IPU board is installed and the trial time is expired)
VOIP Gateway | No | Enabled (Yes/No) | - | - |
Yes | VOIP_GATEWAY | 1 |
CPU-D5C *) | 3 | Maximum boards | - | - |
Unlimited | MAX_BOARDS | 63 |
BackStage | 0 | Users | - | - |
80 (Trial) | - | - | during trial time
2 (Basic) | - | - | defined by Basic license
7-80 | EXT_APP BACKSTAGE | 7-80 |
BEA | 0 | Users | - | - |
250 (Trial) | - | - | during trial time
10 (Basic) | - | - | defined by Basic license
50-250 | EXT_APP BEA | 10-250 |
CCA | 0 | Users | - | - |
40 (Trial) |  | - | during trial time
2 (Basic) |  | - | defined by Basic license
5-40 | EXT_APP CCA | 5-40 |

*) Only displayed in conjunction with a CPU-D5C in order to upgrade the board to a CPU‑D5 to get no limitation in the number of supported board positions.

**) Only displayed if the installed CSW is older than Release 15 R3A

***) Displayed during trial time if the installed CSW is older than Release 15 R3A or CSW is Release 15 R3A or higher and no Basic license exists.

#### Show license file

In order to show the license file of ASB 150 02 click on the “Show license file” button in the ASB 150 02 dialog

##### Description of the license file entries

- ASB150 02 license
  This entry contains following values:

- the board name and board position on which the license file was created
- the central software at the time of the license file generation
- the firmware revision of the board at the time of the license file generation
- whether the license file was created in the factory (FACT‑Init) or created by the ASB 150 02 itself (OAM‑Init)

- created-storage ID, created-system ID, control-info
  These entries are only relevant for the License Administration Tool.
- Storage ID
  This entry contains the unique serial number of the compact flash card on which the license file is stored.
- System ID
  States either the serial number of the connected FECU or the serial number the CPU-D5/CPU-D5C. If a CPU-D5/CPU-D5C is installed in the system with a connected FECU, then always the FECU serial number will be used as the system ID.
- The remaining entries in the license file are describing the licensed internal as well as external applications
  These entries contain values about:

- the dedicated system release for internal applications and the license ID for the external applications
- the feature level
  For detailed description about the feature level values see chapter Values in the ’Licensed feature’ table versus parameters in the license file:
- encrypted license key.

#### To export the license file

1. Click on the ’Export license file’ button in the ASB 150 02 Licensing dialog
   The system ID will automatically be used as the filename for the license file .
2. Click on the filename to download the license file to your desired destination
3. The exported file is then ready for registration purpose in the License Administration Tool on the Ericsson Partner Network.

Note

Before the license file can be registered in the License Administration Tool, Unique Pick Numbers have to be available for the desired functions.

Note

The exported license file must not be modified by using any editor.

#### To import the license file

1. Click on the ’Import license file’ button in the ASB 150 02 Licensing dialog.
   The expected filename will be displayed on the screen.
2. Click the on the ’Browse’ button to search for the expected license file.

Note

Although a certain filename is expected the BMS also accepts any other *.ULK filename.

1. Click on ’Transfer Licensing File to ASB’ to import the selected file.
   In the case of a successful import of the license file, the license status for all licensed features will be updated immediately.

Note

Before the BMS imports the new license file, it performs automatically a check whether the system ID and the storage ID matches with the data in the customer system and rejects the request with an error message if the validation fails.

Note

In case of an upgraded system the first import of a license file with valid license entries will cause a restart of the trial time counter.

Note

After importing the CPU-D5C upgrade license (MAX_BOARDS) a system restart needs to be performed. In case of finding the valid license entry at start up, the system can access all cards, however every new board position needs to be initialized. For further details see chapter Adding of boards.
After the license upgrade the CPU-D5C will be detected as CPU-D5 in the hardware details dialog however the ROF-Info (ROF 157 5124/3) of the CPU-D5C remains.

### Request a new license

This chapter is only relevant for new systems with Release 14 or higher.

#### Basic license

By default an ASB 150 02 Release 14 (or higher) system delivery contains a license file with a valid basic license entry on the CPU-D5/CPU-D5C which provides the possibility to activate all available basic features in the customer‘s system.

If this feature level is sufficient for the customer no further licensing activities are necessary

Most of the other features which require a license will be treated as temporary features which are valid during the trial time (see also chapter Trial time & Temporary features).

When the trial time expires all temporary features will be limited according the license values which are defined in the Basic License (see table in chapter License modularity and order rules.

How a Basic license is indicated in the License dialog see Example 5:.

#### Color pack

In order to get a valid license entry for one or more color packs, use following procedure:

1. Due to the fact that most of the features which need to be licensed are temporary open during the trial time (detailed description see Trial time & Temporary features), you can configure and activate the desired features in the system already before the final license is activated.
2. Order the desired color pack(s).
3. After you have received the Unique Pick Number(s) for the placed order, connect the BMS to the system.
4. Click on the system in the tree view
5. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
6. Export the license file.
   Detailed description see To export the license file.
7. Build up an Internet connection via the Service PC or the customer PC and login to the Ericsson Partner Network (http:\\enterprise.ericsson.net).
8. Open the Web page for the License Administration Tool and follow the offered instructions to create and download the desired license by using the available Unique Pick Numbers.

Note

The received license file must not be modified by using any editor.

1. Import the downloaded license file into the system.
   Detailed description see To import the license file.
2. Verify whether the new content of the ’Licensed feature’ table matches with the features which have been ordered.

### Request an add on license (additional color or plus pack)

1. Connect the BMS to the system.
2. Click on the system in the tree view.
3. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   The Licensed feature table provides an overview of all the licensed features and their feature level. If you are using and upgraded system (from Release 9 - Release 13) you need to create a license file when entering the license dialog the first time. Detailed description see The ASB 150 02 license dialog
4. Verify the ’Remaining trial time’ counter. If the counter has not been elapsed and if it still provides enough operating hours until the final license will imported, you can configure and activate the desired temporary features in the system.
5. Order the desired feature enhancement (for the article numbers see Licensed features).
6. After you have received the Unique Pick Number(s) for the placed order, connect the BMS to the system again.
7. Export the license file.
   Detailed description see To export the license file.
8. Build up an Internet connection via the Service PC or the customer PC and login to the Ericsson Partner Network (http:\\enterprise.ericsson.net).
9. Open the Web page License Administration Tool and follow the offered instructions to create and download the desired license by using the available Unique Pick Numbers
10. Import the downloaded license file into the system. Detailed description see To import the license file.
11. Verify whether the new content of the ’Licensed feature’ table matches with the features which have been ordered. If you are using an upgraded system (from Release 9 - Release 13) a FECU re-mapping has taken place in conjunction with the ordering of a color or plus pack. Detailed description see Mapping of the FECU Index into the license file.

### Request a release update license

Before a system can be upgraded from Release 9-13 to the latest Release, please verify the Pre-requisites.

Note

If no FECU is connected to the CPU-D4, the system is running on a Release 8 feature level independent from the installed software. In this specific case the licensing concept can not be applied after the software upgrade to Release 14 or higher, as the system ID which is mandatory for creating a license file is missing. In order to use the Release 14 or higher functions, a CPU-D4 has to be replaced by a CPU-D5 or any FECU has to be connected to the CPU-D4.

#### Mapping of the FECU Index into the license file

When upgrading an ASB 150 02 system from the hardware key based licensing (FECU) to the software key based licensing the existing FECU index (independent from it‘s dedicated Release) will be considered by the License Administration Tool and be re-mapped into the license file.

A re-mapping of the existing FECU will be performed by the License Administration Tool when ordering one of the following licenses:

- Basic upgrade license - FASBS 102 51/B

- upgrades the FECU feature level to Release 14 (or higher)

- Any color pack except the one for the VoIP Gateway

- upgrades the FECU feature level to Release 14 (or higher)
- adds the new feature which is requested

- The networking plus pack

- upgrades the FECU feature level to Release 14 (or higher)
- enhances the Networking features defined by the FECU to Full/Unlimited

Note

The re-mapping of the FECU will only be performed when requesting the first license file. There is no way to add a FECU afterwards.

The table below describes how the different FECU indexes will be remapped when ordering a basic upgrade license

FECU | License Indication
Index | Description | License Name | License Value
1 | Basic Functions + Full digital networking with 2 trunk interfaces | Basic | Enabled
2 | Standard digital networking with 32 trunk interfaces | Basic | Enabled
NETWORKING | Standard/Unlimited
3 | Standard digital networking with unlimited trunk interfaces | Basic | Enabled
NETWORKING | Standard/Unlimited
4 | Full digital networking with 32 trunk interfaces | Basic | Enabled
NETWORKING | Full/32
5 | Full digital networking with unlimited trunk interfaces | Basic | Enabled
NETWORKING | Full/Unlimited
6 | CTI + Full digital networking with 4 trunk interfaces *) | Basic | Enabled
NETWORKING | Full/32
CTI | 80 Users
7 | CTI + Standard digital networking with 32 trunk interfaces | Basic | Enabled
NETWORKING | Standard/Unlimited
CTI | 80 Users
8 | CTI + Standard digital networking with unlimited trunk interfaces | Basic | Enabled
NETWORKING | Standard/Unlimited
CTI | 80 Users
9 | CTI + Full digital networking with 32 trunk interfaces | Basic | Enabled
NETWORKING | Full/32
CTI | 80 Users
10 | CTI + Full digital networking with unlimited trunk interfaces | Basic | Enabled
NETWORKING | Full/Unlimited
CTI | 80 Users
11 | Voice over IP Gateway | Basic | Enabled
VOIP_GATEWAY | Enabled

*) In this specific case the additional full digital networking features for 4 trunk interfaces will be enhanced to 32 trunk interfaces which are defined in the Networking orange pack.

The colors in the table shall indicate the equivalent color pack. See also chapter License modularity and order rules.

#### License update procedure

1. Order the Basic upgrade license (FASBS 102 51/B) or any color or plus pack.
2. After you have received the Unique Pick Number for the upgrading process, connect the BMS to the system.
3. Upgrade the system according to the procedures described in chapter Special considerations for the software upgrade.
4. Keep the existing FECU plugged to the CPU-D4/CPU-D5.
5. Click on the system in the tree view.
6. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   The BMS automatically detects that there exists no license file in the system and proposes all boards (CPU‑D5, MFU, IPU or VMU-HD) which can be used for the creation of a new license file.
   Select the desired board and click on the ’Create License File ’ button. The license file will be created.

Note

When using the CPU-D5 in Release 13 the license file which is by default stored on the Compact Flash card will be renamed and has to be generated again, when upgrading to a Release 14 (or higher) system software.

1. Verify the entries in the ’Licensed feature’ table
   See also License Dialog Example 1:
2. Export the license file.
   Detailed description see To export the license file.
3. Build up an Internet connection via the Service PC or the customer PC and login to the Ericsson Partner Network (http:\\enterprise.ericsson.net).
4. Open the Web page of the License Administration Tool and follow the offered instructions to create and download the desired license by using the available Unique Pick Numbers
5. Import the downloaded license file into the system.
   Detailed description see To import the license file.
6. Verify whether the new content of the ’Licensed feature table’ matches with the features defined by the connected FECU, see chapter Mapping of the FECU Index into the license file.

Note

It is a must that the FECU is always connected to the system as it provides the system ID. The removal of the FECU has the consequence that all licenses will become invalid and the feature level of the system will automatically fall back to Release 8.

### Repair cases and repair licenses

Following hardware problems require attention for the customer’s licenses:

- Faulty CPU-D4 will be replaced by a CPU-D5
- Faulty CPU-D5/CPU-D5C without a connected FECU
- Faulty CPU-D5/CPU-D5C with a connected FECU
- Faulty FECU on a CPU-D4 or CPU-D5/CPU-D5C
- Faulty license carrier board MFU, VMU-HD or IPU
- Faulty Compact Flash Card on the license carrier board CPU-D5/CPU-D5C
- Faulty Compact Flash Card on the license carrier board MFU, VMU-HD or IPU

##### Faulty CPU-D4 will be replaced by a CPU-D5

1. Switch off the system
2. Exchange the faulty CPU-D4 by a CPU-D5.
3. Remove the FECU from the CPU-D4 and plug it to the CPU-D5
4. Insert the coldstart strap on the CPU-D5
5. Start up the system again.
   The system automatically detects combination of FECU and a valid license file on MFU,VMU-HD or IPU and renames the license file on the CPU-D5 in order to avoid multiple license files
6. Remove the coldstart strap
7. Connect the BMS to the system.
8. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   As the system ID which is given by the FECU is still the same, also all the licensed features are still valid. No further licensing activities are necessary.
9. Reload the customer data into the system.

##### Faulty CPU-D5/CPU-D5C without a connected FECU

1. Switch off the system
2. Exchange the faulty CPU-D5/CPU-D5C but keep the previous Compact Flash Card.
3. Insert the coldstart strap on the CPU-D5/CPU-D5C
4. Start up the system again.
5. Remove the coldstart strap
6. Connect the BMS to the system
7. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   As the system ID has been changed due to the new hardware, all entries in the ’Licensed feature’ table were removed as they became invalid. As a consequence of the invalid license entries the feature level of the system will automatically fall back to Release 8.
8. Click on ’Show license file’

Note

The hardware change is indicated by adding the entry ’Old system ID’.

1. Export the license file.
   Detailed description see To export the license file.
2. Build up an Internet connection via the Service PC or the customer PC and login to the Ericsson Partner Network (http:\\enterprise.ericsson.net).
3. Open the Web page of the License Administration Tool and follow the offered instructions to create a repair license (select 'create license'). As the license is always based on the system ID and the storage ID, and one of these components is still the same, the former license file can easily be recovered.
4. Import the downloaded license file into the system.
   Detailed description see To import the license file.
5. Verify whether the new content of the ’Licensed feature’ table matches with the previously installed features.
6. Reload the customer data into the system.

##### Faulty CPU-D5/CPU-D5C with a connected FECU

1. Switch off the system.
2. Exchange the faulty CPU-D5/CPU-D5C but keep the previous Compact Flash Card and the FECU.
3. Insert the coldstart strap on the CPU-D5/CPU-D5C.
4. Start up the system again.
5. Remove the coldstart strap
6. Connect the BMS to the system.
7. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   As the system ID which is given by the FECU is still the same, also all the licensed features are still valid. No further licensing activities are necessary.
8. Reload the customer data into the system.

##### Faulty FECU on a CPU-D4 or CPU-D5/CPU-D5C

1. Replace the faulty FECU on the CPU-D4/CPU-D5/CPU-D5C by any other FECU (Release independent, but Index must be the same as faulty FECU).

Note

Even if a CPU-D5/CPU-D5C is used, it is not possible to get a Repair license when removing a FECU.

1. Connect the BMS to the system.
2. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   As the system ID has been changed due to the new or missing FECU, all entries in the ’Licensed feature’ table were removed as they became invalid. As a consequence of the invalid license entries the feature level of the system will automatically fall back to the one given by a connected FECU or to the feature level of Release 8 if there is no FECU connected.
3. Export the license file.
   Detailed description see To export the license file.
4. Build up an Internet connection via the Service PC or the customer PC and login to the Ericsson Partner Network (http:\\enterprise.ericsson.net).
5. Open the Web page of the License Administration Tool and follow the offered instructions to create a repair license (select 'create license'). As the license is always based on the system ID and the storage ID, and one of these components is still the same, the former license file can easily be recovered.
6. Import the downloaded license file into the system.
   Detailed description see To import the license file.

##### Faulty license carrier board MFU, VMU-HD or IPU

1. Connect the BMS to the system.
2. Shut down the faulty board.
3. Exchange the faulty board but keep the previous Compact Flash Card.
4. Activate the board again.
5. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   As the storage ID of the Compact Flash card is still the same, also all the licensed features are still valid. No further licensing activities are necessary.

Note

When replacing a faulty IPU board, the IPU related licensing process has to be considered as well. See chapter Update of the IPU license because of a faulty IPU board.

##### Faulty Compact Flash Card on the license carrier board CPU-D5/CPU-D5C

1. Switch off the system.
2. Replace the Compact Flash Card on the CPU-D5/CPU-D5C by a new one.
3. Switch on the system again.
4. Connect the BMS to the system.

Note

The CPU-D5C only detects peripheral boards positioned in slot 1 and 2. All other boards which were previously supported due to the CPU-D5C upgrade license (MAX_BOARDS) will not start up. In order not to loose the customer date, the Update button in the Hardware details dialog must not be pressed for the missing boards.

1. Click on the system in the tree view.
2. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   The BMS automatically detects that there exists no license file in the system and propose all boards (CPU‑D5/CPU-D5C, MFU, IPU or VMU-HD) which can be used for the creation of new license file.
3. Select the CPU-D5/CPU-D5C and click on the ’Create license file’ button.

Note

As the license file does not contain valid entries, the feature level of the system will automatically fall back to the one given by a connected FECU or to the feature level of Release 8 if there is no FECU connected.

Note

When using a CPU-D5C the license file must be created on the CPU-D5C itself.

1. Export the license file.
   Detailed description see To export the license file.
2. Build up an Internet connection via the Service PC or the customer PC and login to the Ericsson Partner Network (http:\\enterprise.ericsson.net).
3. Open the Web page of the License Administration Tool and follow the offered instructions to create a repair license (select 'create license'). As the license is always based on the system ID and the storage ID, and one of these components is still the same, the former license file can easily be recovered.
4. Import the downloaded license file into the system.
   Detailed description see To import the license file.
5. Verify whether the new content of the ’Licensed feature’ table matches with the previously installed features.

##### Faulty Compact Flash Card on the license carrier board MFU, VMU-HD or IPU

1. Connect the BMS to the system.
2. Shut down the board with the faulty Compact Flash Card.
3. Replace the Compact Flash Card by a new one.
4. Activate the board again.
5. Click on the system in the tree view.
6. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   The BMS automatically detects that there exists no license file in the system and propose all boards (CPU‑D5, MFU, IPU or VMU-HD) which can be used for the creation of new license file.
7. Select one of the suggested carrier boards and click on the ’Create license file’ button.

Note

As the license file does not contain valid entries, the feature level of the system will automatically fall back to the one given by a connected FECU.

1. Export the license file.
   Detailed description see To export the license file.
2. Build up an Internet connection via the Service PC or the customer PC and login to the Ericsson Partner Network (http:\\enterprise.ericsson.net).
3. Open the Web page of the License Administration Tool and follow the offered instructions to create a repair license (select 'create license'). As the license is always based on the system ID and the storage ID, and one of these components is still the same, the former license file can easily be recovered.

Note

When replacing a faulty Compact Flash Card on the IPU board, the IPU related licensing process has to be considered as well. See chapter Update of the IPU license because of a faulty Compact Flash Card..

1. Import the downloaded license file into the system.
   Detailed description see To import the license file.
2. Verify whether the new content of the ’Licensed feature’ table matches with the previously installed features.

### Error situations

#### Shut down of a license carrier board (MFU, VMU-HD or IPU)

The shut down state of a license carrier board has no impact on the current license status as long as no re-programming of one of the licensed features will be performed which will cause a reload of the license information. As the license file is not available, the system automatically fetches the feature level from a connected FECU. If no FECU is available the feature level of the system will automatically fall back to the one of Release 8.

Note

When removing a shut down license carrier board, please be aware that at this stage any restart of the system will automatically cause a change of the current feature level either to the one of the connected FECU or to the system feature level of Release 8.

#### Multiple license files

During hardware changes it might happen that a board will be inserted which also carries a license file. The system automatically detects the second license file and performs a check which one matches with the system ID. The license file which does not match will be renamed automatically.

Note

If this error condition is detected during a system start-up, further restarts will take place until all unnecessary license files are renamed.

### Special considerations for the licensing of BusinessPhone Compact

#### General

BusinessPhone Compact is an initiative to further improve the current BusinessPhone Portfolio Offering (BP50, BP128i, BP250). BusinessPhone Compact is a “stripped” version of the BusinessPhone 50. It is a special commercial package consisting of:

- 1 BP 50 cabinet (BDV 101 05)
- 1 CPU-D5C (ROF 157 5124/3)
- 1 MFU
- 3 Dialog 4222 + 2 Dialog 4223 telephones (grey or black)
- 1 Key panel (grey or black)
- 1 Enterprise Application Suite, Online Tutorial and BMS CD-ROM,
- Set of Designation Cards

The CPU-D5C is fully hardware and feature compatible to a CPU-D5 with the only difference that it’s factory programming only supports a CSW R15 or higher and peripheral boards which are located in slot 1 and 2. The CPU‑D5C can be upgraded to a CPU-D5 via the BusinessPhone Compact Upgrade software license.

#### Peripheral boards behavior

The CPU-D5C only supports boards in slot 1 and 2. Boards located in slot 3 and above are not starting up (except IC-LU boards) and their yellow L2 LED‘s are rapidly flashing (for further details about the LED indication, see document Fault Tracing, 1545-ASB 150 02). Further these boards are not indicated in the BMS as the hardware details dialog is also limited to slot 0-2.

To support all board types in slot 3 and above, the CPU-D5C upgrade license (MAX_BOARDS) is required.

For adding boards in slot 3 and above us the procedure described in chapter Adding of boards.

#### Upgrade from a CPU-D5C to a CPU-D5

Use the normal license upgrade procedure as described in chapter Request an add on license (additional color or plus pack). (CPU-D5C upgrade license article number: FALBS 102 64/R)

Note

In case of upgrading the CPU-D5C to the CPU-D5 the license carrier board must be the CPU-D5C itself.

Note

After importing the BusinessPhone Compact Upgrade license a system restart needs to be performed. In case of finding the valid license entry at start up, the system can access all cards, however every new board position needs to be initialized. For further details see chapter Adding of boards.

Note

After the license upgrade the CPU-D5C will be detected as CPU-D5 in the hardware details dialog however the ROF-Info (ROF 157 5124/3) of the CPU-D5C remains.

### Special considerations for the licensing of external applications

#### General

Together with ASB 150 02 Release 15 the software key based licensing concept is replacing the WIBU-Key licensing for BackStage and CCA as well as the BEA licensing, for new sales.

For upgrade purposes the old licensing concepts will be continued as well as they can co-exist with the new licensing concept (both licenses are available to the applications).

The license handling towards the external applications is done via the BusinessLink 3.1 Server.

The BusinessLink Server has full information about:

- Remaining trial time in ASB 150 02
- License updates in ASB 150 02 (importing a new license file)
- Licensed external applications and their total and current free license values

Following license types are supported:

- Session based licensing (supported by BackStage)
  Each BackStage client requests a single license
- Seat based licensing (supported by CCA and BEA)
  The CCA Server requests all available licenses at once. The CCA Servers handles the retrieved licenses towards the CCA Clients.
  The BMS Server requests all available licenses at once. The BMS Server uses the retrieved licenses to define the maximum number of BEA extensions which can be setup.

#### WIBU key / BEA Licensing and software key based licensing

In case of upgrading an existing application (e.g. BEA 3.0, BackStage 6.0 or CCA 3.0), the old licensing concepts (PC based or WIBU-Key) and the new software key based licensing concept can co-exist.

Note

The applications and the BusinessLink have to be upgraded to fulfil the requirements of the new licensing concept. For the BEA the BusinessLink Server/Client has to be installed in addition.

The applications are always searching for both license concepts, which means that the total sum of licenses is available to the applications.

When ordering a new software key based license in order to enhance existing applications, always a color pack and if required also plus packs have be ordered.

##### BackStage license request sequence

##### Call Center Assistant license request sequence

##### BusinessPhone Extension Assistant license request sequence

#### License updates and the behavior of the applications

Clients which are currently occupying a license will not be influenced by a license reduction. Clients which are requesting licenses will get a warning message if the maximum possible value is already reached.

#### Read out the external application licenses via the BusinessLink

1. Start the TSAPI tool on the BusinessLink Server.
2. Connect to the BusinessLink Server by clicking on Communication in the menu bar and Open... in the context menu.
3. In the ApplicationLink server window click the Use Default... button to connect to the BusinessLink Server which is defined in the BusinessLink client.
4. In the CSTA Services window click the Application Licensing button to open the dedicated window

*) not applicable for the licenses which were requested by other applications using the same license ID

##### Example:
Query of BackStage Licenses

Revision: T © Ericsson Enterprise 2005