Hi guys,
3CX has a blogpost set up which describes how to configure 3CX to have it forwards calls to Exchange 2013 to utilize the Unified Messaging functionality of it, like the awesome feature Outlook Voice Access. With Exchange 2010 this was fairly easy to set up. With Exchange 2013 however they have changed the way Exchange handles call routing. It now accepts calls on TCP 5060 and then replies with a redirect to either TCP 5065 or TCP 5067. Up to the latest version of 3CX publically available today (12 SP3), 3CX still doesn't seem able to handle this redirect on TCP 5060 well. The blogpost however doesn't mention a thing about it, but it plainly just doesn't work what is stated there. Now if you would tell 3CX to route the call directly to 5065 or 5067, it will work. But there's no way in telling when Exchange switches from 5065 to 5067 or vice versa, so its an ongoing administrative task which is cumbersome.
Below are the logs which show what is happening:
I have tried to search for people facing this issue as well and couldn't find anything on the topic. Is it that I'm doing something wrong or is it just a too exotic combination that nobody is using? If anybody could help me out on this, it would be greatly appreciated!
3CX has a blogpost set up which describes how to configure 3CX to have it forwards calls to Exchange 2013 to utilize the Unified Messaging functionality of it, like the awesome feature Outlook Voice Access. With Exchange 2010 this was fairly easy to set up. With Exchange 2013 however they have changed the way Exchange handles call routing. It now accepts calls on TCP 5060 and then replies with a redirect to either TCP 5065 or TCP 5067. Up to the latest version of 3CX publically available today (12 SP3), 3CX still doesn't seem able to handle this redirect on TCP 5060 well. The blogpost however doesn't mention a thing about it, but it plainly just doesn't work what is stated there. Now if you would tell 3CX to route the call directly to 5065 or 5067, it will work. But there's no way in telling when Exchange switches from 5065 to 5067 or vice versa, so its an ongoing administrative task which is cumbersome.
Below are the logs which show what is happening:
Code:
7-Mar-2014 12:56:11.104 Leg L:22.1[Line:10000<<00316xxxxxxxx] is terminated: Cause: BYE from PBX
07-Mar-2014 12:56:11.054 [CM503020]: Call(C:22): Normal call termination. Call originator: Line:10000<<00316xxxxxxxx. Reason: Terminated
07-Mar-2014 12:56:11.054 L:22.1[Line:10000<<00316xxxxxxxx] failed to reach Ivr:99, reason Redirected
07-Mar-2014 12:56:11.054 Leg L:22.2[Ivr] is terminated: Cause: 302 Moved Temporarily/INVITE from 192.168.xx.xx:5060
07-Mar-2014 12:56:11.053 [CM503003]: Call(C:22): Call to <sip:[email protected]:5060> has failed; Cause: 302 Moved Temporarily/INVITE from 192.168.xx.xx:5060
07-Mar-2014 12:56:11.053 [CM503014]: Call(C:22): No known route from Line:10000<<00316xxxxxxxx to target: <sip:[email protected]:5062>
07-Mar-2014 12:56:11.053 [CM503006]: Call(C:22): Diverted to: <sip:[email protected]:5062>
07-Mar-2014 12:56:11.053 Call to T:Ivr:99@[Dev:sip:exchange2013.xxxx:5060;transport=TCP] from L:22.1[Line:10000<<00316xxxxxxxx] failed, cause: Cause: 302 Moved Temporarily/INVITE from 192.168.xx.xx:5060
07-Mar-2014 12:56:10.612 [CM503025]: Call(C:22): Calling T:Ivr:99@[Dev:sip:exchange2013.xxxx:5060;transport=TCP] for L:22.1[Line:10000<<00316xxxxxxxx]
07-Mar-2014 12:56:10.583 [CM503027]: Call(C:22): From: Line:10000<<00316xxxxxxxx (<sip:[email protected]:5060>) to T:Ivr:99@[Dev:sip:exchange2013.xxxx:5060;transport=TCP]
07-Mar-2014 12:56:10.582 [CM503004]: Call(C:22): Route 1: from L:22.1[Line:10000<<00316xxxxxxxx] to T:Ivr:99@[Dev:sip:exchange2013.xxxx:5060;transport=TCP]
07-Mar-2014 12:56:10.582 [CM505003]: Provider:[xxxx] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [(Very nice Sip Registrar/Proxy Server)] PBX contact: [sip:[email protected]:5060]
07-Mar-2014 12:56:10.578 [CM503001]: Call(C:22): Incoming call from Line:10000<<00316xxxxxxxx to <sip:[email protected]:5060>I have tried to search for people facing this issue as well and couldn't find anything on the topic. Is it that I'm doing something wrong or is it just a too exotic combination that nobody is using? If anybody could help me out on this, it would be greatly appreciated!
Exchange swaps ports every week or other week. Pity that 3CX doesn't fix this. Would say it should be a fairly minor thing to fix. Thanks for sharing your experience though!
