Re: [Sipping] rtp seq and timestamp

"Ingemar Johansson S" <ingemar.s.johansson@ericsson.com> Wed, 04 June 2008 06:29 UTC

Return-Path: <sipping-bounces@ietf.org>
X-Original-To: sipping-archive@optimus.ietf.org
Delivered-To: ietfarch-sipping-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 94B883A68FC; Tue, 3 Jun 2008 23:29:55 -0700 (PDT)
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 950E23A67F9 for <sipping@core3.amsl.com>; Tue, 3 Jun 2008 23:29:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level:
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WBxIoEgdQtJx for <sipping@core3.amsl.com>; Tue, 3 Jun 2008 23:29:53 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 0DC093A6C52 for <sipping@ietf.org>; Tue, 3 Jun 2008 23:29:43 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 9BF50206E3; Wed, 4 Jun 2008 08:29:46 +0200 (CEST)
X-AuditID: c1b4fb3e-ac194bb000004ec0-22-4846365a9ded
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 763C220477; Wed, 4 Jun 2008 08:29:46 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 4 Jun 2008 08:29:46 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 04 Jun 2008 08:29:45 +0200
Message-ID: <026F8EEDAD2C4342A993203088C1FC0507B84A90@esealmw109.eemea.ericsson.se>
In-Reply-To: <mailman.35.1212519606.26638.sipping@ietf.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: rtp seq and timestamp
thread-index: AcjFrFPOAwJP+dsIRDC07mL8IgmwhQAXpu4Q
References: <mailman.35.1212519606.26638.sipping@ietf.org>
From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: sipping@ietf.org
X-OriginalArrivalTime: 04 Jun 2008 06:29:46.0232 (UTC) FILETIME=[61C5CF80:01C8C60C]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sipping] rtp seq and timestamp
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

Hi

This question probably fits better in the avt wg.

The RTP sequence number should normally increase by one for each packet.

The timestamp should also be monotonically increasing but in some cases
(retransmission) packets may have timestamps that are smaller than the
previous.
Your case below however indicates that the timestamp is reinitialized to
a new value. An RTCP sender report in the A to B direction will then
reveal the NTP (wallclock) time that the packets was transmitted.


Ingemar

> -----Original Message-----
> From: sipping-bounces@ietf.org 
> [mailto:sipping-bounces@ietf.org] On Behalf Of 
> sipping-request@ietf.org
> Sent: den 3 juni 2008 21:00
> To: sipping@ietf.org
> Subject: Sipping Digest, Vol 50, Issue 1
> 
> Send Sipping mailing list submissions to
> 	sipping@ietf.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www.ietf.org/mailman/listinfo/sipping
> or, via email, send a message with subject or body 'help' to
> 	sipping-request@ietf.org
> 
> You can reach the person managing the list at
> 	sipping-owner@ietf.org
> 
> When replying, please edit your Subject line so it is more 
> specific than "Re: Contents of Sipping digest..."
> 
> 
> Today's Topics:
> 
>    1. rtp seq and timestamp ( ??? )
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 3 Jun 2008 16:13:02 +0800
> From: " ??? " <sammanengineer@gmail.com>
> Subject: [Sipping] rtp seq and timestamp
> To: sip@ietf.org, "IETF Sipping List" <sipping@ietf.org>
> Message-ID:
> 	<2374a5fb0806030113v2049961cufbc7a4988bb005a0@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Hi Guys
> 
>    I have a question as following
> 
> A and B are already connented , A sent a re-invite to B, and 
> the three-way handshake  is ok after it, the rtp (A to B)'s 
> seq no is larger than the before  and the SSRC
> is different I think it is ok , but the   timestamp is samller than
> the before I do not know whther it is ok or not
> 
> can anyone give me some advices
> 
> Thanks
> 
> Samman
> 
> 2008-6-3
> 
> --
> msn:yongguangsun@hotmail.com <msn%3Ayongguangsun@hotmail.com>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> https://www.ietf.org/mailman/private/sipping/attachments/20080
> 603/ef8cfba1/attachment-0001.htm 
> 
> ------------------------------
> 
> Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP 
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sip@ietf.org for new developments of core SIP
> 
> End of Sipping Digest, Vol 50, Issue 1
> **************************************
> 
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP