Hi all!
Can I create dialog structures via dmq?
for example, two K. share IP via carp. Active K. (carp master) process calls, create dialogs and send it to slave. When master die, slave became master and has complete info 'bout registered clients and dialogs.
-- WBR, Victor JID: coyote@bks.tv JID: coyote@bryansktel.ru I use FREE operation system: 3.10.19-calculate GNU/Linux
Hi,
On 9 Dec 2013 07:45, "Victor V. Kustov" coyote@bks.tv wrote:
Hi all!
Can I create dialog structures via dmq?
Not yet, but it is work in progress and will be possible soon.
for example, two K. share IP via carp. Active K. (carp master) process calls, create dialogs and send it to slave. When master die, slave became master and has complete info 'bout registered clients and dialogs.
Registrations are a different matter. Replication can be achieved already by sharing a database or using function such as t_replicate().
Regards, Charles
Hi, Charles!
Not yet, but it is work in progress and will be possible soon.
In dialog module no functions to create/destroy dialogs, they described and used in tm module. Do you plan move dialog creation/destroying funcs in dialog module? I think it will more usable for replication: use same functions for create dialog in tm module (when real sip dispatch) and for create "fake" dialog in dmq(??) for replicate...
for example, two K. share IP via carp. Active K. (carp master) process calls, create dialogs and send it to slave. When master die, slave became master and has complete info 'bout registered clients and dialogs.
Registrations are a different matter. Replication can be achieved already by sharing a database or using function such as t_replicate().
How i may realise it?
Master:
... if (is_method(REGISTER)) {
t_replicate('sip:slave:6077'); // will here udp used?
// kk, usual dispatch
... }
Client will register twice in such case?
-- WBR, Victor JID: coyote@bks.tv JID: coyote@bryansktel.ru I use FREE operation system: 3.10.19-calculate GNU/Linux
Hi,
In dialog module no functions to create/destroy dialogs, they described and used in tm module. Do you plan move dialog creation/destroying funcs in dialog module? I think it will more usable for replication: use same functions for create dialog in tm module (when real sip dispatch) and for create "fake" dialog in dmq(??) for replicate...
To which functions are you referring? There is a difference between dialogs and transactions.
Registrations are a different matter. Replication can be achieved already by sharing a database or using function such as t_replicate().
How i may realise it?
Something like:
if (save("location")) { t_replicate("slave"); }
Client will register twice in such case?
Why? On slave, if register comes from master, use save_noreply("location"). The client only knows of the master.
Regards, Charles
Hi,
To which functions are you referring?
new_dlg_*
Something like:
if (save("location")) { t_replicate("slave"); }
Heh, I hoped something like
dmq_send('slave','save_noreply("location")'); dmq_send('slave','new_dlg_uac("param","param","pamparam")');
Why? On slave, if register comes from master, use save_noreply("location"). The client only knows of the master.
ok.
-- WBR, Victor JID: coyote@bks.tv JID: coyote@bryansktel.ru I use FREE operation system: 3.10.19-calculate GNU/Linux
-
Charles Chance -
Victor V. Kustov