[OpenSIPS-Users] OpenSIPS sending 200 OK with SDP

[Ali Pey]

Hi Andreas,

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.

Regards,
Ali Pey

On Tue, Aug 28, 2012 at 8:06 AM, Andreas Sikkema <h323 at ramdyne.nl> wrote:

> Hi,
>
> I know what I'm trying to do is very much frowned upon, but I'm
> hitting walls everywhere to make this work.
>
> We have this platform that is using what seems to be RFC3311 UPDATE
> messages as part of a call transfer. A calls B, B answers, A calls C
> and during the ringing phase A transfers C to B. During the transfer A
> sends an UPDATE message to C to signal that it should send RTP to B
> instead of A. B is notified using re-INVITE messages. B and C are both
> behind an OpenSIPS install built especially for this sceanrio.
>
> Most free software products have a hard time supporting this. Some
> have bugs (see the bugfix for OpenSIPS where we reported the initial
> problem) and others just don't support it at all. Since we're running
> quite a lot of those products I'd rather have something handle the
> UPDATE but don't bother other clients with it.
>
> So, is there a way for OpenSIPS to receive the UPDATE, handle the SDP
> change using either one of the media proxies and respond back to A
> with a 200 OK containing the (perhaps) newly updated SDP?
>
> We're already running an older installation of OpenSIPS that we can't
> (yet) upgrade so we're introducing a new one (I'm hoping temporarily).
> We found this issue while trying to connect our existing OpenSIPS
> based platform to our hosted PBX platform using a SIP connection.
>
> Thanks!
>
> --
> Andreas Sikkema
>
> _______________________________________________
> 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/20120828/5904ab1c/attachment-0001.htm>