Re: [asterisk-users] Re: What's up with the Manager Interface?!?!
Steve Murphy wrote: *snipped I've been fixing manager bugs here and there, and am willing to take on any manager issues out there, for 1.4, and trunk, especially, so as to have things nice and solid for 1.4 before it gets out of beta. *snipped Richard-- I'll lab up 1.4 and see if I can get the hiccups you mention. *snipped given the differences between the 1.2 and 1.4 manager interfaces, i am not sure how much this will help... i just modified my application to tail the last 20 lines of asterisk debug (verbose 3), asterisk messages, and my applications debug log to another log. (at one site) this *should* make it a little easier for me to track down the 'hiccup' issue. ___ --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
[asterisk-users] Re: What's up with the Manager Interface?!?!
Doug, Everyone: I'll make you an offer you (hopefully) can't refuse: I've been fixing manager bugs here and there, and am willing to take on any manager issues out there, for 1.4, and trunk, especially, so as to have things nice and solid for 1.4 before it gets out of beta. So, give me some details. I will file the bug, if you don't. I will reproduce(if I can), and debug, and fix 'em. Just tell me (as explicitly as possible, please!) what the problems are-- especially you, Doug-- where are those inconsistencies, exactly? Richard-- I'll lab up 1.4 and see if I can get the hiccups you mention. murf Douglas Garstang wrote: The Asterisk Manager Interface is driving me nuts. Whoever wrote it should be drawn and quartered. Sometimes the data comes back separated by \r\n, and sometimes it's separated by \n. The whole thing is completely inconsistent, and trying to write any kind of API for it is -GHASTLY- And, Richard Lyman wrote: just wait till you get a 'hiccup' that causes a line to get cut off, drop a char, and continue on next line. G (examples below) this is an older manager.c there have been a lot of mods to the manager interface in the 1.4 tree, but there is no way i would put that into a production envir. - Event: OriginateFailure Privilege: call,all Channel: Zap/g1/xx Context: gdincoming Exten: Reason: 3 Uniqueid: null CallerID: xx CallerIDName: ~308C D13-47426-true~ - Event: OriginateFailure Privilege: call,all Channel: Zap/g1/xx Context: gdincoming Exten: Reason: 5 (rest was gone) - Event: OriginateFailure Privilege: call,all Channel: Zap/g1/xx Context: gdincoming Exten: Reason: 0 Uniqueid: null CallerID: xx Ca lerIDName: ~308CLD14-40566-true~ - Event: OriginateSuccess Privilege: call,all Channel: Zap/g1/xx Context: gdincoming Exten: Reaso : 4 Uniqueid: 1163128185.2006 CallerID: xx CallerIDName: ~308CLD13-50454-true~ -- Steve Murphy Software Developer Digium smime.p7s Description: S/MIME cryptographic signature ___ --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
RE: [asterisk-users] Re: What's up with the Manager Interface?!?!
Hi Steve. Thanks, but unfortunately, I can't be involved in that. We are running Asterisk in a production environment and we're using 1.2, not 1.4. I don't have the resources to work with 1.4. Last time I filed a bug against 1.2 I got told off. Here's an example of that cruddy output. hestia*CLI dundi show peer 00:0e:0c:a1:92:4d Peer:00:0e:0c:a1:92:4d Model: Symmetric Host:xxx.187.142.203 Dynamic: no KeyPend: no Reg: No In Key: dundikey Out Key: dundikey Include logic: -- include all Query logic: -- permit all hestia*CLI The delimiter should not be the colon, as the data may also contain a colon (in this case the MAC address). That makes it really difficult to split the data into fields. Also, the apparent key:value rule gets broken when you get down to the Include Logic line. The '--include all' should be on the same line! Just about every single Asterisk command has screwed up output like this. Fixing all this would be a LOT of work. Doug. -Original Message- From: Steve Murphy [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 4:26 PM To: asterisk-users@lists.digium.com Subject: [asterisk-users] Re: What's up with the Manager Interface?!?! Doug, Everyone: I'll make you an offer you (hopefully) can't refuse: I've been fixing manager bugs here and there, and am willing to take on any manager issues out there, for 1.4, and trunk, especially, so as to have things nice and solid for 1.4 before it gets out of beta. So, give me some details. I will file the bug, if you don't. I will reproduce(if I can), and debug, and fix 'em. Just tell me (as explicitly as possible, please!) what the problems are-- especially you, Doug-- where are those inconsistencies, exactly? Richard-- I'll lab up 1.4 and see if I can get the hiccups you mention. murf Douglas Garstang wrote: The Asterisk Manager Interface is driving me nuts. Whoever wrote it should be drawn and quartered. Sometimes the data comes back separated by \r\n, and sometimes it's separated by \n. The whole thing is completely inconsistent, and trying to write any kind of API for it is -GHASTLY- And, Richard Lyman wrote: just wait till you get a 'hiccup' that causes a line to get cut off, drop a char, and continue on next line. G (examples below) this is an older manager.c there have been a lot of mods to the manager interface in the 1.4 tree, but there is no way i would put that into a production envir. - Event: OriginateFailure Privilege: call,all Channel: Zap/g1/xx Context: gdincoming Exten: Reason: 3 Uniqueid: null CallerID: xx CallerIDName: ~308C D13-47426-true~ - Event: OriginateFailure Privilege: call,all Channel: Zap/g1/xx Context: gdincoming Exten: Reason: 5 (rest was gone) - Event: OriginateFailure Privilege: call,all Channel: Zap/g1/xx Context: gdincoming Exten: Reason: 0 Uniqueid: null CallerID: xx Ca lerIDName: ~308CLD14-40566-true~ - Event: OriginateSuccess Privilege: call,all Channel: Zap/g1/xx Context: gdincoming Exten: Reaso : 4 Uniqueid: 1163128185.2006 CallerID: xx CallerIDName: ~308CLD13-50454-true~ -- Steve Murphy Software Developer Digium ___ --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
[asterisk-users] Re: What's up with the Manager Interface?!?!
In article [EMAIL PROTECTED], Richard Lyman [EMAIL PROTECTED] wrote: just wait till you get a 'hiccup' that causes a line to get cut off, drop a char, and continue on next line. G (examples below) I've made heavy use of the Manager interface for over 2 years now, and have never seen the kind of behaviour you described and showed examples of. I would be more inclined to suspect the functions you are using to read and collect the AMI output. Perhaps there's a buffer boundary error or something. Cheers Tony -- Tony Mountifield Work: [EMAIL PROTECTED] - http://www.softins.co.uk Play: [EMAIL PROTECTED] - http://tony.mountifield.org ___ --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
Re: [asterisk-users] Re: What's up with the Manager Interface?!?!
Tony Mountifield wrote: In article [EMAIL PROTECTED], Richard Lyman [EMAIL PROTECTED] wrote: just wait till you get a 'hiccup' that causes a line to get cut off, drop a char, and continue on next line. G (examples below) I've made heavy use of the Manager interface for over 2 years now, and have never seen the kind of behaviour you described and showed examples of. I would be more inclined to suspect the functions you are using to read and collect the AMI output. Perhaps there's a buffer boundary error or something. Cheers Tony perhaps. not sure what your heavy use is, but mine i feel is rather heavy. an example would be for the time between the following timestamps 2006-11-27 10:42:24 through 2006-11-27 20:48:18 (just a tad over 10 hours) my asterisk debug file recorded 394234 lines of output (verbose 3) my applications log file has 25647 lines of those 25647 lines, 2/3's of those were generated from parsing manager output so a guestimate would be 16927 events were parsed (that is just the ones i wanted to parse) in all, for that time frame i only had 10 of those 'hiccups' if i have more time this week i will take another peek at tracking it down. ___ --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
