External parties can't join conference calls in V12

[jpillow]

Have you opened a ticket with 3cx as if yet??? One thing to try would be to backup 3cx and reinstall using the backup and restore tool that has saved the day for me on more than one occasion.

 

[patpah]

Hi guys,

we have the same issue with v12 sp6. This 3CX server is connected to a gateway "Shout IP", and 3CX support told me that
the problem is on this gateway.
We have another 3CX server in v9 and this one is also connected to a "Shout IP" with same version (v4.0.2) and same parameters,
and there is no problem with the # DTMF.

Nevertheless, we have found that if we force the gateway to work in INBAND mode (default is INBAND+OUTBAND), then external
parties can join the conference without any problem.
Unfortunately, we cannot keep the INBAND mode because in outgoing calls the DTMF doesn't work anymore.

In short, for incoming calls, a gateway or provider need to pass DTMF in INBAND mode to 3CX when its version is higher than v9 (??).

 

[npereira]

I am having the exact same issue.

I see from Wireshark, DTMF is being sent from the gateway as INFO messages and there is no duplicate # (Pound) sign sent.
They should change that to be a wait time of 3 seconds or so, that way we would not have this issue.

 

[SY]

I am having the exact same issue.

I see from Wireshark, DTMF is being sent from the gateway as INFO messages and there is no duplicate # (Pound) sign sent.
They should change that to be a wait time of 3 seconds or so, that way we would not have this issue.

Kindly, check audio stream from the gateway. Does it contain "inband" (audio) DTMFs?
Thanks

 

[npereira]

Problem fixed.

Gateway was sending out of band INFO messages as well as Audi stream having DTMF in-band. The INFO message was causing the second # sign being interpreted by the 3CX, at least that is what I think was happening.

After setting an option "Signaling Digit Relay Mode" to off, problem is now resolved.

Now, I no longer see INFO messages, nor do I see RTP Type 96 packets, but conference and other DTMF (also tested outbound) works fine.

Thanks to Pierre Jourdan 3CX tech

 

[petarl]

Hello all,

I've managed to resolve this issue by following previous solutions.

We're using beroNet bero*fix box to connect our ISDN PRI line to 3CX. On that gateway i've set the DTMF Mode to inband and now conference calls work!

That settings is here:
SIP > Modify button in line with configured SIP server > button more on window that opens > DTMF Mode, select inband instead of rfc2833

Regards.

 

[techmikeny]

I am also having this problem. I can dial into extension 700, enter the pin, press #, then the call disconnects.
We have Sotel SIP service

Thank you,
Mike

Activity log below
19-Sep-2014 13:04:19.005 Leg L:1096.1[Line:10006<<MYCELLNUM] is terminated: Cause: BYE from PBX
19-Sep-2014 13:04:19.004 [CM503008]: Call(C:1096): Call is terminated
19-Sep-2014 13:04:19.002 Leg L:1096.3[Conf] is terminated: Cause: BYE from 127.0.0.1:40300
19-Sep-2014 13:04:11.403 Leg L:1096.2[Ivr] is terminated: Cause: BYE from 127.0.0.1:40600
19-Sep-2014 13:04:11.198 [CM503007]: Call(C:1096): Conf:700 has joined, contact <sip:[email protected]:40300>
19-Sep-2014 13:04:11.193 L:1096.3[Conf] has joined to L:1096.1[Line:10006<<MYCELLNUM]
19-Sep-2014 13:04:11.038 [CM503025]: Call(C:1096): Calling T:Conf:700@[Dev:sip:[email protected]:40300;rinstance=a1e9763270aab866] for L:1096.1[Line:10006<<MYCELLNUM]
19-Sep-2014 13:04:10.986 [CM503027]: Call(C:1096): From: Line:10006<<MYCELLNUM ("Mike Epp" <sip:[email protected]:5060>) to T:Conf:700@[Dev:sip:[email protected]:40300;rinstance=a1e9763270aab866]
19-Sep-2014 13:04:10.986 [CM503004]: Call(C:1096): Route 1: from L:1096.1[Line:10006<<MYCELLNUM] to T:Conf:700@[Dev:sip:[email protected]:40300;rinstance=a1e9763270aab866]
19-Sep-2014 13:04:10.986 [CM505003]: Provider:[Sotel2012] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [ccnq3 nomedia egress-usa] PBX contact: [sip:OFFICENUM@OFFICEIPADDR:5060]
19-Sep-2014 13:04:07.062 Currently active calls - 1: [1096]
19-Sep-2014 13:03:59.759 [CM503007]: Call(C:1096): Ivr:802 has joined, contact <sip:[email protected]:40600>
19-Sep-2014 13:03:59.755 [CM503007]: Call(C:1096): Line:10006<<MYCELLNUM has joined, contact <sip:[email protected]:5060>
19-Sep-2014 13:03:59.753 L:1096.2[Ivr] has joined to L:1096.1[Line:10006<<MYCELLNUM]
19-Sep-2014 13:03:59.609 [CM503025]: Call(C:1096): Calling T:Ivr:802@[Dev:sip:[email protected]:40600;rinstance=c2a8bed04cf758dc] for L:1096.1[Line:10006<<MYCELLNUM]
19-Sep-2014 13:03:59.559 [CM503027]: Call(C:1096): From: Line:10006<<MYCELLNUM ("Mike Epp" <sip:[email protected]:5060>) to T:Ivr:802@[Dev:sip:[email protected]:40600;rinstance=c2a8bed04cf758dc]
19-Sep-2014 13:03:59.559 [CM503004]: Call(C:1096): Route 1: from L:1096.1[Line:10006<<MYCELLNUM] to T:Ivr:802@[Dev:sip:[email protected]:40600;rinstance=c2a8bed04cf758dc]
19-Sep-2014 13:03:59.559 [CM505003]: Provider:[Sotel2012] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [ccnq3 nomedia egress-usa] PBX contact: [sip:OFFICENUM@OFFICEIPADDR:5060]
19-Sep-2014 13:03:59.558 [CM503001]: Call(C:1096): Incoming call from Line:10006<<MYCELLNUM to <sip:802@SERVERIP:5060>
19-Sep-2014 13:03:59.557 Line limit check: Current # of calls for line Lc:10006(@Sotel2012[<sip:[email protected]:5060>]) is 1; limit is 4
19-Sep-2014 13:03:59.549 [CM503012]: Inbound any hours rule (unnamed) for 10006 forwards to DN:802