Look, think of it this way..
When a NATTED phone makes a sip call, it places it's NATTED address in the header information of the call.. Making the far end phone send audio to this UNREACHABLE ip address.. Nathelper will assist you in REWRITING the SIP message such that you REMOVE the private addresses your NATTED phone has put in the SIP message and instead places the actual IP/port your phone uses to talk to SER with into the message. This in itself for most people will allow a natted phone to make phone calls..
Now if you are going from nat to nat or having trouble with one way calls or the like, or if you just want more control over the audio path, you can try mediaproxy. Chances are that you'll either need something like nathelper to fix the SIP messaging OR your proxy will need to be able to ping and be ping the proxy. OR your media proxy module will need to be able to do this rewriting for you.
Hope that helps. -Brett
On Mon, March 13, 2006 10:44 am, Darren Sessions wrote:
I've been reading the docs on nathelper and mediaproxy and am curious about the possibility of implementing both modules/functionalities on the same proxy (with the dispatcher and media proxy scripts running on separate boxes).
The scenario would be to use either nathelper functionality or mediaproxy functionality based on results from something like client_nat_test, nat_uac_test, or another function like these. This would prevent unnecessary local bandwidth consumption by providing the correct nat transversal mechanism.
After extensive googling, I still haven't been able to find a working/ semi-working example on this type of combination.
Does anyone have any good pointers, example configs / basic configs, or ideas?
Thanks in advance,
- Darren
CALL | |-> Analysis | |-> NATHELPER or |-> MEDIAPROXY
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers