Hi Tim,
this means your reply does not have a body... can you confirm this? what
you can try is to log extra info from script. If force_rtp_proxy()
fails, use xlog to print the whole message buffer ($mb) and the message
body ($rb)
(see http://openser.org/docs/pseudo-variables-1.1.x.html).
regards,
bogdan
Tim Barrett wrote:
Hello,
I traced what's happening in the source code based on log messages.
first nathelper.c - force-rtp-proxy2_f is failing on "if(extract_body
(msg, &body) == -1)
nhelper.c - extract_body is returning zero on body->len = msg->len
-(int)(body->s-msg->buf)
Could this be the issue resulting in my sdp (c:) and (m:) not being
updated by openser/nathelper?
If so, what is the issue causing the problem? Is the header on the ok
packet incorrect? Are the OK SDP fields arranged in an order that the
msg_parser can't handle?
Help is greatly appreciated.
From: Bogdan-Andrei Iancu <[EMAIL PROTECTED]>
To: Tim Barrett <[EMAIL PROTECTED]>
CC: devel@openser.org
Subject: Re: [Devel] Openser / Nathelper question
Date: Tue, 28 Feb 2006 11:35:14 +0200
Hi Tim,
Tim Barrett wrote:
I am working with openser and the nathelper on scripting a multiple
nat traversal. Everything works with the exception of 1 particular
SIP end point. Openser is not updating the connection information
when it sends the OK to the calling SIP end point.
you mean the SDP part in the 200 OK? Do you see any errors in the
logs? are you sure you hit the force_rtp_proxy() for that reply?
As a result, all rtp is directed to the private IP address for the
client. I assume that it might be an issue with the SIP register
this en point sends. Can anyone provide any insight?
a network trace will be very helpful.
regards,
bogdan
_______________________________________________
Devel mailing list
Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
