VM PRO with SOE and serial dongle

[jroosen]

Hello all,
I have a serious problem with using vm pro on an ipo small office edition and serial dongle.

ipOffice (2.1.24) has serial dongle direct attached and licenses for phone manager pro, iphone pro and voicemail pro. All licenses are valid.
Problem: VoiceMail Pro (2.1.18) installed on w2kProSP4 does not work. Dialing *17 shows busy. When I dial a voicemail enabled extension monitor shows a red msg "No free VM Port". This does not depend on weather FeatureKey Server is running or not.

Tracking down all this I am unsure how to deal with feature key server. Documentation of voicemail only deals on usb and parallel dongle and running feature key server is mandatory.
But, how to do this with a serial dongle connected to ip office?
And second, if I dont have feature key server running, why doesn't the vm pro server terminate? In fact, the service stays running all the time without feature key server.

What is wrong here? Any suggestions are highly welcome.

Kind regards jr

 

[VOiDDude]

If have multiple systems exactly like yours running fine. Try to tick the 'interact with desktop' on the voicemail service on to see what's happening.

 

[intrigrant]

In the manager there is a field for the IP Adress of the license key server.
It must be blank if using a serial dongle.

The VMProServer Server will always run, if you have a valid license or not does not matter.

If dialling *17 results in a busy tone means that : or VM Pro has no IP connection with IP Office or your license fail.

 

[jroosen]

Hello VOiDDude,
hello intigrant,

I forget to mention:
1: 'Interact with desktop is enabled. Result: none. There is the release info-line (v 2.1.18) and no further activity. In particular, when monitor shows the 'no free VM ports'-error, there is no activity in the screen.

2: Of cource, license server field in manager is empty. When I do a netstat on the VMPRO server I can see a connection between server and ipo all the time. It seems the connection is inititiated by server because servers port differs with each new connection whereas the ipo port is still the same and a very high port 5xxxx, don't know exactly in the moment.
What made me surprise is, the connection seems to persists when I stopped all services. But maybe I forgot an application.


So everything seems right:-??? Or am I wrong?
What's about my versions. ipo is running 2.1.24. VMPro is 2.1.18.

 

[IPGuru]

1) The serial dongle does not need feature key server, it talks directly to the IPO.

2) I am supprised that anyone who reads this forum is even thinking about V2.1(24) Upgrade to V2.1(27) or V2.1(31) NOW!

3) Check the IPO has the correct IP address specified for the VM server

4) Check the WIN XP firewall is correctly configured either allow the VM Pro Service (Not Voicemail pro that is just the configuration app) or disable the firewall completly

 

[intrigrant]

Or run SysMon :

You can check things using the SysMonitor application, run SysMonitor and do the following :
go to "File" and click on "Select Unit", enter the IP Addres and password of the IP Office
go to "Filters" and click on "Trace Options" a new window opens
click on the button marked "Tab clear all"
select the Tab "System" and select "Licensing", click on "OK"
Reboot the IP Office
In SysMonitor you should see a message like this :
1880mS LIC: Added Keylok token 00:47:df:34 (never expires)

This means that the serial key is recognized.
If the licenses are put in the Manager then you will see wich licenses are valid in SysMon.

It can take some time before licenses show "valid", be patient.

To be sure the PC is ok, install VM Lite from the Admin CD, stop the VM Pro services and run VM Lite.

 

[jroosen]

Ok, did a lot things:
I did an upgrade from 2.1.24 to 2.1.31.
Didn't change behaviour.
Then I took the config through the config wizard. It had errors and I removed those errors.
So now I have a proper config.
Along with the upgrade I removed vmpro and admin suite and reinstalled it with admin 2.1.31 und vmp2.1.18 (installed 2.0.17 and did an upgrade.
ipo license server field is empty and licenses are valid.
VMPro server runs and shows regular housekeeping messages and time request event from ipo (timeserver in ipo is not configured, so ipo uses vm-server setting for this. This shows, that vm-server setting is correct).
But *17 is still busy, when dialing an extension monitor still shows error with no free channel.
See monitor messages below:
> 723mS LIC: Added token 00:e0:07:01:57:1e (never xpires)
> 1610mS LIC: Added Keylok token 00:47:e5:d5 (never expires)
> 1611mS LIC: Licence for "Voicemail Pro (4 Ports)" is valid
> 1611mS LIC: Licence for "Phone Manager Pro IP Audio Enabled (users)" is valid
> 1612mS LIC: Licence for "Phone Manager Pro (per seat)" is valid
> 1612mS LIC: Licence for "Phone Manager Pro (per seat)" is valid
> 1613mS LIC: Licence for "Phone Manager Pro (per seat)" is valid
> 1614mS LIC: Licence for "Phone Manager Pro IP Audio Enabled (users)" is valid
> 1614mS LIC: Licence for "Phone Manager Pro IP Audio Enabled (users)" is valid

Error Mesage after 3rd call from Extn206 to Extn203
> 161061mS CMTARGET: SELECT:2 0 0 TGHG=00000000 TGUSER=ffe33104 INCL=00000001 EXCL=00000001
> 161062mS CMTARGET: ADD USER:2 Extn203(203, state=Ringing) (depth=1 B=1) cw=0
> 161062mS CMTARGET: SELECT:2 NO TARGETS, TRY VOICEMAIL
> 161062mS ERR: CMCall::No Free Voicemail ports
> 161062mS CMTARGET: SELECT:2 NO TARGETS, ROUND AGAIN
> 161062mS CMTARGET: SET USER:2 Extn203 orig=0
> 161063mS CMTARGET: ADD USER:2 Extn203(203, state=Ringing) (depth=1 B=1) cw=0
> 161063mS CMTARGET: SELECT:2 SEND SETUP (clearing old=0)

On the VMPRO server I can identify 2 UPD-Ports raised by the VMPRO service: TIME-Port and Port 50791. There is no firewall on the system. It's Win2000proSP4. Static ip-address, dns and gateway configured fine (although everything plays in one subnet) and switch-connected.

I also installed voicemail lite and launched it (stopped VMPRO service before). VMlite raised the same udp-ports like the PRO version. But behaviour remains the same after an ipo reboot. No VM-function, only activity on server screen were the time-requests. Timeserver in ipo is not configured, so ipo obvisiously uses the voicemail-server setting (the only setting in ipo that points to the vmpro-server) to get the time from it.

 

[intrigrant]

Licenses are OK, VM Pro PC seems OK, leaves the IP Office itself.

Check:
In System -> Voice Mail do you have the IP address of VM PC and the option PC selected?
Check IP Routes as well.

Can't think of anything else.

 

[jroosen]

yes,
VM option PC is selected.
IP-Routes are also ok.

 

[mforrence]

Did you turn off Windows and/or any other (Norton, etc.) firewall? It really sounds like a firewall is active and preventing connection.

 

[row1030]

I've recently added VM Pro to a SOE with a serial dongle. If all the licenses show valid then your key is fine. Make sure your VM in manager is set to the correct IP to match your VM Pro server?

 

[intrigrant]

Call a specialist, your name suggest youre in NL.

 

[jroosen]

Ok,
here comes the NEWS.
I agree, this looks like a connectivity problem.
So I took some traces of whats happening.
The result is very strange:
When calling *17 the only packet I can see is a
broadcast from ipo to 255.255.255.255 on udp-port 50799!!!
This is strange as the only port my vm-services raise are
time on udp 123 and a upd port on 60791 !!!
So, this is obvisiously the reason.
But why does ipo do a broadcast on this strange port. vmpro-box
is configured in manager properly.
As I couldn't believe this I did the same trace a second time and it was exactly the same.

Then I traced a devert to mailbox. I called an extension.
In the trace I saw this same boring broadcast at about 5-6 seconds after calling.
Redirection should work after 10 seconds so this broadcast seem to be a kind of
call preparation.
Of cource there was no redirection to mailbox. In the trace then (at about 15-17 seconds after
call initiating) ipo sent a short bunch of broadcast again. 6 or 7 pakets but no proper IP packets.
Those packets have a proper structure up to the ip source and dest- adresses. But when ip packets
then have a type-field of 0x0800, the those packets have a type-field of 0x4744
See one of those packets below:

Frame 135 (60 bytes on wire, 60 bytes captured)
Arrival Time: Apr 28, 2005 21:07:33.409075000
Time delta from previous packet: 0.000003000 seconds
Time since reference or first frame: 19.066986000 seconds
Frame Number: 135
Packet Length: 60 bytes
Capture Length: 60 bytes
Protocols in frame: eth:data
Ethernet II, Src: 00:e0:07:01:57:1e, Dst: ff:ff:ff:ff:ff:ff
Destination: ff:ff:ff:ff:ff:ff (Broadcast)
Source: 00:e0:07:01:57:1e (213.128.108.68)
Type: Unknown (0x4744)
Data (46 bytes)

0000 01 00 e0 07 01 57 1e d8 00 00 58 2e 49 50 20 34 .....W....X.IP 4
0010 30 31 20 4e 47 00 bd 60 ff 92 38 b0 00 00 00 02 01 NG..`..8.....
0020 00 00 00 01 00 00 00 00 d5 80 6c 44 03 01 ..........lD..

Again 10 seconds later there was again this initial broadcast on port (every one should know it now, it's 50799)))
Then I hung up the call.

So, is there anyone capable to give some information on this behaviour.
Givven mail several voicemail installs all produce the same listening port 50791, why does ipo uses the other one.
Does any one have information on avayas port usage?

 

[sizbut]

The broadcast is nothing to do with Voicemail Pro, its a BLF broadcast from the IP Office to any of its apps (PhoneManager and SoftConsole).

I have to say that you guys seem to have dived far to deep already rather than checking the basics.

The licensing looks fine.

1) Run the Voicemail Pro GUI and save/make live. Does that help.

2) Rejig the voicemail pro service to interact with the desktop and restart it. Do you see it check license details with the IP Office and then check/rebuild mailboxes.

3) Connect the Voicemail Pro PC direct to the IP Office control unit to remove all intervening network equipment from the issue.

 

[jroosen]

>1) Run the Voicemail Pro GUI and save/make live. Does that help.

No, tried already and multiple times.

>2) Rejig the voicemail pro service to interact with the desktop and restart it. Do you see it check license details with the IP Office and then check/rebuild mailboxes.

No, see my comments above.

>3) Connect the Voicemail Pro PC direct to the IP Office control unit to remove all intervening network equipment from the issue.

Will do this tommorw because of murphy and layer one.

What does BLF stand for?

 

[intrigrant]

Are yous shortcodes ok? Did you read the installing manuals before starting? If you follow the instructions step by step you can hardly fail.
If still no succes you should contact your vendor or call a specialist in you area.

 

[Ragnorak]

Avaya has a Voice Mail Pro debugging tool that can be very helpful.

I ran into a similar problem on an installation. The problem was Norton (antivirus I think but it may have been part of a package.) Even with everything disabled and not starting it still wouldn't work, I had to uninstall it for the voicemail to pick up.

 

[jroosen]

So, finally I got it running.
I simply did a factory default and once reboot was initiated I saw proper registrations on my vmpro log.