On 09/29/14 13:29, Frank Carmickle wrote: > > On Sep 29, 2014, at 1:24 PM, Richard Fuchs <rfu...@sipwise.com> wrote: > >> On 09/29/14 13:19, Frank Carmickle wrote: >>> >>> On Sep 29, 2014, at 1:14 PM, Richard Fuchs <rfu...@sipwise.com> wrote: >>>> >>>> This may work with rtpengine, as it will open new ports for answers come >>>> from different endpoints. But the final two-way association for the >>>> actual call may still end up broken, as it has no way of knowing which >>>> client ends up receiving the call (unless they do a final re-invite). >>> >>> But it should see the 200. Shouldn't that be enough? >> >> Unfortunately it doesn't see SIP codes, it only sees SDP bodies and some >> particular details from the SIP message. 200 OK would be translated to >> an "answer", but not every answer is from a 200 OK, so you can't use >> that to break other associations. Perhaps this would be a nice addition >> to have in the future. > > I will argue that the only thing that is an answer is a 200. A progress, > early media or pre_answer is a 183. Yes both 183s and 200s need to set up > media but as you know there could be many 183s and only one 200. > > If the UA sends an sdp with both the 183 and the 200 would this work > correctly?
That might just work, as the last answer rtpengine sees determines the association with the offer. cheers _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
