Hi Daniel,
Yes, they are.
At this point I using only one redis key space for both rtpengines. I just fire it up on the backup machine so it reads the RTP sessions from redis.
Both rtpengines had the same configuration. Only one is active.
But I found the nice redis key space separated and active / active - multiple rtpengine feature for it. Not implemented this at the moment.
Am 05.01.2018 8:49 vorm. schrieb "Daniel-Constantin Mierla" < miconda@gmail.com>:
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:
- Plain RTP: just stocks a few seconds and flows. Everything fine.
- 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:
- unencrypted call
- TLS/SDES encrypted call
- DTÖS WebRTC encrypted call
-- Kind Regards *Karsten Horsmann*
Kamailio (SER) - Users Mailing Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com