If you know the public IP in advance, just use a variable such as [$public_ip] instead of [local_ip] everywhere in the scenario (so unless you already use custom scenarios, you have to use the -sd command line parameter to dump the embedded one(s) into file(s), modify them accordingly and use -sf file_name on the command line), and add -set public_ip your.public.ip.address to the command line (maybe there has to be a = sign rather than a space between the variable name and its value).
Pavel Dne 2.4.2019 v 23:14 Cyril Constantin napsal(a): 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 _______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net<mailto:Sipp-users@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/sipp-users -- Ing. Pavel Šindelka senior specialista [cid:part2.B27A57D3.8A8FCA40@ttc.cz] TTC MARCONI s. r. o. Třebohostická 987/5, 100 00 Praha 10 +420 234 051 712, +420 602 355 199 sinde...@ttc.cz<mailto:sinde...@ttc.cz>, www.ttc-marconi.com<http://www.ttc-marconi.com>
_______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
