Problems with VM to email 1

[PImoose]

Does anyone have tips on getting it to work through a local Exchange server? I've come across some pretty unique setups from FreePBX for getting email delivery to work with an inside Exchange so I was hoping for something else.

As a backup I am using our DynDNS Mailhop but I would rather not since we are limited on how much we can send a day through there.

Thanks

 

[PImoose]

I forgot to add that it has worked sporadically doing the remote SMTP setup so I was hoping to use an internal server.

 

[emtsupport]

Can I ask you to do a software update on your UCx.

This will add a new tab to the GUI, entitled Support.

Go into the Support tab and you will see System Log Files.

Make a test call that goes to voicemail on an extension that is set up to send the email notification,
Wait approximately 3 minutes for logging to occur and grab the last 200 line from the maillog
and either attach it to this thread.

Sincerely,
emtsupport

 

[ucxguy]

Hi PImoose!

There should be no reason to look for FreePBX related solutions. UCx uses postfix as its mail server - you just need correctly configured postfix and Exchange.

With a properly configured network, domain and DNS, the default configuration of postfix on UCx should send messages via the Exchange server without any additional configuration steps required. When postfix is started, it performs an MX lookup on the DNS Server and requests the mail server IP address. If an IP address is returned by the DNS server, postfix would use this address to route mail.

If your Exchange server is not receiving email messages from UCx, check the following:
1. The host name used for your UCx system uses the same domain name as the Exchange server
2. The domain name can be resolved using DNS on your network
3. The Exchange server is configured to allow messages from UCx (depending the version of your Exchange server, you may need to set up a receive connector for the IP address or host name of the UCx system)

If you still have problems, the output in maillog (available via the Support - System Log Files page in your GUI) should provide more info.

 

[PImoose]

I just did an update when I saw the latest post about the other controls. I'll work on looking at logs tomorrow as I am out of the office today.

1. The host name used for your UCx system uses the same domain name as the Exchange server
2. The domain name can be resolved using DNS on your network
3. The Exchange server is configured to allow messages from UCx (depending the version of your Exchange server, you may need to set up a receive connector for the IP address or host name of the UCx system)

I was looking at the host name, I tried our local domain.local and i tried companyname.com both with internal DNS pointers. Also something out of curiosity I noticed, the main unit says ucx450.domain.local and the UCx50 Gateways have the same hostnames, does that matter or should I change them?

Exchange is configured to allow the UCx's IP to relay. We have a separate send connector that I have all of the local servers added to for internal relaying of systems messages and such.

 

[PImoose]

Cool, found the mail logs which is alot more helpful than the asterisk ones.

We are getting this error with remote SMTP and are local server added: status=deferred (SASL authentication failed: server quimby.dw.local[172.27.1.90] offered no compatible authentication mechanisms for this type of connection security)



With remote SMTP off I was seeing that it was hitting our Public IP. I then went to our local DNS server (we use Dyn for outside) and added a mx record, we never had anything that required it before, and poof it's working now. Hopefully this is what I needed.