The point of that NDLB-nat-connectile-dysfunction param is to perform a hack on the RFC and ignore the contact given in the packet and replace it in our database with our own contact we formulate by using the IP and PORT the packet was received from. Thus the PORT has to be included because sending invites to that exact IP and PORT is the only way we know will make it back over the NAT translation path.<br>
<br>If you register to me on a public server and you say your contact is <a href="mailto:foo@10.0.0.1">foo@10.0.0.1</a>. but I see the NAT hack enabled on your account. I notice the packet was received from a valid internet IP:PORT since I cannot reach <a href="http://10.0.0.1">10.0.0.1</a> I replace the host from your real contact with the IP you registered from. and I append the PORT the register came from and save that as a contact. Then if i send an invite to that url it will go backwards over your NAT path assuming you are doing keepalives on SIP.<br>
<br>Now, <br><br>"To every Open Source project I have involved in I try to help as much as<br>
I can. And the best thing I can do (due to my home lab setup :-) is<br>
finding bugs. And I think I'm good at it :-)<br>
It sounds very strange to me your are so displeased with it, but I<br>
respect your wishes, of course."<br>
<br>and <br><br>"I'm sorry, in confers I contribute to there is a frequent practice to<br>
support the thoughts by exact RFC content and I just bring this practice<br>
with me to FreeSWITCH conference, because I'm very accustomed with it.<br>
You tell me it is not wonted - ok, I stop it."<br><br>This is the condescending passive-aggressive "kill em with kindness" thing that I was trying to explain is annoying. So if you are serious about not trying to make me mad, tone that down a little more please. I have answered every one of your questions, fixed every one of your issues ahead of stuff I am already working on and I am simply trying to tell you what our policy is and you essentially dismissed each of them with some sort of "I'm sorry but not really" type response.<br>
<br>I clearly said shoving the RFC in someones face as an excuse why they should fix your problem is what annoys us and I said we do comply to the RFC as much as we can apart from the proven cases where conforming to it makes us unable to interop. You still chose to "apologize" and promise never to refer to the RFC again. That is passive-agressive and unwanted behavior.<br>
<br><br>The conclusion that something is a bug, unless it's a seg fault, is subjective and the issue must be deliberated on before a fix is applied and it helps to have that process documented. So, yes please find bugs, and yes use jira to report issues and use the mailing list to ask questions or discuss an ongoing development process.<br>
<br>Please simply acknowledge that you understand my point and do not riddle my email with comments and I will be happy. <br><br>We look forward to your success with FreeSWITCH and welcome to the community.<br><br><br><br>
<br><br><br><br><br><br><br><div class="gmail_quote">On Fri, Apr 11, 2008 at 10:23 AM, kokoska rokoska <<a href="mailto:kokoska.rokoska@post.cz">kokoska.rokoska@post.cz</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Anthony Minessale napsal(a):<br>
<div class="Ih2E3d">> The main reason we write the port in that case is because the idea of<br>
> that nat hack is to make the contact<br>
> be the exact ip/port the register came from. Because of NAT it's some<br>
> random port so putting the port in the contact is the only<br>
> way we can get the packet back to the phone from our scope of the SIP<br>
> stack.<br>
<br>
</div>Thank you very much, Anthony, for your explanation!<br>
I'm not sure I understand well, but I try to read it once more or look<br>
into sources to get a clue :-)<br>
<div class="Ih2E3d"><br>
> Any more advanced techniques need to be applied<br>
> by a router such as openser or from the sofia stack itself. You can<br>
> visit them in #sofia-sip on the same irc server as ours.<br>
><br>
<br>
</div>OK, thank you for pointing me to right direction, I will ask someone<br>
from Sofia.<br>
<div class="Ih2E3d"><br>
><br>
> First of all I would like to complement us on our ability to keep up<br>
> with you.<br>
> Just as a hint, you are starting to abuse our help by asking for an<br>
> average of 3 incidents a day this week.<br>
<br>
</div>First of all, let me apologize if my comments looks like I try to abuse<br>
your willingness. It is not what I want.<br>
<br>
For my defence I like to say that majority of my messages are bug-reports...<br>
<div class="Ih2E3d"><br>
> Do people you pay money even help you that much?<br>
><br>
<br>
</div>As my voluntary work I'm active in some local VoIP forum and try to help<br>
others with things I have enough knowledge about. May be I don't need<br>
much brain power to answer the questions because most of them are very<br>
simple, but there is a huge amount of them per day.<br>
And thus I never think about how much someone can ask me and how much I<br>
could ask others. It is my mistake, let me apologize.<br>
<div class="Ih2E3d"><br>
> Let me give you a few pointers on how to get along with us. You may or<br>
> may not have done all of these things<br>
> but I am listing them for your information. I am not telling you to<br>
> stop bringing up issues but be careful about dominating our time.<br>
<br>
</div>To every Open Source project I have involved in I try to help as much as<br>
I can. And the best thing I can do (due to my home lab setup :-) is<br>
finding bugs. And I think I'm good at it :-)<br>
It sounds very strange to me your are so displeased with it, but I<br>
respect your wishes, of course.<br>
<div class="Ih2E3d"><br>
> You may want to also use <a href="http://jira.freeswitch.org" target="_blank">http://jira.freeswitch.org</a> as a more formal<br>
> way to track your problems.<br>
><br>
<br>
</div>OK, if I see it is not avoidable, I insert it in the jira.<br>
<div class="Ih2E3d"><br>
> 1) Please do not take the extra time to provide any justification to why<br>
> you think we *should* do something just to help your case.<br>
<br>
</div>If I ever used "should" I never meant to force you to help me. It was<br>
just advice about what could help FreeSWITCH to be better - from my<br>
point of view. Nothing more.<br>
If it bother you, I never repeat it.<br>
<div class="Ih2E3d"><br>
> Feel free to ask but do not use what someone else does as an<br>
> excuse. If everyone in Europe was jumping off a cliff, should we too?<br>
> This includes used car salesman techniques like using statements<br>
> like "I have this simple app and it doesn't work how I want.<br>
> If this were a real soft-switch it would do this....."<br>
><br>
> 2) Do not use RFC as a bible. When someone wants something they tend to<br>
> stand up on a soapbox and wave it in the air.<br>
> Meanwhile when something else inconvenient happens like NAT where<br>
> breaking the RFC usually fixes it, then it's ok.<br>
> We all know we should try to work as close to the RFC as possible.<br>
> We also all know it's impossible to actually work right<br>
> at 100% RFC compliance unless you live on a commune full of SIP<br>
> purists. So avoid quoting the RFC to prove your point.<br>
<br>
</div>I'm sorry, in confers I contribute to there is a frequent practice to<br>
support the thoughts by exact RFC content and I just bring this practice<br>
with me to FreeSWITCH conference, because I'm very accustomed with it.<br>
You tell me it is not wonted - ok, I stop it.<br>
<div class="Ih2E3d"><br>
> Save it for rare occasions. The Sofia SIP stack does a lot of work<br>
> to comply and they do a good job you should thank them.<br>
><br>
<br>
</div>I'm very thankful to them, but I hope it doesn't mean I couldn't think<br>
about improvements. Like on any other projects.<br>
<div class="Ih2E3d"><br>
> 3) Keep it in mind that FreeSWITCH is developed primarily by me and I<br>
> only have so many hours in a day.<br>
> I am more than happy to answer questions and help people but be sure<br>
> to give others a turn too.<br>
<br>
</div>I'm sorry. I'm accustomed to send bug reports to dev-lists and I just<br>
continue in this practice with FreeSWITCH. If it is not desired, I stop<br>
it and use jira exlusively.<br>
<div class="Ih2E3d"><br>
> Try asking more questions on the users list or the irc channel to<br>
> give others a chance to help too.<br>
><br>
<br>
</div>I hope I have asked questions in user-list. If not, let me apologize, it<br>
was an oversight...<br>
<div class="Ih2E3d"><br>
> 4) When you feel yourself crossing the line from testing the waters to<br>
> going in production, consider getting a support contract or the visiting<br>
> the donation and/or wishlists so you can give back to the project<br>
> and put smiles on underprivileged developer's faces for pennies a day.<br>
><br>
<br>
</div>Majority of projects I'm using VoIP SW in are non-profit and costs me<br>
not only a lot of time but real money too.<br>
But - wheter I ever will use FreeSWITCH in production or not, I do what<br>
I can to support it because I see big potential in it.<br>
Besides like I do for any other SW project I feel truly amazing...<br>
<br>
Best regards,<br>
<br>
kokoska.rokoska<br>
<br>
<br>
_______________________________________________<br>
Freeswitch-users mailing list<br>
<a href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
<br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:213-799-1400