Administer > Administer the NNM iSPI for IP Telephony > Microsoft IP Telephony

Microsoft IP Telephony

As an administrator, you can configure attributes listed in the table below for monitoring the Microsoft IP telephony infrastructure discovered on the network. This topic includes the following sections:

To access the administration console:

  1. Log on to the NNMi console as an administrator.
  2. From the Workspaces navigation pane, click Configuration > iSPI for IP Telephony Configuration > Microsoft Configuration. The administration console for Microsoft IP telephony appears.

The administration console displays configuration options for the following attributes:

Attribute Description
Call Monitoring

Allows you to configure the call monitoring options of the Microsoft IP Telephony devices.

You can also use this option to view the existing call monitoring configurations.
Frontend

Allows you to configure the discovery of a central Lync site using the front end server pool.

You can also use this option to view the existing front end server pool communication configurations.
Gateway

Allows you to configure the polling interval for gateway interfaces and channels.

You can also configure the interval for performance data collection for the gateways using this page.
Lync End Users

Allows you to configure Lync end user groups.

You can configure end user groups, named end users, and end users to be excluded from monitoring on this page.
Periodic Collection

Allows you to configure periodic collection of CDR and QoE metrics.

This page also provides options to configure the interval for user discovery and topology discovery.
Proxy Communication

Allows you to configure the MS IPT proxy with the NNM iSPI for IP Telephony.

Site

Allows you to configure NNMi sites.

As an administrator, you can map the discovered Lync Server entities (edge servers, gateways, front end servers, registrar pools, and so on) on the network to the site for ease of administration.

Before running topology discovery for discovering Microsoft Lync servers and gateways, you must enable SNMP on Lync servers and gateways. You must also configure the read community string for the Lync servers and gateways. See the NNMi Online Help and the NNM iSPI for IP Telephony Installation Guide for Windows for more information.

Configure Call Monitoring

You can use the NNMi Microsoft Call Monitoring Configuration form to configure the following:

  • Configure Threshold Values for the Monitoring of QoE
  • Configure the Call Termination Cause Codes to be Monitored

Configure Threshold Values for the Monitoring of QoE

The Call Monitoring Configuration link on the Microsoft Configuration pane enables you to configure the monitoring of voice QoE metrics for calls in the Microsoft IP Telephony network. The Thresholds for QoE Monitoring tab on the NNM iSPI for Microsoft IP Telephony Monitoring Configuration pane allows you to specify the threshold values. On violation of set threshold for any of these parameters for any monitored call, the NNMi generates an incident conveying the resulting values and the set threshold.

To configure the QoE monitoring threshold values for Microsoft IP telephony calls:

  1. On the NNMi Microsoft configuration console, click Call Monitoring Configuration. The NNMi Microsoft Monitoring Configuration form opens.
  2. Click the Thresholds for QoE Monitoring tab. The Thresholds for QoE Monitoring tab page opens.

  3. Specify the required details in the fields provided under the Thresholds for QoE Monitoring section of the page. The following table describes the fields that appear under the section:

    By default, the threshold values set for these parameters are -1 or 0, and they indicate that the threshold-based monitoring is disabled and incidents will not be generated. You can enable monitoring and incident generation when you specify the valid threshold values.

    QoE Monitoring Parameter Description
    Audio Jitter Inter Arrival The average network jitter (audio) from the Real Time Control Protocol (RTCP) statistics during the call.
    Audio Packet Loss Rate The average packet loss rate (audio) during the call.
    Audio Round Trip The round trip time (audio) from the RTCP statistics during the call.
    Video Jitter Inter Arrival The average network jitter (video) from the RTCP statistics.
    Video Packet Loss Rate The average packet loss rate (video) during the call.
    Video Round Trip The round trip time (video) from the RTCP statistics during the call.
    Video Frame Loss Rate The percentage of total video frames that are lost during the call.
    Overall Avg Network MOS The average wideband Network mean opinion score (MOS) for the call. This metric depends on the packet loss, the jitter and the codec that are used for the call. This value must be within the range of 0.0 to 5.0.
    Send Listen MOS The average predicted wideband Listening MOS for the audio sent to the network during the call. This includes the speech and noise levels, and the capture device characteristics. This value must be within the range of 0.0 to 5.0.
    Receive Listen MOS The average predicted wideband Listening MOS for the audio received from the network during the call. This includes the speech and noise levels, codec, network conditions and the capture device characteristics. This value must be within the range of 0.0 to 5.0.
  4. Click Apply. The NNMi updates the QoE monitoring configuration values.

Configure Site-specific Threshold Values for the Monitoring of QoE

The Add Site Specific QOE Configuration section on the Thresholds for QoE Monitoring tab page enables you to configure QoE monitoring threshold values for the specific sites of your choice. After you specify threshold values specific to a site, the NNMi lists these threshold values in the Current Configuration section and uses them for the specific site, instead of the threshold values specified in the Thresholds for QoE Monitoring section.

To configure site-specific QoE monitoring threshold values:

  1. On the Thresholds for QoE Monitoring tab page, go to Site Specific Thresholds for QoE Monitoring pane > Add Site Specific QoE Configuration section.

  2. Under the Add Site Specific QoE Configuration section, specify the required details in the fields provided. The following table describes the fields under the section:

    Field NameDescription
    Site Identity

    Select the required site for which you want to configure the threshold values.

    Press and hold down the SHIFT key to select multiple sites.

    Audio Jitter Inter ArrivalThe average network jitter (audio) from the Real Time Control Protocol (RTCP) statistics during the call.
    Audio Packet Loss RateThe average packet loss rate (audio) during the call.
    Audio Round TripThe round trip time (audio) from the RTCP statistics during the call.
    Video Jitter Inter ArrivalThe average network jitter (video) from the RTCP statistics.
    Video Packet Loss RateThe average packet loss rate (video) during the call.
    Video Round TripThe round trip time (video) from the RTCP statistics during the call.
    Video Frame Loss RateThe percentage of total video frames that are lost during the call.
    Overall Avg Network MOSThe average wideband Network mean opinion score (MOS) for the call. This metric depends on the packet loss, the jitter and the codec that are used for the call. This value must be within the range of 0.0 to 5.0.
    Send Listen MOSThe average predicted wideband Listening MOS for the audio sent to the network during the call. This includes the speech and noise levels, and the capture device characteristics. This value must be within the range of 0.0 to 5.0.
    Receive Listen MOSThe average predicted wideband Listening MOS for the audio received from the network during the call. This includes the speech and noise levels, codec, network conditions and the capture device characteristics. This value must be within the range of 0.0 to 5.0.

    For more information about the QoE monitoring parameters, see Configuring Threshold Values for the Monitoring of QoE.

  3. Click Add/Modify. The configuration value for the site is displayed in the Current Configuration section.

To modify site-specific QoE monitoring threshold values:

  1. From the Current Configuration section, select the site-specific configuration that you want to modify .
  2. Click Modify. The current threshold values for the site is displayed in the Add Site Specific QoE Configuration section.
  3. Specify the new values.
  4. Click Add/Modify. The site-specific configuration is updated with the new values.You can modify only one site-specific threshold value at a time.

To delete site-specific QoE monitoring threshold values:

  1. From the Current Configuration section, select the site-specific configuration that you want to delete.
  2. Click Delete. The site-specific threshold values are deleted. After removing the site-specific threshold value configuration, the NNMi uses the values you provided in the Thresholds for QoE Monitoring section.

To export configurations to the Global Manager:

  • Click Export All Config to Global Manager. This sends all the available configuration information listed in the Current Configuration section, irrespective of the check boxes selected, to the Global Manager. If a global manager is not configured, the NNMi does not populate any data.

Configure the Call Termination Cause Codes to be Monitored

The Call Monitoring Configuration link on the Microsoft Configuration pane enables you to configure the termination cause codes that need to be monitored for a specific call in the Microsoft IP Telephony network. You can specify the following types of call termination cause codes:

  • Success Cause Codes: Lists the cause codes for call terminations that occurred without a call failure. For example, 'Participant session expired', 'Conference Terminated - Organizer Ended Session'
  • Expected Failure Cause Codes: Lists the cause codes for call terminations that occurred due to an expected call failure. For example, 'User does not exist', 'User not found'.
  • Unexpected Failure Cause Codes: Lists the cause codes for call terminations that occurred due to an unexpected call failure. For example, 'Service Unavailable', 'Cannot route to destination domain'.

After you specify the codes that you want to be monitored, the NNMi generates the CallTerminationReason incident only when the call termination occurs due to one of the specified call termination cause codes.

To configure the monitoring of call termination cause codes:

  1. On the NNMi Microsoft configuration console, click Call Monitoring Configuration. The NNMi Microsoft Monitoring Configuration form opens.
  2. Click the Call Termination Cause Monitoring tab. The Call Termination Cause Monitoring tab page opens.
  3. From the types of call termination cause codes sections, select the codes that you want to monitor, and then click (the Move Items to Selected List icon). The sections displayed are as follows:
    • Success Cause Codes
    • Expected Failure Cause Codes
    • Unexpected Failure Cause Codes
     
    • To select multiple random cause codes, press the Ctrl key and select the required codes.
    • To select a series of cause codes, press the Shift key and the select the series of cause codes.
    • To move a selected cause code from the monitored cause code list back to the cause code selection list, select the cause code and click ( the Move Items to Non-selected List icon).
    The default version of the property file — uc-cdr-termination-cause-codes.properties — is available in the following folder:
    • %NNMDataDir%\\shared\\ipt\\conf\lync

    The property file can be used to add new termination cause codes that are not listed in the types of call termination cause codes section. After you add a new termination cause code, make sure to restart the IPT jboss application server to reflect the change.

  4. Click Apply Changes to complete this configuration.

Configure Frontend Server Communication

The NNMi Microsoft Front End Configuration form lists the front end server pools configured to discover the corresponding central Lync sites.

To view the Frontend Communication Configuration tab page:

  • On the NNMi Microsoft configuration console, click Frontend Configuration. The NNMi Microsoft Front End Configuration form opens. The Frontend Communication Configuration tab page displays the list of the front end server pools configured to discover the corresponding central Lync sites. For information about the attributes related to the front end server pools configured by the administrator on the network, see Adding a New Front End Server Communication Configuration.

    • You can also select one of the configurations, and then click (the Open icon) to view the attribute details of the configuration.

Modify an Existing Front End Server Communication Configuration

To modify an existing front end server communication configuration:

  1. On the Frontend Communication Configuration tab page, select the front end server communication configuration that you want to modify.
  2. Click (the Edit icon). The Add/Update Frontend Communication Configuration page opens.
  3. Make the required changes, and then click (the Save icon) to save the modified configuration settings.

Delete an Existing Front End Server Communication Configuration

To delete an existing front end server communication configuration:

  1. On the Frontend Communication Configuration tab page, select the front end server communication configuration that you want to delete.
  2. Click (the Delete icon). The selected front end server communication configuration is deleted. You can click the Delete All icon to delete all the existing front end server communication configurations.

Add a New Front End Server Communication Configuration

The (New icon) on the Frontend Communication Configuration tab page enables you to add a new communication configuration. When you click the icon, the Add/Update Frontend Communication Configuration page opens. You can use the page to add a new communication configuration to seed a central Lync site for discovery in the NNMi. You can achieve this by adding the details of the front end server pool in the central Lync site.

Prerequisites for Configuring a New Front End Server Pool

To configure a new front end server pool, you must create a special login for the SQL Server database that is configured to work with Monitoring Server store of the Lync environment.

The login must meet the following requirements:

  • While creating this login, select the SQL Server authentication (and not the default Windows authentication).
  • The password of the login must never expire.
  • The public server role must be assigned to the login.
  • The login must be mapped to the LcsCDR and QoEMetrics databases. The LcsCDR and QoEMetrics databases must be members of the db_datareader, public, and ReportsReadOnlyRole roles.
  • The SQL user must be granted the Execute permission for the dbo.pIPIntToString scalar-valued function.

In addition, the SQL Server database for the Monitoring Server store must use mixed mode authentication (SQL Server and Windows Authentication mode).

To add a new front end server communication configuration:

  1. On the Add/Update Frontend Communication Configuration page, specify the required details in the fields provided on the page. The following table describes the fields on the page:
    Field Description
    Pool NameIndicates the fully qualified domain name for the front end server pool.
    User NameIndicates the name of the user who can access the systems in the front end server pool. The user must have permissions to run PowerShell commands on the front end servers. Specify the user name in the domain name\user name format.
    User PasswordIndicates the password for the user name.
    SQL UserIndicates the login of the SQL Server database that is configured to work with the Monitoring Server store of the Lync environment. The login must meet all the requirements listed in Prerequisites for Configuring a New Front End Server Pool section.
    SQL PasswordIndicates the password for the SQL user.
    Tenant Name

    Indicates the tenant name to be associated with the configuration. You can select a tenant name from the list of tenants configured and displayed in the drop-down list.

    See the NNMi Online Help for information about tenants, user groups, and security groups.

    Proxy NameIndicates the name of the proxy to be associated with the front end server pool. You can select a proxy from the list of proxies integrated with the NNMi.
    Pool DescriptionIndicates the description for the communication configuration.
  2. Click (the Save icon) to save the new front end server communication configuration.

Configure Gateway

You can use the NNMi Microsoft Gateway Configuration form to enable polling and set intervals for the polling of the following types of Lync gateway entities discovered on the network:

  • Interface
  • Channel
  • Performance Data Collection

Configure Gateway Interface State Polling

You can use the Interface tab page on the NNMi Microsoft Gateway Configuration form to enable polling for gateway interface states and specify the polling interval in minutes.

To configure the gateway interface state polling:

  1. On the NNMi Microsoft configuration console, click Gateway Configuration. The NNMi Microsoft Gateway Configuration form opens.
  2. Click the Interface tab.
  3. On the Interface tab page, select the respective tab for which you want to specify the polling configuration. The following table describes the tabs and the fields that appear on them:
    TabDescription
    Administrative State

    This tab allows you to specify the configuration to poll the change in the administrative state of the gateway interface. The available options are:

    • Enable Polling: Select this option to enable polling of the administrative state of the gateway interface.
    • Polling Interval (mins): Specify the interval in minutes to repeat the polling of the administrative state of the gateway interface.
    Line Alarm

    This tab allows you to specify the configuration to poll the changes in the line alarm state of the gateway interface. Line alarm indicates the presence of active alarms generated at the gateway interface for loop back, failure, and so on. This polling configuration helps you to monitor if there are any active alarms and generates the GatewayInterfaceLineStatusAlarmed incident if there are any active alarms present during the polling cycle. The available options are:

    • Enable Polling: Select this option to enable polling of the line alarm state of the gateway interface.
    • Polling Interval (mins): Specify the interval in minutes to repeat the polling of the line alarm state of the gateway interface.
    Operational StateThis tab allows you to specify the configuration to poll the change in the operational state of the gateway interface.

    The available options are:

    • Enable Polling: Select this option to enable polling of the operational state of the gateway interface.
    • Polling Interval (mins): Specify the interval in minutes to repeat the polling of the operational state of the gateway interface.
  4. Click (the Save icon) to save the configuration changes.

Configure Gateway Channel State Polling

You can use the Channel tab page on the NNMi Microsoft Gateway Configuration page to enable polling for gateway channel state and specify the polling interval in minutes.

To configure the gateway channel state polling:

  1. On the NNMi Microsoft configuration console, click Gateway Configuration. The NNMi Microsoft Gateway Configuration form opens.
  2. Click the Channel tab.
  3. On the Channel tab page, select the respective tab for which you want to specify the polling configuration. The following table describes the tabs and the fields that appear on them:
    TabDescription
    Operational StateThis tab allows you to specify the configuration to poll the change in the operational state of the gateway channel.

    The available options are:

    • Enable Polling: Select this option to enable polling of the operational state of the gateway channel.
    • Polling Interval (mins): Specify the interval in minutes to repeat the polling of the operational state of the gateway channel.
    Usage StateThis tab allows you to specify the configuration to poll the change in the usage state of the gateway channel.

    The available options are:

    • Enable Polling: Select this option to enable polling of the usage state of the gateway channel.
    • Polling Interval (mins): Specify the interval in minutes to repeat the polling of the usage state of the gateway channel.

    • Hold Time (mins): Specify the gateway channel hold time in minutes, to generate the channel idle incident (GatewayChannelStatusIdle) in the event of a gateway channel staying in the idle state for the specified hold time. It is recommended to specify the hold time as a multiple of the polling interval specified. For example, if you had specified a polling interval of five minutes, specify the hold time as 10 minutes.

  4. Click (the Save icon) to save the configuration changes.

Configure Gateway Performance Data Collection

You can use the Performance Data Collectiontab page on the NNMi Microsoft Gateway Configuration page to enable performance data collection for gateway interface states and specify the data collection interval in minutes.

To configure the gateway performance data collection:

  1. On the NNMi Microsoft configuration console, click Gateway Configuration. The NNMi Microsoft Gateway Configuration form opens.
  2. Click the Performance Data Collection tab.
  3. On the Performance Data Collection tab page, select the respective tab for which you want to specify the data collection configuration. The following table describes the tabs and the fields that appear on them:
    TabDescription
    Call Statistics

    This tab allows you to specify the configuration for performance data collection for the calls handled by the gateway. The available options are:

    • Enable Collection: Select this option to enable the performance data collection for the calls handled by the gateway.
    • Forward to Global Manager: Select this option if you want the gateway performance data to be sent from the current management server to the global manager. This option is enabled by default.
    • Collection Interval (mins): Specify the interval in minutes to repeat the performance data collection for the gateways discovered on the network.
    B-Channel Activity

    This tab allows you to specify the configuration for the collection of B-Channel activity data for generating reports based on the B-Channel usage. The available options are:

    • Enable Collection: Select this option to enable B-Channel activity data collection.
    • Forward to Global Manager: Select this option if you want the B-Channel activity data to be sent from the current management server to the global manager. This option is enabled by default.
    The NNMi uses the polling interval specified for the Usage State of the Channel tab page of the NNMi Microsoft Gateway Configuration form to collect the information about the B-Channel activity..
  4. Click (the Save icon) to save the configuration changes.

Configure Lync End Users

You can use the NNMi Microsoft Lync End Users Configuration form to configure the following types of Lync end user groups based on the end user attributes:

  • End user groups
  • Named end users
  • Excluded end users

This type of configuration helps in gathering the CDR details for a required group of users. A user can be included in multiple user groups. In this event, the lowest reporting order number configured for the user in a group is given priority when gathering the CDR details for that user. You can configure the following types of end user groups:

Create End User Groups

You can use the End User Groups tab page on the NNMi Microsoft End User Configuration form to view the existing end user groups that are configured. You can also use this page to add new and modify the existing end user groups.

To view the End User Groups tab page:

  1. On the NNMi Microsoft configuration console, click Lync End Users Configuration. The NNMi Microsoft End User Configuration form opens.
  2. Click the End User Groups tab.
  3. The End User Groups tab page displays the list of the configured Lync end user groups. The details displayed on the tab page are described in the following table:
    Attribute Description
    End User GroupIndicates the name configured for the end user group.
    Reporting OrderIndicates the reporting order configured for the end user group.

You can also select one of the configurations, and then click (the Open icon) to view the details of the configuration.

Modify an Existing End User Group Configuration

To modify an existing end user group configuration:

  1. On the End User Group tab page, select the configuration that you want to modify.
  2. Click (the Edit icon). The Add/Update End User Group Configuration page opens.
  3. Make the required changes, and then click (the Save icon) to save the modified configuration settings.

Delete an Existing Front End Server Communication Configuration

To delete an existing front end server communication configuration:

  1. On the End User Group tab page, select the configuration that you want to delete.
  2. Click (the Delete icon). The selected end user group configuration is deleted. You can click the Delete All icon to delete all the existing configurations.

Add a New Lync End User Group

The (New icon) on the End User Groups tab page enables you to add a new end user group. When you click the icon, the Add/Update End User Group Configuration page opens. You can use the page to add a new end user group configuration.

To add a new end user group configuration:

  1. On the Add/Update End User Group Configuration page, specify the required details in the fields provided on the page. The following table describes the fields on the page:
    Field Description
    Group NameIndicates the name of the end user group.
    DescriptionIndicates a description of the end user group.
    Reporting OrderIndicates the reporting order number to be configured for the end user group. The end user group with the lowest order number is given priority.
    Filter Editor Section

    Enables you to create a filter to map the required end users under the end user group. This section provides the following options:

    • Attribute
    • Operator
    • Value

    For more information about the Filter Editor section, see About the Filter Editor Section.

    For more information about defining a filter, see Creating a Filter for an End User Group.

  2. Click (the Save icon) to save the new end user group configuration.

About the Filter Editor Section

The Filter Editor section of the Add/Update End User Group Configuration page allows you to do the following:

  • You can select one of the following end user attributes from the Attribute drop-down list for a filter condition:
    • groupName
    • displayName
    • sipaddress
    • lineURI
    • company
    • countryOrRegionDisplayName
    • department
    • city
    • registrarPool
    • targetRegistrarPool
    • homeServer
    • targetHomeServer
    • enabledForRichPresence
    • audioVideoDisabled
    • voicePolicy
    • conferencingPolicy
    • dialPlan
    • locationPolicy
    • clientPolicy
    • clientVersionPolicy
    • archivingPolicy
    • pinPolicy
    • externalAccessPolicy
    • hostedVoiceMail
    • hostedVoiceMailPolicy
    • hostingProvider
  • You can select one of the following operators from the Operator drop-down list:
    • =: Indicates that the filter must be applied on the attribute that matches the exact value provided.
    • !=: Indicates that the filter must be applied to the attributes that do not match the value provided.
    • like: Indicates that the filter must be applied to all the attributes that match the specified value. You can specify a group of attributes using the wildcard characters percent (%) to match a string and the question mark (?) to match a character in the value provided.
    • not like: Indicates that the filter must be applied to all the attributes that do not match the specified value. You can specify a group of attributes using the wildcard characters percent (%) or asterisk (*) to match a string and the question mark (?) to match a character in the value provided.
    • in: indicates that the filter must be applied to all the attributes matching the list of values specified. You must specify each value in a separate line when typing multiple values.
    • not in: indicates that the filter must not be applied to all the attributes that do not match the list of values specified. You must specify each value in a separate line when typing multiple values.
  • To insert a filter condition (Attribute, Operator, and Value), use the Insert option after selecting the relevant AND or OR condition.
  • To replace a filter condition with a newly specified condition, select the filter condition and then click Replace.
  • To delete a condition, select the filter condition or an AND or an OR condition, and then click Delete.

Create a Filter for an End User Group

This section gives you an example of creating an end user group based on the following attributes:

  • All end users where the company attribute is configured as XYZ
  • All end users where the display name has the string Mgmt% prefixed to the display name.

To create an end user configuration based on the conditions listed, you must define an end user configuration filter using the Add/Update End User Group Configuration page.

To define a filter on the Add/Update End User Group Configuration page:

  1. Click AND. This displays the AND condition parenthesis in the Filter String section
  2. In the Filter Editor section:
    1. From the Attribute drop-down list, select company.
    2. From the Operator drop-down list, select like.
    3. In the Value box, type XYZ.
  3. Click Append. The Filter String section displays the following string: (company like XYZ)
  4. Click AND. The Filter String section now displays the following string: (company like XYZ AND ())
  5. In the Filter Editor section:
    1. From the Attribute drop-down list, select displayName.
    2. From the Operator drop-down list, select like.
    3. In the Value box, type Mgmt%.
  6. Click Append. The Filter String section now displays the complete string as: (company like XYZ AND (displayName like Mgmt%)).

Create Named End User Groups

You can use the Named End Users tab page on the NNMi Microsoft End User Configuration form to create end user groups based on the named users discovered on the network. Named users help in the easy identification of users in reports.

To create an end user groups based on the named users:

  1. On the NNMi Microsoft configuration console, click Lync End Users Configuration. The NNMi Microsoft End User Configuration form opens.
  2. Click the Named End Users tab.
  3. On the Named End Users tab page, create a filter to map the required named end users under a named end user group. For more information about creating a filter, see Create a Filter for Named End Users.
  4. Click (the Save icon) to save the new named end users configuration.

To view the newly added named end user, click (the Refresh icon).

Create a Filter for Named End Users

This section gives you an example of creating an end user group based on the following attributes:

  • All end users where the company attribute is configured as XYZ
  • All end users where the displayName has the string _Mktg suffixed in the display name.

To create an end user configuration based on the conditions listed , you must define a named end user configuration filter using the Named End Users tab page.

To define a filter on the Named End Users tab page:

  1. Click AND. This displays the AND condition parenthesis in the Filter String section
  2. In the Filter Editor section:
    1. From the Attribute drop-down list, select company.
    2. From the Operator drop-down list, select like.
    3. In the Value box, type XYZ.
  3. Click Append. The Filter String section displays the following string: (company like XYZ)
  4. Click AND. The Filter String section now displays the following string: (company like XYZ AND ())
  5. In the Filter Editor section:
    1. From the Attribute drop-down list, select displayName.
    2. From the Operator drop-down list, select like.
    3. In the Value box, type %_Mktg.
  6. Click Append. The Filter String section now displays the complete string as: (company like XYZ AND (displayName like %_Mktg)).

Create Excluded End User Groups

You can use the Excluded End Users tab page on the NNMi Microsoft End User Configuration form to create end user groups to be excluded from monitoring.

To create an end user groups based on the excluded users:

  1. On the NNMi Microsoft configuration console, click Lync End Users Configuration. The NNMi Microsoft End User Configuration form opens.
  2. Click the Excluded End Users tab.
  3. On the Excluded End Users tab page, create a filter to map the required excluded end users under an excluded end user group. For more information about creating a filter, see Create a Filter for Excluded End Users.
  4. Click (the Save icon) to save the excluded end users configuration.

To view the newly added excluded end user, click (the Refresh icon).

Create a Filter for Excluded End Users

This section gives you an example of creating an end user group based on the following attributes:

  • All end users where the department attribute is configured as SrMgmt.
  • All end users where the city is Washington.

To create an excluded end user configuration based on the conditions listed , you must define an excluded end user configuration filter using the Excluded End Users tab page.

To define a filter on the Excluded End Users tab page:

  1. Click AND. This displays the AND condition parenthesis in the Filter String section
  2. In the Filter Editor section:
    1. From the Attribute drop-down list, select department.
    2. From the Operator drop-down list, select =.
    3. In the Value box, type SrMgmt.
  3. Click Append. The Filter String section displays the following string: (department=SrMgmt)
  4. Click AND. The Filter String section now displays the following string: (department=SrMgmt AND ())
  5. In the Filter Editor section:
    1. From the Attribute drop-down list, select city.
    2. From the Operator drop-down list, select =.
    3. In the Value box, type Washington.
  6. Click Append. The Filter String section now displays the complete string as: (department=SrMgmt AND (city=Washington)).

You can select one of the following end user attributes from the Attribute drop-down list for a filter condition:

  • displayName
  • sipaddress
  • company
  • countryOrRegionDisplayName
  • department
  • city

Configure Periodic Collection

You can use the NNMiMicrosoft Periodic Collection Configuration form to configure the following:

  • Call Details Record (CDR) collection
  • Quality of Experience (QoE) score collection
  • Topology discovery interval
  • User discovery interval

Configure Call Detail Record Collection

The CDR tab page on the NNMi Microsoft Periodic Collection Configuration form allows you to configure the call details record collection on the Microsoft IP telephony network.

To configure the CDR collection:

  1. On the NNMi Microsoft configuration console, click Periodic Collection Configuration. The NNMi Microsoft Periodic Collection Configuration form opens.
  2. Click the CDR tab.

  3. On the CDR tab page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

    FieldDescription
    Enable CollectionSelect this option to enable CDR collection.
    Exclude IMSelect this option to exclude CDR collection for Instant Messaging (IM) sessions.
    Forward to Global ManagerSelect this option to send the processed call information from the current management server to the global manager. This option is enabled by default.
    Interval (mins)

    Select the interval in minutes for the CDR collection to be repeated on the network. You can select one of the following intervals:

    • 15
    • 30
    • 45
    • 60

  4. Click (the Save icon) to save the CDR collection configuration changes.

Configure Quality of Experience Collection

The QoE tab page on the NNMi Microsoft Periodic Collection Configuration form allows you to configure the QoE score collection on the Microsoft IP telephony network.

To configure the QoE score collection:

  1. On the NNMi Microsoft configuration console, click Periodic Collection Configuration. The NNMi Microsoft Periodic Collection Configuration form opens.
  2. Click the QoE tab.

  3. On the QoE tab page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

    FieldDescription
    Enable CollectionSelect this option to enable QoE score collection.
    Forward to Global ManagerSelect this option to send the processed QoE score information from the current management server to the global manager. This option is enabled by default.
    Interval (mins)

    Select the interval in minutes for the QoE score collection to be repeated on the network. You can select one of the following intervals:

    • 15
    • 30
    • 45
    • 60

  4. Click (the Save icon) to save the QoE score collection configuration changes.

Configure Topology Discovery Details

The Topology Discovery tab page on the NNMi Microsoft Periodic Collection Configuration form helps you to enable topology discovery on the network and schedule the interval in hours for the topology discovery to be repeated on the network.

To enable the topology discovery:

  1. On the NNMi Microsoft configuration console, click Periodic Collection Configuration. The NNMi Microsoft Periodic Collection Configuration form opens.
  2. Click the Topology Discovery tab.

  3. On the Topology Discovery tab page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

    FieldDescription
    Enable CollectionSelect this option to enable topology discovery.
    Interval (hrs)

    Select the interval in hours for topology discovery to be repeated on the network. You can select one of the following intervals:

    • 12
    • 24
    • 48
    • 60

  4. Click (the Save icon) to save the topology discovery configuration changes.

Configure User Discovery Details

The User Discovery tab page on the NNMi Microsoft Periodic Collection Configuration form allows you to configure the user discovery details on the Microsoft IP telephony network.

To enable the user discovery:

  1. On the NNMi Microsoft configuration console, click Periodic Collection Configuration. The NNMi Microsoft Periodic Collection Configuration form opens.
  2. Click the User Discovery tab.

  3. On the User Discovery tab page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

    FieldDescription
    Enable CollectionSelect this option to enable user discovery.
    Interval (hrs)

    Select the interval in hours for user discovery to be repeated on the network. You can select one of the following intervals:

    • 12
    • 24
    • 48
    • 60

  4. Click (the Save icon) to save the user discovery configuration changes.

Configure MS IPT Proxy with NNMi

In Microsoft Lync Server environment, MS IPT Proxy, a .NET component is responsible for most of the data collection using remote powershell commands. All the requests (such as topology discovery, and CDR collection) from the NNMi pass through MS IPT Proxy to the Microsoft Lync server. It is necessary that you install MS IPT Proxy before you start using the NNMi. For more information about installing MS IPT Proxy, see the NNMiInstallation Guide for Windows.

You can install one or more proxies in your environment based on your requirements.

The NNMi supports the following scenarios:

  • Install NNMi on a Linux server and MS IPT Proxy on a Windows server.
  • Install NNMi on a Windows server and MS IPT Proxy on a different Windows server.
  • Install NNMi and MS IPT Proxy on the same Windows server.

After installing the NNMi and MS IPT Proxy, you must integrate them so that they communicate with each other. If the NNMi does not communicate with MS IPT Proxy, the NNMi cannot discover or monitor the Microsoft Lync Server environment.

To view the proxy communication configurations in your environment:

  • On the NNMi Microsoft configuration console, click Proxy Communication Configuration. The NNMi Microsoft Proxy Communication Configuration form opens.

    The Proxy Communication Configuration tab page displays the list of the proxy communication configurations. The attributes related to the proxy communication configured by the administrator on the network are described in the following table:

    Attribute Description
    Proxy Name Indicates the name given to the MS IPT Proxy by the administrator.
    Proxy IP Address Indicates the IP address of the Windows server on which the MS IPT Proxy is installed.
    Proxy Port Indicates the port number on which MS IPT Proxy is installed.
    Status Indicates whether the proxy is connected with NNMi or not.
    Last Collection Status Indicates the status of last data collection from the front end server pool using the proxy.

    For information about adding a new proxy communication configuration, see Adding a New Proxy Communication Configuration.

Modify an Existing Proxy Communication Configuration

To modify an existing proxy communication configuration:

  1. From the Proxy Communication Configuration tab page, select the proxy communication configuration that you want to modify.
  2. Click (the Edit icon). The Add/Update Proxy Communication Configuration page opens.
  3. Make the required changes, and then click (the Save icon) to save the modified configuration settings.You can update only the Proxy IP Address and the Proxy Port values.

Delete an Existing Proxy Communication Configuration

To delete an existing proxy communication configuration:

  1. From the Proxy Communication Configuration tab page, select the proxy communication configuration that you want to delete.
  2. Click (the Delete icon). The selected proxy communication configuration is deleted. You can click the Delete All icon to delete all the existing proxy communication configurations.
  3. This deletes the selected proxy communication configuration.

Add a New Proxy Communication Configuration

The (New) icon on the Proxy Communication Configuration tab page enables you to add a new proxy communication configuration. When you click the icon, the Add/Update Proxy Communication Configuration page opens. You can use the page to add a new proxy communication configuration to integrate proxies with the NNMi.

To integrate a proxy communication configuration with theNNMi:

  1. On the Add/Update Proxy Communication Configuration page, specify the required details in the fields provided. The following table describes the fields on the page:
    Field Description
    Proxy NameIndicates the name of the MS IPT Proxy. You can give any meaningful name to the proxy; however, you cannot edit this field after the configuration is saved.
    Proxy IP AddressIndicates the IP address of the Windows server on which MS IPT Proxy is installed.
    Proxy PortIndicates the port number on which MS IPT Proxy is installed.
    You can get the IP address and the port number from the msipt.proxy.properties file that is present in the server where you installed MS IPT Proxy. Access this file from the following location in that server:

    %NnmDataDir%\shared\ipt\conf

  2. Click (the Save icon) to save the new proxy communication configuration.

Configure Sites

You can use the NNMi Microsoft Site Configuration form to view the configured sites as well as create new suite configurations to discover the Lync Server entities such as edge servers, gateways, front end servers, and registrar pools on the network. Creating and maintaining sites eases the task of monitoring the discovered Lync Server entities.

To view the Site Configuration tab page:

  • On the NNMi Microsoft configuration console, click Site Configuration. The NNMi Microsoft Site Configuration form opens. The Site Configuration tab page displays the list of the sites configured to discover the Lync Server entities. For more information about the attributes of the configured sites, see Adding a New Site Configuration.

    You can also select one of the configurations, and then click (the Open icon) to view the attribute details of the configuration.

Modify an Existing Site Configuration

To modify an existing end user group:

  1. On the Site Configuration tab page, select the site that you want to modify.
  2. Click (the Edit icon). The Add/Update Site Configuration page opens.
  3. Make the required changes, and then click (the Save icon) to save the modified configuration settings.

Delete an Existing Site Configuration

To delete an existing site:

  1. On the Site Configuration tab page, select the site that you want to delete.
  2. Click (the Delete icon). The selected site configuration is deleted. You can click the Delete All icon to delete all the existing configurations.

Add a New Site Configuration

The (New icon) on the Site Configuration tab page enables you to add a new site configuration. When you click the icon, the Add/Update Site Configuration page opens. You can use the page to add a new site configuration and map the necessary Lync Server entities to the site.

To add a new site communication configuration:

  1. On the Add/Update Site Configuration page, specify the required details in the fields provided on the page. The following table describes the fields on the page:
    Field Description
    SiteIndicates the name of the site.
    DescriptionIndicates a description of the site.
    OrderIndicates the order number to be configured for the site. The site with the lowest order number is given priority.
    Site Definition Section

    Enables you to create filter to map the required Lync Server entities under the site. This section provides the following options:

    • Attribute
    • Operator
    • Value

    For more information about the Site Definition section, see About the Site Definition Section.

    For more information about defining a filter, see Creating a Filter for Site Configuration.

  2. Click (the Save icon) to save the new site communication configuration.

About the Site Definition Section

The Site Definition section of the Add/Update Site Configuration page allows you to do the following:

  • You can select one of the following site attributes from the Attribute drop-down list for a filter condition:
    • Edge Server
    • Gateway
    • Registrar Pool
    • Frontend Server
  • You can select one of the following operators from the Operator drop-down list:
    • =: Indicates that the filter must be applied on the attribute that matches the exact value provided.
    • !=: Indicates that the filter must be applied to the attributes that do not match the value provided.
    • like: Indicates that the filter must be applied to all the attributes that match the specified value. You can specify a group of attributes using the wildcard characters percent (%) to match a string and the question mark (?) to match a character in the value provided.
    • not like: Indicates that the filter must be applied to all the attributes that do not match the specified value. You can specify a group of attributes using the wildcard characters percent (%) or asterisk (*) to match a string and the question mark (?) to match a character in the value provided.
  • To insert a filter condition (Attribute, Operator, and Value), use the Insert option after selecting the relevant AND or OR condition.
  • To replace a filter condition with a newly specified condition, select the filter condition and then click Replace.
  • To delete a condition, select the filter condition or an AND or an OR condition, and then click Delete.

Create a Filter for Site Configuration

This section gives you an example of creating a site configuration that includes the following Lync Server entities:

  • All the front end servers that start with the name ipt and msipt
  • Associated with a registrar pool named Primary Registrar

To create a site configuration based on the conditions listed , you must define a site configuration filter using the Add/Update Site Configuration page.

To define a filter on the Add/Update Site Configuration page:

  1. Click AND. This displays the AND condition parenthesis in the Site Definition section.
  2. Click AND. This displays the AND condition as a nested condition within the AND condition defined in the previous step.
  3. Select the nested AND condition.
  4. In the Site Definition section:
    1. From the Attribute drop-down list, select Frontend Server.
    2. From the Operator drop-down list, select like.
    3. In the Value box, type ipt%.
  5. Click Append. The Filter String section displays the following string: (Frontend Server like ipt%)
  6. Select the nested AND condition.
  7. In the Site Definition section:
    1. From the Attribute drop-down list, select Frontend Server.
    2. From the Operator drop-down list, select like.
    3. In the Value box, type msipt%.
  8. Click Append. This updates the string as follows: (Frontend Server like ipt% AND Frontend Server like msipt%). This filter string defines the first condition for the site configuration — to filter all the frontend servers names that start with ipt and msipt.
  9. Click AND. The Filter String section now displays the following string: ((Frontend Server like ipt% AND Frontend Server like msipt%) AND ())
  10. In the Site Definition section:
    1. From the Attribute drop-down list, select Registrar Pool.
    2. From the Operator drop-down list, select =.
    3. In the Value box, type Primary Registrar.
  11. Click Append. The Filter String section now displays the complete string as: ((Frontend Server like ipt% AND Frontend Server like msipt%) AND (Registrar Pool = Primary Registrar)).

Validate the Site Definition

The Validate Site Definition tab on the Add/Update Site Configuration page allows you to test the validity of the filter that you configured for the Lync Server entities discovered on the network. This opens the Validate Site Definition Result window that displays the results of the filter you configured.

  • The Test Site Definition window displays the details in a tabular format with the Filter and Result columns.
  • The status Pass indicates that there were matches for the filter criteria among the list of Lync Server entities discovered on the network.
  • The status Fail indicates that there were no matches for the filter criteria.

Integrate with SiteScope

You can integrate the NNM iSPI for IP Telephony with SiteScope to gather performance metrics for the Microsoft unified communication and collaboration applications that include the Lync Server applications and the Exchange Server application on your network. With this integration, you can collect performance metrics and generate reports using the monitors that SiteScope provides for the following applications:

  • Microsoft Exchange
  • Microsoft Lync Server applications comprising:
    • Audio/Video conferencing server
    • Archiving server
    • Director server
    • Edge server
    • Frontend server
    • Mediation server
    • Monitoring server
    • Registrar server

Integration Considerations

Make sure that you have the completed the following activities to complete this integration:

  • Installed and configured SiteScope according to the instructions provided in the SiteScope documentation before attempting this integration.
  • Created a data integration connection using the SiteScope console between SiteScope and NNM iSPI for IP Telephony. See the SiteScope documentation to configure the connection between SiteScope and NNMi.
    • You must specify the URL in the following format in the Receiver URL box if you are using an HTTP connection: http://IPTHostName:10080/nms-spi-uc-sitescope-war/Sample. IPTHostName refers to the system name where you have installed the NNM iSPI for IP Telephony.
    • If you provide an HTTPS link as the Receiver URL for the data integration, make sure that you import the NNMi license file to SiteScope. See the NNMi Deployment Reference Guide for more information.
    • You must specify the URL in the following format in the Receiver URL box if you are using an HTTPS connection:https://IPTHOSTName:HTTPS PORT NUMBER/nms-spi-uc-sitescope-war/Sample
  • Enable performance monitoring details to be sent for Microsoft unified communication and collaboration applications from SiteScope to the NNM iSPI for IP Telephony as discussed in the following section.

Enable Performance Monitoring for Microsoft Unified Communication and Collaboration Applications

  1. Log on as an administrator to the NNMi console
  2. Click Integration Module Configuration > SiteScope IP Telephony. This opens the SiteScope IP Telephony tab page.
  3. Select Microsoft UC Applications Performance Monitoring
  4. Select the Forward to Global Manager option if you want the information to be sent from the current management server to the global manager. This option is enabled by default.
  5. Click to save the integration configuration.

Send Help Center feedback