I would recommend two things. Number one would be to tweak your logger.conf to separate out error messages. Number two would be to make your ami call do this:
Set sip debug on Ami action Set sip debug off This lets you get what you need without making a huge log file. From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Wen Li Sent: Tuesday, November 06, 2012 4:48 PM To: asterisk-users@lists.digium.com Subject: [asterisk-users] How to determine if AMI MessageSend succeeded? I am using Asterisk 11.0.0 and have a SIP user called 100. The user registers via SIP but their network connection is cut off. I then proceed to use AMI to send a message to them. root@yumyum:~# telnet 127.0.0.1 5038 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. Asterisk Call Manager/1.3 Action: Login Username: admin Secret: test Response: Success Message: Authentication accepted Event: FullyBooted Privilege: system,all Status: Fully Booted Action: MessageSend To: sip:100 From: Test <sip:101@192.168.88.1 <mailto:sip%3A101@192.168.88.1> > Body: This is a test. Response: Success Message: Message successfully sent However, clearly the message is not sent since the device lost its network connection. How can I know that it failed? Even the log does not appear to show anything unless I turn sip debug on.
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
