DTMF Issue
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: DTMF Issue
- From: kpfleming@xxxxxxxxxx (Kevin P. Fleming)
- Date: Fri, 09 Mar 2012 12:18:38 -0600
- In-reply-to: <BACE74A37B41AD4095D6C6174DC8F02E340D61@om.customteleconnect.local>
- References: <BACE74A37B41AD4095D6C6174DC8F02E25CFA1@om.customteleconnect.local><F748E485-E67E-48BB-BA9A-230E160830CC@SS7.PL><BACE74A37B41AD4095D6C6174DC8F02E25CFB5@om.customteleconnect.local><CAGbA=38_51ATJ83cb5C67SpP+gZ0merFSUGoZ+VTmx25xifcug@mail.gmail.com><BACE74A37B41AD4095D6C6174DC8F02E25D0FD@om.customteleconnect.local><BACE74A37B41AD4095D6C6174DC8F02E25D1A7@om.customteleconnect.local><BACE74A37B41AD4095D6C6174DC8F02E340CFD@om.customteleconnect.local> <4F57DED8.1000106@digium.com> <BACE74A37B41AD4095D6C6174DC8F02E340D61@om.customteleconnect.local>
On 03/09/2012 11:24 AM, Ryan Crowder wrote:
> I just upgraded to Asterisk 1.8.11.0-rc2 and there was no change. Can
> you please tell me the branch where this is fixed? And is there
> anything I can do to help ensure the fix makes it into the next
> production release?
Sorry, I was in fact mistaken. The revision that contains the fix is
358260, which occurred after the 1.8.11.0-rc1 tag was made. Since this
problem wasn't a regression from 1.8.10, it won't be in the 1.8.11 release.
It *will* be in 1.8.12, and of course you are free to apply the patch to
your system in the meantime.
--
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming at digium.com | SIP: kpfleming at digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org
[Index of Archives]
[Asterisk App Development]
[PJ SIP]
[Gnu Gatekeeper]
[IETF Sipping]
[Info Cyrus]
[ALSA User]
[Fedora Linux Users]
[Linux SCTP]
[DCCP]
[Gimp]
[Yosemite Backpacking]
[Deep Creek Hot Springs]
[Yosemite Campsites]
[ISDN Cause Codes]
[Asterisk Books]
