Recent content by vappl

Try disabling the skillset, remove the agents from the skillset and return the skillsets afterward and reenable the skillset.Then one agent login first and verify.

I just did an upgrade today and I did not even ran a precheck but I encountered that cdr error. All I did is reduce the cdr file size from default 400MB to say 40MB, comit and clip and upgrade went through fine.

I see you load the iis6, but did you program the IIS to see the path to the RCC folder and also have you programmed the application pool? Please see starting page 44 of RCC setup and operation guide.

I would replace the system for quick recovery,move the cards, regenerate keycode and restore the backup. I'm thinking you had a bad MSC or Power Supply. You could isolate it in your lab.

Try Patching BCM 400 version 3.7 with BCM370.237UM3 to support Java 1.6. Add the latest patch for RCC BCM370.252RCC, also add BCM370.227VM.Reinstall RCC after Patch.

Patch BCM400 with SU.Desktop.014 with RCC upgrade to 2.4.360 and reinstall RCC.Since you're patching, you can include the latest SU.system patch.022

From what I read UCM is the same as the ECM (Enterprise Common Manager)which would provides centralized authentication and also I expect it to provide Phone Field Folder which could allow administrators to program telephones just like the Telephony Manager.

Have you tried BCM Monitor on BCM50 to see if any digits passing through coming to/from site#4? Please read BSR222 or BCM50e Configuration Guide NN48500-508 which will give you sample designs for BSR222.

Use an older model M2616 , not the aries II . you need to add a daughter board for M2616 for a relay to short whenever the phone rings. This uses the second pair of the rj11 input. The 2nd pair on the jack goes to the Algo duet plus normally open relay. The flasher is connected to the Algo device.

It is a good practice also to renumber inactive DN that is close to your destination codes to avoid wildcard entries.Some extension on your inactive DN might be needed to flow accross.

I have a problem similar to this in my networking and I figured out that the conflict is the public received number from the target lines. The public received number cannot conflict with destination codes.If you need to keep the public received number which is also in the 28xx range,say for...

Your choice, reboot the BCM, Load latest patches for BCM 3.6,still if not fixed upgrade your BCM to 4.0, load patches for 4.0.

I agree with the upgrade to 4.0 .Then load the newest patches. Easier to deal with problems on the new OS , if the problem is still there.

If they are the same type of phone, just switch the phones.

if using default numbering, it is 333.