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]
rio that you are trying to implement.
The ACK should be handled properly and routed to the upstream carrier
(following the same path as the initial INVITE).
Regards,
Ovidiu Sas
On Mon, Sep 5, 2011 at 5:07 PM, Sarat C. Vemuri wrote:
> Again, I apologize for this clumsy way of rep
idiu Sas
On Sat, Sep 3, 2011 at 2:53 PM, Sarat C. Vemuri wrote:
> 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 t
Message-ID: <4e62b466.20...@evaristesys.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
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
> prope
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)
