| Summary: | ASTERISK-01498: [patch] - design suggestion: Codec names unification | ||
| Reporter: | malzina (malzina) | Labels: | |
| Date Opened: | 2004-04-29 05:04:40 | Date Closed: | 2011-06-07 14:05:21 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | This bug is a followup to bug 993 which has been closed (I cannot reopen it). You guys assumed that unifying codec names would break backwards compatibility of config files, but I do not see why. We could accept several codec names (the old one and the new one) to designate the same codec. When the old one is used, a warning message could be generated to encourage the user to use the new syntax, and we accept it anyway, that is it. | ||
| Comments: | By: sbingner (sbingner) 2004-04-29 05:49:23 I reopened the old bug, please post on there how you can do this without breaking codec compatibility. If you have a bug that you need reopened please contact somebody in IRC. | ||