RE: [Sip] B2BUA & Max-Forwards

For UAC (a) UAS (c) is the intended called party in the call. We have to define the intended party in a call when a B2BUA is involved. B2BUA IS an intermediate network element. It acts as some kind of a controller for a domain. It is not the called party in any call.

Regards

Padma

>From: Adam Roach

>To: "'Roy, Radhika R, ALASO'" , Adam Roach

>CC: sip@ietf.org

>Subject: RE: [Sip] B2BUA & Max-Forwards

>Date: Wed, 4 Dec 2002 16:58:14 -0600

> > UAC(a)--->UAS(b)===[application logic here]===UAC(b)--->UAS(c)

> >

> > [RRR] I like to know who has been the called party when

> > UAC(a)) sent the INVITE message? Has it been UAS(b) or UAS(c)?

>I'm going to first need to clarify your question.

>The question I will answer is: "If an INVITE is sent through the

>network described in this diagram, what is the value of the

>Request-URI when UAC(a) sends it?"

>The answer is: it depends. In general, yes, it will probably be

>either of UAS(b) or UAS(c).

> > [RRR] If the answer is UAS(c), the question is: Why the call

> > has been routed to UAS(b) by UAC(a) in the first place?

>The most obvious of several plausible answers is: UAC(a)

>has UAS(b) configured as a local outbound proxy.

> > [RRR] If the answer is UAS(b), probably UAC(a) does not care.

>About what?

>/a

>_______________________________________________

>Sip mailing list https://www1.ietf.org/mailman/listinfo/sip

>This list is for NEW development of the core SIP Protocol

>Use sip-implementors@cs.columbia.edu for questions on current sip

>Use sipping@ietf.org for new developments on the application of sip