IETF Logo Mail Archive

RE: [Sip] SIPit 21 : Topics that attendees argued about

"Christer Holmberg" <christer.holmberg@ericsson.com> Fri, 23 November 2007 10:50 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvW6j-0001t3-Fx; Fri, 23 Nov 2007 05:50:01 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IvW6h-0001sg-MF for sip-confirm+ok@megatron.ietf.org; Fri, 23 Nov 2007 05:49:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvW6h-0001ru-BH for sip@ietf.org; Fri, 23 Nov 2007 05:49:59 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IvW6d-000406-VA for sip@ietf.org; Fri, 23 Nov 2007 05:49:59 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id A2D68207AC; Fri, 23 Nov 2007 11:49:53 +0100 (CET)
X-AuditID: c1b4fb3e-aee9fbb00000459d-fb-4746b051a24a
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 81C96201DD; Fri, 23 Nov 2007 11:49:53 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 23 Nov 2007 11:49:53 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] SIPit 21 : Topics that attendees argued about
Date: Fri, 23 Nov 2007 11:48:19 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DFEE0893@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] SIPit 21 : Topics that attendees argued about
Thread-Index: AcgtLwEk/s+lzhobQfu/gKC4j30tTAAj1rye
References: <82FF9D7A-F7B4-4C06-A0CB-5CA74504413E@nostrum.com> <2C7074A1A040E54DA31B3E72C052FD520938C6DC@BLR-EC-MBX04.wipro.com> <CA9998CD4A020D418654FCDEF4E707DF0339ED44@esealmw113.eemea.ericsson.se> <67A74E87-B494-445B-9D11-B998B269EF81@softarmor.com>
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Dean Willis <dean.willis@softarmor.com>
X-OriginalArrivalTime: 23 Nov 2007 10:49:53.0290 (UTC) FILETIME=[942A5EA0:01C82DBE]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: sip@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

Hi,

>> I agree with Ravi.
>>
>> Eventhough you in theory is supposed to be able to receive what you
>> offer - no matter what you get in the answer - I think that in real 
>> life the only codecs that participants will be prepared to send/receive are
>> the ones sent both in the offer and the answer. That is also the 
>> reason
>> why the answer normally doesn't contain additional codecs - it mostly
>> contains a subset of the codecs in the offer.
>So how do you deal with asymmetric encoding?

You may use different codecs in each direction (eventhough I don't think it happens very often), as long as all codecs have been present in both the offer and the answer.

Regards,

Christer

 



_______________________________________________
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

v2.23.0 | Report a Bug | By Email