[asterisk-dev] ENUM changes: discussion

[John Todd]

I saw the changes to the ENUMLOOKUP function below, and one of them 
raises a question in my mind.  It seems to be going backwards to 
continue using the "enum.conf" file when this is easily specified in 
the function call itself, or assuming the "default" of e164.arpa. 
The RFC for ENUM describes e164.arpa as the "only" ENUM suffix, so 
while I don't agree that it is the "only" suffix that is useful for 
ENUM lookups, having it as a default seems perfectly reasonable.

Using .conf files when there is only one value in them seems to be 
wasteful and confusing.  The "h323driver" value is now meaningless 
(and should be removed) since the ENUMLOOKUP function no longer 
creates a "Dial" action.  So that narrows the number of features in 
enum.conf down to simply "search" and that doesn't do anything, 
either, since the ENUMLOOKUP function only searches through a single 
suffix.

If the dialplan author wishes to search through multiple ENUM zone 
suffixes, it is not (IMHO) an overwhelming burden to use a simple 
"GotoIf" to analyize the results of the prior ENUMLOOKUP function to 
see if there is a value in there.

I was rather hoping to have enum.conf become depreciated, and this 
change seems to go backwards a few steps and solidify it's rather 
confusing position in the config file directory.

JT


>
>Author: kpfleming
>Date: Tue Feb 14 16:20:14 2006
>New Revision: 10065
>
>URL: http://svn.digium.com/view/asterisk?rev=10065&view=rev
>Log:
>warn people about ENUMLOOKUP counting change
>
>Modified:
>     trunk/UPGRADE.txt
>
>Modified: trunk/UPGRADE.txt
>URL: 
>http://svn.digium.com/view/asterisk/trunk/UPGRADE.txt?rev=10065&r1=10064&r2=10065&view=diff
>==============================================================================
>--- trunk/UPGRADE.txt (original)
>+++ trunk/UPGRADE.txt Tue Feb 14 16:20:14 2006
>@@ -40,8 +40,10 @@
>    modules.conf file then you will need to explicitly load the modules that
>    contain the functions you want to use.
>
>-* The ENUM() function no longer supplies a default zone for 
>searching; instead,
>-  it uses the default zone(s) defined in enum.conf.
>+* The ENUMLOOP() function no longer supplies a default zone for 
>searching; instead,
>+  it uses the default zone(s) defined in enum.conf. In addition, when the 'c'
>+  option (for counting the number of records is specified), but the 
>lookup fails
>+  to match any records, the returned value will now be "0" instead of blank.
>
>  The SIP channel: