Hi All, Have created a system that involves using call files in the outgoing spool folder. On some occasions it retries which is fine.... is there any way to view calls waiting retries from the CLI? Using 1.4 btw. Have googled to no avail (although it is near the end of the day so I might be being a muppet!) Thanks in advance. Steve
Steven Howes schrieb:> Have created a system that involves using call files in the outgoing > spool folder. On some occasions it retries which is fine.... is there > any way to view calls waiting retries from the CLI? Using 1.4 btw. > Have googled to no avail (although it is near the end of the day so I > might be being a muppet!)One solution would be to look INTO the callfiles. The content of the file changes if there is a retry involved. I don't know by heard how exactly it changes but afair there is a line stating the retry time. Christian
I have successfully created call files and I can get Asterisk to make calls based on those files. The problem I have is that it seems you need to use a Channel for the first leg of the call file. This means I have to use either a ZAP, SIP or IAX2 channel. What I would prefer to do is send the first leg of the call to a context and extension so I can send the call using DUNDi rather than a predefined channel. Once the call has been established then is should go to context, extension so the second leg of the call can be completed. Is it possible to send the first leg of a call file to DUNDi and if not aviable send over IAX2 or then ZAP? The call files seem to be limited to a channel and not allow the first leg of the call to be decided by the path of a context, extension. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20081106/86ac0f69/attachment.htm
On 6/11/2008 3:01 p.m., David Klaverstyn wrote:> Is it possible to send the first leg of a call file to DUNDi and if not > aviable send over IAX2 or then ZAP? > > The call files seem to be limited to a channel and not allow the first > leg of the call to be decided by the path of a context, extension.Use the Local channel: http://www.voip-info.org/wiki/index.php?page=Asterisk+Local+channels -- Kind Regards, Matt Riddell Director _______________________________________________ http://www.venturevoip.com (Great new VoIP end to end solution) http://www.venturevoip.com/news.php (Daily Asterisk News - html) http://www.venturevoip.com/newrssfeed.php (Daily Asterisk News - rss)
Local channel will help you send your call through the dialplan. You can make all your decision there. If it answers, then the specified application will be execute. Check this example http://www.astblog.com/2008/09/18/use-the-power-of-local-channels/ David Klaverstyn wrote:> > I have successfully created call files and I can get Asterisk to make > calls based on those files. The problem I have is that it seems you > need to use a Channel for the first leg of the call file. This means > I have to use either a ZAP, SIP or IAX2 channel. What I would prefer > to do is send the first leg of the call to a context and extension so > I can send the call using DUNDi rather than a predefined channel. > > > > Once the call has been established then is should go to context, > extension so the second leg of the call can be completed. > > > > Is it possible to send the first leg of a call file to DUNDi and if > not aviable send over IAX2 or then ZAP? > > > > The call files seem to be limited to a channel and not allow the first > leg of the call to be decided by the path of a context, extension. > > ------------------------------------------------------------------------ > > _______________________________________________ > -- 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 > ------------------------------------------------------------------------ > > > Internal Virus Database is out of date. > Checked by AVG. > Version: 8.0.100 / Virus Database: 269.23.16/1448 - Release Date: 5/16/2008 7:42 PM >