I think for this action there's no relevant asterisk output information.
Astmaproxydebug: with unique
Astprox2: autofilter off
Outputs:
Astmaproxydebug:
Asterisk Call Manager Proxy/1.24pre090526
ActionID: 1
Response: Success
Message: Authentication accepted
Astprox2:
Asterisk Call Manager Proxy/1.24pre090526
ActionID: 1
Response: Success
Message: Authentication accepted
Response: Success
ActionID: Autoflot
Message: Queue summary will follow
Server: localhost
As you said (app_queue.c):
astman_append(s, "Event: QueueSummary\r\n"
"Queue: %s\r\n"
"LoggedIn: %d\r\n"
"Available: %d\r\n"
"Callers: %d\r\n"
"HoldTime: %d\r\n"
"TalkTime: %d\r\n"
"LongestHoldTime: %d\r\n"
"%s"
"\r\n",
q->name, qmemcount, qmemavail, qchancount,
q->holdtime, q->talktime, qlongestholdtime, idText);
}
Lacks of the actionid, do you think this is the problem?
Regards!
-----Mensaje original-----
De: astmanproxy@googlegroups.com [mailto:astmanproxy@googlegroups.com] En
nombre de Steve Davies
Enviado el: viernes, 23 de abril de 2010 13:48
Para: astmanproxy@googlegroups.com
Asunto: Re: filters
The patch does cover some incorrectly filtered packets, but I do not
think it is related to the issue you describe (of course it may be!)
Perhaps run astmanproxy in "-dddd" debug mode, and send me a copy of
the trace? If you also send a copy of the asterisk output, and then a
copy of the astmanproxy output (all for a single transaction so they
can be matched up.
Can you confirm that ALL of the returned AMP packets have an ActionID
on them when they come from Asterisk? A couple of commands were broken
and failed to put ActionID on all packets in 1.6.2.6
Regards,
Steve
On 23 April 2010 17:35, Sebastian <scg...@gmail.com> wrote:
> I'm using the last one I think.
> What is the new patch for?
> If I set autofilter=unique I don't even have the Response, if I put an
> actionid or not, has no difference with this option set.
> Any idea?
> Thanks!
> -----Mensaje original-----
> De: astmanproxy@googlegroups.com [mailto:astmanproxy@googlegroups.com] En
> nombre de Steve Davies
> Enviado el: viernes, 23 de abril de 2010 13:16
> Para: astmanproxy@googlegroups.com
> Asunto: Re: filters
> On 23 April 2010 16:09, Sebastian <scg...@gmail.com> wrote:
>> Steve,
>> I think there is a small issue with the filters but I'm not sure, for
>> example I have a filter for example SIP/1001, and I get only the events
> that
>> correspond to it OK, but for example I would like to do like this that
>> should work (I think), example: send Action QueueStatus with an actionid
> so
>> I can have the response, but I only have the response and not the Events
>> that follow, even when debugging I can see they all have the actionid
>> correctly, but they are filtered.
>> As an ugly workaround I hardcoded a unique id that I want to pass always
> but
>> this method is nasty, maybe you can point me where to start, I think has
>> something to do with the add to stack, but I couldn't figure out exactly.
>> Any idea?
> Hello again - I guess I can assume you are using my latest version from
GIT?
> There was one small patch recently, though I do not think it will
> affect your particular issue. I will push it to GIT.
> What have you set "autofilter" to in the astmanproxy configuration? If
> you are not already doing so, can I suggest you try
> "autofilter=unique" as this gives each client connection its own
> unique actionID prefix, and solves the problem that astmanproxy only
> remembers one actionID at a time - As soon as the 2nd ActionID is
> seen, the old one is forgotten, causing packets to be blocked.
> Regards,
> Steve
> --
> You received this message because you are subscribed to the Google Groups
> "Astmanproxy" group.
> To post to this group, send email to astmanproxy@googlegroups.com.
> To unsubscribe from this group, send email to
> astmanproxy+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/astmanproxy?hl=en.
> Se certificó que el correo entrante no contiene virus.
> Comprobada por AVG - www.avg.es
> Versión: 9.0.814 / Base de datos de virus: 271.1.1/2829 - Fecha de la
> versión: 04/23/10 03:31:00
> --
> You received this message because you are subscribed to the Google Groups
"Astmanproxy" group.
> To post to this group, send email to astmanproxy@googlegroups.com.
> To unsubscribe from this group, send email to
astmanproxy+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/astmanproxy?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Astmanproxy" group.
To post to this group, send email to astmanproxy@googlegroups.com.
To unsubscribe from this group, send email to
astmanproxy+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/astmanproxy?hl=en.
Se certificó que el correo entrante no contiene virus.
Comprobada por AVG - www.avg.es
Versión: 9.0.814 / Base de datos de virus: 271.1.1/2829 - Fecha de la
versión: 04/23/10 03:31:00
--
You received this message because you are subscribed to the Google Groups "Astmanproxy" group.
To post to this group, send email to astmanproxy@googlegroups.com.
To unsubscribe from this group, send email to astmanproxy+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/astmanproxy?hl=en.
