- Joined
- Dec 23, 2010
- Messages
- 9
- Reaction score
- 0
Hi,
I'm having problem with conference calls in V12 - external parties can't join them because 3CX hangs up after they press #.
Internal extensions can join conference calls without any problem.
This is from log:
26-feb-2014 17:00:17.916 L:18.2[Conf]: Terminating targets, reason: SIP ;cause=200 ;text="User hangup"
26-feb-2014 17:00:17.916 Leg L:18.2[Conf] is terminated: Cause: BYE from 127.0.0.1:40300
26-feb-2014 17:00:17.912 L:18.2[Conf] got Terminated Recv Req BYE from 127.0.0.1:40300 tid=e936eb00d163af11 Call-ID=OTY1MjRkMWE3ZDRiY2ExMzU5MDI5YWZmNWYyYzgxMzU.:
BYE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:40300;branch=z9hG4bK-d8754z-e936eb00d163af11-1---d8754z-;rport=40300
Max-Forwards: 70
Contact: <sip:[email protected]:40300;rinstance=09cd6742ab1ac9b8>
To: "*81:011xxxxxxx"<sip:[email protected]:5060;nf=e>;tag=20311847
From: <sip:[email protected]:5060>;tag=f72d7854
Call-ID: OTY1MjRkMWE3ZDRiY2ExMzU5MDI5YWZmNWYyYzgxMzU.
CSeq: 2 BYE
User-Agent: 3CX Conference Room
Reason: SIP;description="User Hung Up"
Content-Length: 0
3CX detects that user hangs up, but that is not the case.
I've even tried with restarting Windows server (2008 R2 on ESXi) but that didn't help.
I also changed extension numbers, inbound routing and that didn't help either.
Can anyone suggest any possible solution?
This worked flawlessly in V11.
Regards.
I'm having problem with conference calls in V12 - external parties can't join them because 3CX hangs up after they press #.
Internal extensions can join conference calls without any problem.
This is from log:
26-feb-2014 17:00:17.916 L:18.2[Conf]: Terminating targets, reason: SIP ;cause=200 ;text="User hangup"
26-feb-2014 17:00:17.916 Leg L:18.2[Conf] is terminated: Cause: BYE from 127.0.0.1:40300
26-feb-2014 17:00:17.912 L:18.2[Conf] got Terminated Recv Req BYE from 127.0.0.1:40300 tid=e936eb00d163af11 Call-ID=OTY1MjRkMWE3ZDRiY2ExMzU5MDI5YWZmNWYyYzgxMzU.:
BYE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:40300;branch=z9hG4bK-d8754z-e936eb00d163af11-1---d8754z-;rport=40300
Max-Forwards: 70
Contact: <sip:[email protected]:40300;rinstance=09cd6742ab1ac9b8>
To: "*81:011xxxxxxx"<sip:[email protected]:5060;nf=e>;tag=20311847
From: <sip:[email protected]:5060>;tag=f72d7854
Call-ID: OTY1MjRkMWE3ZDRiY2ExMzU5MDI5YWZmNWYyYzgxMzU.
CSeq: 2 BYE
User-Agent: 3CX Conference Room
Reason: SIP;description="User Hung Up"
Content-Length: 0
3CX detects that user hangs up, but that is not the case.
I've even tried with restarting Windows server (2008 R2 on ESXi) but that didn't help.
I also changed extension numbers, inbound routing and that didn't help either.
Can anyone suggest any possible solution?
This worked flawlessly in V11.
Regards.