| Summary: | ASTERISK-21382: make (at least some of) the payload numbers used by dynamic payload types configurable | ||
| Reporter: | Jaco Kroon (jkroon) | Labels: | |
| Date Opened: | 2013-04-04 11:17:20 | Date Closed: | 2013-04-04 12:41:45 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Core/RTP |
| Versions: | 11.3.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Gentoo Linux, asterisk 11.3.0, no DAHDI. | Attachments: | |
| Description: | I have a problem with one provider where DTMF fails due to our payload number for telephone-event not matching theirs. Asterisk is presenting a value of 101 and they discard and ignore this advertisement if it's not 96 (ie, they WILL NOT send us RFC2833 DTMF digits unless we change the payload type number to 96 for telephone-event).
We had a discussion with them, and they are adamant their behaviour is correct (which I know it's not) but I unfortunately have no choice but to comply with them (being one of the biggest telco's in the country and all). If one is able to specify the payload numbers in rtp.conf that would be fantastic, something like: {noformat} [payload-numbers] telephone-event=96 {noformat} That would be fantastic. But for the moment I'll event settle for only being able to configure telephone-event somehow. | ||
| Comments: | By: Rusty Newton (rnewton) 2013-04-04 12:41:45.966-0500 https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines#AsteriskIssueGuidelines-Howtorequestafeature Per the guidelines we don't accept feature requests on the tracker without patches. This would need to be written for Trunk to go into Asterisk. I don't see any indication that this is a bug. It sounds like the Telco is being very silly unfortunately. If you are working on writing this patch we can re-open, or if you find someone else on the asterisk-dev list who is interested in doing it then we can re-open. Feel free to ping a bug marshal or developer in #asterisk-bugs or #asterisk-dev to discuss. | ||