Search results for query: *

Does anyone know if there is a direct upgrade/replacement path from 403 to 500? Since IP Office 403 is EOL we need to replace it and dont want to purchase licenses all over again.

We are moving; we have to vacate our current space but the new space will not be ready for two weeks. I have to forward all incoming calls to an external number. Does this have to be done buy the phone company or can I do it at the PBX. We have an IP Office 403 PRI 15 Channels and DID.

My company is moving and according to our CLEC we are moving to a new Rate Center and they cant display our main number,301-530-9106. If they display it, 911 will show up at the old location. The only way they can display our number is if our PBX takes control of what numbers are to be sent...

March came and went twice. The upgrade to 2.0 did correct the issue I was having. But now I have another issue that need I need to post. We migrated the e-mail server to a new box; keeping the same version, now the alerts are no longer working. IMS client is a dog so we decided to not use it. I...

Thanks for the info -- we will be upgrading to the newer version first part of March. I will let you know how it goes.

This seems to have stumped everyone. An IP Office Technician took a look and said to wait for version 2.0 which is due out this month. He said he was surprised we ever had the Alert/Forwarding working at all. We may be forced to use IMS.

I stopped and restarted the VMpro service as well as the MS Messenger service and was able to get a MAPI logon failure message. It only appears when I restart the service and leave a message afterwards [2328] 394:0 mailboxes were open (but not active) when flushed [2328] 394:CreateMailboxList...

Which Microsoft service are required to run?

[1804] 122 mailboxes were open (but not active) when flushed [1804] DevIO::RxAbort 192.168.21.17 [1804] DevIO::Detach 192.168.21.17 [1804] Voicemail Pro Server Version 1.2 (12) [1804] Using modified Goertzel algorithm for DTMF detection [1804] Loading VMP configuration... [1804] Using mask of...

Manager 3.3(26) Control Unit ip 403 1.3(34) Voicemail Pro 1.2.12 Are there any known issues with Microsoft service patches that could affect this? I am aware the SP4 locked down impersonations but the VM user has admin access.

Sorry -- the rest got cut off There is nothing in the debug referencing MAPI. ALL users have the e-mail alert enabled. 00000051 732.96783627 [1384] 174:New VMAIL Client 00000052 732.96800917 [1384] 174:Receive OPEN for session 188, call-id 143 (DISC Tone Length 0 secs) 00000053...

Yes Exchange and the IPO are on the same subnet Are there any known issues with MS SPs? This is all it has logged so far -- 00000000 0.00000000 [1384] 174:New VMAIL Client 00000001 0.00008457 [1384] 174:Receive OPEN for session 187, call-id 138 (DISC Tone Length 0 secs) 00000002...

Yes yes I can open Outlook on the server and send an e-mail from the VM account just fine. Can anything like LDAP seetings, routes, where cables are plugged affect it? When a notification is sent is it initiated by the switch or the VM server?

2000SR1 -- Office SP3

how could i forget -- the exchange server requires a certificate. does this need to be configured in VM some how?

Yes the MAPI client is the same user. Outlook is the client and 1.3 firmaware and 3.3.26 is the Manager version

Sorry for waiting so long to respond but this issue stil exists. I can log on locally with the Voicemail user account and send a MAPI mail message to my account fine. The VM service is actually using a domain user to log on, should it be set to a local system account with interact with desktop...

Check you DNS MX records

We have an IP Office 403. E-mail alerts worked when the switch and server had a public address but now both have private addresses and are behind a firewall on the same subnet. Also, the is an e-mail server in the DMZ that relays to the private network. Another change that was made is the key...

Hi, I have the Alert Manager configured in Arcserve 6.5 to print trouble tickets to a printer at the HQ site (which is also where the PDC and print server is located). Users at the remote site can send jobs to the HQ printer w/o any problems. When I try to get the Alert Manager to print trouble...