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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Voicemail Pro Not Operational (and you are running MS DNS) 6

Status
Not open for further replies.

waldrondigital

IS-IT--Management
Mar 4, 2009
94
Got a call from one of my offices today. After running VM Pro on their Windows domain controller fine for 6 months, VM Pro decided to stop communicating with the IPO. It looked like everything was fine, but obviously there was no communication between the IPO and VMPRO. This is because MS DNS decided to eat the ports needed by the VM PRO to communicate with the IPO (UDP 50791-50801)...

If you experience Voicemail Pro Not Operational, but it seems fine... and you get this:

In Monitor:

3233269mS CMTARGET: 5.20.1 27 Q931 Trunk:5 CHAN=1: TimerExpired cause=CMTCNoAnswerTimeout
3233269mS CMTARGET: 5.20.1 27 Q931 Trunk:5 CHAN=1: Retarget NOANSWER EXCEPTED=00000001 ValidTargets=1
3233269mS CMTARGET: 5.20.1 27 Q931 Trunk:5 CHAN=1: Retarget on target_cfg_user=SMConference
3233269mS CMTARGET: 5.20.1 27 Q931 Trunk:5 CHAN=1: ADD USER: SMConference depth=1 disallow_cw=0 dnd=0 real_call=1 group_call=0 type(CMNTypeUnknown) incl(0x1) excpt(0x1), allow_redir(1) remote=00000000
3233270mS CMTARGET: 5.20.1 27 Q931 Trunk:5 CHAN=1: SELECT: TRY VOICEMAIL orig_hg() orig_user(8509)
3233270mS CMTARGET: 5.20.1 27 Q931 Trunk:5 CHAN=1: ADD VM TARGET
3233270mS CMTARGET: Voicemail Pro not operational
3233270mS CMTARGET: 5.20.1 27 Q931 Trunk:5 CHAN=1: ADD VM TARGET: FAILED availability=0
3233271mS CMTARGET: 5.20.1 27 Q931 Trunk:5 CHAN=1: VM targeting failed. Remaining on final target SMConference
3233271mS CMTARGET: 5.20.1 27 Q931 Trunk:5 CHAN=1: GetNoAnswerTimer:22

Microsoft DNS will fight for ephemeral IP ports with DNS. One way to test this is to shutdown the MS DNS server, restart VM Pro and then restart MS DNS. If THEN your server is 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.

Seen this issue before with other stuff, but never VM PRO.
 
or perhaps follow the documentation and don't install avaya applications on a domain controller....

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
 
Indeed, a domain controller used as a vmpro machine always turns out on a disaster and you always loose it from the admin guy.

Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
I will add that even if this WAS NOT a domain controller and you happened to wanted to run a DNS server on the same box you might still have this issue!

Sometimes dedicating a box SOLELY for VM pro is not an option for very small businesses. Frankly VM Pro requires so little overhead I don't really see the big issue with loading on a system with "other" services... providing they don't step on each other.
 
Considering that a server box can cost as little as 200 bucks while a vmpro license can be ten times that amount then I see no reason to claim to be a small poor business that cannot afford a dedicated box.

I always keep critical domain stuff (all of it) away from the box that runs voicemail pro. I won't have to worry about many items if vmpro occupies its own space.



Use system monitor unless of course you are a Tard then it IS the fault of the pbx.
 
A new, reliable "server box" is $200!? That is funny.

Go quote up a system with basic two disc RAID and an OS and I bet it is more than $200.

So I'd be better off running my production VM pro on a $200 box with Windows 7 home, no redundancy, versus on a computer with Microsoft DNS that has RAID 5, redundant power supplies, etc? For the simple fact it is "dedicated"

Sounds nutty to me.


 
Yes you are a nut.

Use system monitor unless of course you are a Tard then it IS the fault of the pbx.
 
Besides yours broke in six months. Not exactly reliable. And how do you reconcile claiming that the poor small company is broke yet you build them one super computer, probably expensive, that has one point of failure. Something breaks and nothing works. Congrats. Great plan. Perhaps they can go another six months before it breaks again.

And yes a 200 dollar computer with xp will run vmpro just fine. Ebay sells em everyday. A computer for the true budget minded.

But hey. Its your customer. Different strokes, different folks. I wouldn't recommend or support vmpro on a domain controller.

Use system monitor unless of course you are a Tard then it IS the fault of the pbx.
 
I have seen strange issues with domain controllers which can not be found.
Moved the vmpro to it's own box and issues where gone.
Also getting admin rights on such machine is a pain because the system admins rather not give that.
If you need to reboot for whatever reason is always a problem.

Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
while I agree with all the comments, sometimes the customer will insist that we use the resources that are available to us.

we do both IT and Telephony (so my role is wide ranging) and most of our customers get dedicated machines, where some, in enviroments where there simply isnt the physical space or budget to splash out £800-1200 quid for a new VMPro / CCR / CS box there has been the odd time where VM Pro has ended up on the companies SBS box!
 
That is why i love the Linux idea.
Setup a virtual machine so there are no extra costs (maybe some extra memory) in most of the times.


HSM, if you see some servers packed with all kind of apps then i get chicken pocks of the idea to run a vmpro on that.
Not that it will not work but all the hassle when something else stops working even when you can't help it.


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
HSM got his name back? Did you get your stars back too?

Use system monitor unless of course you are a Tard then it IS the fault of the pbx.
 
Wow the impossible is possible. Not that you are irrevocably misbehaved and unhelpful but that you can get booted and reinstated with stars. So how did you do it? I need to add the technique to my strategery. ;)

Use system monitor unless of course you are a Tard then it IS the fault of the pbx.
 
well, I'm not sure. I really just assured Dave (Murphy) that my intentions are always for the best, and to be perfectly honest, I don't have any specifics about why I was banned, except there were some "complaints" about my posts from member's.

Ive been informed in the future that instead of mocking the less knowledgeable and the "leeches" I should just flag the post, which works very well.

 
Well its good to have the Original Gangsta Monkey back and in operation.

Use system monitor unless of course you are a Tard then it IS the fault of the pbx.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top