StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7733069
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-11T22:03:09.167
FavoriteCount
0
LastActivityDate
2011-10-11T22:03:09.167
LastEditDate
LastEditorUserId
0
OwnerUserId
194175
ParentId
7661567
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
There is currently no way to do that without removing the call file from your spooling directory (usually: /var/spool/asterisk/outgoing). What you need to do (if you need to kill the retry attempts), is: <pre><code>rm /var/spool/asterisk/outgoing/<callfilename> </code></pre> Another way to handle this is pragmatically, via your dialplan callbacks. For instance: Let's say your callfile looks like the following: <pre><code>Channel: SIP/flowroute/18002223333 Context: my_code Extension: s Priority: 1 MaxRetries: 3 </code></pre> And you want to make your callfile retry the call two times (at most). You could write your dialplan code (to implement <code>my_code</code>) as follows: <pre><code>[my_code] exten => s,1,ExecIf($[ !${DB_EXISTS(call/tries)} ]?Set(DB(call/tries)=0)) exten => s,n,Set(DB(call/tries)=${MATH(${DB(call/tries)}+1,i)}) exten => s,n,NoOp(your code here...) exten => s,n,GotoIf($[ ${DB(call/tries)} > 1 ]?end,1) exten => end,1,DBDel(call/tries) exten => end,n,System(rm /var/spool/asterisk/outgoing/<name>) exten => end,n,Hangup() </code></pre> This will store the state of the callfile in the Asterisk database, and do some manual counting to verify that the call has been attempted < 3 times (if not, then it'll hangup). This method is obviously not optimal (as it's much easier to control this behavior from the application you wrote which actually spools the callfile), but it will work. Hopefully that helps!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODelete Asterisk call file before Maxretries is reached
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USrdegges
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODelete Asterisk call file before Maxretries is reached
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.