7 Jun
2012
7 Jun
'12
10:38 a.m.
Hi,
On 06/05/2012 08:21 PM, Saul Waizer wrote:
I am running Kamailio and rtpprox on ec2
I do have a DBUG log for it, one interesting thing to point out: On the
above line notice how I have 127.0.0.1, I changed this from my external
ip address because i was getting the following on the rtpproxy log:
Jun 5 15:42:55 ip-10-x-x-x rtpproxy[6526]: INFO:handle_command: new
session NmJlNDNhOTA0YmYwZTZhYTEyMTQ4ZDIxY2IxNzQzYmM., tag 2c249068;1
requested, type strong
Jun 5 15:42:55 ip-10-x-x-x rtpproxy[6526]: ERR:create_twinlistener:
can't bind to the IPv4 port 59794: Cannot assign requested address
Jun 5 15:42:55 ip-10-x-x-x rtpproxy[6526]: ERR:handle_command: can't
create listener
Jun 5 15:42:55 ip-10-x-x-x rtpproxy[6526]: DBUG:doreply: sending reply
"6545_8 E10#012"
Jun 5 15:43:01 ip-10-x-x-x rtpproxy[6526]: DBUG:handle_command:
received command "6556_12 Lc0,8,101
NmJlNDNhOTA0YmYwZTZhYTEyMTQ4ZDIxY2IxNzQzYmM. some.ip 56536 2c249068;1
c51afb04;1"
Jun 5 15:43:01 ip-10-x-x-x rtpproxy[6526]: INFO:handle_command: lookup
request failed: session NmJlNDNhOTA0YmYwZTZhYTEyMTQ4ZDIxY2IxNzQzYmM.,
tags 2c249068;1/c51afb04;1 not found
This is expected because rtpproxy cant assign a port to the ec2 external
ip instance, however I see that rtpproxy IS in fact trying to record but
I just end up with a bunch of empty .rtp files.
Well, when starting rtpproxy, you need to tell it the address where it's
listening for rtp packets to relay (and record), and rtpproxy uses this
address as a response to kamailio, which in turn puts this information
into the SDP of the SIP messages and forwards it to the end devices.
If you put 127.0.0.1 there, then your end devices will end up sending
their RTP traffic to 127.0.0.1. Also, if you put the private IP of EC2
there (just to make rtpproxy happy and allow it to bind to this
address), it won't lead you to anywhere because that address is not
reachable from the end-devices. There is a patch floating around for
rtpproxy which allows you to set the advertised address (your public ip
mapped to your EC2 instance), which then will work with EC2.
In general, choosing EC2 for your SIP deployment is not a good idea if
you aren't 100% fit with kamailio, rtpproxy and SIP in general, because
EC2's NAT environment is quite tricky to handle in a SIP environment.
Andreas