Distributed Voicemail and SCN question

[Nick M]

Hi All,

I am running 10.0.0.6 build 3 on 2 IPO 500v2 currently, they're both also running the application servers to provide voicemail.

Voicemail verions: IP Office Application Server - Linux PC R10.0.0.6

Site A (chicago), is setup with Voicemail set to Voicemail Pro.
Site B (london), is setup to Distributed pointing back to Site A.

My issue is, is when someone from Site B calls their extension from outside of the office and dials *7 to retrieve their messages it says no new messages. So it is clearly looking at the Site B voicemail server. If the same person / extension dials *17 from inside the office the voicemail connection goes over the SCN to Site A and retrieves their messages as it should. This is a non-issue in Centralized configuration for site B.

I believe I have SMTP setup properly, since I see messages moving from Site B to Site A.

I am wondering if there is any functionality similar to VPNM available now? I would much rather have individual Voicemail pro servers that are aware of remote extensions and able to forward messages to remote users. The only reason I am using distributed is for the ability to exchange messages between sites.

Thanks,
NM

 

[IPGuru]

When correctly configured all messages reside on the central server & that should be the one that the remote site accesses when retrieving mail

what do you have set for the VM Type in each system?
Are you certain that messages are being transferred from the remote to the central system?

You are using Apps server so this should be much simpler than on a Windows config where IIS & SMTP need correctly configuring before installing VM Pro.



Do things on the cheap & it will cost you dear

 

[Nick M]

Yes, this is syncing is working properly.

The workaround I figured out was to create a dumb extension and have it forward unconditional to *17 and then assign that to a dedicated incoming call route.

That correctly routes them to the central mailbox server. However if they dial their own DID and get their voicemail and press *7 it still goes to the wrong place.

And in dialing *17 from London etc has to traverse the SCN.

Ideally I would love to have (2) Voicemail pro servers that are able to exchange messages between each other. But not storing all on one site.

With our old Nortel CS1000 we achieved this with VPIM.

 

[IPGuru]

to be honest the SCN seems pointless as you cannot useit for calls between sites because of the quality.
in which case you may as well run each system stand alone (cant see whit site A would need access to site B's VM)

to access VM remotely you just need to set the DDI destination to Voicemail.

if you are going to keep the SCN then the 1st thing I would do is temporarily remove the Slave VM & set everything to use the 1 central VM,
one this is working correctly re-configure for Distributed

what are the SMTP settings you have configured on both of the VM Servers at present?




Do things on the cheap & it will cost you dear

 

[Nick M]

The reason I need SCN as far as I am aware is that I need users in Chicago to be able to forward /send voicemail to users in London as an example.

Site A Chicago SMTP (Voicemail pro server):
Mail Domain: 10.0.20.3
Mail Server: 10.0.20.3
Port: 25
Sender: vmpro@10.0.20.3

Site B London SMTP (Distributed)
Mail Domain: 10.245.20.3
Mail Server: 10.245.20.3
Port: 25
Sender: vmpro@10.245.20.3

 

[Nick M]

I also tried forwarding the incoming call route to access voicemail in Site B to forward to the PSTN number for outside access in Site A. However it uses the wrong time zone information and changes the dialect.

 

[IPGuru]

I think you ned to change the email addresses on the VM Pro's for them to work correctly.

· Messaging Between Voicemail Servers
For messaging between voicemail servers, the first entry in the SMTP Sender list must be the one configured and used. Each server uses the SMTP server service on the same server computer as the voicemail service. For example a Windows-based server uses the SMTP e-mail provided by the IIS on the same server. The voicemail service also uses the domain set to filter incoming SMTP mails received by the SMTP server. For this to work, the domain entered should be the fully-qualified name of the server on which the voicemail server is running, for example vmpro1.example.com. Any incoming messages where the recipient mail domain is not exactly the same as the specified domain are ignored. The recipient can either by vmsyncmaster, vmsyncslave, or the name or extension of a mailbox on the voicemail server, for example Extn201@vmprocentral.example.com or 201@vmprocentral.example.com.

I have always used vmsyncmaster@xxxx & vmsyncslave@xxx



Do things on the cheap & it will cost you dear