Ok thanks! Now I understand the differences. It think more people would benefit from this if this can be found somewhere in the documentation.

For my purpose I will stick to using B2BUA because it will not do any media relaying (no delays or possible bandwith/performance issues). It makes sense! I tried modifying the invite_req.hdrs before calling connectCallee(). This works flawlessly (off course it does ;-))

Thanks again!

Tom

-------- Originele bericht --------
Onderwerp: Re: [Sems] B2BUA vs. B2ABUA
Van: Stefan Sayer <[email protected]>
Aan: Tom van der Geer <[email protected]>
CC: sems <[email protected]>
Datum: 12-1-2009 13:15
Hello,

o Tom van der Geer [01/12/09 12:49]:
Hi *,

Could anybody point me to a location where I can find more information about the differences between B2BUA and B2ABUA which are represented by AmB2BSession and AmB2ABSession in SEMS? Google has not helped so far and the documentation in these classes has not been helpful either...
B2ABUA is just from the class name for "B2BUA with audio relay", thus the 'A'. AmB2BSession is for b2bua with no media (only signaling): one dialog on each call leg, but the SDPs are passed from one leg to the other. AmB2ABSession is two dialogs and sessions, unrelated SDP, and the audio is connected.

Still, the AmB2BSession is designed such that SEMS can accept the call first, and later send an invite to the callee, and reinvite the caller leg (e.g. ann_b2b).

I'm developing an application which is currently using AmB2BCallerSession and AmB2BCalleeSession inheritance, but in the method AmB2BCallerSession::connectCallee() I'm missing a parameter to add extra header(s). I noticed that AmB2ABCallerSession also has a connectCallee method which does have a headers parameter.
just set/modify invite_req.hdrs before connectCallee (e.g. removeHeader(invite_req.hdrs, "P-App-Name");)

in B2BSession, the INVITE req on the second leg is constructed from the first INVITE (invite_req), in B2ABSession, a completely unrelated request is built, thus the differing parameters to connectCallee. But you are right that these two should better be combined into one class which would make switching between the two much easier.

Stefan


But before I switch to using the B2AB functionality I'd like to know if this fit my needs or that I'm exchanging one problem with (more) other problems...
Thanks in advance!
Regards,

Tom
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems


_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems

Reply via email to