17 Oct
2012
17 Oct
'12
8:06 p.m.
I guess not many rtpproxy deployments are handling SIP traffic with
multipart/mixed body content and therefor has_body("application/sdp")
works just fine.
In the case that multipart/mixed body is present, blindly invoking
rtpproxy_offer for INVITE will work ok if SDP is present (and that's
the most used pattern: SDP in INVITE/200ok as opposed to 200ok/AC.
So ... yes, not all cases are covered, but it seems that most common
scenarios are covered.
-ovidiu
On Wed, Oct 17, 2012 at 12:57 PM, Juha Heinanen <jh(a)tutpro.com> wrote:
Ovidiu Sas writes:
Making the rtpproxy user friendly would be the
right approach here.
Then based on return code, the script admin should be able to handle
all scenarios.
i thought that using rtpproxy is the mainstream thing. now it appears
that it cannot be used with currently existing script functions (if we
leave raw regex matching out) without getting "Unable to parse sdp"
errors to syslog.
-- juha