[sr-dev] modules_k: nathelper split

Iñaki Baz Castillo ibc at aliax.net
Sun Aug 15 19:15:34 CEST 2010


2010/8/11 Ovidiu Sas <osas at voipembedded.com>:
> nat_traversal and then new nathelper will be somehow redundant to each
> other (nat_traversal is a little bit more advanced by taking advantage
> of the dialog module to keep NAT pinholes alive for incoming calls
> from subscribers that does not register).
> At this point in time I don't want to affect the existing
> functionality.  The split is a noop from a functionality point of
> view.
> All I want is to separate the two major tasks: handling of NATed
> subscribers and rtpproxy communication.  This will provide a cleaner
> design and hopefully a simpler approach in merging the two versions of
> the nathelper module (s and k).

Sure. I also agree that your proposed split is a good idea. Perhaps in
a future it would be great to merge the new nathelper module (just
signalling) and nat_traversal module, but that is a different subject.

Regards.


-- 
Iñaki Baz Castillo
<ibc at aliax.net>



More information about the sr-dev mailing list