| Summary: | ASTERISK-09302: Yet another Asterisk/Enum related bug | ||
| Reporter: | evilbunny (evilbunny) | Labels: | |
| Date Opened: | 2007-04-23 18:30:42 | Date Closed: | 2007-07-11 19:59:11 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Functions/func_enum |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | As Per IETF suggestions we (e164.org) started listing IM protocols as E2U+X-IM:<protocol> as there is no official name space presently, however Asterisk fails to handle this correctly when specific types are requested (eg E2U+X-IM:SKYPE). If just SKYPE is specified this seems to work. http://www1.ietf.org/mail-archive/web/enum/current/msg04768.html | ||
| Comments: | By: Russell Bryant (russell) 2007-05-14 10:43:18 Can you please provide an example of an ENUMLOOKUP that does not work correctly? Also, provide the output that you would expect so that we have something to work with to verify any potential fixes. By: Jason Parker (jparker) 2007-06-26 13:51:20 No response from reporter. Closing. Feel free to reopen this issue if you can do both of the following: upgrade to the latest version of 1.2 (1.2.12.1 was 7 months old when this issue was reported), and if you are still having trouble, provide the information that Russell requested in note 63426. | ||