Hi Daniel-Constantin!
Daniel-Constantin Mierla wrote:
Greger, it seems that the guy already read the Getting started document ... or I do not understand right his message or you actually didn't read the mail :) ... I am sure that the document is very usefully, but you create a lot of confusion and some time looks like intoxicating the mailing list with such links (a lot of replies off-topic) ...
Sorry if you get that impression, I'm just trying to do good... It's not the answer to everything, that's for sure. However, there is actually a config script without the auth, so it could help him for the untangling he mentioned. To me it looked like he hadn't had a look at that script, but I admit my answer was a bit schematic and was not intended to address anything else than the untangling problem.
You see, people who subscribe to the list are not yet informed about the document when they subscribe (we don't want to do that until we are 100% sure that errors and typos have been corrected, which will be pretty soon). Until then newcomers must be informed either by looking/searching in the archives or as you call it: through "intoxicating" emails to people who seem to have a question that may be resolvable through the documentation. Sorry about that, but I'm sure that you welcome the reduction of similar-sounding newcomer-questions, and I'm sure that if you had read the document ;-), you would find it useful to sometimes refer to it, too!
Jeff, to your second email: By using ONsip.org config files, a lot of people will have the same structure and it's easier to help you by understanding the changes you have done. If not, you must at least include an ngrep trace of the messages.
It seems that messages are not coming through to the UAs behind NAT. It may be because the UA is not correctly detected as behind NAT, check with serctl ul show that the NAT flag is set (The GettingStarted document explains in detail the various nat test values.)
Now, back to his topic, it is not quite possible to have SER NAT traversal solution based on nathelper/rtpproxy without having usrloc (user location) in the same place, which usually uses MySQL. You can try using dbtext instead of MySQL for user location, or disable persistence support in user location (in this mode after ser restart all contacts are lost, which is not recommended to have).
Depending on your setup (ex. more than one outbound proxy), you may also have to handle routing to the correct proxy (which will be able to traverse NAT for a particular UA). There was a long discussion on this 1-2 months ago, and Klaus Darillion posted a patch he made for an outbound proxy. You may want to find that post. g-)
On 06/14/05 16:09, Greger V. Teigre wrote:
http://onsip.org/ , go to Downloads and get the Getting Started document and configuration files. g-)
jeff kwong wrote:
Hi to everybody!
Im currently trying to setup an outbound proxy using ser. Im still a newbie with this ser and im not yet that good with the scripting. Could anyone tell me how to configure ser for outbound proxy only using rtpproxy? There are samples files in the Getting started manual but im having troubles eliminating the authentication/mysql part in script since im not yet familiar which modules depends on which. A striped down version of the nat-rtpproxy.cfg file would be really appreciated. Thanks in advance.
_jeff
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers