< Previous by Date | Date Index | Next by Date > |
< Previous in Thread | Thread Index |
Scott Godin wrote:
Looking at your bug report - you are in state UAS_EarlyOffer - which means you received an offer in the invite. You shouldn't be calling provideOffer. You should be using provideAnswer.
provideAnswer works, if I do: sis->provideAnswer(mySdp); sis->provisional(183);Now I get the early media. When looking at ServerInviteSession.hxx, I had thought that provideAnswer might automatically send a 200, so I didn't try this earlier. Maybe a note is need in ServerInviteSession.hxx to suggest using provideAnswer with 183.
-----Original Message----- From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Daniel Pocock Sent: Monday, January 30, 2006 11:17 AM To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx Subject: Re: [reSIProcate] sending early offer with 183 provisional Scott Godin wrote:What version are you using? I'm pretty sure this is fixed already in the SVN head.I'm using the version from the SVN repository, I checked it out about1week ago. Is this something that has been fixed recently, or am I possibly using the wrong repository?-----Original Message----- From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Daniel Pocock Sent: Monday, January 30, 2006 11:03 AM To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx Subject: [reSIProcate] sending early offer with 183 provisional Hi, I notice in a previous email from December that there is a known bug that complicates the sending of early media (i.e. a 183 SessionProgressresponse with an SDP offer attached). ServerInviteSession currently bails out with an `assert' if I attempt to call provideOffer withearlymedia. Is this issue any closer to being resolved, i.e. is there aworkaround,is someone working on it already or should I consider creating apatchmyself? I've just created a new entry in the bug tracker for it, http://track.sipfoundry.org/browse/RSP-24 If anyone else is already working on this problem or knows aworkaround,please contact me or the list. Regards, Daniel
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature