[reSIProcate] Problem with UAC sending ACK automatically

[Scott Godin]

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 at list.sipfoundry.org
[mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of Kovar,
William (Bill)
Sent: Tuesday, June 13, 2006 6:24 PM
To: resiprocate-devel at list.sipfoundry.org
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 at avaya.com
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060613/c9e67fb8/attachment.htm>