asterisk users - Mar 2009 - Are .call files working with extensions.ael ?

Hello,

With an extensions.ael enabled system, I keep getting whatever I change into
my "astup.call" file :

[Mar 12 00:13:56] WARNING[2538]: pbx_spool.c:267 apply_outgoing: At least
one of app or extension (or keyword message/pdu) must be specified, along
with tech and dest in file /var/spool/asterisk/outgoing/astup.call
[Mar 12 00:13:56] WARNING[2538]: pbx_spool.c:457 scan_service: Invalid file
contents in /var/spool/asterisk/outgoing/astup.call, deleting
[Mar 12 00:13:56] WARNING[2538]: pbx_spool.c:505 scan_thread: Failed to scan
service '/var/spool/asterisk/outgoing/astup.call'


With an extensions.conf enabled system, the same "astup.call" file
would
work.

Has anyone tried ?
Any hint ?

Channel: sip/700 at mylocal
CallerID: 692 <692>
MaxRetries: 1
WaitTime: 60
RetryTime: 5
Context: mylocal
Extension: 00123457530
#Priority: 1

I suppose I should have written "mylocal" context in a different way
as my
extensions.ael includes :

context mylocal {
        includes {
                subs;
                };
<snip>
       700 => ...
};

Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20090312/cd51bc50/attachment.htm

On Wed, Mar 11, 2009 at 5:29 PM, Olivier <oza-4h07 at myamail.com> wrote:
> Hello,
>
> With an extensions.ael enabled system, I keep getting whatever I change
> into my "astup.call" file :
>
> [Mar 12 00:13:56] WARNING[2538]: pbx_spool.c:267 apply_outgoing: At least
> one of app or extension (or keyword message/pdu) must be specified, along
> with tech and dest in file /var/spool/asterisk/outgoing/astup.call
> [Mar 12 00:13:56] WARNING[2538]: pbx_spool.c:457 scan_service: Invalid file
> contents in /var/spool/asterisk/outgoing/astup.call, deleting
> [Mar 12 00:13:56] WARNING[2538]: pbx_spool.c:505 scan_thread: Failed to
> scan service '/var/spool/asterisk/outgoing/astup.call'
>
Olivier--

It's complaining that you don't have  "Extension: ---- "  and 
"Priority:
..... " lines in your call file, along with the context,
The Channel: lines calls one phone, the Context, Extension, and priority say
what to execute for the other channel,
and the two are bridged.

Whether the context, exten, and priority specified are in an AEL supplied
dialplan or an extensions.conf
dialplan, doesn't matter. You can even mix both together to form a dialplan.

Let's see, I have a call file laying around...

Channel: Sip/snom
Context: workext
Extension: 983075878001
Priority: 1
...

This will ring the phone specified in Channel, and when it answers, it will
run the extension you specify, and connect the two. (in this case it will
dial the "movie hot line" in Cody, WY, and the leading "98"
says to use
a certain ISP to place the call.

murf

>
> With an extensions.conf enabled system, the same "astup.call"
file would
> work.
>
> Has anyone tried ?
> Any hint ?
>
> Channel: sip/700 at mylocal
> CallerID: 692 <692>
> MaxRetries: 1
> WaitTime: 60
> RetryTime: 5
> Context: mylocal
> Extension: 00123457530
> #Priority: 1
>
> I suppose I should have written "mylocal" context in a different
way as my
> extensions.ael includes :
>
> context mylocal {
>         includes {
>                 subs;
>                 };
> <snip>
>        700 => ...
> };
>
> Regards
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>


-- 
Steve Murphy
ParseTree Corp
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20090311/98b6ca2c/attachment.htm

Hello Olivier,
> With an extensions.ael enabled system, I keep getting whatever I change 
> into my "astup.call" file :
> 
> [Mar 12 00:13:56] WARNING[2538]: pbx_spool.c:267 apply_outgoing: At 
> least one of app or extension (or keyword message/pdu) must be 
> specified, along with tech and dest in file 
> /var/spool/asterisk/outgoing/astup.call
> [Mar 12 00:13:56] WARNING[2538]: pbx_spool.c:457 scan_service: Invalid 
> file contents in /var/spool/asterisk/outgoing/astup.call, deleting
> [Mar 12 00:13:56] WARNING[2538]: pbx_spool.c:505 scan_thread: Failed to 
> scan service '/var/spool/asterisk/outgoing/astup.call'
Do you by chance use bristuff?

-- 
Best regards

Peer Oliver Schmidt
PGP Key ID: 0x83E1C2EA

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

Hi,

As soon as I removed back line 266 as suggested by Peer Oliver, it worked.


Lines changed in /usr/src/bristuff-0.4.0-RC4-xr6/asterisk/pbx/pbx_spool.c :
/* Olivier
        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))) {
*/
        if (ast_strlen_zero(o->tech) || ast_strlen_zero(o->dest) ||
(ast_strlen_zero(o->app) && ast_strlen_zero(o->exten))) {


Procedure used to update:
cd /usr/src/bristuff-0.4.0-RC4-xr6/asterisk/
make all
make install

File astup.call :
Channel: Sip/700
Context: mylocal
Extension: 00123457530
Priority: 1



Now, looking at removed line, it would say "if both message and pdu are
empty, then print error message".
Question is now, is this a feature (ie you must either add a pdu or a
message (or both) in call files) or a bug ?

Regards

PS: I'll post the answer to Bristuff mailinglist as this must of interest
there ...
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20090316/1e348e8b/attachment.htm