[asterisk-users] Are .call files working with extensions.ael ? bristuff problem

[Mark Michelson]

Peer Oliver Schmidt wrote:
> Olivier wrote:
>>>     Do you by chance use bristuff?
>> Yes, I do.
> 
> bristuff patches pbx/pbx_spool.c
> 
> I have no knowledge of C, but there seems to be a problem around line 
> 266.
> 
> The original line (pre-bristuff) looks like this:
> 
> if (ast_strlen_zero(o->tech) || ast_strlen_zero(o->dest) || 
> (ast_strlen_zero(o->app) && ast_strlen_zero(o->exten))) {
> 
> 
> The patched line looks like this:
> 
> if (ast_strlen_zero(o->tech) || ast_strlen_zero(o->dest) || 
> (ast_strlen_zero(o->app) && ast_strlen_zero(o->exten)) || 
> (ast_strlen_zero(o->message) && ast_strlen_zero(o->pdu))) {
> 
> Try reverting that line, and see if that helps with your problem. And 
> maybe someone with a better understanding of C can take a look at the 
> above problem.

Apparently bristuff has added new required parameters to call files. Basically, 
it has the same requirements as vanilla Asterisk (you must specify a full 
channel name and either an app or an extension) and it also requires that one of 
the "message" or "pdu" fields of the outgoing call are filled in. You may want 
to check bristuff documentation to figure out what these mean since they are not 
part of a regular Asterisk installation.

Mark Michelson