anyone? :) David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 On Mon, Apr 1, 2019 at 4:37 PM David Villasmil < david.villasmil.work(a)gmail.com&gt; wrote:

On Monday 01 April 2019 at 17:37:45, David Villasmil wrote: Have you tried something like: ip rule add from int.ernal.ip.addr lookup mytable ip route add default dev external_interface_device table mytable echo "234 mytable" >>/etc/iproute2/rt_tables Antony. -- 3 logicians walk into a bar. The bartender asks "Do you all want a drink?" The first logician says "I don't know." The second logician says "I don't know." The third logician says "Yes!" Please reply to the list; please *don't* CC me.

Have you tried proposed suggestions? On Mon, Apr 1, 2019, 2:12 PM David Villasmil, < david.villasmil.work(a)gmail.com&gt; wrote:

I suppose you've also defined your `listen=` list? On Mon, Apr 1, 2019 at 2:25 PM David Villasmil < david.villasmil.work(a)gmail.com&gt; wrote:

On Monday 01 April 2019 at 20:29:22, David Villasmil wrote: Why? What is the purpose of this rather odd networking setup? Antony -- "It would appear we have reached the limits of what it is possible to achieve with computer technology, although one should be careful with such statements; they tend to sound pretty silly in five years." - John von Neumann (1949) Please reply to the list; please *don't* CC me.

I think i see what's happening, ACK is going through the REALY route, but at that point it does NOT have a$du (and $sndto(ip) is null) note: all those ERROR is juts me logging. ERROR: <script>: [WITHINDLG] ACK Packet coming from PUBLIC:58031 and going to <null> exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=710 a=5 n=route exec: *** cfgtrace:request_route=[NATMANAGE] c=[/etc/kamailio/kamailio.cfg] l=950 a=2 n=return exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=715 a=5 n=route exec: *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=624 a=16 n=if exec: *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=621 a=25 n=is_method exec: *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=627 a=16 n=if exec: *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=624 a=25 n=is_method exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=631 a=16 n=if exec: *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=627 a=25 n=is_method exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=631 a=5 n=route exec: *** cfgtrace:request_route=[CHECK_DEST_NET] c=[/etc/kamailio/kamailio.cfg] l=600 a=26 n=xlog ERROR: <script>: [CHECK_SOURCE] Packet received on: 172.31.69.53:5060 exec: *** cfgtrace:request_route=[CHECK_DEST_NET] c=[/etc/kamailio/kamailio.cfg] l=601 a=26 n=xlog exec: *** cfgtrace:request_route=[CHECK_DEST_NET] c=[/etc/kamailio/kamailio.cfg] l=602 a=26 n=xlog exec: *** cfgtrace:request_route=[CHECK_DEST_NET] c=[/etc/kamailio/kamailio.cfg] l=610 a=16 n=if *DEBUG: pv [pv_core.c:1122]: pv_get_dsturi(): no destination URI* exec: *** cfgtrace:request_route=[CHECK_DEST_NET] c=[/etc/kamailio/kamailio.cfg] l=608 a=39 n=setflag exec: *** cfgtrace:request_route=[CHECK_DEST_NET] c=[/etc/kamailio/kamailio.cfg] l=609 a=26 n=xlog DEBUG: pv [pv_core.c:1122]: pv_get_dsturi(): no destination URI *ERROR: <script>: [CHECK_SOURCE] Packet going to PUBLIC -> [<null>]* whereas an INVITE _does_ have a $du (remember all work, except ACK) ERROR: <script>: [WITHINDLG] ACK Packet coming from PUBLIC:58031 and going to <null> exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=710 a=5 n=route exec: *** cfgtrace:request_route=[NATMANAGE] c=[/etc/kamailio/kamailio.cfg] l=950 a=2 n=return exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=715 a=5 n=route exec: *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=624 a=16 n=if exec: *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=621 a=25 n=is_method exec: *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=627 a=16 n=if exec: *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=624 a=25 n=is_method exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=631 a=16 n=if exec: *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=627 a=25 n=is_method exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=631 a=5 n=route exec: *** cfgtrace:request_route=[CHECK_DEST_NET] c=[/etc/kamailio/kamailio.cfg] l=600 a=26 n=xlog ERROR: <script>: [CHECK_SOURCE] Packet received on: 172.31.69.53:5060 exec: *** cfgtrace:request_route=[CHECK_DEST_NET] c=[/etc/kamailio/kamailio.cfg] l=601 a=26 n=xlog exec: *** cfgtrace:request_route=[CHECK_DEST_NET] c=[/etc/kamailio/kamailio.cfg] l=602 a=26 n=xlog exec: *** cfgtrace:request_route=[CHECK_DEST_NET] c=[/etc/kamailio/kamailio.cfg] l=610 a=16 n=if DEBUG: pv [pv_core.c:1122]: pv_get_dsturi(): no destination URI exec: *** cfgtrace:request_route=[CHECK_DEST_NET] c=[/etc/kamailio/kamailio.cfg] l=608 a=39 n=setflag exec: *** cfgtrace:request_route=[CHECK_DEST_NET] c=[/etc/kamailio/kamailio.cfg] l=609 a=26 n=xlog DEBUG: pv [pv_core.c:1122]: pv_get_dsturi(): no destination URI ERROR: <script>: [CHECK_SOURCE] Packet going to PUBLIC -> [<null>] Why would an ACK not have a $du? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 On Mon, Apr 1, 2019 at 7:50 PM David Villasmil < david.villasmil.work(a)gmail.com&gt; wrote:

