Hi Tanmay, Tanmay Zargar wrote: > > Hello all, > > Firstly thanks to Bert for getting back on my earlier queries. > I have some more doubts regarding the use of B2BUA as a service > execution controller. > > >Since a B2BUA cannot *route* the signaling messages (since it is a UA > and not a proxy), does it have to be configured with some outbound > proxy?
The UAC side of the B2BUA can use the "normal" procedures defined in the SIP spec for determining where to send a request. I can use an outbound proxy or not. > > >Can a B2BUA record-route? If not, how does it remain in the signaling > path between the end points for the entire duration of the call? > UAs don't record-route. A B2BUA remains in the signaling path because it's a signaling endpoint on two calls. Now the other two endpoints may be exchanging media with each other but from the signaling point of view, they're both in a call with the B2BUA. > >If the service logic is going to be built on top of a B2BUA, does the > end-point have to be configured with this B2BUA? > The endpoint using the service provided by the B2BUA does have to establish a session with the B2BUA. How it knows to contact the B2BUA is just a function of the service. For example, to use a pre-paid or post-paid calling card in the US the user must dial an 800 number in many cases. The user knows about this aspect of the service because she was told this by the service provider. SIP proxies can have this kind of knowledge too, minimizing the knowledge an end user is required to have to access different services. The proxies would "route" requests to the service entity based on knowledge they have. I hope this helps, Bert > Thanks, > Tanmay Z. > > > _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
