3CX & Microsoft Exchange 2013 SP1 voicemail integration

Status
Not open for further replies.

mobilowa

Forum User
Joined
Feb 5, 2015
Messages
45
Reaction score
4
I run latest 3CX pro V15.5 SP5 and Exchange 2013 SP1 CU19

Configured integration as mentioned on
https://www.3cx.com/docs/how-to-create-impersonated-user/

After configuration, when i dial VM number 99 call fails anf unanswered calls to VM diversion fails too from 3CX server to Exchange box

Error: (as failed; Cause: 302 Moved Temporarily)
06/28/2018 6:58:19 PM - [CM503003]: Call(C:313): Call to <sip:[email protected]:5060> has failed; Cause: 302 Moved Temporarily/INVITE from 192.168.1.140:5060
06/28/2018 6:58:19 PM - Call to T:Ivr:99@[Dev:sip:Mail.vxx.local:5060;transport=TCP] from L:313.1[Extn:20] failed, cause: Cause: 302 Moved Temporarily/INVITE from 192.168.1.140:5060
06/28/2018 4:01:02 PM - [CM503003]: Call(C:295): Call to <sip:[email protected]:5060> has failed; Cause: 302 Moved Temporarily/INVITE from 192.168.1.140:5060

once I exchange connection port in 3CX from 5060 to 5065 under VM setting in 3cx control pannel
All works fine, because

When having a look at the trace 3CX contacts exchange on port 5060 . Exchange UM will try to redirect the traffic to port 5065. As 3CX will continue to send messages to port 5060 the call won’t succeed.

Looks like current version of 3CX can not handle redirect message properly

Exchange UM Worker process will be recycled once a week, this may has as a result that the Nortel can’t setup a connection after one week. This because the UM Worker process is recycled and now is using 5067.

So manually change port to 5065 is not a consistent solution at all

Please kindly help on this.
Support team please investigate this issue
 
We have seem this a few times before and it is usually caused because in 3CX the FQDN is not written exactly as it is configured in Exchange. Note that in 3CX it is case-sensitive.

In 3CX make sure that the exchange FQDN is written exactly as in the 302:
Code:
06/28/2018 6:58:19 PM - Call to T:Ivr:99@[Dev:sip:Mail.vxx.local:5060;transport=TCP] from L:313.1[Extn:20] failed, cause: Cause: 302 Moved Temporarily/INVITE from 192.168.1.140:5060

This means that Mail.vxx.local in 3CX must be written "Mail.vxx.local", not "mail.vxx.local".
 
Yes we must specify in 3CX management console as per what this outputs in Exchnage Server CMD
net config workstation | findstr /C:"Full Computer name" - Must match exact case
 
Status
Not open for further replies.

Members Online Now

Forum statistics

Threads
111,831
Messages
589,277
Members
164,661
Latest member
ALVI