Search results for query: *

I have 2 Loggers and 2 DMCC links for each logger . Each logger has own CTI services for observation VEs. But it seems that it could be fine 1 DMCC links that includes enough VE for both Loggers.

NP 3.1 and higher version does not require any restart,just update the CLS by using update wizard. NP3.0 and 8.9 ,you have to restart CLS services after every changes on mapping etc.

you need provide more information for this issue.. it is 8.9 or NP version? whats your integration module? Whats your logger type? VOIP,TDM? if Voip active or passive sniffing..?

what solution get from T4 about MML failed problem? Tx

thanks for info

if it is NP3 , you have to restart Interaction Center, whenever you are update&changing any channel. if it is NP3.1 or 3.2 , you just need to update channel mapping and monitor station and apply for integration. most of CM integrations, driver is updating newer stations IP addresses...

whats the integration and Perform version.? is this Digital logger or VoIP?

Problem has been solved by open all TCP ports beetwen client and Application server. we can not locate any specif ports.whenever trying to open new channel monitor on client machice.it use different TCP ports.

if you are using Nicelog Voice locking tool? you need to connect to Logger not the CLS and choice unlock segment dates.

Ports are opened Clients can use BA,monitor,Reporter..etc but channel monitoring.

Anyone has problem with channel monitoring is not fuctional on client pcs sometimes? There is no error when I log in web application and see channel monitoring on the APP server but I cant see channel monitoring client pcs. I get Connection error that says logger connection failed. Desktop...

if there is no screen recording on site and you still have mml failed errors. you may check the QA rules .?f there is any agent grp rules including screen and voice.? uncheck the screen.. check the call details on recording tab. is there any initiator type QM? or only total.

if you dont archive Screen calls, you probably not able to listen old calls that are not on the screen loggers. when you receive player error or any error on BA. check client pc player logs and locate logs on Application server. what it says. or basically restart the locate service on...

when you make a test call,first check the RCM log files and see if there is correct ip adress and extention.then check the logger`s mascmap.evt file.Make sure that RCM update new ip address on logger as well. I assumed that you have already run the sniffer and elimate sniffing problem...

I have seen this error thats not N?ce issue .you should consult with I.T guys that can fixed the problem.

Perform side,Connection is made nice not sa so you can change sa password on SQL Security >Logins rigth click on sa properties....

whats PBX type.What integration are you using. ?t seems that logger is recording properly but you cant receive agent's attach data like phone numbers? if it is AVAYA , you are probably missing ACD numbers..make sure that you are monitoring all devices and ACD ..etc.

if it is 8.9 it is written under nice_cls database table server info

you mean you are using Sc investigate and see logger calls under archive (0) or sending archiveclass5 or 7? Firstly check SC admin and make sure that logger is the member of the CLS secondly check the Task ,if you are using one task for both loggers. make sure that you add them by...

Problem has been solved by changing parametre on Avaya site Admin.