I have a Neax 2000 IVS 1800 series software level. On occasion My UCD group for VM (Rapartee) will hang up. Dial 2500 (Pilot) and it will not go to any of the extentions programmed for it. 2501,2502,...etc. Dial direct (ext) and they come back as fast busy. Only fix I have is to reboot system. I have looked at programming and everything looks good. I have checked (and repaired) grounding. Does anyone have any ideas on what may be causing this?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
UCD Problem
- Thread starter 2400tec
- Start date
- Thread starter
- #3
I did that....Sometimes it works..other times no...
also in addition to problem....At times only a few ports on VM will work. I have 8 ports (2 cards) ports 2,7 will work. others have fast busy..When you dial Pilot (2500)it will transfer to only working (2,7) ports. reboot system and all is well again..
also in addition to problem....At times only a few ports on VM will work. I have 8 ports (2 cards) ports 2,7 will work. others have fast busy..When you dial Pilot (2500)it will transfer to only working (2,7) ports. reboot system and all is well again..
MrComputerTelephony
Vendor
Make your pilot ext 2500 a virtual,but not the pilot.Assign VM ports 2501-2508 for the 8 ports,making 2501 the pilot.Call forward all calls 2500 to new pilot of 2501.This may help...
If the problem goes away with a system reboot, is this a reboot of the PBX or the VM.
If a reboot of the VM, i would seriously suspect a fault on the Dialogic card of the VM system.
If possible, attach analog phones to all of the VM ports directly, and ring the VM pilot as normal, and answer calls, leaving phones offhook to see if the UCD group works fine.
This will at least isolate the issue to either the PBX or VM.
If a VM issue, check the wiring from the PBX to the Dialogic, if you have some split pairs, this can cause all sorts of things to go wrong.
Good luck.
If a reboot of the VM, i would seriously suspect a fault on the Dialogic card of the VM system.
If possible, attach analog phones to all of the VM ports directly, and ring the VM pilot as normal, and answer calls, leaving phones offhook to see if the UCD group works fine.
This will at least isolate the issue to either the PBX or VM.
If a VM issue, check the wiring from the PBX to the Dialogic, if you have some split pairs, this can cause all sorts of things to go wrong.
Good luck.
- Thread starter
- #6
To pabxdude: I know not the VM. I tested the ports with a seperate line (dialed into port).
To MrComputerTelephony: Are you saying to change the UCD pilot to 2501. Add my 8 lines to it. Create a Virtual for 2500 and CFA to 2501 (Pilot). Not sure what this will do. Can you explain?
To MrComputerTelephony: Are you saying to change the UCD pilot to 2501. Add my 8 lines to it. Create a Virtual for 2500 and CFA to 2501 (Pilot). Not sure what this will do. Can you explain?
OzzieGeorge
Programmer
Have you checked to see if there are any call forwards set on any of the extensions? The real test is take the voicemail out of the equation and see if this happens with just analogue phones connected. Also make all test calls from a dterm and watch where the call is going. Better still next time it happens substitute analogues for the voicemail and try the above.
I have retyped the integration option line over again with a space in fromt of it and hit enter 3 times to restart the MCI.Also make sure when you dial each port it matches what you have in page 1 of applications. For example, if 2501-2508 is entered in and 2500 pilot is there, be sure they match the right ports and get answered. MCI needs them in order.
I know this sounds basic, but have you rolled the cards to make sure the cards in the PBX are not bad? Also I would start to suspect the dialogics boards. The next thing I would do is blow out all of the programming for it and start over. Try using different extension numbers for the vmail ports and keep the same pilot. Put them into a different UCD group. Make sure to take all of the extensionsout of UCD CMD 170,171,172 first before you blow away the rest of it. Just a suggestion.
OzzieGeorge
Programmer
There is no better way to restart the MCI than a make busy switch followed by an unplug, reinsert & un busy. Don't trust any software restart.
Sounds like the UCD group is corrupt, Try to change the UCD group number in CM 17 Y data 2. May need to rebuild the group entirely make sure that the pilot is not called during rebuild for this will corrupt the pilot. If this happens need to build and new pilot.
ipfreelyallthetime
Vendor
It sounds like Mextera is on the right track, I have had problems with UCD groups before, due to some coruption. I would blow the UCD group away and rebuild it in a new group number. I would also verify the CMD9000 button programming. Don't think this is your issue, but I have messed it up from time to time.
Thanks,
Chris A
Thanks,
Chris A
OzzieGeorge
Programmer
I've seen a couple of posts that relate to UCD corruption and that it is a known problem. Can anyone tell us which software revisions have this problem?
- Status
Similar threads