[OpenSIPS-Users] opensip proxy behind firwall

[Bogdan-Andrei Iancu]

Hi,

If you want the SDP to remain unaltered, why do you use the rtpproxy 
functions ??

Regards,

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

On 13.07.2016 12:51, Priyanko Bose wrote:
>
> Hi,
>
> Thanks for your reply.
>
> I am able to make SIP call to the device (192.168.v.w(LAN) in below 
> picture) which I have registered to my opensip proxy/registrar server 
> ((LAN) 192.168.x.y), from an UAC located somewhere in the internet.
>
> But the problem is while forwarding the SDP using “rtpproxy_offer()” 
> my proxy server rewriting the SDP with its own private IP which 
> prevents the device to find the public IP of the UAC. Hence, media is 
> not reaching the UAC.
>
> Could you please let know what are the replacement of rtpproxy_offer() 
> and rtpproxy_answer() so that the SDP remains unaltered but SIP call 
> establishes?
>
> Regards,
>
> Priyanko
>
> *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org]
> *Sent:* 11 July 2016 15:54
> *To:* Priyanko Bose; users at lists.opensips.org
> *Cc:* 'Shantanu Kumar Roy'
> *Subject:* Re: opensip proxy behind firwall
>
> Hi,
>
> Could you be more specific in what the "fail to make calls" means ?
>
> Thanks,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
> On 08.07.2016 18:22, Priyanko Bose wrote:
>
>     Hi,
>
>     I am trying to setup a OpenSIP server which should act as a SIP
>     register as well as a SIP proxy server.
>
>     If the server is placed in the same LAN where multiple SIP enabled
>     devices (e.g Cisco SX20, Polycom RPG500) reside, then the devices 
>     get registered  easily and can make SIP calls among themselves.
>
>     But everything fails when the devices are on the other side of the
>     internet and the server is behind firewall like following diagram.
>
>     ----------     ------------
>                                      -------------            
>     --------------
>
>     - Device -    <--->       - F/W   -              <---> 
>                          -  F/W    -                     <---> - 
>     OpenSIPS  -
>
>     ----------       ------------
>                                          -------------           
>      --------------
>
>     192.168.v.w(LAN)    192.168.v.1 : 63.45.x.y     (WAN)
>       220.54.w.y: 192.168.x.1       (LAN) 192.168.x.y
>
>     The server’s private IP (192.168.x.y ) is mapped to a fixed public
>     IP (220.54.w.y) and ‘opensips.cfg’ file has been prepared same as
>     described in the link
>     http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Server-behind-a-NAT-firewall-td5853352.html.
>     This time I am able to register the device but fails to make SIP call.
>
>     Regards,
>
>     Priyanko
>

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