Re: [OpenSIPS-Users] Dialog replication problems

Hello, I backported the commit 00be97f151d254af281c4f05611c1905f51fbcde ("dialog: Fix incorrect replicated dialog ids") from git in an Opensips 2.2.2. opensipsctl fifo dlg_list show the same dialogs on both sides, but after fail-over the BYE is not routed (no problem if no fail-over). My

Re: [OpenSIPS-Users] Dialog replication problems

Thanks for the quick test! Will have it pushed upstream today. Transparent CDR generation for the replicated dialogs is currently not working. For that to work, the two nodes would need to _accurately_ share state (i.e. "who is the primary?"), otherwise double CDR/billing situations could

Re: [OpenSIPS-Users] Dialog replication problems

Hi Liviu, Yes - big difference with the patch : active server: dialog:: hash=3426:1456403041 dialog_id=14716014359137 state:: 4 user_flags:: 0 timestart:: 1478170024 datestart:: 2016-11-03 11:47:04 timeout:: 1478191625 dateout:: 2016-11-03 17:47:05 callid::

Re: [OpenSIPS-Users] Dialog replication problems

Hi, Dawid! I have looked into the problem and also managed to come up with a fix! Could you please go to your OpenSIPS 2.2 source code directory, apply the below patch, recompile the dialog module and see if it fixes the problem? git apply <(base64 -d

Re: [OpenSIPS-Users] Dialog replication problems

Anyone ? I have just upgraded to the latest 2.2 version form GIT and am still experiencing this. active server: dialog:: hash=*2297:947327686* dialog_id=9866487206598 state:: 4 user_flags:: 0 timestart:: 1478162278 datestart:: 2016-11-03 09:37:58 timeout:: 1478183878 dateout:: 2016-11-03

[OpenSIPS-Users] Dialog replication problems

Hi All, I have a reduntant OpenSIPS 2.2.1 setup with clusterer, binary interface replication and a floating IP. I am encountering a few niuances and am wondering if I am doing something wrong or if there is a bug. 1) Replicated dialog hash id is different on the standby server from the active