Up to Discussions in OpenSIPStack

This Question is Answered

1 "correct" answer available (5 pts) 2 "helpful" answers available (1 pts)
1 Replies Last post: Jan 12, 2010 3:08 PM by MoIn  
Click to view MoIn's profile  
MoIn
4 posts since
Jan 12, 2010

Jan 12, 2010 5:07 AM

default behaviour for accept invite and send ringing

Hi,

I'm using the OpenSipStack library and tried to accept an INVITE message to send a RINGING message. Up to now my workmate has always send an OK as soon as he becomes the INVITE but it seems to be that he doesn't handle the INVITE correctly. So if I remove his code to send OK message instantly, the library always send a message 404. I tried a lot other things but alway get another error message or send a new INVITE back.
My workmate has derived a lot of classes (OpalOSSConnection, OpalOSSEndPoint, OpalManager, OpalOSSCore...) and changed the default behavior.
So want I want to know is what I have to do to handle the INVITE message correctly (have I to accept it somewhere) and to send a ringing message (maybe I have to set an internal state that he starts ringing).

Thx
Click to view MoIn's profile  
MoIn
4 posts since
Jan 12, 2010
1. Jan 12, 2010 3:08 PM in response to: MoIn
Re: default behaviour for accept invite and send ringing
Ok,

I think I've found and solved the problem, I hope so :). OSS tries to send back a new INVITE (see OpalOSSConnection::OnIncomingCall) so I didn't call OpalOSSEndPoint::OnSetupIncomingCall(invite, session) and will never get the 404 or a new INVITE.

And the INVITE message has to support "100rel" to trigger automatically retransmission of RINGING messages. I had removed it before for some test cases and forgot to reactivate it.

Never the less

Thx

Actions

More Like This