- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
The agent must first be actively logged-in to the queue before they can perform this function. NOTE WELL - - that if at any time the agent just walks away without first placing their phone in makebusy, that the system will not know they're away and may queue-up a call to that phone. IF THAT HAPPENS then the presented call will ring a few times then re-queue itself back into the hold queue, no harm, no foul, BUT THE AGENT PHONE will be automatically logged out so that this does not happen again. This is an "goof-proof" function of most better call center systems. So now when the agent comes back from break and sits there like a bump on a log because no calls are coming to his/her phone because the system logged him/her out. THIS IS A TRAINING ISSUE and an administrative issue, not a support issue. Hope this helps!!!
hi, your phone have a software problem and its cause is "security test failed"thats why it has a contact service status...by fixing that you need this gadget ... 1.mx key activated dongle with ufs interface 2.3110c fbus cable (same as 3500c and 6300 3.)modified pm 1 and 309 of 3110c procedure... a)open mx key b.)connect the phone to mx key using fbus cable c.)in mx key select bb5 d.)bus check and you you will see this logs SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed! in this logs you will noticed that security _test is the only failed...
e,)we will continue by selecting PM then thick PMM authentication f.)then your pm now is authenticated ,write the modified PM (by writing modified pm ,thick load from file ,then write) g.)after writing PM here now is your phones logs... CONFIG_DATA: FFFFFFFFFFFFFFFF
PROFILE_BITS: FFFFFFFFFFFFFFFF
BLOCK 1: 1=CORRUPTED
h.)now you need to unlocked the phone by clicking ,SERVICE ,IMEI and SECURITY then INIT SIMLOCK...and you phone is done
always remember ,when doing software action to your nokia phone ,always back up the rpl to prevent more damage..thanks for trusting fixya..
I have seen things similar to what you describe. Most likely it is due to a PC setting that retains jobs in the queue. Conceivably, if you have a hard drive in the printer, it is a setting that may be corrected by logging in to the printer's IP address. I have not ever seen it caused by the printer, alone.
×