21 Aug
2007
21 Aug
'07
8:47 a.m.
>>>> Nithin Rajagopal
<nrajagopal(a)signalogic.com> wrote:
I am newbie to this field. We are trying to use a
separate card for
handling the rtp voice traffic but use the RTPProxy (IPtel) software to
handle the NAT issues. We have been fairly successful in doing that.
The problem now is to handle asymmetric NATs. I hear one way audio.
What do you mean as "asymmmetric NAT"?
Cone NAT or asymmetric RTP client behind NAT?
We are not sure how to handle this when there is one
machine running
rtpproxy software and another card with a different IP handling the SDP
(In nathelper.c of Openser new_ip= card IP). In the symmetric NAT
scenario this works fine. I would appreciate and pointers to modify
rtpproxy for this configuration.
So I suppose you mean asymmetric client behind NAT, don't you?
It's more hard case. But if only signaling IP and IP for RTP
differs, it's good. Problems (almost unavoidable) appear if
client's source RTP address differs from destination RTP address
(specified in SDP), "address" here means both host and port.
--
Valentin Nechayev
PortaOne Inc., Software Engineer
mailto:netch@portaone.com