agi.NewEAGI blocks about agi HOT 9 CLOSED

Your program is almost certainly dying. If you look at the Asterisk console, it should be printing the stderr output from the AGI execution. There should be a stack trace there.

from agi.

I suspect the problem is with your implemenation to open file descriptor 3. I would expect that you would use something like this to open FD 3:

eagi, err := os.Open("/dev/fd/3")

from agi.

Just spent a bunch of time playing around with agi set debug on and -cvvvvv, but I see no stack-trace either in the console, or the Asterisk process' Stdout/err streams. Also, as mentioned, the NewStdio seems to block too - and that isn't going anywhere near fd/3! Are you saying its a crash because I'm having to rely on the final Wait to keep the call alive?

from agi.

/proc/<PID>/fd/3 seems to be more likely?

from agi.

Ah, sorry. I missed you saying that NewStdio was failing, too. I'll have to sanity check the basic operation here. I'm not sure that I'm actually using this library anywhere. I think I just whipped it up for testing some time ago.

from agi.

@Ulexus I've attempted to write a simple Golang script without this library, to simply read the EAGI stream, but running into the same issue. Opening a question on SO: http://stackoverflow.com/questions/43353694/accessing-fd-3-for-asterisk-eagi

from agi.

This might just be an issue with Docker: moby/moby#6607

from agi.

I'm going to try this: https://golang.org/pkg/syscall/#Read to see if it lets me read FD 3

from agi.

Closing old issue. Please re-open if this is still a problem.

from agi.