[Sip] SIP2Megaco Busy

"Jati Kalingga Praja" <king.of.kalingga@gmail.com> Thu, 03 January 2008 18:57 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 1JAVGH-0007bx-Jx; Thu, 03 Jan 2008 13:57:49 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JAVGG-0007be-Dy for sip-confirm+ok@megatron.ietf.org; Thu, 03 Jan 2008 13:57:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JAVGG-0007bT-3l for sip@ietf.org; Thu, 03 Jan 2008 13:57:48 -0500
Received: from fg-out-1718.google.com ([72.14.220.159]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JAVGF-00051Q-Iy for sip@ietf.org; Thu, 03 Jan 2008 13:57:48 -0500
Received: by fg-out-1718.google.com with SMTP id 16so3398383fgg.41 for <sip@ietf.org>; Thu, 03 Jan 2008 10:57:46 -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=cGk+Nu4rEUSVZZA9cyGSuqJvmo6Rr/sqqEPfK0qcFPE=; b=xNKTRopeejXXFzgAMoGQAbfnSLEHhXOn2ADiNh0nYeFDQYmJJhNLvnygZ3X1bnytsb1jJEL6PNVxfcYWPmy5APyffQWyjMBLmTYGfdRv0A0cpSplL+xoZnhG+WE5xBH3uWYd0bS2/ZTQxN1/+BtLgBpRhlOrI54p/c/PUcHGZAQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=JjPlKyfHQC7VYkxz3FXMulCTqwAOZk8BKgIBKL9z18NJBKpdffRVb9IHErDj56lIB0Db0RxdmvLK+BnOIrAj2vTNCjVfMF4tCYX3fr+oU5dB5CVFUMnkBjnJmpYbbRf3Qv4XblYl/9uvmml3ID6D7FfHn0BlfaGdo15sUde7czs=
Received: by 10.86.99.9 with SMTP id w9mr15918812fgb.44.1199386666795; Thu, 03 Jan 2008 10:57:46 -0800 (PST)
Received: by 10.86.62.3 with HTTP; Thu, 3 Jan 2008 10:57:46 -0800 (PST)
Message-ID: <fff358f70801031057h66ce3d8ckc5991d7e39673fbe@mail.gmail.com>
Date: Fri, 4 Jan 2008 01:57:46 +0700
From: "Jati Kalingga Praja" <king.of.kalingga@gmail.com>
To: sip@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Subject: [Sip] SIP2Megaco Busy
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>
Content-Type: multipart/mixed; boundary="===============0161668270=="
Errors-To: sip-bounces@ietf.org

Hi,,

I'm new to this mailing list. Right now, i'm studying about interworking
between megaco and sip.
I simulated a call from SIP phone to Analog phone which was busy. You can
download the captured data using ethereal in here:
http://www.4shared.com/file/33781721/3b2ac786/4577020ke4580220busy.html, and
you can view the callflow by writing "*(megaco and ip.addr==10.14.32.186) or
(sip and ip.addr==10.14.32.185) or rtp*" in filter textbox.

I have a few questions about that captured data :
1. Why did SIP Phone send a CANCEL twice?
2. What did line 2115 mean?

I hope my questions are all clear to be understood,,,because i'm not too
good in english.
Hopefully, you guys can help me.

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