Thanks for all the help.<div><br></div><div>The provider is a cellphone operator in my country, they usually don't interconnect with anybody (at least not through SIP), but are giving us access to this only because they want the calls from our service to be routed directly to them.</div>
<div><br></div><div>Unfortunately I have no access to the router, we rent this server on The Planet, but we have never had any problems like this with any other provider, so I'm guessing this doesn't have to do with nat.</div>
<div><br></div><div>Anyway, I was finally able to solve this by setting transport to tcp instead of udp on the gateway config with: <param name="register-transport" value="tcp"/> Even though it's working fine now, I'm not that happy, because I have no idea why it didn't work with udp. Well, hopefully the provider/customer will be glad this got solved.</div>
<div><br></div><div>Again thanks to everyone for all the help. I'd be happy to answer any questions if you are curious about this or have a similar problem.</div><meta charset="utf-8"><meta charset="utf-8"><div><br></div>
<div><br></div><div>Best,</div><div><br></div><div><br></div><div>Nico</div><div><br></div><div><br><br><div class="gmail_quote">On Tue, Oct 19, 2010 at 11:45 AM, Anthony Minessale <span dir="ltr"><<a href="mailto:anthony.minessale@gmail.com">anthony.minessale@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">If the top of their standards are to make it work with asterisk, they<br>
are clearly not very wise.<br>
<br>
Are you using some kind of asymmetric nat? Why is it getting a random port?<br>
Even with rport enabled it should be the true port the packet is seen<br>
coming from and a return path should be expected the same way.<br>
<br>
Check your router for asymmetric nat or SIP ALG features that you can<br>
disable in it's config.<br>
<div><div></div><div class="h5"><br><br></div></div></blockquote></div></div>