<br><br><div class="gmail_quote">2010/4/22 Chris Maciejewski <span dir="ltr"><<a href="mailto:chris@wima.co.uk">chris@wima.co.uk</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi,<br>
<br>
I made a diagram showing what I am trying to achieve:<br>
<br>
<a href="http://wima.co.uk/2x_opensips.pdf" target="_blank">http://wima.co.uk/2x_opensips.pdf</a><br>
<br>
Is this possible at all?<br>
Can we make two OpenSIPs share the same 'location' table, yet each<br>
dealing only with it's "own" contacts?<br>
<br>
Regards,<br>
<font color="#888888">Chris<br>
</font><div><div></div><div class="h5"><br>
<br>
On 22 April 2010 18:47, Brett Nemeroff <<a href="mailto:brett@nemeroff.com">brett@nemeroff.com</a>> wrote:<br>
> Just a quick question here.. can some of this be taken care of with a<br>
> t_replicate for the register?<br>
><br>
> Just a thought..<br>
> -Brett<br>
><br>
><br>
> On Thu, Apr 22, 2010 at 12:36 PM, Chris Maciejewski <<a href="mailto:chris@wima.co.uk">chris@wima.co.uk</a>> wrote:<br>
>> On 22 April 2010 18:11, Bogdan-Andrei Iancu <<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>> wrote:<br>
>>> Chris Maciejewski wrote:<br>
>>>> On 22 April 2010 18:00, Bogdan-Andrei Iancu <<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>> wrote:<br>
>>>><br>
>>>>> Hi Chris,<br>
>>>>><br>
>>>>> running 2 opensips with different IPs ? because opensips saves in<br>
>>>>> location table its own socket (where the REGISTER was received), and if<br>
>>>>> the other server will try to use it, it will not recognize this socket<br>
>>>>> (as it is a different IP).<br>
>>>>><br>
>>>>> Before going further, note that multiple opensips sharing the same<br>
>>>>> location table has some flows (due how SIP works) - like if you are<br>
>>>>> using multiple interfaces, of different port ; also NAT traversal will<br>
>>>>> not work.<br>
>>>>><br>
>>>>> In the end, if you do not have NAT and using a single interface, you can<br>
>>>>> simply ignore those warnings.<br>
>>>>><br>
>>>>> Regards,<br>
>>>>> Bogdan<br>
>>>>><br>
>>>>><br>
>>>><br>
>>>> Hi Bogdan,<br>
>>>><br>
>>>> Thanks for clarification. I am aware due to NAT traversal etc.<br>
>>>> multiple SIP registrar servers sharing the same location table will<br>
>>>> not work.<br>
>>>><br>
>>>> I was just worried this WARNINGs might have some negative impact, but<br>
>>>> in that case I will just ignore them.<br>
>>>><br>
>>> If opensips finds a non-local socket in a usrloc records, it will fire<br>
>>> the warning and use one of its own sockets for dealing with that contact.<br>
>>><br>
>>> Regards,<br>
>>> Bogdan<br>
>>><br>
>><br>
>> Ah, I see now.<br>
>><br>
>> When UA1 registered at Proxy1 only, Nathelper OPTIONs are sent from<br>
>> both Proxy1 and Proxy2. This is not what I wanted :(<br>
>><br>
>> Is there any way to make Proxy2 completely ignore UA1?<br>
>><br>
>> Regards,<br>
>> Chris<br>
>><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br><a href="http://lists.opensips.org/pipermail/users/2008-November/001729.html">http://lists.opensips.org/pipermail/users/2008-November/001729.html</a><br><br>It can be a starting point.<br>
<br>-Laszlo<br><br><br><div style="visibility: hidden; display: inline;" id="avg_ls_inline_popup"></div><style type="text/css">#avg_ls_inline_popup { position:absolute; z-index:9999; padding: 0px 0px; margin-left: 0px; margin-top: 0px; width: 240px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 13px;}</style>