Recovering TLS calls after crash

Status
Not open for further replies.

mintos5

New Member
Aug 7, 2018
3
0
1
30
Slovakia
Hello,
Is here somebody who has experiences with recovering calls after freeswitch crash?
I am following this article: https://freeswitch.org/confluence/display/FREESWITCH/High+Availability
and I am testing on 1 server with this configuration change:
<param name="track-calls" value="true"/> in SIP_PROFILE

I tried this commands after establishing call:
fs_cli -x 'fsctl crash' fs_cli -x 'sofia recover'
Everything works like it should without tls encryption.

BUT

When I export this channel variable (rtp_secure_dialplan) in dialplan like this:
<action application="export" data="rtp_secure_media=optional"/>
the call is now using tls, but I can not recover calls after crashing freeswitch.
The call hangs up like this:
[NOTICE] sofia.c:8273 Hangup sofia/internal/500@192.168.30.41:5061 [CS_RESET] [NORMAL_TEMPORARY_FAILURE]

All help is welcome
 

DigitalDaz

Administrator
Staff member
Sep 29, 2016
3,077
579
113
I'm pretty sure it won't work with TLS because its connection orientated, I would imagine you would have the same problem with TCP too.
 

markjcrane

Active Member
Staff member
Jul 22, 2018
536
185
43
50
Recover calls only works with UDP and TLS uses TCP. TCP realizes the connection is gone and ends the call. If TLS were to use UDP it would be easier to do man in the middle attacks which is why TLS uses TCP. Both SIP UDP and TCP have pros and cons you just found a major one for UDP.
 

mintos5

New Member
Aug 7, 2018
3
0
1
30
Slovakia
Ok, I tested only TCP connection without TLS and the result is same: I can not recover calls.

Thank You for your help. Now I know it will be working just with UDP...
 
Status
Not open for further replies.