So, I went ahead and printed to stderr what I was sending to asterisk, and then
I printed to stderr what I get back. You can see it on the Asterisk console of
course. We have the dial command, immediately followed by the 'Invalid
Command', and oh look... Asterisk then goes ahead and dials it anyway. Huh?
*CLI>
-- Executing AGI("SIP/3250072-c5d3",
"python/iptrouter.py|10001") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/python/iptrouter.py
EXEC "DIAL" "SIP/10000|5|tr"
510 Invalid or unknown command
-- AGI Script Executing Application: (DIAL) Options: (SIP/10000|5|tr)
-- Called 10000
-- SIP/10000-486d is ringing
-- Nobody picked up in 5000 ms
-- AGI Script python/iptrouter.py completed, returning 0
== Auto fallthrough, channel 'SIP/3250072-c5d3' status is
'NOANSWER'
-----Original Message-----
From: Douglas Garstang
Sent: Thursday, February 16, 2006 8:39 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [Asterisk-Users] Non sensical AGI Error
I'm getting an error back from an AGI Dial command. Weird thing is that
it's STILL performing the Dial.
Here's what I am sending (without the paranthesis):
(EXEC DIAL "SIP/10000|5|tr")
and here's what I am getting (without the paranthesis):
(510 Invalid or unknown command)
Why would I get this response to a seemingly good command? And why would
Asterisk go ahead and perform the dial anyway and then come back and say
it's an unknown command? Perhaps this is a bug? It's Asterisk 1.2.4.
Doug
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users