Le 30/04/2014 13:10, Thorsten Göllner a écrit :
Is your script really so simple?
Enable agi debugging (agi set debug on) and take look at it when this
happens.
On Thu, 1 May 2014, Hoggins! wrote:
Yes, it is fairly simple, really.
The problem is that Asterisk's behavior is not constant :
Hello,
Yes, it is fairly simple, really.
And I found out about the return code of Asterisk enabling the agi
debugging, precisely.
The documentation of the "GET DATA" entry specifies that Asterisk should
either return "-1", nothing, or the actual result of what the user
entered, but never "0", am
Is your script really so simple?
Enable agi debugging (agi set debug on) and take look at it when this
happens.
-Thorsten-
Am 30.04.2014 11:47, schrieb Hoggins!:
Hello all,
I have a strange problem with a very simple AGI script, using the GET
DATA command.
When using this command, Asterisk
Hello all,
I have a strange problem with a very simple AGI script, using the GET
DATA command.
When using this command, Asterisk often returns 0 as a result after a
"GET DATA beep 5000" command, without even waiting for input from the
calling party.
It is quite random : sometimes Asterisk behaves
