The code seems to be correct. The to and from tags
are switched for:
- reply with offer (200ok with first SDP)
- request with answer (ACK with second SDP)
Are you sure that you are properly invoking offer/answer rtpproxy
functions?
Regards,
Ovidiu Sas
On Wed, Feb 9, 2011 at 11:48 AM, Emil Kroymann
<emil.kroymann(a)isaco.de> wrote:
Hi,
We recently had a problem with the nathelper module and rtpproxy in
a scenario where the SDP offer is sent only in the 200 OK. We use
sip-router 3.1 and rtp-proxy from git master. The sip-router
configuration uses the rtpproxy_offer() and rtpproxy_answer()
functions in appropriate places. The problem is, that the arguments
sent to the rtpproxy, when the ACK with the sdp answer arrives,
seems to be not in the order, that rtpproxy expects.
On the 200 OK, the nathelper module sends callid, to-tag, from-tag
to rtpproxy. On the ACK, the nathelper module sends callid,
from-tag, to-tag (with different command prefixes, of course, but I
cannot remember them atm). The version of rtpproxy that we are
using seems to expect, that the order of arguments sent on the ACK
request is the same as on the 200 OK.
My question: are there any module parameters, to correct this
behaviour?
Regards,
Emil
--
Emil Kroymann
VoIP Services Engineer
Email: emil.kroymann(a)isaco.de
Tel: +49-30-203899885
ISACO GmbH
Kurfürstenstraße 79
10787 Berlin
Germany
Amtsgericht Charlottenburg, HRB 112464B
Geschäftsführer: Daniel Frommherz
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users