Hello,
it appears that 100 trying is attempted to be sent after a 503 -- so the
dialog doesn't exist because it was not initiated completely. Can you
check the network sip traffic for such case?
Cheers,
Daniel
On 10/11/15 21:22, Ryan Brindley wrote:
> Hey community,
>
> Our current switch is bei
Hey community,
Our current switch is being overloaded and when it does we're getting these
2 messages spammed in our logs:
WARNING: dialog [dlg_handlers.c:1127]: dlg_onroute(): unable to find dialog
for ACK with route param '35d.d2f1' [3411:7981]
ERROR: tm [t_reply.c:1341]: t_should_relay_respon
Hi,
here is the trace of the end of the call. 486 is recieved from the
destination, kamailio sends ACK to it. then kamailio sends the 486 to the
origination and recieves an ACK for it. (the scenario is behind the
companies gateway)
*No. TimeSourceDestination
Hey,
Am 23.01.2012 um 11:13 schrieb Uri Shacked:
> i use the dialog module.
> i create the dialog using dlg_manage() right after the invite is recieved.
> in a case where the final destination rejects the call (486 busy), i get the
> following error:
> " WARNING: dialog [dlg_handlers.c:1054]: un
Hi,
i use the dialog module.
i create the dialog using dlg_manage() right after the invite is recieved.
in a case where the final destination rejects the call (486 busy), i get
the following error:
" WARNING: dialog [dlg_handlers.c:1054]: unable to find dialog for ACK with
route param."
i gues
