Re: [Sipping] Question regarding SDP 'M' Line

To: "Jayantheesh Srimushnam" <jayanteeshs at hcl.in>

Subject: Re: [Sipping] Question regarding SDP 'M' Line

From: "Harsha. R" <harsha.ramanagoudra at gmail.com>

Date: Thu, 17 Apr 2008 09:55:20 +0530

Delivered-to: ietfarch-sipping-web-archive at core3.amsl.com

Delivered-to: sipping at core3.amsl.com

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=tTZ2iGBSwsUNB7CHJJhMJxU2eXuu3QQ6/5aVa6Nf1mY=; b=r2PZU2K5yg72eA9axyGb6bDCPRXxawz7mbqTU4bjMQJ6OOL3vxu4guniURIB7LysJj7KgZmALcBv9h7jRPGYrOMJ9NUWFASjZxz+/1XcTBnjb5G6RUO5Xi3LVz6XLW4RfJYaYDzVV88BiJi5Uyr6f+6gavJFfsWhCFekwBRLGTs=

Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=sd+21F4sA1hP86c0lOV4xKXp9PJacEF4P1adkf3mrk4J8bsk3OGUMdR1ji81OO9p0DCRUzv1WBmuzU8lA+AmLzUN8x1BbfLvNrvFA7wzORi38oq2oY+Yz8PTzPXyX3WrBMIjcB+d0De12255ldyN6Q3TZkjnyAkFiNGkD9LTa+o=

In-reply-to: <66E8AEE9980BB44CA5FCAD39EBA56AC60437112B at CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>

List-help: <mailto:sipping-request@ietf.org?subject=help>

List-id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>

List-post: <mailto:sipping@ietf.org>

List-subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>

List-unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>

References: <66E8AEE9980BB44CA5FCAD39EBA56AC60437112B at CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>

Sender: sipping-bounces at ietf.org

It depends on what you want. If you want to retain audio while sending image, the second example is correct.

The first example. i think violates protocol. If you want to re-use an existing media slot, you should have set deleted the media stream first(by setting port to 0; by setting the port to 0 like this, you will loose audio.) before re-using it.

RFC 3264 section 8.1

8.1 Adding a Media Stream

   New media streams are created by new additional media descriptions
   below the existing ones, or by reusing the "slot" used by an old
   media stream which had been disabled by setting its port to zero.

   Reusing its slot means that the new media description replaces the
   old one, but retains its positioning relative to other media
   descriptions in the SDP

Regards

Harsha

On 16/04/2008, Jayantheesh Srimushnam <jayanteeshs at hcl.in> wrote:

Hi All,

While adding a new media stream is it MUST to add a new 'M' line in the SDP or existing 'M' line can be replaced with the new one.

Please go through the below specified example and clarify me which is the correct way of implementing?

Example 1:

========

Initial INVITE:

m=audio 7100 RTP/AVP 0 101

a=rtcp:7101

a=sendonly

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

Re-Invite:

m=image 20112 udptl t38

a=T38FaxVersion:0

a=T38MaxBitRate:1440

Example 2:

========

Initial INVITE:

m=audio 7100 RTP/AVP 0 101

a=rtcp:7101

a=sendonly

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

Re-Invite:

m=audio 7100 RTP/AVP 0 101

a=rtcp:7101

a=sendonly

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

m=image 5080 udptl t38

c=IN IP4 10.101.210.30

a=T38FaxVersion:0

Thanks,

Jayantheesh

_______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors at cs.columbia.edu for questions on current sip Use sip at ietf.org for new developments of core SIP