[Sip] Translation address mechanism from megaco to sip and vice versa

"Jati Kalingga Praja" <king.of.kalingga@gmail.com> Fri, 18 January 2008 17:14 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 1JFunN-0004bg-A8; Fri, 18 Jan 2008 12:14:21 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JFunM-0004Zh-19 for sip-confirm+ok@megatron.ietf.org; Fri, 18 Jan 2008 12:14:20 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFunL-0004ZX-MO for sip@ietf.org; Fri, 18 Jan 2008 12:14:19 -0500
Received: from fg-out-1718.google.com ([72.14.220.153]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JFunL-00029D-8A for sip@ietf.org; Fri, 18 Jan 2008 12:14:19 -0500
Received: by fg-out-1718.google.com with SMTP id 16so1175288fgg.41 for <sip@ietf.org>; Fri, 18 Jan 2008 09:14:18 -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=a2evky9GhG7F2MygMZYA/U1KToVd5UhOhDev5pXaWIg=; b=PrDYmX2Lgv4yL9HQCYOvwNQT+/3Dx91BvTpd32Pi5+oOHzJNWcMi8I7vjCm8QiJI2T8z05vdXgBDJb/lT4h2AOz0sz9MWwICCXadWna1Gr13ylYEReqaAGqg4hmtrnjdrofcfkSNdexjukzRfIl/nyRwbphSfC8+sI8N3NOAtnM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=UkJKW/zeqkfXtmJaVFFOZd7pGHTie60LzeOfcKNC5t2XgcopGeHaOjqXeKWzMNmEU0iD6K33KU5M1Nyu7ry4SlDHjOBTO3gaNYF0puaDaPp1FMseJ7J4OgI+VyeDBWcO5jXw4I8E5QWyvqDXTsINR6nV1pSCI/qTQnfdm5H4W0k=
Received: by 10.86.71.1 with SMTP id t1mr3260413fga.69.1200676458256; Fri, 18 Jan 2008 09:14:18 -0800 (PST)
Received: by 10.86.96.2 with HTTP; Fri, 18 Jan 2008 09:14:18 -0800 (PST)
Message-ID: <fff358f70801180914k6347fcb5rdff0eeb58de77b61@mail.gmail.com>
Date: Sat, 19 Jan 2008 00:14:18 +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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc:
Subject: [Sip] Translation address mechanism from megaco to sip and vice versa
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="===============2123288452=="
Errors-To: sip-bounces@ietf.org

Hi,

right now, i'm studying about interworking between megaco and sip. I would
like to know about translation address mechanism from megaco to sip and vice
versa. I've been searching on internet, but i haven't found the right
reference. Anyone can help me?

Thx before in advance

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