[OpenSIPS-Users] two opensips using one location table

Bogdan-Andrei Iancu bogdan at voice-system.ro
Thu Jun 3 10:27:17 CEST 2010


Jeff Pyle wrote:
> Hi Bogdan,
>
> On Jun 2, 2010, at 11:22 AM, Bogdan-Andrei Iancu wrote:
>
>   
>> Hi Jeff,
>>
>> Jeff Pyle wrote:
>>     
>>> Hello,
>>>
>>> There was a post a little while back where the goal was to have two Opensips instances instances use one location table, but have each Opensips instance load only its own records.
>>>
>>> My application is slightly different.  I'd like either Opensips instance to load any record from any Opensips instance and use it as its own.
>>>
>>>       
>> so like multiple opensips sharing the same location content (read / 
>> write) via a single DB table ? For this use the db_mode 3 (DB_ONLY) to 
>> avoid caching.
>>     
>
> Yes, exactly.  We've run db_mode=3 from day one with excellent success.  Mysql cluster really shines here.  :)
>
>   
>>> It seems this is possible using two things:
>>>  mhomed=1
>>>  force_send_socket(<local-IP>:5060);
>>>
>>>       
>> not really - that is for opensips running on multiple IP addresses 
>> (multiple listeners) in different networks.
>>     
>
> If I don't force_send_socket() won't I see the warning about the specific socket not being available, since it belongs to the other opensips instance?  Or is there another to way to work around that?  I'd prefer not to fill up my logs with warnings that would be normal in certain modes of operation.
>   
That's an ugly and costly hack to get rid of that warning (harmless 
anyhow) - better let's move the warning to debug level, what do you say ?

Regards,
Bogdan
>
>
> - Jeff
>
>
>   
>> Regards,
>> Bogdan
>>     
>>> Is it really this simple, or am I missing something?
>>>
>>>
>>>       


-- 
Bogdan-Andrei Iancu
www.voice-system.ro




More information about the Users mailing list