Re: [sipcore] UAC or UAS
Brett Tate <brett@broadsoft.com> Mon, 09 December 2013 16:23 UTC
Return-Path: <brett@broadsoft.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1FFC1ADFCC for <sipcore@ietfa.amsl.com>; Mon, 9 Dec 2013 08:23:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 95YcMzKPuSKT for <sipcore@ietfa.amsl.com>; Mon, 9 Dec 2013 08:23:20 -0800 (PST)
Received: from smtpout01.partnerhosted.com (smtpout01.partnerhosted.com [173.225.22.203]) by ietfa.amsl.com (Postfix) with ESMTP id C9E7B1ADFC8 for <sipcore@ietf.org>; Mon, 9 Dec 2013 08:23:20 -0800 (PST)
Received: from CASUMHUB03.citservers.local (172.16.98.219) by smtpedge.partnerhosted.com (172.16.98.247) with Microsoft SMTP Server (TLS) id 14.2.247.3; Mon, 9 Dec 2013 08:25:11 -0800
Received: from MBX08.citservers.local ([fe80::2564:652:8dc8:caae]) by CASUMHUB03.citservers.local ([::1]) with mapi id 14.02.0247.003; Mon, 9 Dec 2013 08:25:11 -0800
From: Brett Tate <brett@broadsoft.com>
To: "Klatsky, Carl" <Carl_Klatsky@cable.comcast.com>, "'sipcore@ietf.org'" <sipcore@ietf.org>
Thread-Topic: UAC or UAS
Thread-Index: Ac706x/ThtcF14MnRhWvlCKibdf7BAAA9unQ
Date: Mon, 09 Dec 2013 16:25:10 +0000
Message-ID: <576A8B541C219D4E9CEB1DF8C19C7B881A06D2ED@MBX08.citservers.local>
References: <6C15A6B88541034E912E94C2D8BC3E87F770AA11@PACDCEXMB12.cable.comcast.com>
In-Reply-To: <6C15A6B88541034E912E94C2D8BC3E87F770AA11@PACDCEXMB12.cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.16.98.77]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [sipcore] UAC or UAS
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Dec 2013 16:23:23 -0000
> In this exchange between A and B: > > B sends A an INVITE with no SDP > A replies with a 200 OK with SDP > B replies with an ACK with SDP > > Is A the UAS or UAC in this scenario? A is the UAS. RFC 3261 section 6 contains the definitions. "User Agent Client (UAC): A user agent client is a logical entity that creates a new request, and then uses the client transaction state machinery to send it. The role of UAC lasts only for the duration of that transaction. In other words, if a piece of software initiates a request, it acts as a UAC for the duration of that transaction. If it receives a request later, it assumes the role of a user agent server for the processing of that transaction." "User Agent Server (UAS): A user agent server is a logical entity that generates a response to a SIP request. The response accepts, rejects, or redirects the request. This role lasts only for the duration of that transaction. In other words, if a piece of software responds to a request, it acts as a UAS for the duration of that transaction. If it generates a request later, it assumes the role of a user agent client for the processing of that transaction." If you have other general SIP questions, you might want to post them to sip-implementors. https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
- Re: [sipcore] UAC or UAS Brett Tate
- [sipcore] UAC or UAS Klatsky, Carl