From mailman-bounces@ietf.org  Wed Dec  1 09:04:25 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00314
	for <megaco-archive@lists.ietf.org>; Wed, 1 Dec 2004 09:04:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZSfV-0002HE-Mm
	for megaco-archive@lists.ietf.org; Wed, 01 Dec 2004 06:29:09 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: megaco-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.22647.1101898163.3553.mailman@lists.ietf.org>
Date: Wed, 01 Dec 2004 05:49:23 -0500
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for megaco-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
megaco@ietf.org                          rFKd      
https://www1.ietf.org/mailman/options/megaco/megaco-archive%40lists.ietf.org


From megaco-bounces@ietf.org  Wed Dec  1 14:30:09 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14456
	for <megaco-archive@lists.ietf.org>; Wed, 1 Dec 2004 14:30:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZZQw-0005Px-Hw; Wed, 01 Dec 2004 13:42:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZYZ5-0003Si-Ox
	for megaco@megatron.ietf.org; Wed, 01 Dec 2004 12:46:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03627
	for <megaco@ietf.org>; Wed, 1 Dec 2004 12:46:53 -0500 (EST)
Received: from ihemail2.lucent.com ([192.11.222.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZYeG-0006bI-7E
	for megaco@ietf.org; Wed, 01 Dec 2004 12:52:28 -0500
Received: from wink.ho.lucent.com (h135-112-126-3.lucent.com [135.112.126.3])
	by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id iB1Hk8DR016916
	for <megaco@ietf.org>; Wed, 1 Dec 2004 11:46:09 -0600 (CST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id MAA22951; Wed, 1 Dec 2004 12:46:07 -0500 (EST)
Received: from [135.112.125.177] by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id MAA22947; Wed, 1 Dec 2004 12:46:06 -0500 (EST)
Message-ID: <41AE035D.2040408@bell-labs.com>
Date: Wed, 01 Dec 2004 12:46:05 -0500
From: Troy Cauble <troy@bell-labs.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: 7bit
Subject: [Megaco] descriptor order and error descriptors
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit


Hi,

I recently ran into the exchange below.
I think it points out a weakness in the protocol
w.r.t. associating descriptor level errors with
the appropriate descriptor.

I could find nothing in the docs that say a response's
descriptors should be in the same order as the request's
descriptors.

I could find nothing in the docs that say the AuditValue's
response's descriptors should be in the same order as the
request tokens.  In fact, the V2 doc has examples of AuditValue
returning descriptors in an order other than the request tokens.

I didn't check to see if there are similar issues in the other
lists that an errorDescriptor can be used in.  It seems likely
though.

Forcing the order to be maintained and using that for context
is ugly, IMO.  But it's probably the minimal change solution.
The real problem is lack of info in the errorDescriptor.
(Relying on the text of the error descriptor field
would also be a bad idea, IMO.)

-troy




MEGACO/1 [135.112.125.109]:55555
    Transaction = 50007 {
       Context = - {AuditValue = aaln/2 {
          Audit{ Packages, Statistics , DigitMap, Signals, Events, Media
    }}}}

MEGACO/1 [135.112.125.214]
Reply = 50007 {
   Context = - {
     AuditValue = aaln/2 {
       Media {
         TerminationState {
           Buffer = OFF},
         Stream = 1 {
           LocalControl {

           }
         }
       },
       Events = 2222 {
         al/of
       },
       Error = 447 { "Descriptor not legal in this command" },
       Error = 447 { "Descriptor not legal in this command" },
       Packages {
         g-1,
         tonegen-1,
         tonedet-1,
         dg-1,
         dd-1,
         cg-1,
         cd-1,
         al-1,
         ct-1,
         rtp-1,
         tdmc-1,
         ftmd-1,
         ctyp-1,
         an-1,
         bau-1,
         aau-1,
         xal-1

       },
       Error = 501 { "Not implemented" }
     }
   }
}

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Thu Dec  2 02:55:43 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16963
	for <megaco-archive@lists.ietf.org>; Thu, 2 Dec 2004 02:55:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZlYF-0008Hn-6E; Thu, 02 Dec 2004 02:38:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZksr-0000WH-2V
	for megaco@megatron.ietf.org; Thu, 02 Dec 2004 01:56:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27018
	for <megaco@ietf.org>; Thu, 2 Dec 2004 01:56:07 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZkyK-0001YV-EY
	for megaco@ietf.org; Thu, 02 Dec 2004 02:01:48 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iB26tZr18090
	for <megaco@ietf.org>; Thu, 2 Dec 2004 01:55:35 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <XQM2PS5N>; Thu, 2 Dec 2004 01:55:35 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536010B1B28@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Troy Cauble <troy@bell-labs.com>, megaco@ietf.org
Subject: RE: [Megaco] descriptor order and error descriptors
Date: Thu, 2 Dec 2004 01:55:19 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

Wouldn't the command processing stop at the first error?

I believe the intent is to enforce order, since that is how the sender can
align where errors occurred with the command.  Christian may be able to
provide more detail on the history of how this was intended to work...

Whatever we decide, we should document the fix into the Implementors' Guides
for V1 and V2, and fix the text in V3.

Kevin 

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Troy Cauble
Sent: Wednesday, December 01, 2004 12:46 PM
To: megaco@ietf.org
Subject: [Megaco] descriptor order and error descriptors


Hi,

I recently ran into the exchange below.
I think it points out a weakness in the protocol w.r.t. associating
descriptor level errors with the appropriate descriptor.

I could find nothing in the docs that say a response's descriptors should be
in the same order as the request's descriptors.

I could find nothing in the docs that say the AuditValue's response's
descriptors should be in the same order as the request tokens.  In fact, the
V2 doc has examples of AuditValue returning descriptors in an order other
than the request tokens.

I didn't check to see if there are similar issues in the other lists that an
errorDescriptor can be used in.  It seems likely though.

Forcing the order to be maintained and using that for context is ugly, IMO.
But it's probably the minimal change solution.
The real problem is lack of info in the errorDescriptor.
(Relying on the text of the error descriptor field would also be a bad idea,
IMO.)

-troy




MEGACO/1 [135.112.125.109]:55555
    Transaction = 50007 {
       Context = - {AuditValue = aaln/2 {
          Audit{ Packages, Statistics , DigitMap, Signals, Events, Media
    }}}}

MEGACO/1 [135.112.125.214]
Reply = 50007 {
   Context = - {
     AuditValue = aaln/2 {
       Media {
         TerminationState {
           Buffer = OFF},
         Stream = 1 {
           LocalControl {

           }
         }
       },
       Events = 2222 {
         al/of
       },
       Error = 447 { "Descriptor not legal in this command" },
       Error = 447 { "Descriptor not legal in this command" },
       Packages {
         g-1,
         tonegen-1,
         tonedet-1,
         dg-1,
         dd-1,
         cg-1,
         cd-1,
         al-1,
         ct-1,
         rtp-1,
         tdmc-1,
         ftmd-1,
         ctyp-1,
         an-1,
         bau-1,
         aau-1,
         xal-1

       },
       Error = 501 { "Not implemented" }
     }
   }
}

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Thu Dec  2 21:19:49 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27760
	for <megaco-archive@lists.ietf.org>; Thu, 2 Dec 2004 21:19:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ca0Pz-0004Cg-8r; Thu, 02 Dec 2004 18:31:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZxSI-0000SN-AQ
	for megaco@megatron.ietf.org; Thu, 02 Dec 2004 15:21:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24590
	for <megaco@ietf.org>; Thu, 2 Dec 2004 15:21:32 -0500 (EST)
Received: from astra.telenet-ops.be ([195.130.132.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZxXs-0005se-FD
	for megaco@ietf.org; Thu, 02 Dec 2004 15:27:21 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by astra.telenet-ops.be (Postfix) with SMTP id 95B9232829A
	for <megaco@ietf.org>; Thu,  2 Dec 2004 21:21:28 +0100 (MET)
Received: from pas (D5778F70.kabel.telenet.be [213.119.143.112])
	by astra.telenet-ops.be (Postfix) with SMTP id 40A9C328009
	for <megaco@ietf.org>; Thu,  2 Dec 2004 21:21:28 +0100 (MET)
Message-ID: <001a01c4d8ac$740e8660$b400a8c0@pandora.be>
From: "Pascal Lambers" <pascal.lambers@pandora.be>
To: <megaco@ietf.org>
Date: Thu, 2 Dec 2004 21:21:06 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Subject: [Megaco] does MGC have to answer?
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Pascal Lambers <pascal.lambers@pandora.be>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0385691065=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0385691065==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0017_01C4D8B4.D5A9BB80"

This is a multi-part message in MIME format.

------=_NextPart_000_0017_01C4D8B4.D5A9BB80
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

Is it mandatory for an MGC to answer to (eg Notify) messages from =
unregistered MGs?
If the MGC receives such a message, typically, its underlying Megaco =
stack will send pending messages to the the MG anyway.
=20
In case it is correct not to answer, here an example of the MG one could =
think of provoque to get the MG registered:

MG                     MGC
------------Notify-------->
<---------Pending--------
<---------Pending--------
<---------Pending--------
                        (mgc stops sending
                          pending msgs)
...
(retries)
-----------Sc Restart----->



Kind regards,
Pascal


------=_NextPart_000_0017_01C4D8B4.D5A9BB80
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1476" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Is it mandatory for an MGC to answer to =
(eg Notify)=20
messages from unregistered MGs?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>If the MGC receives such a message, =
typically, its=20
underlying Megaco stack will send pending messages to the the MG=20
anyway.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>In case it is correct not to answer, =
here an=20
example of the MG one could think of provoque to get the MG=20
registered:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial=20
size=3D2>MG&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MGC</FONT=
></DIV>
<DIV><FONT face=3DArial =
size=3D2>------------Notify--------&gt;</FONT></DIV>
<DIV><FONT face=3DArial =
size=3D2>&lt;---------Pending--------</FONT></DIV>
<DIV>
<DIV><FONT face=3DArial =
size=3D2>&lt;---------Pending--------</FONT></DIV>
<DIV>
<DIV><FONT face=3DArial =
size=3D2>&lt;---------Pending--------</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
(mgc stops sending</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
pending msgs)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>(retries)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>-----------Sc =
Restart-----&gt;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></DIV></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Kind regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Pascal</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0017_01C4D8B4.D5A9BB80--



--===============0385691065==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco

--===============0385691065==--




From megaco-bounces@ietf.org  Thu Dec  2 23:15:26 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07265
	for <megaco-archive@lists.ietf.org>; Thu, 2 Dec 2004 23:15:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ca3sK-0007Ar-VH; Thu, 02 Dec 2004 22:12:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ca0iR-0000Gu-9m
	for megaco@megatron.ietf.org; Thu, 02 Dec 2004 18:50:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15859
	for <megaco@ietf.org>; Thu, 2 Dec 2004 18:50:24 -0500 (EST)
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ca0o2-0002t8-Sc
	for megaco@ietf.org; Thu, 02 Dec 2004 18:56:16 -0500
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id
	iB2NnpAe024665
	for <megaco@ietf.org>; Thu, 2 Dec 2004 17:49:53 -0600 (CST)
Received: from localhost by axes-mach01.axes-mach01.usa.alcatel.com
	(8.9.3+Sun/SMI-SVR4)
	id FAA16755; Fri, 3 Dec 2004 05:20:08 -0500 (GMT)
Date: Fri, 3 Dec 2004 05:20:08 -0500 (GMT)
From: "C. Kamath." <ckamath@axes-mach01.usa.alcatel.com>
To: megaco@ietf.org
Message-ID: <Pine.GSO.4.60.0412030515100.16390@axes-mach01.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 2.0 (++)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Subject: [Megaco] Full match or unambiguous match
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

Hi all,

Can anybody confirm me the following.

MGC has sent the digitmap as [1-9]xxx|xxxxx to MG.

The caller dials  1234#

Now whether MG is supoosed to notify with digits 1234 as Full match or 
unambiguous match


rgds
kamath

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Fri Dec  3 00:33:14 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12763
	for <megaco-archive@lists.ietf.org>; Fri, 3 Dec 2004 00:33:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ca3tz-00087P-1x; Thu, 02 Dec 2004 22:14:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ca1Lt-0003sF-B9
	for megaco@megatron.ietf.org; Thu, 02 Dec 2004 19:31:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19214
	for <megaco@ietf.org>; Thu, 2 Dec 2004 19:31:10 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ca1RL-0003uK-1J
	for megaco@ietf.org; Thu, 02 Dec 2004 19:37:02 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iB30UxR2010625 for <megaco@ietf.org>; Fri, 3 Dec 2004 01:31:00 +0100
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 3 Dec 2004 01:30:59 +0100
Received: from eaubrnt019.epa.ericsson.se ([146.11.9.165]) by
	esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id X8A3GZ00; Fri, 3 Dec 2004 01:30:59 +0100
Received: from ericsson.com (EG2E500202DSEGL [146.11.22.9]) by
	eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id WTM8YGAH; Fri, 3 Dec 2004 11:30:55 +1100
Message-ID: <41AFB3C4.9090601@ericsson.com>
Date: Fri, 03 Dec 2004 11:31:00 +1100
X-Sybari-Trust: edc20493 96d33411 638159be 00000138
From: Christian Groves <christian.groves@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Kevin Boyle <kboyle@nortelnetworks.com>
Subject: Re: [Megaco] descriptor order and error descriptors
References: <B258A372CEA20246A363BB86753DB536010B1B28@zrtphxm2>
In-Reply-To: <B258A372CEA20246A363BB86753DB536010B1B28@zrtphxm2>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Dec 2004 00:30:59.0793 (UTC)
	FILETIME=[5CADA410:01C4D8CF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Content-Transfer-Encoding: 7bit
Cc: megaco@ietf.org, Troy Cauble <troy@bell-labs.com>
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hello Troy and Kevin,

I had always assumed that you would reply back in the same descriptor order as 
what had been requested. I believe this is what we intended. As has been pointed 
out the ErrorDescriptor concept doesn't work without this assumption.

It seems this is another one of those "undocumented" working assumptions in 
H.248. I guess we should add something explicitely to Section 7.1 and fix the 
examples.

Regards, Christian

Kevin Boyle wrote:

> Wouldn't the command processing stop at the first error?
> 
> I believe the intent is to enforce order, since that is how the sender can
> align where errors occurred with the command.  Christian may be able to
> provide more detail on the history of how this was intended to work...
> 
> Whatever we decide, we should document the fix into the Implementors' Guides
> for V1 and V2, and fix the text in V3.
> 
> Kevin 
> 
> -----Original Message-----
> From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
> Troy Cauble
> Sent: Wednesday, December 01, 2004 12:46 PM
> To: megaco@ietf.org
> Subject: [Megaco] descriptor order and error descriptors
> 
> 
> Hi,
> 
> I recently ran into the exchange below.
> I think it points out a weakness in the protocol w.r.t. associating
> descriptor level errors with the appropriate descriptor.
> 
> I could find nothing in the docs that say a response's descriptors should be
> in the same order as the request's descriptors.
> 
> I could find nothing in the docs that say the AuditValue's response's
> descriptors should be in the same order as the request tokens.  In fact, the
> V2 doc has examples of AuditValue returning descriptors in an order other
> than the request tokens.
> 
> I didn't check to see if there are similar issues in the other lists that an
> errorDescriptor can be used in.  It seems likely though.
> 
> Forcing the order to be maintained and using that for context is ugly, IMO.
> But it's probably the minimal change solution.
> The real problem is lack of info in the errorDescriptor.
> (Relying on the text of the error descriptor field would also be a bad idea,
> IMO.)
> 
> -troy
> 
> 
> 
> 
> MEGACO/1 [135.112.125.109]:55555
>     Transaction = 50007 {
>        Context = - {AuditValue = aaln/2 {
>           Audit{ Packages, Statistics , DigitMap, Signals, Events, Media
>     }}}}
> 
> MEGACO/1 [135.112.125.214]
> Reply = 50007 {
>    Context = - {
>      AuditValue = aaln/2 {
>        Media {
>          TerminationState {
>            Buffer = OFF},
>          Stream = 1 {
>            LocalControl {
> 
>            }
>          }
>        },
>        Events = 2222 {
>          al/of
>        },
>        Error = 447 { "Descriptor not legal in this command" },
>        Error = 447 { "Descriptor not legal in this command" },
>        Packages {
>          g-1,
>          tonegen-1,
>          tonedet-1,
>          dg-1,
>          dd-1,
>          cg-1,
>          cd-1,
>          al-1,
>          ct-1,
>          rtp-1,
>          tdmc-1,
>          ftmd-1,
>          ctyp-1,
>          an-1,
>          bau-1,
>          aau-1,
>          xal-1
> 
>        },
>        Error = 501 { "Not implemented" }
>      }
>    }
> }
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Fri Dec  3 03:19:38 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10213
	for <megaco-archive@lists.ietf.org>; Fri, 3 Dec 2004 03:19:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ca7JF-0005rR-8I; Fri, 03 Dec 2004 01:52:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ca51T-0008DJ-Nw
	for megaco@megatron.ietf.org; Thu, 02 Dec 2004 23:26:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07868
	for <megaco@ietf.org>; Thu, 2 Dec 2004 23:26:20 -0500 (EST)
Received: from global.mvnhost.com ([69.93.218.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ca576-0000g6-V9
	for megaco@ietf.org; Thu, 02 Dec 2004 23:32:15 -0500
Received: from 69-171-226-173.clspco.adelphia.net ([69.171.226.173]
	helo=gandalf)
	by global.mvnhost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43)
	id 1Ca51Q-0002HR-7q; Thu, 02 Dec 2004 22:25:58 -0600
Subject: Re: [Megaco] Full match or unambiguous match
From: Terry L Howe <terry@jeeptech.com>
To: "C. Kamath." <ckamath@axes-mach01.usa.alcatel.com>
In-Reply-To: <Pine.GSO.4.60.0412030515100.16390@axes-mach01.usa.alcatel.com>
References: <Pine.GSO.4.60.0412030515100.16390@axes-mach01.usa.alcatel.com>
Content-Type: text/plain
Organization: JeepTech
Message-Id: <1102047976.32287.5.camel@cj8>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-1) 
Date: Thu, 02 Dec 2004 21:26:17 -0700
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - global.mvnhost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jeeptech.com
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: terry@jeeptech.com
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit


The MG would generate the notify as soon as the 4 was pressed, so
it all depends on what the MGC asked the MG to do after it
got the notify.


On Fri, 2004-12-03 at 03:20, C. Kamath. wrote:
> Hi all,
> 
> Can anybody confirm me the following.
> 
> MGC has sent the digitmap as [1-9]xxx|xxxxx to MG.
> 
> The caller dials  1234#
> 
> Now whether MG is supoosed to notify with digits 1234 as Full match or 
> unambiguous match
> 
> 
> rgds
> kamath
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
Terry L Howe                                    terry@jeeptech.com 
http://www.jeeptech.com/          http://www.tiptoprockracing.com/ 
~             http://www.tiptopsoftwarecompany.com/              ~


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Fri Dec  3 05:15:34 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18578
	for <megaco-archive@lists.ietf.org>; Fri, 3 Dec 2004 05:15:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ca8nG-0000Sv-Dj; Fri, 03 Dec 2004 03:27:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ca7Lz-00068N-L2
	for megaco@megatron.ietf.org; Fri, 03 Dec 2004 01:55:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18950
	for <megaco@ietf.org>; Fri, 3 Dec 2004 01:55:42 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ca7Rg-0003pe-2S
	for megaco@ietf.org; Fri, 03 Dec 2004 02:01:36 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iB36tA824916
	for <megaco@ietf.org>; Fri, 3 Dec 2004 01:55:10 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <XQM246K3>; Fri, 3 Dec 2004 01:55:11 -0500
Message-ID: <B258A372CEA20246A363BB86753DB53601135FCF@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: "C. Kamath." <ckamath@axes-mach01.usa.alcatel.com>, megaco@ietf.org
Subject: RE: [Megaco] Full match or unambiguous match
Date: Fri, 3 Dec 2004 01:54:48 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

In all cases, this would be a Full Match, with the octothorpe ('#') as an
extra digit.  Remember that 'x' only matches the digits 0-9.

Note that Unambiguous Match only applies to the base matching procedures,
and not to the enhanced procedures described by H.248.16.

Kevin 

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
C. Kamath.
Sent: Friday, December 03, 2004 12:20 PM
To: megaco@ietf.org
Subject: [Megaco] Full match or unambiguous match

Hi all,

Can anybody confirm me the following.

MGC has sent the digitmap as [1-9]xxx|xxxxx to MG.

The caller dials  1234#

Now whether MG is supoosed to notify with digits 1234 as Full match or
unambiguous match


rgds
kamath

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Fri Dec  3 07:08:05 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27216
	for <megaco-archive@lists.ietf.org>; Fri, 3 Dec 2004 07:08:05 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaAPp-00043h-1N; Fri, 03 Dec 2004 05:11:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ca8kM-0008Sf-B0
	for megaco@megatron.ietf.org; Fri, 03 Dec 2004 03:24:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10756
	for <megaco@ietf.org>; Fri, 3 Dec 2004 03:24:56 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ca8q3-0005ZB-G4
	for megaco@ietf.org; Fri, 03 Dec 2004 03:30:51 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iB38OKE22793
	for <megaco@ietf.org>; Fri, 3 Dec 2004 03:24:21 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <XQM2VC0Y>; Fri, 3 Dec 2004 03:24:21 -0500
Message-ID: <B258A372CEA20246A363BB86753DB53601135FD9@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: terry@jeeptech.com, "C. Kamath." <ckamath@axes-mach01.usa.alcatel.com>
Subject: RE: [Megaco] Full match or unambiguous match
Date: Fri, 3 Dec 2004 03:24:06 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is incorrect.  According to the base match rules, the notify would
occur once the '#' was pressed as a Full Match.

When using the enhanced matching rules from H.248.16, then the match would
express as a Full Match once the 4 was detected.

Kevin 

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Terry L Howe
Sent: Friday, December 03, 2004 6:26 AM
To: C. Kamath.
Cc: megaco@ietf.org
Subject: Re: [Megaco] Full match or unambiguous match


The MG would generate the notify as soon as the 4 was pressed, so it all
depends on what the MGC asked the MG to do after it got the notify.


On Fri, 2004-12-03 at 03:20, C. Kamath. wrote:
> Hi all,
> 
> Can anybody confirm me the following.
> 
> MGC has sent the digitmap as [1-9]xxx|xxxxx to MG.
> 
> The caller dials  1234#
> 
> Now whether MG is supoosed to notify with digits 1234 as Full match or 
> unambiguous match
> 
> 
> rgds
> kamath
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
Terry L Howe                                    terry@jeeptech.com 
http://www.jeeptech.com/          http://www.tiptoprockracing.com/ 
~             http://www.tiptopsoftwarecompany.com/              ~


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Fri Dec  3 13:15:52 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12899
	for <megaco-archive@lists.ietf.org>; Fri, 3 Dec 2004 13:15:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaDfr-0004lb-0d; Fri, 03 Dec 2004 08:40:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZuLg-0000t2-Lh
	for megaco@megatron.ietf.org; Thu, 02 Dec 2004 12:02:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09040
	for <megaco@ietf.org>; Thu, 2 Dec 2004 12:02:29 -0500 (EST)
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZuRE-00018q-Gu
	for megaco@ietf.org; Thu, 02 Dec 2004 12:08:17 -0500
Received: from usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id
	iB2H1v3c007123
	for <megaco@ietf.org>; Thu, 2 Dec 2004 11:01:57 -0600 (CST)
Received: from [172.22.176.142] by auds930.usa.alcatel.com (mshttpd);
	Thu, 02 Dec 2004 12:01:57 -0500
From: Chandrakan Kamath <chandrakant.kamath@alcatel.com>
To: megaco@ietf.org
Message-ID: <89b2808972e7.8972e789b280@usa.alcatel.com>
Date: Thu, 02 Dec 2004 12:01:57 -0500
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.21 (built Sep  8 2003)
MIME-Version: 1.0
Content-Language: en
X-Accept-Language: en
Priority: normal
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 03 Dec 2004 08:40:30 -0500
Subject: [Megaco] UM or FM
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

hello all,

Can anybody pls confirm the following.

MGC has send the following digitmap to MG in Modify

[1-9]xxx|xxxxx

the caller dials 1234#

Now the MG should notify digits 1234 as FULL Match or Unambiguous match ?


rgds
kamath



_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Sun Dec  5 17:23:05 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14454
	for <megaco-archive@lists.ietf.org>; Sun, 5 Dec 2004 17:23:05 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cb4dT-0004XZ-TI; Sun, 05 Dec 2004 17:13:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cb4W2-0003jg-UZ
	for megaco@megatron.ietf.org; Sun, 05 Dec 2004 17:06:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13435
	for <megaco@ietf.org>; Sun, 5 Dec 2004 17:06:00 -0500 (EST)
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cb4cG-0000nb-AS
	for megaco@ietf.org; Sun, 05 Dec 2004 17:12:29 -0500
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id
	iB5M5QAe018713
	for <megaco@ietf.org>; Sun, 5 Dec 2004 16:05:28 -0600 (CST)
Received: from localhost by axes-mach01.axes-mach01.usa.alcatel.com
	(8.9.3+Sun/SMI-SVR4)
	id DAA16692; Mon, 6 Dec 2004 03:35:42 -0500 (GMT)
Date: Mon, 6 Dec 2004 03:35:42 -0500 (GMT)
From: "C. Kamath." <ckamath@axes-mach01.usa.alcatel.com>
To: megaco@ietf.org
Message-ID: <Pine.GSO.4.60.0412060330220.16411@axes-mach01.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Subject: [Megaco] al/of with Root and not *
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

Hi all,

i would like to know if we can arm off hook(al/of) for all the 
terminations in  the gateway by using terminaion as ROOT ie

Modify = ROOT{Events = 100(al/on)}


rgds
kamath

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Mon Dec  6 05:49:09 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22156
	for <megaco-archive@lists.ietf.org>; Mon, 6 Dec 2004 05:49:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbGLw-0008LN-DL; Mon, 06 Dec 2004 05:44:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbGGm-0007bl-VM
	for megaco@megatron.ietf.org; Mon, 06 Dec 2004 05:39:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21600
	for <megaco@ietf.org>; Mon, 6 Dec 2004 05:39:02 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbGN7-00079R-5J
	for megaco@ietf.org; Mon, 06 Dec 2004 05:45:38 -0500
Received: from zcard303.ca.nortel.com (zcard303.ca.nortel.com [47.129.242.59])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iB6AcTG27703; Mon, 6 Dec 2004 05:38:29 -0500 (EST)
Received: from [47.164.193.151] (actft04v.europe.nortel.com [47.164.193.151])
	by zcard303.ca.nortel.com with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2653.13)
	id W14FT2BW; Mon, 6 Dec 2004 05:38:29 -0500
Message-ID: <41B436A3.605@nortelnetworks.com>
Date: Mon, 06 Dec 2004 05:38:27 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "C. Kamath." <ckamath@axes-mach01.usa.alcatel.com>
Subject: Re: [Megaco] al/of with Root and not *
References: <Pine.GSO.4.60.0412060330220.16411@axes-mach01.usa.alcatel.com>
In-Reply-To: <Pine.GSO.4.60.0412060330220.16411@axes-mach01.usa.alcatel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

No.  ROOT refers to the functional capabilities of the MG as a device, where * 
refers to the capabilities of the individual terminations.  The MG contains 
terminations, but it is a different beast.

C. Kamath. wrote:
> Hi all,
> 
> i would like to know if we can arm off hook(al/of) for all the 
> terminations in  the gateway by using terminaion as ROOT ie
> 
> Modify = ROOT{Events = 100(al/on)}
> 
> 
> rgds
> kamath
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 
> 

-- 
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.com

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Mon Dec  6 11:40:01 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28512
	for <megaco-archive@lists.ietf.org>; Mon, 6 Dec 2004 11:40:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbLmS-0008TU-0Y; Mon, 06 Dec 2004 11:32:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbLjS-0007fh-Ls
	for megaco@megatron.ietf.org; Mon, 06 Dec 2004 11:29:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27675
	for <megaco@ietf.org>; Mon, 6 Dec 2004 11:29:00 -0500 (EST)
Received: from togw.navtelcom.com ([199.166.16.39])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CbLpp-0000ZJ-QM
	for megaco@ietf.org; Mon, 06 Dec 2004 11:35:39 -0500
Received: from no.name.available by [199.166.16.39]
	via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP;
	Mon, 6 Dec 2004 11:34:18 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Dec 2004 11:31:01 -0500
Message-ID: <BA0F16E522C0264FB6842D674209530B5BF919@toexh1w2.navtelcom.com>
Thread-Topic: sdp stream type parameter and stream id
Thread-Index: AcTbsPy7fTpGHH3SSTWQiVnr3HT2tg==
From: "Nenad Milidrag" <nenad.milidrag@navtelcom.com>
To: <megaco@ietf.org>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb
Subject: [Megaco] sdp stream type parameter and stream id
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1072658242=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1072658242==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4DBB0.F9107412"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4DBB0.F9107412
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

=20

I would like to know if it is allowed to send ADD request with SDP's
media-type empty such as in "m=3D- $ RTP/AVP 0" and leave it to MG to
decide what media type stream will carry or ADD request always has to
carry media type such as in "m=3Daudio $ RTP/AVP 0" or "m=3Dvideo $ =
RTP/AVP
0".

Further, if MGC can leave media-type parameter empty how can we follow
accepted practice (I have found this at
http://www1.ietf.org/mail-archive/web/megaco/current/msg02933.html not
in an RFC) that MGC assigns stream id according to media type?

=20

Thank you in advance,

=20

Nenad

=20

=20

=20


------_=_NextPart_001_01C4DBB0.F9107412
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi all,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I would like to know if it is allowed to send ADD =
request with
SDP&#8217;s media-type empty such as in &#8220;m=3D- $ RTP/AVP 0&#8221; =
and leave
it to MG to decide what media type stream will carry or ADD request =
always has
to carry media type such as in &#8220;m=3Daudio $ RTP/AVP 0&#8221; or =
&#8220;m=3Dvideo
$ RTP/AVP 0&#8221;.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Further, if MGC can leave media-type parameter empty =
how can
we follow accepted practice (I have found this at </span></font><a
href=3D"http://www1.ietf.org/mail-archive/web/megaco/current/msg02933.htm=
l">http://www1.ietf.org/mail-archive/web/megaco/current/msg02933.html</a>=

<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>not in
an RFC) that MGC assigns stream id according to media =
type?</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thank you in advance,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Nenad</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C4DBB0.F9107412--


--===============1072658242==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco

--===============1072658242==--



From megaco-bounces@ietf.org  Mon Dec  6 21:03:44 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18467
	for <megaco-archive@lists.ietf.org>; Mon, 6 Dec 2004 21:03:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbUVq-00070M-VR; Mon, 06 Dec 2004 20:51:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbUPZ-0005LO-Ps
	for megaco@megatron.ietf.org; Mon, 06 Dec 2004 20:45:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17014
	for <Megaco@ietf.org>; Mon, 6 Dec 2004 20:45:03 -0500 (EST)
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbUVo-0005BU-Vb
	for Megaco@ietf.org; Mon, 06 Dec 2004 20:51:47 -0500
Received: from wink.ho.lucent.com (h135-112-126-3.lucent.com [135.112.126.3])
	by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id iB71iV0h002292
	for <Megaco@ietf.org>; Mon, 6 Dec 2004 19:44:36 -0600 (CST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id UAA21242; Mon, 6 Dec 2004 20:44:30 -0500 (EST)
Received: from [135.112.125.177] by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id UAA21238; Mon, 6 Dec 2004 20:44:29 -0500 (EST)
Message-ID: <41B50AFE.5010004@bell-labs.com>
Date: Mon, 06 Dec 2004 20:44:30 -0500
From: Troy Cauble <troy@bell-labs.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Megaco@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
Subject: [Megaco] off hook warning tone
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit


Hi all,

Is xcg/roh from Q.1950 the proper (and only) way to request
Off Hook Warning tone / Receiver Off Hook tone?

What is the meaning of cg/rt, "(Recording) Warning Tone",
in Annex E?

-troy


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Mon Dec  6 21:16:16 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19566
	for <megaco-archive@lists.ietf.org>; Mon, 6 Dec 2004 21:16:16 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbUsH-0002wt-Qc; Mon, 06 Dec 2004 21:14:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbUoj-0002AS-0d
	for megaco@megatron.ietf.org; Mon, 06 Dec 2004 21:11:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19242
	for <Megaco@ietf.org>; Mon, 6 Dec 2004 21:11:03 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbUvB-0005q5-Gp
	for Megaco@ietf.org; Mon, 06 Dec 2004 21:17:46 -0500
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70])
	by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id iB72AUgo016116
	for <Megaco@ietf.org>; Mon, 6 Dec 2004 20:10:31 -0600 (CST)
Received: from milu (mmraju.lra.lucent.com [192.11.172.74]) by
	ihmail.ih.lucent.com (8.11.7p1+Sun/EMS-1.5 sol2)
	id iB72AUt13885; Mon, 6 Dec 2004 20:10:30 -0600 (CST)
From: "Maridi R. Makaraju \(Raju\)" <mmraju@lucent.com>
To: "Troy Cauble" <troy@bell-labs.com>, <Megaco@ietf.org>
Subject: RE: [Megaco] off hook warning tone
Date: Mon, 6 Dec 2004 20:10:18 -0600
Message-ID: <NPEHJHFOKFCPFAAGFKHPGEDHCCAA.mmraju@lucent.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
In-Reply-To: <41B50AFE.5010004@bell-labs.com>
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Troy,

> Hi all,
> 
> Is xcg/roh from Q.1950 the proper (and only) way to request
> Off Hook Warning tone / Receiver Off Hook tone?
> 
> What is the meaning of cg/rt, "(Recording) Warning Tone",
> in Annex E?

RingbackTone!

-Raju

> 
> -troy
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Tue Dec  7 01:52:21 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09842
	for <megaco-archive@lists.ietf.org>; Tue, 7 Dec 2004 01:52:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbZBI-0004WV-FE; Tue, 07 Dec 2004 01:50:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbZAj-0004Mz-4n
	for megaco@megatron.ietf.org; Tue, 07 Dec 2004 01:50:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09765
	for <Megaco@ietf.org>; Tue, 7 Dec 2004 01:50:04 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbZHD-000334-WF
	for Megaco@ietf.org; Tue, 07 Dec 2004 01:56:49 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iB76nQu02431; Tue, 7 Dec 2004 01:49:26 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YFGS8D5J>; Tue, 7 Dec 2004 01:49:26 -0500
Message-ID: <B258A372CEA20246A363BB86753DB5360124B672@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: "Maridi R. Makaraju (Raju)" <mmraju@lucent.com>,
        Troy Cauble
	<troy@bell-labs.com>, Megaco@ietf.org
Subject: RE: [Megaco] off hook warning tone
Date: Tue, 7 Dec 2004 01:49:13 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0227354430=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============0227354430==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4DC27.FA7D5DB9"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C4DC27.FA7D5DB9
Content-Type: text/plain;
	charset="iso-8859-1"

I believe that Troy was asking about cg/wt.  This tone is meant to indicate
to the parties on the call that a recording device is hooked up and
listening.  This definition can be found in E.180/Q.35.
 
So, yes, the proper/only way to do Howler/Offhook Warning Tone/ROH/etc. is
xcg/roh.
 
Kevin

  _____  

From: megaco-bounces@ietf.org on behalf of Maridi R. Makaraju (Raju)
Sent: Mon 12/6/2004 9:10 PM
To: Troy Cauble; Megaco@ietf.org
Subject: RE: [Megaco] off hook warning tone



Troy,

> Hi all,
>
> Is xcg/roh from Q.1950 the proper (and only) way to request
> Off Hook Warning tone / Receiver Off Hook tone?
>
> What is the meaning of cg/rt, "(Recording) Warning Tone",
> in Annex E?

RingbackTone!

-Raju

>
> -troy
>
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
<https://www1.ietf.org/mailman/listinfo/megaco> 
>


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
<https://www1.ietf.org/mailman/listinfo/megaco> 




------_=_NextPart_001_01C4DC27.FA7D5DB9
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7226.0">
<TITLE>RE: [Megaco] off hook warning tone</TITLE>
</HEAD>
<BODY>
<DIV id=3DidOWAReplyText30439 dir=3Dltr>
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>I believe =
that Troy was=20
asking about cg/wt.&nbsp; This tone is meant to indicate to the parties =
on the=20
call that a recording device is hooked up and listening.&nbsp; This =
definition=20
can be found in E.180/Q.35.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>So, yes, the proper/only way =
to do=20
Howler/Offhook Warning Tone/ROH/etc. is xcg/roh.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Kevin</FONT></DIV></DIV>
<DIV dir=3Dltr><BR>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> megaco-bounces@ietf.org on =
behalf of=20
Maridi R. Makaraju (Raju)<BR><B>Sent:</B> Mon 12/6/2004 9:10 =
PM<BR><B>To:</B>=20
Troy Cauble; Megaco@ietf.org<BR><B>Subject:</B> RE: [Megaco] off hook =
warning=20
tone<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=3D2>Troy,<BR><BR>&gt; Hi all,<BR>&gt;<BR>&gt; Is xcg/roh =
from Q.1950=20
the proper (and only) way to request<BR>&gt; Off Hook Warning tone / =
Receiver=20
Off Hook tone?<BR>&gt;<BR>&gt; What is the meaning of cg/rt, =
"(Recording)=20
Warning Tone",<BR>&gt; in Annex=20
E?<BR><BR>RingbackTone!<BR><BR>-Raju<BR><BR>&gt;<BR>&gt;=20
-troy<BR>&gt;<BR>&gt;<BR>&gt;=20
_______________________________________________<BR>&gt; Megaco mailing=20
list<BR>&gt; Megaco@ietf.org<BR>&gt; <A=20
href=3D"https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf=
.org/mailman/listinfo/megaco</A><BR>&gt;<BR><BR><BR>___________________=
____________________________<BR>Megaco=20
mailing list<BR>Megaco@ietf.org<BR><A=20
href=3D"https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf=
.org/mailman/listinfo/megaco</A><BR><BR></FONT></P></DIV>

</BODY>
</HTML>
------_=_NextPart_001_01C4DC27.FA7D5DB9--


--===============0227354430==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco

--===============0227354430==--



From megaco-bounces@ietf.org  Tue Dec  7 07:31:19 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20401
	for <megaco-archive@lists.ietf.org>; Tue, 7 Dec 2004 07:31:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbeNh-0000m7-W5; Tue, 07 Dec 2004 07:23:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbeKD-0008Q1-GH
	for megaco@megatron.ietf.org; Tue, 07 Dec 2004 07:20:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19466
	for <Megaco@ietf.org>; Tue, 7 Dec 2004 07:20:12 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbeQj-0001GR-6Q
	for Megaco@ietf.org; Tue, 07 Dec 2004 07:27:00 -0500
Received: from wink.ho.lucent.com (h135-112-126-3.lucent.com [135.112.126.3])
	by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id iB7CJVR9012510
	for <Megaco@ietf.org>; Tue, 7 Dec 2004 06:19:34 -0600 (CST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id HAA23065; Tue, 7 Dec 2004 07:19:29 -0500 (EST)
Received: from [192.11.60.168] by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id HAA23061; Tue, 7 Dec 2004 07:19:29 -0500 (EST)
Message-ID: <41B59FCD.6070708@bell-labs.com>
Date: Tue, 07 Dec 2004 07:19:25 -0500
From: Troy Cauble <troy@bell-labs.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Megaco@ietf.org
Subject: Re: [Megaco] off hook warning tone
References: <B258A372CEA20246A363BB86753DB5360124B672@zrtphxm2>
In-Reply-To: <B258A372CEA20246A363BB86753DB5360124B672@zrtphxm2>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Kevin Boyle wrote:
> 
> I believe that Troy was asking about cg/wt.  This tone is meant to 
> indicate to the parties on the call that a recording device is hooked up 
> and listening.  This definition can be found in E.180/Q.35.
>  
> So, yes, the proper/only way to do Howler/Offhook Warning Tone/ROH/etc. 
> is xcg/roh.
>  
> Kevin
> 
> *From:* megaco-bounces@ietf.org on behalf of Maridi R. Makaraju (Raju)
> *Sent:* Mon 12/6/2004 9:10 PM
> *To:* Troy Cauble; Megaco@ietf.org
> *Subject:* RE: [Megaco] off hook warning tone
> 
> Troy,
> 
>  > Hi all,
>  >
>  > Is xcg/roh from Q.1950 the proper (and only) way to request
>  > Off Hook Warning tone / Receiver Off Hook tone?
>  >
>  > What is the meaning of cg/rt, "(Recording) Warning Tone",
>  > in Annex E?
> 
> RingbackTone!
> 
> -Raju
> 
>  >
>  > -troy
> 


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Tue Dec  7 07:36:16 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20898
	for <megaco-archive@lists.ietf.org>; Tue, 7 Dec 2004 07:36:16 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbeW9-00024p-RR; Tue, 07 Dec 2004 07:32:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbeRo-0001Lu-Bp
	for megaco@megatron.ietf.org; Tue, 07 Dec 2004 07:28:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20236
	for <Megaco@ietf.org>; Tue, 7 Dec 2004 07:28:03 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbeYN-0001Qw-9H
	for Megaco@ietf.org; Tue, 07 Dec 2004 07:34:51 -0500
Received: from wink.ho.lucent.com (h135-112-126-3.lucent.com [135.112.126.3])
	by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id iB7CRUC6018240
	for <Megaco@ietf.org>; Tue, 7 Dec 2004 06:27:31 -0600 (CST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id HAA23100; Tue, 7 Dec 2004 07:27:28 -0500 (EST)
Received: from [192.11.60.168] by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id HAA23076; Tue, 7 Dec 2004 07:27:26 -0500 (EST)
Message-ID: <41B5A1AA.6000806@bell-labs.com>
Date: Tue, 07 Dec 2004 07:27:22 -0500
From: Troy Cauble <troy@bell-labs.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Kevin Boyle <kboyle@nortelnetworks.com>
Original-CC: "Maridi R. Makaraju (Raju)" <mmraju@lucent.com>, Megaco@ietf.org
Subject: Re: [Megaco] off hook warning tone
References: <B258A372CEA20246A363BB86753DB5360124B672@zrtphxm2>
In-Reply-To: <B258A372CEA20246A363BB86753DB5360124B672@zrtphxm2>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
Cc: "Maridi R. Makaraju \(Raju\)" <mmraju@lucent.com>, Megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Yes, "rt" was a typo.  Thanks.  -troy


Kevin Boyle wrote:
> 
> I believe that Troy was asking about cg/wt.  This tone is meant to 
> indicate to the parties on the call that a recording device is hooked up 
> and listening.  This definition can be found in E.180/Q.35.
>  
> So, yes, the proper/only way to do Howler/Offhook Warning Tone/ROH/etc. 
> is xcg/roh.
>  
> Kevin
> 
> *From:* megaco-bounces@ietf.org on behalf of Maridi R. Makaraju (Raju)
> *Sent:* Mon 12/6/2004 9:10 PM
> *To:* Troy Cauble; Megaco@ietf.org
> *Subject:* RE: [Megaco] off hook warning tone
> 
> Troy,
> 
>  > Hi all,
>  >
>  > Is xcg/roh from Q.1950 the proper (and only) way to request
>  > Off Hook Warning tone / Receiver Off Hook tone?
>  >
>  > What is the meaning of cg/rt, "(Recording) Warning Tone",
>  > in Annex E?
> 
> RingbackTone!
> 
> -Raju
> 
>  >
>  > -troy

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Tue Dec  7 18:35:46 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14914
	for <megaco-archive@lists.ietf.org>; Tue, 7 Dec 2004 18:35:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CboaE-0003mA-9k; Tue, 07 Dec 2004 18:17:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CboK0-0008VL-3r
	for megaco@megatron.ietf.org; Tue, 07 Dec 2004 18:00:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10455
	for <megaco@ietf.org>; Tue, 7 Dec 2004 18:00:36 -0500 (EST)
Received: from adicia.telenet-ops.be ([195.130.132.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CboQd-0003Vb-Lv
	for megaco@ietf.org; Tue, 07 Dec 2004 18:07:32 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by adicia.telenet-ops.be (Postfix) with SMTP id 49E83441F6
	for <megaco@ietf.org>; Wed,  8 Dec 2004 00:00:34 +0100 (MET)
Received: from pas (D5778D8C.kabel.telenet.be [213.119.141.140])
	by adicia.telenet-ops.be (Postfix) with SMTP id 15D23440AC
	for <megaco@ietf.org>; Wed,  8 Dec 2004 00:00:34 +0100 (MET)
Message-ID: <00de01c4dcb0$8cfa8680$b400a8c0@pandora.be>
From: "Pascal Lambers" <pascal.lambers@pandora.be>
To: <megaco@ietf.org>
Subject: Fw: [Megaco] does MGC have to answer?
Date: Wed, 8 Dec 2004 00:00:23 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.2 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Pascal Lambers <pascal.lambers@pandora.be>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1828876498=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1828876498==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00DB_01C4DCB8.EA005500"

This is a multi-part message in MIME format.

------=_NextPart_000_00DB_01C4DCB8.EA005500
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

Is it mandatory for an MGC to answer to (eg Notify) messages from =
unregistered MGs? If the MGC receives such a message, typically, its =
underlying Megaco stack will send pending messages to the the MG anyway, =
even though the actual MGC does not answer to the message. In other =
words, is the following scenario a good one:

MG                     MGC
------------Notify-------->
<---------Pending-------- =20
<---------Pending--------
<---------Pending--------
                        (mgc stops sending
                          pending msgs)
...
(retries)
-----------Sc Restart----->



Kind regards,
Pascal
------=_NextPart_000_00DB_01C4DCB8.EA005500
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1476" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Is it mandatory for an MGC to answer to =
(eg Notify)=20
messages from unregistered MGs? </FONT><FONT face=3DArial size=3D2>If =
the MGC=20
receives such a message, typically, its underlying Megaco stack will =
send=20
pending messages to the the MG anyway, even though the actual MGC does =
not=20
answer to the message. </FONT><FONT face=3DArial size=3D2>In other =
words, is the=20
following scenario a good one:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial=20
size=3D2>MG&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MGC</FONT=
></DIV>
<DIV><FONT face=3DArial =
size=3D2>------------Notify--------&gt;</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>&lt;---------Pending--------&nbsp;&nbsp;</FONT></DIV>
<DIV>
<DIV><FONT face=3DArial =
size=3D2>&lt;---------Pending--------</FONT></DIV>
<DIV>
<DIV><FONT face=3DArial =
size=3D2>&lt;---------Pending--------</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
(mgc stops sending</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
pending msgs)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>(retries)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>-----------Sc =
Restart-----&gt;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></DIV></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Kind regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Pascal</FONT></DIV></BODY></HTML>

------=_NextPart_000_00DB_01C4DCB8.EA005500--



--===============1828876498==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco

--===============1828876498==--




From megaco-bounces@ietf.org  Wed Dec  8 01:57:21 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24698
	for <megaco-archive@lists.ietf.org>; Wed, 8 Dec 2004 01:57:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbveD-00038H-Sl; Wed, 08 Dec 2004 01:50:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cbvc5-0002af-3G
	for megaco@megatron.ietf.org; Wed, 08 Dec 2004 01:47:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24257
	for <megaco@ietf.org>; Wed, 8 Dec 2004 01:47:48 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbvim-0005bX-QY
	for megaco@ietf.org; Wed, 08 Dec 2004 01:54:46 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iB86lAw09099
	for <megaco@ietf.org>; Wed, 8 Dec 2004 01:47:11 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YFGTDJ2P>; Wed, 8 Dec 2004 01:47:10 -0500
Message-ID: <B258A372CEA20246A363BB86753DB5360124B67C@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Pascal Lambers <pascal.lambers@pandora.be>, megaco@ietf.org
Subject: RE: [Megaco] does MGC have to answer?
Date: Wed, 8 Dec 2004 01:44:28 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1007192050=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============1007192050==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4DCF1.5D67FAB5"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C4DCF1.5D67FAB5
Content-Type: text/plain;
	charset="iso-8859-1"

I would think that MGCs would ignore any messages from unregistered MGs that
are not ServiceChanges.  Sending Pendings may only serve to extend a DoS
attack.
 
I do not believe that the use of Pending in this case is typical, either.
In fact, I would say that it is atypical, and in fact, wrong.
 
Kevin

  _____  

From: megaco-bounces@ietf.org on behalf of Pascal Lambers
Sent: Wed 12/8/2004 1:00 AM
To: megaco@ietf.org
Subject: Fw: [Megaco] does MGC have to answer?


Hi,
 
Is it mandatory for an MGC to answer to (eg Notify) messages from
unregistered MGs? If the MGC receives such a message, typically, its
underlying Megaco stack will send pending messages to the the MG anyway,
even though the actual MGC does not answer to the message. In other words,
is the following scenario a good one:
 
MG                     MGC
------------Notify-------->
<---------Pending--------  
<---------Pending--------
<---------Pending--------
                        (mgc stops sending
                          pending msgs)
...
(retries)
-----------Sc Restart----->
 
 
 
Kind regards,
Pascal

------_=_NextPart_001_01C4DCF1.5D67FAB5
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 6.00.2800.1476" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV id=3DidOWAReplyText91384 dir=3Dltr>
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>I would =
think that MGCs would=20
ignore any messages from unregistered MGs that are not =
ServiceChanges.&nbsp;=20
Sending Pendings may only serve to extend a DoS attack.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I do not believe that the =
use of Pending in=20
this case is typical, either.&nbsp; In fact, I would say that it is =
atypical,=20
and in fact, wrong.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Kevin</FONT></DIV></DIV>
<DIV dir=3Dltr><BR>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> megaco-bounces@ietf.org on =
behalf of=20
Pascal Lambers<BR><B>Sent:</B> Wed 12/8/2004 1:00 AM<BR><B>To:</B>=20
megaco@ietf.org<BR><B>Subject:</B> Fw: [Megaco] does MGC have to=20
answer?<BR></FONT><BR></DIV>
<DIV>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Is it mandatory for an MGC to answer =
to (eg Notify)=20
messages from unregistered MGs? </FONT><FONT face=3DArial size=3D2>If =
the MGC=20
receives such a message, typically, its underlying Megaco stack will =
send=20
pending messages to the the MG anyway, even though the actual MGC does =
not=20
answer to the message. </FONT><FONT face=3DArial size=3D2>In other =
words, is the=20
following scenario a good one:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial=20
size=3D2>MG&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MGC</FO=
NT></DIV>
<DIV><FONT face=3DArial =
size=3D2>------------Notify--------&gt;</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>&lt;---------Pending--------&nbsp;&nbsp;</FONT></DIV>
<DIV>
<DIV><FONT face=3DArial =
size=3D2>&lt;---------Pending--------</FONT></DIV>
<DIV>
<DIV><FONT face=3DArial =
size=3D2>&lt;---------Pending--------</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
(mgc stops sending</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
pending msgs)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>(retries)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>-----------Sc =
Restart-----&gt;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></DIV></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Kind regards,</FONT></DIV>
<DIV><FONT face=3DArial =
size=3D2>Pascal</FONT></DIV></DIV></BODY></HTML>

------_=_NextPart_001_01C4DCF1.5D67FAB5--


--===============1007192050==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco

--===============1007192050==--



From megaco-bounces@ietf.org  Wed Dec  8 02:18:15 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12728
	for <megaco-archive@lists.ietf.org>; Wed, 8 Dec 2004 02:18:15 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cbw1W-0002pi-L0; Wed, 08 Dec 2004 02:14:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbvxW-0001aq-6d
	for megaco@megatron.ietf.org; Wed, 08 Dec 2004 02:09:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05275
	for <megaco@ietf.org>; Wed, 8 Dec 2004 02:09:56 -0500 (EST)
Received: from [194.90.152.129] (helo=mr.teledata-networks.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbw4D-00060Q-EQ
	for megaco@ietf.org; Wed, 08 Dec 2004 02:16:54 -0500
Received: from mr.teledata-networks.com (localhost.localdomain [127.0.0.1])
	by localhost.teledata-networks.com (Postfix) with ESMTP id 264807C0071
	for <megaco@ietf.org>; Wed,  8 Dec 2004 09:05:20 +0200 (IST)
Received: from tndcmail.Teledata.Local (ADC-FW.ser.netvision.net.il [199.203
	.98.2])by mr.teledata-networks.com (Postfix) with ESMTP id
	1B8B87C006Bfor <
	megaco@ietf.org>; Wed,  8 Dec 2004 02:05:20 -0500 (EST)
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Wed, 8 Dec 2004 09:09:54 +0200
Message-ID: <D6FAAE89E48C5B488B41BEBBDCD746CD06EB65@tndcmail.Teledata.Local>
Thread-Topic: signal directionality
Thread-Index: AcTc9NbGrCHvtc1bQVGV5/tuE51GXw==
From: "Matia Marcu" <Matia.Marcu@Teledata-Networks.com>
To: <megaco@ietf.org>
X-imss-version: 2.0
X-imss-result: Passed
X-imss-scores: Clean:41.56001 C:20 M:1 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576
Subject: [Megaco] signal directionality
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0930672120=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0930672120==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4DCF4.EAC899E8"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4DCF4.EAC899E8
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable



Please, I have a few questions concerning signal directionality.

1. I think that there is a slight difference between the definitions of =
directionality in Q.1950 and H.248.23 /H.248.27.=20

All the sources are clear concerning "external" and "both"; I quote here =
the explanations concerning "internal":

H.248.2x: "Internal" denotes that the signal shall proceed toward the =
centre of the context from the termination.
=20
Q.1950 - 4.4.48 signal direction: The stimulus can be placed on a =
termination so that none of the other terminations in the context "hear" =
it (external) or so that other terminations in the context "hear" it =
also (internal). 					    =20

I understand the first definition as saying that only the other =
terminations in the context "hear" the signal while the second =
definition says that these terminations also "hear" the signal. In the =
Q.1950 case, who is also hearing the signal? The termination itself =
(i.e. like in the "external" case)? If so, what's the difference between =
"internal" and "both"?

2. Assuming that the H.248.2x definition is correct, I'd like to verify =
a simple example of tone application:

Termination A (physA, ephemA in context C1) is calling termination B =
(physB, ephemB in context C2); termination A must receive ringback tone. =
The softswitch may request either bcg/brt (or cg/rt) on physA =
("external" direction explicit or implied) or bcg/brt -"internal" on =
ephemA. Is it also ok to request bcg/brt-"external" on ephemB? This =
would be similar to ringback tone application in classical telephony =
(from the terminating side, to avoid clipping on answer), but in VoIP is =
there any reason to do so?=20

3. What should a gateway answer if it receives a ring command with an =
incorrect direction (like - using the example above - =
alert/ri-"internal" on physB)? The message is legal, so no error of this =
kind applies; on the other hand, it's not exactly a case for answering =
"513"; error "421" Unknown action or illegal combination of actions =
(also not an exact match) appears in H.248.8 as "not used"...

4. The usefullness of "internal" and "both" directions is clear for =
multi-party sessions (conference, announcements...). Are there other =
types of applications where directionality is very useful?

Many thanks,

Matia Marcu
Teledata Networks



------_=_NextPart_001_01C4DCF4.EAC899E8
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7226.0">
<TITLE>signal directionality</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>
<BR>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Please, I have a few =
questions concerning signal directionality.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">1. I think that there is a =
slight difference between the definitions of directionality in Q.1950 =
and H.248.23 /H.248.27. </FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">All the sources are clear =
concerning &quot;external&quot; and &quot;both&quot;; I quote here the =
explanations concerning &quot;internal&quot;:</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">H.248.2x:</FONT><FONT =
FACE=3D"TimesNewRoman"> &quot;Internal&quot; denotes that the signal =
shall proceed toward the centre of the context from the =
termination.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Q.1950 -</FONT> <FONT =
FACE=3D"TimesNewRoman,Bold">4.4.48 signal directio</FONT><FONT =
FACE=3D"TimesNewRoman">n: The stimulus can be placed on a termination so =
that none of the other terminations in the context &quot;hear&quot; it =
(external) or so that other terminations in the context &quot;hear&quot; =
it also<B></B> (internal).</FONT><FONT SIZE=3D2 FACE=3D"Arial"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; =
</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">I understand the first =
definition as saying that</FONT><B> <FONT SIZE=3D2 =
FACE=3D"Arial">only</FONT></B> <FONT SIZE=3D2 FACE=3D"Arial">the other =
terminations in the context &quot;hear&quot; the signal while the second =
definition says that these terminations</FONT><B> <FONT SIZE=3D2 =
FACE=3D"Arial">also</FONT></B><FONT SIZE=3D2 FACE=3D"Arial"> =
&quot;hear&quot; the signal. In the Q.1950 case, who is</FONT><B> <FONT =
SIZE=3D2 FACE=3D"Arial">also</FONT></B><FONT SIZE=3D2 FACE=3D"Arial"> =
hearing the signal? The termination itself (i.e. like in the =
&quot;external&quot; case)? If so, what's the difference between =
&quot;internal&quot; and &quot;both&quot;?</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">2. Assuming that the H.248.2x =
definition is correct, I'd like to verify a simple example of tone =
application:</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Termination A (physA, ephemA =
in context C1) is calling termination B (physB, ephemB in context C2); =
termination A must receive ringback tone. The softswitch may request =
either bcg/brt (or cg/rt) on physA (&quot;external&quot; direction =
explicit or implied) or bcg/brt -&quot;internal&quot; on ephemA. Is it =
also ok to request bcg/brt-&quot;external&quot; on ephemB? This would be =
similar to ringback tone application in classical telephony (from the =
terminating side, to avoid clipping on answer), but in VoIP is there any =
reason to do so? </FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">3. What should a gateway =
answer if it receives a ring command with an incorrect direction (like - =
using the example above - alert/ri-&quot;internal&quot; on physB)? The =
message is legal, so no error of this kind applies; on the other hand, =
it's not exactly a case for answering &quot;513&quot;; error =
&quot;421&quot;</FONT><B></B><B></B><B> <FONT =
FACE=3D"TimesNewRoman,Bold">Unknown action or illegal combination of =
actions</FONT></B> <FONT FACE=3D"TimesNewRoman,Bold">(also not an exact =
match) appears in H.248.8 as &quot;not used&quot;...</FONT></P>

<P DIR=3DLTR><FONT FACE=3D"TimesNewRoman,Bold">4.</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">The usefullness of &quot;internal&quot; and =
&quot;both&quot; directions is clear for multi-party sessions =
(conference, announcements...). Are there other types of applications =
where directionality is very useful?</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Many thanks,</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Matia Marcu</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Teledata Networks</FONT></P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C4DCF4.EAC899E8--


--===============0930672120==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco

--===============0930672120==--



From megaco-bounces@ietf.org  Wed Dec  8 03:05:04 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28730
	for <megaco-archive@lists.ietf.org>; Wed, 8 Dec 2004 03:05:04 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cbwg7-0006er-Mi; Wed, 08 Dec 2004 02:56:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbwYH-0005MF-00
	for megaco@megatron.ietf.org; Wed, 08 Dec 2004 02:47:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27553
	for <megaco@ietf.org>; Wed, 8 Dec 2004 02:47:55 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbwew-0006iH-LS
	for megaco@ietf.org; Wed, 08 Dec 2004 02:54:52 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iB87lIT12376; Wed, 8 Dec 2004 02:47:18 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YFGTDQRW>; Wed, 8 Dec 2004 02:47:18 -0500
Message-ID: <B258A372CEA20246A363BB86753DB5360124B67E@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Matia Marcu <Matia.Marcu@Teledata-Networks.com>, megaco@ietf.org
Subject: RE: [Megaco] signal directionality
Date: Wed, 8 Dec 2004 02:47:11 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: a492040269d440726bfd84680622cee7
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1783989630=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============1783989630==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4DCF7.5250E8E6"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C4DCF7.5250E8E6
Content-Type: text/plain;
	charset="iso-8859-1"

Directionality is being added in H.248 version 3 as a default signal
parameter.  In the definition there, "internal" plays the signal toward the
center of the context.  To have it play in both directions, one would use
"both". This means that the wording in Q.1950 section 4.4.48 appears to be
incorrect.  Note that the wording in the packages themselves (Annex A) is
correct.
 
In your example, note that there are 4 terminations, not two.  I assume
terminations A and B are the physical terminations in this case.  Keep in
mind that physical and ephemeral terminations are not linked in H.248,
except by being placed in a context together.
 
Your examples on the ringback are all ok.  In theory, you could also put
ringback on physB and use internal.  I can think of several cases where it
would be better to place the ringback on ephemB; what if party B is on a
different MG, controlled by a different MGC?
 
A revision of H.248.8 is upcoming and will be released in conjunction with
H.248.1v3.  We are defining a new error code that will cover this case: 449
"Unsupported or Unknown Parameter or Property Value".
 
As for where this is useful, that would depend upon the requirements of the
applications you are providing in your system.  I can think of several,
including the "remote ringback" case discussed here.
 
Kevin

  _____  

From: megaco-bounces@ietf.org on behalf of Matia Marcu
Sent: Wed 12/8/2004 9:09 AM
To: megaco@ietf.org
Subject: [Megaco] signal directionality





Please, I have a few questions concerning signal directionality.

1. I think that there is a slight difference between the definitions of
directionality in Q.1950 and H.248.23 /H.248.27. 

All the sources are clear concerning "external" and "both"; I quote here the
explanations concerning "internal":

H.248.2x: "Internal" denotes that the signal shall proceed toward the centre
of the context from the termination.

 

Q.1950 - 4.4.48 signal direction: The stimulus can be placed on a
termination so that none of the other terminations in the context "hear" it
(external) or so that other terminations in the context "hear" it also
(internal).                                             

I understand the first definition as saying that only the other terminations
in the context "hear" the signal while the second definition says that these
terminations also "hear" the signal. In the Q.1950 case, who is also hearing
the signal? The termination itself (i.e. like in the "external" case)? If
so, what's the difference between "internal" and "both"?

2. Assuming that the H.248.2x definition is correct, I'd like to verify a
simple example of tone application:

Termination A (physA, ephemA in context C1) is calling termination B (physB,
ephemB in context C2); termination A must receive ringback tone. The
softswitch may request either bcg/brt (or cg/rt) on physA ("external"
direction explicit or implied) or bcg/brt -"internal" on ephemA. Is it also
ok to request bcg/brt-"external" on ephemB? This would be similar to
ringback tone application in classical telephony (from the terminating side,
to avoid clipping on answer), but in VoIP is there any reason to do so? 

3. What should a gateway answer if it receives a ring command with an
incorrect direction (like - using the example above - alert/ri-"internal" on
physB)? The message is legal, so no error of this kind applies; on the other
hand, it's not exactly a case for answering "513"; error "421" Unknown
action or illegal combination of actions (also not an exact match) appears
in H.248.8 as "not used"...

4. The usefullness of "internal" and "both" directions is clear for
multi-party sessions (conference, announcements...). Are there other types
of applications where directionality is very useful?

Many thanks,

Matia Marcu

Teledata Networks



------_=_NextPart_001_01C4DCF7.5250E8E6
Content-Type: text/html;
	charset="iso-8859-1"


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>signal directionality</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText89755 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Directionality is being added 
in H.248 version 3 as a default signal parameter.&nbsp; In the definition there, 
"internal" plays the signal toward the center of the context.&nbsp; To have it 
play in both directions, one would use "both". </FONT><FONT face=Arial 
size=2>This means that the wording in Q.1950 section 4.4.48 appears to be 
incorrect.&nbsp; Note that the wording in the packages themselves (Annex A) is 
correct.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr><FONT face=Arial size=2>In your example, note that there are 4 
terminations, not two.&nbsp; I assume terminations A and B are the physical 
terminations in this case.&nbsp; Keep in mind that physical and ephemeral 
terminations are not linked in H.248, except by being placed in a context 
together.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr><FONT face=Arial size=2>Your examples on the ringback are all 
ok.&nbsp; In theory, you could also put ringback on physB and use 
internal.&nbsp; I can think of several cases where it would be better to place 
the ringback on ephemB; what if party B is on a different MG, controlled by a 
different MGC?</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr><FONT face=Arial size=2>A revision of H.248.8 is upcoming and will 
be released in conjunction with H.248.1v3.&nbsp; We are defining a new error 
code that will cover this case: 449 "Unsupported or Unknown Parameter or 
Property Value".</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr><FONT face=Arial size=2>As for where this is useful, that would 
depend upon the requirements of the applications you are providing in your 
system.&nbsp;&nbsp;I can think of several, including the "remote ringback" case 
discussed here.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr><FONT face=Arial size=2>Kevin</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> megaco-bounces@ietf.org on behalf of Matia 
Marcu<BR><B>Sent:</B> Wed 12/8/2004 9:09 AM<BR><B>To:</B> 
megaco@ietf.org<BR><B>Subject:</B> [Megaco] signal 
directionality<BR></FONT><BR></DIV>
<DIV><BR><BR>
<P dir=ltr><FONT face=Arial size=2>Please, I have a few questions concerning 
signal directionality.</FONT></P>
<P dir=ltr><FONT face=Arial size=2>1. I think that there is a slight difference 
between the definitions of directionality in Q.1950 and H.248.23 /H.248.27. 
</FONT></P>
<P dir=ltr><FONT face=Arial size=2>All the sources are clear concerning 
"external" and "both"; I quote here the explanations concerning 
"internal":</FONT></P>
<P dir=ltr><FONT face=Arial size=2>H.248.2x:</FONT><FONT face=TimesNewRoman> 
"Internal" denotes that the signal shall proceed toward the centre of the 
context from the termination.</FONT></P>
<P dir=ltr><FONT face=Arial size=2></FONT>&nbsp;</P>
<P dir=ltr><FONT face=Arial size=2>Q.1950 -</FONT> <FONT 
face=TimesNewRoman,Bold>4.4.48 signal directio</FONT><FONT face=TimesNewRoman>n: 
The stimulus can be placed on a termination so that none of the other 
terminations in the context "hear" it (external) or so that other terminations 
in the context "hear" it also<B></B> (internal).</FONT><FONT face=Arial size=2> 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; </FONT></P>
<P dir=ltr><FONT face=Arial size=2>I understand the first definition as saying 
that</FONT><B> <FONT face=Arial size=2>only</FONT></B> <FONT face=Arial 
size=2>the other terminations in the context "hear" the signal while the second 
definition says that these terminations</FONT><B> <FONT face=Arial 
size=2>also</FONT></B><FONT face=Arial size=2> "hear" the signal. In the Q.1950 
case, who is</FONT><B> <FONT face=Arial size=2>also</FONT></B><FONT face=Arial 
size=2> hearing the signal? The termination itself (i.e. like in the "external" 
case)? If so, what's the difference between "internal" and "both"?</FONT></P>
<P dir=ltr><FONT face=Arial size=2>2. Assuming that the H.248.2x definition is 
correct, I'd like to verify a simple example of tone application:</FONT></P>
<P dir=ltr><FONT face=Arial size=2>Termination A (physA, ephemA in context C1) 
is calling termination B (physB, ephemB in context C2); termination A must 
receive ringback tone. The softswitch may request either bcg/brt (or cg/rt) on 
physA ("external" direction explicit or implied) or bcg/brt -"internal" on 
ephemA. Is it also ok to request bcg/brt-"external" on ephemB? This would be 
similar to ringback tone application in classical telephony (from the 
terminating side, to avoid clipping on answer), but in VoIP is there any reason 
to do so? </FONT></P>
<P dir=ltr><FONT face=Arial size=2>3. What should a gateway answer if it 
receives a ring command with an incorrect direction (like - using the example 
above - alert/ri-"internal" on physB)? The message is legal, so no error of this 
kind applies; on the other hand, it's not exactly a case for answering "513"; 
error "421"</FONT><B></B><B></B><B> <FONT face=TimesNewRoman,Bold>Unknown action 
or illegal combination of actions</FONT></B> <FONT face=TimesNewRoman,Bold>(also 
not an exact match) appears in H.248.8 as "not used"...</FONT></P>
<P dir=ltr><FONT face=TimesNewRoman,Bold>4.</FONT> <FONT face=Arial size=2>The 
usefullness of "internal" and "both" directions is clear for multi-party 
sessions (conference, announcements...). Are there other types of applications 
where directionality is very useful?</FONT></P>
<P dir=ltr><FONT face=Arial size=2>Many thanks,</FONT></P>
<P dir=ltr><FONT face=Arial size=2>Matia Marcu</FONT></P>
<P dir=ltr><FONT face=Arial size=2>Teledata 
Networks</FONT></P><BR></DIV>

</BODY>
</HTML>
------_=_NextPart_001_01C4DCF7.5250E8E6--


--===============1783989630==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco

--===============1783989630==--



From megaco-bounces@ietf.org  Wed Dec  8 03:55:22 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03159
	for <megaco-archive@lists.ietf.org>; Wed, 8 Dec 2004 03:55:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbxXq-0000HH-GT; Wed, 08 Dec 2004 03:51:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbxU9-00085d-9V
	for megaco@megatron.ietf.org; Wed, 08 Dec 2004 03:47:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01969
	for <megaco@ietf.org>; Wed, 8 Dec 2004 03:47:43 -0500 (EST)
Received: from [194.90.152.129] (helo=mr.teledata-networks.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbxar-0007oz-Nk
	for megaco@ietf.org; Wed, 08 Dec 2004 03:54:43 -0500
Received: from mr.teledata-networks.com (localhost.localdomain [127.0.0.1])
	by localhost.teledata-networks.com (Postfix) with ESMTP
	id 3B4F07C0070; Wed,  8 Dec 2004 10:43:08 +0200 (IST)
Received: from tndcmail.Teledata.Local (ADC-FW.ser.netvision.net.il [199.203
	.98.2])by mr.teledata-networks.com (Postfix) with ESMTPid 2AB687C0076;
	Wed, 8 Dec 2004 03:43:08 -0500 (EST)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Megaco] signal directionality
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Wed, 8 Dec 2004 10:45:17 +0200
Message-ID: <D6FAAE89E48C5B488B41BEBBDCD746CD06EB66@tndcmail.Teledata.Local>
Thread-Topic: [Megaco] signal directionality
Thread-Index: AcTc+jl0+AN0XIrITfad6SFyuLipVgAATHMw
From: "Matia Marcu" <Matia.Marcu@Teledata-Networks.com>
To: "Kevin Boyle" <kboyle@nortelnetworks.com>, <megaco@ietf.org>
X-imss-version: 2.0
X-imss-result: Passed
X-imss-scores: Clean:77.90115 C:17 M:1 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 4c463dcf97e2b913ab242796279c24d2
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1551550083=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1551550083==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4DD02.3E2E083E"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4DD02.3E2E083E
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Kevin,
=20
Thanks for the answer.=20
Right, in my text it should have been User A and User B.
=20
Concerning the ringback applied from the terminating side:
=20
"I can think of several cases where it would be better to place the =
ringback on ephemB; what if party B is on a different MG, controlled by =
a different MGC?"
=20
Classic telephony advocates tones being applied from the side close to =
the user receiving the tone, because this way the users receive the =
tones they are used to (example: in case of a call between US and Italy, =
if the call is broken, the US user would receive a US tone /English =
announcement and the user in Italy would receive an Italian tone =
/Italian announcement). Classic telephony also refers to ringback tone =
as a case when this rule must be broken (when the far-party answers, if =
the ringback tone comes from the originating side, there will be some =
switching in the exchanges on the way, which can lead to voice =
clipping).
=20
In case of both user A and user B being served by VoIP networks =
connected by a PSTN network, I guess that the ringback should come from =
ephemB. But what about a purely VoIP network - wouldn't it be preferable =
to have the ringback come from the outgoing gateway? Same for an =
unsuccessful call that fails in the terminating side backyard - I think =
that it's better to have the terminating exchange signal the call result =
out-of-band and have the outgoing side apply the tone /announcement. Of =
course, this requires some exchange of information between the involved =
MGC (and interworking signaling gateways, when relevant). Is this how =
things are happening today?
=20
Thank you,
=20
Matia Marcu
Teledata Networks

-----Original Message-----
From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]
Sent: Wednesday, December 08, 2004 9:47 AM
To: Matia Marcu; megaco@ietf.org
Subject: RE: [Megaco] signal directionality


Directionality is being added in H.248 version 3 as a default signal =
parameter.  In the definition there, "internal" plays the signal toward =
the center of the context.  To have it play in both directions, one =
would use "both". This means that the wording in Q.1950 section 4.4.48 =
appears to be incorrect.  Note that the wording in the packages =
themselves (Annex A) is correct.
=20
In your example, note that there are 4 terminations, not two.  I assume =
terminations A and B are the physical terminations in this case.  Keep =
in mind that physical and ephemeral terminations are not linked in =
H.248, except by being placed in a context together.
=20
Your examples on the ringback are all ok.  In theory, you could also put =
ringback on physB and use internal.  I can think of several cases where =
it would be better to place the ringback on ephemB; what if party B is =
on a different MG, controlled by a different MGC?
=20
A revision of H.248.8 is upcoming and will be released in conjunction =
with H.248.1v3.  We are defining a new error code that will cover this =
case: 449 "Unsupported or Unknown Parameter or Property Value".
=20
As for where this is useful, that would depend upon the requirements of =
the applications you are providing in your system.  I can think of =
several, including the "remote ringback" case discussed here.
=20
Kevin

  _____ =20

From: megaco-bounces@ietf.org on behalf of Matia Marcu
Sent: Wed 12/8/2004 9:09 AM
To: megaco@ietf.org
Subject: [Megaco] signal directionality





Please, I have a few questions concerning signal directionality.

1. I think that there is a slight difference between the definitions of =
directionality in Q.1950 and H.248.23 /H.248.27.=20

All the sources are clear concerning "external" and "both"; I quote here =
the explanations concerning "internal":

H.248.2x: "Internal" denotes that the signal shall proceed toward the =
centre of the context from the termination.

=20

Q.1950 - 4.4.48 signal direction: The stimulus can be placed on a =
termination so that none of the other terminations in the context "hear" =
it (external) or so that other terminations in the context "hear" it =
also (internal).                                            =20

I understand the first definition as saying that only the other =
terminations in the context "hear" the signal while the second =
definition says that these terminations also "hear" the signal. In the =
Q.1950 case, who is also hearing the signal? The termination itself =
(i.e. like in the "external" case)? If so, what's the difference between =
"internal" and "both"?

2. Assuming that the H.248.2x definition is correct, I'd like to verify =
a simple example of tone application:

Termination A (physA, ephemA in context C1) is calling termination B =
(physB, ephemB in context C2); termination A must receive ringback tone. =
The softswitch may request either bcg/brt (or cg/rt) on physA =
("external" direction explicit or implied) or bcg/brt -"internal" on =
ephemA. Is it also ok to request bcg/brt-"external" on ephemB? This =
would be similar to ringback tone application in classical telephony =
(from the terminating side, to avoid clipping on answer), but in VoIP is =
there any reason to do so?=20

3. What should a gateway answer if it receives a ring command with an =
incorrect direction (like - using the example above - =
alert/ri-"internal" on physB)? The message is legal, so no error of this =
kind applies; on the other hand, it's not exactly a case for answering =
"513"; error "421" Unknown action or illegal combination of actions =
(also not an exact match) appears in H.248.8 as "not used"...

4. The usefullness of "internal" and "both" directions is clear for =
multi-party sessions (conference, announcements...). Are there other =
types of applications where directionality is very useful?

Many thanks,

Matia Marcu

Teledata Networks



------_=_NextPart_001_01C4DD02.3E2E083E
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>signal directionality</TITLE>

<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D762265607-08122004><FONT face=3DArial color=3D#0000ff =

size=3D2>Kevin,</FONT></SPAN></DIV>
<DIV><SPAN class=3D762265607-08122004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D762265607-08122004><FONT face=3DArial color=3D#0000ff =
size=3D2>Thanks=20
for the answer. </FONT></SPAN></DIV>
<DIV><SPAN class=3D762265607-08122004><FONT face=3DArial color=3D#0000ff =
size=3D2>Right,=20
in my text it should have been User A and User B.</FONT></SPAN></DIV>
<DIV><SPAN class=3D762265607-08122004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D762265607-08122004><FONT face=3DArial color=3D#0000ff =

size=3D2>Concerning the ringback applied from the terminating=20
side:</FONT></SPAN></DIV>
<DIV><SPAN class=3D762265607-08122004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D762265607-08122004><FONT face=3DArial size=3D2>"I can =
think of=20
several cases where it would be better to place the ringback on ephemB; =
what if=20
party B is on a different MG, controlled by a different=20
MGC?"</FONT></SPAN></DIV>
<DIV><SPAN class=3D762265607-08122004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D762265607-08122004><FONT face=3DArial color=3D#0000ff =

size=3D2>Classic telephony advocates tones being applied from the side =
close to=20
the user receiving the tone, because this way the users receive the =
tones they=20
are used to&nbsp;(example: in case of a call&nbsp;between=20
US&nbsp;and&nbsp;Italy, if the call is&nbsp;broken, the&nbsp;US user =
would=20
receive&nbsp;a&nbsp;US&nbsp;tone /English announcement and the&nbsp;user =
in=20
Italy would receive&nbsp;an Italian&nbsp;tone&nbsp;/Italian=20
announcement).&nbsp;C</FONT></SPAN><SPAN =
class=3D762265607-08122004><FONT=20
face=3DArial color=3D#0000ff size=3D2>lassic telephony&nbsp;also refers =
to ringback=20
tone as&nbsp;a&nbsp;case when this&nbsp;rule must be broken (when the =
far-party=20
answers, if the ringback tone comes from the originating side, there =
will be=20
some switching in&nbsp;</FONT></SPAN><SPAN =
class=3D762265607-08122004><FONT=20
face=3DArial color=3D#0000ff size=3D2>the exchanges on the way, which =
can lead to=20
voice clipping).</FONT></SPAN></DIV>
<DIV><SPAN class=3D762265607-08122004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D762265607-08122004><FONT face=3DArial color=3D#0000ff =
size=3D2>In=20
case of&nbsp;both user A and user B being served by VoIP =
networks&nbsp;connected=20
by a PSTN network, I&nbsp;guess that the ringback should come from =
ephemB. But=20
what about a purely VoIP network - wouldn't it be&nbsp;preferable to =
have the=20
ringback come from the outgoing gateway? Same for an unsuccessful call =
that=20
fails in the terminating side backyard - I think that it's better to =
have the=20
terminating exchange signal the call result out-of-band and have the =
outgoing=20
side apply the tone /announcement. Of course, this requires some =
exchange of=20
information between the involved MGC (and interworking signaling =
gateways, when=20
relevant). Is this how things are happening today?</FONT></SPAN></DIV>
<DIV><SPAN class=3D762265607-08122004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D762265607-08122004><FONT face=3DArial color=3D#0000ff =
size=3D2>Thank=20
you,</FONT></SPAN></DIV>
<DIV><SPAN class=3D762265607-08122004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D762265607-08122004><FONT face=3DArial color=3D#0000ff =
size=3D2>Matia=20
Marcu</FONT></SPAN></DIV>
<DIV><SPAN class=3D762265607-08122004><FONT face=3DArial color=3D#0000ff =

size=3D2>Teledata Networks</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Kevin Boyle=20
  [mailto:kboyle@nortelnetworks.com]<BR><B>Sent:</B> Wednesday, December =
08,=20
  2004 9:47 AM<BR><B>To:</B> Matia Marcu; =
megaco@ietf.org<BR><B>Subject:</B> RE:=20
  [Megaco] signal directionality<BR><BR></FONT></DIV>
  <DIV id=3DidOWAReplyText89755 dir=3Dltr>
  <DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2>Directionality is being=20
  added in H.248 version 3 as a default signal parameter.&nbsp; In the=20
  definition there, "internal" plays the signal toward the center of the =

  context.&nbsp; To have it play in both directions, one would use =
"both".=20
  </FONT><FONT face=3DArial size=3D2>This means that the wording in =
Q.1950 section=20
  4.4.48 appears to be incorrect.&nbsp; Note that the wording in the =
packages=20
  themselves (Annex A) is correct.</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>In your example, note that =
there are 4=20
  terminations, not two.&nbsp; I assume terminations A and B are the =
physical=20
  terminations in this case.&nbsp; Keep in mind that physical and =
ephemeral=20
  terminations are not linked in H.248, except by being placed in a =
context=20
  together.</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>Your examples on the =
ringback are all=20
  ok.&nbsp; In theory, you could also put ringback on physB and use=20
  internal.&nbsp; I can think of several cases where it would be better =
to place=20
  the ringback on ephemB; what if party B is on a different MG, =
controlled by a=20
  different MGC?</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>A revision of H.248.8 is =
upcoming and=20
  will be released in conjunction with H.248.1v3.&nbsp; We are defining =
a new=20
  error code that will cover this case: 449 "Unsupported or Unknown =
Parameter or=20
  Property Value".</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>As for where this is =
useful, that would=20
  depend upon the requirements of the applications you are providing in =
your=20
  system.&nbsp;&nbsp;I can think of several, including the "remote =
ringback"=20
  case discussed here.</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>Kevin</FONT></DIV></DIV>
  <DIV dir=3Dltr><BR>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> megaco-bounces@ietf.org on =
behalf of=20
  Matia Marcu<BR><B>Sent:</B> Wed 12/8/2004 9:09 AM<BR><B>To:</B>=20
  megaco@ietf.org<BR><B>Subject:</B> [Megaco] signal=20
  directionality<BR></FONT><BR></DIV>
  <DIV><BR><BR>
  <P dir=3Dltr><FONT face=3DArial size=3D2>Please, I have a few =
questions concerning=20
  signal directionality.</FONT></P>
  <P dir=3Dltr><FONT face=3DArial size=3D2>1. I think that there is a =
slight=20
  difference between the definitions of directionality in Q.1950 and =
H.248.23=20
  /H.248.27. </FONT></P>
  <P dir=3Dltr><FONT face=3DArial size=3D2>All the sources are clear =
concerning=20
  "external" and "both"; I quote here the explanations concerning=20
  "internal":</FONT></P>
  <P dir=3Dltr><FONT face=3DArial size=3D2>H.248.2x:</FONT><FONT =
face=3DTimesNewRoman>=20
  "Internal" denotes that the signal shall proceed toward the centre of =
the=20
  context from the termination.</FONT></P>
  <P dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</P>
  <P dir=3Dltr><FONT face=3DArial size=3D2>Q.1950 -</FONT> <FONT=20
  face=3DTimesNewRoman,Bold>4.4.48 signal directio</FONT><FONT=20
  face=3DTimesNewRoman>n: The stimulus can be placed on a termination so =
that none=20
  of the other terminations in the context "hear" it (external) or so =
that other=20
  terminations in the context "hear" it also<B></B> =
(internal).</FONT><FONT=20
  face=3DArial size=3D2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;=20
</FONT></P>
  <P dir=3Dltr><FONT face=3DArial size=3D2>I understand the first =
definition as saying=20
  that</FONT><B> <FONT face=3DArial size=3D2>only</FONT></B> <FONT =
face=3DArial=20
  size=3D2>the other terminations in the context "hear" the signal while =
the=20
  second definition says that these terminations</FONT><B> <FONT =
face=3DArial=20
  size=3D2>also</FONT></B><FONT face=3DArial size=3D2> "hear" the =
signal. In the=20
  Q.1950 case, who is</FONT><B> <FONT face=3DArial =
size=3D2>also</FONT></B><FONT=20
  face=3DArial size=3D2> hearing the signal? The termination itself =
(i.e. like in=20
  the "external" case)? If so, what's the difference between "internal" =
and=20
  "both"?</FONT></P>
  <P dir=3Dltr><FONT face=3DArial size=3D2>2. Assuming that the H.248.2x =
definition is=20
  correct, I'd like to verify a simple example of tone =
application:</FONT></P>
  <P dir=3Dltr><FONT face=3DArial size=3D2>Termination A (physA, ephemA =
in context C1)=20
  is calling termination B (physB, ephemB in context C2); termination A =
must=20
  receive ringback tone. The softswitch may request either bcg/brt (or =
cg/rt) on=20
  physA ("external" direction explicit or implied) or bcg/brt =
-"internal" on=20
  ephemA. Is it also ok to request bcg/brt-"external" on ephemB? This =
would be=20
  similar to ringback tone application in classical telephony (from the=20
  terminating side, to avoid clipping on answer), but in VoIP is there =
any=20
  reason to do so? </FONT></P>
  <P dir=3Dltr><FONT face=3DArial size=3D2>3. What should a gateway =
answer if it=20
  receives a ring command with an incorrect direction (like - using the =
example=20
  above - alert/ri-"internal" on physB)? The message is legal, so no =
error of=20
  this kind applies; on the other hand, it's not exactly a case for =
answering=20
  "513"; error "421"</FONT><B></B><B></B><B> <FONT=20
  face=3DTimesNewRoman,Bold>Unknown action or illegal combination of=20
  actions</FONT></B> <FONT face=3DTimesNewRoman,Bold>(also not an exact =
match)=20
  appears in H.248.8 as "not used"...</FONT></P>
  <P dir=3Dltr><FONT face=3DTimesNewRoman,Bold>4.</FONT> <FONT =
face=3DArial size=3D2>The=20
  usefullness of "internal" and "both" directions is clear for =
multi-party=20
  sessions (conference, announcements...). Are there other types of =
applications=20
  where directionality is very useful?</FONT></P>
  <P dir=3Dltr><FONT face=3DArial size=3D2>Many thanks,</FONT></P>
  <P dir=3Dltr><FONT face=3DArial size=3D2>Matia Marcu</FONT></P>
  <P dir=3Dltr><FONT face=3DArial size=3D2>Teledata=20
Networks</FONT></P><BR></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C4DD02.3E2E083E--


--===============1551550083==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco

--===============1551550083==--



From megaco-bounces@ietf.org  Wed Dec  8 11:30:34 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11965
	for <megaco-archive@lists.ietf.org>; Wed, 8 Dec 2004 11:30:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc4XS-0001iG-62; Wed, 08 Dec 2004 11:19:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cc4JA-0005kQ-GR
	for megaco@megatron.ietf.org; Wed, 08 Dec 2004 11:04:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09152
	for <megaco@ietf.org>; Wed, 8 Dec 2004 11:04:50 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cc4Px-0000lX-Pw
	for megaco@ietf.org; Wed, 08 Dec 2004 11:11:54 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iB8G47j18078; Wed, 8 Dec 2004 11:04:07 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YFGTFQ67>; Wed, 8 Dec 2004 11:04:07 -0500
Message-ID: <B258A372CEA20246A363BB86753DB5360124B680@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Matia Marcu <Matia.Marcu@Teledata-Networks.com>, megaco@ietf.org
Subject: RE: [Megaco] signal directionality
Date: Wed, 8 Dec 2004 11:03:47 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 5b943e80df8c8cad631fd60298783617
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0511570555=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============0511570555==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4DD03.6A307E71"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C4DD03.6A307E71
Content-Type: text/plain;
	charset="iso-8859-1"

Generally speaking, the vendors that are highly active in the VoIP market
today are deploying solutions that are functionally equivalne tot he PSTN.
Subscribers understand how the PSTN works, so it is seen as desireable for
the PSTN replacement to work more-or-less equivalently.
 
If the MGCs can communicate the intention of where to play the ringbakc,
then great.  But in the absence of that capability, the MGC should take the
actions it thinks are necessary.  I belive it is a fine assumption to try to
function the same way as the PSTN.
 
Kevin

  _____  

From: Matia Marcu [mailto:Matia.Marcu@Teledata-Networks.com]
Sent: Wed 12/8/2004 10:45 AM
To: Boyle, Kevin [NCRTP:3Z40:EXCH]; megaco@ietf.org
Subject: RE: [Megaco] signal directionality


Kevin,
 
Thanks for the answer. 
Right, in my text it should have been User A and User B.
 
Concerning the ringback applied from the terminating side:
 
"I can think of several cases where it would be better to place the ringback
on ephemB; what if party B is on a different MG, controlled by a different
MGC?"
 
Classic telephony advocates tones being applied from the side close to the
user receiving the tone, because this way the users receive the tones they
are used to (example: in case of a call between US and Italy, if the call is
broken, the US user would receive a US tone /English announcement and the
user in Italy would receive an Italian tone /Italian announcement). Classic
telephony also refers to ringback tone as a case when this rule must be
broken (when the far-party answers, if the ringback tone comes from the
originating side, there will be some switching in the exchanges on the way,
which can lead to voice clipping).
 
In case of both user A and user B being served by VoIP networks connected by
a PSTN network, I guess that the ringback should come from ephemB. But what
about a purely VoIP network - wouldn't it be preferable to have the ringback
come from the outgoing gateway? Same for an unsuccessful call that fails in
the terminating side backyard - I think that it's better to have the
terminating exchange signal the call result out-of-band and have the
outgoing side apply the tone /announcement. Of course, this requires some
exchange of information between the involved MGC (and interworking signaling
gateways, when relevant). Is this how things are happening today?
 
Thank you,
 
Matia Marcu
Teledata Networks

-----Original Message-----
From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]
Sent: Wednesday, December 08, 2004 9:47 AM
To: Matia Marcu; megaco@ietf.org
Subject: RE: [Megaco] signal directionality


Directionality is being added in H.248 version 3 as a default signal
parameter.  In the definition there, "internal" plays the signal toward the
center of the context.  To have it play in both directions, one would use
"both". This means that the wording in Q.1950 section 4.4.48 appears to be
incorrect.  Note that the wording in the packages themselves (Annex A) is
correct.
 
In your example, note that there are 4 terminations, not two.  I assume
terminations A and B are the physical terminations in this case.  Keep in
mind that physical and ephemeral terminations are not linked in H.248,
except by being placed in a context together.
 
Your examples on the ringback are all ok.  In theory, you could also put
ringback on physB and use internal.  I can think of several cases where it
would be better to place the ringback on ephemB; what if party B is on a
different MG, controlled by a different MGC?
 
A revision of H.248.8 is upcoming and will be released in conjunction with
H.248.1v3.  We are defining a new error code that will cover this case: 449
"Unsupported or Unknown Parameter or Property Value".
 
As for where this is useful, that would depend upon the requirements of the
applications you are providing in your system.  I can think of several,
including the "remote ringback" case discussed here.
 
Kevin

  _____  

From: megaco-bounces@ietf.org on behalf of Matia Marcu
Sent: Wed 12/8/2004 9:09 AM
To: megaco@ietf.org
Subject: [Megaco] signal directionality





Please, I have a few questions concerning signal directionality.

1. I think that there is a slight difference between the definitions of
directionality in Q.1950 and H.248.23 /H.248.27. 

All the sources are clear concerning "external" and "both"; I quote here the
explanations concerning "internal":

H.248.2x: "Internal" denotes that the signal shall proceed toward the centre
of the context from the termination.

 

Q.1950 - 4.4.48 signal direction: The stimulus can be placed on a
termination so that none of the other terminations in the context "hear" it
(external) or so that other terminations in the context "hear" it also
(internal).                                             

I understand the first definition as saying that only the other terminations
in the context "hear" the signal while the second definition says that these
terminations also "hear" the signal. In the Q.1950 case, who is also hearing
the signal? The termination itself (i.e. like in the "external" case)? If
so, what's the difference between "internal" and "both"?

2. Assuming that the H.248.2x definition is correct, I'd like to verify a
simple example of tone application:

Termination A (physA, ephemA in context C1) is calling termination B (physB,
ephemB in context C2); termination A must receive ringback tone. The
softswitch may request either bcg/brt (or cg/rt) on physA ("external"
direction explicit or implied) or bcg/brt -"internal" on ephemA. Is it also
ok to request bcg/brt-"external" on ephemB? This would be similar to
ringback tone application in classical telephony (from the terminating side,
to avoid clipping on answer), but in VoIP is there any reason to do so? 

3. What should a gateway answer if it receives a ring command with an
incorrect direction (like - using the example above - alert/ri-"internal" on
physB)? The message is legal, so no error of this kind applies; on the other
hand, it's not exactly a case for answering "513"; error "421" Unknown
action or illegal combination of actions (also not an exact match) appears
in H.248.8 as "not used"...

4. The usefullness of "internal" and "both" directions is clear for
multi-party sessions (conference, announcements...). Are there other types
of applications where directionality is very useful?

Many thanks,

Matia Marcu

Teledata Networks



------_=_NextPart_001_01C4DD03.6A307E71
Content-Type: text/html;
	charset="iso-8859-1"


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<TITLE>signal directionality</TITLE>

<META content="MSHTML 6.00.2800.1106" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText23742 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Generally speaking, the 
vendors that are highly active in the VoIP market today are deploying solutions 
that are functionally equivalne tot he PSTN.&nbsp; Subscribers understand how 
the PSTN works, so it is seen as desireable for the PSTN replacement to work 
more-or-less equivalently.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr><FONT face=Arial size=2>If the MGCs can communicate the intention 
of where to play the ringbakc, then great.&nbsp; But in the absence of that 
capability, the MGC should take the actions it thinks are necessary.&nbsp; I 
belive it is a fine assumption to try to function the same way as the 
PSTN.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr><FONT face=Arial size=2>Kevin</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Matia Marcu 
[mailto:Matia.Marcu@Teledata-Networks.com]<BR><B>Sent:</B> Wed 12/8/2004 10:45 
AM<BR><B>To:</B> Boyle, Kevin [NCRTP:3Z40:EXCH]; 
megaco@ietf.org<BR><B>Subject:</B> RE: [Megaco] signal 
directionality<BR></FONT><BR></DIV>
<DIV>
<DIV><SPAN class=762265607-08122004><FONT face=Arial color=#0000ff 
size=2>Kevin,</FONT></SPAN></DIV>
<DIV><SPAN class=762265607-08122004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=762265607-08122004><FONT face=Arial color=#0000ff size=2>Thanks 
for the answer. </FONT></SPAN></DIV>
<DIV><SPAN class=762265607-08122004><FONT face=Arial color=#0000ff size=2>Right, 
in my text it should have been User A and User B.</FONT></SPAN></DIV>
<DIV><SPAN class=762265607-08122004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=762265607-08122004><FONT face=Arial color=#0000ff 
size=2>Concerning the ringback applied from the terminating 
side:</FONT></SPAN></DIV>
<DIV><SPAN class=762265607-08122004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=762265607-08122004><FONT face=Arial size=2>"I can think of 
several cases where it would be better to place the ringback on ephemB; what if 
party B is on a different MG, controlled by a different 
MGC?"</FONT></SPAN></DIV>
<DIV><SPAN class=762265607-08122004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=762265607-08122004><FONT face=Arial color=#0000ff 
size=2>Classic telephony advocates tones being applied from the side close to 
the user receiving the tone, because this way the users receive the tones they 
are used to&nbsp;(example: in case of a call&nbsp;between 
US&nbsp;and&nbsp;Italy, if the call is&nbsp;broken, the&nbsp;US user would 
receive&nbsp;a&nbsp;US&nbsp;tone /English announcement and the&nbsp;user in 
Italy would receive&nbsp;an Italian&nbsp;tone&nbsp;/Italian 
announcement).&nbsp;C</FONT></SPAN><SPAN class=762265607-08122004><FONT 
face=Arial color=#0000ff size=2>lassic telephony&nbsp;also refers to ringback 
tone as&nbsp;a&nbsp;case when this&nbsp;rule must be broken (when the far-party 
answers, if the ringback tone comes from the originating side, there will be 
some switching in&nbsp;</FONT></SPAN><SPAN class=762265607-08122004><FONT 
face=Arial color=#0000ff size=2>the exchanges on the way, which can lead to 
voice clipping).</FONT></SPAN></DIV>
<DIV><SPAN class=762265607-08122004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=762265607-08122004><FONT face=Arial color=#0000ff size=2>In 
case of&nbsp;both user A and user B being served by VoIP networks&nbsp;connected 
by a PSTN network, I&nbsp;guess that the ringback should come from ephemB. But 
what about a purely VoIP network - wouldn't it be&nbsp;preferable to have the 
ringback come from the outgoing gateway? Same for an unsuccessful call that 
fails in the terminating side backyard - I think that it's better to have the 
terminating exchange signal the call result out-of-band and have the outgoing 
side apply the tone /announcement. Of course, this requires some exchange of 
information between the involved MGC (and interworking signaling gateways, when 
relevant). Is this how things are happening today?</FONT></SPAN></DIV>
<DIV><SPAN class=762265607-08122004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=762265607-08122004><FONT face=Arial color=#0000ff size=2>Thank 
you,</FONT></SPAN></DIV>
<DIV><SPAN class=762265607-08122004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=762265607-08122004><FONT face=Arial color=#0000ff size=2>Matia 
Marcu</FONT></SPAN></DIV>
<DIV><SPAN class=762265607-08122004><FONT face=Arial color=#0000ff 
size=2>Teledata Networks</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Kevin Boyle 
  [mailto:kboyle@nortelnetworks.com]<BR><B>Sent:</B> Wednesday, December 08, 
  2004 9:47 AM<BR><B>To:</B> Matia Marcu; megaco@ietf.org<BR><B>Subject:</B> RE: 
  [Megaco] signal directionality<BR><BR></FONT></DIV>
  <DIV id=idOWAReplyText89755 dir=ltr>
  <DIV dir=ltr><FONT face=Arial color=#000000 size=2>Directionality is being 
  added in H.248 version 3 as a default signal parameter.&nbsp; In the 
  definition there, "internal" plays the signal toward the center of the 
  context.&nbsp; To have it play in both directions, one would use "both". 
  </FONT><FONT face=Arial size=2>This means that the wording in Q.1950 section 
  4.4.48 appears to be incorrect.&nbsp; Note that the wording in the packages 
  themselves (Annex A) is correct.</FONT></DIV>
  <DIV dir=ltr><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV dir=ltr><FONT face=Arial size=2>In your example, note that there are 4 
  terminations, not two.&nbsp; I assume terminations A and B are the physical 
  terminations in this case.&nbsp; Keep in mind that physical and ephemeral 
  terminations are not linked in H.248, except by being placed in a context 
  together.</FONT></DIV>
  <DIV dir=ltr><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV dir=ltr><FONT face=Arial size=2>Your examples on the ringback are all 
  ok.&nbsp; In theory, you could also put ringback on physB and use 
  internal.&nbsp; I can think of several cases where it would be better to place 
  the ringback on ephemB; what if party B is on a different MG, controlled by a 
  different MGC?</FONT></DIV>
  <DIV dir=ltr><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV dir=ltr><FONT face=Arial size=2>A revision of H.248.8 is upcoming and 
  will be released in conjunction with H.248.1v3.&nbsp; We are defining a new 
  error code that will cover this case: 449 "Unsupported or Unknown Parameter or 
  Property Value".</FONT></DIV>
  <DIV dir=ltr><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV dir=ltr><FONT face=Arial size=2>As for where this is useful, that would 
  depend upon the requirements of the applications you are providing in your 
  system.&nbsp;&nbsp;I can think of several, including the "remote ringback" 
  case discussed here.</FONT></DIV>
  <DIV dir=ltr><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV dir=ltr><FONT face=Arial size=2>Kevin</FONT></DIV></DIV>
  <DIV dir=ltr><BR>
  <HR tabIndex=-1>
  <FONT face=Tahoma size=2><B>From:</B> megaco-bounces@ietf.org on behalf of 
  Matia Marcu<BR><B>Sent:</B> Wed 12/8/2004 9:09 AM<BR><B>To:</B> 
  megaco@ietf.org<BR><B>Subject:</B> [Megaco] signal 
  directionality<BR></FONT><BR></DIV>
  <DIV><BR><BR>
  <P dir=ltr><FONT face=Arial size=2>Please, I have a few questions concerning 
  signal directionality.</FONT></P>
  <P dir=ltr><FONT face=Arial size=2>1. I think that there is a slight 
  difference between the definitions of directionality in Q.1950 and H.248.23 
  /H.248.27. </FONT></P>
  <P dir=ltr><FONT face=Arial size=2>All the sources are clear concerning 
  "external" and "both"; I quote here the explanations concerning 
  "internal":</FONT></P>
  <P dir=ltr><FONT face=Arial size=2>H.248.2x:</FONT><FONT face=TimesNewRoman> 
  "Internal" denotes that the signal shall proceed toward the centre of the 
  context from the termination.</FONT></P>
  <P dir=ltr><FONT face=Arial size=2></FONT>&nbsp;</P>
  <P dir=ltr><FONT face=Arial size=2>Q.1950 -</FONT> <FONT 
  face=TimesNewRoman,Bold>4.4.48 signal directio</FONT><FONT 
  face=TimesNewRoman>n: The stimulus can be placed on a termination so that none 
  of the other terminations in the context "hear" it (external) or so that other 
  terminations in the context "hear" it also<B></B> (internal).</FONT><FONT 
  face=Arial size=2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; 
</FONT></P>
  <P dir=ltr><FONT face=Arial size=2>I understand the first definition as saying 
  that</FONT><B> <FONT face=Arial size=2>only</FONT></B> <FONT face=Arial 
  size=2>the other terminations in the context "hear" the signal while the 
  second definition says that these terminations</FONT><B> <FONT face=Arial 
  size=2>also</FONT></B><FONT face=Arial size=2> "hear" the signal. In the 
  Q.1950 case, who is</FONT><B> <FONT face=Arial size=2>also</FONT></B><FONT 
  face=Arial size=2> hearing the signal? The termination itself (i.e. like in 
  the "external" case)? If so, what's the difference between "internal" and 
  "both"?</FONT></P>
  <P dir=ltr><FONT face=Arial size=2>2. Assuming that the H.248.2x definition is 
  correct, I'd like to verify a simple example of tone application:</FONT></P>
  <P dir=ltr><FONT face=Arial size=2>Termination A (physA, ephemA in context C1) 
  is calling termination B (physB, ephemB in context C2); termination A must 
  receive ringback tone. The softswitch may request either bcg/brt (or cg/rt) on 
  physA ("external" direction explicit or implied) or bcg/brt -"internal" on 
  ephemA. Is it also ok to request bcg/brt-"external" on ephemB? This would be 
  similar to ringback tone application in classical telephony (from the 
  terminating side, to avoid clipping on answer), but in VoIP is there any 
  reason to do so? </FONT></P>
  <P dir=ltr><FONT face=Arial size=2>3. What should a gateway answer if it 
  receives a ring command with an incorrect direction (like - using the example 
  above - alert/ri-"internal" on physB)? The message is legal, so no error of 
  this kind applies; on the other hand, it's not exactly a case for answering 
  "513"; error "421"</FONT><B></B><B></B><B> <FONT 
  face=TimesNewRoman,Bold>Unknown action or illegal combination of 
  actions</FONT></B> <FONT face=TimesNewRoman,Bold>(also not an exact match) 
  appears in H.248.8 as "not used"...</FONT></P>
  <P dir=ltr><FONT face=TimesNewRoman,Bold>4.</FONT> <FONT face=Arial size=2>The 
  usefullness of "internal" and "both" directions is clear for multi-party 
  sessions (conference, announcements...). Are there other types of applications 
  where directionality is very useful?</FONT></P>
  <P dir=ltr><FONT face=Arial size=2>Many thanks,</FONT></P>
  <P dir=ltr><FONT face=Arial size=2>Matia Marcu</FONT></P>
  <P dir=ltr><FONT face=Arial size=2>Teledata 
Networks</FONT></P><BR></DIV></BLOCKQUOTE></DIV></BODY></HTML>

------_=_NextPart_001_01C4DD03.6A307E71--


--===============0511570555==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco

--===============0511570555==--



From megaco-bounces@ietf.org  Thu Dec  9 00:35:24 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05434
	for <megaco-archive@lists.ietf.org>; Thu, 9 Dec 2004 00:35:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcGuZ-0006Ht-BV; Thu, 09 Dec 2004 00:32:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcGgJ-0002tD-8o
	for megaco@megatron.ietf.org; Thu, 09 Dec 2004 00:17:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04587
	for <megaco@ietf.org>; Thu, 9 Dec 2004 00:17:32 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcGn3-0004KN-K7
	for megaco@ietf.org; Thu, 09 Dec 2004 00:24:44 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iB95HMO6019624 for <megaco@ietf.org>; Thu, 9 Dec 2004 06:17:22 +0100
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 9 Dec 2004 06:17:22 +0100
Received: from eaubrnt019.epa.ericsson.se ([146.11.9.165]) by
	esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id WHLVTKT4; Thu, 9 Dec 2004 06:17:22 +0100
Received: from ericsson.com (EG2E500202DSEGL [146.11.22.78]) by
	eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id WTM87NDJ; Thu, 9 Dec 2004 16:17:17 +1100
Message-ID: <41B7DE3B.6040401@ericsson.com>
Date: Thu, 09 Dec 2004 16:10:19 +1100
X-Sybari-Trust: 74832b4d a5e9b67f 19596640 00000139
From: Christian Groves <christian.groves@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Kevin Boyle <kboyle@nortelnetworks.com>
Subject: Re: [Megaco] signal directionality
References: <B258A372CEA20246A363BB86753DB5360124B680@zrtphxm2>
In-Reply-To: <B258A372CEA20246A363BB86753DB5360124B680@zrtphxm2>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Dec 2004 05:17:22.0405 (UTC)
	FILETIME=[5CCAA950:01C4DDAE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9af087f15dbdd4c64ae6bbcdbc5b1d44
Content-Transfer-Encoding: 7bit
Cc: megaco@ietf.org, Matia Marcu <Matia.Marcu@Teledata-Networks.com>
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

With respect to Q.1950 I believe the intention is not to re-define how direction 
is used. The full quote for:
4.4.48	signal direction: Indicates the directionality of a stimulus applied to a 
termination. The stimulus can be placed on a termination so that none of the 
other terminations in the context "hear" it (external) or so that other 
terminations in the context "hear" it also (internal). The direction may be set 
to (both way) indicating that all the terminations in the context "hear" it as 
well as it being sent external to the BIWF.

Its clear that "both" and "internal" are distinguished. The use of "also" is 
meant to refer to the additional capability of "internal" rather than "also" 
with regards to the termination played.

Christian

Kevin Boyle wrote:

> Generally speaking, the vendors that are highly active in the VoIP 
> market today are deploying solutions that are functionally equivalne tot 
> he PSTN.  Subscribers understand how the PSTN works, so it is seen as 
> desireable for the PSTN replacement to work more-or-less equivalently.
>  
> If the MGCs can communicate the intention of where to play the ringbakc, 
> then great.  But in the absence of that capability, the MGC should take 
> the actions it thinks are necessary.  I belive it is a fine assumption 
> to try to function the same way as the PSTN.
>  
> Kevin
> 
> ------------------------------------------------------------------------
> From: Matia Marcu [mailto:Matia.Marcu@Teledata-Networks.com]
> Sent: Wed 12/8/2004 10:45 AM
> To: Boyle, Kevin [NCRTP:3Z40:EXCH]; megaco@ietf.org
> Subject: RE: [Megaco] signal directionality
> 
> Kevin,
>  
> Thanks for the answer.
> Right, in my text it should have been User A and User B.
>  
> Concerning the ringback applied from the terminating side:
>  
> "I can think of several cases where it would be better to place the 
> ringback on ephemB; what if party B is on a different MG, controlled by 
> a different MGC?"
>  
> Classic telephony advocates tones being applied from the side close to 
> the user receiving the tone, because this way the users receive the 
> tones they are used to (example: in case of a call between US and Italy, 
> if the call is broken, the US user would receive a US tone /English 
> announcement and the user in Italy would receive an 
> Italian tone /Italian announcement). Classic telephony also refers to 
> ringback tone as a case when this rule must be broken (when the 
> far-party answers, if the ringback tone comes from the originating side, 
> there will be some switching in the exchanges on the way, which can lead 
> to voice clipping).
>  
> In case of both user A and user B being served by VoIP 
> networks connected by a PSTN network, I guess that the ringback should 
> come from ephemB. But what about a purely VoIP network - wouldn't it 
> be preferable to have the ringback come from the outgoing gateway? Same 
> for an unsuccessful call that fails in the terminating side backyard - I 
> think that it's better to have the terminating exchange signal the call 
> result out-of-band and have the outgoing side apply the tone 
> /announcement. Of course, this requires some exchange of information 
> between the involved MGC (and interworking signaling gateways, when 
> relevant). Is this how things are happening today?
>  
> Thank you,
>  
> Matia Marcu
> Teledata Networks
> 
>     -----Original Message-----
>     From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]
>     Sent: Wednesday, December 08, 2004 9:47 AM
>     To: Matia Marcu; megaco@ietf.org
>     Subject: RE: [Megaco] signal directionality
> 
>     Directionality is being added in H.248 version 3 as a default signal
>     parameter.  In the definition there, "internal" plays the signal
>     toward the center of the context.  To have it play in both
>     directions, one would use "both". This means that the wording in
>     Q.1950 section 4.4.48 appears to be incorrect.  Note that the
>     wording in the packages themselves (Annex A) is correct.
>      
>     In your example, note that there are 4 terminations, not two.  I
>     assume terminations A and B are the physical terminations in this
>     case.  Keep in mind that physical and ephemeral terminations are not
>     linked in H.248, except by being placed in a context together.
>      
>     Your examples on the ringback are all ok.  In theory, you could also
>     put ringback on physB and use internal.  I can think of several
>     cases where it would be better to place the ringback on ephemB; what
>     if party B is on a different MG, controlled by a different MGC?
>      
>     A revision of H.248.8 is upcoming and will be released in
>     conjunction with H.248.1v3.  We are defining a new error code that
>     will cover this case: 449 "Unsupported or Unknown Parameter or
>     Property Value".
>      
>     As for where this is useful, that would depend upon the requirements
>     of the applications you are providing in your system.  I can think
>     of several, including the "remote ringback" case discussed here.
>      
>     Kevin
> 
>     ------------------------------------------------------------------------
>     From: megaco-bounces@ietf.org on behalf of Matia Marcu
>     Sent: Wed 12/8/2004 9:09 AM
>     To: megaco@ietf.org
>     Subject: [Megaco] signal directionality
> 
> 
> 
>     Please, I have a few questions concerning signal directionality.
> 
>     1. I think that there is a slight difference between the definitions
>     of directionality in Q.1950 and H.248.23 /H.248.27.
> 
>     All the sources are clear concerning "external" and "both"; I quote
>     here the explanations concerning "internal":
> 
>     H.248.2x: "Internal" denotes that the signal shall proceed toward
>     the centre of the context from the termination.
> 
>      
> 
>     Q.1950 - 4.4.48 signal direction: The stimulus can be placed on a
>     termination so that none of the other terminations in the context
>     "hear" it (external) or so that other terminations in the context
>     "hear" it also (internal).                                            
> 
>     I understand the first definition as saying that only the other
>     terminations in the context "hear" the signal while the second
>     definition says that these terminations also "hear" the signal. In
>     the Q.1950 case, who is also hearing the signal? The termination
>     itself (i.e. like in the "external" case)? If so, what's the
>     difference between "internal" and "both"?
> 
>     2. Assuming that the H.248.2x definition is correct, I'd like to
>     verify a simple example of tone application:
> 
>     Termination A (physA, ephemA in context C1) is calling termination B
>     (physB, ephemB in context C2); termination A must receive ringback
>     tone. The softswitch may request either bcg/brt (or cg/rt) on physA
>     ("external" direction explicit or implied) or bcg/brt -"internal" on
>     ephemA. Is it also ok to request bcg/brt-"external" on ephemB? This
>     would be similar to ringback tone application in classical telephony
>     (from the terminating side, to avoid clipping on answer), but in
>     VoIP is there any reason to do so?
> 
>     3. What should a gateway answer if it receives a ring command with
>     an incorrect direction (like - using the example above -
>     alert/ri-"internal" on physB)? The message is legal, so no error of
>     this kind applies; on the other hand, it's not exactly a case for
>     answering "513"; error "421" Unknown action or illegal combination
>     of actions (also not an exact match) appears in H.248.8 as "not used"...
> 
>     4. The usefullness of "internal" and "both" directions is clear for
>     multi-party sessions (conference, announcements...). Are there other
>     types of applications where directionality is very useful?
> 
>     Many thanks,
> 
>     Matia Marcu
> 
>     Teledata Networks
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco



_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Tue Dec 14 10:18:32 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07425
	for <megaco-archive@lists.ietf.org>; Tue, 14 Dec 2004 10:18:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeEAe-0001Fs-4j; Tue, 14 Dec 2004 10:01:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ce1Lb-0007yS-7g
	for megaco@megatron.ietf.org; Mon, 13 Dec 2004 20:19:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15875
	for <megaco@ietf.org>; Mon, 13 Dec 2004 20:19:26 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ce1TV-0008SV-7m
	for megaco@ietf.org; Mon, 13 Dec 2004 20:27:38 -0500
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-5.cisco.com with ESMTP; 13 Dec 2004 17:18:58 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com
	[171.71.163.34])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id iBE1Io6n018099;
	Mon, 13 Dec 2004 17:18:50 -0800 (PST)
Received: from cisco.com (dhcp-171-71-9-171.cisco.com [171.71.9.171])
	by mira-sjc5-a.cisco.com (MOS 3.4.5-GR) with ESMTP id AWL92920;
	Mon, 13 Dec 2004 17:12:44 -0800 (PST)
Message-ID: <41BE3F79.5050704@cisco.com>
Date: Mon, 13 Dec 2004 17:18:49 -0800
From: Steve Yeung <skyeung@cisco.com>
Organization: Cisco Systems
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.0.1) Gecko/20020823
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.2 (+)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 14 Dec 2004 10:00:58 -0500
Cc: Steve Yeung <skyeung@cisco.com>
Subject: [Megaco] dynamic tone string definition
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Dear Sir/Madam:

       I have a question about the H.248.6 specification.
In this dynamic tone package, it defines DefToneElement
as 'ToneName["," ToneDuration [ "," ToneAmplitude]]'.
With the syntax, how do I define the cadence for a tone?
For example, I want to define a tone with 2 frequencies playing
together for 500ms and then stop for 300ms and then play continously.
This tone I want it to play for 20 seconds.  How to use the syntax
to define this?  Thank you very much!

-- 
Steve Yeung
Software Engineer
408-853-4214


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Wed Dec 15 16:59:14 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21491
	for <megaco-archive@lists.ietf.org>; Wed, 15 Dec 2004 16:59:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CegvJ-00027i-5O; Wed, 15 Dec 2004 16:43:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cegh6-0001I7-MV
	for megaco@megatron.ietf.org; Wed, 15 Dec 2004 16:28:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16003
	for <megaco@ietf.org>; Wed, 15 Dec 2004 16:28:22 -0500 (EST)
Received: from europa.telenet-ops.be ([195.130.132.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CegpP-0003HG-2e
	for megaco@ietf.org; Wed, 15 Dec 2004 16:36:59 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by europa.telenet-ops.be (Postfix) with SMTP
	id D476519831F; Wed, 15 Dec 2004 22:28:17 +0100 (MET)
Received: from pas (D5778A38.kabel.telenet.be [213.119.138.56])
	by europa.telenet-ops.be (Postfix) with SMTP
	id 63164198010; Wed, 15 Dec 2004 22:28:17 +0100 (MET)
Message-ID: <001c01c4e2ed$0d131f20$b400a8c0@telenet.be>
From: "Pascal Lambers" <pascal.lambers@pandora.be>
To: "Kevin Boyle" <kboyle@nortelnetworks.com>, <megaco@ietf.org>
References: <B258A372CEA20246A363BB86753DB5360124B67C@zrtphxm2>
Subject: Re: [Megaco] does MGC have to answer?
Date: Wed, 15 Dec 2004 22:28:42 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 140baa79ca42e6b0e2b4504291346186
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Pascal Lambers <pascal.lambers@pandora.be>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1678278484=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1678278484==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0019_01C4E2F5.6E839AC0"

This is a multi-part message in MIME format.

------=_NextPart_000_0019_01C4E2F5.6E839AC0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I can more ore less agree with this point of view. On the other hand, =
what is the purpose of the error reply "402 - Unauthorized" (as it was =
defined in the past in RFC 3015 and now defined in H.248.8)?  Should an =
MGC never sent it to a gateway which is not registered?=20

Kind regards,
Pascal


  ----- Original Message -----=20
  From: Kevin Boyle=20
  To: Pascal Lambers ; megaco@ietf.org=20
  Sent: Wednesday, December 08, 2004 7:44 AM
  Subject: RE: [Megaco] does MGC have to answer?


  I would think that MGCs would ignore any messages from unregistered =
MGs that are not ServiceChanges.  Sending Pendings may only serve to =
extend a DoS attack.

  I do not believe that the use of Pending in this case is typical, =
either.  In fact, I would say that it is atypical, and in fact, wrong.

  Kevin


-------------------------------------------------------------------------=
-----
  From: megaco-bounces@ietf.org on behalf of Pascal Lambers
  Sent: Wed 12/8/2004 1:00 AM
  To: megaco@ietf.org
  Subject: Fw: [Megaco] does MGC have to answer?


  Hi,

  Is it mandatory for an MGC to answer to (eg Notify) messages from =
unregistered MGs? If the MGC receives such a message, typically, its =
underlying Megaco stack will send pending messages to the the MG anyway, =
even though the actual MGC does not answer to the message. In other =
words, is the following scenario a good one:

  MG                     MGC
  ------------Notify-------->
  <---------Pending-------- =20
  <---------Pending--------
  <---------Pending--------
                          (mgc stops sending
                            pending msgs)
  ...
  (retries)
  -----------Sc Restart----->



  Kind regards,
  Pascal


-------------------------------------------------------------------------=
-----


  _______________________________________________
  Megaco mailing list
  Megaco@ietf.org
  https://www1.ietf.org/mailman/listinfo/megaco

------=_NextPart_000_0019_01C4E2F5.6E839AC0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1479" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I can more ore less agree with this =
point of view.=20
On the other hand, what is the purpose of the error reply "402 - =
Unauthorized"=20
(as it was defined in the past in RFC 3015 and now defined in =
H.248.8)?&nbsp;=20
Should an MGC never sent it to a gateway which is not registered?=20
<BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Kind regards,</DIV></FONT>
<DIV>Pascal</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dkboyle@nortelnetworks.com=20
  href=3D"mailto:kboyle@nortelnetworks.com">Kevin Boyle</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dpascal.lambers@pandora.be=20
  href=3D"mailto:pascal.lambers@pandora.be">Pascal Lambers</A> ; <A=20
  title=3Dmegaco@ietf.org =
href=3D"mailto:megaco@ietf.org">megaco@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, December 08, =
2004 7:44=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [Megaco] does MGC =
have to=20
  answer?</DIV>
  <DIV><BR></DIV>
  <DIV id=3DidOWAReplyText91384 dir=3Dltr>
  <DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>I would =
think that MGCs=20
  would ignore any messages from unregistered MGs that are not=20
  ServiceChanges.&nbsp; Sending Pendings may only serve to extend a DoS=20
  attack.</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>I do not believe that the =
use of Pending=20
  in this case is typical, either.&nbsp; In fact, I would say that it is =

  atypical, and in fact, wrong.</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>Kevin</FONT></DIV></DIV>
  <DIV dir=3Dltr><BR>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> <A=20
  href=3D"mailto:megaco-bounces@ietf.org">megaco-bounces@ietf.org</A> on =
behalf of=20
  Pascal Lambers<BR><B>Sent:</B> Wed 12/8/2004 1:00 AM<BR><B>To:</B> <A=20
  href=3D"mailto:megaco@ietf.org">megaco@ietf.org</A><BR><B>Subject:</B> =
Fw:=20
  [Megaco] does MGC have to answer?<BR></FONT><BR></DIV>
  <DIV>
  <DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Is it mandatory for an MGC to answer =
to (eg=20
  Notify) messages from unregistered MGs? </FONT><FONT face=3DArial =
size=3D2>If the=20
  MGC receives such a message, typically, its underlying Megaco stack =
will send=20
  pending messages to the the MG anyway, even though the actual MGC does =
not=20
  answer to the message. </FONT><FONT face=3DArial size=3D2>In other =
words, is the=20
  following scenario a good one:</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>MG&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MGC</FONT=
></DIV>
  <DIV><FONT face=3DArial =
size=3D2>------------Notify--------&gt;</FONT></DIV>
  <DIV><FONT face=3DArial=20
  size=3D2>&lt;---------Pending--------&nbsp;&nbsp;</FONT></DIV>
  <DIV>
  <DIV><FONT face=3DArial =
size=3D2>&lt;---------Pending--------</FONT></DIV>
  <DIV>
  <DIV><FONT face=3DArial =
size=3D2>&lt;---------Pending--------</FONT></DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
  (mgc stops sending</FONT></DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  pending msgs)</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>...</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>(retries)</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>-----------Sc =
Restart-----&gt;</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></DIV></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Kind regards,</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Pascal</FONT></DIV></DIV>
  <P>
  <HR>

  <P></P>_______________________________________________<BR>Megaco =
mailing=20
  =
list<BR>Megaco@ietf.org<BR>https://www1.ietf.org/mailman/listinfo/megaco<=
BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0019_01C4E2F5.6E839AC0--



--===============1678278484==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco

--===============1678278484==--




From megaco-bounces@ietf.org  Wed Dec 15 23:13:52 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02284
	for <megaco-archive@lists.ietf.org>; Wed, 15 Dec 2004 23:13:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cemx1-00037Y-Td; Wed, 15 Dec 2004 23:09:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cemth-0002gQ-Ep
	for megaco@megatron.ietf.org; Wed, 15 Dec 2004 23:05:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01955
	for <megaco@ietf.org>; Wed, 15 Dec 2004 23:05:45 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cen1r-00055t-O4
	for megaco@ietf.org; Wed, 15 Dec 2004 23:14:26 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP id 69B933468FF
	for <megaco@ietf.org>; Wed, 15 Dec 2004 20:04:38 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 18513-199E5851;
	Wed, 15 Dec 2004 20:04:38 -0800
Received: from Mahesh (unknown [172.25.0.61])
	by smtp.ccpu.com (Postfix) with ESMTP id F09053467EF
	for <megaco@ietf.org>; Wed, 15 Dec 2004 20:04:36 -0800 (PST)
From: "Mahesh" <mahesh@ccpu.com>
To: <megaco@ietf.org>
Date: Thu, 16 Dec 2004 09:34:41 +0530
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTjJF5qtkAo0fmWToeKdOrOA/0Kgg==
Message-Id: <20041216040436.F09053467EF@smtp.ccpu.com>
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.29.0.5;
	VDF: 6.29.0.18; host: smtp)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Subject: [Megaco] ReserveGroup and Reserve value
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0598046512=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0598046512==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_008A_01C4E352.7A2FC170"

This is a multi-part message in MIME format.

------=_NextPart_000_008A_01C4E352.7A2FC170
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

HI ,

 

Could you please tell me the exact difference between Reserve Group and
Reserve Value .

 

With regards

Mahesh

 

 


------=_NextPart_000_008A_01C4E352.7A2FC170
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>HI ,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Could you please tell me the exact difference between =
Reserve
Group and Reserve Value .<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>With regards<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Mahesh<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_008A_01C4E352.7A2FC170--




--===============0598046512==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco

--===============0598046512==--





From megaco-bounces@ietf.org  Wed Dec 15 23:47:01 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04471
	for <megaco-archive@lists.ietf.org>; Wed, 15 Dec 2004 23:47:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CenVO-0000uy-Gu; Wed, 15 Dec 2004 23:44:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CenOa-00006O-L4
	for megaco@megatron.ietf.org; Wed, 15 Dec 2004 23:37:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03724
	for <megaco@ietf.org>; Wed, 15 Dec 2004 23:37:41 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CenWv-0005m8-LR
	for megaco@ietf.org; Wed, 15 Dec 2004 23:46:23 -0500
Received: from esealmw127.eemea.ericsson.se ([153.88.254.122])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBG4auh5017773; Thu, 16 Dec 2004 05:37:01 +0100 (MET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 16 Dec 2004 05:36:56 +0100
Received: from eaubrnt019.epa.ericsson.se ([146.11.9.165]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 16 Dec 2004 05:36:55 +0100
Received: from ericsson.com (EG2E500202DSEGL [146.11.22.59]) by
	eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id Y0DJ56CP; Thu, 16 Dec 2004 15:36:52 +1100
Message-ID: <41C11103.8040106@ericsson.com>
Date: Thu, 16 Dec 2004 15:37:23 +1100
X-Sybari-Trust: 922655a2 96d33411 55a1ffab 00000138
From: Christian Groves <christian.groves@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Mahesh <mahesh@ccpu.com>
Subject: Re: [Megaco] ReserveGroup and Reserve value
References: <20041216040436.F09053467EF@smtp.ccpu.com>
In-Reply-To: <20041216040436.F09053467EF@smtp.ccpu.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Dec 2004 04:36:55.0952 (UTC)
	FILETIME=[DF679100:01C4E328]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Reserve Group allows you to reserve sets of values where their could be an 
interdepency between them.

eg. Group1    AudioCodec=AMR
	      VideoCodec=H.263
     Group2    Codec=G711
   	      VideoCodec=H.264
Which basically says the MG can do AMR and H.263  or G711 and H.264.


Reserve Value allows to do a similar thing but theres no association between the 
parameters.
    	      Codec=AMR,G711
	      VideoCodec=H.263,H.264
So the MG could support AMR and H.264 or H.263.

Christian

Mahesh wrote:

> HI ,
> 
>  
> 
> Could you please tell me the exact difference between Reserve Group and
> Reserve Value .
> 
>  
> 
> With regards
> 
> Mahesh
> 
>  
> 
>  
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Thu Dec 16 00:10:01 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05763
	for <megaco-archive@lists.ietf.org>; Thu, 16 Dec 2004 00:10:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cenp9-0004mj-D8; Thu, 16 Dec 2004 00:05:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CenjW-0003T8-Fu
	for megaco@megatron.ietf.org; Wed, 15 Dec 2004 23:59:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05325
	for <megaco@ietf.org>; Wed, 15 Dec 2004 23:59:19 -0500 (EST)
From: bvswamy@hssworld.com
Received: from spark.hss.co.in ([203.200.71.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cenrr-0006P3-ES
	for megaco@ietf.org; Thu, 16 Dec 2004 00:08:01 -0500
Received: from spark.hss.co.in (localhost [127.0.0.1])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iBG4tYpV024527
	for <megaco@ietf.org>; Thu, 16 Dec 2004 10:25:35 +0530 (IST)
Received: from webmail.hss.hns.com (webmail.hss.hns.com [192.168.100.50])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iBG4tSI4024494;
	Thu, 16 Dec 2004 10:25:33 +0530 (IST)
In-Reply-To: <20041216040436.F09053467EF@smtp.ccpu.com>
Subject: Re: [Megaco] ReserveGroup and Reserve value
To: "Mahesh" <mahesh@ccpu.com>
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF42CEAA09.B3DB059C-ON65256F6C.0018E389-65256F6C.001B87B8@hssworld.com>
Date: Thu, 16 Dec 2004 10:23:07 +0530
X-MIMETrack: Serialize by Router on WebMail/HSS(Release 6.5.1|January 21,
	2004) at 12/16/2004 10:23:14 AM
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: 93e7fb8fef2e780414389440f367c879
Content-Transfer-Encoding: quoted-printable
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable






Hi
   The defination of ReserveGroup and Reserve Value is given in the
protocol section 7.1.8

   "If ReserveGroup is True, the MG reserves the resources required to
   support any of the requested property group alternatives that it can
   currently support.  If ReserveValue is True, the MG reserves the
   resources required to support any of the requested property value
   alternatives that it can currently support."

an example of this would be a case where CallAgent wishes to know if MG
supports both Audio and Fax capabilities, then Call Agent will
instructs MG to respond with the values of both its audio RTP/AVP
capabilities and its image/t38 capabilities. For this it sets the
"ReserveGroup=3DTrue" in the LocalControl descriptor to ask the MG to=
 reserve
resources for both audio and image media descriptors.
Similarly CallAgent will set "ReserveValue =3D True" to ask the MG to=
 reserve
resources for all the possible codecs(example below 18 and 0)
offered in the media descriptor

Add =3D $ {
Media {
Stream =3D 1 {
LocalControl { Mode =3D ReceiveOnly, ReserveGroup =3D True, ReserveValue =
=3D
True},
Local {
v=3D0
c=3DIN IP4 $
m=3Daudio $ RTP/AVP 18 0
v=3D0
c=3DIN IP4 $
m=3Dimage $ udptl t38
}} }


So if MG supports both Audio and Fax then in response to Add command it
will return both the media capabilities with resources reserved for all the
codecs.
For further details on incapability to support the resources refer the
guidelines given in the protocol section 7.1.8.

regards
B Venkat S.R Swamy
Senior Technical Leader
Hughes Software Systems
Phone:  +91-124-2455555 Extn 3620
Fax: +91-124-2455345
web: www.hssworld.com




                                                                          =
=0D
             "Mahesh"                                                     =
=0D
             <mahesh@ccpu.com>                                            =
=0D
             Sent by:                                                   To=
=0D
             megaco-bounces@ie         <megaco@ietf.org>                  =
=0D
             tf.org                                                     cc=
=0D
                                                                          =
=0D
                                                                   Subject=
=0D
             12/16/2004 09:34          [Megaco] ReserveGroup and Reserve  =
=0D
             AM                        value                              =
=0D
                                                                          =
=0D
                                                                          =
=0D
                                                                          =
=0D
                                                                          =
=0D
                                                                          =
=0D
                                                                          =
=0D






HI ,



Could you please tell me the exact difference between Reserve Group and
Reserve Value .



With regards

Mahesh




_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco



***********************  HSS-Unclassified   ***********************


"Please note:  The email domain of Hughes Software Systems Ltd. has
been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems
Limited (HSS) and is intended solely for the use of the  individual
to whom it is addressed. It may contain  privileged or confidential
information and  should not be  circulated or  used for any purpose
other than for what  it is intended.  If  you have   received  this
message in  error, please notify the originator immediately. If you
are   not the  intended recipient, you are  notified  that  you are
strictly  prohibited  from  using, copying, altering, or disclosing
the contents of this message.  HSS  accepts no  responsibility  for
loss or damage arising from the use of  the information transmitted
by this email including damage from virus."

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Thu Dec 16 09:20:12 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25939
	for <megaco-archive@lists.ietf.org>; Thu, 16 Dec 2004 09:20:12 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CewON-0004o3-8V; Thu, 16 Dec 2004 09:14:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CewJP-0003QU-5E
	for megaco@megatron.ietf.org; Thu, 16 Dec 2004 09:08:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24692
	for <megaco@ietf.org>; Thu, 16 Dec 2004 09:08:57 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CewRg-0001pE-HX
	for megaco@ietf.org; Thu, 16 Dec 2004 09:17:43 -0500
Received: from wink.ho.lucent.com (h135-112-126-3.lucent.com [135.112.126.3])
	by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id iBGE8FBX019563
	for <megaco@ietf.org>; Thu, 16 Dec 2004 08:08:16 -0600 (CST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id JAA01729; Thu, 16 Dec 2004 09:08:13 -0500 (EST)
Received: from [192.11.62.118] by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id JAA01725; Thu, 16 Dec 2004 09:08:13 -0500 (EST)
Message-ID: <41C196CE.5040500@lucent.com>
Date: Thu, 16 Dec 2004 09:08:14 -0500
From: Richard Sun <xsun@lucent.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit
Subject: [Megaco] how codec negotiation is triggered by MGC?
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hi, Can anyone pelase clarify the standard
for MGC to trigger a codec negotiation in MG
(i.e, MG should provide a list of codecs
it supports)?

One way I can think of is an empty "Local{}"
without SDP, such as:
Transaction = 299012 {
  Context = $ {
    Add = aaln/1 {
      Media { Stream = 1 {
        LocalControl {Mode = SendReceive}
    }}},
    Add = $ {
      Media {Stream = 1 {
        LocalControl {Mode=ReceiveOnly},
        Local {}
}}}}}

The question is: is this legal? Should MG reject
the message with some kind of error such as "SDP missing",
or MG is suppose to fill up the SDP section in response?
What if the "Local{}" does not present at all?

The other way is something like this:
Transaction = 299012 {
  Context = $ {
    Add = aaln/1 {
      Media { Stream = 1 {
        LocalControl {Mode = SendReceive}
    }}},
    Add = $ {
      Media {Stream = 1 {
        LocalControl {Mode=ReceiveOnly},
        Local {
v=0
o=$ $ $ IN IP4 $
s=$
c=IN IP4 $
t=$ $
m=audio $ RTP/AVP -
a=ptime:20
}}}}}}
With "-" in "m=audio $ RTP/AVP -", should MG
fill up the list of codecs?
Or should it be something like
"m=audio $ RTP/AVP $"?

Thanks for any information.
-Richard

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Thu Dec 16 18:40:08 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28619
	for <megaco-archive@lists.ietf.org>; Thu, 16 Dec 2004 18:40:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cf599-0006px-J6; Thu, 16 Dec 2004 18:34:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cf53R-0005PM-2H
	for megaco@megatron.ietf.org; Thu, 16 Dec 2004 18:29:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27536
	for <megaco@ietf.org>; Thu, 16 Dec 2004 18:29:01 -0500 (EST)
Received: from mail.sonusnet.com ([208.45.178.33] helo=revere.sonusnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cf5Bx-0005um-7M
	for megaco@ietf.org; Thu, 16 Dec 2004 18:37:53 -0500
Received: from sonusms1.sonusnet.com (sonusms1 [10.128.32.93])
	by revere.sonusnet.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	iBGNSRKX020202
	for <megaco@ietf.org>; Thu, 16 Dec 2004 18:28:27 -0500 (EST)
Received: from sonusmail03.sonusnet.com (unverified) by sonusms1.sonusnet.com
	(Content Technologies SMTPRS 4.3.12) with ESMTP id
	<T6de98c151a0a80205d3a4@sonusms1.sonusnet.com>; 
	Thu, 16 Dec 2004 18:28:27 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 16 Dec 2004 18:28:26 -0500
Message-ID: <A3863F3136CBC546A40A61BA9CBA9D9301050462@sonusmail03.sonusnet.com>
Thread-Topic: [Megaco] signal directionality
Thread-Index: AcTdsQeJQs2YFehUSJmgkBI/vNVRNgGFRmew
From: "Kamitses, Jerry" <jkamitses@sonusnet.com>
To: <megaco@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Content-Transfer-Encoding: quoted-printable
Cc: Christian Groves <christian.groves@ericsson.com>,
        Kevin Boyle <kboyle@nortelnetworks.com>
Subject: [Megaco] Question on the semantics of Subtract command;
	Question regarding Digitmap Completion Events 
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Reference RFC 3525    Gateway Control Protocol Version 1


Question 1) I would appreciate some clarification regarding precise =
effect=20
of the Subtract command on physical terminations.  In Section  7.2.3 =
Subtract,=20
the final paragraph states:

   When a provisioned Termination is Subtracted from a Context, its
   property values shall revert to:
   -  the default value, if specified for the property and not
      overridden by provisioning;
   -  otherwise, the provisioned value.

1a) I assume "provisioned Termination" in the 1st line should read =
"physical Termination"
since the concept of "provisioned Termination" does not appear elsewhere =
in the RFC.
Is this correct, or is there some other meaning for "provisioned =
Termination" that is=20
intended here?

(1b) It is not clear to me from the context exactly what is meant by =
"property"? Is=20
"property" used to refer strictly to the formal concept of termination =
properties,=20
that is,  parameters that are assigned values via the=20
        propertyParm         =3D pkgdName parmValue
productions in the formal syntax using the localControlDescriptor and/or =
terminationStateDescriptor. =20

Or is "property" here used in some more generic sense to possibly refer =
to other=20
aspects of the termination state?

For example, if a subtract is sent to a termination with a currently =
active signal then=20
does the signal stop as a side effect of receiving the subtract, or =
should the signal=20
be unaffected by the subtract.?

Question 2) Digitmap Completion Events=20

2a)  Section 7.1.9 Events Descriptor contains the text:
    The default streamID is 0, indicating that the event to be
    detected is not related to a particular media stream.

We have assumed that streamID 0 also could mean the event is related to =
all=20
media streams. That is, for those events which apply to media streams, =
then=20
when there are one or more streams on the context, and the MGC wants to =
enable=20
an event concurrently on all streams, must the MGC send one instance of =
the=20
event with streamID 0, or must the MGC send multiple instances each a =
separate=20
non-0 streamID?

2b) This section also contains the text:=20
  If a digit map completion event is present or implied in the
   EventsDescriptor, the EventDM parameter is used to carry either the
   name or the value of the associated digit map. =20

Could you please explain "implied" digitmap completion event and provide =
a=20
pointer to RFC text that discusses this concept?=20

2c) Regarding the statement in section 7.1.14.6 DigitMap Activation
   A digit map completion event that does not contain an eventDM field
   in its requested actions field is considered an error. =20
We have encountered instances of the following message syntax

    ... Events =3D 1 { dd/ce }, DigitMap =3D { (0 | xxxxxxxx|x.#) } ...

Since the digitMapDescriptor in the above example omits the =
digitMapName,=20
then clearly it has no possible use except in the context of the =
associated=20
completion event.  Perhaps  this could be an instance of an "implied" =
digitMapDescriptor=20
for the completion event,  and be allowed even though it seems to =
technically violate=20
the correct syntax for the ce event, which should be=20

    ... Events =3D 1 { dd/ce{ DigitMap =3D { (0 | xxxxxxxx|x.#) } }  }, =
...

Is the 1st Events example above allowable ?


Thanks.



_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Thu Dec 16 20:42:55 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08229
	for <megaco-archive@lists.ietf.org>; Thu, 16 Dec 2004 20:42:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cf77U-00029Z-Cg; Thu, 16 Dec 2004 20:41:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cf70P-0001Te-Ob
	for megaco@megatron.ietf.org; Thu, 16 Dec 2004 20:34:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07467
	for <megaco@ietf.org>; Thu, 16 Dec 2004 20:34:03 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cf78w-00017Y-5i
	for megaco@ietf.org; Thu, 16 Dec 2004 20:42:55 -0500
Received: from zcard303.ca.nortel.com (zcard303.ca.nortel.com [47.129.242.59])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iBH1XTV26051; Thu, 16 Dec 2004 20:33:29 -0500 (EST)
Received: from [47.130.16.167] (acart05a.ca.nortel.com [47.130.16.167]) by
	zcard303.ca.nortel.com with SMTP (Microsoft Exchange Internet
	Mail Service Version 5.5.2653.13)
	id W14FV1MK; Thu, 16 Dec 2004 20:33:28 -0500
Message-ID: <41C2374E.7000603@nortelnetworks.com>
Date: Thu, 16 Dec 2004 20:33:02 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kamitses, Jerry" <jkamitses@sonusnet.com>
Subject: Re: [Megaco] Question on the semantics of Subtract command; Question
	regarding Digitmap Completion Events
References: <A3863F3136CBC546A40A61BA9CBA9D9301050462@sonusmail03.sonusnet.com>
In-Reply-To: <A3863F3136CBC546A40A61BA9CBA9D9301050462@sonusmail03.sonusnet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Content-Transfer-Encoding: 7bit
Cc: megaco@ietf.org, Kevin Boyle <kboyle@nortelnetworks.com>,
        Christian Groves <christian.groves@ericsson.com>
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Answers below, marked by [PTT].

Kamitses, Jerry wrote:
> Reference RFC 3525    Gateway Control Protocol Version 1
> 
> 
> Question 1) I would appreciate some clarification regarding precise effect 
> of the Subtract command on physical terminations.  In Section  7.2.3 Subtract, 
> the final paragraph states:
> 
>    When a provisioned Termination is Subtracted from a Context, its
>    property values shall revert to:
>    -  the default value, if specified for the property and not
>       overridden by provisioning;
>    -  otherwise, the provisioned value.
> 
> 1a) I assume "provisioned Termination" in the 1st line should read "physical Termination"
> since the concept of "provisioned Termination" does not appear elsewhere in the RFC.
> Is this correct, or is there some other meaning for "provisioned Termination" that is 
> intended here?
> 
[PTT] I may have introduced this phrase once upon a time.  It's probably a red 
herring, but I have always believed that one could provision terminations that 
would otherwise be ephemerals -- PVCs in effect.  That's why the term, but I 
expect in normal practice this is identical with "physical termination".

> (1b) It is not clear to me from the context exactly what is meant by "property"? Is 
> "property" used to refer strictly to the formal concept of termination properties, 
> that is,  parameters that are assigned values via the 
>         propertyParm         = pkgdName parmValue
> productions in the formal syntax using the localControlDescriptor and/or terminationStateDescriptor.  
> 
> Or is "property" here used in some more generic sense to possibly refer to other 
> aspects of the termination state?
> 
> For example, if a subtract is sent to a termination with a currently active signal then 
> does the signal stop as a side effect of receiving the subtract, or should the signal 
> be unaffected by the subtract.?

[PTT] "Property" here is intended in the generic sense that all descriptor values 
are properties of the termination.  Thus a Subtract definitely ends an on-going 
signal, and may possibly install an alternative if a non-empty Signals descriptor 
was provisioned as the default for the termination.
> 
> Question 2) Digitmap Completion Events 
> 
> 2a)  Section 7.1.9 Events Descriptor contains the text:
>     The default streamID is 0, indicating that the event to be
>     detected is not related to a particular media stream.
> 
> We have assumed that streamID 0 also could mean the event is related to all 
> media streams. That is, for those events which apply to media streams, then 
> when there are one or more streams on the context, and the MGC wants to enable 
> an event concurrently on all streams, must the MGC send one instance of the 
> event with streamID 0, or must the MGC send multiple instances each a separate 
> non-0 streamID?
>
[PTT] One instance with streamID 0 will pick up digitmap completion events from 
all active streams.  If it is important to relate the event to the originating 
stream, you might want to enable the events against the individual streams.

> 2b) This section also contains the text: 
>   If a digit map completion event is present or implied in the
>    EventsDescriptor, the EventDM parameter is used to carry either the
>    name or the value of the associated digit map.  
> 
> Could you please explain "implied" digitmap completion event and provide a 
> pointer to RFC text that discusses this concept? 

[PTT] I believe this was meant to refer to the use of the "ALL" wildcard as 
described in the preceding paragraph.  I would have to look at the Megaco 
correspondance between February and May of 2000 to verify that.  (The text first 
appears in the RFC 2886 corrigendum to RFC 2885.)
> 
> 2c) Regarding the statement in section 7.1.14.6 DigitMap Activation
>    A digit map completion event that does not contain an eventDM field
>    in its requested actions field is considered an error.  
> We have encountered instances of the following message syntax
> 
>     ... Events = 1 { dd/ce }, DigitMap = { (0 | xxxxxxxx|x.#) } ...
> 
> Since the digitMapDescriptor in the above example omits the digitMapName, 
> then clearly it has no possible use except in the context of the associated 
> completion event.  Perhaps  this could be an instance of an "implied" digitMapDescriptor 
> for the completion event,  and be allowed even though it seems to technically violate 
> the correct syntax for the ce event, which should be 
> 
>     ... Events = 1 { dd/ce{ DigitMap = { (0 | xxxxxxxx|x.#) } }  }, ...
> 
> Is the 1st Events example above allowable ?
> 
[PTT] I think I'll leave this one for Kevin or Christian to comment on.
> 
> Thanks.
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 
> 

-- 
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.com

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Fri Dec 17 10:44:03 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29259
	for <megaco-archive@lists.ietf.org>; Fri, 17 Dec 2004 10:44:03 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfK8y-0006NZ-Hf; Fri, 17 Dec 2004 10:35:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfJwu-0002I7-9W
	for megaco@megatron.ietf.org; Fri, 17 Dec 2004 10:23:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27298
	for <megaco@ietf.org>; Fri, 17 Dec 2004 10:23:17 -0500 (EST)
Received: from mail.sonusnet.com ([208.45.178.33] helo=revere.sonusnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfK5X-00087G-IM
	for megaco@ietf.org; Fri, 17 Dec 2004 10:32:16 -0500
Received: from sonusms1.sonusnet.com (sonusms1 [10.128.32.93])
	by revere.sonusnet.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	iBHFMlKX029458
	for <megaco@ietf.org>; Fri, 17 Dec 2004 10:22:47 -0500 (EST)
Received: from sonusmail03.sonusnet.com (unverified) by sonusms1.sonusnet.com
	(Content Technologies SMTPRS 4.3.12) with ESMTP id
	<T6decf5cced0a80205d3a4@sonusms1.sonusnet.com>; 
	Fri, 17 Dec 2004 10:22:47 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Megaco] Question on the semantics of Subtract command
Date: Fri, 17 Dec 2004 10:22:46 -0500
Message-ID: <A3863F3136CBC546A40A61BA9CBA9D930119C222@sonusmail03.sonusnet.com>
Thread-Topic: [Megaco] Question on the semantics of Subtract command;
	Question regarding Digitmap Completion Events
Thread-Index: AcTj2Gu9Ta0JgOhnSjSlh+rX99MKFQAWnjMQ
From: "Kamitses, Jerry" <jkamitses@sonusnet.com>
To: "Tom Taylor" <taylor@nortelnetworks.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fcb459c204557d9509ce9c1b55d771f1
Content-Transfer-Encoding: quoted-printable
Cc: megaco@ietf.org, Kevin Boyle <kboyle@nortelnetworks.com>,
        Christian Groves <christian.groves@ericsson.com>
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Tom,
Thanks for such a prompt reply.=20

Regarding operation of the Subtract command, I am a little surprised =
that=20
this important side effect of Subtract (which I learned of thru the =
grapevine)=20
seems to be nowhere expressly mentioned in the RFC? The section that =
specifies=20
signals and events doesn't mention it, and neither does the section on =
subtract,=20
other than the reference to property that I cited below, where =
"property" seems=20
to have acquired additional meaning. Elsewhere the RFC seems to view =
"properties"=20
and "events and signals" as being distinct? For example, Section 6.2.1 =
Termination=20
dynamics, contains the text:
   The Termination properties, and events and signals are described in
   the ensuing subclauses. =20
This seems to say that "events and signals" are distinct from =
"properties"?
Likewise  6.2.3 Packages includes the text:
   Properties, Events, Signals and Statistics defined in Packages, as
   well as parameters to them, are referenced by identifiers (Ids).

Again suggesting that "Properties" and "Events, Signals" are different=20
animals? Same again in section 6.2.4 Termination properties and=20
descriptors:
	Terminations have properties. =20
	The properties have unique PropertyIDs.=20

This section (6.2.4) also addresses the effect of the Subtract command=20
when it describes what occurs when a termination is returned to the=20
NULL context.
	If not provisioned otherwise, the properties in all descriptors=20
	except TerminationState and LocalControl default to empty/"no value"=20
	when a Termination is first created or returned to the null Context. =20

All use of the expression "property" in this section are clearly =
referring=20
to Property type properties and not signals/events, for example:=20
	... properties are referred to by a name consisting of the PackageName=20
	and a PropertyId. =20
	... Properties may be read-only or read/write. =20

In addition, the RFC does take pains to specify that the Subtract =
command=20
may not include any eventsDescriptor or signalsDescriptor. One seemingly =

straightforward inference of this restriction regarding Subtract is that =

the Subtract command is not intended to have any effect on the =
signal/event=20
state of a termination (except for the obvious case that the subtract=20
eliminates an ephemeral termination). The statement in section (6.2.4)=20
	In general, if a Descriptor is completely omitted from one of the=20
	aforementioned Commands, the properties in that Descriptor retain=20
	their prior values for the Termination(s) upon which the Command acts.  =

contributes to the conclusion that Subtract should have no effect on=20
the eventsDescriptor or the signalsDescriptor (since these descriptors =
will=20
always be completely omitted in the Subtract).  The key to this =
confusion=20
is the vague use of "aforementioned Commands" instead precisely =
specifying=20
the commands which apply.

If the MGC's intention is to stop a signal as part of a Subtract then=20
a Modify with empty signalsDescriptor ahead of the Subtract seems like=20
a pretty straightforward way to accomplish this.

Furthermore, if a signal is active on a termination in the null context, =
and=20
an Add command that omits any eventsDescriptor or signalsDescriptor is =
sent=20
to that termination, then does the protocol require the signal to be =
stopped=20
in this case too?  If not (which I believe is the case?), then we seem =
to=20
have this strange asymmetry regarding events/signals:  the event/signal=20
can persist unaffected when the termination is added to a context but =
not=20
survive the termination being removed. I don't quite understand the=20
rationale behind this?

In light of the above I am a bit puzzled as to the definitive source of=20
"a Subtract definitely ends an on-going signal"?  Apparently the source =
is=20
not the actual RFC3525. Could it be in one of the implementer's guides,=20
or some other email thread?

Lastly, regarding your comment:
  [subtract side effect] may possibly install an alternative if a=20
  non-empty Signals descriptor was provisioned as the default for=20
  the termination.

I am assuming the source for this in the RFC is again the text:
    When a provisioned Termination is Subtracted from a Context, its
    property values shall revert to:
    -  the default value, if specified for the property and not
       overridden by provisioning;
    -  otherwise, the provisioned value.

In this case I am somewhat unclear as to exactly how this works for =
signals?
If there is such a default signal provisioned for a termination then =
exactly=20
when is it re-activated? Only as a side effect of the Subtract command, =
or=20
might this also apply whenever the termination receives an empty=20
signalsDescriptor?=20

I also have a question regarding the effect of Subtract on actual =
property=20
type "properties" for a termination. Property type properties can be =
altered=20
via MGC commands that contain instances of the  propertyParm, present in =
the=20
mediaDescriptor subdescriptors localControlDescriptor or =
terminationStateDescriptor.=20

Instances of these descriptors may be present in Add and Modify type =
requests=20
sent to a termination in either the NULL or a non-NULL context.=20

If the MGC changes the value of a property type property of a =
termination while=20
in the NULL context then according to the above RFC text this change =
will persist=20
at most until the next Subtract. Correct?

Is there is no means available in the protocol for the MGC to make a =
more permanent=20
change to a termination property type property that will persist across =
subsequent=20
add/subtract commands? Is there no distinction between property type =
properties that=20
are set when the termination is in a non-NULL context (which could be =
viewed as part=20
of an active call) vs. those set while the termination is in the NULL =
context=20
(which could be viewed more as semi-permanent)?

Also, while a termination is in a non-NULL context is it still valid for =
the MGC to=20
send a modify to the NULL context for the termination? This isn't =
discussed in=20
the section on Modify and I couldn't seem to find any other reference to =
this.
If the NULL context is still a valid context for commands while the =
termination=20
is in a non-NULL context, and the MGC sets a property type property =
value, or=20
signals and/or events, for the NULL context at that termination, then do =
these=20
changes apply to the termination in the non-NULL context as well? =20

Thanks again.

Happy Holidays



-----Original Message-----
From: Tom Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, December 16, 2004 8:33 PM
To: Kamitses, Jerry
Cc: megaco@ietf.org; Christian Groves; Kevin Boyle
Subject: Re: [Megaco] Question on the semantics of Subtract command;
Question regarding Digitmap Completion Events


Answers below, marked by [PTT].

Kamitses, Jerry wrote:
> Reference RFC 3525    Gateway Control Protocol Version 1
>=20
>=20
> Question 1) I would appreciate some clarification regarding precise =
effect=20
> of the Subtract command on physical terminations.  In Section  7.2.3 =
Subtract,=20
> the final paragraph states:
>=20
>    When a provisioned Termination is Subtracted from a Context, its
>    property values shall revert to:
>    -  the default value, if specified for the property and not
>       overridden by provisioning;
>    -  otherwise, the provisioned value.
>=20
> 1a) I assume "provisioned Termination" in the 1st line should read =
"physical Termination"
> since the concept of "provisioned Termination" does not appear =
elsewhere in the RFC.
> Is this correct, or is there some other meaning for "provisioned =
Termination" that is=20
> intended here?
>=20
[PTT] I may have introduced this phrase once upon a time.  It's probably =
a red=20
herring, but I have always believed that one could provision =
terminations that=20
would otherwise be ephemerals -- PVCs in effect.  That's why the term, =
but I=20
expect in normal practice this is identical with "physical termination".

> (1b) It is not clear to me from the context exactly what is meant by =
"property"? Is=20
> "property" used to refer strictly to the formal concept of termination =
properties,=20
> that is,  parameters that are assigned values via the=20
>         propertyParm         =3D pkgdName parmValue
> productions in the formal syntax using the localControlDescriptor =
and/or terminationStateDescriptor. =20
>=20
> Or is "property" here used in some more generic sense to possibly =
refer to other=20
> aspects of the termination state?
>=20
> For example, if a subtract is sent to a termination with a currently =
active signal then=20
> does the signal stop as a side effect of receiving the subtract, or =
should the signal=20
> be unaffected by the subtract.?

[PTT] "Property" here is intended in the generic sense that all =
descriptor values=20
are properties of the termination.  Thus a Subtract definitely ends an =
on-going=20
signal, and may possibly install an alternative if a non-empty Signals =
descriptor=20
was provisioned as the default for the termination.
>=20
> Question 2) Digitmap Completion Events=20
>=20
> 2a)  Section 7.1.9 Events Descriptor contains the text:
>     The default streamID is 0, indicating that the event to be
>     detected is not related to a particular media stream.
>=20
> We have assumed that streamID 0 also could mean the event is related =
to all=20
> media streams. That is, for those events which apply to media streams, =
then=20
> when there are one or more streams on the context, and the MGC wants =
to enable=20
> an event concurrently on all streams, must the MGC send one instance =
of the=20
> event with streamID 0, or must the MGC send multiple instances each a =
separate=20
> non-0 streamID?
>
[PTT] One instance with streamID 0 will pick up digitmap completion =
events from=20
all active streams.  If it is important to relate the event to the =
originating=20
stream, you might want to enable the events against the individual =
streams.

> 2b) This section also contains the text:=20
>   If a digit map completion event is present or implied in the
>    EventsDescriptor, the EventDM parameter is used to carry either the
>    name or the value of the associated digit map. =20
>=20
> Could you please explain "implied" digitmap completion event and =
provide a=20
> pointer to RFC text that discusses this concept?=20

[PTT] I believe this was meant to refer to the use of the "ALL" wildcard =
as=20
described in the preceding paragraph.  I would have to look at the =
Megaco=20
correspondance between February and May of 2000 to verify that.  (The =
text first=20
appears in the RFC 2886 corrigendum to RFC 2885.)
>=20
> 2c) Regarding the statement in section 7.1.14.6 DigitMap Activation
>    A digit map completion event that does not contain an eventDM field
>    in its requested actions field is considered an error. =20
> We have encountered instances of the following message syntax
>=20
>     ... Events =3D 1 { dd/ce }, DigitMap =3D { (0 | xxxxxxxx|x.#) } =
...
>=20
> Since the digitMapDescriptor in the above example omits the =
digitMapName,=20
> then clearly it has no possible use except in the context of the =
associated=20
> completion event.  Perhaps  this could be an instance of an "implied" =
digitMapDescriptor=20
> for the completion event,  and be allowed even though it seems to =
technically violate=20
> the correct syntax for the ce event, which should be=20
>=20
>     ... Events =3D 1 { dd/ce{ DigitMap =3D { (0 | xxxxxxxx|x.#) } }  =
}, ...
>=20
> Is the 1st Events example above allowable ?
>=20
[PTT] I think I'll leave this one for Kevin or Christian to comment on.
>=20
> Thanks.
>=20
>=20
>=20
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
>=20
>=20

--=20
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.com

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Fri Dec 17 10:57:57 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01852
	for <megaco-archive@lists.ietf.org>; Fri, 17 Dec 2004 10:57:57 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfKIG-0000W5-VP; Fri, 17 Dec 2004 10:45:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfF9A-0006Ro-8d
	for megaco@megatron.ietf.org; Fri, 17 Dec 2004 05:15:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00963
	for <megaco@ietf.org>; Fri, 17 Dec 2004 05:15:38 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfFHl-0007KS-9k
	for megaco@ietf.org; Fri, 17 Dec 2004 05:24:34 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBHAFRO6021546 for <megaco@ietf.org>; Fri, 17 Dec 2004 11:15:27 +0100
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 17 Dec 2004 11:15:27 +0100
Received: from ESEALNT744.al.sw.ericsson.se ([153.88.251.4]) by
	esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id ZAPB6YPF; Fri, 17 Dec 2004 11:15:27 +0100
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service
	(5.5.2653.19) id <X15H3FA2>; Fri, 17 Dec 2004 11:15:26 +0100
Message-ID: <FBB5E93ACF0CD51188D20002A55CBC98083E1D16@edeacnt101.eed.ericsson.se>
X-Sybari-Trust: 2df194ea 96d33411 47145045 00000138
From: "Marcello Pantaleo (AC/EDD)" <marcello.pantaleo@ericsson.com>
To: "'Richard Sun'" <xsun@lucent.com>
Subject: RE: [Megaco] how codec negotiation is triggered by MGC?
Date: Fri, 17 Dec 2004 11:15:23 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 17 Dec 2004 10:15:27.0074 (UTC)
	FILETIME=[54309420:01C4E421]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
X-Mailman-Approved-At: Fri, 17 Dec 2004 10:45:20 -0500
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

Hi,

MGC can use audit capabilities to get the list of codecs supported by a MG. Alternatively a MGC can be provisioned with MG capabilities.

MGC wouldn't use Add to know MG capabilities (e.g. supported codecs).

If MGC sends an Add command with an empty local desciptor, this is a request to release any resources previously reserved for the media flow received, that means nothing given that MGC is now creating the termination.
If local descriptor is unspecified (i.e. absent), MG considers this as missing mandatory parameter. MG uses whatever previously specified. 

If MGC sends "m=audio $ RTP/AVP $" it requests MG to choose one of the supported codecs, so you don't get the list.

I don't think you can use * wildcard in the "m=".

Regards,
Marcello 

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]On Behalf
Of Richard Sun
Sent: Thursday, December 16, 2004 3:08 PM
To: megaco@ietf.org
Subject: [Megaco] how codec negotiation is triggered by MGC?


Hi, Can anyone pelase clarify the standard
for MGC to trigger a codec negotiation in MG
(i.e, MG should provide a list of codecs
it supports)?

One way I can think of is an empty "Local{}"
without SDP, such as:
Transaction = 299012 {
  Context = $ {
    Add = aaln/1 {
      Media { Stream = 1 {
        LocalControl {Mode = SendReceive}
    }}},
    Add = $ {
      Media {Stream = 1 {
        LocalControl {Mode=ReceiveOnly},
        Local {}
}}}}}

The question is: is this legal? Should MG reject
the message with some kind of error such as "SDP missing",
or MG is suppose to fill up the SDP section in response?
What if the "Local{}" does not present at all?

The other way is something like this:
Transaction = 299012 {
  Context = $ {
    Add = aaln/1 {
      Media { Stream = 1 {
        LocalControl {Mode = SendReceive}
    }}},
    Add = $ {
      Media {Stream = 1 {
        LocalControl {Mode=ReceiveOnly},
        Local {
v=0
o=$ $ $ IN IP4 $
s=$
c=IN IP4 $
t=$ $
m=audio $ RTP/AVP -
a=ptime:20
}}}}}}
With "-" in "m=audio $ RTP/AVP -", should MG
fill up the list of codecs?
Or should it be something like
"m=audio $ RTP/AVP $"?

Thanks for any information.
-Richard

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Fri Dec 17 12:56:21 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15552
	for <megaco-archive@lists.ietf.org>; Fri, 17 Dec 2004 12:56:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfMBL-0002JO-1W; Fri, 17 Dec 2004 12:46:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfLuv-0006IU-JF
	for megaco@megatron.ietf.org; Fri, 17 Dec 2004 12:29:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12885
	for <megaco@ietf.org>; Fri, 17 Dec 2004 12:29:23 -0500 (EST)
Received: from ihemail2.lucent.com ([192.11.222.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfM3R-0004kI-J7
	for megaco@ietf.org; Fri, 17 Dec 2004 12:38:24 -0500
Received: from wink.ho.lucent.com (h135-112-126-3.lucent.com [135.112.126.3])
	by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id iBHHSf18029425
	for <megaco@ietf.org>; Fri, 17 Dec 2004 11:28:41 -0600 (CST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id MAA07291; Fri, 17 Dec 2004 12:28:39 -0500 (EST)
Received: from [135.112.108.30] by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id MAA07282; Fri, 17 Dec 2004 12:28:38 -0500 (EST)
Message-ID: <41C319BA.9050405@lucent.com>
Date: Fri, 17 Dec 2004 12:39:06 -0500
From: Richard Sun <xsun@lucent.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Marcello Pantaleo (AC/EDD)" <marcello.pantaleo@ericsson.com>
Original-CC: megaco@ietf.org
Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
References: <FBB5E93ACF0CD51188D20002A55CBC98083E1D16@edeacnt101.eed.ericsson.se>
In-Reply-To: <FBB5E93ACF0CD51188D20002A55CBC98083E1D16@edeacnt101.eed.ericsson.se>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Content-Transfer-Encoding: 7bit
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Marcello,
Thanks for your helpfull information.

Now assume that MGC audits MG and learns
that MG supports "PCMU" *and* "telephone-event".
If "m=audio $ RTP/AVP $" means that
MG to choose *one* codec, then
what is the syntax for MGC to instruct MG
"use PCMU, *and* choose a payload number for
telephone-event"?

-Richard

Marcello Pantaleo (AC/EDD) wrote:

> Hi,
> 
> MGC can use audit capabilities to get the list of codecs supported by a MG. Alternatively a MGC can be provisioned with MG capabilities.
> 
> MGC wouldn't use Add to know MG capabilities (e.g. supported codecs).
> 
> If MGC sends an Add command with an empty local desciptor, this is a request to release any resources previously reserved for the media flow received, that means nothing given that MGC is now creating the termination.
> If local descriptor is unspecified (i.e. absent), MG considers this as missing mandatory parameter. MG uses whatever previously specified. 
> 
> If MGC sends "m=audio $ RTP/AVP $" it requests MG to choose one of the supported codecs, so you don't get the list.
> 
> I don't think you can use * wildcard in the "m=".
> 
> Regards,
> Marcello 
> 
> -----Original Message-----
> From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]On Behalf
> Of Richard Sun
> Sent: Thursday, December 16, 2004 3:08 PM
> To: megaco@ietf.org
> Subject: [Megaco] how codec negotiation is triggered by MGC?
> 
> 
> Hi, Can anyone pelase clarify the standard
> for MGC to trigger a codec negotiation in MG
> (i.e, MG should provide a list of codecs
> it supports)?
> 
> One way I can think of is an empty "Local{}"
> without SDP, such as:
> Transaction = 299012 {
>   Context = $ {
>     Add = aaln/1 {
>       Media { Stream = 1 {
>         LocalControl {Mode = SendReceive}
>     }}},
>     Add = $ {
>       Media {Stream = 1 {
>         LocalControl {Mode=ReceiveOnly},
>         Local {}
> }}}}}
> 
> The question is: is this legal? Should MG reject
> the message with some kind of error such as "SDP missing",
> or MG is suppose to fill up the SDP section in response?
> What if the "Local{}" does not present at all?
> 
> The other way is something like this:
> Transaction = 299012 {
>   Context = $ {
>     Add = aaln/1 {
>       Media { Stream = 1 {
>         LocalControl {Mode = SendReceive}
>     }}},
>     Add = $ {
>       Media {Stream = 1 {
>         LocalControl {Mode=ReceiveOnly},
>         Local {
> v=0
> o=$ $ $ IN IP4 $
> s=$
> c=IN IP4 $
> t=$ $
> m=audio $ RTP/AVP -
> a=ptime:20
> }}}}}}
> With "-" in "m=audio $ RTP/AVP -", should MG
> fill up the list of codecs?
> Or should it be something like
> "m=audio $ RTP/AVP $"?
> 
> Thanks for any information.
> -Richard
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Fri Dec 17 13:45:18 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19166
	for <megaco-archive@lists.ietf.org>; Fri, 17 Dec 2004 13:45:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfMzc-00075s-DF; Fri, 17 Dec 2004 13:38:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfMtC-0005Vb-8U
	for megaco@megatron.ietf.org; Fri, 17 Dec 2004 13:31:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18185
	for <megaco@ietf.org>; Fri, 17 Dec 2004 13:31:39 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfN1p-0006kM-RM
	for megaco@ietf.org; Fri, 17 Dec 2004 13:40:41 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iBHIV6q02498
	for <megaco@ietf.org>; Fri, 17 Dec 2004 13:31:06 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Y0S9D96L>; Fri, 17 Dec 2004 13:31:07 -0500
Message-ID: <B258A372CEA20246A363BB86753DB5360165BEB7@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Richard Sun <xsun@lucent.com>,
        "Marcello Pantaleo (AC/EDD)"
	<marcello.pantaleo@ericsson.com>
Subject: RE: [Megaco] how codec negotiation is triggered by MGC?
Date: Fri, 17 Dec 2004 13:30:59 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

Why not just have the MGC choose the payload number for the 2833 events?

Note that the m line example here restricts the payload selectors to those
defined as RTP/AVP.  This can be avoided by using $ for that element as
well.

To confirm Marcello's statement, '*' is not a permitted wildcard in
underspecified SDP.  '$' is allowed in any position and means choose.  Note
that the use of wildcards is only allowed in the MGC->MG direction.  MGs are
always expected to send compliant SDP.

Kevin 

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Richard Sun
Sent: Friday, December 17, 2004 12:39 PM
To: Marcello Pantaleo (AC/EDD)
Cc: megaco@ietf.org
Subject: Re: [Megaco] how codec negotiation is triggered by MGC?

Marcello,
Thanks for your helpfull information.

Now assume that MGC audits MG and learns that MG supports "PCMU" *and*
"telephone-event".
If "m=audio $ RTP/AVP $" means that
MG to choose *one* codec, then
what is the syntax for MGC to instruct MG "use PCMU, *and* choose a payload
number for telephone-event"?

-Richard

Marcello Pantaleo (AC/EDD) wrote:

> Hi,
> 
> MGC can use audit capabilities to get the list of codecs supported by a
MG. Alternatively a MGC can be provisioned with MG capabilities.
> 
> MGC wouldn't use Add to know MG capabilities (e.g. supported codecs).
> 
> If MGC sends an Add command with an empty local desciptor, this is a
request to release any resources previously reserved for the media flow
received, that means nothing given that MGC is now creating the termination.
> If local descriptor is unspecified (i.e. absent), MG considers this as
missing mandatory parameter. MG uses whatever previously specified. 
> 
> If MGC sends "m=audio $ RTP/AVP $" it requests MG to choose one of the
supported codecs, so you don't get the list.
> 
> I don't think you can use * wildcard in the "m=".
> 
> Regards,
> Marcello
> 
> -----Original Message-----
> From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]On 
> Behalf Of Richard Sun
> Sent: Thursday, December 16, 2004 3:08 PM
> To: megaco@ietf.org
> Subject: [Megaco] how codec negotiation is triggered by MGC?
> 
> 
> Hi, Can anyone pelase clarify the standard for MGC to trigger a codec 
> negotiation in MG (i.e, MG should provide a list of codecs it 
> supports)?
> 
> One way I can think of is an empty "Local{}"
> without SDP, such as:
> Transaction = 299012 {
>   Context = $ {
>     Add = aaln/1 {
>       Media { Stream = 1 {
>         LocalControl {Mode = SendReceive}
>     }}},
>     Add = $ {
>       Media {Stream = 1 {
>         LocalControl {Mode=ReceiveOnly},
>         Local {}
> }}}}}
> 
> The question is: is this legal? Should MG reject the message with some 
> kind of error such as "SDP missing", or MG is suppose to fill up the 
> SDP section in response?
> What if the "Local{}" does not present at all?
> 
> The other way is something like this:
> Transaction = 299012 {
>   Context = $ {
>     Add = aaln/1 {
>       Media { Stream = 1 {
>         LocalControl {Mode = SendReceive}
>     }}},
>     Add = $ {
>       Media {Stream = 1 {
>         LocalControl {Mode=ReceiveOnly},
>         Local {
> v=0
> o=$ $ $ IN IP4 $
> s=$
> c=IN IP4 $
> t=$ $
> m=audio $ RTP/AVP -
> a=ptime:20
> }}}}}}
> With "-" in "m=audio $ RTP/AVP -", should MG fill up the list of 
> codecs?
> Or should it be something like
> "m=audio $ RTP/AVP $"?
> 
> Thanks for any information.
> -Richard
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Fri Dec 17 14:21:02 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23461
	for <megaco-archive@lists.ietf.org>; Fri, 17 Dec 2004 14:21:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfNW9-00056X-UP; Fri, 17 Dec 2004 14:11:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfNRR-0004C4-VP
	for megaco@megatron.ietf.org; Fri, 17 Dec 2004 14:07:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22248
	for <megaco@ietf.org>; Fri, 17 Dec 2004 14:07:04 -0500 (EST)
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfNa8-00082Q-Vk
	for megaco@ietf.org; Fri, 17 Dec 2004 14:16:05 -0500
Received: from wink.ho.lucent.com (h135-112-126-3.lucent.com [135.112.126.3])
	by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id iBHJ6sn3012863
	for <megaco@ietf.org>; Fri, 17 Dec 2004 13:06:59 -0600 (CST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id OAA07574; Fri, 17 Dec 2004 14:06:53 -0500 (EST)
Received: from [135.112.108.30] by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id OAA07559; Fri, 17 Dec 2004 14:06:51 -0500 (EST)
Message-ID: <41C330BF.4030001@lucent.com>
Date: Fri, 17 Dec 2004 14:17:19 -0500
From: Richard Sun <xsun@lucent.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Kevin Boyle <kboyle@nortelnetworks.com>
Original-CC: "Marcello Pantaleo (AC/EDD)" <marcello.pantaleo@ericsson.com>,
	megaco@ietf.org
Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
References: <B258A372CEA20246A363BB86753DB5360165BEB7@zrtphxm2>
In-Reply-To: <B258A372CEA20246A363BB86753DB5360165BEB7@zrtphxm2>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
Content-Transfer-Encoding: 7bit
Cc: "Marcello Pantaleo \(AC/EDD\)" <marcello.pantaleo@ericsson.com>,
        megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Kevin,
Thanks for the reply.

 > Why not just have the MGC choose the payload number for
 > the 2833 events?

Good question. That was what I asked. But some
MGC implementation says that MGC does not
care rfc2833 and its payload type at all, MGC just expects
MG to turn on rfc2833 automatically. I thought this
is not possible, so I asked the question just to
make sure that I do not miss anything.

To put it another way:
does it make any sense for any MGC to say:
"MGC never needs to look at the SDP contents, it
just pass SDP among MGs. MGs should just
handle the codec negotiation themself"?

This is indeed possible with MGCP. But it seems
that this is really not possibile with H248.
For H248, MGC always needs to be involved in this
codec negotiation.

Let me know if I am wrong. Thanks,
-Richard


Kevin Boyle wrote:

> Why not just have the MGC choose the payload number for the 2833 events?
> 
> Note that the m line example here restricts the payload selectors to 
> those defined as RTP/AVP.  This can be avoided by using $ for that 
> element as well.
> 
> To confirm Marcello's statement, '*' is not a permitted wildcard in 
> underspecified SDP.  '$' is allowed in any position and means choose.  
> Note that the use of wildcards is only allowed in the MGC->MG 
> direction.  MGs are always expected to send compliant SDP.
> 
> Kevin
> 
> -----Original Message-----
> From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf 
> Of Richard Sun
> Sent: Friday, December 17, 2004 12:39 PM
> To: Marcello Pantaleo (AC/EDD)
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
> 
> Marcello,
> Thanks for your helpfull information.
> 
> Now assume that MGC audits MG and learns that MG supports "PCMU" *and* 
> "telephone-event".
> If "m=audio $ RTP/AVP $" means that
> MG to choose *one* codec, then
> what is the syntax for MGC to instruct MG "use PCMU, *and* choose a 
> payload number for telephone-event"?
> 
> -Richard
> 
> Marcello Pantaleo (AC/EDD) wrote:
> 
>  > Hi,
>  >
>  > MGC can use audit capabilities to get the list of codecs supported by 
> a MG. Alternatively a MGC can be provisioned with MG capabilities.
> 
>  >
>  > MGC wouldn't use Add to know MG capabilities (e.g. supported codecs).
>  >
>  > If MGC sends an Add command with an empty local desciptor, this is a 
> request to release any resources previously reserved for the media flow 
> received, that means nothing given that MGC is now creating the termination.
> 
>  > If local descriptor is unspecified (i.e. absent), MG considers this 
> as missing mandatory parameter. MG uses whatever previously specified.
> 
>  >
>  > If MGC sends "m=audio $ RTP/AVP $" it requests MG to choose one of 
> the supported codecs, so you don't get the list.
>  >
>  > I don't think you can use * wildcard in the "m=".
>  >
>  > Regards,
>  > Marcello
>  >
>  > -----Original Message-----
>  > From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]On
>  > Behalf Of Richard Sun
>  > Sent: Thursday, December 16, 2004 3:08 PM
>  > To: megaco@ietf.org
>  > Subject: [Megaco] how codec negotiation is triggered by MGC?
>  >
>  >
>  > Hi, Can anyone pelase clarify the standard for MGC to trigger a codec
>  > negotiation in MG (i.e, MG should provide a list of codecs it
>  > supports)?
>  >
>  > One way I can think of is an empty "Local{}"
>  > without SDP, such as:
>  > Transaction = 299012 {
>  >   Context = $ {
>  >     Add = aaln/1 {
>  >       Media { Stream = 1 {
>  >         LocalControl {Mode = SendReceive}
>  >     }}},
>  >     Add = $ {
>  >       Media {Stream = 1 {
>  >         LocalControl {Mode=ReceiveOnly},
>  >         Local {}
>  > }}}}}
>  >
>  > The question is: is this legal? Should MG reject the message with some
>  > kind of error such as "SDP missing", or MG is suppose to fill up the
>  > SDP section in response?
>  > What if the "Local{}" does not present at all?
>  >
>  > The other way is something like this:
>  > Transaction = 299012 {
>  >   Context = $ {
>  >     Add = aaln/1 {
>  >       Media { Stream = 1 {
>  >         LocalControl {Mode = SendReceive}
>  >     }}},
>  >     Add = $ {
>  >       Media {Stream = 1 {
>  >         LocalControl {Mode=ReceiveOnly},
>  >         Local {
>  > v=0
>  > o=$ $ $ IN IP4 $
>  > s=$
>  > c=IN IP4 $
>  > t=$ $
>  > m=audio $ RTP/AVP -
>  > a=ptime:20
>  > }}}}}}
>  > With "-" in "m=audio $ RTP/AVP -", should MG fill up the list of
>  > codecs?
>  > Or should it be something like
>  > "m=audio $ RTP/AVP $"?
>  >
>  > Thanks for any information.
>  > -Richard
>  >
>  > _______________________________________________
>  > Megaco mailing list
>  > Megaco@ietf.org
>  > https://www1.ietf.org/mailman/listinfo/megaco
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Fri Dec 17 14:33:48 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24749
	for <megaco-archive@lists.ietf.org>; Fri, 17 Dec 2004 14:33:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfNmb-0000QJ-Oz; Fri, 17 Dec 2004 14:28:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfNgo-0007LD-2G
	for megaco@megatron.ietf.org; Fri, 17 Dec 2004 14:22:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23692
	for <megaco@ietf.org>; Fri, 17 Dec 2004 14:22:56 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfNpU-0008Sz-PL
	for megaco@ietf.org; Fri, 17 Dec 2004 14:31:57 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iBHJMMM25353
	for <megaco@ietf.org>; Fri, 17 Dec 2004 14:22:23 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Y0S91C28>; Fri, 17 Dec 2004 14:22:24 -0500
Message-ID: <B258A372CEA20246A363BB86753DB5360165BFB0@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Richard Sun <xsun@lucent.com>
Subject: RE: [Megaco] how codec negotiation is triggered by MGC?
Date: Fri, 17 Dec 2004 14:22:13 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1
Cc: "Marcello Pantaleo \(AC/EDD\)" <marcello.pantaleo@ericsson.com>,
        megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

Actually, this is not true.  While MGCP does not send SDP from the CA to the
MTA, it *does* send "Local Connection Options" which function in the same
capacity as underspecified Local SDP in H.248 -- to indicate to the MG the
constraints of the SDP it may return.

Now, if the MG wants to always do 2833 and you don't want the MGC to worry
about having to ask the MG to do it, then the MGC could send an
underspecified SDP requesting that the MG choose the codecs.  The MG can
then choose to include a payload number for 2833 if it chooses to do so.

Kevin 

-----Original Message-----
From: Richard Sun [mailto:xsun@lucent.com] 
Sent: Friday, December 17, 2004 2:17 PM
To: Boyle, Kevin [NCRTP:3Z40:EXCH]
Cc: Marcello Pantaleo (AC/EDD); megaco@ietf.org
Subject: Re: [Megaco] how codec negotiation is triggered by MGC?

Kevin,
Thanks for the reply.

 > Why not just have the MGC choose the payload number for  > the 2833
events?

Good question. That was what I asked. But some MGC implementation says that
MGC does not care rfc2833 and its payload type at all, MGC just expects MG
to turn on rfc2833 automatically. I thought this is not possible, so I asked
the question just to make sure that I do not miss anything.

To put it another way:
does it make any sense for any MGC to say:
"MGC never needs to look at the SDP contents, it just pass SDP among MGs.
MGs should just handle the codec negotiation themself"?

This is indeed possible with MGCP. But it seems that this is really not
possibile with H248.
For H248, MGC always needs to be involved in this codec negotiation.

Let me know if I am wrong. Thanks,
-Richard


Kevin Boyle wrote:

> Why not just have the MGC choose the payload number for the 2833 events?
> 
> Note that the m line example here restricts the payload selectors to 
> those defined as RTP/AVP.  This can be avoided by using $ for that 
> element as well.
> 
> To confirm Marcello's statement, '*' is not a permitted wildcard in 
> underspecified SDP.  '$' is allowed in any position and means choose.
> Note that the use of wildcards is only allowed in the MGC->MG 
> direction.  MGs are always expected to send compliant SDP.
> 
> Kevin
> 
> -----Original Message-----
> From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On 
> Behalf Of Richard Sun
> Sent: Friday, December 17, 2004 12:39 PM
> To: Marcello Pantaleo (AC/EDD)
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
> 
> Marcello,
> Thanks for your helpfull information.
> 
> Now assume that MGC audits MG and learns that MG supports "PCMU" *and* 
> "telephone-event".
> If "m=audio $ RTP/AVP $" means that
> MG to choose *one* codec, then
> what is the syntax for MGC to instruct MG "use PCMU, *and* choose a 
> payload number for telephone-event"?
> 
> -Richard
> 
> Marcello Pantaleo (AC/EDD) wrote:
> 
>  > Hi,
>  >
>  > MGC can use audit capabilities to get the list of codecs supported 
> by a MG. Alternatively a MGC can be provisioned with MG capabilities.
> 
>  >
>  > MGC wouldn't use Add to know MG capabilities (e.g. supported codecs).
>  >
>  > If MGC sends an Add command with an empty local desciptor, this is 
> a request to release any resources previously reserved for the media 
> flow received, that means nothing given that MGC is now creating the
termination.
> 
>  > If local descriptor is unspecified (i.e. absent), MG considers this 
> as missing mandatory parameter. MG uses whatever previously specified.
> 
>  >
>  > If MGC sends "m=audio $ RTP/AVP $" it requests MG to choose one of 
> the supported codecs, so you don't get the list.
>  >
>  > I don't think you can use * wildcard in the "m=".
>  >
>  > Regards,
>  > Marcello
>  >
>  > -----Original Message-----
>  > From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]On
>  > Behalf Of Richard Sun
>  > Sent: Thursday, December 16, 2004 3:08 PM  > To: megaco@ietf.org  > 
> Subject: [Megaco] how codec negotiation is triggered by MGC?
>  >
>  >
>  > Hi, Can anyone pelase clarify the standard for MGC to trigger a 
> codec  > negotiation in MG (i.e, MG should provide a list of codecs it  
> > supports)?
>  >
>  > One way I can think of is an empty "Local{}"
>  > without SDP, such as:
>  > Transaction = 299012 {
>  >   Context = $ {
>  >     Add = aaln/1 {
>  >       Media { Stream = 1 {
>  >         LocalControl {Mode = SendReceive}
>  >     }}},
>  >     Add = $ {
>  >       Media {Stream = 1 {
>  >         LocalControl {Mode=ReceiveOnly},
>  >         Local {}
>  > }}}}}
>  >
>  > The question is: is this legal? Should MG reject the message with 
> some  > kind of error such as "SDP missing", or MG is suppose to fill 
> up the  > SDP section in response?
>  > What if the "Local{}" does not present at all?
>  >
>  > The other way is something like this:
>  > Transaction = 299012 {
>  >   Context = $ {
>  >     Add = aaln/1 {
>  >       Media { Stream = 1 {
>  >         LocalControl {Mode = SendReceive}
>  >     }}},
>  >     Add = $ {
>  >       Media {Stream = 1 {
>  >         LocalControl {Mode=ReceiveOnly},
>  >         Local {
>  > v=0
>  > o=$ $ $ IN IP4 $
>  > s=$
>  > c=IN IP4 $
>  > t=$ $
>  > m=audio $ RTP/AVP -
>  > a=ptime:20
>  > }}}}}}
>  > With "-" in "m=audio $ RTP/AVP -", should MG fill up the list of  > 
> codecs?
>  > Or should it be something like
>  > "m=audio $ RTP/AVP $"?
>  >
>  > Thanks for any information.
>  > -Richard
>  >
>  > _______________________________________________
>  > Megaco mailing list
>  > Megaco@ietf.org
>  > https://www1.ietf.org/mailman/listinfo/megaco
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Fri Dec 17 16:47:57 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15059
	for <megaco-archive@lists.ietf.org>; Fri, 17 Dec 2004 16:47:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfPdt-0007wG-D4; Fri, 17 Dec 2004 16:28:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfP8Z-000221-4k
	for megaco@megatron.ietf.org; Fri, 17 Dec 2004 15:55:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04149
	for <megaco@ietf.org>; Fri, 17 Dec 2004 15:55:41 -0500 (EST)
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfPHG-0003Rs-Bc
	for megaco@ietf.org; Fri, 17 Dec 2004 16:04:43 -0500
Received: from wink.ho.lucent.com (h135-112-126-3.lucent.com [135.112.126.3])
	by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id iBHKtd2x009270
	for <megaco@ietf.org>; Fri, 17 Dec 2004 14:55:39 -0600 (CST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id PAA07851; Fri, 17 Dec 2004 15:55:35 -0500 (EST)
Received: from [192.11.61.203] by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id PAA07837; Fri, 17 Dec 2004 15:55:33 -0500 (EST)
Message-ID: <41C347C7.7000002@lucent.com>
Date: Fri, 17 Dec 2004 15:55:35 -0500
From: Richard Sun <xsun@lucent.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Kevin Boyle <kboyle@nortelnetworks.com>
Original-CC: "Marcello Pantaleo (AC/EDD)" <marcello.pantaleo@ericsson.com>,
	megaco@ietf.org
Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
References: <B258A372CEA20246A363BB86753DB5360165BFB0@zrtphxm2>
In-Reply-To: <B258A372CEA20246A363BB86753DB5360165BFB0@zrtphxm2>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b66a1e94d7d92973ece9e5da449ff80
Content-Transfer-Encoding: 7bit
Cc: "Marcello Pantaleo \(AC/EDD\)" <marcello.pantaleo@ericsson.com>,
        megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Kevin, thanks for the response. See below ...

>Actually, this is not true.  While MGCP does not send SDP from the CA to the
>MTA, it *does* send "Local Connection Options" which function in the same
>capacity as underspecified Local SDP in H.248 -- to indicate to the MG the
>constraints of the SDP it may return.
>  
>
Agree.

>Now, if the MG wants to always do 2833 and you don't want the MGC to worry
>about having to ask the MG to do it, then the MGC could send an
>underspecified SDP requesting that the MG choose the codecs.  The MG can
>then choose to include a payload number for 2833 if it chooses to do so.
>  
>
So it is true that, in any case, MGC needs to do something special to 
handle rfc2833.
Just want to be clear on "underspecified SDP request":

If MGC just sends "m=audio $ RTP/AVP 0", it means no rfc2833, right?

If MGC sends "m=audio $ RTP/AVP $", it means that MG will choose *one* 
codec,
say, MG may respond "m=audio 8000 RTP/AVP 0", but how MG responds
the payload number for RFC2833 if it always wants to support RFC2833? If 
MGC sends
m=audio $ RTP/AVP $
a=rtpmap:$ telephone-evemts/8000
then can MG responds with
m=audio 8000 RTP/AVP 0 101
a=rtpmap:101 telephone-evemts/8000
If this the true, then is the last $ in "m=" acturally a list?

Or should MG respond with
m=audio 8000 RTP/AVP 0
a=rtpmap:101 telephone-evemts/8000
(is this SDP legal?)

Regards,
Richard


>Kevin 
>
>-----Original Message-----
>From: Richard Sun [mailto:xsun@lucent.com] 
>Sent: Friday, December 17, 2004 2:17 PM
>To: Boyle, Kevin [NCRTP:3Z40:EXCH]
>Cc: Marcello Pantaleo (AC/EDD); megaco@ietf.org
>Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
>
>Kevin,
>Thanks for the reply.
>
> > Why not just have the MGC choose the payload number for  > the 2833
>events?
>
>Good question. That was what I asked. But some MGC implementation says that
>MGC does not care rfc2833 and its payload type at all, MGC just expects MG
>to turn on rfc2833 automatically. I thought this is not possible, so I asked
>the question just to make sure that I do not miss anything.
>
>To put it another way:
>does it make any sense for any MGC to say:
>"MGC never needs to look at the SDP contents, it just pass SDP among MGs.
>MGs should just handle the codec negotiation themself"?
>
>This is indeed possible with MGCP. But it seems that this is really not
>possibile with H248.
>For H248, MGC always needs to be involved in this codec negotiation.
>
>Let me know if I am wrong. Thanks,
>-Richard
>
>
>Kevin Boyle wrote:
>
>  
>
>>Why not just have the MGC choose the payload number for the 2833 events?
>>
>>Note that the m line example here restricts the payload selectors to 
>>those defined as RTP/AVP.  This can be avoided by using $ for that 
>>element as well.
>>
>>To confirm Marcello's statement, '*' is not a permitted wildcard in 
>>underspecified SDP.  '$' is allowed in any position and means choose.
>>Note that the use of wildcards is only allowed in the MGC->MG 
>>direction.  MGs are always expected to send compliant SDP.
>>
>>Kevin
>>
>>-----Original Message-----
>>From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On 
>>Behalf Of Richard Sun
>>Sent: Friday, December 17, 2004 12:39 PM
>>To: Marcello Pantaleo (AC/EDD)
>>Cc: megaco@ietf.org
>>Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
>>
>>Marcello,
>>Thanks for your helpfull information.
>>
>>Now assume that MGC audits MG and learns that MG supports "PCMU" *and* 
>>"telephone-event".
>>If "m=audio $ RTP/AVP $" means that
>>MG to choose *one* codec, then
>>what is the syntax for MGC to instruct MG "use PCMU, *and* choose a 
>>payload number for telephone-event"?
>>
>>-Richard
>>
>>Marcello Pantaleo (AC/EDD) wrote:
>>
>> > Hi,
>> >
>> > MGC can use audit capabilities to get the list of codecs supported 
>>by a MG. Alternatively a MGC can be provisioned with MG capabilities.
>>
>> >
>> > MGC wouldn't use Add to know MG capabilities (e.g. supported codecs).
>> >
>> > If MGC sends an Add command with an empty local desciptor, this is 
>>a request to release any resources previously reserved for the media 
>>flow received, that means nothing given that MGC is now creating the
>>    
>>
>termination.
>  
>
>> > If local descriptor is unspecified (i.e. absent), MG considers this 
>>as missing mandatory parameter. MG uses whatever previously specified.
>>
>> >
>> > If MGC sends "m=audio $ RTP/AVP $" it requests MG to choose one of 
>>the supported codecs, so you don't get the list.
>> >
>> > I don't think you can use * wildcard in the "m=".
>> >
>> > Regards,
>> > Marcello
>> >
>> > -----Original Message-----
>> > From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]On
>> > Behalf Of Richard Sun
>> > Sent: Thursday, December 16, 2004 3:08 PM  > To: megaco@ietf.org  > 
>>Subject: [Megaco] how codec negotiation is triggered by MGC?
>> >
>> >
>> > Hi, Can anyone pelase clarify the standard for MGC to trigger a 
>>codec  > negotiation in MG (i.e, MG should provide a list of codecs it  
>>    
>>
>>>supports)?
>>>      
>>>
>> >
>> > One way I can think of is an empty "Local{}"
>> > without SDP, such as:
>> > Transaction = 299012 {
>> >   Context = $ {
>> >     Add = aaln/1 {
>> >       Media { Stream = 1 {
>> >         LocalControl {Mode = SendReceive}
>> >     }}},
>> >     Add = $ {
>> >       Media {Stream = 1 {
>> >         LocalControl {Mode=ReceiveOnly},
>> >         Local {}
>> > }}}}}
>> >
>> > The question is: is this legal? Should MG reject the message with 
>>some  > kind of error such as "SDP missing", or MG is suppose to fill 
>>up the  > SDP section in response?
>> > What if the "Local{}" does not present at all?
>> >
>> > The other way is something like this:
>> > Transaction = 299012 {
>> >   Context = $ {
>> >     Add = aaln/1 {
>> >       Media { Stream = 1 {
>> >         LocalControl {Mode = SendReceive}
>> >     }}},
>> >     Add = $ {
>> >       Media {Stream = 1 {
>> >         LocalControl {Mode=ReceiveOnly},
>> >         Local {
>> > v=0
>> > o=$ $ $ IN IP4 $
>> > s=$
>> > c=IN IP4 $
>> > t=$ $
>> > m=audio $ RTP/AVP -
>> > a=ptime:20
>> > }}}}}}
>> > With "-" in "m=audio $ RTP/AVP -", should MG fill up the list of  > 
>>codecs?
>> > Or should it be something like
>> > "m=audio $ RTP/AVP $"?
>> >
>> > Thanks for any information.
>> > -Richard
>> >
>> > _______________________________________________
>> > Megaco mailing list
>> > Megaco@ietf.org
>> > https://www1.ietf.org/mailman/listinfo/megaco
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>>
>>    
>>
>
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
>  
>


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Fri Dec 17 18:10:01 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28039
	for <megaco-archive@lists.ietf.org>; Fri, 17 Dec 2004 18:10:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfRAx-0004hF-21; Fri, 17 Dec 2004 18:06:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfQwy-0004vE-VD
	for megaco@megatron.ietf.org; Fri, 17 Dec 2004 17:51:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23580
	for <megaco@ietf.org>; Fri, 17 Dec 2004 17:51:50 -0500 (EST)
Received: from mail.utstar.com ([216.37.114.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfR5e-0001sP-5H
	for megaco@ietf.org; Fri, 17 Dec 2004 18:00:53 -0500
Received: from balanew (balanew.nj.us.utstar.com [172.16.41.57])
	by mail.utstar.com (8.12.10/8.12.10) with ESMTP id iBHMpYBL010719;
	Fri, 17 Dec 2004 17:51:35 -0500 (EST)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'Richard Sun'" <xsun@lucent.com>,
        "'Kevin Boyle'" <kboyle@nortelnetworks.com>
Subject: RE: [Megaco] how codec negotiation is triggered by MGC?
Date: Fri, 17 Dec 2004 17:51:32 -0500
Message-ID: <006d01c4e48a$f7b4fd70$392910ac@nj.us.utstar.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <41C347C7.7000002@lucent.com>
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a4e5f67c5e230eddf754446d1a2201a4
Content-Transfer-Encoding: quoted-printable
Cc: "'Marcello Pantaleo \(AC/EDD\)'" <marcello.pantaleo@ericsson.com>,
        megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

I don't think MGC can "assume" that the MG can always do RFC2833. MGC =
cannot
predict how an MG would respond to an underspecified SDP
(including/excluding RFC2833). When interoperating with multiple MGs, =
you
want to specifically know if each MG can or cannot do RFC2833.

I kinda agree with Richard that there's no clear method as to how the =
MGC
can learn of MG's ability to do RFC2833 in H.248.

Bala
=20

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf =
Of
Richard Sun
Sent: Friday, December 17, 2004 3:56 PM
To: Kevin Boyle
Cc: Marcello Pantaleo (AC/EDD); megaco@ietf.org
Subject: Re: [Megaco] how codec negotiation is triggered by MGC?

Kevin, thanks for the response. See below ...

>Actually, this is not true.  While MGCP does not send SDP from the CA =
to
the
>MTA, it *does* send "Local Connection Options" which function in the =
same
>capacity as underspecified Local SDP in H.248 -- to indicate to the MG =
the
>constraints of the SDP it may return.
> =20
>
Agree.

>Now, if the MG wants to always do 2833 and you don't want the MGC to =
worry
>about having to ask the MG to do it, then the MGC could send an
>underspecified SDP requesting that the MG choose the codecs.  The MG =
can
>then choose to include a payload number for 2833 if it chooses to do =
so.
> =20
>
So it is true that, in any case, MGC needs to do something special to=20
handle rfc2833.
Just want to be clear on "underspecified SDP request":

If MGC just sends "m=3Daudio $ RTP/AVP 0", it means no rfc2833, right?

If MGC sends "m=3Daudio $ RTP/AVP $", it means that MG will choose *one* =

codec,
say, MG may respond "m=3Daudio 8000 RTP/AVP 0", but how MG responds
the payload number for RFC2833 if it always wants to support RFC2833? If =

MGC sends
m=3Daudio $ RTP/AVP $
a=3Drtpmap:$ telephone-evemts/8000
then can MG responds with
m=3Daudio 8000 RTP/AVP 0 101
a=3Drtpmap:101 telephone-evemts/8000
If this the true, then is the last $ in "m=3D" acturally a list?

Or should MG respond with
m=3Daudio 8000 RTP/AVP 0
a=3Drtpmap:101 telephone-evemts/8000
(is this SDP legal?)

Regards,
Richard


>Kevin=20
>
>-----Original Message-----
>From: Richard Sun [mailto:xsun@lucent.com]=20
>Sent: Friday, December 17, 2004 2:17 PM
>To: Boyle, Kevin [NCRTP:3Z40:EXCH]
>Cc: Marcello Pantaleo (AC/EDD); megaco@ietf.org
>Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
>
>Kevin,
>Thanks for the reply.
>
> > Why not just have the MGC choose the payload number for  > the 2833
>events?
>
>Good question. That was what I asked. But some MGC implementation says =
that
>MGC does not care rfc2833 and its payload type at all, MGC just expects =
MG
>to turn on rfc2833 automatically. I thought this is not possible, so I
asked
>the question just to make sure that I do not miss anything.
>
>To put it another way:
>does it make any sense for any MGC to say:
>"MGC never needs to look at the SDP contents, it just pass SDP among =
MGs.
>MGs should just handle the codec negotiation themself"?
>
>This is indeed possible with MGCP. But it seems that this is really not
>possibile with H248.
>For H248, MGC always needs to be involved in this codec negotiation.
>
>Let me know if I am wrong. Thanks,
>-Richard
>
>
>Kevin Boyle wrote:
>
> =20
>
>>Why not just have the MGC choose the payload number for the 2833 =
events?
>>
>>Note that the m line example here restricts the payload selectors to=20
>>those defined as RTP/AVP.  This can be avoided by using $ for that=20
>>element as well.
>>
>>To confirm Marcello's statement, '*' is not a permitted wildcard in=20
>>underspecified SDP.  '$' is allowed in any position and means choose.
>>Note that the use of wildcards is only allowed in the MGC->MG=20
>>direction.  MGs are always expected to send compliant SDP.
>>
>>Kevin
>>
>>-----Original Message-----
>>From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On=20
>>Behalf Of Richard Sun
>>Sent: Friday, December 17, 2004 12:39 PM
>>To: Marcello Pantaleo (AC/EDD)
>>Cc: megaco@ietf.org
>>Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
>>
>>Marcello,
>>Thanks for your helpfull information.
>>
>>Now assume that MGC audits MG and learns that MG supports "PCMU" *and* =

>>"telephone-event".
>>If "m=3Daudio $ RTP/AVP $" means that
>>MG to choose *one* codec, then
>>what is the syntax for MGC to instruct MG "use PCMU, *and* choose a=20
>>payload number for telephone-event"?
>>
>>-Richard
>>
>>Marcello Pantaleo (AC/EDD) wrote:
>>
>> > Hi,
>> >
>> > MGC can use audit capabilities to get the list of codecs supported=20
>>by a MG. Alternatively a MGC can be provisioned with MG capabilities.
>>
>> >
>> > MGC wouldn't use Add to know MG capabilities (e.g. supported =
codecs).
>> >
>> > If MGC sends an Add command with an empty local desciptor, this is=20
>>a request to release any resources previously reserved for the media=20
>>flow received, that means nothing given that MGC is now creating the
>>   =20
>>
>termination.
> =20
>
>> > If local descriptor is unspecified (i.e. absent), MG considers this =

>>as missing mandatory parameter. MG uses whatever previously specified.
>>
>> >
>> > If MGC sends "m=3Daudio $ RTP/AVP $" it requests MG to choose one =
of=20
>>the supported codecs, so you don't get the list.
>> >
>> > I don't think you can use * wildcard in the "m=3D".
>> >
>> > Regards,
>> > Marcello
>> >
>> > -----Original Message-----
>> > From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]On
>> > Behalf Of Richard Sun
>> > Sent: Thursday, December 16, 2004 3:08 PM  > To: megaco@ietf.org  > =

>>Subject: [Megaco] how codec negotiation is triggered by MGC?
>> >
>> >
>> > Hi, Can anyone pelase clarify the standard for MGC to trigger a=20
>>codec  > negotiation in MG (i.e, MG should provide a list of codecs it =
=20
>>   =20
>>
>>>supports)?
>>>     =20
>>>
>> >
>> > One way I can think of is an empty "Local{}"
>> > without SDP, such as:
>> > Transaction =3D 299012 {
>> >   Context =3D $ {
>> >     Add =3D aaln/1 {
>> >       Media { Stream =3D 1 {
>> >         LocalControl {Mode =3D SendReceive}
>> >     }}},
>> >     Add =3D $ {
>> >       Media {Stream =3D 1 {
>> >         LocalControl {Mode=3DReceiveOnly},
>> >         Local {}
>> > }}}}}
>> >
>> > The question is: is this legal? Should MG reject the message with=20
>>some  > kind of error such as "SDP missing", or MG is suppose to fill=20
>>up the  > SDP section in response?
>> > What if the "Local{}" does not present at all?
>> >
>> > The other way is something like this:
>> > Transaction =3D 299012 {
>> >   Context =3D $ {
>> >     Add =3D aaln/1 {
>> >       Media { Stream =3D 1 {
>> >         LocalControl {Mode =3D SendReceive}
>> >     }}},
>> >     Add =3D $ {
>> >       Media {Stream =3D 1 {
>> >         LocalControl {Mode=3DReceiveOnly},
>> >         Local {
>> > v=3D0
>> > o=3D$ $ $ IN IP4 $
>> > s=3D$
>> > c=3DIN IP4 $
>> > t=3D$ $
>> > m=3Daudio $ RTP/AVP -
>> > a=3Dptime:20
>> > }}}}}}
>> > With "-" in "m=3Daudio $ RTP/AVP -", should MG fill up the list of  =
>=20
>>codecs?
>> > Or should it be something like
>> > "m=3Daudio $ RTP/AVP $"?
>> >
>> > Thanks for any information.
>> > -Richard
>> >
>> > _______________________________________________
>> > Megaco mailing list
>> > Megaco@ietf.org
>> > https://www1.ietf.org/mailman/listinfo/megaco
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>>
>>   =20
>>
>
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
> =20
>


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Fri Dec 17 23:20:29 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00587
	for <megaco-archive@lists.ietf.org>; Fri, 17 Dec 2004 23:20:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfW36-0007t7-Lk; Fri, 17 Dec 2004 23:18:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfW0Y-0007Ec-Pr
	for megaco@megatron.ietf.org; Fri, 17 Dec 2004 23:15:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00347
	for <megaco@ietf.org>; Fri, 17 Dec 2004 23:15:50 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfW9I-0005b6-8P
	for megaco@ietf.org; Fri, 17 Dec 2004 23:24:56 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iBI4FJJ24363
	for <megaco@ietf.org>; Fri, 17 Dec 2004 23:15:19 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Y0S91RJV>; Fri, 17 Dec 2004 23:15:19 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536016DE391@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Balasubramanian Pitchandi <bs@utstar.com>,
        "'Richard Sun'"
	<xsun@lucent.com>
Subject: RE: [Megaco] how codec negotiation is triggered by MGC?
Date: Fri, 17 Dec 2004 23:15:11 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8cb9b411340046bf4080a729180a0672
Cc: "'Marcello Pantaleo \(AC/EDD\)'" <marcello.pantaleo@ericsson.com>,
        megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

Why would the MGC care if the MG can do 2833?  If it matters, then the MGC
can explicitly signal it in the Local descriptor by choosing a dynamic
payload number and including the appropriate rtpmap and associated a line
parameters.

If the MGC sends $ as the payload list, the MG can return as many payload
numbers as it likes, ordered by preference.  So if the MG wishes to include
2833 as an option, it would return the info necessary in the SDP along with
whatever other codecs it may wish to choose.

If the MGC really NEEDS to know if the MG can do RFC2833 out of band
signalling of telephony events, then it could try auditing the Local
descriptor for that information... but the response may be particularly
unwieldy and difficult to parse for the MGC.

Kevin 

-----Original Message-----
From: Balasubramanian Pitchandi [mailto:bs@utstar.com] 
Sent: Friday, December 17, 2004 5:52 PM
To: 'Richard Sun'; Boyle, Kevin [NCRTP:3Z40:EXCH]
Cc: 'Marcello Pantaleo (AC/EDD)'; megaco@ietf.org
Subject: RE: [Megaco] how codec negotiation is triggered by MGC?

I don't think MGC can "assume" that the MG can always do RFC2833. MGC cannot
predict how an MG would respond to an underspecified SDP
(including/excluding RFC2833). When interoperating with multiple MGs, you
want to specifically know if each MG can or cannot do RFC2833.

I kinda agree with Richard that there's no clear method as to how the MGC
can learn of MG's ability to do RFC2833 in H.248.

Bala
 

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Richard Sun
Sent: Friday, December 17, 2004 3:56 PM
To: Kevin Boyle
Cc: Marcello Pantaleo (AC/EDD); megaco@ietf.org
Subject: Re: [Megaco] how codec negotiation is triggered by MGC?

Kevin, thanks for the response. See below ...

>Actually, this is not true.  While MGCP does not send SDP from the CA 
>to
the
>MTA, it *does* send "Local Connection Options" which function in the 
>same capacity as underspecified Local SDP in H.248 -- to indicate to 
>the MG the constraints of the SDP it may return.
>  
>
Agree.

>Now, if the MG wants to always do 2833 and you don't want the MGC to 
>worry about having to ask the MG to do it, then the MGC could send an 
>underspecified SDP requesting that the MG choose the codecs.  The MG 
>can then choose to include a payload number for 2833 if it chooses to do
so.
>  
>
So it is true that, in any case, MGC needs to do something special to handle
rfc2833.
Just want to be clear on "underspecified SDP request":

If MGC just sends "m=audio $ RTP/AVP 0", it means no rfc2833, right?

If MGC sends "m=audio $ RTP/AVP $", it means that MG will choose *one*
codec, say, MG may respond "m=audio 8000 RTP/AVP 0", but how MG responds the
payload number for RFC2833 if it always wants to support RFC2833? If MGC
sends m=audio $ RTP/AVP $ a=rtpmap:$ telephone-evemts/8000 then can MG
responds with m=audio 8000 RTP/AVP 0 101
a=rtpmap:101 telephone-evemts/8000
If this the true, then is the last $ in "m=" acturally a list?

Or should MG respond with
m=audio 8000 RTP/AVP 0
a=rtpmap:101 telephone-evemts/8000
(is this SDP legal?)

Regards,
Richard


>Kevin
>
>-----Original Message-----
>From: Richard Sun [mailto:xsun@lucent.com]
>Sent: Friday, December 17, 2004 2:17 PM
>To: Boyle, Kevin [NCRTP:3Z40:EXCH]
>Cc: Marcello Pantaleo (AC/EDD); megaco@ietf.org
>Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
>
>Kevin,
>Thanks for the reply.
>
> > Why not just have the MGC choose the payload number for  > the 2833
>events?
>
>Good question. That was what I asked. But some MGC implementation says 
>that MGC does not care rfc2833 and its payload type at all, MGC just 
>expects MG to turn on rfc2833 automatically. I thought this is not 
>possible, so I
asked
>the question just to make sure that I do not miss anything.
>
>To put it another way:
>does it make any sense for any MGC to say:
>"MGC never needs to look at the SDP contents, it just pass SDP among MGs.
>MGs should just handle the codec negotiation themself"?
>
>This is indeed possible with MGCP. But it seems that this is really not 
>possibile with H248.
>For H248, MGC always needs to be involved in this codec negotiation.
>
>Let me know if I am wrong. Thanks,
>-Richard
>
>
>Kevin Boyle wrote:
>
>  
>
>>Why not just have the MGC choose the payload number for the 2833 events?
>>
>>Note that the m line example here restricts the payload selectors to 
>>those defined as RTP/AVP.  This can be avoided by using $ for that 
>>element as well.
>>
>>To confirm Marcello's statement, '*' is not a permitted wildcard in 
>>underspecified SDP.  '$' is allowed in any position and means choose.
>>Note that the use of wildcards is only allowed in the MGC->MG 
>>direction.  MGs are always expected to send compliant SDP.
>>
>>Kevin
>>
>>-----Original Message-----
>>From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On 
>>Behalf Of Richard Sun
>>Sent: Friday, December 17, 2004 12:39 PM
>>To: Marcello Pantaleo (AC/EDD)
>>Cc: megaco@ietf.org
>>Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
>>
>>Marcello,
>>Thanks for your helpfull information.
>>
>>Now assume that MGC audits MG and learns that MG supports "PCMU" *and* 
>>"telephone-event".
>>If "m=audio $ RTP/AVP $" means that
>>MG to choose *one* codec, then
>>what is the syntax for MGC to instruct MG "use PCMU, *and* choose a 
>>payload number for telephone-event"?
>>
>>-Richard
>>
>>Marcello Pantaleo (AC/EDD) wrote:
>>
>> > Hi,
>> >
>> > MGC can use audit capabilities to get the list of codecs supported
>>by a MG. Alternatively a MGC can be provisioned with MG capabilities.
>>
>> >
>> > MGC wouldn't use Add to know MG capabilities (e.g. supported codecs).
>> >
>> > If MGC sends an Add command with an empty local desciptor, this is
>>a request to release any resources previously reserved for the media 
>>flow received, that means nothing given that MGC is now creating the
>>    
>>
>termination.
>  
>
>> > If local descriptor is unspecified (i.e. absent), MG considers this
>>as missing mandatory parameter. MG uses whatever previously specified.
>>
>> >
>> > If MGC sends "m=audio $ RTP/AVP $" it requests MG to choose one of
>>the supported codecs, so you don't get the list.
>> >
>> > I don't think you can use * wildcard in the "m=".
>> >
>> > Regards,
>> > Marcello
>> >
>> > -----Original Message-----
>> > From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]On
>> > Behalf Of Richard Sun
>> > Sent: Thursday, December 16, 2004 3:08 PM  > To: megaco@ietf.org  >
>>Subject: [Megaco] how codec negotiation is triggered by MGC?
>> >
>> >
>> > Hi, Can anyone pelase clarify the standard for MGC to trigger a
>>codec  > negotiation in MG (i.e, MG should provide a list of codecs it
>>    
>>
>>>supports)?
>>>      
>>>
>> >
>> > One way I can think of is an empty "Local{}"
>> > without SDP, such as:
>> > Transaction = 299012 {
>> >   Context = $ {
>> >     Add = aaln/1 {
>> >       Media { Stream = 1 {
>> >         LocalControl {Mode = SendReceive}
>> >     }}},
>> >     Add = $ {
>> >       Media {Stream = 1 {
>> >         LocalControl {Mode=ReceiveOnly},
>> >         Local {}
>> > }}}}}
>> >
>> > The question is: is this legal? Should MG reject the message with
>>some  > kind of error such as "SDP missing", or MG is suppose to fill 
>>up the  > SDP section in response?
>> > What if the "Local{}" does not present at all?
>> >
>> > The other way is something like this:
>> > Transaction = 299012 {
>> >   Context = $ {
>> >     Add = aaln/1 {
>> >       Media { Stream = 1 {
>> >         LocalControl {Mode = SendReceive}
>> >     }}},
>> >     Add = $ {
>> >       Media {Stream = 1 {
>> >         LocalControl {Mode=ReceiveOnly},
>> >         Local {
>> > v=0
>> > o=$ $ $ IN IP4 $
>> > s=$
>> > c=IN IP4 $
>> > t=$ $
>> > m=audio $ RTP/AVP -
>> > a=ptime:20
>> > }}}}}}
>> > With "-" in "m=audio $ RTP/AVP -", should MG fill up the list of  >
>>codecs?
>> > Or should it be something like
>> > "m=audio $ RTP/AVP $"?
>> >
>> > Thanks for any information.
>> > -Richard
>> >
>> > _______________________________________________
>> > Megaco mailing list
>> > Megaco@ietf.org
>> > https://www1.ietf.org/mailman/listinfo/megaco
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>>
>>    
>>
>
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
>  
>


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco



_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Sun Dec 19 18:47:14 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21762
	for <megaco-archive@lists.ietf.org>; Sun, 19 Dec 2004 18:47:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgAfe-0002LB-Sz; Sun, 19 Dec 2004 18:41:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgAdo-00024c-ND
	for megaco@megatron.ietf.org; Sun, 19 Dec 2004 18:39:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20871
	for <megaco@ietf.org>; Sun, 19 Dec 2004 18:39:05 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgAmw-0006Og-K4
	for megaco@ietf.org; Sun, 19 Dec 2004 18:48:36 -0500
Received: from esealmw127.eemea.ericsson.se ([153.88.254.122])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBJNd2h5025304; Mon, 20 Dec 2004 00:39:02 +0100 (MET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 20 Dec 2004 00:39:01 +0100
Received: from eaubrnt019.epa.ericsson.se ([146.11.9.165]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 20 Dec 2004 00:39:00 +0100
Received: from ericsson.com (EG2E500202DSEGL [146.11.22.128]) by
	eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id Y0DJ8LZ3; Mon, 20 Dec 2004 10:38:53 +1100
Message-ID: <41C61131.8070205@ericsson.com>
Date: Mon, 20 Dec 2004 10:39:29 +1100
X-Sybari-Trust: 66954908 9db1dfa1 62357d84 00000139
From: Christian Groves <christian.groves@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: "Kamitses, Jerry" <jkamitses@sonusnet.com>
Subject: Re: [Megaco] Question on the semantics of Subtract command
References: <A3863F3136CBC546A40A61BA9CBA9D930119C222@sonusmail03.sonusnet.com>
In-Reply-To: <A3863F3136CBC546A40A61BA9CBA9D930119C222@sonusmail03.sonusnet.com>
Content-Type: multipart/mixed; boundary="------------040909080504070701010709"
X-OriginalArrivalTime: 19 Dec 2004 23:39:00.0988 (UTC)
	FILETIME=[EABF83C0:01C4E623]
X-Spam-Score: 3.2 (+++)
X-Scan-Signature: b6435b1bfa5977f2eb96dc7e52434b6d
Cc: Tom Taylor <taylor@nortelnetworks.com>, megaco@ietf.org,
        Kevin Boyle <kboyle@nortelnetworks.com>
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.
--------------040909080504070701010709
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hello Jerry,

The latest IG can be found at:
http://avguest@ftp3.itu.int/av-arch/avc-site/2001-2004/0411_Gen/H_248_Sub-Series_IG.zip 

PW: Avguest

As Tom has clarified in his earlier email the behaviour that is intended was 
that a Subtract stops signals and returns values to default (or provisioned). 
Yes this wasn't described in the best way that is why it was updated in the IG 
to be made clearer.

I have attached a message from 2000 to show this has been the case for a long 
time and is not something we recently dreamed up.

===========================================================================
-------- Original Message --------
Subject: 	Re: Event and Signal descriptor on Subtract
Date: 	Thu, 20 Apr 2000 08:16:10 -0500
From: 	Tom-PT Taylor <taylor@NORTELNETWORKS.COM>
Reply-To: 	Tom-PT Taylor <taylor@NORTELNETWORKS.COM>
To: 	MEGACO@STANDARDS.NORTELNETWORKS.COM



Based on the E-mail I just put out yesterday, this would be so, but the
default values of these descriptors (in the absence of provisioned
values) would be "empty".

       -----Original Message-----
       From:   Hemant Agrawal [SMTP:hemantag@FICON-TECH.COM]
       Sent:   Thursday, April 20, 2000 6:23 AM
       To:     MEGACO@STANDARDS.NORTELNETWORKS.COM
       Subject:        Event and Signal descriptor on Subtract

        Hi Brian, Tom, list,

        In ref to section 7.2.3 for Subtract command
        "When a provisioned Termination is Subtracted from a context, its
       property
        values shall revert to:
        *    the default value, if specified for the property and not
       overridden by
       provisioning,
        *    otherwise, the provisioned value."


         Is this action also valid for signal and event descriptor, that
       is, after
       a  termination
        is subtracted from a context, MG stops playing signals and stop
       listening
       for
        events (since the default value of Event & Signal Descriptor is
       NULL).



        thanks
        Hemant Agrawal



        ________________________________________
        Hemant Agrawal
        Ficon Technology
        E-mail: hemantag@ficon-tech.com
        Web: http://www.ficon-tech.com
===========================================================================

In answer to your queury on "Also, while a termination is in a non-NULL context 
is it still valid for the MGC to send a modify to the NULL context for the 
termination?" I would say no, the MG would send back an error code "435 Name: 
Termination ID is not in specified Context"


Regards, Christian

Kamitses, Jerry wrote:
> Tom,
> Thanks for such a prompt reply. 
> 
> Regarding operation of the Subtract command, I am a little surprised that 
> this important side effect of Subtract (which I learned of thru the grapevine) 
> seems to be nowhere expressly mentioned in the RFC? The section that specifies 
> signals and events doesn't mention it, and neither does the section on subtract, 
> other than the reference to property that I cited below, where "property" seems 
> to have acquired additional meaning. Elsewhere the RFC seems to view "properties" 
> and "events and signals" as being distinct? For example, Section 6.2.1 Termination 
> dynamics, contains the text:
>    The Termination properties, and events and signals are described in
>    the ensuing subclauses.  
> This seems to say that "events and signals" are distinct from "properties"?
> Likewise  6.2.3 Packages includes the text:
>    Properties, Events, Signals and Statistics defined in Packages, as
>    well as parameters to them, are referenced by identifiers (Ids).
> 
> Again suggesting that "Properties" and "Events, Signals" are different 
> animals? Same again in section 6.2.4 Termination properties and 
> descriptors:
> 	Terminations have properties.  
> 	The properties have unique PropertyIDs. 
> 
> This section (6.2.4) also addresses the effect of the Subtract command 
> when it describes what occurs when a termination is returned to the 
> NULL context.
> 	If not provisioned otherwise, the properties in all descriptors 
> 	except TerminationState and LocalControl default to empty/"no value" 
> 	when a Termination is first created or returned to the null Context.  
> 
> All use of the expression "property" in this section are clearly referring 
> to Property type properties and not signals/events, for example: 
> 	... properties are referred to by a name consisting of the PackageName 
> 	and a PropertyId.  
> 	... Properties may be read-only or read/write.  
> 
> In addition, the RFC does take pains to specify that the Subtract command 
> may not include any eventsDescriptor or signalsDescriptor. One seemingly 
> straightforward inference of this restriction regarding Subtract is that 
> the Subtract command is not intended to have any effect on the signal/event 
> state of a termination (except for the obvious case that the subtract 
> eliminates an ephemeral termination). The statement in section (6.2.4) 
> 	In general, if a Descriptor is completely omitted from one of the 
> 	aforementioned Commands, the properties in that Descriptor retain 
> 	their prior values for the Termination(s) upon which the Command acts.  
> contributes to the conclusion that Subtract should have no effect on 
> the eventsDescriptor or the signalsDescriptor (since these descriptors will 
> always be completely omitted in the Subtract).  The key to this confusion 
> is the vague use of "aforementioned Commands" instead precisely specifying 
> the commands which apply.
> 
> If the MGC's intention is to stop a signal as part of a Subtract then 
> a Modify with empty signalsDescriptor ahead of the Subtract seems like 
> a pretty straightforward way to accomplish this.
> 
> Furthermore, if a signal is active on a termination in the null context, and 
> an Add command that omits any eventsDescriptor or signalsDescriptor is sent 
> to that termination, then does the protocol require the signal to be stopped 
> in this case too?  If not (which I believe is the case?), then we seem to 
> have this strange asymmetry regarding events/signals:  the event/signal 
> can persist unaffected when the termination is added to a context but not 
> survive the termination being removed. I don't quite understand the 
> rationale behind this?
> 
> In light of the above I am a bit puzzled as to the definitive source of 
> "a Subtract definitely ends an on-going signal"?  Apparently the source is 
> not the actual RFC3525. Could it be in one of the implementer's guides, 
> or some other email thread?
> 
> Lastly, regarding your comment:
>   [subtract side effect] may possibly install an alternative if a 
>   non-empty Signals descriptor was provisioned as the default for 
>   the termination.
> 
> I am assuming the source for this in the RFC is again the text:
>     When a provisioned Termination is Subtracted from a Context, its
>     property values shall revert to:
>     -  the default value, if specified for the property and not
>        overridden by provisioning;
>     -  otherwise, the provisioned value.
> 
> In this case I am somewhat unclear as to exactly how this works for signals?
> If there is such a default signal provisioned for a termination then exactly 
> when is it re-activated? Only as a side effect of the Subtract command, or 
> might this also apply whenever the termination receives an empty 
> signalsDescriptor? 
> 
> I also have a question regarding the effect of Subtract on actual property 
> type "properties" for a termination. Property type properties can be altered 
> via MGC commands that contain instances of the  propertyParm, present in the 
> mediaDescriptor subdescriptors localControlDescriptor or terminationStateDescriptor. 
> 
> Instances of these descriptors may be present in Add and Modify type requests 
> sent to a termination in either the NULL or a non-NULL context. 
> 
> If the MGC changes the value of a property type property of a termination while 
> in the NULL context then according to the above RFC text this change will persist 
> at most until the next Subtract. Correct?
> 
> Is there is no means available in the protocol for the MGC to make a more permanent 
> change to a termination property type property that will persist across subsequent 
> add/subtract commands? Is there no distinction between property type properties that 
> are set when the termination is in a non-NULL context (which could be viewed as part 
> of an active call) vs. those set while the termination is in the NULL context 
> (which could be viewed more as semi-permanent)?
> 
> Also, while a termination is in a non-NULL context is it still valid for the MGC to 
> send a modify to the NULL context for the termination? This isn't discussed in 
> the section on Modify and I couldn't seem to find any other reference to this.
> If the NULL context is still a valid context for commands while the termination 
> is in a non-NULL context, and the MGC sets a property type property value, or 
> signals and/or events, for the NULL context at that termination, then do these 
> changes apply to the termination in the non-NULL context as well?  
> 
> Thanks again.
> 
> Happy Holidays
> 
> 
> 
> -----Original Message-----
> From: Tom Taylor [mailto:taylor@nortelnetworks.com]
> Sent: Thursday, December 16, 2004 8:33 PM
> To: Kamitses, Jerry
> Cc: megaco@ietf.org; Christian Groves; Kevin Boyle
> Subject: Re: [Megaco] Question on the semantics of Subtract command;
> Question regarding Digitmap Completion Events
> 
> 
> Answers below, marked by [PTT].
> 
> Kamitses, Jerry wrote:
> 
>>Reference RFC 3525    Gateway Control Protocol Version 1
>>
>>
>>Question 1) I would appreciate some clarification regarding precise effect 
>>of the Subtract command on physical terminations.  In Section  7.2.3 Subtract, 
>>the final paragraph states:
>>
>>   When a provisioned Termination is Subtracted from a Context, its
>>   property values shall revert to:
>>   -  the default value, if specified for the property and not
>>      overridden by provisioning;
>>   -  otherwise, the provisioned value.
>>
>>1a) I assume "provisioned Termination" in the 1st line should read "physical Termination"
>>since the concept of "provisioned Termination" does not appear elsewhere in the RFC.
>>Is this correct, or is there some other meaning for "provisioned Termination" that is 
>>intended here?
>>
> 
> [PTT] I may have introduced this phrase once upon a time.  It's probably a red 
> herring, but I have always believed that one could provision terminations that 
> would otherwise be ephemerals -- PVCs in effect.  That's why the term, but I 
> expect in normal practice this is identical with "physical termination".
> 
> 
>>(1b) It is not clear to me from the context exactly what is meant by "property"? Is 
>>"property" used to refer strictly to the formal concept of termination properties, 
>>that is,  parameters that are assigned values via the 
>>        propertyParm         = pkgdName parmValue
>>productions in the formal syntax using the localControlDescriptor and/or terminationStateDescriptor.  
>>
>>Or is "property" here used in some more generic sense to possibly refer to other 
>>aspects of the termination state?
>>
>>For example, if a subtract is sent to a termination with a currently active signal then 
>>does the signal stop as a side effect of receiving the subtract, or should the signal 
>>be unaffected by the subtract.?
> 
> 
> [PTT] "Property" here is intended in the generic sense that all descriptor values 
> are properties of the termination.  Thus a Subtract definitely ends an on-going 
> signal, and may possibly install an alternative if a non-empty Signals descriptor 
> was provisioned as the default for the termination.
> 
>>Question 2) Digitmap Completion Events 
>>
>>2a)  Section 7.1.9 Events Descriptor contains the text:
>>    The default streamID is 0, indicating that the event to be
>>    detected is not related to a particular media stream.
>>
>>We have assumed that streamID 0 also could mean the event is related to all 
>>media streams. That is, for those events which apply to media streams, then 
>>when there are one or more streams on the context, and the MGC wants to enable 
>>an event concurrently on all streams, must the MGC send one instance of the 
>>event with streamID 0, or must the MGC send multiple instances each a separate 
>>non-0 streamID?
>>
> 
> [PTT] One instance with streamID 0 will pick up digitmap completion events from 
> all active streams.  If it is important to relate the event to the originating 
> stream, you might want to enable the events against the individual streams.
> 
> 
>>2b) This section also contains the text: 
>>  If a digit map completion event is present or implied in the
>>   EventsDescriptor, the EventDM parameter is used to carry either the
>>   name or the value of the associated digit map.  
>>
>>Could you please explain "implied" digitmap completion event and provide a 
>>pointer to RFC text that discusses this concept? 
> 
> 
> [PTT] I believe this was meant to refer to the use of the "ALL" wildcard as 
> described in the preceding paragraph.  I would have to look at the Megaco 
> correspondance between February and May of 2000 to verify that.  (The text first 
> appears in the RFC 2886 corrigendum to RFC 2885.)
> 
>>2c) Regarding the statement in section 7.1.14.6 DigitMap Activation
>>   A digit map completion event that does not contain an eventDM field
>>   in its requested actions field is considered an error.  
>>We have encountered instances of the following message syntax
>>
>>    ... Events = 1 { dd/ce }, DigitMap = { (0 | xxxxxxxx|x.#) } ...
>>
>>Since the digitMapDescriptor in the above example omits the digitMapName, 
>>then clearly it has no possible use except in the context of the associated 
>>completion event.  Perhaps  this could be an instance of an "implied" digitMapDescriptor 
>>for the completion event,  and be allowed even though it seems to technically violate 
>>the correct syntax for the ce event, which should be 
>>
>>    ... Events = 1 { dd/ce{ DigitMap = { (0 | xxxxxxxx|x.#) } }  }, ...
>>
>>Is the 1st Events example above allowable ?
>>
> 
> [PTT] I think I'll leave this one for Kevin or Christian to comment on.
> 
>>Thanks.
>>
>>
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>>
>>
> 
> 

--------------040909080504070701010709
Content-Type: message/rfc822;
 name="Attached Message"
Content-Disposition: inline;
 filename="Attached Message"

Received: from brsi02.epa.ericsson.se ([146.11.15.8]) by
	eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2448.0)
	id H0011KRP; Thu, 20 Apr 2000 23:21:54 +1000
Received: from mcsi00.epa.ericsson.se (mcsi00 [146.11.8.201])
	by brsi02.epa.ericsson.se (8.9.1/8.9.1) with ESMTP id XAA09150;
	Thu, 20 Apr 2000 23:22:18 +1000 (EST)
Received: from brsi02.epa.ericsson.se (brsi02.epa.ericsson.se [146.11.15.8])
	by mcsi00.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id XAA11945;
	Thu, 20 Apr 2000 23:22:02 +1000 (EST)
Received: from alaska.wise.edt.ericsson.se (alaska.wise.edt.ericsson.se
	[153.88.253.21])
	by brsi02.epa.ericsson.se (8.9.1/8.9.1) with ESMTP id XAA09135;
	Thu, 20 Apr 2000 23:22:13 +1000 (EST)
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com
	[137.118.21.16])
	by alaska.wise.edt.ericsson.se (8.9.3/8.9.3/WIREfire-1.8) with ESMTP id
	PAA01439; Thu, 20 Apr 2000 15:20:07 +0200 (MET DST)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com
	(LSMTP for Windows NT v1.1a) with SMTP id
	<0.A35B23B0@standards.nortelnetworks.com>;
	Thu, 20 Apr 2000 9:13:06 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
	(LISTSERV-TCP/IP release 1.8d) with spool id 9767 for
	MEGACO@STANDARDS.NORTELNETWORKS.COM; Thu, 20 Apr 2000 09:11:49 -0400
Received: from smtprich.nortel.com by standards.nortelnetworks.com (LSMTP for
	Windows NT v1.1a) with SMTP id
	<0.759993D0@standards.nortelnetworks.com>; Thu, 20 Apr 2000 9:11:49
	-0400
Received: from zrchb213.us.nortel.com (actually zrchb213) by
	smtprich.nortel.com; Thu, 20 Apr 2000 08:17:16 -0500
Received: by zrchb213.us.nortel.com with Internet Mail Service (5.5.2650.21) id
	<269W4JT1>; Thu, 20 Apr 2000 08:16:09 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFAACA.9725E6E4"
X-Orig: <taylor@americasm01.nt.com>
Message-ID: <C51ED84B6F47D211917A0000F8BCBD1193B6C7@zcard00g.ca.nortel.com>
Date: Thu, 20 Apr 2000 08:16:10 -0500
Reply-To: Tom-PT Taylor <taylor@NORTELNETWORKS.COM>
Sender: "Media Gateway Control (megaco)" <MEGACO@STANDARDS.NORTELNETWORKS.COM>
From: Tom-PT Taylor <taylor@NORTELNETWORKS.COM>
Subject: Re: Event and Signal descriptor on Subtract
X-To: Hemant Agrawal <hemantag@FICON-TECH.COM>
To: MEGACO@STANDARDS.NORTELNETWORKS.COM

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01BFAACA.9725E6E4
Content-Type: text/plain

Based on the E-mail I just put out yesterday, this would be so, but the
default values of these descriptors (in the absence of provisioned
values) would be "empty".

	-----Original Message----- 
From:   Hemant Agrawal [SMTP:hemantag@FICON-TECH.COM] 
Sent:   Thursday, April 20, 2000 6:23 AM 
To:     MEGACO@STANDARDS.NORTELNETWORKS.COM 
Subject:        Event and Signal descriptor on Subtract 

	 Hi Brian, Tom, list, 

	 In ref to section 7.2.3 for Subtract command 
 "When a provisioned Termination is Subtracted from a context, its
property 
 values shall revert to: 
 *    the default value, if specified for the property and not
overridden by 
provisioning, 
 *    otherwise, the provisioned value." 


	  Is this action also valid for signal and event descriptor,
that is, after 
a  termination 
 is subtracted from a context, MG stops playing signals and stop
listening 
for 
 events (since the default value of Event & Signal Descriptor is NULL). 



	 thanks 
 Hemant Agrawal 



	 ________________________________________ 
 Hemant Agrawal 
 Ficon Technology 
 E-mail: hemantag@ficon-tech.com 
 Web: http://www.ficon-tech.com <http://www.ficon-tech.com>  


------_=_NextPart_001_01BFAACA.9725E6E4
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>

<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2651.65">
<TITLE>RE: Event and Signal descriptor on Subtract</TITLE>
</HEAD>
<BODY>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Based on the E-mail =
I just put out yesterday, this would be so, but the default values of =
these descriptors (in the absence of provisioned values) would be =
&quot;empty&quot;.</FONT></P>
<UL>
<P><FONT SIZE=3D1 FACE=3D"Arial">-----Original Message-----</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">From:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Hemant Agrawal =
[SMTP:hemantag@FICON-TECH.COM]</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Thursday, April 20, 2000 6:23 AM</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Arial">MEGACO@STANDARDS.NORTELNETWORKS.COM</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Arial">Event and Signal descriptor on =
Subtract</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;Hi Brian, Tom, list,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;In ref to section 7.2.3 for =
Subtract command</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&quot;When a provisioned =
Termination is Subtracted from a context, its property</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;values shall revert to:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;*&nbsp;&nbsp;&nbsp; the default =
value, if specified for the property and not overridden by</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">provisioning,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;*&nbsp;&nbsp;&nbsp; otherwise, =
the provisioned value.&quot;</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp; Is this action also valid for =
signal and event descriptor, that is, after</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">a&nbsp; termination</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;is subtracted from a context, =
MG stops playing signals and stop listening</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">for</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;events (since the default value =
of Event &amp; Signal Descriptor is NULL).</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;thanks</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;Hemant Agrawal</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;________________________________________</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;Hemant Agrawal</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;Ficon Technology</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;E-mail: =
hemantag@ficon-tech.com</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;Web:<U> </U></FONT><U><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://www.ficon-tech.com" =
TARGET=3D"_blank">http://www.ficon-tech.com</A></FONT></U>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01BFAACA.9725E6E4--


--------------040909080504070701010709
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco

--------------040909080504070701010709--




From megaco-bounces@ietf.org  Mon Dec 20 11:52:38 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15415
	for <megaco-archive@lists.ietf.org>; Mon, 20 Dec 2004 11:52:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgQkm-0007yA-Rf; Mon, 20 Dec 2004 11:51:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgQiz-0007oW-80
	for megaco@megatron.ietf.org; Mon, 20 Dec 2004 11:49:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15283
	for <megaco@ietf.org>; Mon, 20 Dec 2004 11:49:30 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgQs6-0005fP-VD
	for megaco@ietf.org; Mon, 20 Dec 2004 11:59:09 -0500
Received: from wink.ho.lucent.com (h135-112-126-3.lucent.com [135.112.126.3])
	by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id iBKGmmL8025313
	for <megaco@ietf.org>; Mon, 20 Dec 2004 10:48:49 -0600 (CST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id LAA17470; Mon, 20 Dec 2004 11:48:48 -0500 (EST)
Received: from [135.112.108.30] by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id LAA17451; Mon, 20 Dec 2004 11:48:46 -0500 (EST)
Message-ID: <41C704E5.1020009@lucent.com>
Date: Mon, 20 Dec 2004 11:59:17 -0500
From: Richard Sun <xsun@lucent.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Kevin Boyle <kboyle@nortelnetworks.com>
Original-CC: Balasubramanian Pitchandi <bs@utstar.com>,
	"'Marcello Pantaleo (AC/EDD)'" <marcello.pantaleo@ericsson.com>,
	megaco@ietf.org
Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
References: <B258A372CEA20246A363BB86753DB536016DE391@zrtphxm2>
In-Reply-To: <B258A372CEA20246A363BB86753DB536016DE391@zrtphxm2>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 90e8b0e368115979782f8b3d811b226b
Content-Transfer-Encoding: 7bit
Cc: Balasubramanian Pitchandi <bs@utstar.com>,
        "'Marcello Pantaleo \(AC/EDD\)'" <marcello.pantaleo@ericsson.com>,
        megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

 > If the MGC sends $ as the payload list, the MG can
 > return as many payload numbers as it likes,
 > ordered by preference.

So it seems the best way to handle the case is:
When MGC sends "m=audio $ RTP/AVP $",
MG should interpret the 2nd $ as a *list*
of codec it supports. This makes the best
sense to me, just not sure if the 2nd '$' in
"m=" is *allowed* by H248 to be a *list* of
codecs (rather than *choose one* codec).
I guess the answer is yes(?).

I agree that the best way is for MGC to assign the
payload number for 2833, and provides the list of
codecs. This issue is only for MGCs that
do not support it that way, and just expects
MGs to take care SDPs automatically.

Thanks for the helpfull discussion.
-Richard

Kevin Boyle wrote:

> Why would the MGC care if the MG can do 2833?  If it matters, then the MGC
> can explicitly signal it in the Local descriptor by choosing a dynamic
> payload number and including the appropriate rtpmap and associated a line
> parameters.
> 
> If the MGC sends $ as the payload list, the MG can return as many payload
> numbers as it likes, ordered by preference.  So if the MG wishes to include
> 2833 as an option, it would return the info necessary in the SDP along with
> whatever other codecs it may wish to choose.
> 
> If the MGC really NEEDS to know if the MG can do RFC2833 out of band
> signalling of telephony events, then it could try auditing the Local
> descriptor for that information... but the response may be particularly
> unwieldy and difficult to parse for the MGC.
> 
> Kevin 
> 
> -----Original Message-----
> From: Balasubramanian Pitchandi [mailto:bs@utstar.com] 
> Sent: Friday, December 17, 2004 5:52 PM
> To: 'Richard Sun'; Boyle, Kevin [NCRTP:3Z40:EXCH]
> Cc: 'Marcello Pantaleo (AC/EDD)'; megaco@ietf.org
> Subject: RE: [Megaco] how codec negotiation is triggered by MGC?
> 
> I don't think MGC can "assume" that the MG can always do RFC2833. MGC cannot
> predict how an MG would respond to an underspecified SDP
> (including/excluding RFC2833). When interoperating with multiple MGs, you
> want to specifically know if each MG can or cannot do RFC2833.
> 
> I kinda agree with Richard that there's no clear method as to how the MGC
> can learn of MG's ability to do RFC2833 in H.248.
> 
> Bala
>  
> 
> -----Original Message-----
> From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
> Richard Sun
> Sent: Friday, December 17, 2004 3:56 PM
> To: Kevin Boyle
> Cc: Marcello Pantaleo (AC/EDD); megaco@ietf.org
> Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
> 
> Kevin, thanks for the response. See below ...
> 
> 
>>Actually, this is not true.  While MGCP does not send SDP from the CA 
>>to
> 
> the
> 
>>MTA, it *does* send "Local Connection Options" which function in the 
>>same capacity as underspecified Local SDP in H.248 -- to indicate to 
>>the MG the constraints of the SDP it may return.
>> 
>>
> 
> Agree.
> 
> 
>>Now, if the MG wants to always do 2833 and you don't want the MGC to 
>>worry about having to ask the MG to do it, then the MGC could send an 
>>underspecified SDP requesting that the MG choose the codecs.  The MG 
>>can then choose to include a payload number for 2833 if it chooses to do
> 
> so.
> 
>> 
>>
> 
> So it is true that, in any case, MGC needs to do something special to handle
> rfc2833.
> Just want to be clear on "underspecified SDP request":
> 
> If MGC just sends "m=audio $ RTP/AVP 0", it means no rfc2833, right?
> 
> If MGC sends "m=audio $ RTP/AVP $", it means that MG will choose *one*
> codec, say, MG may respond "m=audio 8000 RTP/AVP 0", but how MG responds the
> payload number for RFC2833 if it always wants to support RFC2833? If MGC
> sends m=audio $ RTP/AVP $ a=rtpmap:$ telephone-evemts/8000 then can MG
> responds with m=audio 8000 RTP/AVP 0 101
> a=rtpmap:101 telephone-evemts/8000
> If this the true, then is the last $ in "m=" acturally a list?
> 
> Or should MG respond with
> m=audio 8000 RTP/AVP 0
> a=rtpmap:101 telephone-evemts/8000
> (is this SDP legal?)
> 
> Regards,
> Richard
> 
> 
> 
>>Kevin
>>
>>-----Original Message-----
>>From: Richard Sun [mailto:xsun@lucent.com]
>>Sent: Friday, December 17, 2004 2:17 PM
>>To: Boyle, Kevin [NCRTP:3Z40:EXCH]
>>Cc: Marcello Pantaleo (AC/EDD); megaco@ietf.org
>>Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
>>
>>Kevin,
>>Thanks for the reply.
>>
>>
>>>Why not just have the MGC choose the payload number for  > the 2833
>>
>>events?
>>
>>Good question. That was what I asked. But some MGC implementation says 
>>that MGC does not care rfc2833 and its payload type at all, MGC just 
>>expects MG to turn on rfc2833 automatically. I thought this is not 
>>possible, so I
> 
> asked
> 
>>the question just to make sure that I do not miss anything.
>>
>>To put it another way:
>>does it make any sense for any MGC to say:
>>"MGC never needs to look at the SDP contents, it just pass SDP among MGs.
>>MGs should just handle the codec negotiation themself"?
>>
>>This is indeed possible with MGCP. But it seems that this is really not 
>>possibile with H248.
>>For H248, MGC always needs to be involved in this codec negotiation.
>>
>>Let me know if I am wrong. Thanks,
>>-Richard
>>
>>
>>Kevin Boyle wrote:
>>
>> 
>>
>>
>>>Why not just have the MGC choose the payload number for the 2833 events?
>>>
>>>Note that the m line example here restricts the payload selectors to 
>>>those defined as RTP/AVP.  This can be avoided by using $ for that 
>>>element as well.
>>>
>>>To confirm Marcello's statement, '*' is not a permitted wildcard in 
>>>underspecified SDP.  '$' is allowed in any position and means choose.
>>>Note that the use of wildcards is only allowed in the MGC->MG 
>>>direction.  MGs are always expected to send compliant SDP.
>>>
>>>Kevin
>>>
>>>-----Original Message-----
>>>From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On 
>>>Behalf Of Richard Sun
>>>Sent: Friday, December 17, 2004 12:39 PM
>>>To: Marcello Pantaleo (AC/EDD)
>>>Cc: megaco@ietf.org
>>>Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
>>>
>>>Marcello,
>>>Thanks for your helpfull information.
>>>
>>>Now assume that MGC audits MG and learns that MG supports "PCMU" *and* 
>>>"telephone-event".
>>>If "m=audio $ RTP/AVP $" means that
>>>MG to choose *one* codec, then
>>>what is the syntax for MGC to instruct MG "use PCMU, *and* choose a 
>>>payload number for telephone-event"?
>>>
>>>-Richard
>>>
>>>Marcello Pantaleo (AC/EDD) wrote:
>>>
>>>
>>>>Hi,
>>>>
>>>>MGC can use audit capabilities to get the list of codecs supported
>>>
>>>by a MG. Alternatively a MGC can be provisioned with MG capabilities.
>>>
>>>
>>>>MGC wouldn't use Add to know MG capabilities (e.g. supported codecs).
>>>>
>>>>If MGC sends an Add command with an empty local desciptor, this is
>>>
>>>a request to release any resources previously reserved for the media 
>>>flow received, that means nothing given that MGC is now creating the
>>>   
>>>
>>
>>termination.
>> 
>>
>>
>>>>If local descriptor is unspecified (i.e. absent), MG considers this
>>>
>>>as missing mandatory parameter. MG uses whatever previously specified.
>>>
>>>
>>>>If MGC sends "m=audio $ RTP/AVP $" it requests MG to choose one of
>>>
>>>the supported codecs, so you don't get the list.
>>>
>>>>I don't think you can use * wildcard in the "m=".
>>>>
>>>>Regards,
>>>>Marcello
>>>>
>>>>-----Original Message-----
>>>>From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]On
>>>>Behalf Of Richard Sun
>>>>Sent: Thursday, December 16, 2004 3:08 PM  > To: megaco@ietf.org  >
>>>
>>>Subject: [Megaco] how codec negotiation is triggered by MGC?
>>>
>>>>
>>>>Hi, Can anyone pelase clarify the standard for MGC to trigger a
>>>
>>>codec  > negotiation in MG (i.e, MG should provide a list of codecs it
>>>   
>>>
>>>
>>>>supports)?
>>>>     
>>>>
>>>>
>>>>One way I can think of is an empty "Local{}"
>>>>without SDP, such as:
>>>>Transaction = 299012 {
>>>>  Context = $ {
>>>>    Add = aaln/1 {
>>>>      Media { Stream = 1 {
>>>>        LocalControl {Mode = SendReceive}
>>>>    }}},
>>>>    Add = $ {
>>>>      Media {Stream = 1 {
>>>>        LocalControl {Mode=ReceiveOnly},
>>>>        Local {}
>>>>}}}}}
>>>>
>>>>The question is: is this legal? Should MG reject the message with
>>>
>>>some  > kind of error such as "SDP missing", or MG is suppose to fill 
>>>up the  > SDP section in response?
>>>
>>>>What if the "Local{}" does not present at all?
>>>>
>>>>The other way is something like this:
>>>>Transaction = 299012 {
>>>>  Context = $ {
>>>>    Add = aaln/1 {
>>>>      Media { Stream = 1 {
>>>>        LocalControl {Mode = SendReceive}
>>>>    }}},
>>>>    Add = $ {
>>>>      Media {Stream = 1 {
>>>>        LocalControl {Mode=ReceiveOnly},
>>>>        Local {
>>>>v=0
>>>>o=$ $ $ IN IP4 $
>>>>s=$
>>>>c=IN IP4 $
>>>>t=$ $
>>>>m=audio $ RTP/AVP -
>>>>a=ptime:20
>>>>}}}}}}
>>>>With "-" in "m=audio $ RTP/AVP -", should MG fill up the list of  >
>>>
>>>codecs?
>>>
>>>>Or should it be something like
>>>>"m=audio $ RTP/AVP $"?
>>>>
>>>>Thanks for any information.
>>>>-Richard
>>>>
>>>>_______________________________________________
>>>>Megaco mailing list
>>>>Megaco@ietf.org
>>>>https://www1.ietf.org/mailman/listinfo/megaco
>>>
>>>_______________________________________________
>>>Megaco mailing list
>>>Megaco@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/megaco
>>>
>>>   
>>>
>>
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>> 
>>
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Mon Dec 20 12:36:36 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18208
	for <megaco-archive@lists.ietf.org>; Mon, 20 Dec 2004 12:36:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgRPq-0002vT-7q; Mon, 20 Dec 2004 12:33:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgRM4-0001zW-GZ
	for megaco@megatron.ietf.org; Mon, 20 Dec 2004 12:29:56 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17803
	for <megaco@ietf.org>; Mon, 20 Dec 2004 12:29:53 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgRVJ-0006dS-Pw
	for megaco@ietf.org; Mon, 20 Dec 2004 12:39:33 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iBKHTGu29157
	for <megaco@ietf.org>; Mon, 20 Dec 2004 12:29:16 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Y0S9FPDS>; Mon, 20 Dec 2004 12:29:17 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536016DEA7F@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Richard Sun <xsun@lucent.com>
Subject: RE: [Megaco] how codec negotiation is triggered by MGC?
Date: Mon, 20 Dec 2004 12:29:10 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fec852dbea6d068499ed3250edf328e2
Cc: Balasubramanian Pitchandi <bs@utstar.com>,
        "'Marcello Pantaleo \(AC/EDD\)'" <marcello.pantaleo@ericsson.com>,
        megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

'$' means "choose" -- not necessarily "choose one".  In some instances, like
termIDs, it doesn't make sense to choose more than one.  But there is no
limitation in the spec to make '$' mean "choose one and only one".

Kevin

-----Original Message-----
From: Richard Sun [mailto:xsun@lucent.com] 
Sent: Monday, December 20, 2004 11:59 AM
To: Boyle, Kevin [NCRTP:3Z40:EXCH]
Cc: Balasubramanian Pitchandi; 'Marcello Pantaleo (AC/EDD)'; megaco@ietf.org
Subject: Re: [Megaco] how codec negotiation is triggered by MGC?

 > If the MGC sends $ as the payload list, the MG can  > return as many
payload numbers as it likes,  > ordered by preference.

So it seems the best way to handle the case is:
When MGC sends "m=audio $ RTP/AVP $",
MG should interpret the 2nd $ as a *list* of codec it supports. This makes
the best sense to me, just not sure if the 2nd '$' in "m=" is *allowed* by
H248 to be a *list* of codecs (rather than *choose one* codec).
I guess the answer is yes(?).

I agree that the best way is for MGC to assign the payload number for 2833,
and provides the list of codecs. This issue is only for MGCs that do not
support it that way, and just expects MGs to take care SDPs automatically.

Thanks for the helpfull discussion.
-Richard

Kevin Boyle wrote:

> Why would the MGC care if the MG can do 2833?  If it matters, then the 
> MGC can explicitly signal it in the Local descriptor by choosing a 
> dynamic payload number and including the appropriate rtpmap and 
> associated a line parameters.
> 
> If the MGC sends $ as the payload list, the MG can return as many 
> payload numbers as it likes, ordered by preference.  So if the MG 
> wishes to include
> 2833 as an option, it would return the info necessary in the SDP along 
> with whatever other codecs it may wish to choose.
> 
> If the MGC really NEEDS to know if the MG can do RFC2833 out of band 
> signalling of telephony events, then it could try auditing the Local 
> descriptor for that information... but the response may be 
> particularly unwieldy and difficult to parse for the MGC.
> 
> Kevin
> 
> -----Original Message-----
> From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
> Sent: Friday, December 17, 2004 5:52 PM
> To: 'Richard Sun'; Boyle, Kevin [NCRTP:3Z40:EXCH]
> Cc: 'Marcello Pantaleo (AC/EDD)'; megaco@ietf.org
> Subject: RE: [Megaco] how codec negotiation is triggered by MGC?
> 
> I don't think MGC can "assume" that the MG can always do RFC2833. MGC 
> cannot predict how an MG would respond to an underspecified SDP 
> (including/excluding RFC2833). When interoperating with multiple MGs, 
> you want to specifically know if each MG can or cannot do RFC2833.
> 
> I kinda agree with Richard that there's no clear method as to how the 
> MGC can learn of MG's ability to do RFC2833 in H.248.
> 
> Bala
>  
> 
> -----Original Message-----
> From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On 
> Behalf Of Richard Sun
> Sent: Friday, December 17, 2004 3:56 PM
> To: Kevin Boyle
> Cc: Marcello Pantaleo (AC/EDD); megaco@ietf.org
> Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
> 
> Kevin, thanks for the response. See below ...
> 
> 
>>Actually, this is not true.  While MGCP does not send SDP from the CA 
>>to
> 
> the
> 
>>MTA, it *does* send "Local Connection Options" which function in the 
>>same capacity as underspecified Local SDP in H.248 -- to indicate to 
>>the MG the constraints of the SDP it may return.
>> 
>>
> 
> Agree.
> 
> 
>>Now, if the MG wants to always do 2833 and you don't want the MGC to 
>>worry about having to ask the MG to do it, then the MGC could send an 
>>underspecified SDP requesting that the MG choose the codecs.  The MG 
>>can then choose to include a payload number for 2833 if it chooses to 
>>do
> 
> so.
> 
>> 
>>
> 
> So it is true that, in any case, MGC needs to do something special to 
> handle rfc2833.
> Just want to be clear on "underspecified SDP request":
> 
> If MGC just sends "m=audio $ RTP/AVP 0", it means no rfc2833, right?
> 
> If MGC sends "m=audio $ RTP/AVP $", it means that MG will choose *one* 
> codec, say, MG may respond "m=audio 8000 RTP/AVP 0", but how MG 
> responds the payload number for RFC2833 if it always wants to support 
> RFC2833? If MGC sends m=audio $ RTP/AVP $ a=rtpmap:$ 
> telephone-evemts/8000 then can MG responds with m=audio 8000 RTP/AVP 0 
> 101
> a=rtpmap:101 telephone-evemts/8000
> If this the true, then is the last $ in "m=" acturally a list?
> 
> Or should MG respond with
> m=audio 8000 RTP/AVP 0
> a=rtpmap:101 telephone-evemts/8000
> (is this SDP legal?)
> 
> Regards,
> Richard
> 
> 
> 
>>Kevin
>>
>>-----Original Message-----
>>From: Richard Sun [mailto:xsun@lucent.com]
>>Sent: Friday, December 17, 2004 2:17 PM
>>To: Boyle, Kevin [NCRTP:3Z40:EXCH]
>>Cc: Marcello Pantaleo (AC/EDD); megaco@ietf.org
>>Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
>>
>>Kevin,
>>Thanks for the reply.
>>
>>
>>>Why not just have the MGC choose the payload number for  > the 2833
>>
>>events?
>>
>>Good question. That was what I asked. But some MGC implementation says 
>>that MGC does not care rfc2833 and its payload type at all, MGC just 
>>expects MG to turn on rfc2833 automatically. I thought this is not 
>>possible, so I
> 
> asked
> 
>>the question just to make sure that I do not miss anything.
>>
>>To put it another way:
>>does it make any sense for any MGC to say:
>>"MGC never needs to look at the SDP contents, it just pass SDP among MGs.
>>MGs should just handle the codec negotiation themself"?
>>
>>This is indeed possible with MGCP. But it seems that this is really 
>>not possibile with H248.
>>For H248, MGC always needs to be involved in this codec negotiation.
>>
>>Let me know if I am wrong. Thanks,
>>-Richard
>>
>>
>>Kevin Boyle wrote:
>>
>> 
>>
>>
>>>Why not just have the MGC choose the payload number for the 2833 events?
>>>
>>>Note that the m line example here restricts the payload selectors to 
>>>those defined as RTP/AVP.  This can be avoided by using $ for that 
>>>element as well.
>>>
>>>To confirm Marcello's statement, '*' is not a permitted wildcard in 
>>>underspecified SDP.  '$' is allowed in any position and means choose.
>>>Note that the use of wildcards is only allowed in the MGC->MG 
>>>direction.  MGs are always expected to send compliant SDP.
>>>
>>>Kevin
>>>
>>>-----Original Message-----
>>>From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On 
>>>Behalf Of Richard Sun
>>>Sent: Friday, December 17, 2004 12:39 PM
>>>To: Marcello Pantaleo (AC/EDD)
>>>Cc: megaco@ietf.org
>>>Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
>>>
>>>Marcello,
>>>Thanks for your helpfull information.
>>>
>>>Now assume that MGC audits MG and learns that MG supports "PCMU" 
>>>*and* "telephone-event".
>>>If "m=audio $ RTP/AVP $" means that
>>>MG to choose *one* codec, then
>>>what is the syntax for MGC to instruct MG "use PCMU, *and* choose a 
>>>payload number for telephone-event"?
>>>
>>>-Richard
>>>
>>>Marcello Pantaleo (AC/EDD) wrote:
>>>
>>>
>>>>Hi,
>>>>
>>>>MGC can use audit capabilities to get the list of codecs supported
>>>
>>>by a MG. Alternatively a MGC can be provisioned with MG capabilities.
>>>
>>>
>>>>MGC wouldn't use Add to know MG capabilities (e.g. supported codecs).
>>>>
>>>>If MGC sends an Add command with an empty local desciptor, this is
>>>
>>>a request to release any resources previously reserved for the media 
>>>flow received, that means nothing given that MGC is now creating the
>>>   
>>>
>>
>>termination.
>> 
>>
>>
>>>>If local descriptor is unspecified (i.e. absent), MG considers this
>>>
>>>as missing mandatory parameter. MG uses whatever previously specified.
>>>
>>>
>>>>If MGC sends "m=audio $ RTP/AVP $" it requests MG to choose one of
>>>
>>>the supported codecs, so you don't get the list.
>>>
>>>>I don't think you can use * wildcard in the "m=".
>>>>
>>>>Regards,
>>>>Marcello
>>>>
>>>>-----Original Message-----
>>>>From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]On
>>>>Behalf Of Richard Sun
>>>>Sent: Thursday, December 16, 2004 3:08 PM  > To: megaco@ietf.org  >
>>>
>>>Subject: [Megaco] how codec negotiation is triggered by MGC?
>>>
>>>>
>>>>Hi, Can anyone pelase clarify the standard for MGC to trigger a
>>>
>>>codec  > negotiation in MG (i.e, MG should provide a list of codecs 
>>>it
>>>   
>>>
>>>
>>>>supports)?
>>>>     
>>>>
>>>>
>>>>One way I can think of is an empty "Local{}"
>>>>without SDP, such as:
>>>>Transaction = 299012 {
>>>>  Context = $ {
>>>>    Add = aaln/1 {
>>>>      Media { Stream = 1 {
>>>>        LocalControl {Mode = SendReceive}
>>>>    }}},
>>>>    Add = $ {
>>>>      Media {Stream = 1 {
>>>>        LocalControl {Mode=ReceiveOnly},
>>>>        Local {}
>>>>}}}}}
>>>>
>>>>The question is: is this legal? Should MG reject the message with
>>>
>>>some  > kind of error such as "SDP missing", or MG is suppose to fill 
>>>up the  > SDP section in response?
>>>
>>>>What if the "Local{}" does not present at all?
>>>>
>>>>The other way is something like this:
>>>>Transaction = 299012 {
>>>>  Context = $ {
>>>>    Add = aaln/1 {
>>>>      Media { Stream = 1 {
>>>>        LocalControl {Mode = SendReceive}
>>>>    }}},
>>>>    Add = $ {
>>>>      Media {Stream = 1 {
>>>>        LocalControl {Mode=ReceiveOnly},
>>>>        Local {
>>>>v=0
>>>>o=$ $ $ IN IP4 $
>>>>s=$
>>>>c=IN IP4 $
>>>>t=$ $
>>>>m=audio $ RTP/AVP -
>>>>a=ptime:20
>>>>}}}}}}
>>>>With "-" in "m=audio $ RTP/AVP -", should MG fill up the list of  >
>>>
>>>codecs?
>>>
>>>>Or should it be something like
>>>>"m=audio $ RTP/AVP $"?
>>>>
>>>>Thanks for any information.
>>>>-Richard
>>>>
>>>>_______________________________________________
>>>>Megaco mailing list
>>>>Megaco@ietf.org
>>>>https://www1.ietf.org/mailman/listinfo/megaco
>>>
>>>_______________________________________________
>>>Megaco mailing list
>>>Megaco@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/megaco
>>>
>>>   
>>>
>>
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>> 
>>
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Mon Dec 20 17:31:47 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19599
	for <megaco-archive@lists.ietf.org>; Mon, 20 Dec 2004 17:31:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgW1z-0007Rt-TN; Mon, 20 Dec 2004 17:29:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgVyQ-0006Xy-Hb
	for megaco@megatron.ietf.org; Mon, 20 Dec 2004 17:25:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19005
	for <megaco@ietf.org>; Mon, 20 Dec 2004 17:25:47 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgW7k-00088n-OV
	for megaco@ietf.org; Mon, 20 Dec 2004 17:35:29 -0500
Received: from esealmw126.eemea.ericsson.se ([153.88.254.123])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBKMPTO6012059; Mon, 20 Dec 2004 23:25:40 +0100
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 20 Dec 2004 23:25:29 +0100
Received: from eaubrnt019.epa.ericsson.se ([146.11.9.165]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 20 Dec 2004 23:25:28 +0100
Received: from ericsson.com (EG2E500202DSEGL [146.11.22.104]) by
	eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id Y0DJ9C5Y; Tue, 21 Dec 2004 09:25:23 +1100
Message-ID: <41C75176.2090007@ericsson.com>
Date: Tue, 21 Dec 2004 09:25:58 +1100
X-Sybari-Trust: 913219cf 9db1dfa1 62357d84 00000139
From: Christian Groves <christian.groves@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Kevin Boyle <kboyle@nortelnetworks.com>
Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
References: <B258A372CEA20246A363BB86753DB536016DEA7F@zrtphxm2>
In-Reply-To: <B258A372CEA20246A363BB86753DB536016DEA7F@zrtphxm2>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Dec 2004 22:25:28.0767 (UTC)
	FILETIME=[CF45C4F0:01C4E6E2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: abb8110dde048486ea2be9c769692569
Content-Transfer-Encoding: 7bit
Cc: Balasubramanian Pitchandi <bs@utstar.com>,
        "'Marcello Pantaleo \(AC/EDD\)'" <marcello.pantaleo@ericsson.com>,
        megaco@ietf.org, Richard Sun <xsun@lucent.com>
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

G'Day Kevin,

This is not entirely  true.

In the case of termID you must return only one. From 6.2.2, "A wildcarding 
mechanism using two types of wildcards can be used with TerminationIDs. The two 
wildcards are ALL and CHOOSE. The former is used to address multiple 
Terminations at once, while the latter is used to indicate to a media gateway 
that it must select a Termination satisfying the partially specified 
TerminationID."

So clearly it says CHOOSE "A" termination not several.

With regards to CHOOSE, there is an interaction with the Reserve Group and 
Reserve Value parameters. See for example: 7.1.7 LocalControl descriptor, "...If 
the value of a Reserve property is False, the MG SHALL choose one of the 
alternatives specified in the Local descriptor (if present) and one of the 
alternatives specified in the Remote descriptor (if present)."

I don't believe the other instances in the spec talk about return a list or 
multiple values, they talk about choosing from a list of supported values.

Regards, Christian

Kevin Boyle wrote:
> '$' means "choose" -- not necessarily "choose one".  In some instances, like
> termIDs, it doesn't make sense to choose more than one.  But there is no
> limitation in the spec to make '$' mean "choose one and only one".
> 
> Kevin
> 
> -----Original Message-----
> From: Richard Sun [mailto:xsun@lucent.com] 
> Sent: Monday, December 20, 2004 11:59 AM
> To: Boyle, Kevin [NCRTP:3Z40:EXCH]
> Cc: Balasubramanian Pitchandi; 'Marcello Pantaleo (AC/EDD)'; megaco@ietf.org
> Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
> 
>  > If the MGC sends $ as the payload list, the MG can  > return as many
> payload numbers as it likes,  > ordered by preference.
> 
> So it seems the best way to handle the case is:
> When MGC sends "m=audio $ RTP/AVP $",
> MG should interpret the 2nd $ as a *list* of codec it supports. This makes
> the best sense to me, just not sure if the 2nd '$' in "m=" is *allowed* by
> H248 to be a *list* of codecs (rather than *choose one* codec).
> I guess the answer is yes(?).
> 
> I agree that the best way is for MGC to assign the payload number for 2833,
> and provides the list of codecs. This issue is only for MGCs that do not
> support it that way, and just expects MGs to take care SDPs automatically.
> 
> Thanks for the helpfull discussion.
> -Richard
> 
> Kevin Boyle wrote:
> 
> 
>>Why would the MGC care if the MG can do 2833?  If it matters, then the 
>>MGC can explicitly signal it in the Local descriptor by choosing a 
>>dynamic payload number and including the appropriate rtpmap and 
>>associated a line parameters.
>>
>>If the MGC sends $ as the payload list, the MG can return as many 
>>payload numbers as it likes, ordered by preference.  So if the MG 
>>wishes to include
>>2833 as an option, it would return the info necessary in the SDP along 
>>with whatever other codecs it may wish to choose.
>>
>>If the MGC really NEEDS to know if the MG can do RFC2833 out of band 
>>signalling of telephony events, then it could try auditing the Local 
>>descriptor for that information... but the response may be 
>>particularly unwieldy and difficult to parse for the MGC.
>>
>>Kevin
>>
>>-----Original Message-----
>>From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
>>Sent: Friday, December 17, 2004 5:52 PM
>>To: 'Richard Sun'; Boyle, Kevin [NCRTP:3Z40:EXCH]
>>Cc: 'Marcello Pantaleo (AC/EDD)'; megaco@ietf.org
>>Subject: RE: [Megaco] how codec negotiation is triggered by MGC?
>>
>>I don't think MGC can "assume" that the MG can always do RFC2833. MGC 
>>cannot predict how an MG would respond to an underspecified SDP 
>>(including/excluding RFC2833). When interoperating with multiple MGs, 
>>you want to specifically know if each MG can or cannot do RFC2833.
>>
>>I kinda agree with Richard that there's no clear method as to how the 
>>MGC can learn of MG's ability to do RFC2833 in H.248.
>>
>>Bala
>> 
>>
>>-----Original Message-----
>>From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On 
>>Behalf Of Richard Sun
>>Sent: Friday, December 17, 2004 3:56 PM
>>To: Kevin Boyle
>>Cc: Marcello Pantaleo (AC/EDD); megaco@ietf.org
>>Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
>>
>>Kevin, thanks for the response. See below ...
>>
>>
>>
>>>Actually, this is not true.  While MGCP does not send SDP from the CA 
>>>to
>>
>>the
>>
>>
>>>MTA, it *does* send "Local Connection Options" which function in the 
>>>same capacity as underspecified Local SDP in H.248 -- to indicate to 
>>>the MG the constraints of the SDP it may return.
>>>
>>>
>>
>>Agree.
>>
>>
>>
>>>Now, if the MG wants to always do 2833 and you don't want the MGC to 
>>>worry about having to ask the MG to do it, then the MGC could send an 
>>>underspecified SDP requesting that the MG choose the codecs.  The MG 
>>>can then choose to include a payload number for 2833 if it chooses to 
>>>do
>>
>>so.
>>
>>
>>>
>>So it is true that, in any case, MGC needs to do something special to 
>>handle rfc2833.
>>Just want to be clear on "underspecified SDP request":
>>
>>If MGC just sends "m=audio $ RTP/AVP 0", it means no rfc2833, right?
>>
>>If MGC sends "m=audio $ RTP/AVP $", it means that MG will choose *one* 
>>codec, say, MG may respond "m=audio 8000 RTP/AVP 0", but how MG 
>>responds the payload number for RFC2833 if it always wants to support 
>>RFC2833? If MGC sends m=audio $ RTP/AVP $ a=rtpmap:$ 
>>telephone-evemts/8000 then can MG responds with m=audio 8000 RTP/AVP 0 
>>101
>>a=rtpmap:101 telephone-evemts/8000
>>If this the true, then is the last $ in "m=" acturally a list?
>>
>>Or should MG respond with
>>m=audio 8000 RTP/AVP 0
>>a=rtpmap:101 telephone-evemts/8000
>>(is this SDP legal?)
>>
>>Regards,
>>Richard
>>
>>
>>
>>
>>>Kevin
>>>
>>>-----Original Message-----
>>>From: Richard Sun [mailto:xsun@lucent.com]
>>>Sent: Friday, December 17, 2004 2:17 PM
>>>To: Boyle, Kevin [NCRTP:3Z40:EXCH]
>>>Cc: Marcello Pantaleo (AC/EDD); megaco@ietf.org
>>>Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
>>>
>>>Kevin,
>>>Thanks for the reply.
>>>
>>>
>>>
>>>>Why not just have the MGC choose the payload number for  > the 2833
>>>
>>>events?
>>>
>>>Good question. That was what I asked. But some MGC implementation says 
>>>that MGC does not care rfc2833 and its payload type at all, MGC just 
>>>expects MG to turn on rfc2833 automatically. I thought this is not 
>>>possible, so I
>>
>>asked
>>
>>
>>>the question just to make sure that I do not miss anything.
>>>
>>>To put it another way:
>>>does it make any sense for any MGC to say:
>>>"MGC never needs to look at the SDP contents, it just pass SDP among MGs.
>>>MGs should just handle the codec negotiation themself"?
>>>
>>>This is indeed possible with MGCP. But it seems that this is really 
>>>not possibile with H248.
>>>For H248, MGC always needs to be involved in this codec negotiation.
>>>
>>>Let me know if I am wrong. Thanks,
>>>-Richard
>>>
>>>
>>>Kevin Boyle wrote:
>>>
>>>
>>>
>>>
>>>
>>>>Why not just have the MGC choose the payload number for the 2833 events?
>>>>
>>>>Note that the m line example here restricts the payload selectors to 
>>>>those defined as RTP/AVP.  This can be avoided by using $ for that 
>>>>element as well.
>>>>
>>>>To confirm Marcello's statement, '*' is not a permitted wildcard in 
>>>>underspecified SDP.  '$' is allowed in any position and means choose.
>>>>Note that the use of wildcards is only allowed in the MGC->MG 
>>>>direction.  MGs are always expected to send compliant SDP.
>>>>
>>>>Kevin
>>>>
>>>>-----Original Message-----
>>>>From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On 
>>>>Behalf Of Richard Sun
>>>>Sent: Friday, December 17, 2004 12:39 PM
>>>>To: Marcello Pantaleo (AC/EDD)
>>>>Cc: megaco@ietf.org
>>>>Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
>>>>
>>>>Marcello,
>>>>Thanks for your helpfull information.
>>>>
>>>>Now assume that MGC audits MG and learns that MG supports "PCMU" 
>>>>*and* "telephone-event".
>>>>If "m=audio $ RTP/AVP $" means that
>>>>MG to choose *one* codec, then
>>>>what is the syntax for MGC to instruct MG "use PCMU, *and* choose a 
>>>>payload number for telephone-event"?
>>>>
>>>>-Richard
>>>>
>>>>Marcello Pantaleo (AC/EDD) wrote:
>>>>
>>>>
>>>>
>>>>>Hi,
>>>>>
>>>>>MGC can use audit capabilities to get the list of codecs supported
>>>>
>>>>by a MG. Alternatively a MGC can be provisioned with MG capabilities.
>>>>
>>>>
>>>>
>>>>>MGC wouldn't use Add to know MG capabilities (e.g. supported codecs).
>>>>>
>>>>>If MGC sends an Add command with an empty local desciptor, this is
>>>>
>>>>a request to release any resources previously reserved for the media 
>>>>flow received, that means nothing given that MGC is now creating the
>>>>  
>>>>
>>>
>>>termination.
>>>
>>>
>>>
>>>
>>>>>If local descriptor is unspecified (i.e. absent), MG considers this
>>>>
>>>>as missing mandatory parameter. MG uses whatever previously specified.
>>>>
>>>>
>>>>
>>>>>If MGC sends "m=audio $ RTP/AVP $" it requests MG to choose one of
>>>>
>>>>the supported codecs, so you don't get the list.
>>>>
>>>>
>>>>>I don't think you can use * wildcard in the "m=".
>>>>>
>>>>>Regards,
>>>>>Marcello
>>>>>
>>>>>-----Original Message-----
>>>>>From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]On
>>>>>Behalf Of Richard Sun
>>>>>Sent: Thursday, December 16, 2004 3:08 PM  > To: megaco@ietf.org  >
>>>>
>>>>Subject: [Megaco] how codec negotiation is triggered by MGC?
>>>>
>>>>
>>>>>Hi, Can anyone pelase clarify the standard for MGC to trigger a
>>>>
>>>>codec  > negotiation in MG (i.e, MG should provide a list of codecs 
>>>>it
>>>>  
>>>>
>>>>
>>>>
>>>>>supports)?
>>>>>    
>>>>>
>>>>>
>>>>>One way I can think of is an empty "Local{}"
>>>>>without SDP, such as:
>>>>>Transaction = 299012 {
>>>>> Context = $ {
>>>>>   Add = aaln/1 {
>>>>>     Media { Stream = 1 {
>>>>>       LocalControl {Mode = SendReceive}
>>>>>   }}},
>>>>>   Add = $ {
>>>>>     Media {Stream = 1 {
>>>>>       LocalControl {Mode=ReceiveOnly},
>>>>>       Local {}
>>>>>}}}}}
>>>>>
>>>>>The question is: is this legal? Should MG reject the message with
>>>>
>>>>some  > kind of error such as "SDP missing", or MG is suppose to fill 
>>>>up the  > SDP section in response?
>>>>
>>>>
>>>>>What if the "Local{}" does not present at all?
>>>>>
>>>>>The other way is something like this:
>>>>>Transaction = 299012 {
>>>>> Context = $ {
>>>>>   Add = aaln/1 {
>>>>>     Media { Stream = 1 {
>>>>>       LocalControl {Mode = SendReceive}
>>>>>   }}},
>>>>>   Add = $ {
>>>>>     Media {Stream = 1 {
>>>>>       LocalControl {Mode=ReceiveOnly},
>>>>>       Local {
>>>>>v=0
>>>>>o=$ $ $ IN IP4 $
>>>>>s=$
>>>>>c=IN IP4 $
>>>>>t=$ $
>>>>>m=audio $ RTP/AVP -
>>>>>a=ptime:20
>>>>>}}}}}}
>>>>>With "-" in "m=audio $ RTP/AVP -", should MG fill up the list of  >
>>>>
>>>>codecs?
>>>>
>>>>
>>>>>Or should it be something like
>>>>>"m=audio $ RTP/AVP $"?
>>>>>
>>>>>Thanks for any information.
>>>>>-Richard
>>>>>
>>>>>_______________________________________________
>>>>>Megaco mailing list
>>>>>Megaco@ietf.org
>>>>>https://www1.ietf.org/mailman/listinfo/megaco
>>>>
>>>>_______________________________________________
>>>>Megaco mailing list
>>>>Megaco@ietf.org
>>>>https://www1.ietf.org/mailman/listinfo/megaco
>>>>
>>>>  
>>>>
>>>
>>>
>>>_______________________________________________
>>>Megaco mailing list
>>>Megaco@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/megaco
>>>
>>>
>>
>>
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>>
>>
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Tue Dec 21 10:30:56 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19900
	for <megaco-archive@lists.ietf.org>; Tue, 21 Dec 2004 10:30:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CglsS-0007wF-4j; Tue, 21 Dec 2004 10:24:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgWmP-0005ed-IH
	for megaco@megatron.ietf.org; Mon, 20 Dec 2004 18:17:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23933
	for <megaco@ietf.org>; Mon, 20 Dec 2004 18:17:26 -0500 (EST)
Received: from mail.utstar.com ([216.37.114.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgWvf-0000ze-98
	for megaco@ietf.org; Mon, 20 Dec 2004 18:27:09 -0500
Received: from balanew (balanew.nj.us.utstar.com [172.16.41.57])
	by mail.utstar.com (8.12.10/8.12.10) with ESMTP id iBKNH6BL027833;
	Mon, 20 Dec 2004 18:17:07 -0500 (EST)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'Kevin Boyle'" <kboyle@nortelnetworks.com>,
        "'Richard Sun'" <xsun@lucent.com>
Subject: RE: [Megaco] how codec negotiation is triggered by MGC?
Date: Mon, 20 Dec 2004 18:17:04 -0500
Message-ID: <000001c4e6ea$0a9c55d0$392910ac@nj.us.utstar.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
In-Reply-To: <B258A372CEA20246A363BB86753DB536016DE391@zrtphxm2>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 772a6990a160cebc49b9e3d175956d12
X-Mailman-Approved-At: Tue, 21 Dec 2004 10:24:42 -0500
Cc: "'Marcello Pantaleo \(AC/EDD\)'" <marcello.pantaleo@ericsson.com>,
        megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0940371666=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0940371666==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0001_01C4E6C0.21C64DD0"

This is a multi-part message in MIME format.

------=_NextPart_000_0001_01C4E6C0.21C64DD0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The MGC would like to know if the MGs can (or cannot) do RFC2833 =
because,
while controlling two participating MGs, it needs to know the =
capabilities
of both when sending media parameters to both. It can explicitly specify =
it
in the Local Descriptor as you have said, but in that case that Add =
command
would get fail if that MG does not support RFC2833 (and the exact reason =
why
the add command (inability to support RFC2833) would not be clear from =
the
error response) in which case the call would not be established.

=20

Bala

=20

-----Original Message-----
From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]=20
Sent: Friday, December 17, 2004 11:15 PM
To: Balasubramanian Pitchandi; 'Richard Sun'
Cc: 'Marcello Pantaleo (AC/EDD)'; megaco@ietf.org
Subject: RE: [Megaco] how codec negotiation is triggered by MGC?

=20

Why would the MGC care if the MG can do 2833?  If it matters, then the =
MGC
can explicitly signal it in the Local descriptor by choosing a dynamic
payload number and including the appropriate rtpmap and associated a =
line
parameters.

If the MGC sends $ as the payload list, the MG can return as many =
payload
numbers as it likes, ordered by preference.  So if the MG wishes to =
include
2833 as an option, it would return the info necessary in the SDP along =
with
whatever other codecs it may wish to choose.

If the MGC really NEEDS to know if the MG can do RFC2833 out of band
signalling of telephony events, then it could try auditing the Local
descriptor for that information... but the response may be particularly
unwieldy and difficult to parse for the MGC.

Kevin=20

-----Original Message-----=20
From: Balasubramanian Pitchandi [mailto:bs@utstar.com]=20
Sent: Friday, December 17, 2004 5:52 PM=20
To: 'Richard Sun'; Boyle, Kevin [NCRTP:3Z40:EXCH]=20
Cc: 'Marcello Pantaleo (AC/EDD)'; megaco@ietf.org=20
Subject: RE: [Megaco] how codec negotiation is triggered by MGC?=20

I don't think MGC can "assume" that the MG can always do RFC2833. MGC =
cannot
predict how an MG would respond to an underspecified SDP
(including/excluding RFC2833). When interoperating with multiple MGs, =
you
want to specifically know if each MG can or cannot do RFC2833.

I kinda agree with Richard that there's no clear method as to how the =
MGC
can learn of MG's ability to do RFC2833 in H.248.

Bala=20
 =20

-----Original Message-----=20
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf =
Of
Richard Sun=20
Sent: Friday, December 17, 2004 3:56 PM=20
To: Kevin Boyle=20
Cc: Marcello Pantaleo (AC/EDD); megaco@ietf.org=20
Subject: Re: [Megaco] how codec negotiation is triggered by MGC?=20

Kevin, thanks for the response. See below ...=20

>Actually, this is not true.  While MGCP does not send SDP from the CA=20
>to=20
the=20
>MTA, it *does* send "Local Connection Options" which function in the=20
>same capacity as underspecified Local SDP in H.248 -- to indicate to=20
>the MG the constraints of the SDP it may return.=20
> =20
>=20
Agree.=20

>Now, if the MG wants to always do 2833 and you don't want the MGC to=20
>worry about having to ask the MG to do it, then the MGC could send an=20
>underspecified SDP requesting that the MG choose the codecs.  The MG=20
>can then choose to include a payload number for 2833 if it chooses to =
do
so.=20
> =20
>=20
So it is true that, in any case, MGC needs to do something special to =
handle
rfc2833.=20
Just want to be clear on "underspecified SDP request":=20

If MGC just sends "m=3Daudio $ RTP/AVP 0", it means no rfc2833, right?=20

If MGC sends "m=3Daudio $ RTP/AVP $", it means that MG will choose *one*
codec, say, MG may respond "m=3Daudio 8000 RTP/AVP 0", but how MG =
responds the
payload number for RFC2833 if it always wants to support RFC2833? If MGC
sends m=3Daudio $ RTP/AVP $ a=3Drtpmap:$ telephone-evemts/8000 then can =
MG
responds with m=3Daudio 8000 RTP/AVP 0 101

a=3Drtpmap:101 telephone-evemts/8000=20
If this the true, then is the last $ in "m=3D" acturally a list?=20

Or should MG respond with=20
m=3Daudio 8000 RTP/AVP 0=20
a=3Drtpmap:101 telephone-evemts/8000=20
(is this SDP legal?)=20

Regards,=20
Richard=20

=20

>Kevin=20
>=20
>-----Original Message-----=20
>From: Richard Sun [mailto:xsun@lucent.com]=20
>Sent: Friday, December 17, 2004 2:17 PM=20
>To: Boyle, Kevin [NCRTP:3Z40:EXCH]=20
>Cc: Marcello Pantaleo (AC/EDD); megaco@ietf.org=20
>Subject: Re: [Megaco] how codec negotiation is triggered by MGC?=20
>=20
>Kevin,=20
>Thanks for the reply.=20
>=20
> > Why not just have the MGC choose the payload number for  > the 2833=20
>events?=20
>=20
>Good question. That was what I asked. But some MGC implementation says=20
>that MGC does not care rfc2833 and its payload type at all, MGC just=20
>expects MG to turn on rfc2833 automatically. I thought this is not=20
>possible, so I=20
asked=20
>the question just to make sure that I do not miss anything.=20
>=20
>To put it another way:=20
>does it make any sense for any MGC to say:=20
>"MGC never needs to look at the SDP contents, it just pass SDP among =
MGs.=20
>MGs should just handle the codec negotiation themself"?=20
>=20
>This is indeed possible with MGCP. But it seems that this is really not =

>possibile with H248.=20
>For H248, MGC always needs to be involved in this codec negotiation.=20
>=20
>Let me know if I am wrong. Thanks,=20
>-Richard=20
>=20
>=20
>Kevin Boyle wrote:=20
>=20
> =20
>=20
>>Why not just have the MGC choose the payload number for the 2833 =
events?=20
>>=20
>>Note that the m line example here restricts the payload selectors to=20
>>those defined as RTP/AVP.  This can be avoided by using $ for that=20
>>element as well.=20
>>=20
>>To confirm Marcello's statement, '*' is not a permitted wildcard in=20
>>underspecified SDP.  '$' is allowed in any position and means choose.=20
>>Note that the use of wildcards is only allowed in the MGC->MG=20
>>direction.  MGs are always expected to send compliant SDP.=20
>>=20
>>Kevin=20
>>=20
>>-----Original Message-----=20
>>From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On=20
>>Behalf Of Richard Sun=20
>>Sent: Friday, December 17, 2004 12:39 PM=20
>>To: Marcello Pantaleo (AC/EDD)=20
>>Cc: megaco@ietf.org=20
>>Subject: Re: [Megaco] how codec negotiation is triggered by MGC?=20
>>=20
>>Marcello,=20
>>Thanks for your helpfull information.=20
>>=20
>>Now assume that MGC audits MG and learns that MG supports "PCMU" *and* =

>>"telephone-event".=20
>>If "m=3Daudio $ RTP/AVP $" means that=20
>>MG to choose *one* codec, then=20
>>what is the syntax for MGC to instruct MG "use PCMU, *and* choose a=20
>>payload number for telephone-event"?=20
>>=20
>>-Richard=20
>>=20
>>Marcello Pantaleo (AC/EDD) wrote:=20
>>=20
>> > Hi,=20
>> >=20
>> > MGC can use audit capabilities to get the list of codecs supported=20
>>by a MG. Alternatively a MGC can be provisioned with MG capabilities.=20
>>=20
>> >=20
>> > MGC wouldn't use Add to know MG capabilities (e.g. supported =
codecs).=20
>> >=20
>> > If MGC sends an Add command with an empty local desciptor, this is=20
>>a request to release any resources previously reserved for the media=20
>>flow received, that means nothing given that MGC is now creating the=20
>>   =20
>>=20
>termination.=20
> =20
>=20
>> > If local descriptor is unspecified (i.e. absent), MG considers this =

>>as missing mandatory parameter. MG uses whatever previously specified. =

>>=20
>> >=20
>> > If MGC sends "m=3Daudio $ RTP/AVP $" it requests MG to choose one =
of=20
>>the supported codecs, so you don't get the list.=20
>> >=20
>> > I don't think you can use * wildcard in the "m=3D".=20
>> >=20
>> > Regards,=20
>> > Marcello=20
>> >=20
>> > -----Original Message-----=20
>> > From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]On=20
>> > Behalf Of Richard Sun=20
>> > Sent: Thursday, December 16, 2004 3:08 PM  > To: megaco@ietf.org  > =

>>Subject: [Megaco] how codec negotiation is triggered by MGC?=20
>> >=20
>> >=20
>> > Hi, Can anyone pelase clarify the standard for MGC to trigger a=20
>>codec  > negotiation in MG (i.e, MG should provide a list of codecs it =

>>   =20
>>=20
>>>supports)?=20
>>>     =20
>>>=20
>> >=20
>> > One way I can think of is an empty "Local{}"=20
>> > without SDP, such as:=20
>> > Transaction =3D 299012 {=20
>> >   Context =3D $ {=20
>> >     Add =3D aaln/1 {=20
>> >       Media { Stream =3D 1 {=20
>> >         LocalControl {Mode =3D SendReceive}=20
>> >     }}},=20
>> >     Add =3D $ {=20
>> >       Media {Stream =3D 1 {=20
>> >         LocalControl {Mode=3DReceiveOnly},=20
>> >         Local {}=20
>> > }}}}}=20
>> >=20
>> > The question is: is this legal? Should MG reject the message with=20
>>some  > kind of error such as "SDP missing", or MG is suppose to fill=20
>>up the  > SDP section in response?=20
>> > What if the "Local{}" does not present at all?=20
>> >=20
>> > The other way is something like this:=20
>> > Transaction =3D 299012 {=20
>> >   Context =3D $ {=20
>> >     Add =3D aaln/1 {=20
>> >       Media { Stream =3D 1 {=20
>> >         LocalControl {Mode =3D SendReceive}=20
>> >     }}},=20
>> >     Add =3D $ {=20
>> >       Media {Stream =3D 1 {=20
>> >         LocalControl {Mode=3DReceiveOnly},=20
>> >         Local {=20
>> > v=3D0=20
>> > o=3D$ $ $ IN IP4 $=20
>> > s=3D$=20
>> > c=3DIN IP4 $=20
>> > t=3D$ $=20
>> > m=3Daudio $ RTP/AVP -=20
>> > a=3Dptime:20=20
>> > }}}}}}=20
>> > With "-" in "m=3Daudio $ RTP/AVP -", should MG fill up the list of  =
>=20
>>codecs?=20
>> > Or should it be something like=20
>> > "m=3Daudio $ RTP/AVP $"?=20
>> >=20
>> > Thanks for any information.=20
>> > -Richard=20
>> >=20
>> > _______________________________________________=20
>> > Megaco mailing list=20
>> > Megaco@ietf.org=20
>> > https://www1.ietf.org/mailman/listinfo/megaco=20
>>=20
>>_______________________________________________=20
>>Megaco mailing list=20
>>Megaco@ietf.org=20
>>https://www1.ietf.org/mailman/listinfo/megaco=20
>>=20
>>   =20
>>=20
>=20
>=20
>_______________________________________________=20
>Megaco mailing list=20
>Megaco@ietf.org=20
>https://www1.ietf.org/mailman/listinfo/megaco=20
> =20
>=20

=20

_______________________________________________=20
Megaco mailing list=20
Megaco@ietf.org=20
https://www1.ietf.org/mailman/listinfo/megaco=20

=20


------=_NextPart_000_0001_01C4E6C0.21C64DD0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">
<title>RE: [Megaco] how codec negotiation is triggered by MGC?</title>

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p
	{margin-right:0in;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{font-family:Verdana;
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
style=3D'font-size:
9.0pt;font-family:Verdana;color:blue'>The MGC would like to know if the =
MGs can
(or cannot) do RFC2833 because, while controlling two participating MGs, =
it
needs to know the capabilities of both when sending media parameters to =
both.
It can explicitly specify it in the Local Descriptor as you have said, =
but in
that case that Add command would get fail if that MG does not support =
RFC2833 (and
the exact reason why the add command (inability to support RFC2833) =
would not
be clear from the error response) in which case the call would not be
established.</span></font></p>

<div>

<p class=3DMsoAutoSig><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
11.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoAutoSig><font size=3D1 color=3Dblue face=3DVerdana><span
style=3D'font-size:7.5pt;font-family:Verdana;color:blue'>Bala</span></fon=
t></p>

</div>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
style=3D'font-size:
9.0pt;font-family:Verdana;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Kevin Boyle
[mailto:kboyle@nortelnetworks.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, December =
17, 2004
11:15 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Balasubramanian =
Pitchandi;
'Richard Sun'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> 'Marcello Pantaleo =
(AC/EDD)';
megaco@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [Megaco] how =
codec
negotiation is triggered by MGC?</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>Why would the MGC care if the MG can do =
2833?&nbsp; If
it matters, then the MGC can explicitly signal it in the Local =
descriptor by
choosing a dynamic payload number and including the appropriate rtpmap =
and
associated a line parameters.</span></font></p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>If the MGC sends $ as the payload list, the =
MG can
return as many payload numbers as it likes, ordered by preference.&nbsp; =
So if
the MG wishes to include 2833 as an option, it would return the info =
necessary
in the SDP along with whatever other codecs it may wish to =
choose.</span></font></p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>If the MGC really NEEDS to know if the MG can =
do
RFC2833 out of band signalling of telephony events, then it could try =
auditing
the Local descriptor for that information... but the response may be
particularly unwieldy and difficult to parse for the =
MGC.</span></font></p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>Kevin </span></font></p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>-----Original Message-----</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>From: Balasubramanian =
Pitchandi [<a
href=3D"mailto:bs@utstar.com">mailto:bs@utstar.com</a>] =
</span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>Sent: Friday, December =
17, 2004
5:52 PM</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>To: 'Richard Sun'; =
Boyle, Kevin
[NCRTP:3Z40:EXCH]</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>Cc: 'Marcello Pantaleo =
(AC/EDD)';
megaco@ietf.org</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>Subject: RE: [Megaco] =
how codec
negotiation is triggered by MGC?</span></font> </p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>I don't think MGC can &quot;assume&quot; that =
the MG
can always do RFC2833. MGC cannot predict how an MG would respond to an
underspecified SDP (including/excluding RFC2833). When interoperating =
with
multiple MGs, you want to specifically know if each MG can or cannot do
RFC2833.</span></font></p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>I kinda agree with Richard that there's no =
clear
method as to how the MGC can learn of MG's ability to do RFC2833 in =
H.248.</span></font></p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>Bala</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&nbsp;</span></font> =
</p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>-----Original Message-----</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>From: =
megaco-bounces@ietf.org [<a
href=3D"mailto:megaco-bounces@ietf.org">mailto:megaco-bounces@ietf.org</a=
>] On
Behalf Of Richard Sun</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>Sent: Friday, December =
17, 2004
3:56 PM</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>To: Kevin =
Boyle</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>Cc: Marcello Pantaleo =
(AC/EDD);
megaco@ietf.org</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>Subject: Re: [Megaco] =
how codec
negotiation is triggered by MGC?</span></font> </p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>Kevin, thanks for the response. See below =
...</span></font>
</p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>&gt;Actually, this is not true.&nbsp; While =
MGCP does
not send SDP from the CA </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;to</span></font> =
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>the</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;MTA, it *does* send =
&quot;Local
Connection Options&quot; which function in the </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;same capacity as =
underspecified
Local SDP in H.248 -- to indicate to </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;the MG the =
constraints of the
SDP it may return.</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&nbsp; =
</span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>Agree.</span></font> =
</p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>&gt;Now, if the MG wants to always do 2833 =
and you
don't want the MGC to </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;worry about having =
to ask the
MG to do it, then the MGC could send an </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;underspecified SDP =
requesting
that the MG choose the codecs.&nbsp; The MG </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;can then choose to =
include a
payload number for 2833 if it chooses to do so.</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&nbsp; =
</span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>So it is true that, in =
any case,
MGC needs to do something special to handle rfc2833.</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>Just want to be clear on
&quot;underspecified SDP request&quot;:</span></font> </p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>If MGC just sends &quot;m=3Daudio $ RTP/AVP =
0&quot;, it
means no rfc2833, right?</span></font> </p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>If MGC sends &quot;m=3Daudio $ RTP/AVP =
$&quot;, it means
that MG will choose *one* codec, say, MG may respond &quot;m=3Daudio =
8000 RTP/AVP
0&quot;, but how MG responds the payload number for RFC2833 if it always =
wants
to support RFC2833? If MGC sends m=3Daudio $ RTP/AVP $ a=3Drtpmap:$
telephone-evemts/8000 then can MG responds with m=3Daudio 8000 RTP/AVP 0 =
101</span></font></p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>a=3Drtpmap:101 =
telephone-evemts/8000</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>If this the true, then =
is the last
$ in &quot;m=3D&quot; acturally a list?</span></font> </p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>Or should MG respond with</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>m=3Daudio 8000 RTP/AVP =
0</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>a=3Drtpmap:101 =
telephone-evemts/8000</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>(is this SDP =
legal?)</span></font> </p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>Regards,</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>Richard</span></font> =
</p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>&gt;Kevin</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;-----Original =
Message-----</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;From: Richard Sun =
[<a
href=3D"mailto:xsun@lucent.com">mailto:xsun@lucent.com</a>]</span></font>=
 <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;Sent: Friday, =
December 17, 2004
2:17 PM</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;To: Boyle, Kevin
[NCRTP:3Z40:EXCH]</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;Cc: Marcello =
Pantaleo (AC/EDD);
megaco@ietf.org</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;Subject: Re: =
[Megaco] how codec
negotiation is triggered by MGC?</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;Kevin,</span></font> =
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;Thanks for the =
reply.</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt; &gt; Why not just =
have the MGC
choose the payload number for&nbsp; &gt; the 2833</span></font> <br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;events?</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;Good question. That =
was what I
asked. But some MGC implementation says </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;that MGC does not =
care rfc2833
and its payload type at all, MGC just </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;expects MG to turn =
on rfc2833
automatically. I thought this is not </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;possible, so =
I</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>asked</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;the question just to =
make sure
that I do not miss anything.</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;To put it another =
way:</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;does it make any =
sense for any
MGC to say:</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&quot;MGC never =
needs to look
at the SDP contents, it just pass SDP among MGs.</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;MGs should just =
handle the
codec negotiation themself&quot;?</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;This is indeed =
possible with
MGCP. But it seems that this is really not </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;possibile with =
H248.</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;For H248, MGC always =
needs to
be involved in this codec negotiation.</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;Let me know if I am =
wrong.
Thanks,</span></font> <br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;-Richard</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;Kevin Boyle =
wrote:</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&nbsp; =
</span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;Why not just =
have the MGC
choose the payload number for the 2833 events?</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;</span></font> =
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;Note that the m =
line
example here restricts the payload selectors to </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;those defined as
RTP/AVP.&nbsp; This can be avoided by using $ for that =
</span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;element as =
well.</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;</span></font> =
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;To confirm =
Marcello's
statement, '*' is not a permitted wildcard in </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;underspecified =
SDP.&nbsp;
'$' is allowed in any position and means choose.</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;Note that the =
use of
wildcards is only allowed in the MGC-&gt;MG </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;direction.&nbsp; =
MGs are
always expected to send compliant SDP.</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;</span></font> =
<br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;&gt;Kevin</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;</span></font> =
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;-----Original =
Message-----</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;From:
megaco-bounces@ietf.org [<a =
href=3D"mailto:megaco-bounces@ietf.org">mailto:megaco-bounces@ietf.org</a=
>]
On </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;Behalf Of =
Richard Sun</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;Sent: Friday, =
December 17,
2004 12:39 PM</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;To: Marcello =
Pantaleo
(AC/EDD)</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;Cc: =
megaco@ietf.org</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;Subject: Re: =
[Megaco] how
codec negotiation is triggered by MGC?</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;</span></font> =
<br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;&gt;Marcello,</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;Thanks for your =
helpfull
information.</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;</span></font> =
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;Now assume that =
MGC audits
MG and learns that MG supports &quot;PCMU&quot; *and* </span></font><br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;&gt;&quot;telephone-event&quot;.</span></f=
ont>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;If =
&quot;m=3Daudio $ RTP/AVP
$&quot; means that</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;MG to choose =
*one* codec,
then</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;what is the =
syntax for MGC
to instruct MG &quot;use PCMU, *and* choose a </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;payload number =
for
telephone-event&quot;?</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;</span></font> =
<br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;&gt;-Richard</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;</span></font> =
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;Marcello =
Pantaleo (AC/EDD)
wrote:</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;</span></font> =
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; =
Hi,</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; =
&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; MGC can =
use audit
capabilities to get the list of codecs supported</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;by a MG. =
Alternatively a
MGC can be provisioned with MG capabilities.</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;</span></font> =
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; =
&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; MGC =
wouldn't use Add
to know MG capabilities (e.g. supported codecs).</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; =
&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; If MGC =
sends an Add
command with an empty local desciptor, this is</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;a request to =
release any
resources previously reserved for the media </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;flow received, =
that means
nothing given that MGC is now creating the</span></font> <br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;&gt;&nbsp;&nbsp;&nbsp; </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;</span></font> =
<br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;termination.</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&nbsp; =
</span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; If local =
descriptor
is unspecified (i.e. absent), MG considers this</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;as missing =
mandatory
parameter. MG uses whatever previously specified.</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;</span></font> =
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; =
&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; If MGC =
sends
&quot;m=3Daudio $ RTP/AVP $&quot; it requests MG to choose one =
of</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;the supported =
codecs, so
you don't get the list.</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; =
&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; I don't =
think you can
use * wildcard in the &quot;m=3D&quot;.</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; =
&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; =
Regards,</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; =
Marcello</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; =
&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; =
-----Original
Message-----</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; From:
megaco-bounces@ietf.org [<a =
href=3D"mailto:megaco-bounces@ietf.org">mailto:megaco-bounces@ietf.org</a=
>]On</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; Behalf Of =
Richard Sun</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; Sent: =
Thursday,
December 16, 2004 3:08 PM&nbsp; &gt; To: megaco@ietf.org&nbsp; =
&gt;</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;Subject: =
[Megaco] how codec
negotiation is triggered by MGC?</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; =
&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; =
&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; Hi, Can =
anyone pelase
clarify the standard for MGC to trigger a</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;codec&nbsp; &gt;
negotiation in MG (i.e, MG should provide a list of codecs =
it</span></font> <br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;&gt;&nbsp;&nbsp;&nbsp; </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;</span></font> =
<br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;&gt;&gt;supports)?</span></font>
<br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font><br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;&gt;&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; =
&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; One way I =
can think
of is an empty &quot;Local{}&quot;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; without =
SDP, such as:</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; =
Transaction =3D 299012
{</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; =
&gt;&nbsp;&nbsp; Context =3D
$ {</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Add =3D aaln/1 {</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Media { Stream =3D 1 =
{</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LocalControl {Mode =
=3D
SendReceive}</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp; }}},</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Add =3D $ {</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Media {Stream =3D 1 =
{</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LocalControl
{Mode=3DReceiveOnly},</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Local =
{}</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; =
}}}}}</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; =
&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; The =
question is: is
this legal? Should MG reject the message with</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;some&nbsp; &gt; =
kind of
error such as &quot;SDP missing&quot;, or MG is suppose to fill =
</span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;up the&nbsp; =
&gt; SDP
section in response?</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; What if =
the
&quot;Local{}&quot; does not present at all?</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; =
&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; The other =
way is
something like this:</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; =
Transaction =3D 299012
{</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; =
&gt;&nbsp;&nbsp; Context =3D
$ {</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Add =3D aaln/1 {</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Media { Stream =3D 1 =
{</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LocalControl {Mode =
=3D
SendReceive}</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp; }}},</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Add =3D $ {</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Media {Stream =3D 1 =
{</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LocalControl
{Mode=3DReceiveOnly},</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Local =
{</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; =
v=3D0</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; o=3D$ $ $ =
IN IP4 $</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; =
s=3D$</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; c=3DIN IP4 =
$</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; t=3D$ =
$</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; m=3Daudio =
$ RTP/AVP -</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; =
a=3Dptime:20</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; =
}}}}}}</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; With =
&quot;-&quot; in
&quot;m=3Daudio $ RTP/AVP -&quot;, should MG fill up the list of&nbsp; =
&gt;</span></font>
<br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;&gt;codecs?</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; Or should =
it be
something like</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; =
&quot;m=3Daudio $
RTP/AVP $&quot;?</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; =
&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; Thanks for =
any
information.</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; =
-Richard</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; =
&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt;
_______________________________________________</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; Megaco =
mailing list</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; =
Megaco@ietf.org</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt; &gt; <a
href=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
target=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</a></span=
></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;</span></font> =
<br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;&gt;______________________________________=
_________</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;Megaco mailing =
list</span></font>
<br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;&gt;Megaco@ietf.org</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;<a
href=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
target=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</a></span=
></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;</span></font> =
<br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;&gt;&nbsp;&nbsp;&nbsp; </span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&gt;</span></font> =
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;</span></font> <br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;__________________________________________=
_____</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;Megaco mailing =
list</span></font>
<br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>&gt;Megaco@ietf.org</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;<a
href=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
target=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</a></span=
></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;&nbsp; =
</span></font><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;</span></font> </p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>______________________________________________=
_</span></font>
<br>
<font size=3D2><span style=3D'font-size:10.0pt'>Megaco mailing =
list</span></font> <br>
<font size=3D2><span =
style=3D'font-size:10.0pt'>Megaco@ietf.org</span></font> <br>
<font size=3D2><span style=3D'font-size:10.0pt'><a
href=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
target=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</a></span=
></font>
</p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0001_01C4E6C0.21C64DD0--



--===============0940371666==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco

--===============0940371666==--




From megaco-bounces@ietf.org  Wed Dec 22 03:56:32 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02673
	for <megaco-archive@lists.ietf.org>; Wed, 22 Dec 2004 03:56:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ch29o-0005JE-0m; Wed, 22 Dec 2004 03:47:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ch25N-0004N3-Jm
	for megaco@megatron.ietf.org; Wed, 22 Dec 2004 03:43:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01858
	for <megaco@ietf.org>; Wed, 22 Dec 2004 03:43:07 -0500 (EST)
From: Albrecht.Schwarz@alcatel.de
Received: from mailrelay1.alcatel.de ([194.113.59.55]
	helo=mailrelay2.alcatel.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ch2F0-0006MH-O8
	for megaco@ietf.org; Wed, 22 Dec 2004 03:53:07 -0500
Received: from demail05.netfr.alcatel.fr (demail05.netfr.alcatel.fr
	[155.132.182.205])
	by mailrelay2.alcatel.de (8.12.11/8.12.10) with ESMTP id iBM8gY3v023773;
	Wed, 22 Dec 2004 09:42:34 +0100 (MET)
In-Reply-To: <000001c4e6ea$0a9c55d0$392910ac@nj.us.utstar.com>
Subject: RE: [Megaco] how codec negotiation is triggered by MGC?
To: "Balasubramanian Pitchandi" <bs@utstar.com>
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF5BA8E090.84884075-ONC1256F72.002AD53A-C1256F72.002FD72D@netfr.alcatel.fr>
Date: Wed, 22 Dec 2004 09:42:32 +0100
X-MIMETrack: Serialize by Router on DEMAIL05/DE/ALCATEL(Release 5.0.12HF788 |
	September 23, 2004) at 12/22/2004 09:42:34
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-AES-MTA-scanned-and-authorized: yes
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 509eeaf340e89c687918a6101c6def35
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org


Just two side comments, the perspective here is too narrow in my opinion:

When (1) both parties connected to the same MG, or when (2) a single MGC is
controlling both MGs (where the parties connected are), are valid
scenarios, but not the general case.

Did you further consider the more general cases:
(3) case with MGC-to-MGC signalling (both MGs are associated to different
controllers), or
(4) different encoding modes (one MG uses binary encoding, other MG uses
text encoding => MGC must support dual mode, what about  ... SDP handling
...)?

I my opinion, the underlying issues is there are two fundamentally
different types of negotiation procedure from network perspective ("which
are both may collapse at a control interface like in our case with H.248):

1st type: end-to-end or peer-to-peer negotiation (=> only related to
protocol endpoints, "termination capability negotiation")
       => for instance, examples for VoIP H.248 case: H.248 MG peering
either another H.248 MG, or another non-H.248 MG, or an H.248 VoIP terminal
(RFC 3054), or an non-H.248 VoIP terminal (like SIP phone, H.323 terminal)

2nd type: hop-by-hop negotiation (=> related to protocol endpoints and all
involved in path nodes, "bearer capability negotiation")
       => examples for H.248 systems: negotiation procedures in 3GPP
Release 4 Circuit-Switched domain, or BICC Capability Set 2

Now, in case of decomposed systems like H.248, there are (at least) two
vertical control methods: a) strict control by MGC, or b) "more autonomous
control" by MG [see for instance H.248-controlled T.38 service where both
"negotiation" controls are supported].

The 2nd negotiation category (hop-by-hop) is typically "strictly
controlled" (because there are call/session control protocols or bearer
control protocols as prime negotiators).

The "RFC2833 case" of this email thread belongs to the 1st category in my
opinion. I tend to agree Kevin's view here.
regards
Albrecht





                                                                                                                                
                      "Balasubramanian                                                                                          
                      Pitchandi"               To:      "'Kevin Boyle'" <kboyle@nortelnetworks.com>, "'Richard Sun'"            
                      <bs@utstar.com>          <xsun@lucent.com>                                                                
                      Sent by:                 cc:      "'Marcello Pantaleo \(AC/EDD\)'" <marcello.pantaleo@ericsson.com>,      
                      megaco-bounces@i         megaco@ietf.org                                                                  
                      etf.org                  Subject: RE: [Megaco] how codec negotiation is triggered by MGC?                 
                                                                                                                                
                                                                                                                                
                      21.12.2004 00:17                                                                                          
                                                                                                                                




The MGC would like to know if the MGs can (or cannot) do RFC2833 because,
while controlling two participating MGs, it needs to know the capabilities
of both when sending media parameters to both. It can explicitly specify it
in the Local Descriptor as you have said, but in that case that Add command
would get fail if that MG does not support RFC2833 (and the exact reason
why the add command (inability to support RFC2833) would not be clear from
the error response) in which case the call would not be established.

Bala

-----Original Message-----
From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]
Sent: Friday, December 17, 2004 11:15 PM
To: Balasubramanian Pitchandi; 'Richard Sun'
Cc: 'Marcello Pantaleo (AC/EDD)'; megaco@ietf.org
Subject: RE: [Megaco] how codec negotiation is triggered by MGC?



Why would the MGC care if the MG can do 2833?  If it matters, then the MGC
can explicitly signal it in the Local descriptor by choosing a dynamic
payload number and including the appropriate rtpmap and associated a line
parameters.


If the MGC sends $ as the payload list, the MG can return as many payload
numbers as it likes, ordered by preference.  So if the MG wishes to include
2833 as an option, it would return the info necessary in the SDP along with
whatever other codecs it may wish to choose.


If the MGC really NEEDS to know if the MG can do RFC2833 out of band
signalling of telephony events, then it could try auditing the Local
descriptor for that information... but the response may be particularly
unwieldy and difficult to parse for the MGC.


Kevin


-----Original Message-----
From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
Sent: Friday, December 17, 2004 5:52 PM
To: 'Richard Sun'; Boyle, Kevin [NCRTP:3Z40:EXCH]
Cc: 'Marcello Pantaleo (AC/EDD)'; megaco@ietf.org
Subject: RE: [Megaco] how codec negotiation is triggered by MGC?


I don't think MGC can "assume" that the MG can always do RFC2833. MGC
cannot predict how an MG would respond to an underspecified SDP
(including/excluding RFC2833). When interoperating with multiple MGs, you
want to specifically know if each MG can or cannot do RFC2833.


I kinda agree with Richard that there's no clear method as to how the MGC
can learn of MG's ability to do RFC2833 in H.248.


Bala



-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Richard Sun
Sent: Friday, December 17, 2004 3:56 PM
To: Kevin Boyle
Cc: Marcello Pantaleo (AC/EDD); megaco@ietf.org
Subject: Re: [Megaco] how codec negotiation is triggered by MGC?


Kevin, thanks for the response. See below ...


>Actually, this is not true.  While MGCP does not send SDP from the CA
>to
the
>MTA, it *does* send "Local Connection Options" which function in the
>same capacity as underspecified Local SDP in H.248 -- to indicate to
>the MG the constraints of the SDP it may return.
>
>
Agree.


>Now, if the MG wants to always do 2833 and you don't want the MGC to
>worry about having to ask the MG to do it, then the MGC could send an
>underspecified SDP requesting that the MG choose the codecs.  The MG
>can then choose to include a payload number for 2833 if it chooses to do
so.
>
>
So it is true that, in any case, MGC needs to do something special to
handle rfc2833.
Just want to be clear on "underspecified SDP request":


If MGC just sends "m=audio $ RTP/AVP 0", it means no rfc2833, right?


If MGC sends "m=audio $ RTP/AVP $", it means that MG will choose *one*
codec, say, MG may respond "m=audio 8000 RTP/AVP 0", but how MG responds
the payload number for RFC2833 if it always wants to support RFC2833? If
MGC sends m=audio $ RTP/AVP $ a=rtpmap:$ telephone-evemts/8000 then can MG
responds with m=audio 8000 RTP/AVP 0 101


a=rtpmap:101 telephone-evemts/8000
If this the true, then is the last $ in "m=" acturally a list?


Or should MG respond with
m=audio 8000 RTP/AVP 0
a=rtpmap:101 telephone-evemts/8000
(is this SDP legal?)


Regards,
Richard



>Kevin
>
>-----Original Message-----
>From: Richard Sun [mailto:xsun@lucent.com]
>Sent: Friday, December 17, 2004 2:17 PM
>To: Boyle, Kevin [NCRTP:3Z40:EXCH]
>Cc: Marcello Pantaleo (AC/EDD); megaco@ietf.org
>Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
>
>Kevin,
>Thanks for the reply.
>
> > Why not just have the MGC choose the payload number for  > the 2833
>events?
>
>Good question. That was what I asked. But some MGC implementation says
>that MGC does not care rfc2833 and its payload type at all, MGC just
>expects MG to turn on rfc2833 automatically. I thought this is not
>possible, so I
asked
>the question just to make sure that I do not miss anything.
>
>To put it another way:
>does it make any sense for any MGC to say:
>"MGC never needs to look at the SDP contents, it just pass SDP among MGs.
>MGs should just handle the codec negotiation themself"?
>
>This is indeed possible with MGCP. But it seems that this is really not
>possibile with H248.
>For H248, MGC always needs to be involved in this codec negotiation.
>
>Let me know if I am wrong. Thanks,
>-Richard
>
>
>Kevin Boyle wrote:
>
>
>
>>Why not just have the MGC choose the payload number for the 2833 events?
>>
>>Note that the m line example here restricts the payload selectors to
>>those defined as RTP/AVP.  This can be avoided by using $ for that
>>element as well.
>>
>>To confirm Marcello's statement, '*' is not a permitted wildcard in
>>underspecified SDP.  '$' is allowed in any position and means choose.
>>Note that the use of wildcards is only allowed in the MGC->MG
>>direction.  MGs are always expected to send compliant SDP.
>>
>>Kevin
>>
>>-----Original Message-----
>>From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On
>>Behalf Of Richard Sun
>>Sent: Friday, December 17, 2004 12:39 PM
>>To: Marcello Pantaleo (AC/EDD)
>>Cc: megaco@ietf.org
>>Subject: Re: [Megaco] how codec negotiation is triggered by MGC?
>>
>>Marcello,
>>Thanks for your helpfull information.
>>
>>Now assume that MGC audits MG and learns that MG supports "PCMU" *and*
>>"telephone-event".
>>If "m=audio $ RTP/AVP $" means that
>>MG to choose *one* codec, then
>>what is the syntax for MGC to instruct MG "use PCMU, *and* choose a
>>payload number for telephone-event"?
>>
>>-Richard
>>
>>Marcello Pantaleo (AC/EDD) wrote:
>>
>> > Hi,
>> >
>> > MGC can use audit capabilities to get the list of codecs supported
>>by a MG. Alternatively a MGC can be provisioned with MG capabilities.
>>
>> >
>> > MGC wouldn't use Add to know MG capabilities (e.g. supported codecs).
>> >
>> > If MGC sends an Add command with an empty local desciptor, this is
>>a request to release any resources previously reserved for the media
>>flow received, that means nothing given that MGC is now creating the
>>
>>
>termination.
>
>
>> > If local descriptor is unspecified (i.e. absent), MG considers this
>>as missing mandatory parameter. MG uses whatever previously specified.
>>
>> >
>> > If MGC sends "m=audio $ RTP/AVP $" it requests MG to choose one of
>>the supported codecs, so you don't get the list.
>> >
>> > I don't think you can use * wildcard in the "m=".
>> >
>> > Regards,
>> > Marcello
>> >
>> > -----Original Message-----
>> > From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]On
>> > Behalf Of Richard Sun
>> > Sent: Thursday, December 16, 2004 3:08 PM  > To: megaco@ietf.org  >
>>Subject: [Megaco] how codec negotiation is triggered by MGC?
>> >
>> >
>> > Hi, Can anyone pelase clarify the standard for MGC to trigger a
>>codec  > negotiation in MG (i.e, MG should provide a list of codecs it
>>
>>
>>>supports)?
>>>
>>>
>> >
>> > One way I can think of is an empty "Local{}"
>> > without SDP, such as:
>> > Transaction = 299012 {
>> >   Context = $ {
>> >     Add = aaln/1 {
>> >       Media { Stream = 1 {
>> >         LocalControl {Mode = SendReceive}
>> >     }}},
>> >     Add = $ {
>> >       Media {Stream = 1 {
>> >         LocalControl {Mode=ReceiveOnly},
>> >         Local {}
>> > }}}}}
>> >
>> > The question is: is this legal? Should MG reject the message with
>>some  > kind of error such as "SDP missing", or MG is suppose to fill
>>up the  > SDP section in response?
>> > What if the "Local{}" does not present at all?
>> >
>> > The other way is something like this:
>> > Transaction = 299012 {
>> >   Context = $ {
>> >     Add = aaln/1 {
>> >       Media { Stream = 1 {
>> >         LocalControl {Mode = SendReceive}
>> >     }}},
>> >     Add = $ {
>> >       Media {Stream = 1 {
>> >         LocalControl {Mode=ReceiveOnly},
>> >         Local {
>> > v=0
>> > o=$ $ $ IN IP4 $
>> > s=$
>> > c=IN IP4 $
>> > t=$ $
>> > m=audio $ RTP/AVP -
>> > a=ptime:20
>> > }}}}}}
>> > With "-" in "m=audio $ RTP/AVP -", should MG fill up the list of  >
>>codecs?
>> > Or should it be something like
>> > "m=audio $ RTP/AVP $"?
>> >
>> > Thanks for any information.
>> > -Richard
>> >
>> > _______________________________________________
>> > Megaco mailing list
>> > Megaco@ietf.org
>> > https://www1.ietf.org/mailman/listinfo/megaco
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>>
>>
>>
>
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
>
>



_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
 _______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco





_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Mon Dec 27 10:40:23 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22297
	for <megaco-archive@lists.ietf.org>; Mon, 27 Dec 2004 10:40:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CiwvP-00025S-UD; Mon, 27 Dec 2004 10:36:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CiwsH-0001H7-26
	for megaco@megatron.ietf.org; Mon, 27 Dec 2004 10:33:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21757
	for <megaco@ietf.org>; Mon, 27 Dec 2004 10:33:31 -0500 (EST)
Received: from [200.51.236.11] (helo=mail4.telefonica.com.ar)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cix2z-0005k3-Dr
	for megaco@ietf.org; Mon, 27 Dec 2004 10:44:38 -0500
Received: by mailhub2.telefonica.com.ar with Internet Mail Service
	(5.5.2653.19) id <4R8H9ZX8>; Mon, 27 Dec 2004 12:33:19 -0300
Message-ID: <6BB2DEB822D3D111817B00805FBE5F0215182819@mstelefonica6.telefonica.com.ar>
From: Pellegrino Jose Luis <pellegrj@TELEFONICA.COM.AR>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Mon, 27 Dec 2004 12:33:10 -0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Subject: [Megaco] optional parameters "ServiceChamgeAddress", "ImmAck"
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0530323911=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============0530323911==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4EC29.5F463F30"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C4EC29.5F463F30
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Hi, can anyone give me one opinion?

In order to resolve interoperability multivendor, both, MG and MGC must
agree wich optional parameters are soported.
For example, the ServiceChangeAddress is optional in Service Change. =
And so
is ImmAck in replay. So, because they are optional, may be that  many
vendors soport these parameters, and others doesn=B4t, so the =
interoperability
is not possible.

The question, if anybody can help me, is wich is the criteria to =
include
these parameters.
=20
Reading the "Megaco/h.248 call flows examples", we can find that
ServiceChangeAddress is used in ServiceChange,  but ImmAck is not. It =
seems
to be ServiceChangeAddress is more frecuently used than ImmAck. Am I =
right?

Best regards,
Jos=E9
=20

------_=_NextPart_001_01C4EC29.5F463F30
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>optional parameters &quot;ServiceChamgeAddress&quot;, =
&quot;ImmAck&quot;</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi, can anyone give me one =
opinion?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">In order to resolve interoperability =
multivendor, both, MG and MGC must agree wich optional parameters are =
soported.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">For example, the ServiceChangeAddress =
is optional in Service Change. And so is ImmAck in replay. So, because =
they are optional, may be that&nbsp; many vendors soport these =
parameters, and others doesn=B4t, so the interoperability is not =
possible.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The question, if anybody can help me, =
is wich is the criteria to include these parameters.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Reading the &quot;Megaco/h.248 call =
flows examples&quot;, we can find that ServiceChangeAddress is used in =
ServiceChange,&nbsp; but ImmAck is not. It seems to be =
ServiceChangeAddress is more frecuently used than ImmAck. Am I =
right?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Best regards,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Jos=E9</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C4EC29.5F463F30--


--===============0530323911==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco

--===============0530323911==--



From megaco-bounces@ietf.org  Tue Dec 28 00:35:57 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10635
	for <megaco-archive@lists.ietf.org>; Tue, 28 Dec 2004 00:35:57 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cj9zn-000677-GJ; Tue, 28 Dec 2004 00:34:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cj9sa-000363-O5
	for megaco@megatron.ietf.org; Tue, 28 Dec 2004 00:26:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10252
	for <megaco@ietf.org>; Tue, 28 Dec 2004 00:26:42 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjA3R-00072G-E9
	for megaco@ietf.org; Tue, 28 Dec 2004 00:37:57 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iBS5Q9M12931
	for <megaco@ietf.org>; Tue, 28 Dec 2004 00:26:09 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Y0S9KC2B>; Tue, 28 Dec 2004 00:26:10 -0500
Message-ID: <B258A372CEA20246A363BB86753DB53601846A9A@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Pellegrino Jose Luis <pellegrj@TELEFONICA.COM.AR>,
        "'megaco@ietf.org'"
	<megaco@ietf.org>
Subject: RE: [Megaco] optional parameters "ServiceChamgeAddress", "ImmAck"
Date: Tue, 28 Dec 2004 00:26:00 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

ImmAck is actually required when a Pending has been sent.  So there are
instances where the ImmAck is not optional.
 
Further, while these are optional to send, I believe implementations ought
to be expected to handle them if received.  So the receiver of these
parameters should have implemented the correct functionality as concerns the
parameters in question.
 
ImmAck only really comes into play in an ALF/UDP transport scenario -- it is
unnecessary when using a guaranteed-delivery transport.  The use of
ServiceChangeAddress is, I believe, cautioned against in the spec.  I
disagree that SCAddr is more common in actual use -- my experience shows
much more frequent use of ImmAck.
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Pellegrino Jose Luis
Sent: Monday, December 27, 2004 10:33 AM
To: 'megaco@ietf.org'
Subject: [Megaco] optional parameters "ServiceChamgeAddress", "ImmAck"




Hi, can anyone give me one opinion? 

In order to resolve interoperability multivendor, both, MG and MGC must
agree wich optional parameters are soported. 
For example, the ServiceChangeAddress is optional in Service Change. And so
is ImmAck in replay. So, because they are optional, may be that  many
vendors soport these parameters, and others doesn´t, so the interoperability
is not possible.

The question, if anybody can help me, is wich is the criteria to include
these parameters. 
  
Reading the "Megaco/h.248 call flows examples", we can find that
ServiceChangeAddress is used in ServiceChange,  but ImmAck is not. It seems
to be ServiceChangeAddress is more frecuently used than ImmAck. Am I right?

Best regards, 
José 
  


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Wed Dec 29 15:01:29 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05948
	for <megaco-archive@lists.ietf.org>; Wed, 29 Dec 2004 15:01:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cjjyt-0007NP-Dg; Wed, 29 Dec 2004 14:59:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cjjvg-0006YH-F5
	for megaco@megatron.ietf.org; Wed, 29 Dec 2004 14:56:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05598
	for <megaco@ietf.org>; Wed, 29 Dec 2004 14:56:18 -0500 (EST)
From: Albrecht.Schwarz@alcatel.de
Received: from mailrelay1.alcatel.de ([194.113.59.55]
	helo=mailrelay2.alcatel.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cjk6r-0007P8-3m
	for megaco@ietf.org; Wed, 29 Dec 2004 15:07:54 -0500
Received: from demail05.netfr.alcatel.fr (demail05.netfr.alcatel.fr
	[155.132.182.205])
	by mailrelay2.alcatel.de (8.12.11/8.12.10) with ESMTP id iBTJtjcR020798;
	Wed, 29 Dec 2004 20:55:45 +0100 (MET)
In-Reply-To: <B258A372CEA20246A363BB86753DB536EC13FD@zrtphxm2>
To: "Kevin Boyle" <kboyle@nortelnetworks.com>
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF8484DFDF.557B663D-ONC1256F79.006C4659-C1256F79.006D7927@netfr.alcatel.fr>
Date: Wed, 29 Dec 2004 20:55:43 +0100
X-MIMETrack: Serialize by Router on DEMAIL05/DE/ALCATEL(Release 5.0.12HF788 |
	September 23, 2004) at 12/29/2004 20:55:45
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
X-AES-MTA-scanned-and-authorized: yes
X-Spam-Score: 0.3 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: quoted-printable
Cc: megaco@ietf.org
Subject: [Megaco] SC Reasons 918, 919, 920
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable


Hi Kevin (or whoever may help)!
I'm currently reviewing our latest Annex F (TD39r1 WP2/16), I'm wonderi=
ng
where the ServiceChangeReasons above codepoint 917 were introduced. 919=
 &
920 are used in =A7 F.3.5. I couldn't find 918 up to now.
Could you please point me on the contributions, temporary documents or
background about these ServiceChangeReasons definitions.

Couldn't find them in my latest H.248.8, Amendment and H.248.1 Annex F
docs.

Thanks
Albrecht

=



_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Thu Dec 30 05:33:57 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00799
	for <megaco-archive@lists.ietf.org>; Thu, 30 Dec 2004 05:33:57 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjxbP-000237-8q; Thu, 30 Dec 2004 05:32:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjxVR-0000hy-5u
	for megaco@megatron.ietf.org; Thu, 30 Dec 2004 05:26:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29837
	for <megaco@ietf.org>; Thu, 30 Dec 2004 05:26:07 -0500 (EST)
From: Aliza.Nagauker@ecitele.com
Received: from ilsmtp01.ecitele.com ([147.234.1.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cjxgh-000459-1s
	for megaco@ietf.org; Thu, 30 Dec 2004 05:37:50 -0500
To: megaco@ietf.org
X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999
Message-ID: <OFC21071F5.119D6A02-ONC2256F7A.0036955E@ecitele.com>
Date: Thu, 30 Dec 2004 12:25:57 +0200
X-MIMETrack: Serialize by Router on ILSMTP01/ECI Telecom(Release 6.5.1|January
	21, 2004) at 12/30/2004 12:30:23
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: [Megaco] extended packages.
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org





Hello,

I have a question regarding extended packages.
Consider the following packages example: al , xal

Are the basic events ALWAYS refered with the basic package (al/on) and ONLY
the extendet event/signals refered with the extended package (xal/las)?

If MG supports xal package:
1. When MGC instructs MG to detect event or send signals will it refer ONLY
with xal package name? (e.g: xal/on , xal/off) or it may also refer with
al/on?
2. In Audit capabilities, does the MG has to report "al" package as well as
"xal" package? or reporting "xal" is enough?
3. In case that  only "xal" was reported, can the MGC still refer MG with
"al" package's event/signals? (e.g al/on), or it will use xal package to
refer these events?

I'll appreciate your help on the above.

Thanks, Aliza





_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Thu Dec 30 08:59:58 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13366
	for <megaco-archive@lists.ietf.org>; Thu, 30 Dec 2004 08:59:58 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ck0n2-0000Cy-Uk; Thu, 30 Dec 2004 08:56:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ck0i6-00080a-92
	for megaco@megatron.ietf.org; Thu, 30 Dec 2004 08:51:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12962
	for <megaco@ietf.org>; Thu, 30 Dec 2004 08:51:24 -0500 (EST)
From: Jean-Luc.Lecuyer@alcatel.fr
Received: from smail3.alcatel.fr ([194.133.58.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ck0tQ-0000Pg-1u
	for megaco@ietf.org; Thu, 30 Dec 2004 09:03:09 -0500
Received: from frmail26.netfr.alcatel.fr (frmail26.netfr.alcatel.fr
	[155.132.182.156])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id iBUDopqO002762;
	Thu, 30 Dec 2004 14:50:51 +0100
In-Reply-To: <OFC21071F5.119D6A02-ONC2256F7A.0036955E@ecitele.com>
Subject: Re: [Megaco] extended packages.
To: Aliza.Nagauker@ecitele.com
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OFE01CF88D.63EE0044-ONC1256F7A.004B632B-C1256F7A.004C1124@netfr.alcatel.fr>
Date: Thu, 30 Dec 2004 14:50:50 +0100
X-MIMETrack: Serialize by Router on FRMAIL26/FR/ALCATEL(Release 5.0.12HF788 |
	September 23, 2004) at 12/30/2004 14:50:50
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-Alcanet-MTA-scanned-and-authorized: yes
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org



Hello,

>From my understanding see my answers in your mail.

Regards
Jean-Luc




Aliza.Nagauker@ecitele.com@ietf.org on 30/12/2004 11:25:57

Sent by:    megaco-bounces@ietf.org


To:    megaco@ietf.org
cc:
Subject:    [Megaco] extended packages.






Hello,

I have a question regarding extended packages.
Consider the following packages example: al , xal

Are the basic events ALWAYS refered with the basic package (al/on) and ONLY
the extendet event/signals refered with the extended package (xal/las)?
JLR : no you can you use the extented package as well. The rule is that
event/signals existing in the basic package can be refered with the basic
package or the extended package. Event/signals defined in the extended
package can be refered of course only with the extended package.

If MG supports xal package:
1. When MGC instructs MG to detect event or send signals will it refer ONLY
with xal package name? (e.g: xal/on , xal/off) or it may also refer with
al/on?
JLR : both are valid and equivalent and should be accepted by the MG

2. In Audit capabilities, does the MG has to report "al" package as well as
"xal" package? or reporting "xal" is enough?
JLR : both are valid and equivalent and should be accepted by the MGC

3. In case that  only "xal" was reported, can the MGC still refer MG with
"al" package's event/signals? (e.g al/on), or it will use xal package to
refer these events?
JLR : both are valid and equivalent and should be accepted by the MG

I'll appreciate your help on the above.

Thanks, Aliza





_______________________________________________
Megaco mailing list
Megaco@ietf.org
 https://www1.ietf.org/mailman/listinfo/megaco





_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Thu Dec 30 11:01:22 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23148
	for <megaco-archive@lists.ietf.org>; Thu, 30 Dec 2004 11:01:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ck2e8-0005Gp-DJ; Thu, 30 Dec 2004 10:55:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ck2a4-00043i-7d
	for megaco@megatron.ietf.org; Thu, 30 Dec 2004 10:51:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22532
	for <megaco@ietf.org>; Thu, 30 Dec 2004 10:51:14 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ck2lQ-0003Kl-8W
	for megaco@ietf.org; Thu, 30 Dec 2004 11:03:00 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iBUFogL27022
	for <megaco@ietf.org>; Thu, 30 Dec 2004 10:50:43 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Y0S9K5AV>; Thu, 30 Dec 2004 10:50:43 -0500
Message-ID: <B258A372CEA20246A363BB86753DB53601846D97@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Jean-Luc.Lecuyer@alcatel.fr, Aliza.Nagauker@ecitele.com
Subject: RE: [Megaco] extended packages.
Date: Thu, 30 Dec 2004 10:50:32 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

Note that the additional signals, etc. in the extension package may only be
referred to by the extension package.  For example, xal/las cannot be
referred to by the al package name.

Also keep in mind that extensions to parameter values can only be referred
to by the extension package name.  If I had a property a/prop that took
values 1,2,3,4 and then defined an extension package b that added values 5
and 6 for prop, then 5 and 6 may only be used with b/prop.

Kevin

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Jean-Luc.Lecuyer@alcatel.fr
Sent: Thursday, December 30, 2004 8:51 AM
To: Aliza.Nagauker@ecitele.com
Cc: megaco@ietf.org
Subject: Re: [Megaco] extended packages.



Hello,

>From my understanding see my answers in your mail.

Regards
Jean-Luc




Aliza.Nagauker@ecitele.com@ietf.org on 30/12/2004 11:25:57

Sent by:    megaco-bounces@ietf.org


To:    megaco@ietf.org
cc:
Subject:    [Megaco] extended packages.






Hello,

I have a question regarding extended packages.
Consider the following packages example: al , xal

Are the basic events ALWAYS refered with the basic package (al/on) and ONLY
the extendet event/signals refered with the extended package (xal/las)?
JLR : no you can you use the extented package as well. The rule is that
event/signals existing in the basic package can be refered with the basic
package or the extended package. Event/signals defined in the extended
package can be refered of course only with the extended package.

If MG supports xal package:
1. When MGC instructs MG to detect event or send signals will it refer ONLY
with xal package name? (e.g: xal/on , xal/off) or it may also refer with
al/on?
JLR : both are valid and equivalent and should be accepted by the MG

2. In Audit capabilities, does the MG has to report "al" package as well as
"xal" package? or reporting "xal" is enough?
JLR : both are valid and equivalent and should be accepted by the MGC

3. In case that  only "xal" was reported, can the MGC still refer MG with
"al" package's event/signals? (e.g al/on), or it will use xal package to
refer these events?
JLR : both are valid and equivalent and should be accepted by the MG

I'll appreciate your help on the above.

Thanks, Aliza





_______________________________________________
Megaco mailing list
Megaco@ietf.org
 https://www1.ietf.org/mailman/listinfo/megaco





_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Fri Dec 31 00:39:48 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18067
	for <megaco-archive@lists.ietf.org>; Fri, 31 Dec 2004 00:39:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CkFNl-00056w-SM; Fri, 31 Dec 2004 00:31:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CkFHS-00033i-MR
	for megaco@megatron.ietf.org; Fri, 31 Dec 2004 00:24:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17364
	for <megaco@ietf.org>; Fri, 31 Dec 2004 00:24:51 -0500 (EST)
From: bvswamy@hssworld.com
Received: from spark.hss.co.in ([203.200.71.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CkFSe-0006ix-F8
	for megaco@ietf.org; Fri, 31 Dec 2004 00:36:46 -0500
Received: from spark.hss.co.in (localhost [127.0.0.1])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iBV5KWpX020879
	for <megaco@ietf.org>; Fri, 31 Dec 2004 10:50:34 +0530 (IST)
Received: from webmail.hss.hns.com (webmail.hss.hns.com [192.168.100.50])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iBV5KUI4020846;
	Fri, 31 Dec 2004 10:50:30 +0530 (IST)
In-Reply-To: <OFE01CF88D.63EE0044-ONC1256F7A.004B632B-C1256F7A.004C1124@netfr.alcatel.fr>
Subject: Re: [Megaco] extended packages.
To: Jean-Luc.Lecuyer@alcatel.fr
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF97367191.4707CD5F-ON65256F7B.001C2585-65256F7B.001DDB2B@hssworld.com>
Date: Fri, 31 Dec 2004 10:48:01 +0530
X-MIMETrack: Serialize by Router on WebMail/HSS(Release 6.5.1|January 21,
	2004) at 12/31/2004 10:48:04 AM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org






Hi all

Just to highlight one more things relating point 3 below is that as per the
protocol (H248.1 V2 May 2002) Sec 6.2.3,para 5
It is mandatory for the MG to support Base package , however it is optional
to publish the base package as an allowed interface through the Audit
procedure.
So if MG has not published the base package  then MGC should not send AL/ON
and only XAL/ON is valid.

regards
B Venkat S.R Swamy
Senior Technical Leader
Hughes Software Systems
Phone:  +91-124-2455555 Extn 3620
Fax: +91-124-2455345
web: www.hssworld.com



                                                                           
             Jean-Luc.Lecuyer@                                             
             alcatel.fr                                                    
             Sent by:                                                   To 
             megaco-bounces@ie         Aliza.Nagauker@ecitele.com          
             tf.org                                                     cc 
                                       megaco@ietf.org                     
                                                                   Subject 
             12/30/2004 07:20          Re: [Megaco] extended packages.     
             PM                                                            
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           






Hello,

>From my understanding see my answers in your mail.

Regards
Jean-Luc




Aliza.Nagauker@ecitele.com@ietf.org on 30/12/2004 11:25:57

Sent by:    megaco-bounces@ietf.org


To:    megaco@ietf.org
cc:
Subject:    [Megaco] extended packages.






Hello,

I have a question regarding extended packages.
Consider the following packages example: al , xal

Are the basic events ALWAYS refered with the basic package (al/on) and ONLY
the extendet event/signals refered with the extended package (xal/las)?
JLR : no you can you use the extented package as well. The rule is that
event/signals existing in the basic package can be refered with the basic
package or the extended package. Event/signals defined in the extended
package can be refered of course only with the extended package.

If MG supports xal package:
1. When MGC instructs MG to detect event or send signals will it refer ONLY
with xal package name? (e.g: xal/on , xal/off) or it may also refer with
al/on?
JLR : both are valid and equivalent and should be accepted by the MG

2. In Audit capabilities, does the MG has to report "al" package as well as
"xal" package? or reporting "xal" is enough?
JLR : both are valid and equivalent and should be accepted by the MGC

3. In case that  only "xal" was reported, can the MGC still refer MG with
"al" package's event/signals? (e.g al/on), or it will use xal package to
refer these events?
JLR : both are valid and equivalent and should be accepted by the MG

I'll appreciate your help on the above.

Thanks, Aliza





_______________________________________________
Megaco mailing list
Megaco@ietf.org
 https://www1.ietf.org/mailman/listinfo/megaco





_______________________________________________
Megaco mailing list
Megaco@ietf.org
 https://www1.ietf.org/mailman/listinfo/megaco


 ***********************  HSS-Restricted   ***********************


"Please note:  The email domain of Hughes Software Systems Ltd. has
been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems
Limited (HSS) and is intended solely for the use of the  individual
to whom it is addressed. It may contain  privileged or confidential
information and  should not be  circulated or  used for any purpose
other than for what  it is intended.  If  you have   received  this
message in  error, please notify the originator immediately. If you
are   not the  intended recipient, you are  notified  that  you are
strictly  prohibited  from  using, copying, altering, or disclosing
the contents of this message.  HSS  accepts no  responsibility  for
loss or damage arising from the use of  the information transmitted
by this email including damage from virus."

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From megaco-bounces@ietf.org  Fri Dec 31 01:21:22 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20179
	for <megaco-archive@lists.ietf.org>; Fri, 31 Dec 2004 01:21:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CkFtz-0003aw-8b; Fri, 31 Dec 2004 01:04:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CkFj2-0001mP-4Z
	for megaco@megatron.ietf.org; Fri, 31 Dec 2004 00:53:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18727
	for <megaco@ietf.org>; Fri, 31 Dec 2004 00:53:20 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CkFuV-0007OV-9p
	for megaco@ietf.org; Fri, 31 Dec 2004 01:05:15 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iBV5qog13779
	for <megaco@ietf.org>; Fri, 31 Dec 2004 00:52:50 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Y0S9LCTG>; Fri, 31 Dec 2004 00:52:50 -0500
Message-ID: <B258A372CEA20246A363BB86753DB53601846E54@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: bvswamy@hssworld.com, Jean-Luc.Lecuyer@alcatel.fr
Subject: RE: [Megaco] extended packages.
Date: Fri, 31 Dec 2004 00:52:46 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

For packages meant only to be extended, or for some of the more interesting
packages like the phrase and variable syntax packages in H.248.9, there is
no point in publishing them, since the MGC cannot use those packages to
control the MG.  For all other packages, why would the MG limit use to just
the extension package?  What if the MGC doesn't support the extension
package but DOES support the base package?  In that particular scenario, the
MG will lose all the capabilities of not only the extension package, but the
base package as well!

It seems to me that choosing not to publish the base package in the package
audit response is a poor design choice for MGs.

Kevin

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
bvswamy@hssworld.com
Sent: Friday, December 31, 2004 12:18 AM
To: Jean-Luc.Lecuyer@alcatel.fr
Cc: megaco@ietf.org
Subject: Re: [Megaco] extended packages.






Hi all

Just to highlight one more things relating point 3 below is that as per the
protocol (H248.1 V2 May 2002) Sec 6.2.3,para 5 It is mandatory for the MG to
support Base package , however it is optional to publish the base package as
an allowed interface through the Audit procedure.
So if MG has not published the base package  then MGC should not send AL/ON
and only XAL/ON is valid.

regards
B Venkat S.R Swamy
Senior Technical Leader
Hughes Software Systems
Phone:  +91-124-2455555 Extn 3620
Fax: +91-124-2455345
web: www.hssworld.com



                                                                           
             Jean-Luc.Lecuyer@                                             
             alcatel.fr                                                    
             Sent by:                                                   To 
             megaco-bounces@ie         Aliza.Nagauker@ecitele.com          
             tf.org                                                     cc 
                                       megaco@ietf.org                     
                                                                   Subject 
             12/30/2004 07:20          Re: [Megaco] extended packages.     
             PM                                                            
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           






Hello,

>From my understanding see my answers in your mail.

Regards
Jean-Luc




Aliza.Nagauker@ecitele.com@ietf.org on 30/12/2004 11:25:57

Sent by:    megaco-bounces@ietf.org


To:    megaco@ietf.org
cc:
Subject:    [Megaco] extended packages.






Hello,

I have a question regarding extended packages.
Consider the following packages example: al , xal

Are the basic events ALWAYS refered with the basic package (al/on) and ONLY
the extendet event/signals refered with the extended package (xal/las)?
JLR : no you can you use the extented package as well. The rule is that
event/signals existing in the basic package can be refered with the basic
package or the extended package. Event/signals defined in the extended
package can be refered of course only with the extended package.

If MG supports xal package:
1. When MGC instructs MG to detect event or send signals will it refer ONLY
with xal package name? (e.g: xal/on , xal/off) or it may also refer with
al/on?
JLR : both are valid and equivalent and should be accepted by the MG

2. In Audit capabilities, does the MG has to report "al" package as well as
"xal" package? or reporting "xal" is enough?
JLR : both are valid and equivalent and should be accepted by the MGC

3. In case that  only "xal" was reported, can the MGC still refer MG with
"al" package's event/signals? (e.g al/on), or it will use xal package to
refer these events?
JLR : both are valid and equivalent and should be accepted by the MG

I'll appreciate your help on the above.

Thanks, Aliza





_______________________________________________
Megaco mailing list
Megaco@ietf.org
 https://www1.ietf.org/mailman/listinfo/megaco





_______________________________________________
Megaco mailing list
Megaco@ietf.org
 https://www1.ietf.org/mailman/listinfo/megaco


 ***********************  HSS-Restricted   ***********************


"Please note:  The email domain of Hughes Software Systems Ltd. has been
changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended solely for the use of the  individual to whom it is
addressed. It may contain  privileged or confidential information and
should not be  circulated or  used for any purpose
other than for what  it is intended.  If  you have   received  this
message in  error, please notify the originator immediately. If you
are   not the  intended recipient, you are  notified  that  you are
strictly  prohibited  from  using, copying, altering, or disclosing the
contents of this message.  HSS  accepts no  responsibility  for loss or
damage arising from the use of  the information transmitted by this email
including damage from virus."

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


