- Joined
- Mar 3, 2016
- Messages
- 5
- Reaction score
- 0
Hello,
In my job to make a Migration Tutorial for people migrating from Asterix/FreePBX to 3CX, I ran into the following problem:
Example: When you have an Intercom or another device which registers as a SIP TRUNK to 3CX. Then 3CX can NOT forward DTMF tones incomming from the SIP Trunk Provider to the Intercom (which is a SIP Trunk and not an extension).
I tested the above thoroughlythe past days and made Wireshark traces. In the trace you can see DTMF tones (as RFC2833 payload) coming in from the SIP Provider to 3CX, now 3CX does forward them to Extensions but NOT to other SIP Trunks (aka, the Intercoms). For intercom systems it is very important to have DTMF working because of opening a Gate or Door is one of it functions.
See the two drawings below for the concept. I am wondering whether this is a 'bug' or 'by design'.
(Click to enlarge!)
When the Intercom Rings a normal extension, the extension can send DTMF and 3CX forwards this DTMF to the Intercom.

When the Intercom Rings a mobile phone (via the SIP Trunk Provider), the Mobile phone sends DTMF which is received by 3CX but 3CX does not forward this to the Intercom. In my Wireshark traces I see in the SIP/SDP block that all devices support RFC2833 (telephone-event-101).

(sorry for the attachments below, it is neccesary to display the above image and I can not hide them)
In my job to make a Migration Tutorial for people migrating from Asterix/FreePBX to 3CX, I ran into the following problem:
- 3CX can forward DTMF tones from a SIP Trunk to an Extension (IP Phone).
- 3CX can also forward DTMF tones from Extensions to the SIP Trunk Provider.
- 3CX can not forward DTMF tones received on a SIP trunk to another SIP tunk.
Example: When you have an Intercom or another device which registers as a SIP TRUNK to 3CX. Then 3CX can NOT forward DTMF tones incomming from the SIP Trunk Provider to the Intercom (which is a SIP Trunk and not an extension).
I tested the above thoroughlythe past days and made Wireshark traces. In the trace you can see DTMF tones (as RFC2833 payload) coming in from the SIP Provider to 3CX, now 3CX does forward them to Extensions but NOT to other SIP Trunks (aka, the Intercoms). For intercom systems it is very important to have DTMF working because of opening a Gate or Door is one of it functions.
See the two drawings below for the concept. I am wondering whether this is a 'bug' or 'by design'.
(Click to enlarge!)
When the Intercom Rings a normal extension, the extension can send DTMF and 3CX forwards this DTMF to the Intercom.
When the Intercom Rings a mobile phone (via the SIP Trunk Provider), the Mobile phone sends DTMF which is received by 3CX but 3CX does not forward this to the Intercom. In my Wireshark traces I see in the SIP/SDP block that all devices support RFC2833 (telephone-event-101).
(sorry for the attachments below, it is neccesary to display the above image and I can not hide them)