[Sip] Translation Megaco 2 SIP

"Jati Kalingga Praja" <king.of.kalingga@gmail.com> Wed, 09 January 2008 19:00 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 1JCgAD-0008JV-MH; Wed, 09 Jan 2008 14:00:33 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JCgAB-0008IB-NJ for sip-confirm+ok@megatron.ietf.org; Wed, 09 Jan 2008 14:00:31 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCgAB-0008Hy-87 for sip@ietf.org; Wed, 09 Jan 2008 14:00:31 -0500
Received: from fg-out-1718.google.com ([72.14.220.159]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCgAA-0006Sj-1r for sip@ietf.org; Wed, 09 Jan 2008 14:00:31 -0500
Received: by fg-out-1718.google.com with SMTP id 16so361599fgg.41 for <sip@ietf.org>; Wed, 09 Jan 2008 11:00:29 -0800 (PST)
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:mime-version:content-type; bh=wx+/RiTjtYfXbVMrRXDvZwjaMuL44ZYLPuFhesNlUwo=; b=v/Q5DdmMyEs5yfxTm/TSt42GTLAJUxUd0GKPj0AEp+AVWIhU6nmpj5GdmzN8J5irdRS6LxhTjMLkE6Dp6fOF/Fw8a22Cg3fhNXeLki+92CkgAKJBVa9wXKNq+X5t4Jcd4dvCrk5hayx/mP3uk3jsyBicPcqOpHk3h4oxRfHg1xg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=HKU8cStWisyNSGu5GIpoeeCGoPTs+mPXPlsaLwnMDwVvuEVAEfnfu6Gg8Hk9TOMaBYs5OK+2VXajyZNGdy12hC5Pei7tWL6j7AU76UDpl/CLeqLWF8p4Z8LsWHQW9o01I2SqH9pnEZWsTBFq+8e9wtQSOvaXhNNlcWhfWf82fNM=
Received: by 10.86.86.12 with SMTP id j12mr927404fgb.68.1199905229368; Wed, 09 Jan 2008 11:00:29 -0800 (PST)
Received: by 10.86.61.5 with HTTP; Wed, 9 Jan 2008 11:00:29 -0800 (PST)
Message-ID: <fff358f70801091100xfbafd67wb801ea1864bcecc7@mail.gmail.com>
Date: Thu, 10 Jan 2008 02:00:29 +0700
From: "Jati Kalingga Praja" <king.of.kalingga@gmail.com>
To: sip@ietf.org, sip-implementors@lists.cs.columbia.edu, megaco@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_10989_26389566.1199905229342"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ba883ba659fcd62a05a0ed0aea6f612
Cc:
Subject: [Sip] Translation Megaco 2 SIP
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,,

Right now, i'm studying about interworking between megaco and sip. Here i
attached the call flow diagram which i have concluded from my study. But i
found some questions here :
1. Look at the attached file, if i want to count delay translation from
megaco to sip "INVITE" message, which megaco message that i must use as the
time reference to count the delay?Is it notify digits or notify digits
response or add response?
2. Loot at the part of before the RTP, there is
3. Loot at the end part of the attached file, theoritically, when the analog
phone onhooked first, MGC must send the BYE message to the SIP phone, don't
it?,,,then, why did the SIP phone sent the BYE message?

Thx before in advance,,,

Best Regards,


Jati
_______________________________________________
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