it is still one IP from point of view of signaling (SIP). Do you
want to provide single IP also for media (RTP)? If you have lot of
calls, then it can result in a bottleneck for bandwidth as all
voice/video streams end up on the same server.
Cheers,
Daniel
On 3/26/13 2:16 PM, Felipe Ramos wrote:
Daniel Thanks a lot for your response, in my case i
don't want to provide so many ips to carriers acl because aws
elastic ip are not consistent, that is the reason i wanted to
proxy everything trough kamailio, here it is my setup
i wont be doing any registration because of my setup does not
required it, on hardware i had kamailio forwarding to freeswitch
then distributed to asterisk and finish to a sbcswitch which i
will be virtualizing on aws.
again thanks a lot for your advice you're the best.
#i a planning to send it to distpatcher module once i get
calls flowing.
if(!t_relay_to_udp("ip internal", "5060")) {
sl_reply_error();
}
exit;
}
On Tue, Mar 26, 2013 at 5:13 AM,
Daniel-Constantin Mierla <miconda@gmail.com> wrote:
Hello,
On 3/26/13 2:38 AM, Felipe Ramos wrote:
Can anyone please point me on a
configuration example for kamailio when it is behind
NAT, i need to change the contact ip from internal to
external on sdp
you should not need that. Kamailio should do record
routing, advertising the public IP, so the signaling from
the other side is sent to Route headers, not to Contact
address.
and proxy all media from outside
to internal asterisk farm.
Asterisk has support for external IP, so it can advertise
that IP in SDP and the media will go directly to the
asterisk. Makes no sense to make a user space forwarding
with rtpproxy.
Cheers,
Daniel
Please any help will be appreciated.
most of documentation available is when client is
behind Nat but not when Server behind Nat like is
the case with Amazon aws vpc instances.