Hi Michael,
I wouldn't say the messages are not important, they can reveal broken
signaling.
As per the message, the To-tag of the ACK does not match what the dialog
learned from 200 OK. I would advise you to double check that via a SIP
capture of the traffic.
Regards,
Bogdan-Andrei
Let me try 0.
On Tue, Apr 14, 2020, 7:56 PM David Villasmil <
david.villasmil.w...@gmail.com> wrote:
> Have you tried with 1 or 0?
> Regards,
>
> David Villasmil
> email: david.villasmil.w...@gmail.com
> phone: +34669448337
>
>
> On Wed, Apr 15, 2020 at 12:09 AM Saint Michael wrote:
>
>> what
Have you tried with 1 or 0?
Regards,
David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
On Wed, Apr 15, 2020 at 12:09 AM Saint Michael wrote:
> what is the lowest debug level that is safe to use?
>
>
> On Tue, Apr 14, 2020 at 6:59 PM David Villasmil <
>
what is the lowest debug level that is safe to use?
On Tue, Apr 14, 2020 at 6:59 PM David Villasmil <
david.villasmil.w...@gmail.com> wrote:
> Maybe lower the debug?
>
> On Tue, 14 Apr 2020 at 23:00, Saint Michael wrote:
>
>> I see thousands of the messages below. If they are not important,
Maybe lower the debug?
On Tue, 14 Apr 2020 at 23:00, Saint Michael wrote:
> I see thousands of the messages below. If they are not important, how do I
> hide them
> ARNING:dialog:dlg_onroute: tight matching failed for ACK with
> callid='5063212c34ac27e23d25ea143ca8bf4f@64.140.166.100:5060'/52,
I see thousands of the messages below. If they are not important, how do I
hide them
ARNING:dialog:dlg_onroute: tight matching failed for ACK with
callid='5063212c34ac27e23d25ea143ca8bf4f@64.140.166.100:5060'/52,
ftag='as480e6ada'/10, ttag='8e2e-a7407c352db2ab880c67b8cc744fbbfe'/37 and
direction=1
