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

VMPro Synchronisation 6

Status
Not open for further replies.

davea2

Technical User
Mar 14, 2005
742
GB
Hi

So I have just added a Secondary to an IPO network.

All is OK but I don't think the VMPro master is talking to the slave properly.
All set up as per the docs but - all the call flows on the master - should these get sent to and also be visible in the slave?
Should I also be able to see a list of users and mailboxes on the slave?

I am thinking yes, but there is nothing there, so assume I have got something wrong? (With the SMTP settings)

Cheers
 
Stop the voicemail on the primary.
You should see the secondary slave voicemail take over.

Then all your users and call flows will appear if you set it up correctly.

You can watch the process on SSA VOICEMAIL TAB.

If you open SSA for both systems voicemail tab..
Display them side by side
You will see the licence and ports on the primary.Active

On secondary SSA you won’t see any ports and inactive.

When the primary voicemail is off you can watch the ports changing over to the secondary server voicemail.

After a while usually about 3 minutes the voicemail type should change from none to say Centralised backup Active


When it’s working you can then log into the vmpro client of the secondary and the call flows should be there as well as the users and groups.

Re enable the Primary voicemail and SSA will show you the secondary closing down and the Primary voicemail ports becoming Active again.

This usually happens very quickly.

It it doesn’t work then you don’t have it set up correctly.

Have you tested your failover yet for phones from primary to secondary to see it they work.




 
Thanks for the reply, that's great.

I will test out of hours tonight.

Not tested phone failover either, all must be done out of hours

Cheers

 
I hope they are IP phones.
Otherwise it won’t work as it’s the ip phone that triggers the failover.

You can see it in SSA alarms
 
Thanks for the replies, I have yet to test again, but the problem was the SMPT settings diomains weren't liked.
I changed for IP addresses and communication started.

After a few minutes I could see the modules in the backup VMPro client
 
*SMTP
*domains
Been a long day
 
I have found the documentation a little light on detail.

Same for DECT resiliency, some of it needs to be interpreted

 
So, I am trying to do another one of these and I am finding that the severs are not even trying to communicate with each other.

No SMTP traffic whatsoever.
I have tried every combination of settings in SMTP Sender and SMTP Receiver I can think of and nothing at all..

Really tearing my hair out, any advice?

Anything that would stop the SMTP even trying to send anything?

Cheers!

 
It must be set up as the first SMTP server for this to work any VM to email settings must be after the set up for redundancy.
Main VM SMTP sender:
Mail Domain: ip address of the main VM server
Mail server: ip address of the main VM server
port:25
sender: vmpro@main
Main VM SMTP receiver:
internal
port: 25
Domain: ip address of the main VM server
Remote VM SMTP sender:
Mail Domain: ip address of the remote VM server
Mail server: ip address of the Main VM server
Port: 25
Sender: vmpro@main
Remote SMTP Receiver:
internal
Port: 25
Domain: ip address of the remote VM server
This is what worked for me.
Mike
 
Looks like they are starting to talk to each other!

many thanks!

dave

 
Just wanted to add to this thread in case anyone is still having problems with this, we have been told by Avaya this this is in fact the correct config:

Code:
1. RESILIENCY for PRIMARY  VOICEMAIL SERVER
Voicemail SMTP settings (using Voicemail client)
 
SMTP Sender

     MAIL DOMAIN: LOCAL_IP_ADDRESS = PRIMARY SERVER IP Address
     MAIL SERVER: localhost or 127.0.0.1
     PORT 25
     SENDER:VMPRO@LOCALHOST = PRIMARY SERVER  <== Any valid email address can be used in this field, as long as it does not conflict with your email domain.
     

SMTP RECEIVER

     Set to INTERNAL (Use the EXTERNAL option when the Voicemail Pro server is on a server where is co-exists with a third-party SMTP application, for example an IIS server with SMTP enabled)
     PORT25
     DOMAIN=LOCAL_IP_ADDRESS = PRIMARY SERVER IP Address

2. RESILIENCY FOR SECONDARY  VOICEMAIL SERVER
Voicemail SMTP settings (using Voicemail client)
 
Same as for Primary, but using the Secondary Server IP address:
 
 
SMTP Sender

     MAIL DOMAIN: LOCAL_IP_ADDRESS = SECONDARY SERVER IP Address
     MAIL SERVER: localhost or 127.0.0.1
     PORT 25
     SENDER:VMPRO@LOCALHOST = SECONDARY SERVER  <== Any valid email address can be used in this field, as long as it does not conflict with your email domain otherwise SYNCH will not start

For more info regarding voicemail to email settings please, refer to section below.

SMTP RECEIVER

     Set to INTERNAL (Use the EXTERNAL option when the Voicemail Pro server is on a server where is co-exists with a third-party SMTP application, for example an IIS server with SMTP enabled)
     PORT25
     DOMAIN=LOCAL_IP_ADDRESS = SECONDARY SERVER IP Address

We had originally set it up as per teletechman's post but it stopped working on 11.1

This config fixed a heap of issues at a bunch of places for us
 
Hi

Asking for a bit of advice on this...

Just had to rebuild a primary and secondary server, and the VMpros would not talk to each other.

I have tried all combinations of settings I can think of but nothing!
Well that's not strictly true, on restarting the Primary VM it looked like the backup was taking place, but actually the Primary VM got wiped.

Call flows, greetings, names everything, deleted.

Would appreciate some pointers!

Many thanks
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top