[OpenSIPS-Users] OpenSIPS sending 200 OK with SDP

[Ali Pey]

If I understand your question correctly, you need to examine and manipulate
the SDP parameters in the 200 OK?

You can use the sipmsgops module for that. There are functions such as
codec_exists(),
codec_delete(), etc. Check out the module here. There are lots of good
function in there. You can also check out the textops module as well for
manipulation.

http://www.opensips.org/html/docs/modules/1.8.x/sipmsgops.html#id293116

Regards,
Ali Pey

On Thu, Aug 30, 2012 at 10:09 AM, Andreas Sikkema <h323 at ramdyne.nl> wrote:

> > I don't see why you can't do this. In your routing script you can look
> for
> > the update message (there should be something about this update message
> that
> > you can detect it), make changes as required and generate a response to
> any
> > destination you want. This is what the routing script (opensips.cfg) is
> for.
>
> I know in theory that it's possible to code something that might look
> like what I want to do (pseudocode):
>
> if (method="") && (src_ip="w.x.y.z") {
>     rtpproxy_answer();
>     send_reply("200 OK");
> }
>
> But I'm not sure that the 200 OK will contain the correct SDP lines
> from the media/rtpproxy, if I can add some (thankfully predictable)
> codec parameters, etc to the 200 response. I can't remember ever
> having seen someone do something like that here on the mailinglist.
> Google also doesn't seem to be able to find  something like this.
>
> I'd prefer to do this without running as a B2BUA, but if that's
> necessary, not a problem.
>
> For now I have a workaround, but for the longer term I need something
> to prevent those UPDATE messages getting passed through to the rest of
> my network.
>
> --
> Andreas
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20120830/9b231a46/attachment.htm>