I read that, but I am not using that sample config file. Greger V. Teigre wrote: > Have a look at the http://ONsip.org/ Getting Started document. Note > the news-posting on the frontpage regarding an error in the rtpproxy > example config. > g-) > > Rod Bacon wrote: > >> Well.. it probably is. >> >> I have had mixed success with SER 0.8.14 and RTPPROXY. I have RADIUS >> auth, accounting, MYSQL, blah, blah, blah, all working.... >> >> My question, however, surrounds NAThelper configuration. If I leave >> all clients behind NATs to attempt registration with private IPs, >> fix the IPs with NAThelper and proxy the streams, then everything >> works OK. >> If I inroduce a client that is on a LIVE IP address, I only get >> one-way audio to a natted client (the natted client can't hear the >> live client). I assume that what is happening is that the live >> client is attempting to send it's audio direct to the natted >> client, instead of via the proxy. >> I figure that I've missed something silly somewhere in the config, >> but I'm darned if I know where. >> >> I won't bother posting my entire config (unless specifically >> requested), rather I'd like a general pointer as to where I should >> be looking. >> Thanks in advance. >> >> >> >> _______________________________________________ >> Serusers mailing list >> serusers(a)lists.iptel.org >> http://lists.iptel.org/mailman/listinfo/serusers

You have to use nathelper+rtpproxy as soon as one of the clients is behind NAT. E.g. if the public client calls the natted client, you also have to use rtpproxy. Thus, you have to setup a reply route. nat_uac_test detects only if the caller is natted. To detect if the callee is NATed, use the nat_flag parameter: http://lists.iptel.org/pipermail/serusers/2003-December/004412.html

Anyone knows how to find out if a callee in a mid-dialog call is behind NAT?