< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] about call to hunt group...and several answerers


Actually the client is supposed to BYE each leg it doesn't want to
handle.  This is the applications responsibility.

> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> Daniel Pocock
> Sent: Tuesday, November 07, 2006 10:57 AM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [reSIProcate] about call to hunt group...and several
> answerers
> 
> 
> 
> Jason Fischl wrote:
> 
> >On 11/7/06, Didier HERCOUET <Didier.HERCOUET@xxxxxxxxx> wrote:
> >
> >
> >>My question : how the initial caller can handle these multiple
> 200ok+SDP[Answer] and also these multiple RTP streams?!
> >>
> >>
> >
> >This really isn't a question for resiprocate. You will get a new
> >ClientInviteSession for each 200 OK and will have to handle the SDP
> >negotiation and multiple RTP streams in your application.
> >
> >
> The client is supposed to CANCEL all the other attempts after the
first
> one succeeds, hopefully before the others answer.  Does reSIProcate
> help
> to do that automatically, or does the application developer have to
> take
> responsibility for this?
> 
> 
> >_______________________________________________
> >resiprocate-devel mailing list
> >resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> >https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
> >
> >
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel