Is it still failing? When you deployed the logger did you correctly choose the correct config file in NDM? Are there any errors in the logger log file?
Some days I do my job, other days it feels like I'm doing everyone elses job, other days I should have stayed at home and mowed the lawns.
It's been a few days with no response, I'm hoping you are still not stuck on this issue, in case here are a few ideas:
I doubt this is a firewall issue considering the logger is on the same server. It sounds like the logger is not starting to a point that you can add it to Sys Admin.
Have...
As Vedovotao stated set up smtp in IIS 6.0 Manager
Then test you can send email from the applications server command prompt using telnet commands: http://support.microsoft.com/kb/153119
Once you have verified email works using telnet then start testing nice, you need to have:
- a 'from' email...
Required on all client workstations if .Net 4.5.1 has been installed the following registry configuration is required to allow Full Site Trust Permissions as set by the Set Security Tool:
Registry Location:
32-bit environment: HKLM\SOFTWARE\MICROSOFT\.NETFramework
64-bit environment...
what is the name of the user in the calls you have retrieved? is it
- basic recordings user, indicates your CTI Integration is failing and calls are being recorded through total recording
- unmapped user, indicates CTI integration is avaialble but your agents are not being identified...
Have you set IE to compatability mode?
Some days I do my job, other days it feels like I'm doing everyone elses job, other days I should have stayed at home and mowed the lawns.
Is this a new site that you haven't previously had working or is this an old site that you've added 4.5.1 to?
Some days I do my job, other days it feels like I'm doing everyone elses job, other days I should have stayed at home and mowed the lawns.
Have you put the key in the right registry area? It is different for 32 and 64 bit environments
• 32-bit: HKLM\SOFTWARE\MICROSOFT\.NETFramework
• 64-bit: HKLM\SOFTWARE\Wow6432Node\Microsoft\.NETFramework
Some days I do my job, other days it feels like I'm doing everyone elses...
it sounds like you are missing the event answered or network reached message (sorry can't remember the exact message but it is something along these lines) in NICE. Check you have installed the correct Cisco client in NICE and configured NICE to the correct version of Cisco. Also what...
What version Nice?
Is this occurring on the server or the client?
Have you defined your servers by IP or Machine Name?
Have you re-run Set Security after the address change?
Have you run NICE Rename Host Tool?
If it is an issue on the server start with the...
Sorry just as further info from memory I think the internal call gets tagged by default with the agent receiving the call. I assume you will likely find the other recorded segment under Basic Recordings User assuming you have TRS running with total recording although I've never bothered to...
The answer from NICE is as per the default configuration, specific setting is RecordOnlyBestParticipant in the RCM. I believe this setting can be turned off but this is not supported with all environments such as Active By Call Recording.
I would recommend discussing this setting further...
If it is set to automatic and it starts with no issue when you start it manually it's likely it is trying to start when a dependancy service is not yet available. Check the logs for the service to see if it is trying to start when the server is restarted. Check with NICE if there is an update...
Is this a new system?
Has anything been moved recently? If so what has changed.
Some days I do my job, other days it feels like I'm doing everyone elses job, other days I should have stayed at home and mowed the lawns.
Are you trying to re-archive the calls in the 3.1 or 4.1 solution?
If in 4.1 you need to create a historical storage rule.
If 3.1 there is a flag somewhere in registry if I remember right that tells the system to only go back as far as 7 days. This can be changed but can only go back to a...
Sounds like you are going to need to test each component individually by swapping out with replacement components. I'd start with the coupler itself, if that fails try the cable from the coupler to the logger. I am assuming when you changed ports in the coupler you used the same cables for the...
In order for users to be able to access the Perform web page the following GPO setting must be set to disabled:
•Deny all add-ons unless specifically allowed in the Add-on List
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.