Thanks everyone for the thorough replies. I'm posting a somewhat related but separate followup about stateless proxies in a moment.
-Adam On 4/25/06, Paul Kyzivat <[EMAIL PROTECTED]> wrote: > > > > Voipers Portugal wrote: > > It should be the same UA otherwise you won't be able to bind the 5060 > port > > to the other UA. > > You seem to believe that a UA must be able to bind to a port. But the > notion of a UA in 3261 is much more abstract than that. (See section 6 > definition.) > > I usually think of a UA as being synonymous with a contact URI, used to > REGISTER and/or in a dialog establishing request or response. (That > isn't the full picture, because it doesn't cover requests that don't > have contact addresses.) > > IMO a phone that provides two "lines" by registering twice contains two > UAs. > > But it really isn't terribly important. What is important is that a > single server can register multiple times and then determine which > registration an incoming request is for. > > It works for servers that don't register too. A good example that is > widely deployed is a PSTN gateway. > > Paul > > > Jose Simoes > > > > On 4/25/06, Dale R. Worley <[EMAIL PROTECTED]> wrote: > > > >>On Tue, 2006-04-25 at 10:20 -0400, Kedar Karmarkar wrote: > >> > >>>Is it possible to do? > >>> > >>>UA1 ---+ > >>>UA2 ---+ ------ port 5000 <---- to network ------> > >>>UA3 ---+ > >>> > >>>I am assuming they are three users? > >> > >>Yes, it is possible to separate INVITEs according to the user part of > >>the request-URIs, and route each INVITE to what is effectively a > >>different user agent. Although in that case, people generally *call* > >>the whole system a single user agent. But that does not make any > >>difference, really. (Of course, if the user agent(s) register with a > >>registrar, each user name has to be registered individually.) > >> > >>Dale > >> > >>--- > >>interop.pingtel.com -- the public SIP phone interoperability test server > >> > >>_______________________________________________ > >>Sip-implementors mailing list > >>[email protected] > >>https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > >> > > > > _______________________________________________ > > Sip-implementors mailing list > > [email protected] > > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
