Jump to: navigation, search

Processing of Enabled Seats

Agent Connector

The enabled seat count for Agent Connector is measured differently than the other enabled seat counts mentioned here. The daily enabled seat count for Agent Connector is defined as the total number of unique seats (i.e. Places and DNs) that has been used during the day that are not using a Genesys Agent Desktop, Genesys Supervisor Desktop, or Interaction Workspace for the log-in

Chat Media Type for Interaction Server

Assume any seats configured in the system may be used to log into the Interaction Server and then once logged in, they can use any of the media channel they want. In this case, the enabled seat count is the total of the number of Places associated with at least one DN, plus the number of DNs not associated with a Place.

Computer Telephony Integration Contact-Center Legacy

A Computer Telephony Integration (CTI) seat refers to a physical seat occupied by an Agent who is logged in to a T-Server, SIP Server or Interaction Server in a tenant for which at least one tenant-specific instance (in other words, has only this tenant in the tenant list) of Universal Routing Server (URS) is configured with a connection to a database access point (DAP). If a URS with a DAP connection is associated with multiple tenants, LRM does not report any usage of CTI seat licenses associated with that URS instance. If a tenant has multiple URS instances with DAP connections, LRM counts one CTI seat license per enabled seat. LRM provides a report of enabled CTI seat count based on the presence of a DAP connection and applies to all of the logged in seats in a given tenant. The enabled seat count is the total of the number of Places associated with at least one DN, plus the number of DNs not associated with a Place, where the DNs belong to a switch that belong to a tenant that meet the above URS configuration condition.

E-Mail Media Type for Interaction Server

Assume any seats configured in the system may be used to log into the Interaction Server and then once logged in, they can use any of the media channel they want. In this case, the enabled seat count is the total of the number of Places associated with at least one DN, plus the number of DNs not associated with a Place.

Genesys CIM Platform - Single-Site and Multi-Site

A CIM Platform has two kinds of seats: Single-Site (SS) seat and Multi-Site (MS) Concurrent seat. Each is a physical seat occupied by a person who is logged in to a T-Server, SIP Server, or Interaction Server in a location defined as SS for Single-Site or MS for Multi-Site in the Entitlement File. LRM determines if the site is defined as Single-Site or Multi-Site by examining data in the entitlement tables, which contain the data from the Entitlement File. When the site has been defined as SS or MS, all of the login sessions from the preselected set are calculated as a Genesys CIM Platform- SS or MS sellable items. For the CIM Platform - MS or SS Concurrent seats, LRM counts the number of enabled seats as the total of the number of Places associated with at least one DN, plus the number of DNs not associated with a Place.

Genesys Inbound Voice

A Genesys Inbound Voice seat is a physical seat whose occupant is logged in to any T-Server other than SIP Server. A seat is enabled for use if the DN associated with this seat is on this kind of Switch. For Genesys Inbound Voice, the enabled seat count for the system is the total of the number of Places associated with at least one DN, plus the number of DNs not associated with any Place, where the DNs belong to a switch that is not configured as 0 (Unknown Switch), 72 (SIP Switch) or 63 (OM Switch).

Genesys Network Voice

A Genesys Network Voice seat is a physical seat occupied by an Agent; who is configured as an Agent and logged into a T-Server other than SIP Server, on a system that has one or more (non-SIP) Network T-Servers configured. A seat is enabled for use if the DN associated with this seat is on this kind of switch and the LRM has determined that one or more (non-SIP) Network T-Servers is configured. In this case, the enabled seat count for Genesys Network Voice for the system is the total of the number of Places associated with at least one DN, plus the number of DNs not associated with a Place, where the DNs belong to a switch that is not configured as 72 (SIP Switch) or 63 (OM Switch).

Limitation

There is no reliable way to determine a Network Switch or a Network T-Server. However, it is possible to configure the Network Switch as a Voice switch in Configuration Database. You can also enable LRM to count Genesys Network Voice sellable items by setting the lrm-network-switch option in the [lrm] section to true. For more information about how to configure this option, see Configuration Options.

Genesys SIP Server

