[Asterisk-Users] Class features in dialplan ?

[Lance Arbuckle]

> Here's how Mark wants it done:
> 
> In the channel_pvt structure, we have a pointer to a new structure:
> 
> struct ast_common_features {
>         char fwd[AST_MAX_EXTENSION];
>         char fwd_off[AST_MAX_EXTENSION];
>         .
>         .
>         .
> };
> 
> This allows the codes to be redefined per installation (for those who
> don't like the NANPA assignments) or even per channel.  In addition,
> those who want to handle the codes in the dialplan can turn off various
> featuresets by setting their codes to "".
> 
> Then, when we're processing extensions in the channel driver, we do
> the following:
> 
> if (ast_feature_match(&p->common_features, exten, ...)) {
>         /* Make channel if it doesn't already exist */
>         ast_feature_handle(chan, &p->common_features, exten, ...);
> }
> 
> and in the config, the features would be configured with another common
> routine:
> 
> else if (!ast_feature_config(&p->common_features, v->var, v->value)) {
>         ast_log(LOG_WARNING, "Unknown keyword '%s'\n", v->var);
> }
> 
> All these common features could then be handled either in a device
> independent way (such as forward, where the end number is entered into
> a database for later lookup) or in a device-specific way, as
> appropriate.
> 
> I've looked at implementing this, but it is quite complex and extensive,
> and I haven't had the time to complete it.  Add to that all the
> negativity of people who don't like this plan and have vociferously
> expressed their distaste (intending to implement these in the dialplan
> instead), and you see why this code is even more difficult to write.
> 
> -Tilghman



So, it sounds like everyone is stuck reinventing the wheel for a while
unless these featurs are going to be available "real soon now"  :)  I
guess I'll go throught the nanpa list and pick out the ones that are
must haves for now.
Thanks

-Lance