The Min SE parameter 1

[titiksha]

Hi All,

We are using NICE Perform 3.2.

We have been receiving frequent alarms on NICE Sentinel with the below description;

" The Min SE parameter on the PBX is greater than the one on the Recorder"

The recommended action in Sentinel is to either:
1. Change VRSP’s SipStackSessionTimerSessionExpires to the Min SE which is configured in CUCM.

-or-
2. Reduce the CUCM’s Min SE to 90.

But, we are not aware of the above mentioned parameters either on the NICE side or on the CUCM.
Also there were no changes that coul have triggered this alarm and that too, this frequently i.e. almost twice a week.

Any insights on what this alarm is about and how does this impact call recording, if at all, will be really apppreciated.

Thanks

 

[nice12345]

hi its the sesssion expire parameter. have a look here for its location in CUCM

https://supportforums.cisco.com/thread/2137437

in NICE you will find it under CTI integration in system administration

 

[nice12345]

Solution: While the suggestion above is to change the NICE side to match the Cisco side value of 1800, this is out of the range defined in NICE, which includes values from 10 - 1000.

The options to address this are:

1. Change the MinSE parameter on the Cisco side (current value: 1800) to match the NICE side (current value: 90)
2. Change both sides to fall within NICE's range for the value of this parameter (10 - 1000)

Here's where to make this change on the NICE side:

In System Administrator (make sure you're in Technician Mode first), the field is called "SessionTimerMinSE" under CTI Integrations > Media Provider Controller > (Click your MPC link) > Additional Media Provider Controller Parameters > Look for "SessionTimerMinSE" > Edit and set to the desired value. Save and you will need to stop and start the Nice Integrations Dispatch service and the Nice Interactions Center service on the IC server for this to take effect.


Additionally, this change must be made on the NICE Logger. This is under Start > Programs > NICE Systems > VoIP Logger Tools > IPTool.

In the IPTool, you'll see the "SIP Configuration" option. Under "Advanced SIP Setup," this is the section for updating the MinSE field. Please refer to PDF details on this in the VoIP Logger Guide, also in the attached "VoIP Logger - SIP Session Parameters.pdf"







(Ignore the circled "SIP Port" selection above. Please refer to the "Advanced SIP Setup" in the lower half of the screenshot.)

This will then require a restart of the NICE services on the NICE VoIP logger.

NOTE: The restart of the IC and Logger services will cause an interruption to recording while the system re-monitors all devices and reads the mapping again. This may need to be performed after hours or at a point of lowest call volume.

Root Cause:

Discrepancy between the "SessionTimerMinSE" parameter in Cisco being configured to 1800 by default yet the corresponding "MinSE" parameter in NICE being set to 90 by default.


OriginalID: 2906

 

[blesio]

What real impact does not changing this have on the VoIP Recording solution? Except the obvious error in Sentinel?

Thanks

blesio