but maxium 3 times and if the *
star digit is used twice in sequence (without other digits inbetween ) then it means
'go to the menulevel above current level'.
This was todays 'noise' from me.
Freddi
Subject: Re: [Asterisk-Users] Feedback request: AGI GET DATA change -
termination digits
From
Why use this rather than STREAM FILE?
On Sat, 2003-10-18 at 16:50, Paul Crick wrote:
** REPOST: A week later and no feedback - am I the only one
** who'd find this functionality useful? No other AGI stuff
** out there needing something similar?
I'd like some feedback on potentially
** REPOST: A week later and no feedback - am I the only one
** who'd find this functionality useful? No other AGI stuff
** out there needing something similar?
I'd like some feedback on potentially submitting a request (and probably a
patch too) to change the way the AGI command GET DATA works.
** REPOST: A week later and no feedback - am I the only one
** who'd find this functionality useful? No other AGI stuff
** out there needing something similar?
I'd like some feedback on potentially submitting a request (and probably a
patch too) to change the way the AGI command GET DATA works.
While that change is fine, you could also just write the
same functionality with get digit and deal with it inside
the AGI app.
I guess the digit handling part is doable with WAIT FOR DIGIT.. I was going
to ask about interupting the prompt that played before that but on RTFM-ing
I see that
While that change is fine, you could also just write the
same functionality with get digit and deal with it inside
the AGI app.
I guess the digit handling part is doable with WAIT FOR DIGIT.. I was going
to ask about interupting the prompt that played before that but on RTFM-ing
I see that
I'd like some feedback on potentially submitting a request (and probably a
patch too) to change the way the AGI command GET DATA works.
Right now, # terminates the entry, which is then returned with the #
stripped off the end. What I'd like is to allow user configurable
termination digits, which