[OpenSIPS-Users] Interaction between OpenSIPS as UAC and real UAC

[Bogdan-Andrei Iancu]

Hello,

Use the dialog based topology hiding
http://www.opensips.org/html/docs/modules/1.10.x/dialog.html#id296001

when forwarding the INVITE to Asterisk (in OpenSIPS).

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 11.02.2014 10:12, Александр Пучков wrote:
>
> 10.02.2014 13:24, Bogdan-Andrei Iancu пишет:
>> Hello,
>>
>> In this scenario:
>>
>>     Astеrisk <-- 3 -- OpenSIPS <-- 4 -- UAC
>>
>> What SIP requests the UAC is sending ? REGISTER ? INVITES ?
> Hello!
>
> UAC registered to Opensips, Opensips registered as UAC on Asterisk. 
> When the INVITE request comes from the UAC, Opensips need to sent 
> INVITE to Asterisk as UAC.
>
> Note that the UAC does not know about Asterisk and Asterisk does not 
> know about UAC. Asterisk know about only Opensips.
>
> It is necessary to any UAC registered on Opensips could imagine how 
> extension on Asterisk, without changing the configuration of UAC.
>
> Thank you.
>
>>
>>
>> Regards,
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developer
>> http://www.opensips-solutions.com
>> On 20.01.2014 13:05, Александр Пучков wrote:
>>> Hi!
>>>
>>> OpenSIPS version 1.8.
>>>
>>> We have the following diagram:
>>>
>>> PSTN        <-- 1 --> OpenSIPS    <-- 2 --> Astеrisk    <-- 3 --> UAC
>>> 192.168.1.1 <-- 1 --> 192.168.1.2 <-- 2 --> 192.168.1.3 <-- 3 --> 
>>> 192.168.1.*
>>>
>>> I would like to make the following scheme:
>>>
>>> PSTN        <-- 1 --> OpenSIPS    <-- 2 --> Astеrisk    <-- 3 --> 
>>> OpenSIPS    <-- 4 --> UAC
>>> 192.168.1.1 <-- 1 --> 192.168.1.2 <-- 2 --> 192.168.1.3 <-- 3 --> 
>>> 192.168.1.2 <-- 4 --> 192.168.1.*
>>>
>>> Interestingly the following schema fragment:
>>> Astеrisk <-- 3 --> OpenSIPS    <-- 4 --> UAC
>>>
>>> Here OpenSIPS need to increase control over the services for UAC. 
>>> UAC should not know about the existence of Asterisk and UAC must be 
>>> registered on the server OpenSIPS, and any SIP request OpenSIPS 
>>> should redirect to Asterisk.
>>>
>>> I tried to use the module in UAC_REGISTRANT OpenSIPS, it works fine 
>>> in the direction:
>>>
>>> Astеrisk -- 3 --> OpenSIPS -- 4 --> UAC
>>>
>>> But how to implement the scheme in the direction:
>>>
>>> Astеrisk <-- 3 -- OpenSIPS <-- 4 -- UAC
>>>
>>> I do not really imagine. Please tell me how it can be implemented.
>>>
>>> Thank!
>>>
>>>
>>> *Александр Пучков,
>>> Системный администратор,
>>> Тел.: +7(496) 569-24-24 доб.тел. 255;
>>> e-mail: mailex at poig.ru;
>>> *ООО "ПОИГ" (Интернет-провайдер г. Щелково)
>>> Факс: +7(496) 569-24-24 доб. 103;
>>> Адрес: 141108, М.О., г.Щелково, Пролетарский пр., д.11;
>>> WEB: http://www.schelkovo-net.ru
>>>
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
>
>
> *Александр Пучков,
> Системный администратор,
> Тел.: +7(496) 569-24-24 доб.тел. 255;
> *ООО "ПОИГ" (Интернет-провайдер г. Щелково)
> Факс: +7(496) 569-24-24 доб. 103;
> Адрес: 141108, М.О., г.Щелково, Пролетарский пр., д.11;
> WEB: http://www.schelkovo-net.ru
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20140211/71803900/attachment.htm>