Hi Maxim,
I am in the process of testing this new version in our lab with 0.8.13.
We have been using the older versions with great success for many months
now. But the new version does not work. We are testing with
Grandstream and Sipura units. When a Sipura calls another Sipura, the
nathelper/rtpproxy fails to insert the proper "Connection Information
(c)" in the SDP. Instead of filling in the IP Address of the RTPProxy it
just leaves the same address and adds these four characters "\000" to
the end which seem to make the other Sipura unhappy because it
terminates the call right away with a "488- Not Acceptable" Message.
When a Grandstream is making the call, the same thing happens, with the
exception of the four characters. (IP Address in Connection Information
(c) is not updated)
The Ports do seem to get changed appropiately by the nathelper/rtpproxy
in both cases. But since the IP is not substituted there is no chance
of audio being setup properly.
I can send the Ethereal traces if you want.
Let me know what we can do to fix this issue.
Thanks,
--
Andres
Network Admin
http://www.telesip.net
Maxim Sobolev wrote:
> Maxim Sobolev wrote:
>
>> Hi,
>>
>> I've just committed major update for rtpproxy/nathelper, which adds
>> support for proxying RTCP and also make RTP proxy behave much better
>> for non-NATed clients by pre-loading remote addresses[1] of each
>> party from the SIP request/reply. Please note that proxy's command
>> protocol has been extended to support new functionality, so that you
>> need both new rtp proxy and new nathelper (old nathelper will not
>> work with new rtp proxy and vice versa). Both of them can be obtained
>> from the ser's cvs repository:
>>
>>
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/rtpproxy/
>>
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/nathelper/
>>
>>
>> Please let me know if there are any problems with the new version.
>>
>> -Maxim
>> [1] currently only IPv4 addresses can be pre-loaded, though it should
>> be trivial to extend proxy, nathelper and command protocol to
>> accomodate IPv6 as well. Proxy's core supports IPv4<->IPv4,
>> IPv4<->IPv6 and IPv6<->IPv6 relaying already both for RTP and RTCP.
>
>
> P.S. Forgot to mention: nathelper now inserts special flag into SDP
> body which indicates that the session is already forced to go through
> one rtp proxy and do not apply rtp proxy to messages with such flag
> already set.
>
> _______________________________________________
> Serusers mailing list
> serusers@lists.iptel.org
>
http://lists.iptel.org/mailman/listinfo/serusers
>
>
