That makes sense, thanks Arsen. We're already catching it then we just sl_reply_error() - I'll add some special handling for this scenario

Thanks again

On Wed, Oct 20, 2021 at 12:58 PM Arsen Semenov <arsperger@gmail.com> wrote:
Hi,

Yes, you can handle return codes from t_relay(). It should return -1 in case of network failure.

On Wed, 20 Oct 2021 at 4:39 PM, Marrold <kamailio@marrold.co.uk> wrote:
Hi all,

Is there any way of catching these errors before sending a 500 No error (2/SL) ?

Thanks

On Tue, Oct 5, 2021 at 5:01 PM Marrold <kamailio@marrold.co.uk> wrote:
Hi Arsen

That looks perfect, except we're still using 4.3.X on some of our proxies ( I should have mentioned, sorry) . We plan on upgrading very soon...

Thanks


On Tue, Oct 5, 2021 at 4:58 PM Arsen Semenov <arsperger@gmail.com> wrote:

On Tue, Oct 5, 2021 at 8:49 PM Marrold <kamailio@marrold.co.uk> wrote:
Hi,

We're currently implementing WebRTC (SIP over a websocket) on our Kamailio proxies and we're experiencing a minor issue after a restart.

We write all USRLOC entries to a shared database to implement HA. These are then loaded on a restart, which leaves us with entries with TCP connections that no longer exist. When a call attempt is made the proxy can't find the connection ID and immediately rejects the call with a "500 No error (2/SL)" -

Oct  5 15:38:24 proxy-01 /sbin/kamailio[32087]: WARNING: <core> [core/msg_translator.c:2861]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found
Oct  5 15:38:24 proxy-01 /sbin/kamailio[32087]: ERROR: <core> [core/msg_translator.c:2038]: build_req_buf_from_sip_req(): could not create Via header
Oct  5 15:38:24 proxy-01 /sbin/kamailio[32087]: ERROR: tm [t_fwd.c:479]: prepare_new_uac(): could not build request
Oct  5 15:38:24 proxy-01 /sbin/kamailio[32087]: ERROR: tm [t_fwd.c:1759]: t_forward_nonack(): failure to add branches
Oct  5 15:38:24 proxy-01 /sbin/kamailio[32087]: ERROR: sl [sl_funcs.c:414]: sl_reply_error(): stateless error reply used: No error (2/SL)

How can we catch this error to avoid terminating the call prematurely? Or should we flush these TCP connections on start up?

Thanks
Matthew

__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
  * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


--
Arsen Semenov

__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
  * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
  * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Sent from Gmail Mobile
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
  * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users