Helpful Member!(3) amriddle01 (Programmer)
16 May 12 6:15
May be DNS (not DHCP) in fact, one way to test this is to shutdown the MS DNS server, restart VM Pro and then restart MS DNS. If your server IS then working you need to reserve the IP office ports so Microsoft DNS can't grab them:
Start Registry Editor (Regedit.exe).
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
On the Edit menu, point to New, and then click Multi-string Value. There may be an entry already there, just modify it.
Right-click the new value, click Rename, type ReservedPorts, and then press ENTER.
Double-click the ReservedPorts value, type the range of ports that you want to reserve, and then click OK.
Add 50790-50801
Click OK.
Quit Registry Editor.
Restart your voicemail pro system (full reboot)... now your MS DNS will not try to grab ports that VM PRO needs to operate.
But in reality... Avaya tell you not to use the server you are for this very reason smile
thread940-1683281
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.