A SIP Server seat is a physical seat whose occupant is logged in to SIP Server. A seat is enabled for SIP Server use if the DN associated with this seat is on a SIP Server Switch. For Genesys SIP Server, the enabled seat count for the system is the total of the number of Places associated with at least one DN, plus the number of DNs not associated with any Place, where the DNs belong to a switch that is configured as 72 (SIP Switch).

Genesys Social Media

Assume any seats configured in the system may be used to log into the Interaction Server and then once logged in, they can use any of the media channel they want. In this case, the enabled seat count is the total of the number of Places associated with at least one DN, plus the number of DNs not associated with a Place.

Genesys Workforce Management

A Workforce Management seat is a physical seat occupied by a person who is logged in to a T-Server, SIP Server, or Interaction Server where WFM Data Aggregator is configured with a connection to a Stat Server associated with the person's tenant. When these conditions are met, the LRM considers the seats enabled for this tenant to be enabled for Workforce Management. The enabled seat count is the total of: the number of Places associated with at least one DN, plus the number of DNs not associated with a Place, where the DNs belong to a switch that belongs to a tenant that has Workforce Management enabled.

Genesys Outbound Contact - Multi-Site

The License Reporting Manager assumes that any seats configured in a Multi-Site environment is enabled for outbound contacts. LRM determines from the entitlement file whether the location is SS or MS. If the location is multi-site, LRM counts the number of enabled seats as the total of the number of Places associated with at least one DN, plus the number of DNs not associated with a Place.

Skills-Based Routing

The License Reporting Manager assumes that any seats configured in the customer environment may be logged in by an agent with skills configured. LRM counts the number of enabled seats as the total of the number of Places associated with at least one DN, plus the number of DNs not associated with a Place.

Third-Party Work Items

Assume any seats configured in the system may be used to log into the Interaction Server and then once logged in, they can use any of the media channel they want. In this case, the enabled seat count is the total of the number of Places associated with at least one DN, plus the number of DNs not associated with a Place.

Genesys Agent Desktop

This sellable item is based on the client software used to log in. The LRM assumes that any seats configured in the system may be used to log into the T-Server, SIP Server or Interaction Server. In this case, the enabled seat count is the total of the number of Places associated with at least one DN, plus the number of DNs not associated with a Place.

Genesys Supervisor Desktop

This sellable item is based on the client software used to log in. The LRM assumes that any seats configured in the system may be used to log into the T-Server, SIP Server or Interaction Server. In this case, the enabled seat count is the total of the number of Places associated with at least one DN, plus the number of DNs not associated with a Place.

Genesys Info Mart Server

In a deployment where at least one instance of the Genesys Info Mart application has been configured, the enabled seat count for Genesys Info Mart Server is the total of the number of Places associated with at least one DN, plus the number of DNs not associated with a Place.

Genesys Interactive Insights

In a deployment where at least one instance of the Genesys Info Mart application has been configured and Interactive Insights has been defined in the Entitlement File, the enabled seat count for Genesys Info Mart Server is the total of the number of Places associated with at least one DN, plus the number of DNs not associated with a Place.

Interaction Workspace

This sellable item is based on the client software used to log in. The LRM assumes that any seats configured in the system may be used to log into the T-Server, SIP Server or Interaction Server. In this case, the enabled seat count is the total of the number of Places associated with at least one DN, plus the number of DNs not associated with a Place.

IVR Connector

An enabled IVR Connector port is an IVR Port object on the Configuration Server where the IVR Port option is set to enabled. The LRM counts the total number of these objects for the number of enabled IVR Connector ports.

High-Availability

A T-Server, or SIP-Server may be configured as High-Availability if you set up a Backup Server for it. A seat is enabled for High-Availability if it can be used to log into such a T-Server. In this case, the enabled seat count for High-Availability is the total of the number of Places associated with at least one DN, plus the number of DNs not associated with a Place, where the DNs belong to a switch where its associated T-Server has been configured as Highly-Available.

Voicemail

A voicemail count is a DN object on the Configuration Server where the DN object has the [Tserver] gvm_mailbox option set to any value. The LRM counts the number of these DN objects as the number of enabled mailboxes.

This page was last edited on July 30, 2013, at 13:59.

Feedback

Comment on this article:

blog comments powered by Disqus