Search results for query: *

what's showing on the HEX display now or after you power it up and let it shit for a few minutes?

You sure the calls are being dropped and not the caller hanging up?

Is this the only phone acting up? Swapped it out or with someone to see if its the phone or software...isolate the problem then trouble-shoot

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.

look in the engineering and planning guide to determine what the buffer should be set at.

change cls sfd to sfa - might have to change it on both set

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...

i'm using a motorola h500 and it works better on the 1140e than it does on my cell

the side 0/1 i was refering to is acutally the sti link, wherer you define the tn key0/1 of the virtual agents. its actually STI01-001-001 for the first agent all the way thru -032 and the same for STI02-xxx-xxx basically build out all your agents on the board before going over to the second...

also make sure when you built out your agents in the cp server that you didn't skipped the 1st port and built out 1 side first before going on to the next. we had this problem when 1 of our techs decided to build out 12 channels on side 0 and 12 channels on side 1. everything was working except...

change the ext number in software to non did and leave the phone label with the original ext.

You stated that all of this started to happen after the main greeting was changed. Is it possible that the wrong greeting was changed or multiple greeting was changed? Have you dial up PM and verified the greetings in all of the menues or looked at them all?

Are you using PoE for the set or a power brick? We had a similar problem with several of our phones and used the power brick instead of PoE and that cured the problem. Apperantly, those PoE ports on our switches weren't providing enough power to power both the phone and exp module.