Search results for query: *

I finally got it working. I enabled "rerun STUN at startup" my IP Office starts registering at my ITSP at startup, so now I can receive calls. My ITSP doens't support STUN so I used the default STUN IP address.

When I run STUN options do change. My firewall is detected as "Port restricted Cone NAT", public port as 17558 and my IP is shown in the public IP field. My ITSP does not support STUN so I used the default STUN server to test. I find it a bit strange I can't find anything in the sysmonitor of...

I am using a Draytek 2900 firewall. As far as I can see it doesn't have any SIP settings. I forwarded the RTP range as you suggested and tried both firewall settings but with no succes. When I boot the IPO while sysmonitor is running with only the SIP options selected I see nothing happening...

The IPO is behind a firewall. Port 5060 is redirected to the IPO.

I have a Small Office with a valid SIP license and a SIP account. I can dial-out using SIP without a problem but cannot receive calls. It seems like IPO does not register itself at my SIP provider. I cannot find any attempts of the IPO trying to register in sysmonitor. My SIP provider does not...

I never used Phone Manager to pop an external application, so I'm not 100% sure this is gonna work. The calling party is passed as the first parameter of your batchfile. So with %1 you should be able to pass the calling party to the URL. Add ?phone=%1 if no other URL parameters are used...

According to the 3.2 upgrade instructions you can only upgrade from 3.1.65, this way the config is upgraded correctly. Although you can upgrade to 3.2 from other versions I would only use this for a new install. I upgraded a 403DT some time ago to 3.0 and was still be able to use DT extensions...

It sounds like you are trying to transfer a call to an outside line blindly. As far as I know that is not possible with the IPO. Try if you can transfer the call announced. Hit during a call the transfer button, dial 9+number wait till the other side answeres and then hangup.

As far as I know you need a free port for every call that goes through Voicemail Pro even it is just a transfer action without audio. Voicemail Pro will also reject a call from a queue when all ports are busy. The call will be placed back in the queue but won't hear the 'still queued' message...

I've never tested it before, but if it's not possible to set a time profile to a user restriction, try the following: Create a Least Cost Route which blocks calling 09x numbers and set a time profile on this route. This way you should be able to block the 09x numbers during the night, but this...

There are two ways to connect a 3rd party IP device with the IP Office: as extention or as trunk. To connect an IP Endpoint as extention to your IP Office you need an IP Endpoint-license or a Phone Manager Pro and Phone Manager Pro IP Audio Enabled license. In this situation the IP Endpoint...

As far as I know you can select under which user the Voicemail Pro service should run. I cannot think of a reason why this should be user 'Avaya'. The purpose of a RAID is that the system won't go down is a disk fails. So why Voicemail Pro should not start if one disk crashes is a mistery to me.

Voicemail Lite uses the MAPI.DLL of you email client to send the message. Exchange also has a MAPI.DLL which is different and causes Voicemail Lite to crash. You cannot replace the MAPI.DLL of Exchange with one of your client since this can (or will) cause problems with Exchange. As IPkokken...

If you hear the engaged tone you are not be able to transfer a call. You can only transfer a call to an engaged extention if 'call waiting' is enabled. In that case you hear a ringing tone if you call an engaged extention. The engaged user will be allerted that a second call is waiting.

The problem is not Windows Server 2003 but Exchange. Exchange has it's own MAPI32.DLL. Voicemail Lite uses MAPI to send messages through Outlook Express. Since the MAPI32.DLL is different from the Outlook Express Voicemail Lite crashes. If you try to install Outlook (the one that comes with...

Although not supported by Avaya, TAPI works under Terminal Server (or Citrix). You need a CTI Pro licence or else only one user is be able to call using Outlook (or whatever program you want to use). I have at least 2 customers working that way. Just recently I found out Avaya is not supporting it.

In the helpfile search for conference. You should see a result called "Voicemail Pro Samples". Open this page. Under "Modules" you should see a link to a PDF about conferencing. Good luck.

In the helpfile of Voicemail Pro is an example how to do this. Mainly it is nothing more than a transfer to the "Conference Meet Me" functioncode.

I just upgraded an IPO to 3.1.65 and now the called huntgroup is not displayed at the extentions (all analog) if the caller has no CLI. If someone call with CLI both the number of the caller and the called huntgroup is visible. This company services for other companies so they have to see the...

I never tried it but a friend of mine told me how he solved this problem with an IP Office. For this to work you must have one single outgoing line. Create a huntgroup with one member and queing enabled. The member should have forwarding enabled using the single outgoing line. The first call...