[OpenSIPS-Users] dialog: send BYE from another opensips instance

[samuel]

Hi Flavio,

I've checked but, as far as I know, this feature only allows to distribute
the profiles, not the data of the dialog themselves.
Doing some tests, I have 2 instances of opensips sharing the same
database.  I've also set the timeout to a low value and make several calls.
Stopping an opensips instance while calls are on, only the calls of the
active opensips instance are stopped. The calls that went through the
stopped opensips instance are still on the database and are not stopped. As
soon as the stopped opensips is started again, it checks the dialog table
and finds the expired dialogs. Immediately it sends the BYE to both
endpoints.

I had not yet time to check deeper in the code but it looks like each
opensips instances "owns" some dialogs (I think is related to the hash
identifiers). I guess that using the same "seed" could create conflict
while saving the dialog data in the database so I don't know whether
there's an option for several opensips instance to trully share the dialog
table.

Thank you in advance,
Samuel.

El 09/01/2013 10:17, "Flavio Goncalves" <flavio at asteriskguide.com> va
escriure:

> Hi Samuel,
>
> I suggest you investigate the new feature called distributed dialog
> profiles
> http://lists.opensips.org/pipermail/users/2012-February/020657.html
>
> Flavio E. Goncalves
> www.sippulse.com
>
>
>
> 2013/1/7 samuel <samu60 at gmail.com>
>
>> Hi folks,
>>
>> I'm started reading about dialog module and how to use it in a
>> distributed environment. I've read about the 'B' flag and how it can be
>> used to send BYEs to the end-points. My question is whether, using db_mode
>> REALTIME, another instance of opensips can use the information stored in
>> the database to send the BYE to a dialog created in another opensips
>> instance.
>>
>> The scenario is the next one:
>> 1.several opensips sharing the database and one of them receives an
>> INVITE.
>> 2.It creates the dialog and sets the B flag. The parameter timeout is
>> then set to the corresponding value.
>> 3.Another opensips uses the information from the dialog table to send the
>> BYE either forced by an external t_dlg command or reading from the database
>> (I guess the period can be controlled with the db_update_period parameter).
>>
>> Is this possible with the current version?
>>
>> Thank you very much in advance and congratulations,
>> Samuel.
>>
>>
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20130109/1905b672/attachment.htm>