Lets start with the obvious...
Have you checked the OS (Device Manager) to see if your modem is listed and reported as attached to COMM1?
Is there more than 1 modem listed in Device Manager?
Can you send a query to the modem from the OS?
There should only be 1 modem listed in Device Manager...
PCAnywhere is not require, its optional, if you want to use PCAnywhere you can, or for those that wants to use RDC, they can too. PCAnywhere is for those that complaints about leaving certain ports open on the RDC side.
that patch is for people that are using PCAnywhere.
One other thing to verify, you've most likey done this several times already, but just verify that on the CP server, its the CCMS CLAN address that is entered.
I've made this mistake several times, because the CCMS requires the CP ELAN IP, but the CP requires the CCMS CLAN IP - all falls back...
If the CP is the 201i, then sure you can reseat the card, doesn't matter what release of software its on.
Just curious, when you rebooted the 2 servers, did you wait for CCMS to come "FULLY" up first before bringing up CP? I asked because like I said earlier, the CP requires the MLSM service...
Have you tried resetting the MLSM service on the CCMS? That is what CP use to communicate with the CCMS.
Also check and make sure the MAS Link Handler Port #2 is enable on the CCMS. Windows 2003 server has a problem with that service starting up every-now and then.
in the call presentation class, there should be a check box to place personal call on hold and answer acd call
the agent would have to know there's a acd call waiting and place his/her personal call on hold to be presented with an acd call.
if you have ld137 in mid, then every 5 days the system will run a data cmdu. this perform a read test on the cmdu. the read test does a read on the hd, fk, and cdrom. if you don't have a cd in the drive, you'll get the error because there's nothing to read.
use mdp refresh instead of install if you have any special patches. mdp install delete all current patches, refresh will remove and update any obsolete or defective patches.
you have to create a new acd q for the ivr ports
you hadd that acd q number in the sdn table in the callpilot as symposium services
you pick how many port you want to lose from the callpilot and delete those and rebuild them in the new acd q except this time you'll have to add AST to the set...
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.