So I think i've found the culprit of the issue. ForceHELO was enabled on my Default Send Connector. Now that has been set to False, it has allowed all my outbound mail to attempt a TLS session. Now i'll keep an eye on this because I assume ForceHELO was enabled for a reason. No one knows why though.
We have been requested to send at very least, Opportunistic TLS emails to one of our partners, so i'm currently trying to get this to work with CheckTLS, however i'm having some trouble doing so.
We have a Server 2008 R2 box which hosts Exchange 2010. We have third party certs installed and...
Root cause has been found!
So I performed a trace and low and behold, my call got routed through to another number. Ultimately confused!
Turns out a divert by our supplier was put on during an investigation many many months ago. It appears it was never reverted!
That explains why the main...
The time profile is definitely correct and it's pointing to the right place as I can dial it internally.
It wouldn't be anything to do with the VM Pro port licenses would it?
I'll do that at half 5 tonight and see the call come in. Thanks.
I don't want to play around with profiles during core hours. So in the mean time, is there anything else I could check config wise?
Ta
I'm going a little barmy with the configuration which should just work.
We have an IP Office 500 V2 with a Voicemail Pro install on a CentOS linux box (this never gets touched).
Our setup for voice is on a different VLAN and we manage IP Office and Voicemail Pro from our data VLAN, this has...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.