[SR-Users] kamailio-5.0.5 active/passive pcs/cluster with rtpengine - how to fix calls after failover

Daniel-Constantin Mierla miconda at gmail.com
Fri Jan 5 08:49:05 CET 2018


Hello,

are kamailio and rtpenigine on same system?

Cheers,
Daniel


On 04.01.18 12:21, Karsten Horsmann wrote:
> Hello List,
>
> and also an happy new year to everyone.
>
> I use CentOS 7.4.x with kamailio 5.0.5 and rtpengine on a
> pacemaker/corosync cluster
> in front of an internal kamailio siprouter and media-services.
>
> If i did an "pcs node standby" to failover my frontend-kamailio
> (udp/tcp 5060, udp/tcp 5061-tls and tcp websocket-secure) i noticed
> the following scenarios:
>
> 1) Plain RTP: just stocks a few seconds and flows. Everything fine.
> 2) SDES/RTP: silence - but REINVITE manually in my client brings audio
> back. Need improvement.
> 3) DTLS/RTP WebRTC: silence - all clients shows an active call. I know
> that there is NO way to recover this call - because of the temporay
> DTLS certificate due the rtpengine start-up.
>
>
> So i thought - for scenario1) i dont need anything to do. Works nice.
> For scenario2) i need something to "remember its SDES/RTP calls and
> send them an REINVITE"
> And for scenario3) i should just hangup all WebRTC calls - IMHO the
> best for that.
>
> How can i fire-up these tasks to get an "clean-up" or "reinvite" after
> an failover?
>
>
> scenario legend:
> 1) unencrypted call
> 2) TLS/SDES encrypted call
> 3) DTÖS WebRTC encrypted call
>
> -- 
> Kind Regards
> *Karsten Horsmann*
>
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20180105/5bf57b6a/attachment.html>


More information about the sr-users mailing list