[asterisk-users] Wake-Up Call didn't work

[Asterisk guy]

1  there is a correct file in  /var/spool/asterisk/outgoing

2  i run  asterisk -vvvvr to monitor it  , it gives out the following error

 -- Attempting call on Local/6009 at default for application MusicOnHold()
(Retry 1)

Jul 24 08:23:17 NOTICE[21177]: chan_local.c:479 local_alloc: No such
extension/context 6009 at default creating local channel

Jul 24 08:23:17 NOTICE[21177]: channel.c:2409 __ast_request_and_dial: Unable
to request channel Local/6009 at default


( but i have a extension 6009 login to * ) ,  what is the problem?



On 7/23/07, James FitzGibbon <james.fitzgibbon at gmail.com> wrote:
>
> On 7/23/07, Dovid B <asteriskusers at dovid.net> wrote:
>
>  Can it be that asterisk does not have permission to copy the file over ?
> > Also check your date settings on the server.
> >
>
>
> Yes, it's interesting that the page intro includes the sentence "Lots of
> error checking to make sure its done correctly", but the final step that
> makes the process work (ensuring that the callfile ends up in the directory
> that pbx_spool is watching) doesn't have any error checking:
>
> touch( $wakefile, $time_wakeup, $time_wakeup );
>
> rename( $wakefile, $callfile );
>
> The fact that you see files in /tmp when all is said and done means that
> at least some of the script is working.  A few things to check:
>
> Do the files in /tmp have the correct timestamp (file matches the
> requested wakeup time)?  If so, then everything preceeding the rename seems
> to have worked, so check if the user running the AGI can move files from
> /tmp to /var/spool/asterisk/outgoing.  Though given that it's an AGI being
> run by *, you'd have to have a pretty strange setup for that to fail.
> Perhaps the outgoing directory just doesn't exist (was never created for
> some reason?)
>
> If the files don't have the correct timestamp, start following the logic
> backwards.  Do they look complete?  Look through the AGI for places where
> the wakeup file is written to (i.e. fputs( $wuc, "maxretries: $parm_maxretries\n");
> ) and check that everything that should be written is being written
>
> Working backwards you should be able to figure out where the script is
> failing, then you can check everything that comes afterwards as the user
> running the AGI to make sure that permissions and directories are set up
> properly.
>
> --
> j.
> _______________________________________________
> --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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070724/d6da43b4/attachment.htm