04-10-2007 07:37 AM - edited 03-14-2019 08:54 PM
Greetings,
Recently I have found a problem with transferring voice mail between sites.
Transferring Voice mail from same site to same site works fine, but when we try to transfer to a remote site, it doesn?t transfer.
When the server reboots, all of the voice mails that were waiting to transfer push through at once.
Has anyone run into this problem, or a way to resolve it? Can it be as simple as restarting a service?
After the reboot it works fine for a few weeks, and then at some random time it stops transferring.
Solved! Go to Solution.
04-10-2007 12:32 PM
man, Im good! (good guessing)
Depends on the fowarding. It's mostly DNS that handles this and then Exchange has to allow fowarding from another domain. (allowing this in the Exchange server SMTP) It's basically relying messages, and normally this is turned off because this is how spammers hit servers.
so what you can do, is still check that DNS is working ok in each domain. Verify, check, and ping each server that they can talk to each other through the WAN.
If you are getting dropped packets, possibly when SMTP attempts to connect, or is connecting, it dies out and the message is not sent cause a backup on the que.
If the local DNS server is running slow, cant resolve the remote name quick enough, that would be aproblem.
04-10-2007 09:34 AM
can you describe your setup more. Sounds like you have Unity.
Is it Unity VMO?
How many Unity servers
Exchange at each site, or hub and spoke?
Sounds like you are trying to forward voicemails to another location that has Unity. In that case, here is what happens.... Exchange and AD basically do all the work. If you have UnityA and UnityB seperate by a WAN or whatever, AD/Exchange using its Sites and Services to do Message Transfers between the sites. Same thing as if you had ExchangeA and ExchangeB seperated by sites.
If your AD is having issues communicating between the sites, DNS issues between the sites or MTA in Exchange between the servers, this could be your problem.
04-10-2007 09:43 AM
T,
Yes, we use Unity. I should have said that from the start.
We have a unity server at site1 and site2
We are trying to forward voicemails from unity on site1, to unity on site2.
04-10-2007 09:48 AM
Sounds like someone set this up before you.
Unity can only forward messages between sites using AD/Exchange, Unity Bridge, or AMIS.
Unity Digital Networking requires that each Unity site, be a memeber of the same AD Domain. (Unity only runs on Active Directory and Exchange for message storage or Notes if you are using Notes) So yes, you do have AD and Exchange running at each location.
Question is, are they in the same domain? If they are in the same domain, then Digital networking should work with a few configs in AD/Exchange.
Unity VMO Domain
SiteA DC/Exchange
SiteB DC/Exchange
If they are not in the same domain, then message forwarding could be a problem
04-10-2007 10:17 AM
T,
Yeah, it was setup prior to me.
They are not in a domain, they are in a workgroup.
As I said, it works after a reboot fine. But at some time in the future... it stops and starts queueing them. THen at the next reboot it pushes everything through.
04-10-2007 10:25 AM
Well, Unity can't be in a workgroup. It has to be in Domain for it work with Exchange
So if you log into the Unity server you will have at the W2k screen:
Username
Password
Domain
If the servers are not in the same domain, then possibly someone setup SMTP forwarding between the two Exchange servers. (which is not standard)
you can read through the guide to understand the basic concepts of Digital Networking and how it works.
Also, if your backgroup is not AD/Exchange, then it would be wise to find someone to help out.
TAC is going to ask you how your network is setup. If you say it is workgroup, they wont believe you. So verify how UnityA and UnityB are setup. (Using Exchange or Notes, etc)
04-10-2007 12:12 PM
Your right again T,
They are on different domains. And someone has setup smtp forwarding.
I'm currently in the smtp for voicemail.menifee.com (remote delivery) and the connection state is stuck on retry.
04-10-2007 12:32 PM
man, Im good! (good guessing)
Depends on the fowarding. It's mostly DNS that handles this and then Exchange has to allow fowarding from another domain. (allowing this in the Exchange server SMTP) It's basically relying messages, and normally this is turned off because this is how spammers hit servers.
so what you can do, is still check that DNS is working ok in each domain. Verify, check, and ping each server that they can talk to each other through the WAN.
If you are getting dropped packets, possibly when SMTP attempts to connect, or is connecting, it dies out and the message is not sent cause a backup on the que.
If the local DNS server is running slow, cant resolve the remote name quick enough, that would be aproblem.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide