On the UAS Side the local URI and remote URI are related with from and to header.
Section 12.1.1 The remote URI MUST be set to the URI in the From field, and the local URI MUST be set to the URI in the To field. For the UAC which is building and sending request on an existing dialog, primarily uses a different block of information saved in dialog, called Remote Target URI to build the request URI. Section 12.2.1.1 The UAC uses the remote target and route set to build the Request-URI and Route header field of the request. If the route set is empty, the UAC MUST place the remote target URI into the Request-URI. The UAC MUST NOT add a Route header field to the request. Hope this helps. Regards, Indresh -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Corbe Sent: Wednesday, March 14, 2007 3:25 PM To: [email protected] Subject: [Sip-implementors] Question about dialogs ... A dialog contains certain pieces of state needed for further message transmissions within the dialog. This state consists of the dialog ID, a local sequence number (used to order requests from the UA to its peer), a remote sequence number (used to order requests from its peer to the UA), a local URI, a remote URI, Is that a request URI? I doubt its the URI from the From: or To: headers. -Daniel _______________________________________________ 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
