RE: [reSIProcate] Problem with UAC sending ACK automatically
If for some reason the RTP stack only allows you to create
bi-directional RTP connections - and you must wait for the 200 before
you can start listening on your RTP port. If this is the case you will
want to ensure this process is completed before the ACK is sent.
I do agree however that you SHOULD be listening for RTP when you send
the original Invite. Making this configurable gives dum some
flexibility.
Scott
> -----Original Message-----
> From: derek@xxxxxxxxxxxxxxx [mailto:derek@xxxxxxxxxxxxxxx]
> Sent: Wednesday, June 14, 2006 1:30 AM
> To: Scott Godin
> Cc: 'Kovar,William (Bill)'; resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [reSIProcate] Problem with UAC sending ACK automatically
>
> Having RTP ports/etc created bfore the ACK is send in the INVITE w/o
offer
> case might be reasonable...but this should be accomplshed syncronously
in
> onAnswerRequired w/ some prior work. If an app sends an INV w/out SDP
> having some resources pre-allocated seems like a reasonable
requirement.
>
> However, Bill's use case was where there was an offer in the INV and
an
> answer in the 200. Media will flow from the UAS side once the 200 is
sent,
> and will be send by the UAC(Bill's UA) once the 200 is recieved; what
is
> the motivation for delaying the ACK?
>
> --Derek
>
> Scott Godin said:
> > Currently you cannot control this - but there are use cases where
you
> > would
> > want to (ie. App needs to be sure RTP ports are created and
listening
> > before
> > ACK is sent). I think we should modify dum in order to make this
> > behaviour
> > configurable.
> >
> > Scott
> >
> > _____
> >
> > From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> Kovar,
> > William (Bill)
> > Sent: Tuesday, June 13, 2006 6:24 PM
> > To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: [reSIProcate] Problem with UAC sending ACK automatically
> >
> >
> > I have a UAC that sends INVITE (w/sdp) and receives 180 (no sdp).
> >
> > At this point the onNewSession(ClientSession....) is called which
does
> > nothing.
> >
> > The far side is set to auto-answer.
> >
> > After that, a 200 OK w/sdp arrives to the UAC and DUM (or
resiprocate??)
> > sends out the ACK without any actions on my part. The only callback
> fired
> > before the ACK is sent is onReadyToSend().
> >
> > In my app I don't want to send the ACK until I'm good and ready. How
can
> I
> > control it??
> >
> > Bill Kovar
> > Avaya Inc.
> > (732) 852-2609
> > bkovar@xxxxxxxxx
> >
> > _______________________________________________
> > resiprocate-devel mailing list
> > resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>