[Megaco] Megaco protocol
Tushar Paithankar <p.tushar99@gmail.com> Fri, 09 May 2014 11:03 UTC
Return-Path: <p.tushar99@gmail.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 337ED1A027F for <megaco@ietfa.amsl.com>; Fri, 9 May 2014 04:03:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.349
X-Spam-Level:
X-Spam-Status: No, score=-0.349 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3kQfEbUROaal for <megaco@ietfa.amsl.com>; Fri, 9 May 2014 04:03:20 -0700 (PDT)
Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 297071A024B for <megaco@ietf.org>; Fri, 9 May 2014 04:03:19 -0700 (PDT)
Received: by mail-we0-f171.google.com with SMTP id w62so3744782wes.2 for <megaco@ietf.org>; Fri, 09 May 2014 04:03:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=ZRHHyNlci8JAdFe0cB37DaWl2eSHSqq8ZoUu7BCQWP4=; b=vSFcy6hHhfyFhK0YTPfb4LwqzppE/xRVu2aQF4S17P3SKgBWf1Jl+8p8BZNz7Br4Qn NQK0a4O1f9xgUcwIGx59GDq8gy5Vc0Kk1PAEwGdNCTmXgI5o18wIFu0AUPyvgYDGxEZF oKcCqjfFey5LbT8JDqxjAhLHLkzM2RXrN3s+4LvAV7dLUSEzKJPCROVn/XtqYuskn3g7 89/vJo3m7tGN/HuRUu5XbMrc7bYyl5Z7ZMdGOJJvimuFxahu8QNgb6juyMCFtANMpENg haAuNOD4HAMRwrmZwWJcmkP8MqNVNxpviSJQNvpGhSAsJdVFcci3wP4832QzcAjGq4B1 wD6Q==
MIME-Version: 1.0
X-Received: by 10.194.91.175 with SMTP id cf15mr7957664wjb.5.1399633394917; Fri, 09 May 2014 04:03:14 -0700 (PDT)
Received: by 10.216.246.70 with HTTP; Fri, 9 May 2014 04:03:14 -0700 (PDT)
Date: Fri, 09 May 2014 16:33:14 +0530
Message-ID: <CAE1+-sC+kce5Gyjw4E=85xhnh_Jh+16EeYfOqvJL-GEepNke2Q@mail.gmail.com>
From: Tushar Paithankar <p.tushar99@gmail.com>
To: megaco <megaco@ietf.org>
Content-Type: multipart/alternative; boundary="047d7bfcebc651efa004f8f58b4c"
Archived-At: http://mailarchive.ietf.org/arch/msg/megaco/cW29fS5PrLg068QsgWV2pfm5iYY
Subject: [Megaco] Megaco protocol
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: p.tushar99@gmail.com
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco/>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 May 2014 11:03:21 -0000
Hi all,
I am new to MEGACO protocol, I tried to go through the Draft for same,
I have to implement a protocol between MG and MGC, here i have some
questions
1. How may service change Request we have to send from MG to MGC, is it
nessesory to send Service change
Request for each channel. Or only one Service change request between MG
and MGC at start.
I will come up with more question too,
Thanks
Tushar
- [Megaco] Megaco protocol Tushar Paithankar
- Re: [Megaco] Megaco protocol Christian Groves