Summary: | ASTERISK-18736: Do not retransmit DTMF signal from INFO oriented mode SIP channel to RFC2833 oriented SIP channel | ||
Reporter: | Volnikov Ivan (ivan) | Labels: | |
Date Opened: | 2011-10-19 10:52:27 | Date Closed: | 2011-11-21 14:10:41.000-0600 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | Applications/app_dial |
Versions: | Frequency of Occurrence | Constant | |
Related Issues: | |||
Environment: | Linux RH 13 | Attachments: | |
Description: | 2 sip friends like: [222] username=222 type=friend secret=222 qualify=no nat=yes host=dynamic context=incoming-call call-limit=3 dtmfmode=rfc2833 callerid=Ivan<222> canreinvite=no progressinband=yes allow=all [225] username=225 type=friend secret=225 qualify=no nat=yes host=dynamic context=incoming-call call-limit=10 dtmfmode=info callerid=ayi<225> canreinvite=no progressinband=yes allow=all Dialplan [incoming-call] exten => _[0-9*#p]!,1,Dial(SIP/222) Make call 225->222 After successfully connection DTMF: 225->222 - FAIL 222->225 - OK | ||
Comments: | By: Paul Belanger (pabelanger) 2011-10-19 13:08:27.403-0500 We require a complete debug log to help triage the issue. This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Volnikov Ivan (ivan) 2011-10-20 01:41:56.886-0500 I have stated conditions of 100 % of a repeated situation. I think that the given situation is similar to bug fix. I certainly will put demanded broad gulls but later or I will put correction that will be more true |