[OpenSIPS-Users] Sometime opensips sends 477 reply for BYE packet in TLS

[Bogdan-Andrei Iancu]

Hi,

477 is an intern error meaning some transport level err happened - like 
in your case, OpenSIPS did not find and was not able to open a new TLS 
connection back to softphone.

Probably some times, depending on the call duration, the TLS conn is 
still up and the BYE is routed.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 16.02.2024 14:41, Vinayak Makwana via Users wrote:
>
> Hello all,
> I am facing an issue when opensips gets BYE from the freeswitch side. 
> At that time, opensips sent 477 reply to the BYE request.
>
> Here's the call scenario : when we dial the call from softphone to 
> opensips, it's TLS call flow, and from opensips to Freeswitch, it's 
> UDP call flow. So when we disconnect a call from Softphone at that 
> time, the call disconnects properly, but when we disconnect a call 
> from FreeSwitch at that time, opensips sends 477 sending failed to 
> Freeswitch. but sometimes OpenSIP sends 200 OK successfully to 
> Freeswitch, and calls get disconnected also.
>
> *opensips logs at the time of 477 reply send:*
>  ERROR:core:tcp_connect_blocking_timeout: connect timed out, 99171 us 
> elapsed out of 100000 us
>  ERROR:core:tcp_sync_connect_fd: tcp_blocking_connect failed
>  ERROR:proto_tls:proto_tls_send: connect failed
>  ERROR:tm:msg_send: send() to a.b.c.d:53722 for proto tls/3 failed
>  ERROR:tm:t_forward_nonack: sending request failed
>  DBG:tm:t_relay_to: t_forward_nonack returned error
>  DBG:sl:sl_reply_error: error text is Send failed (477/SL)
>
> Please suggest if anything needs to be configured on the opensips side.
>
> --
> Regards,
> *Vinayak Makwana
> *
>
>
> *Disclaimer*
> In addition to generic Disclaimer which you have agreed on our 
> website, any views or opinions presented in this email are solely 
> those of the originator and do not necessarily represent those of the 
> Company or its sister concerns. Any liability (in negligence, contract 
> or otherwise) arising from any third party taking any action, or 
> refraining from taking any action on the basis of any of the 
> information contained in this email is hereby excluded.
>
> *Confidentiality*
> This communication (including any attachment/s) is intended only for 
> the use of the addressee(s) and contains information that is 
> PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, 
> distribution, or copying of this communication is prohibited. Please 
> inform originator if you have received it in error.
>
> *Caution for viruses, malware etc.*
> This communication, including any attachments, may not be free of 
> viruses, trojans, similar or new contaminants/malware, interceptions 
> or interference, and may not be compatible with your systems. You 
> shall carry out virus/malware scanning on your own before opening any 
> attachment to this e-mail. The sender of this e-mail and Company 
> including its sister concerns shall not be liable for any damage that 
> may incur to you as a result of viruses, incompleteness of this 
> message, a delay in receipt of this message or any other computer 
> problems.
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240216/be54008f/attachment.html>