[Sipp-users] AWS EC2 NAT 1:1

[Cyril C. <cyr...@gm...>]

Hi Guys,

I'm trying from an AWS EC2 to generate SIPP calls to a remote server also
hosted on AWS EC2, the problem is that I only have one internal private IP
to bind on with SIPP and can't rewrite the SIP headers with -i option to
use my AWS EC2 public IP.

My remote server reject my INVITE with a 488 Not acceptable here because
messages come from a public IP but SIP headers contain the internal IP that
I was using to bind.

AWS EC2 is doing a NAT 1:1 between the public IP and private IP but it's
not possible to assign an ethernet interface with a public IP.

Do you see a way to achieve it ?

Thanks in advance for your help.

Best Regards