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?
Tilghman Lesher wrote: > On Friday 25 April 2008 15:23:05 Chris Elliott wrote: > >> 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. > > -- Thank you and have any kind of day you want, Anthony Francis Rockynet VOIP _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users