by Drakh, Wednesday 26 of July, 2006 [17:05:55 UTC]
Working with Asterisk Manager API connecting to asterisk via TCP/IP port 5038 i found a problem.
When i made originate and trying to hang it up with Action: hangup or Action ZapHangup i found that it does not work.
So i made one connection for originate and another for hangup. On the hangup connection again the same proble. Action: hangup or Action ZapHangup dosent worked again.
Again using just one connection for hanging and for originating i tryed to send after originate
Action: command
command: soft hangup channel
Doesnt work.
So again two connections one for originate and second for hangup.
on the hangup connection..
Action: command
command: soft hangup channel
WORKED..
222
333ZapHangup?
by flobi, Thursday 25 of August, 2005 [17:44:50 UTC]
Just out of curiousity, cause I haven't used Zap channels, does the normal hangup not work on Zap channels?
Usually ports are the equivalent of simultaneous connnections.
DIDs aren't usually tied to a specific port.
Whether outgoing calls take up a port depends on the provider.
Comments
333Hangup/ZapHangup doesnt work with AMI
When i made originate and trying to hang it up with Action: hangup or Action ZapHangup i found that it does not work.
So i made one connection for originate and another for hangup. On the hangup connection again the same proble. Action: hangup or Action ZapHangup dosent worked again.
Again using just one connection for hanging and for originating i tryed to send after originate
Action: command
command: soft hangup channel
Doesnt work.
So again two connections one for originate and second for hangup.
on the hangup connection..
Action: command
command: soft hangup channel
WORKED..
333ZapHangup?