Search results for query: *

I have a door entry system set up with an IP Office 412. When the users press the button for the door entry this goes into system via the Analogue line ports. I have a line id of 10 which in incoming call route points to a group Door. When the door button is pressed the user is waiting 9-10...

Just wanted to say, that I unplugged the module and reboot the unit last night and the error os no longer about. I should have known better than to think a soft reboot would work! So thanks for everyone's help. Chris

Is there any way to check the programming? If this is a handset problem then I'm in trouble, as I could be aout to lose half of my handsets. I get about 2-3 a day that lock up and require reseting. Hmmm

Upgrade to 2.1?? It seems to me that upgrading tends to be a lottery. Or is it now considered stable?

hmmm interesting, does talking the right way involve making threats? Thanks for the PDF I'll read it on the way home tonight. hehehe I know what you mean re: Index phones, I'm still using a DT3 handset - our last working one! I get all nostalgic about it. All the rest are 2030's which are good...

Tell you what, I'll unplug the module and send a reboot when free request to the 412 and see if the message disappears.... I can't power off the unit for a few days - Damn lawyers working mad hours! GoHome! Chris

Sorry I should have made it clear that I was aware it wouldn't detect the module till it was power reset. But wondered if that was what was causing the problem.

IP Office 412 (2.0 1602) 2 xDT30 4xDT16 & 2x POTS16 (4.0 16) I have noticed recently that I am getting more and more handsets locking up. They are eiher not responding at all or I get intermittant static. Is this a firmware upgrade thing or more terminal? How is 2.1?? Also we are about to...

Hi all, IP Office 412 (2.0 1602) system with DT30/16 modules (4.0 16) I have just added a new DT30, but haven't been able to power off the unit yet so the 412 hasn't detected it yet either. I keep on getting this message in SysMonitor: 3000848mS ERR: CM::Message Line not found 3001830mS ERR...

Well it appears we have cracked it! Because we upgraded from AgentBranch with basic Voicemail to IPOffice with VMPro there appears to be an issue with the original greetings! After re-recording all the user greetings we've had no further issues. FYI: We are on ISDN30 PRI. Thanks for those...

Hmmmm.... Interesting! I was doing some testing here and was watching the VMPro console whilst leaving a message at 7.30am this morning and 2 things struck me: 1) The tone that is played after the user greeting was a bit of a squawk! 2) The call is hung up immediately after playing the user...

Thanks for that, I now have VMPro running as a program. There were no MAPI errors in the very confusing file that it dbgout.txt!!! VPIM & IMS were not installed either. My main problem is that my chairman sends his PA a voicemail every morning with a list of stuff to remind him when he gets...

Thanks for that, but I'd read that earlier and checked but there are no spaces in the usernames at all - eg. AliceW, AlisonB, etc. I'm running VMPro as a service, is there anyway of running it from the desktop as a program like the 'old' Voicemail' did??? I've checked all the power settings...

I have VMPro (2.0.16) on Win2K Server (I had it originally on an XP Pro box but was advised to change to 2K) and all works fine except that I have started getting blank Voicemail messages (1Kb in size), initially I thought the caller hung up when they got the Vmail message, but that is not the...