Hi Benni, Thanks for the changes. See my comment below about your question:
>"Vishal Phirke " >1. Remove the faststart response code from ooAcceptCall function in ooq931.c >and make it a separate function. >2. Call this function in both ooSendAlerting and ooAcceptCall functions. >3. Probabely we will need a flag, to make sure that we don't start channels >again while sending faststart response through connect >" > >I tried to did the first 2, I am not sure about number 3 cause afaik, it's perfectly fine to send faststart reply in multiple >provision/progress message (proceeding, alerting, connect). But i will have to see the ITU document again or maybe >someone can correct me for that. " => You are right about being able to send fast start reply in multiple messages, but what I was talking about in point 3 above is actual opening of receive and transmit rtp channels. This should be done only once as you are acknowledging same channels in multiple messages. I will take care of this. Can you send a patch file, so that it will be easy to integrate into the cvs. Vishal ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ ooh323c-devel mailing list ooh323c-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ooh323c-devel