Hello Check your reply_route. An example I use with public and private interfaces and mhomed=1 onreply_route[MANAGE_REPLY] { xdbg("incoming reply\n"); if(t_check_status("(180|183|200)")){ fix_nated_contact(); } El lun., 1 de abr. de 2019 12:38 p. m., David Villasmil < david.villasmil.work(a)gmail.com&gt; escribió:

On Monday 01 April 2019 at 21:07:59, David Villasmil wrote: Okay. No, but it might not be the right question to ask :) Do you prefer to ask "how can I make this strange networking setup operate?" or "how can I arrange my networking so that this service works?" Antony. -- How I want a drink, alcoholic of course, after the heavy chapters involving quantum mechanics. - mnemonic for 3.14159265358979 Please reply to the list; please *don't* CC me.

On Monday 01 April 2019 at 21:19:13, David Villasmil wrote: No, because (unless AWS works in some totally strange way that I can't imagine being the case) the two interfaces would have different IPs and different routes, and only one would be your default route to the Internet (ie: public IP addresses). Then your "internal" machines would connect to the IP on an interface which only routes back to them and can't see the Internet, and public connections would come in to a different IP on another interface which can route back to them. Someone with personal familiarity with AWS systems may be able to inject a more definite answer here. Antony. -- There's a good theatrical performance about puns on in the West End. It's a play on words. Please reply to the list; please *don't* CC me.

actually that's a good point, the default gateway. But, ven if i have 2 different IPs, those 2 would still have direct contact with the private IPs. Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 On Mon, Apr 1, 2019 at 8:27 PM Antony Stone < Antony.Stone(a)kamailio.open.source.it&gt; wrote:

They're not, they're in the same subnet. At least on my tests. Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 On Mon, Apr 1, 2019 at 8:47 PM Antony Stone < Antony.Stone(a)kamailio.open.source.it&gt; wrote:

Well, As suggested, i decided to go with a single ip address. Thanks everyone! Thanks to @Federico Cabiddu &lt;federico.cabiddu(a)gmail.com&gt; i understood why the ACK has no $du. This is because all record-routes have been consumed because this is the final hop. So no record-route, no $du. I have to use the ruri. Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 On Mon, Apr 1, 2019 at 9:01 PM Antony Stone < Antony.Stone(a)kamailio.open.source.it&gt; wrote:

David, out of curiosity, are you finally using only one listen= line or two in your AWS setup? More specific: are you only listening on one port with the ‘advertise’ set or are you finally listenting on two ports? If your are using one port only you might find yourself using egress (billed) traffic between your instances, so make sure in the captures your are really seeing your internal IP in the RR headers when talking to internal servers instead of the egress (public) IP. Thanks, Joel On Mon, Apr 1, 2019 at 13:54 David Villasmil &lt;david.villasmil.work(a)gmail.com&gt; wrote: