I think I have this working. For anyone else trying to do similar thing (or
placing Kamailio behind FW/NAT), here is my cookbook.
We are trying to setup the following:
[UAS] <-->
(PubIP)[FireWall/One-to-OneNAT]<>(PrivIP)[Kamailio/RTPProxy](PrivIP)<-->(PrivIP2)[UAC]
gt; with the carrier.
>
> Thanks
> SV.
>
>
> -Original Message-
> From: Ovidiu Sas [mailto:o...@voipembedded.com]
> Sent: Tuesday, September 06, 2011 9:50 AM
> To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users
> Mailing List
> Subject
and SIP Express Router (SER) - Users
Mailing List
Subject: Re: [SR-Users] Kamailio + rtpproxy talking to multiple carrier gateways
It seems that something is miss configured on your server. The fixes that I
made in the trunk (and you pulled in your local 3.1 repo) were designed to
handle the scena
ith this? I've
> tried to set an alias= core parameter with the public IP, but doesn't seem to
> have any effect. The public IP is not reachable from internal network.
>
> Thanks for your help
>
> SV.
> ----------
>
> Message: 3
> Date: S
On 09/05/2011 08:07 PM, Sarat C. Vemuri wrote:
How do I remove the "public IP" entry from the route set before
forwarding the reply to Internal UAC?
You don't -- at least, not in a protocol-compliant way. You can, of
course, do remove_hf("Route"); if you want to, but with effects that are
u
Thanks for your help
SV.
--
Message: 3
Date: Sat, 3 Sep 2011 16:44:22 -0700
From: Ovidiu Sas
Subject: Re: [SR-Users] Kamailio + rtpproxy talking to multiple
carrier gateways - some via Firewall/NAT
To: "SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
Use
Ovidiu as well with some more details.
Thanks
SV.
--
Message: 2
Date: Sat, 03 Sep 2011 19:12:38 -0400
From: Alex Balashov
Subject: Re: [SR-Users] Kamailio + rtpproxy talking to multiple
carrier gateways - some via Firewall/NAT
To: sr-users@lists.sip-router.org
It is feasable to what you want: kamailio behind NAT proxying traffic
from/to public internet to/from private network.
You will need to properly craft the INVITE and use proper record route headers.
Use set_advertised_address when needed:
http://kamailio.org/dokuwiki/doku.php/core-cookbook:3.1.x#se
On 09/03/2011 05:53 PM, Sarat C. Vemuri wrote:
3.Using request_route_preset(“publicIP”)
The above “mostly” works. By that I mean, the INVITE transaction is
properly passed between internal UAS and carrier SBC and the call is
setup. However, further transactions (BYE/re-INVITE) etc do not work
p
We are trying to configure Kamailio (3.1.x) as a "boarder proxy" where it acts
as the front for various carrier gateways so that internal UACs and UASs are
unaware of the carrier gateways.
Let me try to present a clear picture of our setup.
1. Kamailio has several NICs (physical or vlan)
10 matches
Mail list logo