DTMF RFC2833 - Not Working
2 posters
Page 1 of 1
DTMF RFC2833 - Not Working
Hi Team,
Im testing FreeSBC and have my Yealink headsets set to RFC2833 for DTMF but that doesn't seem to work. Only SIP INFO seems to work with DTMF, is there a setting to enable RFC2833?
Regards,
Glen Ganderton
Im testing FreeSBC and have my Yealink headsets set to RFC2833 for DTMF but that doesn't seem to work. Only SIP INFO seems to work with DTMF, is there a setting to enable RFC2833?
Regards,
Glen Ganderton
ggflow- Number of Messages : 5
Point : 9
Registration Date : 2022-03-08
Re: DTMF RFC2833 - Not Working
Hi
SBC is compatible with RFC2833. But if you want to transcode between RFC2833 and SIP INFO you need to use a transcoding device. To better understand the RFC2833 problem you can run RTP capture on ProSBC, please flow the link below and analyze the RTPs with wireshark;
https://docs.telcobridges.com/mediawiki/index.php/VoIP_Ethernet_Capture_FreeSBC_A
SBC is compatible with RFC2833. But if you want to transcode between RFC2833 and SIP INFO you need to use a transcoding device. To better understand the RFC2833 problem you can run RTP capture on ProSBC, please flow the link below and analyze the RTPs with wireshark;
https://docs.telcobridges.com/mediawiki/index.php/VoIP_Ethernet_Capture_FreeSBC_A
Similar topics
» TCP transport Server not working
» Send DTMF with payload 101 instead of 96
» What does the system require to detect DTMF tones for SIP INFO?
» What are the steps to capture a call trace if no DTMF input is detected?
» Inbound calls are working but outbound calls are failing for SIP Trunk
» Send DTMF with payload 101 instead of 96
» What does the system require to detect DTMF tones for SIP INFO?
» What are the steps to capture a call trace if no DTMF input is detected?
» Inbound calls are working but outbound calls are failing for SIP Trunk
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum