< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate-users] How to work on forwarding request and forking?


I think you are probably going down the wrong path here.  Sounds like what you want to create is pretty much SIP proxy functionality.  In that case, I would avoid using DUM or ichat-gw altogether (unless you really want a B2BUA) and take a look at using repro (SIP proxy) as your starting ground.  There is already logic in repro to forward/fork requests and to gather their responses for sending back to the request originator.

Regards,
Scott


On Tue, Feb 18, 2014 at 3:19 AM, leung terry <terryleung83@xxxxxxxxx> wrote:
Hi all,

I am new to here. I am now reading the document and code.
I am going to have a new project which involves forking an incoming request.
It is not supposed to be a B2BUA. The incoming and outgoing invite should have the same To/From/Call-Id. 

I tried to read the ichat-gw included in the source code. However, it is actually a B2BUA case and I cannot find any example doing proxy by using dum layer api or forking incoming invite.

My question, for such case, I should have 3 Session object per call?
I am not sure if I am correct or not. I just put my understanding based on the ichat-gw I read and I think I should do the following modification in order to made it work for my case.

When I receive the first invite, I should receive onNewSession and then onOffer in the B2BSession. 
Then I should now create two peer by creating two more B2BSession(createNewPeer in ichat-gw) and run mDum.makeInviteSession with the use of the incoming message with the use of another overloaded version 

      SharedPtr<SipMessage> makeInviteSession(const NameAddr& target, InviteSessionHandle sessionToReplace, const SharedPtr<UserProfile>& userProfile, const Contents* initialOffer, AppDialogSet* ads = 0);

I should change the RURI/Route header/.... accordingly in the two different makeInviteSession

Am I correct? 


Best Regards,
Terry

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/