Chris Elliott
2008-Apr-30 14:08 UTC
[asterisk-users] asterisk-users Digest, Vol 45, Issue 85
That what I wanted. Extension 0 in the dialplan connects to the console. The Async option lets me call an extension from the console using a manager API app. The only downside is that by reversing the originate, the console doesn't hear any ring back. The 100% CPU utilization in the first case is a bug. I'm not quite sure where to submit it, but I'll read the FAQ and see about submitting it.> Plus that originate is going to call the sip device, and upon answer > connect it to extension 0 in the internal context, is that what you > wanted? > > >>> If I reverse the situation it gets a little better. Asterisk doesn't >>> use 100% of the CPU, but until SIP/exten-20 answers, the manager >>> interface doesn't respond. So I can't hangup the line using the >>> manager >>> API if SIP/exten-20 doesn't answer. SIP/exten-20 is a SPA3102 FXS. >>> Here is that example: >>> >>> Action: Originate >>> Channel: SIP/exten-20 >>> Context: internal >>> Extension: 0 >>> Priority: 1 >>> >> >> The reason Manager doesn't respond is that it's waiting for a result >> code to >> give you. If you don't care, use the "Async: yes" option to the >> Originate >> action to get AMI to continue past that point.