From megaco-admin@ietf.org Sun Nov 2 19:31:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00738 for ; Sun, 2 Nov 2003 19:31:27 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGScY-0003B2-8F; Sun, 02 Nov 2003 19:31:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGSc3-0003AP-Dn for megaco@optimus.ietf.org; Sun, 02 Nov 2003 19:30:31 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00712 for ; Sun, 2 Nov 2003 19:30:19 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGSc1-0004kO-00 for megaco@ietf.org; Sun, 02 Nov 2003 19:30:29 -0500 Received: from law15-f69.law15.hotmail.com ([64.4.23.69] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 1AGSc1-0004jv-00 for megaco@ietf.org; Sun, 02 Nov 2003 19:30:29 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 2 Nov 2003 16:29:59 -0800 Received: from 210.21.224.54 by lw15fd.law15.hotmail.msn.com with HTTP; Mon, 03 Nov 2003 00:29:58 GMT X-Originating-IP: [210.21.224.54] X-Originating-Email: [juniperfu@hotmail.com] From: "å® ä»" To: megaco@ietf.org Date: Mon, 03 Nov 2003 08:29:58 +0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 03 Nov 2003 00:29:59.0346 (UTC) FILETIME=[9D112920:01C3A1A1] Subject: [Megaco] a problem about audit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , All, When MGC restart or HA, Maybe it need audit the context and termination of MG, and it can send the command Context = * { AuditValue= ROOT {Audit { } } and the MG should return Context = 100 { AuditValue= TermA, TermB } Context = 200 { AuditValue= TermC, TermD } Context = 300 { AuditValue= TermE, TermF } And my problem is if the MG has a lot of context and a megaco message can't include them, So how do the mg return all its context, thanks! Mark _________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Sun Nov 2 19:31:28 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00764 for ; Sun, 2 Nov 2003 19:31:28 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGScg-0003Bv-E4 for megaco-archive@odin.ietf.org; Sun, 02 Nov 2003 19:31:10 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA30VAeY012261 for megaco-archive@odin.ietf.org; Sun, 2 Nov 2003 19:31:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGScg-0003Bg-9E for megaco-web-archive@optimus.ietf.org; Sun, 02 Nov 2003 19:31:10 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00719 for ; Sun, 2 Nov 2003 19:30:58 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGSce-0004kd-00 for megaco-web-archive@ietf.org; Sun, 02 Nov 2003 19:31:08 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AGSce-0004kZ-00 for megaco-web-archive@ietf.org; Sun, 02 Nov 2003 19:31:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGScY-0003B2-8F; Sun, 02 Nov 2003 19:31:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGSc3-0003AP-Dn for megaco@optimus.ietf.org; Sun, 02 Nov 2003 19:30:31 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00712 for ; Sun, 2 Nov 2003 19:30:19 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGSc1-0004kO-00 for megaco@ietf.org; Sun, 02 Nov 2003 19:30:29 -0500 Received: from law15-f69.law15.hotmail.com ([64.4.23.69] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 1AGSc1-0004jv-00 for megaco@ietf.org; Sun, 02 Nov 2003 19:30:29 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 2 Nov 2003 16:29:59 -0800 Received: from 210.21.224.54 by lw15fd.law15.hotmail.msn.com with HTTP; Mon, 03 Nov 2003 00:29:58 GMT X-Originating-IP: [210.21.224.54] X-Originating-Email: [juniperfu@hotmail.com] From: "å® ä»" To: megaco@ietf.org Date: Mon, 03 Nov 2003 08:29:58 +0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 03 Nov 2003 00:29:59.0346 (UTC) FILETIME=[9D112920:01C3A1A1] Subject: [Megaco] a problem about audit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , All, When MGC restart or HA, Maybe it need audit the context and termination of MG, and it can send the command Context = * { AuditValue= ROOT {Audit { } } and the MG should return Context = 100 { AuditValue= TermA, TermB } Context = 200 { AuditValue= TermC, TermD } Context = 300 { AuditValue= TermE, TermF } And my problem is if the MG has a lot of context and a megaco message can't include them, So how do the mg return all its context, thanks! Mark _________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Sun Nov 2 22:49:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05227 for ; Sun, 2 Nov 2003 22:49:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGVi9-0001qw-HS; Sun, 02 Nov 2003 22:49:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGVhT-0001nr-VT for megaco@optimus.ietf.org; Sun, 02 Nov 2003 22:48:19 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05204 for ; Sun, 2 Nov 2003 22:48:07 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGVhQ-0006tc-00 for megaco@ietf.org; Sun, 02 Nov 2003 22:48:16 -0500 Received: from [203.197.168.150] (helo=mailscanout256k.tataelxsi.co.in) by ietf-mx with smtp (Exim 4.12) id 1AGVhP-0006tZ-00 for megaco@ietf.org; Sun, 02 Nov 2003 22:48:15 -0500 Received: FROM vscaninternal.tataelxsi.co.in BY mailscanout256k.tataelxsi.co.in ; Mon Nov 03 09:20:14 2003 +0500 Received: FROM bsh BY vscaninternal.tataelxsi.co.in ; Mon Nov 03 09:19:44 2003 +0500 From: "Shridhara B" To: Date: Mon, 3 Nov 2003 09:19:25 +0530 Message-ID: <000c01c3a1bd$7a36d2d0$d528010a@telxsi.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 CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 Content-Transfer-Encoding: 7bit Subject: [Megaco] Query on ITU-T ATME No. 2 test line response package defined in H.248.17 Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hello, Could any one of you please clarify the following? The parameterID 'resp' defined in the above package takes 3 possible values, "type_a", "type_b" and for the third one reference to 8.1.1.7 is given. But section 8.1.1.7 gives only the description. Can we assume "type_c" string for the third possible value? If no, what string we should be using? Also can we assume (0x0003) value for this? Thanks in advance. - Shridhara.B _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Sun Nov 2 22:49:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05242 for ; Sun, 2 Nov 2003 22:49:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGViF-0001rm-1y for megaco-archive@odin.ietf.org; Sun, 02 Nov 2003 22:49:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA33n713007168 for megaco-archive@odin.ietf.org; Sun, 2 Nov 2003 22:49:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGViE-0001rX-UB for megaco-web-archive@optimus.ietf.org; Sun, 02 Nov 2003 22:49:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05215 for ; Sun, 2 Nov 2003 22:48:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGViB-0006tu-00 for megaco-web-archive@ietf.org; Sun, 02 Nov 2003 22:49:03 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AGViB-0006tr-00 for megaco-web-archive@ietf.org; Sun, 02 Nov 2003 22:49:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGVi9-0001qw-HS; Sun, 02 Nov 2003 22:49:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGVhT-0001nr-VT for megaco@optimus.ietf.org; Sun, 02 Nov 2003 22:48:19 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05204 for ; Sun, 2 Nov 2003 22:48:07 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGVhQ-0006tc-00 for megaco@ietf.org; Sun, 02 Nov 2003 22:48:16 -0500 Received: from [203.197.168.150] (helo=mailscanout256k.tataelxsi.co.in) by ietf-mx with smtp (Exim 4.12) id 1AGVhP-0006tZ-00 for megaco@ietf.org; Sun, 02 Nov 2003 22:48:15 -0500 Received: FROM vscaninternal.tataelxsi.co.in BY mailscanout256k.tataelxsi.co.in ; Mon Nov 03 09:20:14 2003 +0500 Received: FROM bsh BY vscaninternal.tataelxsi.co.in ; Mon Nov 03 09:19:44 2003 +0500 From: "Shridhara B" To: Date: Mon, 3 Nov 2003 09:19:25 +0530 Message-ID: <000c01c3a1bd$7a36d2d0$d528010a@telxsi.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 CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 Content-Transfer-Encoding: 7bit Subject: [Megaco] Query on ITU-T ATME No. 2 test line response package defined in H.248.17 Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello, Could any one of you please clarify the following? The parameterID 'resp' defined in the above package takes 3 possible values, "type_a", "type_b" and for the third one reference to 8.1.1.7 is given. But section 8.1.1.7 gives only the description. Can we assume "type_c" string for the third possible value? If no, what string we should be using? Also can we assume (0x0003) value for this? Thanks in advance. - Shridhara.B _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Mon Nov 3 09:07:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02239 for ; Mon, 3 Nov 2003 09:07:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGfME-0007Be-4X; Mon, 03 Nov 2003 09:07:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGZAm-0003VV-0R for megaco@optimus.ietf.org; Mon, 03 Nov 2003 02:30:48 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22599 for ; Mon, 3 Nov 2003 02:30:37 -0500 (EST) From: Eli.Liluz@veraznetworks.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGZAi-0001Ux-00 for megaco@ietf.org; Mon, 03 Nov 2003 02:30:44 -0500 Received: from mink.ecitele.com ([147.234.1.100]) by ietf-mx with esmtp (Exim 4.12) id 1AGZAh-0001Ut-00 for megaco@ietf.org; Mon, 03 Nov 2003 02:30:43 -0500 Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125]) by mink.ecitele.com (8.12.10+Sun/8.12.10) with ESMTP id hA37PI4D013318 for ; Mon, 3 Nov 2003 09:25:20 +0200 (IST) To: megaco@ietf.org X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999 Message-ID: Date: Mon, 3 Nov 2003 09:30:35 +0200 X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at 11/03/2003 09:30:47 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Subject: [Megaco] Cmd and ack issue. Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Hi all. Let us assume that MG sends an SVC restart to MGC#1 and receives a reply for this command from MGC#2. Both MGC#1 and MGC#2 are valid from MG point of view. Is it legal that MGC#2 answers to a command that was sent to MGC#1 ? Is there any special procedure that shell be taken from the MG as a result of such scenario ? Thank you, Eli Liluz. _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Mon Nov 3 09:07:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02254 for ; Mon, 3 Nov 2003 09:07:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGfMH-0007DH-Hm for megaco-archive@odin.ietf.org; Mon, 03 Nov 2003 09:07:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA3E74s2027709 for megaco-archive@odin.ietf.org; Mon, 3 Nov 2003 09:07:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGfMG-0007Cq-Hy for megaco-web-archive@optimus.ietf.org; Mon, 03 Nov 2003 09:07:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02233 for ; Mon, 3 Nov 2003 09:06:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGfME-00061h-00 for megaco-web-archive@ietf.org; Mon, 03 Nov 2003 09:07:03 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AGfME-00061e-00 for megaco-web-archive@ietf.org; Mon, 03 Nov 2003 09:07:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGfME-0007Be-4X; Mon, 03 Nov 2003 09:07:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGZAm-0003VV-0R for megaco@optimus.ietf.org; Mon, 03 Nov 2003 02:30:48 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22599 for ; Mon, 3 Nov 2003 02:30:37 -0500 (EST) From: Eli.Liluz@veraznetworks.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGZAi-0001Ux-00 for megaco@ietf.org; Mon, 03 Nov 2003 02:30:44 -0500 Received: from mink.ecitele.com ([147.234.1.100]) by ietf-mx with esmtp (Exim 4.12) id 1AGZAh-0001Ut-00 for megaco@ietf.org; Mon, 03 Nov 2003 02:30:43 -0500 Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125]) by mink.ecitele.com (8.12.10+Sun/8.12.10) with ESMTP id hA37PI4D013318 for ; Mon, 3 Nov 2003 09:25:20 +0200 (IST) To: megaco@ietf.org X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999 Message-ID: Date: Mon, 3 Nov 2003 09:30:35 +0200 X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at 11/03/2003 09:30:47 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Subject: [Megaco] Cmd and ack issue. Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Hi all. Let us assume that MG sends an SVC restart to MGC#1 and receives a reply for this command from MGC#2. Both MGC#1 and MGC#2 are valid from MG point of view. Is it legal that MGC#2 answers to a command that was sent to MGC#1 ? Is there any special procedure that shell be taken from the MG as a result of such scenario ? Thank you, Eli Liluz. _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Mon Nov 3 15:47:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20523 for ; Mon, 3 Nov 2003 15:47:28 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGlbJ-0005ec-EU; Mon, 03 Nov 2003 15:47:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGlaK-0005dX-VZ for megaco@optimus.ietf.org; Mon, 03 Nov 2003 15:46:01 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20483 for ; Mon, 3 Nov 2003 15:45:33 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGla2-0004F2-00 for megaco@ietf.org; Mon, 03 Nov 2003 15:45:42 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AGla2-0004Es-00 for megaco@ietf.org; Mon, 03 Nov 2003 15:45:42 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA3Kj5U03333 for ; Mon, 3 Nov 2003 15:45:06 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 3 Nov 2003 15:45:05 -0500 Message-ID: From: "Kevin Boyle" To: Eli.Liluz@veraznetworks.com, megaco@ietf.org Subject: RE: [Megaco] Cmd and ack issue. Date: Mon, 3 Nov 2003 15:44:59 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , MGC2 may not respond to this message. If MGC2 is not the Primary MGC, as the MG, I would assume this was misdirected messaging at best, and an attack at worst. Kevin -----Original Message----- From: Eli.Liluz@veraznetworks.com [mailto:Eli.Liluz@veraznetworks.com] Sent: Monday, November 03, 2003 2:31 AM To: megaco@ietf.org Subject: [Megaco] Cmd and ack issue. Hi all. Let us assume that MG sends an SVC restart to MGC#1 and receives a reply for this command from MGC#2. Both MGC#1 and MGC#2 are valid from MG point of view. Is it legal that MGC#2 answers to a command that was sent to MGC#1 ? Is there any special procedure that shell be taken from the MG as a result of such scenario ? Thank you, Eli Liluz. _______________________________________________ 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 exim@www1.ietf.org Mon Nov 3 16:35:07 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20522 for ; Mon, 3 Nov 2003 15:47:28 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGlbQ-0005fr-MY for megaco-archive@odin.ietf.org; Mon, 03 Nov 2003 15:47:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA3Kl8bD021805 for megaco-archive@odin.ietf.org; Mon, 3 Nov 2003 15:47:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGlbQ-0005fY-IM for megaco-web-archive@optimus.ietf.org; Mon, 03 Nov 2003 15:47:08 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20512 for ; Mon, 3 Nov 2003 15:46:58 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGlbO-0004G0-00 for megaco-web-archive@ietf.org; Mon, 03 Nov 2003 15:47:06 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AGlbO-0004Fx-00 for megaco-web-archive@ietf.org; Mon, 03 Nov 2003 15:47:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGlbJ-0005ec-EU; Mon, 03 Nov 2003 15:47:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGlaK-0005dX-VZ for megaco@optimus.ietf.org; Mon, 03 Nov 2003 15:46:01 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20483 for ; Mon, 3 Nov 2003 15:45:33 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGla2-0004F2-00 for megaco@ietf.org; Mon, 03 Nov 2003 15:45:42 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AGla2-0004Es-00 for megaco@ietf.org; Mon, 03 Nov 2003 15:45:42 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA3Kj5U03333 for ; Mon, 3 Nov 2003 15:45:06 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 3 Nov 2003 15:45:05 -0500 Message-ID: From: "Kevin Boyle" To: Eli.Liluz@veraznetworks.com, megaco@ietf.org Subject: RE: [Megaco] Cmd and ack issue. Date: Mon, 3 Nov 2003 15:44:59 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , MGC2 may not respond to this message. If MGC2 is not the Primary MGC, as the MG, I would assume this was misdirected messaging at best, and an attack at worst. Kevin -----Original Message----- From: Eli.Liluz@veraznetworks.com [mailto:Eli.Liluz@veraznetworks.com] Sent: Monday, November 03, 2003 2:31 AM To: megaco@ietf.org Subject: [Megaco] Cmd and ack issue. Hi all. Let us assume that MG sends an SVC restart to MGC#1 and receives a reply for this command from MGC#2. Both MGC#1 and MGC#2 are valid from MG point of view. Is it legal that MGC#2 answers to a command that was sent to MGC#1 ? Is there any special procedure that shell be taken from the MG as a result of such scenario ? Thank you, Eli Liluz. _______________________________________________ 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-admin@ietf.org Mon Nov 3 16:48:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23740 for ; Mon, 3 Nov 2003 16:48:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGmYL-0001Ej-0h; Mon, 03 Nov 2003 16:48:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGmXf-0001DU-R6 for megaco@optimus.ietf.org; Mon, 03 Nov 2003 16:47:19 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23567 for ; Mon, 3 Nov 2003 16:47:08 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGmXd-0005QC-00 for megaco@ietf.org; Mon, 03 Nov 2003 16:47:17 -0500 Received: from motgate5.mot.com ([144.189.100.105]) by ietf-mx with esmtp (Exim 4.12) id 1AGmXc-0005Q1-00 for megaco@ietf.org; Mon, 03 Nov 2003 16:47:16 -0500 Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132]) by motgate5.mot.com (Motorola/Motgate5) with ESMTP id hA3LlG1N020636 for ; Mon, 3 Nov 2003 14:47:16 -0700 (MST) Received: from smilevm.motorola.com ([10.14.25.162]) by il06exr02.mot.com (Motorola/il06exr02) with ESMTP id hA3LjnLw005026 for ; Mon, 3 Nov 2003 15:45:49 -0600 Message-Id: <5.2.1.1.0.20031103161345.02936800@IL06EXM13.corp.mot.com> X-Sender: A19776@IL06EXM13.corp.mot.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Mon, 03 Nov 2003 16:44:22 -0500 To: megaco@ietf.org From: Aleksandr Ryabin Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Megaco] Megaco MIB: medGwyPropertyProfileTable property OIDs Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Hi, In the latest MEGACO MIB draft http://www.ietf.org/internet-drafts/draft-ietf-megaco-mib-05.txt on page 22 in description of medGwyPropertyProfileTable there is a following statement: "-- (3) Each Property is defined as an Object Identifer in the various -- Package Mibs (like MEGACO-TONES-MIB etc)." I take it is a reference to expired "Tones MIB" draft, which can be found at: http://www.watersprings.org/pub/id/draft-doyle-megaco-tonesmib-00.txt Is there any other expired, or non-expired documents ever produced to be used for above MEGACO MIB table? Is there any work currently done, or planned to be done to define MIBs for any packages? Thanks Aleks _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Mon Nov 3 16:48:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23755 for ; Mon, 3 Nov 2003 16:48:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGmYO-0001FW-6o for megaco-archive@odin.ietf.org; Mon, 03 Nov 2003 16:48:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA3Lm4x4004798 for megaco-archive@odin.ietf.org; Mon, 3 Nov 2003 16:48:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGmYO-0001FJ-2W for megaco-web-archive@optimus.ietf.org; Mon, 03 Nov 2003 16:48:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23685 for ; Mon, 3 Nov 2003 16:47:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGmYL-0005Sa-00 for megaco-web-archive@ietf.org; Mon, 03 Nov 2003 16:48:02 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AGmYL-0005SX-00 for megaco-web-archive@ietf.org; Mon, 03 Nov 2003 16:48:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGmYL-0001Ej-0h; Mon, 03 Nov 2003 16:48:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGmXf-0001DU-R6 for megaco@optimus.ietf.org; Mon, 03 Nov 2003 16:47:19 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23567 for ; Mon, 3 Nov 2003 16:47:08 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGmXd-0005QC-00 for megaco@ietf.org; Mon, 03 Nov 2003 16:47:17 -0500 Received: from motgate5.mot.com ([144.189.100.105]) by ietf-mx with esmtp (Exim 4.12) id 1AGmXc-0005Q1-00 for megaco@ietf.org; Mon, 03 Nov 2003 16:47:16 -0500 Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132]) by motgate5.mot.com (Motorola/Motgate5) with ESMTP id hA3LlG1N020636 for ; Mon, 3 Nov 2003 14:47:16 -0700 (MST) Received: from smilevm.motorola.com ([10.14.25.162]) by il06exr02.mot.com (Motorola/il06exr02) with ESMTP id hA3LjnLw005026 for ; Mon, 3 Nov 2003 15:45:49 -0600 Message-Id: <5.2.1.1.0.20031103161345.02936800@IL06EXM13.corp.mot.com> X-Sender: A19776@IL06EXM13.corp.mot.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Mon, 03 Nov 2003 16:44:22 -0500 To: megaco@ietf.org From: Aleksandr Ryabin Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Megaco] Megaco MIB: medGwyPropertyProfileTable property OIDs Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Hi, In the latest MEGACO MIB draft http://www.ietf.org/internet-drafts/draft-ietf-megaco-mib-05.txt on page 22 in description of medGwyPropertyProfileTable there is a following statement: "-- (3) Each Property is defined as an Object Identifer in the various -- Package Mibs (like MEGACO-TONES-MIB etc)." I take it is a reference to expired "Tones MIB" draft, which can be found at: http://www.watersprings.org/pub/id/draft-doyle-megaco-tonesmib-00.txt Is there any other expired, or non-expired documents ever produced to be used for above MEGACO MIB table? Is there any work currently done, or planned to be done to define MIBs for any packages? Thanks Aleks _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Wed Nov 5 08:15:48 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04483 for ; Wed, 5 Nov 2003 08:15:48 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHNV3-0008Rn-5f; Wed, 05 Nov 2003 08:15:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHNUw-0008II-Rr for megaco@optimus.ietf.org; Wed, 05 Nov 2003 08:14:58 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04373 for ; Wed, 5 Nov 2003 08:14:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHNUv-0003jT-00 for megaco@ietf.org; Wed, 05 Nov 2003 08:14:57 -0500 Received: from zcars0m9.nortelnetworks.com ([47.129.242.157]) by ietf-mx with esmtp (Exim 4.12) id 1AHNUv-0003i0-00 for megaco@ietf.org; Wed, 05 Nov 2003 08:14:57 -0500 Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA5DEPC17789 for ; Wed, 5 Nov 2003 08:14:25 -0500 (EST) Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id VRTPF9QK; Wed, 5 Nov 2003 08:14:25 -0500 Received: from nortelnetworks.com (acart1f3.ca.nortel.com [47.129.129.145]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id SZW5NKNA; Wed, 5 Nov 2003 08:14:25 -0500 Message-ID: <3FA8F7B0.6020602@nortelnetworks.com> Date: Wed, 05 Nov 2003 08:14:24 -0500 X-Sybari-Space: 00000000 00000000 00000000 00000000 From: Tom Taylor User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: megaco@ietf.org Subject: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by zcars0m9.nortelnetworks.com id hA5DEPC17789 Content-Transfer-Encoding: quoted-printable Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable -------- Original Message -------- Subject: FW: [MEGACO] Can a gateway drop active calls? Date: Wed, 5 Nov 2003 14:58:11 +0200 From: Nurit Shenhar To: Taylor, Tom-PT [CAR:5N00:EXCH] Tom Again, it didn=92t reach the list=85 Nurit -----Original Message----- *From:* Nurit Shenhar *Sent:* Wednesday, November 05, 2003 9:00 AM *To:* 'megaco@ietf.org' *Subject:* [MEGACO] Can a gateway drop active calls? Hi Assuming the following scenario: 1. GW is active with open calls. 2. Connection with the MGC is lost, and reconnection to all possible MGC is not successful. This state goes on for a long time (minutes, hours). Is it legitimate for the GW in this state to drop the active calls? */ /* */Nurit Shenhar/* */H.248 Prime/* ** E-Mail: nurit.shenhar@audiocodes.com Fax. +972-3-5394223 www.audiocodes.com _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Wed Nov 5 08:15:52 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04502 for ; Wed, 5 Nov 2003 08:15:52 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHNVT-0000C8-GD for megaco-archive@odin.ietf.org; Wed, 05 Nov 2003 08:15:34 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA5DFV1s000742 for megaco-archive@odin.ietf.org; Wed, 5 Nov 2003 08:15:31 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHNVT-0000Bt-B1 for megaco-web-archive@optimus.ietf.org; Wed, 05 Nov 2003 08:15:31 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04414 for ; Wed, 5 Nov 2003 08:15:19 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHNVS-0003mT-00 for megaco-web-archive@ietf.org; Wed, 05 Nov 2003 08:15:30 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AHNVR-0003mP-00 for megaco-web-archive@ietf.org; Wed, 05 Nov 2003 08:15:29 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHNV3-0008Rn-5f; Wed, 05 Nov 2003 08:15:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHNUw-0008II-Rr for megaco@optimus.ietf.org; Wed, 05 Nov 2003 08:14:58 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04373 for ; Wed, 5 Nov 2003 08:14:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHNUv-0003jT-00 for megaco@ietf.org; Wed, 05 Nov 2003 08:14:57 -0500 Received: from zcars0m9.nortelnetworks.com ([47.129.242.157]) by ietf-mx with esmtp (Exim 4.12) id 1AHNUv-0003i0-00 for megaco@ietf.org; Wed, 05 Nov 2003 08:14:57 -0500 Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA5DEPC17789 for ; Wed, 5 Nov 2003 08:14:25 -0500 (EST) Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id VRTPF9QK; Wed, 5 Nov 2003 08:14:25 -0500 Received: from nortelnetworks.com (acart1f3.ca.nortel.com [47.129.129.145]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id SZW5NKNA; Wed, 5 Nov 2003 08:14:25 -0500 Message-ID: <3FA8F7B0.6020602@nortelnetworks.com> Date: Wed, 05 Nov 2003 08:14:24 -0500 X-Sybari-Space: 00000000 00000000 00000000 00000000 From: Tom Taylor User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: megaco@ietf.org Subject: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by zcars0m9.nortelnetworks.com id hA5DEPC17789 Content-Transfer-Encoding: quoted-printable Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable -------- Original Message -------- Subject: FW: [MEGACO] Can a gateway drop active calls? Date: Wed, 5 Nov 2003 14:58:11 +0200 From: Nurit Shenhar To: Taylor, Tom-PT [CAR:5N00:EXCH] Tom Again, it didn=92t reach the list=85 Nurit -----Original Message----- *From:* Nurit Shenhar *Sent:* Wednesday, November 05, 2003 9:00 AM *To:* 'megaco@ietf.org' *Subject:* [MEGACO] Can a gateway drop active calls? Hi Assuming the following scenario: 1. GW is active with open calls. 2. Connection with the MGC is lost, and reconnection to all possible MGC is not successful. This state goes on for a long time (minutes, hours). Is it legitimate for the GW in this state to drop the active calls? */ /* */Nurit Shenhar/* */H.248 Prime/* ** E-Mail: nurit.shenhar@audiocodes.com Fax. +972-3-5394223 www.audiocodes.com _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Wed Nov 5 09:18:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06241 for ; Wed, 5 Nov 2003 09:18:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHOTx-0003iL-4G; Wed, 05 Nov 2003 09:18:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHOTI-0003hk-L7 for megaco@optimus.ietf.org; Wed, 05 Nov 2003 09:17:20 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06230 for ; Wed, 5 Nov 2003 09:17:07 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHOTG-0004mL-00 for megaco@ietf.org; Wed, 05 Nov 2003 09:17:18 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AHOTG-0004m4-00 for megaco@ietf.org; Wed, 05 Nov 2003 09:17:18 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA5EGfe03132 for ; Wed, 5 Nov 2003 09:16:42 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Wed, 5 Nov 2003 09:16:42 -0500 Message-ID: From: "Kevin Boyle" To: megaco@ietf.org Subject: RE: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] Date: Wed, 5 Nov 2003 09:16:40 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Comments inline. [KJBII] Kevin -----Original Message----- From: Taylor, Tom-PT [CAR:5N00:EXCH] Sent: Wednesday, November 05, 2003 8:14 AM To: megaco@ietf.org Subject: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] -------- Original Message -------- Subject: FW: [MEGACO] Can a gateway drop active calls? Date: Wed, 5 Nov 2003 14:58:11 +0200 From: Nurit Shenhar To: Taylor, Tom-PT [CAR:5N00:EXCH] Tom Again, it didn't reach the list... Nurit -----Original Message----- *From:* Nurit Shenhar *Sent:* Wednesday, November 05, 2003 9:00 AM *To:* 'megaco@ietf.org' *Subject:* [MEGACO] Can a gateway drop active calls? Hi Assuming the following scenario: 1. GW is active with open calls. 2. Connection with the MGC is lost, and reconnection to all possible MGC is not successful. This state goes on for a long time (minutes, hours). Is it legitimate for the GW in this state to drop the active calls? [KJBII] Technically no. However, if the MG is unable to connect to any MGCs, how would the MGCs know the MG didn't undergo a cold boot? Be very careful here, though -- subscribers tend to complain a lot to their providers when calls are dropped. I think that if an MG wants to drop calls, it better have a very good reason -- that is, it should cold reboot. */ /* */Nurit Shenhar/* */H.248 Prime/* ** E-Mail: nurit.shenhar@audiocodes.com Fax. +972-3-5394223 www.audiocodes.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 exim@www1.ietf.org Wed Nov 5 09:18:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06256 for ; Wed, 5 Nov 2003 09:18:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHOU0-0003jk-NY for megaco-archive@odin.ietf.org; Wed, 05 Nov 2003 09:18:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA5EI4I9014358 for megaco-archive@odin.ietf.org; Wed, 5 Nov 2003 09:18:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHOU0-0003jV-Jn for megaco-web-archive@optimus.ietf.org; Wed, 05 Nov 2003 09:18:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06237 for ; Wed, 5 Nov 2003 09:17:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHOTy-0004mm-00 for megaco-web-archive@ietf.org; Wed, 05 Nov 2003 09:18:03 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AHOTy-0004mj-00 for megaco-web-archive@ietf.org; Wed, 05 Nov 2003 09:18:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHOTx-0003iL-4G; Wed, 05 Nov 2003 09:18:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHOTI-0003hk-L7 for megaco@optimus.ietf.org; Wed, 05 Nov 2003 09:17:20 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06230 for ; Wed, 5 Nov 2003 09:17:07 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHOTG-0004mL-00 for megaco@ietf.org; Wed, 05 Nov 2003 09:17:18 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AHOTG-0004m4-00 for megaco@ietf.org; Wed, 05 Nov 2003 09:17:18 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA5EGfe03132 for ; Wed, 5 Nov 2003 09:16:42 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Wed, 5 Nov 2003 09:16:42 -0500 Message-ID: From: "Kevin Boyle" To: megaco@ietf.org Subject: RE: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] Date: Wed, 5 Nov 2003 09:16:40 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Comments inline. [KJBII] Kevin -----Original Message----- From: Taylor, Tom-PT [CAR:5N00:EXCH] Sent: Wednesday, November 05, 2003 8:14 AM To: megaco@ietf.org Subject: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] -------- Original Message -------- Subject: FW: [MEGACO] Can a gateway drop active calls? Date: Wed, 5 Nov 2003 14:58:11 +0200 From: Nurit Shenhar To: Taylor, Tom-PT [CAR:5N00:EXCH] Tom Again, it didn't reach the list... Nurit -----Original Message----- *From:* Nurit Shenhar *Sent:* Wednesday, November 05, 2003 9:00 AM *To:* 'megaco@ietf.org' *Subject:* [MEGACO] Can a gateway drop active calls? Hi Assuming the following scenario: 1. GW is active with open calls. 2. Connection with the MGC is lost, and reconnection to all possible MGC is not successful. This state goes on for a long time (minutes, hours). Is it legitimate for the GW in this state to drop the active calls? [KJBII] Technically no. However, if the MG is unable to connect to any MGCs, how would the MGCs know the MG didn't undergo a cold boot? Be very careful here, though -- subscribers tend to complain a lot to their providers when calls are dropped. I think that if an MG wants to drop calls, it better have a very good reason -- that is, it should cold reboot. */ /* */Nurit Shenhar/* */H.248 Prime/* ** E-Mail: nurit.shenhar@audiocodes.com Fax. +972-3-5394223 www.audiocodes.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-admin@ietf.org Thu Nov 6 08:01:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06845 for ; Thu, 6 Nov 2003 08:01:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHjl0-0004cz-9r; Thu, 06 Nov 2003 08:01:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHjk7-0004a9-JE for megaco@optimus.ietf.org; Thu, 06 Nov 2003 08:00:07 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06756 for ; Thu, 6 Nov 2003 07:59:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHjk3-0000TX-00 for megaco@ietf.org; Thu, 06 Nov 2003 08:00:03 -0500 Received: from znsgs01r.nortelnetworks.com ([47.166.48.91]) by ietf-mx with esmtp (Exim 4.12) id 1AHjk3-0000TK-00 for megaco@ietf.org; Thu, 06 Nov 2003 08:00:03 -0500 Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.160.46.124]) by znsgs01r.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA6CxPV25471 for ; Thu, 6 Nov 2003 12:59:26 GMT Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19) id ; Thu, 6 Nov 2003 12:59:27 -0000 Message-ID: From: "Paul Richard" To: "'megaco@ietf.org'" Date: Thu, 6 Nov 2003 12:59:26 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3A465.CE84D5D0" Subject: [Megaco] Context wildcards Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , 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_01C3A465.CE84D5D0 Content-Type: text/plain; charset="iso-8859-1" Hi, I have a theoretical type question. I'd simply like to get my head around the exact meaning of the following type of message (as sent by the MGC to the MG): !/1 [10.67.97.76]:2944 T=5981{C=*{MF=tp/0016{SG{},M{O{MO=IN}}},S=tp/0016{AT{}}}} This is clearly a clean-up attempt by the MGC. However , is the "*" wildcard here meant to specify that the modify command should be carried out against tp/0016 regardless of which context the termination happens to be in? If so, then I assume that the MG should always respond positively to this command (under any circumstance). Thanks, Paul ------_=_NextPart_001_01C3A465.CE84D5D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Context wildcards

Hi,

I have a theoretical type question. = I'd simply like to get my head around the exact meaning of the = following type of message (as sent by the MGC to the MG):

!/1 [10.67.97.76]:2944 = T=3D5981{C=3D*{MF=3Dtp/0016{SG{},M{O{MO=3DIN}}},S=3Dtp/0016{AT{}}}}

This is clearly a clean-up attempt by = the MGC.  However , is the "*" wildcard here meant to = specify that the modify command should be carried out against tp/0016 = regardless of which context the termination happens to be = in?

If so, then I assume that the MG = should always respond positively to this command (under any = circumstance). 

Thanks,
Paul

------_=_NextPart_001_01C3A465.CE84D5D0-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Thu Nov 6 08:01:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06861 for ; Thu, 6 Nov 2003 08:01:26 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHjl4-0004eN-SW for megaco-archive@odin.ietf.org; Thu, 06 Nov 2003 08:01:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA6D163I017869 for megaco-archive@odin.ietf.org; Thu, 6 Nov 2003 08:01:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHjl4-0004e8-P5 for megaco-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 08:01:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06807 for ; Thu, 6 Nov 2003 08:00:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHjl3-0000WF-00 for megaco-web-archive@ietf.org; Thu, 06 Nov 2003 08:01:05 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AHjl3-0000WC-00 for megaco-web-archive@ietf.org; Thu, 06 Nov 2003 08:01:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHjl0-0004cz-9r; Thu, 06 Nov 2003 08:01:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHjk7-0004a9-JE for megaco@optimus.ietf.org; Thu, 06 Nov 2003 08:00:07 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06756 for ; Thu, 6 Nov 2003 07:59:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHjk3-0000TX-00 for megaco@ietf.org; Thu, 06 Nov 2003 08:00:03 -0500 Received: from znsgs01r.nortelnetworks.com ([47.166.48.91]) by ietf-mx with esmtp (Exim 4.12) id 1AHjk3-0000TK-00 for megaco@ietf.org; Thu, 06 Nov 2003 08:00:03 -0500 Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.160.46.124]) by znsgs01r.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA6CxPV25471 for ; Thu, 6 Nov 2003 12:59:26 GMT Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19) id ; Thu, 6 Nov 2003 12:59:27 -0000 Message-ID: From: "Paul Richard" To: "'megaco@ietf.org'" Date: Thu, 6 Nov 2003 12:59:26 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3A465.CE84D5D0" Subject: [Megaco] Context wildcards Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , 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_01C3A465.CE84D5D0 Content-Type: text/plain; charset="iso-8859-1" Hi, I have a theoretical type question. I'd simply like to get my head around the exact meaning of the following type of message (as sent by the MGC to the MG): !/1 [10.67.97.76]:2944 T=5981{C=*{MF=tp/0016{SG{},M{O{MO=IN}}},S=tp/0016{AT{}}}} This is clearly a clean-up attempt by the MGC. However , is the "*" wildcard here meant to specify that the modify command should be carried out against tp/0016 regardless of which context the termination happens to be in? If so, then I assume that the MG should always respond positively to this command (under any circumstance). Thanks, Paul ------_=_NextPart_001_01C3A465.CE84D5D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Context wildcards

Hi,

I have a theoretical type question. = I'd simply like to get my head around the exact meaning of the = following type of message (as sent by the MGC to the MG):

!/1 [10.67.97.76]:2944 = T=3D5981{C=3D*{MF=3Dtp/0016{SG{},M{O{MO=3DIN}}},S=3Dtp/0016{AT{}}}}

This is clearly a clean-up attempt by = the MGC.  However , is the "*" wildcard here meant to = specify that the modify command should be carried out against tp/0016 = regardless of which context the termination happens to be = in?

If so, then I assume that the MG = should always respond positively to this command (under any = circumstance). 

Thanks,
Paul

------_=_NextPart_001_01C3A465.CE84D5D0-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Thu Nov 6 08:28:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07966 for ; Thu, 6 Nov 2003 08:28:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHkB7-0006Sl-2g; Thu, 06 Nov 2003 08:28:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHkAC-0006SB-GU for megaco@optimus.ietf.org; Thu, 06 Nov 2003 08:27:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07919 for ; Thu, 6 Nov 2003 08:26:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHkAB-0000xh-00 for megaco@ietf.org; Thu, 06 Nov 2003 08:27:03 -0500 Received: from eins.siemens.at ([193.81.246.11]) by ietf-mx with esmtp (Exim 4.12) id 1AHkAA-0000xE-00 for megaco@ietf.org; Thu, 06 Nov 2003 08:27:02 -0500 Received: from mailhost2.sie.siemens.at (forix [10.1.140.2]) by eins.siemens.at (8.12.9/8.12.8) with ESMTP id hA6DQVTm010753 for ; Thu, 6 Nov 2003 14:26:31 +0100 Received: from vies194a.sie.siemens.at (nets109x.sie.siemens.at [158.226.134.96]) by mailhost2.sie.siemens.at (8.12.10/8.12.1) with ESMTP id hA6DQ8eG003017 for ; Thu, 6 Nov 2003 14:26:08 +0100 Received: by vies194a.sie.siemens.at with Internet Mail Service (5.5.2653.19) id ; Thu, 6 Nov 2003 14:26:40 +0100 Message-ID: From: Kalleitner Franz To: megaco@ietf.org Subject: AW: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] Date: Thu, 6 Nov 2003 14:26:38 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , I would say, MGC would also detect that the MG is not accessable. If no other possibility can be triggered to access the MG. MGC would start to release the calls on signaling level. The end point would stop transferring user payload or start a bearer release depending on the chosen L2/L3 protocol used for the connection. ciao Franz -----Ursprungliche Nachricht----- Von: Kevin Boyle [mailto:kboyle@nortelnetworks.com] Gesendet: Mittwoch, 05. November 2003 15:17 An: megaco@ietf.org Betreff: RE: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] Comments inline. [KJBII] Kevin -----Original Message----- From: Taylor, Tom-PT [CAR:5N00:EXCH] Sent: Wednesday, November 05, 2003 8:14 AM To: megaco@ietf.org Subject: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] -------- Original Message -------- Subject: FW: [MEGACO] Can a gateway drop active calls? Date: Wed, 5 Nov 2003 14:58:11 +0200 From: Nurit Shenhar To: Taylor, Tom-PT [CAR:5N00:EXCH] Tom Again, it didn't reach the list... Nurit -----Original Message----- *From:* Nurit Shenhar *Sent:* Wednesday, November 05, 2003 9:00 AM *To:* 'megaco@ietf.org' *Subject:* [MEGACO] Can a gateway drop active calls? Hi Assuming the following scenario: 1. GW is active with open calls. 2. Connection with the MGC is lost, and reconnection to all possible MGC is not successful. This state goes on for a long time (minutes, hours). Is it legitimate for the GW in this state to drop the active calls? [KJBII] Technically no. However, if the MG is unable to connect to any MGCs, how would the MGCs know the MG didn't undergo a cold boot? Be very careful here, though -- subscribers tend to complain a lot to their providers when calls are dropped. I think that if an MG wants to drop calls, it better have a very good reason -- that is, it should cold reboot. */ /* */Nurit Shenhar/* */H.248 Prime/* ** E-Mail: nurit.shenhar@audiocodes.com Fax. +972-3-5394223 www.audiocodes.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 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Thu Nov 6 08:28:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07989 for ; Thu, 6 Nov 2003 08:28:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHkB9-0006UD-St for megaco-archive@odin.ietf.org; Thu, 06 Nov 2003 08:28:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA6DS3eY024932 for megaco-archive@odin.ietf.org; Thu, 6 Nov 2003 08:28:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHkB9-0006U3-OO for megaco-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 08:28:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07947 for ; Thu, 6 Nov 2003 08:27:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHkB8-0000y4-00 for megaco-web-archive@ietf.org; Thu, 06 Nov 2003 08:28:02 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AHkB8-0000y0-00 for megaco-web-archive@ietf.org; Thu, 06 Nov 2003 08:28:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHkB7-0006Sl-2g; Thu, 06 Nov 2003 08:28:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHkAC-0006SB-GU for megaco@optimus.ietf.org; Thu, 06 Nov 2003 08:27:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07919 for ; Thu, 6 Nov 2003 08:26:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHkAB-0000xh-00 for megaco@ietf.org; Thu, 06 Nov 2003 08:27:03 -0500 Received: from eins.siemens.at ([193.81.246.11]) by ietf-mx with esmtp (Exim 4.12) id 1AHkAA-0000xE-00 for megaco@ietf.org; Thu, 06 Nov 2003 08:27:02 -0500 Received: from mailhost2.sie.siemens.at (forix [10.1.140.2]) by eins.siemens.at (8.12.9/8.12.8) with ESMTP id hA6DQVTm010753 for ; Thu, 6 Nov 2003 14:26:31 +0100 Received: from vies194a.sie.siemens.at (nets109x.sie.siemens.at [158.226.134.96]) by mailhost2.sie.siemens.at (8.12.10/8.12.1) with ESMTP id hA6DQ8eG003017 for ; Thu, 6 Nov 2003 14:26:08 +0100 Received: by vies194a.sie.siemens.at with Internet Mail Service (5.5.2653.19) id ; Thu, 6 Nov 2003 14:26:40 +0100 Message-ID: From: Kalleitner Franz To: megaco@ietf.org Subject: AW: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] Date: Thu, 6 Nov 2003 14:26:38 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , I would say, MGC would also detect that the MG is not accessable. If no other possibility can be triggered to access the MG. MGC would start to release the calls on signaling level. The end point would stop transferring user payload or start a bearer release depending on the chosen L2/L3 protocol used for the connection. ciao Franz -----Ursprungliche Nachricht----- Von: Kevin Boyle [mailto:kboyle@nortelnetworks.com] Gesendet: Mittwoch, 05. November 2003 15:17 An: megaco@ietf.org Betreff: RE: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] Comments inline. [KJBII] Kevin -----Original Message----- From: Taylor, Tom-PT [CAR:5N00:EXCH] Sent: Wednesday, November 05, 2003 8:14 AM To: megaco@ietf.org Subject: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] -------- Original Message -------- Subject: FW: [MEGACO] Can a gateway drop active calls? Date: Wed, 5 Nov 2003 14:58:11 +0200 From: Nurit Shenhar To: Taylor, Tom-PT [CAR:5N00:EXCH] Tom Again, it didn't reach the list... Nurit -----Original Message----- *From:* Nurit Shenhar *Sent:* Wednesday, November 05, 2003 9:00 AM *To:* 'megaco@ietf.org' *Subject:* [MEGACO] Can a gateway drop active calls? Hi Assuming the following scenario: 1. GW is active with open calls. 2. Connection with the MGC is lost, and reconnection to all possible MGC is not successful. This state goes on for a long time (minutes, hours). Is it legitimate for the GW in this state to drop the active calls? [KJBII] Technically no. However, if the MG is unable to connect to any MGCs, how would the MGCs know the MG didn't undergo a cold boot? Be very careful here, though -- subscribers tend to complain a lot to their providers when calls are dropped. I think that if an MG wants to drop calls, it better have a very good reason -- that is, it should cold reboot. */ /* */Nurit Shenhar/* */H.248 Prime/* ** E-Mail: nurit.shenhar@audiocodes.com Fax. +972-3-5394223 www.audiocodes.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 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Thu Nov 6 11:32:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16867 for ; Thu, 6 Nov 2003 11:32:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn3B-0001JJ-Br; Thu, 06 Nov 2003 11:32:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn2c-0001IA-CI for megaco@optimus.ietf.org; Thu, 06 Nov 2003 11:31:26 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16816 for ; Thu, 6 Nov 2003 11:31:14 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHn2b-0003hD-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:31:25 -0500 Received: from pat.telica.com ([4.19.224.196] helo=wench.telica.com) by ietf-mx with esmtp (Exim 4.12) id 1AHn2b-0003hA-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:31:25 -0500 Received: by wench.telica.com with Internet Mail Service (5.5.2653.19) id ; Thu, 6 Nov 2003 11:30:36 -0500 Message-ID: From: Rishi Ahuja To: "'megaco@ietf.org'" Date: Thu, 6 Nov 2003 11:30:35 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3A483.06A94154" Subject: [Megaco] Default values for Digit Map TImers Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , 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_01C3A483.06A94154 Content-Type: text/plain; charset="iso-8859-1" Are the default values of T, S and L timers specified somewhere or are they implementation dependent? ------_=_NextPart_001_01C3A483.06A94154 Content-Type: text/html; charset="iso-8859-1" Context wildcards
Are the default values of T, S and L timers specified somewhere or are they implementation dependent?
 
------_=_NextPart_001_01C3A483.06A94154-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Thu Nov 6 11:32:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16882 for ; Thu, 6 Nov 2003 11:32:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn3F-0001Kj-SP for megaco-archive@odin.ietf.org; Thu, 06 Nov 2003 11:32:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA6GW5wf005121 for megaco-archive@odin.ietf.org; Thu, 6 Nov 2003 11:32:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn3F-0001KW-NU for megaco-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 11:32:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16826 for ; Thu, 6 Nov 2003 11:31:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHn3E-0003hY-00 for megaco-web-archive@ietf.org; Thu, 06 Nov 2003 11:32:04 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AHn3D-0003hR-00 for megaco-web-archive@ietf.org; Thu, 06 Nov 2003 11:32:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn3B-0001JJ-Br; Thu, 06 Nov 2003 11:32:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn2c-0001IA-CI for megaco@optimus.ietf.org; Thu, 06 Nov 2003 11:31:26 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16816 for ; Thu, 6 Nov 2003 11:31:14 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHn2b-0003hD-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:31:25 -0500 Received: from pat.telica.com ([4.19.224.196] helo=wench.telica.com) by ietf-mx with esmtp (Exim 4.12) id 1AHn2b-0003hA-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:31:25 -0500 Received: by wench.telica.com with Internet Mail Service (5.5.2653.19) id ; Thu, 6 Nov 2003 11:30:36 -0500 Message-ID: From: Rishi Ahuja To: "'megaco@ietf.org'" Date: Thu, 6 Nov 2003 11:30:35 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3A483.06A94154" Subject: [Megaco] Default values for Digit Map TImers Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , 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_01C3A483.06A94154 Content-Type: text/plain; charset="iso-8859-1" Are the default values of T, S and L timers specified somewhere or are they implementation dependent? ------_=_NextPart_001_01C3A483.06A94154 Content-Type: text/html; charset="iso-8859-1" Context wildcards
Are the default values of T, S and L timers specified somewhere or are they implementation dependent?
 
------_=_NextPart_001_01C3A483.06A94154-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Thu Nov 6 11:38:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17208 for ; Thu, 6 Nov 2003 11:38:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn8z-0001t1-Lj; Thu, 06 Nov 2003 11:38:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn8S-0001lh-UB for megaco@optimus.ietf.org; Thu, 06 Nov 2003 11:37:28 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17133 for ; Thu, 6 Nov 2003 11:37:16 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHn8R-0003mp-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:37:27 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AHn8Q-0003m9-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:37:27 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA6GatA02643 for ; Thu, 6 Nov 2003 11:36:55 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Thu, 6 Nov 2003 11:36:55 -0500 Message-ID: From: "Kevin Boyle" To: Kalleitner Franz , megaco@ietf.org Subject: RE: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] Date: Thu, 6 Nov 2003 11:36:47 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , The MGC could figure out that the MG has gone, but remember that the MGC cannot establish control associations. So, this means that the MGC has to wait for the MG to make the next contact, not the other way around. For the primary MGC, this will be via a SC Disconnected. The MG is specifically prohibited from altering terminations or contexts without MGC direction. Because of this prohibition, the MGC MUST intervene to clean up any contexts that existed at the time of communications loss. The only exception to this is if the MG undergoes a Cold Boot, at which time the MGC can assume that all state is lost and the MG is in a newly started state. Also note that there is no such thing as an endpoint in H.248. H.248 operates on terminations. Terminations and endpoints are two different concepts. Kevin -----Original Message----- From: Kalleitner Franz [mailto:franz.kalleitner@siemens.com] Sent: Thursday, November 06, 2003 8:27 AM To: megaco@ietf.org Subject: AW: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] I would say, MGC would also detect that the MG is not accessable. If no other possibility can be triggered to access the MG. MGC would start to release the calls on signaling level. The end point would stop transferring user payload or start a bearer release depending on the chosen L2/L3 protocol used for the connection. ciao Franz -----Ursprungliche Nachricht----- Von: Kevin Boyle [mailto:kboyle@nortelnetworks.com] Gesendet: Mittwoch, 05. November 2003 15:17 An: megaco@ietf.org Betreff: RE: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] Comments inline. [KJBII] Kevin -----Original Message----- From: Taylor, Tom-PT [CAR:5N00:EXCH] Sent: Wednesday, November 05, 2003 8:14 AM To: megaco@ietf.org Subject: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] -------- Original Message -------- Subject: FW: [MEGACO] Can a gateway drop active calls? Date: Wed, 5 Nov 2003 14:58:11 +0200 From: Nurit Shenhar To: Taylor, Tom-PT [CAR:5N00:EXCH] Tom Again, it didn't reach the list... Nurit -----Original Message----- *From:* Nurit Shenhar *Sent:* Wednesday, November 05, 2003 9:00 AM *To:* 'megaco@ietf.org' *Subject:* [MEGACO] Can a gateway drop active calls? Hi Assuming the following scenario: 1. GW is active with open calls. 2. Connection with the MGC is lost, and reconnection to all possible MGC is not successful. This state goes on for a long time (minutes, hours). Is it legitimate for the GW in this state to drop the active calls? [KJBII] Technically no. However, if the MG is unable to connect to any MGCs, how would the MGCs know the MG didn't undergo a cold boot? Be very careful here, though -- subscribers tend to complain a lot to their providers when calls are dropped. I think that if an MG wants to drop calls, it better have a very good reason -- that is, it should cold reboot. */ /* */Nurit Shenhar/* */H.248 Prime/* ** E-Mail: nurit.shenhar@audiocodes.com Fax. +972-3-5394223 www.audiocodes.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 _______________________________________________ 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 exim@www1.ietf.org Thu Nov 6 11:38:31 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17232 for ; Thu, 6 Nov 2003 11:38:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn9A-0001zT-N2 for megaco-archive@odin.ietf.org; Thu, 06 Nov 2003 11:38:13 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA6GcCml007622 for megaco-archive@odin.ietf.org; Thu, 6 Nov 2003 11:38:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn99-0001yQ-6g for megaco-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 11:38:11 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17176 for ; Thu, 6 Nov 2003 11:37:58 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHn97-0003ng-00 for megaco-web-archive@ietf.org; Thu, 06 Nov 2003 11:38:09 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AHn97-0003nS-00 for megaco-web-archive@ietf.org; Thu, 06 Nov 2003 11:38:09 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn8z-0001t1-Lj; Thu, 06 Nov 2003 11:38:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn8S-0001lh-UB for megaco@optimus.ietf.org; Thu, 06 Nov 2003 11:37:28 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17133 for ; Thu, 6 Nov 2003 11:37:16 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHn8R-0003mp-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:37:27 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AHn8Q-0003m9-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:37:27 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA6GatA02643 for ; Thu, 6 Nov 2003 11:36:55 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Thu, 6 Nov 2003 11:36:55 -0500 Message-ID: From: "Kevin Boyle" To: Kalleitner Franz , megaco@ietf.org Subject: RE: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] Date: Thu, 6 Nov 2003 11:36:47 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , The MGC could figure out that the MG has gone, but remember that the MGC cannot establish control associations. So, this means that the MGC has to wait for the MG to make the next contact, not the other way around. For the primary MGC, this will be via a SC Disconnected. The MG is specifically prohibited from altering terminations or contexts without MGC direction. Because of this prohibition, the MGC MUST intervene to clean up any contexts that existed at the time of communications loss. The only exception to this is if the MG undergoes a Cold Boot, at which time the MGC can assume that all state is lost and the MG is in a newly started state. Also note that there is no such thing as an endpoint in H.248. H.248 operates on terminations. Terminations and endpoints are two different concepts. Kevin -----Original Message----- From: Kalleitner Franz [mailto:franz.kalleitner@siemens.com] Sent: Thursday, November 06, 2003 8:27 AM To: megaco@ietf.org Subject: AW: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] I would say, MGC would also detect that the MG is not accessable. If no other possibility can be triggered to access the MG. MGC would start to release the calls on signaling level. The end point would stop transferring user payload or start a bearer release depending on the chosen L2/L3 protocol used for the connection. ciao Franz -----Ursprungliche Nachricht----- Von: Kevin Boyle [mailto:kboyle@nortelnetworks.com] Gesendet: Mittwoch, 05. November 2003 15:17 An: megaco@ietf.org Betreff: RE: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] Comments inline. [KJBII] Kevin -----Original Message----- From: Taylor, Tom-PT [CAR:5N00:EXCH] Sent: Wednesday, November 05, 2003 8:14 AM To: megaco@ietf.org Subject: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] -------- Original Message -------- Subject: FW: [MEGACO] Can a gateway drop active calls? Date: Wed, 5 Nov 2003 14:58:11 +0200 From: Nurit Shenhar To: Taylor, Tom-PT [CAR:5N00:EXCH] Tom Again, it didn't reach the list... Nurit -----Original Message----- *From:* Nurit Shenhar *Sent:* Wednesday, November 05, 2003 9:00 AM *To:* 'megaco@ietf.org' *Subject:* [MEGACO] Can a gateway drop active calls? Hi Assuming the following scenario: 1. GW is active with open calls. 2. Connection with the MGC is lost, and reconnection to all possible MGC is not successful. This state goes on for a long time (minutes, hours). Is it legitimate for the GW in this state to drop the active calls? [KJBII] Technically no. However, if the MG is unable to connect to any MGCs, how would the MGCs know the MG didn't undergo a cold boot? Be very careful here, though -- subscribers tend to complain a lot to their providers when calls are dropped. I think that if an MG wants to drop calls, it better have a very good reason -- that is, it should cold reboot. */ /* */Nurit Shenhar/* */H.248 Prime/* ** E-Mail: nurit.shenhar@audiocodes.com Fax. +972-3-5394223 www.audiocodes.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 _______________________________________________ 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-admin@ietf.org Thu Nov 6 11:39:19 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17320 for ; Thu, 6 Nov 2003 11:39:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn9w-0002By-P5; Thu, 06 Nov 2003 11:39:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn9u-0002Bf-Ce for megaco@optimus.ietf.org; Thu, 06 Nov 2003 11:38:58 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17267 for ; Thu, 6 Nov 2003 11:38:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHn9t-0003pL-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:38:57 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AHn9s-0003oX-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:38:56 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA6GcOA02753 for ; Thu, 6 Nov 2003 11:38:25 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Thu, 6 Nov 2003 11:38:25 -0500 Message-ID: From: "Kevin Boyle" To: Rishi Ahuja , "'megaco@ietf.org'" Subject: RE: [Megaco] Default values for Digit Map TImers Date: Thu, 6 Nov 2003 11:38:24 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , This would depend upon local requirements. See the relevant requirements specifications for the region in question for details. Kevin _____ From: Rishi Ahuja [mailto:RishiA@telica.com] Sent: Thursday, November 06, 2003 11:31 AM To: 'megaco@ietf.org' Subject: [Megaco] Default values for Digit Map TImers Are the default values of T, S and L timers specified somewhere or are they implementation dependent? _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Thu Nov 6 11:39:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17338 for ; Thu, 6 Nov 2003 11:39:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn9y-0002Da-2r for megaco-archive@odin.ietf.org; Thu, 06 Nov 2003 11:39:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA6Gd2V7008520 for megaco-archive@odin.ietf.org; Thu, 6 Nov 2003 11:39:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn9x-0002DK-U4 for megaco-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 11:39:01 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17277 for ; Thu, 6 Nov 2003 11:38:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHn9w-0003pd-00 for megaco-web-archive@ietf.org; Thu, 06 Nov 2003 11:39:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AHn9w-0003pY-00 for megaco-web-archive@ietf.org; Thu, 06 Nov 2003 11:39:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn9w-0002By-P5; Thu, 06 Nov 2003 11:39:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHn9u-0002Bf-Ce for megaco@optimus.ietf.org; Thu, 06 Nov 2003 11:38:58 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17267 for ; Thu, 6 Nov 2003 11:38:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHn9t-0003pL-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:38:57 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AHn9s-0003oX-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:38:56 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA6GcOA02753 for ; Thu, 6 Nov 2003 11:38:25 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Thu, 6 Nov 2003 11:38:25 -0500 Message-ID: From: "Kevin Boyle" To: Rishi Ahuja , "'megaco@ietf.org'" Subject: RE: [Megaco] Default values for Digit Map TImers Date: Thu, 6 Nov 2003 11:38:24 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , This would depend upon local requirements. See the relevant requirements specifications for the region in question for details. Kevin _____ From: Rishi Ahuja [mailto:RishiA@telica.com] Sent: Thursday, November 06, 2003 11:31 AM To: 'megaco@ietf.org' Subject: [Megaco] Default values for Digit Map TImers Are the default values of T, S and L timers specified somewhere or are they implementation dependent? _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Thu Nov 6 11:45:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17666 for ; Thu, 6 Nov 2003 11:45:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHnFm-0002XW-WB; Thu, 06 Nov 2003 11:45:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHnEm-0002WS-Eo for megaco@optimus.ietf.org; Thu, 06 Nov 2003 11:44:00 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17556 for ; Thu, 6 Nov 2003 11:43:48 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHnEl-0003uc-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:43:59 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AHnEk-0003uM-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:43:58 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA6GhRi06765 for ; Thu, 6 Nov 2003 11:43:27 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Thu, 6 Nov 2003 11:43:28 -0500 Message-ID: From: "Kevin Boyle" To: "Paul Richard" , "'megaco@ietf.org'" Subject: RE: [Megaco] Context wildcards Date: Thu, 6 Nov 2003 11:43:25 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Comments inline. [KJBII] Kevin _____ From: Richard, Paul [MOP:MA03:EXCH] Sent: Thursday, November 06, 2003 7:59 AM To: 'megaco@ietf.org' Subject: [Megaco] Context wildcards Hi, I have a theoretical type question. I'd simply like to get my head around the exact meaning of the following type of message (as sent by the MGC to the MG): !/1 [10.67.97.76]:2944 T=5981{C=*{MF=tp/0016{SG{},M{O{MO=IN}}},S=tp/0016{AT{}}}} This is clearly a clean-up attempt by the MGC. However , is the "*" wildcard here meant to specify that the modify command should be carried out against tp/0016 regardless of which context the termination happens to be in? [KJBII] Remember that C=* does NOT match Null. If the term is in Null, the MG will fail the Modify with ER=411 and halt processing there. If so, then I assume that the MG should always respond positively to this command (under any circumstance). Thanks, Paul _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Thu Nov 6 11:45:27 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17683 for ; Thu, 6 Nov 2003 11:45:27 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHnFt-0002ai-Gq for megaco-archive@odin.ietf.org; Thu, 06 Nov 2003 11:45:09 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA6Gj9Z7009954 for megaco-archive@odin.ietf.org; Thu, 6 Nov 2003 11:45:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHnFt-0002aT-AP for megaco-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 11:45:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17626 for ; Thu, 6 Nov 2003 11:44:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHnFn-0003vY-00 for megaco-web-archive@ietf.org; Thu, 06 Nov 2003 11:45:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AHnFn-0003vV-00 for megaco-web-archive@ietf.org; Thu, 06 Nov 2003 11:45:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHnFm-0002XW-WB; Thu, 06 Nov 2003 11:45:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHnEm-0002WS-Eo for megaco@optimus.ietf.org; Thu, 06 Nov 2003 11:44:00 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17556 for ; Thu, 6 Nov 2003 11:43:48 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHnEl-0003uc-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:43:59 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AHnEk-0003uM-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:43:58 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA6GhRi06765 for ; Thu, 6 Nov 2003 11:43:27 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Thu, 6 Nov 2003 11:43:28 -0500 Message-ID: From: "Kevin Boyle" To: "Paul Richard" , "'megaco@ietf.org'" Subject: RE: [Megaco] Context wildcards Date: Thu, 6 Nov 2003 11:43:25 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Comments inline. [KJBII] Kevin _____ From: Richard, Paul [MOP:MA03:EXCH] Sent: Thursday, November 06, 2003 7:59 AM To: 'megaco@ietf.org' Subject: [Megaco] Context wildcards Hi, I have a theoretical type question. I'd simply like to get my head around the exact meaning of the following type of message (as sent by the MGC to the MG): !/1 [10.67.97.76]:2944 T=5981{C=*{MF=tp/0016{SG{},M{O{MO=IN}}},S=tp/0016{AT{}}}} This is clearly a clean-up attempt by the MGC. However , is the "*" wildcard here meant to specify that the modify command should be carried out against tp/0016 regardless of which context the termination happens to be in? [KJBII] Remember that C=* does NOT match Null. If the term is in Null, the MG will fail the Modify with ER=411 and halt processing there. If so, then I assume that the MG should always respond positively to this command (under any circumstance). Thanks, Paul _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Thu Nov 6 11:50:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17893 for ; Thu, 6 Nov 2003 11:50:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHnKc-0002mu-Qn; Thu, 06 Nov 2003 11:50:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHnJl-0002kv-Jl for megaco@optimus.ietf.org; Thu, 06 Nov 2003 11:49:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17829 for ; Thu, 6 Nov 2003 11:48:57 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHnJk-00041t-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:49:08 -0500 Received: from motgate2.mot.com ([136.182.1.10]) by ietf-mx with esmtp (Exim 4.12) id 1AHnJj-00041q-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:49:07 -0500 Received: from il06exr02.mot.com (pobox.mot.com [129.188.137.100]) by motgate2.mot.com (Motorola/Motgate2) with ESMTP id hA6Gn6eS020458; Thu, 6 Nov 2003 09:49:07 -0700 (MST) Received: from smilevm.motorola.com ([10.14.25.162]) by il06exr02.mot.com (Motorola/il06exr02) with ESMTP id hA6GiULw029693; Thu, 6 Nov 2003 10:44:31 -0600 Message-Id: <5.2.1.1.0.20031106114125.02a2e7f0@IL06EXM13.corp.mot.com> X-Sender: A19776@IL06EXM13.corp.mot.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Thu, 06 Nov 2003 11:42:29 -0500 To: Kalleitner Franz, From: Aleksandr Ryabin Subject: Re: AW: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , And what if signalling used is CAS handled by same MG using MEGACO? Aleks At 08:26 AM 11/6/2003, Kalleitner Franz wrote: >I would say, MGC would also detect that the MG is not accessable. If no >other possibility can be triggered to access the MG. MGC would start to >release the calls on signaling level. >The end point would stop transferring user payload or start a bearer release >depending on the chosen L2/L3 protocol used for the connection. > >ciao >Franz > > >-----Ursprungliche Nachricht----- >Von: Kevin Boyle [mailto:kboyle@nortelnetworks.com] >Gesendet: Mittwoch, 05. November 2003 15:17 >An: megaco@ietf.org >Betreff: RE: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] > > >Comments inline. [KJBII] > >Kevin > >-----Original Message----- >From: Taylor, Tom-PT [CAR:5N00:EXCH] >Sent: Wednesday, November 05, 2003 8:14 AM >To: megaco@ietf.org >Subject: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] > > > >-------- Original Message -------- >Subject: FW: [MEGACO] Can a gateway drop active calls? >Date: Wed, 5 Nov 2003 14:58:11 +0200 >From: Nurit Shenhar >To: Taylor, Tom-PT [CAR:5N00:EXCH] > > > >Tom > > > >Again, it didn't reach the list... > > > >Nurit > > > >-----Original Message----- >*From:* Nurit Shenhar >*Sent:* Wednesday, November 05, 2003 9:00 AM >*To:* 'megaco@ietf.org' >*Subject:* [MEGACO] Can a gateway drop active calls? > > > >Hi > > > >Assuming the following scenario: > > 1. GW is active with open calls. > 2. Connection with the MGC is lost, and reconnection to all possible > MGC is not successful. This state goes on for a long time > (minutes, hours). > > > >Is it legitimate for the GW in this state to drop the active calls? > >[KJBII] Technically no. However, if the MG is unable to connect to any >MGCs, how would the MGCs know the MG didn't undergo a cold boot? Be very >careful here, though -- subscribers tend to complain a lot to their >providers when calls are dropped. I think that if an MG wants to drop >calls, it better have a very good reason -- that is, it should cold reboot. > >*/ /* > >*/Nurit Shenhar/* > >*/H.248 Prime/* > > > >** > >E-Mail: nurit.shenhar@audiocodes.com > >Fax. +972-3-5394223 > >www.audiocodes.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 > >_______________________________________________ >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 exim@www1.ietf.org Thu Nov 6 11:50:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17908 for ; Thu, 6 Nov 2003 11:50:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHnKe-0002oK-E2 for megaco-archive@odin.ietf.org; Thu, 06 Nov 2003 11:50:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA6Go4mb010798 for megaco-archive@odin.ietf.org; Thu, 6 Nov 2003 11:50:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHnKe-0002o5-AP for megaco-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 11:50:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17868 for ; Thu, 6 Nov 2003 11:49:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHnKd-000431-00 for megaco-web-archive@ietf.org; Thu, 06 Nov 2003 11:50:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AHnKc-00042y-00 for megaco-web-archive@ietf.org; Thu, 06 Nov 2003 11:50:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHnKc-0002mu-Qn; Thu, 06 Nov 2003 11:50:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHnJl-0002kv-Jl for megaco@optimus.ietf.org; Thu, 06 Nov 2003 11:49:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17829 for ; Thu, 6 Nov 2003 11:48:57 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHnJk-00041t-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:49:08 -0500 Received: from motgate2.mot.com ([136.182.1.10]) by ietf-mx with esmtp (Exim 4.12) id 1AHnJj-00041q-00 for megaco@ietf.org; Thu, 06 Nov 2003 11:49:07 -0500 Received: from il06exr02.mot.com (pobox.mot.com [129.188.137.100]) by motgate2.mot.com (Motorola/Motgate2) with ESMTP id hA6Gn6eS020458; Thu, 6 Nov 2003 09:49:07 -0700 (MST) Received: from smilevm.motorola.com ([10.14.25.162]) by il06exr02.mot.com (Motorola/il06exr02) with ESMTP id hA6GiULw029693; Thu, 6 Nov 2003 10:44:31 -0600 Message-Id: <5.2.1.1.0.20031106114125.02a2e7f0@IL06EXM13.corp.mot.com> X-Sender: A19776@IL06EXM13.corp.mot.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Thu, 06 Nov 2003 11:42:29 -0500 To: Kalleitner Franz, From: Aleksandr Ryabin Subject: Re: AW: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , And what if signalling used is CAS handled by same MG using MEGACO? Aleks At 08:26 AM 11/6/2003, Kalleitner Franz wrote: >I would say, MGC would also detect that the MG is not accessable. If no >other possibility can be triggered to access the MG. MGC would start to >release the calls on signaling level. >The end point would stop transferring user payload or start a bearer release >depending on the chosen L2/L3 protocol used for the connection. > >ciao >Franz > > >-----Ursprungliche Nachricht----- >Von: Kevin Boyle [mailto:kboyle@nortelnetworks.com] >Gesendet: Mittwoch, 05. November 2003 15:17 >An: megaco@ietf.org >Betreff: RE: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] > > >Comments inline. [KJBII] > >Kevin > >-----Original Message----- >From: Taylor, Tom-PT [CAR:5N00:EXCH] >Sent: Wednesday, November 05, 2003 8:14 AM >To: megaco@ietf.org >Subject: [Fwd: FW: [MEGACO] Can a gateway drop active calls?] > > > >-------- Original Message -------- >Subject: FW: [MEGACO] Can a gateway drop active calls? >Date: Wed, 5 Nov 2003 14:58:11 +0200 >From: Nurit Shenhar >To: Taylor, Tom-PT [CAR:5N00:EXCH] > > > >Tom > > > >Again, it didn't reach the list... > > > >Nurit > > > >-----Original Message----- >*From:* Nurit Shenhar >*Sent:* Wednesday, November 05, 2003 9:00 AM >*To:* 'megaco@ietf.org' >*Subject:* [MEGACO] Can a gateway drop active calls? > > > >Hi > > > >Assuming the following scenario: > > 1. GW is active with open calls. > 2. Connection with the MGC is lost, and reconnection to all possible > MGC is not successful. This state goes on for a long time > (minutes, hours). > > > >Is it legitimate for the GW in this state to drop the active calls? > >[KJBII] Technically no. However, if the MG is unable to connect to any >MGCs, how would the MGCs know the MG didn't undergo a cold boot? Be very >careful here, though -- subscribers tend to complain a lot to their >providers when calls are dropped. I think that if an MG wants to drop >calls, it better have a very good reason -- that is, it should cold reboot. > >*/ /* > >*/Nurit Shenhar/* > >*/H.248 Prime/* > > > >** > >E-Mail: nurit.shenhar@audiocodes.com > >Fax. +972-3-5394223 > >www.audiocodes.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 > >_______________________________________________ >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-admin@ietf.org Fri Nov 7 13:39:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28420 for ; Fri, 7 Nov 2003 13:39:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBVd-0006Mv-GK; Fri, 07 Nov 2003 13:39:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBVV-0006MS-Nv for megaco@optimus.ietf.org; Fri, 07 Nov 2003 13:38:53 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28381 for ; Fri, 7 Nov 2003 13:38:42 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIBVT-000108-00 for megaco@ietf.org; Fri, 07 Nov 2003 13:38:51 -0500 Received: from ihemail2.lucent.com ([192.11.222.163] helo=ihemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AIBVS-0000zk-00 for megaco@ietf.org; Fri, 07 Nov 2003 13:38:50 -0500 Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3]) by ihemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hA7IcGw28849 for ; Fri, 7 Nov 2003 12:38:17 -0600 (CST) Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id NAA26080; Fri, 7 Nov 2003 13:38:35 -0500 (EST) Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id NAA26076; Fri, 7 Nov 2003 13:38:34 -0500 (EST) Message-ID: <3FABE618.1020005@bell-labs.com> Date: Fri, 07 Nov 2003 13:36:08 -0500 From: Troy Cauble User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: MEGACO list Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Megaco] discovering physical terminations Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Can someone suggest a minimal, wildcarded request from the MGC that would cause an MG to return the list of all physical terminations? -troy _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Fri Nov 7 13:39:35 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28451 for ; Fri, 7 Nov 2003 13:39:35 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBVr-0006Ob-Vi for megaco-archive@odin.ietf.org; Fri, 07 Nov 2003 13:39:16 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA7IdFJI024579 for megaco-archive@odin.ietf.org; Fri, 7 Nov 2003 13:39:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBVr-0006OM-Qs for megaco-web-archive@optimus.ietf.org; Fri, 07 Nov 2003 13:39:15 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28412 for ; Fri, 7 Nov 2003 13:39:04 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIBVp-00010t-00 for megaco-web-archive@ietf.org; Fri, 07 Nov 2003 13:39:13 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AIBVm-00010d-00 for megaco-web-archive@ietf.org; Fri, 07 Nov 2003 13:39:10 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBVd-0006Mv-GK; Fri, 07 Nov 2003 13:39:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBVV-0006MS-Nv for megaco@optimus.ietf.org; Fri, 07 Nov 2003 13:38:53 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28381 for ; Fri, 7 Nov 2003 13:38:42 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIBVT-000108-00 for megaco@ietf.org; Fri, 07 Nov 2003 13:38:51 -0500 Received: from ihemail2.lucent.com ([192.11.222.163] helo=ihemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AIBVS-0000zk-00 for megaco@ietf.org; Fri, 07 Nov 2003 13:38:50 -0500 Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3]) by ihemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hA7IcGw28849 for ; Fri, 7 Nov 2003 12:38:17 -0600 (CST) Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id NAA26080; Fri, 7 Nov 2003 13:38:35 -0500 (EST) Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id NAA26076; Fri, 7 Nov 2003 13:38:34 -0500 (EST) Message-ID: <3FABE618.1020005@bell-labs.com> Date: Fri, 07 Nov 2003 13:36:08 -0500 From: Troy Cauble User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: MEGACO list Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Megaco] discovering physical terminations Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Can someone suggest a minimal, wildcarded request from the MGC that would cause an MG to return the list of all physical terminations? -troy _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Fri Nov 7 13:51:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29078 for ; Fri, 7 Nov 2003 13:51:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBhF-0007Xj-41; Fri, 07 Nov 2003 13:51:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBgm-0007Wi-2c for megaco@optimus.ietf.org; Fri, 07 Nov 2003 13:50:32 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28989 for ; Fri, 7 Nov 2003 13:50:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIBgj-0001DE-00 for megaco@ietf.org; Fri, 07 Nov 2003 13:50:29 -0500 Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx with esmtp (Exim 4.12) id 1AIBgj-0001Bw-00 for megaco@ietf.org; Fri, 07 Nov 2003 13:50:29 -0500 Received: from VNANDURI-W2K1.cisco.com (sjc-vpn3-984.cisco.com [10.21.67.216]) by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id hA7InuiO020082; Fri, 7 Nov 2003 10:49:57 -0800 (PST) Message-Id: <4.3.2.7.2.20031107104101.0229bdc0@mira-sjc5-6.cisco.com> X-Sender: vnanduri@mira-sjc5-6.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 07 Nov 2003 10:49:55 -0800 To: megaco@ietf.org From: Venkata Narasimha Murthy Nanduri Cc: skyeung@cisco.com, jquan@cisco.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Megaco] Question about Tone list Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Hi, When the MGC specify: "-Signals "{dg/pt {tl=[d5,d5,d6,d7,d8,d9], Duration = 15000}}" Does it mean that Timeout between two consecutive tones is 15000/5 milliseconds? Thanks Venkata _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Fri Nov 7 13:51:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29090 for ; Fri, 7 Nov 2003 13:51:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBhG-0007YY-Vy for megaco-archive@odin.ietf.org; Fri, 07 Nov 2003 13:51:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA7Ip257029040 for megaco-archive@odin.ietf.org; Fri, 7 Nov 2003 13:51:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBhG-0007YJ-Rq for megaco-web-archive@optimus.ietf.org; Fri, 07 Nov 2003 13:51:02 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29058 for ; Fri, 7 Nov 2003 13:50:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIBhE-0001Du-00 for megaco-web-archive@ietf.org; Fri, 07 Nov 2003 13:51:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AIBhE-0001Dq-00 for megaco-web-archive@ietf.org; Fri, 07 Nov 2003 13:51:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBhF-0007Xj-41; Fri, 07 Nov 2003 13:51:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBgm-0007Wi-2c for megaco@optimus.ietf.org; Fri, 07 Nov 2003 13:50:32 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28989 for ; Fri, 7 Nov 2003 13:50:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIBgj-0001DE-00 for megaco@ietf.org; Fri, 07 Nov 2003 13:50:29 -0500 Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx with esmtp (Exim 4.12) id 1AIBgj-0001Bw-00 for megaco@ietf.org; Fri, 07 Nov 2003 13:50:29 -0500 Received: from VNANDURI-W2K1.cisco.com (sjc-vpn3-984.cisco.com [10.21.67.216]) by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id hA7InuiO020082; Fri, 7 Nov 2003 10:49:57 -0800 (PST) Message-Id: <4.3.2.7.2.20031107104101.0229bdc0@mira-sjc5-6.cisco.com> X-Sender: vnanduri@mira-sjc5-6.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 07 Nov 2003 10:49:55 -0800 To: megaco@ietf.org From: Venkata Narasimha Murthy Nanduri Cc: skyeung@cisco.com, jquan@cisco.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Megaco] Question about Tone list Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Hi, When the MGC specify: "-Signals "{dg/pt {tl=[d5,d5,d6,d7,d8,d9], Duration = 15000}}" Does it mean that Timeout between two consecutive tones is 15000/5 milliseconds? Thanks Venkata _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Fri Nov 7 14:01:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29471 for ; Fri, 7 Nov 2003 14:01:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBqx-00089Y-1z; Fri, 07 Nov 2003 14:01:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBqM-00087x-Qi for megaco@optimus.ietf.org; Fri, 07 Nov 2003 14:00:26 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29404 for ; Fri, 7 Nov 2003 14:00:15 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIBqK-0001Ll-00 for megaco@ietf.org; Fri, 07 Nov 2003 14:00:24 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AIBqK-0001Jz-00 for megaco@ietf.org; Fri, 07 Nov 2003 14:00:24 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA7IxlR06508 for ; Fri, 7 Nov 2003 13:59:47 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 7 Nov 2003 13:59:48 -0500 Message-ID: From: "Kevin Boyle" To: Venkata Narasimha Murthy Nanduri , megaco@ietf.org Cc: skyeung@cisco.com, jquan@cisco.com Subject: RE: [Megaco] Question about Tone list Date: Fri, 7 Nov 2003 13:59:42 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Two comments: First, this signalling is illegal, as it is missing the ind parameter, and ind has no default value. The MG would reject this Signals descriptor. Second, duration means duration. Start at the beginning of the list, and play out the tones in order until you reach the duration specified. At that time the signal will halt, regardless of which digit is being played out. Duration does not have any effect on inter-tone duration -- only on overall duration. Kevin -----Original Message----- From: Venkata Narasimha Murthy Nanduri [mailto:vnanduri@cisco.com] Sent: Friday, November 07, 2003 1:50 PM To: megaco@ietf.org Cc: skyeung@cisco.com; jquan@cisco.com Subject: [Megaco] Question about Tone list Hi, When the MGC specify: "-Signals "{dg/pt {tl=[d5,d5,d6,d7,d8,d9], Duration = 15000}}" Does it mean that Timeout between two consecutive tones is 15000/5 milliseconds? Thanks Venkata _______________________________________________ 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 exim@www1.ietf.org Fri Nov 7 14:01:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29487 for ; Fri, 7 Nov 2003 14:01:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBqy-0008B8-Rw for megaco-archive@odin.ietf.org; Fri, 07 Nov 2003 14:01:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA7J14qm031432 for megaco-archive@odin.ietf.org; Fri, 7 Nov 2003 14:01:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBqy-0008At-N3 for megaco-web-archive@optimus.ietf.org; Fri, 07 Nov 2003 14:01:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29425 for ; Fri, 7 Nov 2003 14:00:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIBqw-0001MQ-00 for megaco-web-archive@ietf.org; Fri, 07 Nov 2003 14:01:02 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AIBqv-0001MN-00 for megaco-web-archive@ietf.org; Fri, 07 Nov 2003 14:01:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBqx-00089Y-1z; Fri, 07 Nov 2003 14:01:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBqM-00087x-Qi for megaco@optimus.ietf.org; Fri, 07 Nov 2003 14:00:26 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29404 for ; Fri, 7 Nov 2003 14:00:15 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIBqK-0001Ll-00 for megaco@ietf.org; Fri, 07 Nov 2003 14:00:24 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AIBqK-0001Jz-00 for megaco@ietf.org; Fri, 07 Nov 2003 14:00:24 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA7IxlR06508 for ; Fri, 7 Nov 2003 13:59:47 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 7 Nov 2003 13:59:48 -0500 Message-ID: From: "Kevin Boyle" To: Venkata Narasimha Murthy Nanduri , megaco@ietf.org Cc: skyeung@cisco.com, jquan@cisco.com Subject: RE: [Megaco] Question about Tone list Date: Fri, 7 Nov 2003 13:59:42 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Two comments: First, this signalling is illegal, as it is missing the ind parameter, and ind has no default value. The MG would reject this Signals descriptor. Second, duration means duration. Start at the beginning of the list, and play out the tones in order until you reach the duration specified. At that time the signal will halt, regardless of which digit is being played out. Duration does not have any effect on inter-tone duration -- only on overall duration. Kevin -----Original Message----- From: Venkata Narasimha Murthy Nanduri [mailto:vnanduri@cisco.com] Sent: Friday, November 07, 2003 1:50 PM To: megaco@ietf.org Cc: skyeung@cisco.com; jquan@cisco.com Subject: [Megaco] Question about Tone list Hi, When the MGC specify: "-Signals "{dg/pt {tl=[d5,d5,d6,d7,d8,d9], Duration = 15000}}" Does it mean that Timeout between two consecutive tones is 15000/5 milliseconds? Thanks Venkata _______________________________________________ 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-admin@ietf.org Fri Nov 7 14:13:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00257 for ; Fri, 7 Nov 2003 14:13:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIC2X-0000eF-HB; Fri, 07 Nov 2003 14:13:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIC2W-0000e2-20 for megaco@optimus.ietf.org; Fri, 07 Nov 2003 14:13:00 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29960 for ; Fri, 7 Nov 2003 14:12:45 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIC2Q-0001UZ-00 for megaco@ietf.org; Fri, 07 Nov 2003 14:12:54 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AIC2P-0001Tt-00 for megaco@ietf.org; Fri, 07 Nov 2003 14:12:53 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA7JCMR08881 for ; Fri, 7 Nov 2003 14:12:23 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 7 Nov 2003 14:12:23 -0500 Message-ID: From: "Kevin Boyle" To: skyeung Cc: Venkata Narasimha Murthy Nanduri , megaco@ietf.org, jquan@cisco.com Subject: RE: [Megaco] Question about Tone list Date: Fri, 7 Nov 2003 14:12:19 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , The signals descriptor provided will play each digit for the length of time provisioned in the MG. There is no way to override the duration of one signal in a list using playtone. If you need to play a list of signals and be able to override the signals individually, then you have to use the SignalList construct. Because playtone is, itself, a signal, the duration parameter applies to the entire list as a whole (that is, it applies to pt, not the individual tones in the tl list). The tones in the list are played out according to their provisioning in the MG. Kevin _____ From: skyeung [mailto:skyeung@cisco.com] Sent: Friday, November 07, 2003 2:06 PM To: Boyle, Kevin [NCRTP:3Z40:EXCH] Cc: Venkata Narasimha Murthy Nanduri; megaco@ietf.org; jquan@cisco.com Subject: Re: [Megaco] Question about Tone list Hi Kevin: How long will each signal be played? Is each individual signal's play time equal to: Duration divided by the total number of signals, i.e. 15000/6? Or does the duration includes the inter-signal gap? Thank you very much! Kevin Boyle wrote: Two comments: First, this signalling is illegal, as it is missing the ind parameter, and ind has no default value. The MG would reject this Signals descriptor. Second, duration means duration. Start at the beginning of the list, and play out the tones in order until you reach the duration specified. At that time the signal will halt, regardless of which digit is being played out. Duration does not have any effect on inter-tone duration -- only on overall duration. Kevin -----Original Message----- From: Venkata Narasimha Murthy Nanduri [mailto:vnanduri@cisco.com ] Sent: Friday, November 07, 2003 1:50 PM To: megaco@ietf.org Cc: skyeung@cisco.com ; jquan@cisco.com Subject: [Megaco] Question about Tone list Hi, When the MGC specify: "-Signals "{dg/pt {tl=[d5,d5,d6,d7,d8,d9], Duration = 15000}}" Does it mean that Timeout between two consecutive tones is 15000/5 milliseconds? Thanks Venkata _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco -- Steve Yeung Software Engineer 408-853-4214 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Fri Nov 7 14:13:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00283 for ; Fri, 7 Nov 2003 14:13:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIC2Z-0000f5-G2 for megaco-archive@odin.ietf.org; Fri, 07 Nov 2003 14:13:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA7JD30H002537 for megaco-archive@odin.ietf.org; Fri, 7 Nov 2003 14:13:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIC2Z-0000eq-B6 for megaco-web-archive@optimus.ietf.org; Fri, 07 Nov 2003 14:13:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00014 for ; Fri, 7 Nov 2003 14:12:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIC2W-0001Uo-00 for megaco-web-archive@ietf.org; Fri, 07 Nov 2003 14:13:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AIC2W-0001Ul-00 for megaco-web-archive@ietf.org; Fri, 07 Nov 2003 14:13:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIC2X-0000eF-HB; Fri, 07 Nov 2003 14:13:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIC2W-0000e2-20 for megaco@optimus.ietf.org; Fri, 07 Nov 2003 14:13:00 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29960 for ; Fri, 7 Nov 2003 14:12:45 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIC2Q-0001UZ-00 for megaco@ietf.org; Fri, 07 Nov 2003 14:12:54 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AIC2P-0001Tt-00 for megaco@ietf.org; Fri, 07 Nov 2003 14:12:53 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA7JCMR08881 for ; Fri, 7 Nov 2003 14:12:23 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 7 Nov 2003 14:12:23 -0500 Message-ID: From: "Kevin Boyle" To: skyeung Cc: Venkata Narasimha Murthy Nanduri , megaco@ietf.org, jquan@cisco.com Subject: RE: [Megaco] Question about Tone list Date: Fri, 7 Nov 2003 14:12:19 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , The signals descriptor provided will play each digit for the length of time provisioned in the MG. There is no way to override the duration of one signal in a list using playtone. If you need to play a list of signals and be able to override the signals individually, then you have to use the SignalList construct. Because playtone is, itself, a signal, the duration parameter applies to the entire list as a whole (that is, it applies to pt, not the individual tones in the tl list). The tones in the list are played out according to their provisioning in the MG. Kevin _____ From: skyeung [mailto:skyeung@cisco.com] Sent: Friday, November 07, 2003 2:06 PM To: Boyle, Kevin [NCRTP:3Z40:EXCH] Cc: Venkata Narasimha Murthy Nanduri; megaco@ietf.org; jquan@cisco.com Subject: Re: [Megaco] Question about Tone list Hi Kevin: How long will each signal be played? Is each individual signal's play time equal to: Duration divided by the total number of signals, i.e. 15000/6? Or does the duration includes the inter-signal gap? Thank you very much! Kevin Boyle wrote: Two comments: First, this signalling is illegal, as it is missing the ind parameter, and ind has no default value. The MG would reject this Signals descriptor. Second, duration means duration. Start at the beginning of the list, and play out the tones in order until you reach the duration specified. At that time the signal will halt, regardless of which digit is being played out. Duration does not have any effect on inter-tone duration -- only on overall duration. Kevin -----Original Message----- From: Venkata Narasimha Murthy Nanduri [mailto:vnanduri@cisco.com ] Sent: Friday, November 07, 2003 1:50 PM To: megaco@ietf.org Cc: skyeung@cisco.com ; jquan@cisco.com Subject: [Megaco] Question about Tone list Hi, When the MGC specify: "-Signals "{dg/pt {tl=[d5,d5,d6,d7,d8,d9], Duration = 15000}}" Does it mean that Timeout between two consecutive tones is 15000/5 milliseconds? Thanks Venkata _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco -- Steve Yeung Software Engineer 408-853-4214 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Fri Nov 7 14:14:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00809 for ; Fri, 7 Nov 2003 14:14:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIC3V-0000mH-8s; Fri, 07 Nov 2003 14:14:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBwW-0008Sq-Ml for megaco@optimus.ietf.org; Fri, 07 Nov 2003 14:06:48 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29672 for ; Fri, 7 Nov 2003 14:06:36 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIBwU-0001QW-00 for megaco@ietf.org; Fri, 07 Nov 2003 14:06:46 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AIBwT-0001Q8-00 for megaco@ietf.org; Fri, 07 Nov 2003 14:06:45 -0500 Received: from cisco.com (171.71.177.238) by sj-iport-3.cisco.com with ESMTP; 07 Nov 2003 11:11:29 -0800 Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com [171.71.163.34]) by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id hA7J67mW003750; Fri, 7 Nov 2003 11:06:13 -0800 (PST) Received: from cisco.com (dhcp-171-71-9-171.cisco.com [171.71.9.171]) by mira-sjc5-a.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id ALH97579; Fri, 7 Nov 2003 11:06:06 -0800 (PST) Message-ID: <3FABED1E.10100@cisco.com> Date: Fri, 07 Nov 2003 11:06:06 -0800 From: skyeung User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 X-Accept-Language: en, zh-hk, zh, zh-CN, zh-TW MIME-Version: 1.0 To: Kevin Boyle CC: Venkata Narasimha Murthy Nanduri , megaco@ietf.org, jquan@cisco.com Subject: Re: [Megaco] Question about Tone list References: Content-Type: multipart/alternative; boundary="------------070006070003090306090202" Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , --------------070006070003090306090202 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi Kevin: How long will each signal be played? Is each individual signal's play time equal to: Duration divided by the total number of signals, i.e. 15000/6? Or does the duration includes the inter-signal gap? Thank you very much! Kevin Boyle wrote: > Two comments: > > First, this signalling is illegal, as it is missing the ind parameter, > and ind has no default value. The MG would reject this Signals > descriptor. > > Second, duration means duration. Start at the beginning of the list, > and play out the tones in order until you reach the duration > specified. At that time the signal will halt, regardless of which > digit is being played out. Duration does not have any effect on > inter-tone duration -- only on overall duration. > > Kevin > > -----Original Message----- > From: Venkata Narasimha Murthy Nanduri [mailto:vnanduri@cisco.com] > Sent: Friday, November 07, 2003 1:50 PM > To: megaco@ietf.org > Cc: skyeung@cisco.com; jquan@cisco.com > Subject: [Megaco] Question about Tone list > > Hi, > > > When the MGC specify: > > "-Signals "{dg/pt {tl=[d5,d5,d6,d7,d8,d9], Duration = 15000}}" > > Does it mean that Timeout between two consecutive tones is 15000/5 > milliseconds? > > Thanks > Venkata > > > _______________________________________________ > Megaco mailing list > Megaco@ietf.org > https://www1.ietf.org/mailman/listinfo/megaco > -- Steve Yeung Software Engineer 408-853-4214 --------------070006070003090306090202 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Kevin:

        How long will each signal be played?  Is each individual signal's play
time equal to:  Duration divided by the total number of signals, i.e.
15000/6?

        Or does the duration includes the inter-signal gap?

Thank you very much!


Kevin Boyle wrote:
RE: [Megaco] Question about Tone list

Two comments:

First, this signalling is illegal, as it is missing the ind parameter, and ind has no default value.  The MG would reject this Signals descriptor.

Second, duration means duration.  Start at the beginning of the list, and play out the tones in order until you reach the duration specified.  At that time the signal will halt, regardless of which digit is being played out.  Duration does not have any effect on inter-tone duration -- only on overall duration.

Kevin

-----Original Message-----
From: Venkata Narasimha Murthy Nanduri [mailto:vnanduri@cisco.com]
Sent: Friday, November 07, 2003 1:50 PM
To: megaco@ietf.org
Cc: skyeung@cisco.com; jquan@cisco.com
Subject: [Megaco] Question about Tone list

Hi,


When the MGC specify:

"-Signals "{dg/pt {tl=[d5,d5,d6,d7,d8,d9], Duration = 15000}}"

Does it mean that Timeout between two consecutive tones is 15000/5 milliseconds?

Thanks
Venkata


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


-- 
Steve Yeung
Software Engineer
408-853-4214

--------------070006070003090306090202-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Fri Nov 7 14:14:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00834 for ; Fri, 7 Nov 2003 14:14:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIC3X-0000pm-7Q for megaco-archive@odin.ietf.org; Fri, 07 Nov 2003 14:14:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA7JE3gU003200 for megaco-archive@odin.ietf.org; Fri, 7 Nov 2003 14:14:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIC3X-0000pW-3o for megaco-web-archive@optimus.ietf.org; Fri, 07 Nov 2003 14:14:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00536 for ; Fri, 7 Nov 2003 14:13:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIC3U-0001WR-00 for megaco-web-archive@ietf.org; Fri, 07 Nov 2003 14:14:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AIC3T-0001WO-00 for megaco-web-archive@ietf.org; Fri, 07 Nov 2003 14:13:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIC3V-0000mH-8s; Fri, 07 Nov 2003 14:14:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIBwW-0008Sq-Ml for megaco@optimus.ietf.org; Fri, 07 Nov 2003 14:06:48 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29672 for ; Fri, 7 Nov 2003 14:06:36 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIBwU-0001QW-00 for megaco@ietf.org; Fri, 07 Nov 2003 14:06:46 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AIBwT-0001Q8-00 for megaco@ietf.org; Fri, 07 Nov 2003 14:06:45 -0500 Received: from cisco.com (171.71.177.238) by sj-iport-3.cisco.com with ESMTP; 07 Nov 2003 11:11:29 -0800 Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com [171.71.163.34]) by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id hA7J67mW003750; Fri, 7 Nov 2003 11:06:13 -0800 (PST) Received: from cisco.com (dhcp-171-71-9-171.cisco.com [171.71.9.171]) by mira-sjc5-a.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id ALH97579; Fri, 7 Nov 2003 11:06:06 -0800 (PST) Message-ID: <3FABED1E.10100@cisco.com> Date: Fri, 07 Nov 2003 11:06:06 -0800 From: skyeung User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 X-Accept-Language: en, zh-hk, zh, zh-CN, zh-TW MIME-Version: 1.0 To: Kevin Boyle CC: Venkata Narasimha Murthy Nanduri , megaco@ietf.org, jquan@cisco.com Subject: Re: [Megaco] Question about Tone list References: Content-Type: multipart/alternative; boundary="------------070006070003090306090202" Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , --------------070006070003090306090202 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi Kevin: How long will each signal be played? Is each individual signal's play time equal to: Duration divided by the total number of signals, i.e. 15000/6? Or does the duration includes the inter-signal gap? Thank you very much! Kevin Boyle wrote: > Two comments: > > First, this signalling is illegal, as it is missing the ind parameter, > and ind has no default value. The MG would reject this Signals > descriptor. > > Second, duration means duration. Start at the beginning of the list, > and play out the tones in order until you reach the duration > specified. At that time the signal will halt, regardless of which > digit is being played out. Duration does not have any effect on > inter-tone duration -- only on overall duration. > > Kevin > > -----Original Message----- > From: Venkata Narasimha Murthy Nanduri [mailto:vnanduri@cisco.com] > Sent: Friday, November 07, 2003 1:50 PM > To: megaco@ietf.org > Cc: skyeung@cisco.com; jquan@cisco.com > Subject: [Megaco] Question about Tone list > > Hi, > > > When the MGC specify: > > "-Signals "{dg/pt {tl=[d5,d5,d6,d7,d8,d9], Duration = 15000}}" > > Does it mean that Timeout between two consecutive tones is 15000/5 > milliseconds? > > Thanks > Venkata > > > _______________________________________________ > Megaco mailing list > Megaco@ietf.org > https://www1.ietf.org/mailman/listinfo/megaco > -- Steve Yeung Software Engineer 408-853-4214 --------------070006070003090306090202 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Kevin:

        How long will each signal be played?  Is each individual signal's play
time equal to:  Duration divided by the total number of signals, i.e.
15000/6?

        Or does the duration includes the inter-signal gap?

Thank you very much!


Kevin Boyle wrote:
RE: [Megaco] Question about Tone list

Two comments:

First, this signalling is illegal, as it is missing the ind parameter, and ind has no default value.  The MG would reject this Signals descriptor.

Second, duration means duration.  Start at the beginning of the list, and play out the tones in order until you reach the duration specified.  At that time the signal will halt, regardless of which digit is being played out.  Duration does not have any effect on inter-tone duration -- only on overall duration.

Kevin

-----Original Message-----
From: Venkata Narasimha Murthy Nanduri [mailto:vnanduri@cisco.com]
Sent: Friday, November 07, 2003 1:50 PM
To: megaco@ietf.org
Cc: skyeung@cisco.com; jquan@cisco.com
Subject: [Megaco] Question about Tone list

Hi,


When the MGC specify:

"-Signals "{dg/pt {tl=[d5,d5,d6,d7,d8,d9], Duration = 15000}}"

Does it mean that Timeout between two consecutive tones is 15000/5 milliseconds?

Thanks
Venkata


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


-- 
Steve Yeung
Software Engineer
408-853-4214

--------------070006070003090306090202-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Fri Nov 7 14:46:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03636 for ; Fri, 7 Nov 2003 14:46:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AICYT-0003I7-9D; Fri, 07 Nov 2003 14:46:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIC6l-00013x-1M for megaco@optimus.ietf.org; Fri, 07 Nov 2003 14:17:23 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02095 for ; Fri, 7 Nov 2003 14:17:11 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIC6i-0001c4-00 for megaco@ietf.org; Fri, 07 Nov 2003 14:17:20 -0500 Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx with esmtp (Exim 4.12) id 1AIC6i-0001bo-00 for megaco@ietf.org; Fri, 07 Nov 2003 14:17:20 -0500 Received: from cypher.cisco.com (cypher.cisco.com [171.69.11.143]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hA7JGlAu011509; Fri, 7 Nov 2003 11:16:48 -0800 (PST) Date: Fri, 7 Nov 2003 11:16:47 -0800 (PST) From: Julie Quan To: Kevin Boyle cc: Venkata Narasimha Murthy Nanduri , megaco@ietf.org, skyeung@cisco.com Subject: RE: [Megaco] Question about Tone list In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Hi, Kevin, If each digit timeout value is default to 100 millisecond, and the Inter-Digit duration default is 60 millisecond. The time spending on playing digits is 6*100 + 5*60 = 900 millisecond. But there is still 14+ seconds left on specified duration. Do we play the last digit till the 15 seoncds timeout? or do we stop? Thanks a lot. - Julie > Two comments: > > First, this signalling is illegal, as it is missing the ind parameter, and > ind has no default value. The MG would reject this Signals descriptor. > > Second, duration means duration. Start at the beginning of the list, and > play out the tones in order until you reach the duration specified. At that > time the signal will halt, regardless of which digit is being played out. > Duration does not have any effect on inter-tone duration -- only on overall > duration. > > Kevin > > -----Original Message----- > From: Venkata Narasimha Murthy Nanduri [mailto:vnanduri@cisco.com] > Sent: Friday, November 07, 2003 1:50 PM > To: megaco@ietf.org > Cc: skyeung@cisco.com; jquan@cisco.com > Subject: [Megaco] Question about Tone list > > Hi, > > > When the MGC specify: > > "-Signals "{dg/pt {tl=[d5,d5,d6,d7,d8,d9], Duration = 15000}}" > > Does it mean that Timeout between two consecutive tones is 15000/5 > milliseconds? > > Thanks > Venkata > > > _______________________________________________ > 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 > > ================================================================ Julie Quan Phone & Fax: 949-823-1428 Pager: jquan@epage.cisco.com 1-800-796-7363 PIN 100-9425 Cisco Systems 121 Theory Dr. Irvine, CA 92612 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Fri Nov 7 14:46:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03651 for ; Fri, 7 Nov 2003 14:46:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AICYV-0003J2-LL for megaco-archive@odin.ietf.org; Fri, 07 Nov 2003 14:46:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA7Jk3Cr012702 for megaco-archive@odin.ietf.org; Fri, 7 Nov 2003 14:46:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AICYV-0003In-IE for megaco-web-archive@optimus.ietf.org; Fri, 07 Nov 2003 14:46:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03627 for ; Fri, 7 Nov 2003 14:45:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AICYS-0001zp-00 for megaco-web-archive@ietf.org; Fri, 07 Nov 2003 14:46:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AICYS-0001zm-00 for megaco-web-archive@ietf.org; Fri, 07 Nov 2003 14:46:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AICYT-0003I7-9D; Fri, 07 Nov 2003 14:46:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIC6l-00013x-1M for megaco@optimus.ietf.org; Fri, 07 Nov 2003 14:17:23 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02095 for ; Fri, 7 Nov 2003 14:17:11 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIC6i-0001c4-00 for megaco@ietf.org; Fri, 07 Nov 2003 14:17:20 -0500 Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx with esmtp (Exim 4.12) id 1AIC6i-0001bo-00 for megaco@ietf.org; Fri, 07 Nov 2003 14:17:20 -0500 Received: from cypher.cisco.com (cypher.cisco.com [171.69.11.143]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hA7JGlAu011509; Fri, 7 Nov 2003 11:16:48 -0800 (PST) Date: Fri, 7 Nov 2003 11:16:47 -0800 (PST) From: Julie Quan To: Kevin Boyle cc: Venkata Narasimha Murthy Nanduri , megaco@ietf.org, skyeung@cisco.com Subject: RE: [Megaco] Question about Tone list In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Hi, Kevin, If each digit timeout value is default to 100 millisecond, and the Inter-Digit duration default is 60 millisecond. The time spending on playing digits is 6*100 + 5*60 = 900 millisecond. But there is still 14+ seconds left on specified duration. Do we play the last digit till the 15 seoncds timeout? or do we stop? Thanks a lot. - Julie > Two comments: > > First, this signalling is illegal, as it is missing the ind parameter, and > ind has no default value. The MG would reject this Signals descriptor. > > Second, duration means duration. Start at the beginning of the list, and > play out the tones in order until you reach the duration specified. At that > time the signal will halt, regardless of which digit is being played out. > Duration does not have any effect on inter-tone duration -- only on overall > duration. > > Kevin > > -----Original Message----- > From: Venkata Narasimha Murthy Nanduri [mailto:vnanduri@cisco.com] > Sent: Friday, November 07, 2003 1:50 PM > To: megaco@ietf.org > Cc: skyeung@cisco.com; jquan@cisco.com > Subject: [Megaco] Question about Tone list > > Hi, > > > When the MGC specify: > > "-Signals "{dg/pt {tl=[d5,d5,d6,d7,d8,d9], Duration = 15000}}" > > Does it mean that Timeout between two consecutive tones is 15000/5 > milliseconds? > > Thanks > Venkata > > > _______________________________________________ > 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 > > ================================================================ Julie Quan Phone & Fax: 949-823-1428 Pager: jquan@epage.cisco.com 1-800-796-7363 PIN 100-9425 Cisco Systems 121 Theory Dr. Irvine, CA 92612 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Fri Nov 7 19:32:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16300 for ; Fri, 7 Nov 2003 19:32:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIH1G-0004wm-0g; Fri, 07 Nov 2003 19:32:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIH0T-0004ue-Bx for megaco@optimus.ietf.org; Fri, 07 Nov 2003 19:31:13 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16246 for ; Fri, 7 Nov 2003 19:31:00 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIH0R-0005mC-00 for megaco@ietf.org; Fri, 07 Nov 2003 19:31:11 -0500 Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AIH0R-0005lk-00 for megaco@ietf.org; Fri, 07 Nov 2003 19:31:11 -0500 Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3]) by hoemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hA80UcY23414 for ; Fri, 7 Nov 2003 18:30:38 -0600 (CST) Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id TAA27176; Fri, 7 Nov 2003 19:30:56 -0500 (EST) Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id TAA27172; Fri, 7 Nov 2003 19:30:55 -0500 (EST) Message-ID: <3FAC38AF.3000907@bell-labs.com> Date: Fri, 07 Nov 2003 19:28:31 -0500 From: Troy Cauble User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: MEGACO list Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Megaco] ServiceChange/ Restart question Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit ON STARTUP an MG sends: ========== MEGACO/1 [192.168.17.217] Transaction = 667 { Context = - { ServiceChange = ROOT { Services { Method = Restart } } } } Does the use of ROOT imply that all terminations are InService? If the MG is configured (via SNMP for example) to have some terminations disabled, should it send "Method = Restart" for each enabled termination instead of one for ROOT? (All in the same Context/Transaction/Message?) If so, should it also send "Method = Forced" or "Method = Graceful" for the disabled terminations? Thanks, -troy _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Fri Nov 7 19:32:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16315 for ; Fri, 7 Nov 2003 19:32:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIH1I-0004ys-LE for megaco-archive@odin.ietf.org; Fri, 07 Nov 2003 19:32:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA80W4FU019140 for megaco-archive@odin.ietf.org; Fri, 7 Nov 2003 19:32:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIH1I-0004yd-Fp for megaco-web-archive@optimus.ietf.org; Fri, 07 Nov 2003 19:32:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16282 for ; Fri, 7 Nov 2003 19:31:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIH1G-0005nG-00 for megaco-web-archive@ietf.org; Fri, 07 Nov 2003 19:32:02 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AIH1G-0005nD-00 for megaco-web-archive@ietf.org; Fri, 07 Nov 2003 19:32:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIH1G-0004wm-0g; Fri, 07 Nov 2003 19:32:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIH0T-0004ue-Bx for megaco@optimus.ietf.org; Fri, 07 Nov 2003 19:31:13 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16246 for ; Fri, 7 Nov 2003 19:31:00 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIH0R-0005mC-00 for megaco@ietf.org; Fri, 07 Nov 2003 19:31:11 -0500 Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AIH0R-0005lk-00 for megaco@ietf.org; Fri, 07 Nov 2003 19:31:11 -0500 Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3]) by hoemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hA80UcY23414 for ; Fri, 7 Nov 2003 18:30:38 -0600 (CST) Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id TAA27176; Fri, 7 Nov 2003 19:30:56 -0500 (EST) Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id TAA27172; Fri, 7 Nov 2003 19:30:55 -0500 (EST) Message-ID: <3FAC38AF.3000907@bell-labs.com> Date: Fri, 07 Nov 2003 19:28:31 -0500 From: Troy Cauble User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: MEGACO list Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Megaco] ServiceChange/ Restart question Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit ON STARTUP an MG sends: ========== MEGACO/1 [192.168.17.217] Transaction = 667 { Context = - { ServiceChange = ROOT { Services { Method = Restart } } } } Does the use of ROOT imply that all terminations are InService? If the MG is configured (via SNMP for example) to have some terminations disabled, should it send "Method = Restart" for each enabled termination instead of one for ROOT? (All in the same Context/Transaction/Message?) If so, should it also send "Method = Forced" or "Method = Graceful" for the disabled terminations? Thanks, -troy _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Sat Nov 8 13:25:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22763 for ; Sat, 8 Nov 2003 13:25:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIXlf-0000zV-4N; Sat, 08 Nov 2003 13:25:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIXlJ-0000yS-MF for megaco@optimus.ietf.org; Sat, 08 Nov 2003 13:24:41 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22716 for ; Sat, 8 Nov 2003 13:24:28 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIXlH-0002f8-00 for megaco@ietf.org; Sat, 08 Nov 2003 13:24:39 -0500 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1AIXlH-0002e3-00 for megaco@ietf.org; Sat, 08 Nov 2003 13:24:39 -0500 Received: from cisco.com (64.104.129.221) by sj-iport-5.cisco.com with ESMTP; 08 Nov 2003 10:26:49 -0800 Received: from samrat.cisco.com (samrat.cisco.com [192.135.241.21]) by india-msg-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hA8Npj0s023879; Sat, 8 Nov 2003 23:51:45 GMT Received: from cisco.com ([192.135.241.109]) by samrat.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id XAA27767; Sat, 8 Nov 2003 23:54:06 +0530 (IST) Message-ID: <3FAD387E.E5B5497E@cisco.com> Date: Sun, 09 Nov 2003 00:09:58 +0530 From: Venugopal Sharma X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Troy Cauble CC: MEGACO list Subject: Re: [Megaco] ServiceChange/ Restart question References: <3FAC38AF.3000907@bell-labs.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Troy, I think ROOT termination indicates MG as a whole. In Service and Out of Service messages are sent only at the MG level and not per terminations. Hence 'In service' should only indicate that the H248 stack is up and running in the MG. thanks / Venu -------------- Troy Cauble wrote: > > ON STARTUP an MG sends: > ========== > > MEGACO/1 [192.168.17.217] > Transaction = 667 { > Context = - { > ServiceChange = ROOT { > Services { > Method = Restart > } > } > } > } > > Does the use of ROOT imply that all terminations are InService? > > If the MG is configured (via SNMP for example) to have some terminations > disabled, should it send "Method = Restart" for each enabled termination > instead of one for ROOT? (All in the same Context/Transaction/Message?) > > If so, should it also send "Method = Forced" or "Method = Graceful" > for the disabled terminations? > > Thanks, > > -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 exim@www1.ietf.org Sat Nov 8 13:25:25 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22777 for ; Sat, 8 Nov 2003 13:25:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIXlj-00010E-HQ for megaco-archive@odin.ietf.org; Sat, 08 Nov 2003 13:25:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA8IP7wc003855 for megaco-archive@odin.ietf.org; Sat, 8 Nov 2003 13:25:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIXlj-000106-Cd for megaco-web-archive@optimus.ietf.org; Sat, 08 Nov 2003 13:25:07 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22729 for ; Sat, 8 Nov 2003 13:24:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIXlh-0002fN-00 for megaco-web-archive@ietf.org; Sat, 08 Nov 2003 13:25:05 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AIXlg-0002fK-00 for megaco-web-archive@ietf.org; Sat, 08 Nov 2003 13:25:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIXlf-0000zV-4N; Sat, 08 Nov 2003 13:25:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIXlJ-0000yS-MF for megaco@optimus.ietf.org; Sat, 08 Nov 2003 13:24:41 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22716 for ; Sat, 8 Nov 2003 13:24:28 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AIXlH-0002f8-00 for megaco@ietf.org; Sat, 08 Nov 2003 13:24:39 -0500 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1AIXlH-0002e3-00 for megaco@ietf.org; Sat, 08 Nov 2003 13:24:39 -0500 Received: from cisco.com (64.104.129.221) by sj-iport-5.cisco.com with ESMTP; 08 Nov 2003 10:26:49 -0800 Received: from samrat.cisco.com (samrat.cisco.com [192.135.241.21]) by india-msg-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hA8Npj0s023879; Sat, 8 Nov 2003 23:51:45 GMT Received: from cisco.com ([192.135.241.109]) by samrat.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id XAA27767; Sat, 8 Nov 2003 23:54:06 +0530 (IST) Message-ID: <3FAD387E.E5B5497E@cisco.com> Date: Sun, 09 Nov 2003 00:09:58 +0530 From: Venugopal Sharma X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Troy Cauble CC: MEGACO list Subject: Re: [Megaco] ServiceChange/ Restart question References: <3FAC38AF.3000907@bell-labs.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Troy, I think ROOT termination indicates MG as a whole. In Service and Out of Service messages are sent only at the MG level and not per terminations. Hence 'In service' should only indicate that the H248 stack is up and running in the MG. thanks / Venu -------------- Troy Cauble wrote: > > ON STARTUP an MG sends: > ========== > > MEGACO/1 [192.168.17.217] > Transaction = 667 { > Context = - { > ServiceChange = ROOT { > Services { > Method = Restart > } > } > } > } > > Does the use of ROOT imply that all terminations are InService? > > If the MG is configured (via SNMP for example) to have some terminations > disabled, should it send "Method = Restart" for each enabled termination > instead of one for ROOT? (All in the same Context/Transaction/Message?) > > If so, should it also send "Method = Forced" or "Method = Graceful" > for the disabled terminations? > > Thanks, > > -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-admin@ietf.org Sun Nov 9 19:59:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20608 for ; Sun, 9 Nov 2003 19:59:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ0OT-0003NM-46; Sun, 09 Nov 2003 19:59:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ0OF-0003N1-5C for megaco@optimus.ietf.org; Sun, 09 Nov 2003 19:58:47 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20587 for ; Sun, 9 Nov 2003 19:58:34 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJ0OD-0003Ds-00 for megaco@ietf.org; Sun, 09 Nov 2003 19:58:45 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AJ0OC-0003DL-00 for megaco@ietf.org; Sun, 09 Nov 2003 19:58:44 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAA0w8o14379 for ; Sun, 9 Nov 2003 19:58:09 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Sun, 9 Nov 2003 19:58:09 -0500 Message-ID: From: "Kevin Boyle" To: Venugopal Sharma , Troy Cauble Cc: MEGACO list Subject: RE: [Megaco] ServiceChange/ Restart question Date: Sun, 9 Nov 2003 19:58:08 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Not true. ServiceStates is a parameter on every termination, not just Root. Further, the spec indicates that the default value for the ServiceStates parameter is "Inservice". This means that upon registration, all terminations are assumed to be inservice. The MG can prevent this by sending subsequent SC Forced messages on the terminations that are out of service. Kevin -----Original Message----- From: Venugopal Sharma [mailto:skolari@cisco.com] Sent: Saturday, November 08, 2003 1:40 PM To: Troy Cauble Cc: MEGACO list Subject: Re: [Megaco] ServiceChange/ Restart question Troy, I think ROOT termination indicates MG as a whole. In Service and Out of Service messages are sent only at the MG level and not per terminations. Hence 'In service' should only indicate that the H248 stack is up and running in the MG. thanks / Venu -------------- Troy Cauble wrote: > > ON STARTUP an MG sends: > ========== > > MEGACO/1 [192.168.17.217] > Transaction = 667 { > Context = - { > ServiceChange = ROOT { > Services { > Method = Restart > } > } > } > } > > Does the use of ROOT imply that all terminations are InService? > > If the MG is configured (via SNMP for example) to have some > terminations disabled, should it send "Method = Restart" for each > enabled termination instead of one for ROOT? (All in the same > Context/Transaction/Message?) > > If so, should it also send "Method = Forced" or "Method = Graceful" > for the disabled terminations? > > Thanks, > > -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 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Sun Nov 9 19:59:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20625 for ; Sun, 9 Nov 2003 19:59:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ0OX-0003OE-QK for megaco-archive@odin.ietf.org; Sun, 09 Nov 2003 19:59:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAA0x5Ro013024 for megaco-archive@odin.ietf.org; Sun, 9 Nov 2003 19:59:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ0OX-0003Nz-Mv for megaco-web-archive@optimus.ietf.org; Sun, 09 Nov 2003 19:59:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20600 for ; Sun, 9 Nov 2003 19:58:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJ0OV-0003E7-00 for megaco-web-archive@ietf.org; Sun, 09 Nov 2003 19:59:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJ0OV-0003E3-00 for megaco-web-archive@ietf.org; Sun, 09 Nov 2003 19:59:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ0OT-0003NM-46; Sun, 09 Nov 2003 19:59:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ0OF-0003N1-5C for megaco@optimus.ietf.org; Sun, 09 Nov 2003 19:58:47 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20587 for ; Sun, 9 Nov 2003 19:58:34 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJ0OD-0003Ds-00 for megaco@ietf.org; Sun, 09 Nov 2003 19:58:45 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AJ0OC-0003DL-00 for megaco@ietf.org; Sun, 09 Nov 2003 19:58:44 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAA0w8o14379 for ; Sun, 9 Nov 2003 19:58:09 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Sun, 9 Nov 2003 19:58:09 -0500 Message-ID: From: "Kevin Boyle" To: Venugopal Sharma , Troy Cauble Cc: MEGACO list Subject: RE: [Megaco] ServiceChange/ Restart question Date: Sun, 9 Nov 2003 19:58:08 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Not true. ServiceStates is a parameter on every termination, not just Root. Further, the spec indicates that the default value for the ServiceStates parameter is "Inservice". This means that upon registration, all terminations are assumed to be inservice. The MG can prevent this by sending subsequent SC Forced messages on the terminations that are out of service. Kevin -----Original Message----- From: Venugopal Sharma [mailto:skolari@cisco.com] Sent: Saturday, November 08, 2003 1:40 PM To: Troy Cauble Cc: MEGACO list Subject: Re: [Megaco] ServiceChange/ Restart question Troy, I think ROOT termination indicates MG as a whole. In Service and Out of Service messages are sent only at the MG level and not per terminations. Hence 'In service' should only indicate that the H248 stack is up and running in the MG. thanks / Venu -------------- Troy Cauble wrote: > > ON STARTUP an MG sends: > ========== > > MEGACO/1 [192.168.17.217] > Transaction = 667 { > Context = - { > ServiceChange = ROOT { > Services { > Method = Restart > } > } > } > } > > Does the use of ROOT imply that all terminations are InService? > > If the MG is configured (via SNMP for example) to have some > terminations disabled, should it send "Method = Restart" for each > enabled termination instead of one for ROOT? (All in the same > Context/Transaction/Message?) > > If so, should it also send "Method = Forced" or "Method = Graceful" > for the disabled terminations? > > Thanks, > > -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 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Sun Nov 9 20:02:18 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20732 for ; Sun, 9 Nov 2003 20:02:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ0RM-0003a3-SP; Sun, 09 Nov 2003 20:02:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ0Qy-0003Ze-NB for megaco@optimus.ietf.org; Sun, 09 Nov 2003 20:01:36 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20683 for ; Sun, 9 Nov 2003 20:01:24 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJ0Qw-0003KB-00 for megaco@ietf.org; Sun, 09 Nov 2003 20:01:34 -0500 Received: from law15-f76.law15.hotmail.com ([64.4.23.76] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 1AJ0Qw-0003K0-00 for megaco@ietf.org; Sun, 09 Nov 2003 20:01:34 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 9 Nov 2003 17:01:03 -0800 Received: from 210.21.224.54 by lw15fd.law15.hotmail.msn.com with HTTP; Mon, 10 Nov 2003 01:01:03 GMT X-Originating-IP: [210.21.224.54] X-Originating-Email: [juniperfu@hotmail.com] From: "å® ä»" To: megaco@ietf.org Date: Mon, 10 Nov 2003 09:01:03 +0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 10 Nov 2003 01:01:03.0836 (UTC) FILETIME=[1D4801C0:01C3A726] Subject: [Megaco] a problem about audit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , All, When MGC restart or HA, Maybe it need audit the context and termination of MG, and it can send the command Context = * { AuditValue= ROOT {Audit { } } and the MG should return Context = 100 { AuditValue= TermA, TermB } Context = 200 { AuditValue= TermC, TermD } Context = 300 { AuditValue= TermE, TermF } And my problem is if the MG has a lot of context and a megaco message can't include them, So how do the mg return all its context, thanks! juniper _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Sun Nov 9 20:02:25 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20747 for ; Sun, 9 Nov 2003 20:02:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ0RT-0003b3-8q for megaco-archive@odin.ietf.org; Sun, 09 Nov 2003 20:02:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAA127d1013814 for megaco-archive@odin.ietf.org; Sun, 9 Nov 2003 20:02:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ0RS-0003ai-Pw for megaco-web-archive@optimus.ietf.org; Sun, 09 Nov 2003 20:02:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20705 for ; Sun, 9 Nov 2003 20:01:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJ0RQ-0003Ku-00 for megaco-web-archive@ietf.org; Sun, 09 Nov 2003 20:02:04 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJ0RQ-0003Kl-00 for megaco-web-archive@ietf.org; Sun, 09 Nov 2003 20:02:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ0RM-0003a3-SP; Sun, 09 Nov 2003 20:02:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ0Qy-0003Ze-NB for megaco@optimus.ietf.org; Sun, 09 Nov 2003 20:01:36 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20683 for ; Sun, 9 Nov 2003 20:01:24 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJ0Qw-0003KB-00 for megaco@ietf.org; Sun, 09 Nov 2003 20:01:34 -0500 Received: from law15-f76.law15.hotmail.com ([64.4.23.76] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 1AJ0Qw-0003K0-00 for megaco@ietf.org; Sun, 09 Nov 2003 20:01:34 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 9 Nov 2003 17:01:03 -0800 Received: from 210.21.224.54 by lw15fd.law15.hotmail.msn.com with HTTP; Mon, 10 Nov 2003 01:01:03 GMT X-Originating-IP: [210.21.224.54] X-Originating-Email: [juniperfu@hotmail.com] From: "å® ä»" To: megaco@ietf.org Date: Mon, 10 Nov 2003 09:01:03 +0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 10 Nov 2003 01:01:03.0836 (UTC) FILETIME=[1D4801C0:01C3A726] Subject: [Megaco] a problem about audit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , All, When MGC restart or HA, Maybe it need audit the context and termination of MG, and it can send the command Context = * { AuditValue= ROOT {Audit { } } and the MG should return Context = 100 { AuditValue= TermA, TermB } Context = 200 { AuditValue= TermC, TermD } Context = 300 { AuditValue= TermE, TermF } And my problem is if the MG has a lot of context and a megaco message can't include them, So how do the mg return all its context, thanks! juniper _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Sun Nov 9 22:20:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23282 for ; Sun, 9 Nov 2003 22:20:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ2aw-0000QY-BX; Sun, 09 Nov 2003 22:20:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ2aF-0000Pb-Q6 for megaco@optimus.ietf.org; Sun, 09 Nov 2003 22:19:19 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23266 for ; Sun, 9 Nov 2003 22:19:05 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJ2aC-0004yx-00 for megaco@ietf.org; Sun, 09 Nov 2003 22:19:16 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AJ2aC-0004yt-00 for megaco@ietf.org; Sun, 09 Nov 2003 22:19:16 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAA3Ijo16684 for ; Sun, 9 Nov 2003 22:18:45 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Sun, 9 Nov 2003 22:18:46 -0500 Message-ID: From: "Kevin Boyle" To: Julie Quan Cc: Venkata Narasimha Murthy Nanduri , megaco@ietf.org, skyeung@cisco.com Subject: RE: [Megaco] Question about Tone list Date: Sun, 9 Nov 2003 22:18:45 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Well... I would think that the final tone would effectively be overridden to fill out the duration of the list, so the former of the two options. I suppose, however, that it would be up to the MG. Note that with playtone, the ind parameter must be specified. Kevin -----Original Message----- From: Julie Quan [mailto:jquan@cisco.com] Sent: Friday, November 07, 2003 2:17 PM To: Boyle, Kevin [NCRTP:3Z40:EXCH] Cc: Venkata Narasimha Murthy Nanduri; megaco@ietf.org; skyeung@cisco.com Subject: RE: [Megaco] Question about Tone list Hi, Kevin, If each digit timeout value is default to 100 millisecond, and the Inter-Digit duration default is 60 millisecond. The time spending on playing digits is 6*100 + 5*60 = 900 millisecond. But there is still 14+ seconds left on specified duration. Do we play the last digit till the 15 seoncds timeout? or do we stop? Thanks a lot. - Julie > Two comments: > > First, this signalling is illegal, as it is missing the ind parameter, > and ind has no default value. The MG would reject this Signals descriptor. > > Second, duration means duration. Start at the beginning of the list, > and play out the tones in order until you reach the duration > specified. At that time the signal will halt, regardless of which digit is being played out. > Duration does not have any effect on inter-tone duration -- only on > overall duration. > > Kevin > > -----Original Message----- > From: Venkata Narasimha Murthy Nanduri [mailto:vnanduri@cisco.com] > Sent: Friday, November 07, 2003 1:50 PM > To: megaco@ietf.org > Cc: skyeung@cisco.com; jquan@cisco.com > Subject: [Megaco] Question about Tone list > > Hi, > > > When the MGC specify: > > "-Signals "{dg/pt {tl=[d5,d5,d6,d7,d8,d9], Duration = 15000}}" > > Does it mean that Timeout between two consecutive tones is 15000/5 > milliseconds? > > Thanks > Venkata > > > _______________________________________________ > 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 > > ================================================================ Julie Quan Phone & Fax: 949-823-1428 Pager: jquan@epage.cisco.com 1-800-796-7363 PIN 100-9425 Cisco Systems 121 Theory Dr. Irvine, CA 92612 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Sun Nov 9 22:20:25 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23297 for ; Sun, 9 Nov 2003 22:20:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ2b3-0000Rl-Cj for megaco-archive@odin.ietf.org; Sun, 09 Nov 2003 22:20:09 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAA3K8oL001709 for megaco-archive@odin.ietf.org; Sun, 9 Nov 2003 22:20:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ2b1-0000RU-Re for megaco-web-archive@optimus.ietf.org; Sun, 09 Nov 2003 22:20:07 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23272 for ; Sun, 9 Nov 2003 22:19:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJ2ay-0004zI-00 for megaco-web-archive@ietf.org; Sun, 09 Nov 2003 22:20:04 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJ2ay-0004zF-00 for megaco-web-archive@ietf.org; Sun, 09 Nov 2003 22:20:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ2aw-0000QY-BX; Sun, 09 Nov 2003 22:20:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ2aF-0000Pb-Q6 for megaco@optimus.ietf.org; Sun, 09 Nov 2003 22:19:19 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23266 for ; Sun, 9 Nov 2003 22:19:05 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJ2aC-0004yx-00 for megaco@ietf.org; Sun, 09 Nov 2003 22:19:16 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AJ2aC-0004yt-00 for megaco@ietf.org; Sun, 09 Nov 2003 22:19:16 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAA3Ijo16684 for ; Sun, 9 Nov 2003 22:18:45 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Sun, 9 Nov 2003 22:18:46 -0500 Message-ID: From: "Kevin Boyle" To: Julie Quan Cc: Venkata Narasimha Murthy Nanduri , megaco@ietf.org, skyeung@cisco.com Subject: RE: [Megaco] Question about Tone list Date: Sun, 9 Nov 2003 22:18:45 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Well... I would think that the final tone would effectively be overridden to fill out the duration of the list, so the former of the two options. I suppose, however, that it would be up to the MG. Note that with playtone, the ind parameter must be specified. Kevin -----Original Message----- From: Julie Quan [mailto:jquan@cisco.com] Sent: Friday, November 07, 2003 2:17 PM To: Boyle, Kevin [NCRTP:3Z40:EXCH] Cc: Venkata Narasimha Murthy Nanduri; megaco@ietf.org; skyeung@cisco.com Subject: RE: [Megaco] Question about Tone list Hi, Kevin, If each digit timeout value is default to 100 millisecond, and the Inter-Digit duration default is 60 millisecond. The time spending on playing digits is 6*100 + 5*60 = 900 millisecond. But there is still 14+ seconds left on specified duration. Do we play the last digit till the 15 seoncds timeout? or do we stop? Thanks a lot. - Julie > Two comments: > > First, this signalling is illegal, as it is missing the ind parameter, > and ind has no default value. The MG would reject this Signals descriptor. > > Second, duration means duration. Start at the beginning of the list, > and play out the tones in order until you reach the duration > specified. At that time the signal will halt, regardless of which digit is being played out. > Duration does not have any effect on inter-tone duration -- only on > overall duration. > > Kevin > > -----Original Message----- > From: Venkata Narasimha Murthy Nanduri [mailto:vnanduri@cisco.com] > Sent: Friday, November 07, 2003 1:50 PM > To: megaco@ietf.org > Cc: skyeung@cisco.com; jquan@cisco.com > Subject: [Megaco] Question about Tone list > > Hi, > > > When the MGC specify: > > "-Signals "{dg/pt {tl=[d5,d5,d6,d7,d8,d9], Duration = 15000}}" > > Does it mean that Timeout between two consecutive tones is 15000/5 > milliseconds? > > Thanks > Venkata > > > _______________________________________________ > 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 > > ================================================================ Julie Quan Phone & Fax: 949-823-1428 Pager: jquan@epage.cisco.com 1-800-796-7363 PIN 100-9425 Cisco Systems 121 Theory Dr. Irvine, CA 92612 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Sun Nov 9 22:27:17 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23442 for ; Sun, 9 Nov 2003 22:27:17 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ2hg-0000nx-SD; Sun, 09 Nov 2003 22:27:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ2h8-0000nZ-BN for megaco@optimus.ietf.org; Sun, 09 Nov 2003 22:26:26 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23402 for ; Sun, 9 Nov 2003 22:26:11 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJ2h5-00051f-00 for megaco@ietf.org; Sun, 09 Nov 2003 22:26:23 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AJ2h4-00051V-00 for megaco@ietf.org; Sun, 09 Nov 2003 22:26:22 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAA3Pqo16721 for ; Sun, 9 Nov 2003 22:25:52 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Sun, 9 Nov 2003 22:25:53 -0500 Message-ID: From: "Kevin Boyle" To: å® ä» , megaco@ietf.org Subject: RE: [Megaco] a problem about audit Date: Sun, 9 Nov 2003 22:25:52 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , If you use TCP, there really isn't a limit to the message length, since the transport will segment the message. For UDP, I can suggest using short form tokens and removing all non-mandatory whitespace. This will help keep the message size down. Other than that, at this moment, there's not a lot you can do about the message size. Kevin -----Original Message----- From: å® ä» [mailto:juniperfu@hotmail.com] Sent: Sunday, November 09, 2003 8:01 PM To: megaco@ietf.org Subject: [Megaco] a problem about audit All, When MGC restart or HA, Maybe it need audit the context and termination of MG, and it can send the command Context = * { AuditValue= ROOT {Audit { } } and the MG should return Context = 100 { AuditValue= TermA, TermB } Context = 200 { AuditValue= TermC, TermD } Context = 300 { AuditValue= TermE, TermF } And my problem is if the MG has a lot of context and a megaco message can't include them, So how do the mg return all its context, thanks! juniper _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail _______________________________________________ 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 exim@www1.ietf.org Sun Nov 9 22:27:19 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23457 for ; Sun, 9 Nov 2003 22:27:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ2hj-0000op-7e for megaco-archive@odin.ietf.org; Sun, 09 Nov 2003 22:27:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAA3R3tk003141 for megaco-archive@odin.ietf.org; Sun, 9 Nov 2003 22:27:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ2hj-0000oa-38 for megaco-web-archive@optimus.ietf.org; Sun, 09 Nov 2003 22:27:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23418 for ; Sun, 9 Nov 2003 22:26:48 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJ2hf-00051r-00 for megaco-web-archive@ietf.org; Sun, 09 Nov 2003 22:26:59 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJ2hf-00051o-00 for megaco-web-archive@ietf.org; Sun, 09 Nov 2003 22:26:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ2hg-0000nx-SD; Sun, 09 Nov 2003 22:27:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ2h8-0000nZ-BN for megaco@optimus.ietf.org; Sun, 09 Nov 2003 22:26:26 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23402 for ; Sun, 9 Nov 2003 22:26:11 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJ2h5-00051f-00 for megaco@ietf.org; Sun, 09 Nov 2003 22:26:23 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AJ2h4-00051V-00 for megaco@ietf.org; Sun, 09 Nov 2003 22:26:22 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAA3Pqo16721 for ; Sun, 9 Nov 2003 22:25:52 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Sun, 9 Nov 2003 22:25:53 -0500 Message-ID: From: "Kevin Boyle" To: å® ä» , megaco@ietf.org Subject: RE: [Megaco] a problem about audit Date: Sun, 9 Nov 2003 22:25:52 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , If you use TCP, there really isn't a limit to the message length, since the transport will segment the message. For UDP, I can suggest using short form tokens and removing all non-mandatory whitespace. This will help keep the message size down. Other than that, at this moment, there's not a lot you can do about the message size. Kevin -----Original Message----- From: å® ä» [mailto:juniperfu@hotmail.com] Sent: Sunday, November 09, 2003 8:01 PM To: megaco@ietf.org Subject: [Megaco] a problem about audit All, When MGC restart or HA, Maybe it need audit the context and termination of MG, and it can send the command Context = * { AuditValue= ROOT {Audit { } } and the MG should return Context = 100 { AuditValue= TermA, TermB } Context = 200 { AuditValue= TermC, TermD } Context = 300 { AuditValue= TermE, TermF } And my problem is if the MG has a lot of context and a megaco message can't include them, So how do the mg return all its context, thanks! juniper _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail _______________________________________________ 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-admin@ietf.org Mon Nov 10 10:05:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22135 for ; Mon, 10 Nov 2003 10:05:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJDbB-0000Ki-ND; Mon, 10 Nov 2003 10:05:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJDaQ-0000J2-JW for megaco@optimus.ietf.org; Mon, 10 Nov 2003 10:04:15 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22000 for ; Mon, 10 Nov 2003 10:04:00 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJDaO-0005bT-00 for megaco@ietf.org; Mon, 10 Nov 2003 10:04:12 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AJDaO-0005bP-00 for megaco@ietf.org; Mon, 10 Nov 2003 10:04:12 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAAF3ee24513 for ; Mon, 10 Nov 2003 10:03:40 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 10 Nov 2003 10:03:40 -0500 Message-ID: From: "Kevin Boyle" To: FND-AD Wang JuLin , ? ? , megaco@ietf.org Subject: RE: [Megaco] a problem about audit Date: Mon, 10 Nov 2003 10:03:38 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , The question was how to return all the contexts in existence on the MG. So, my answer still stands -- there's not a lot that can be done to overcome the MTU limitation in UDP. TCP segments its messages based on the MTU size, so there's not a problem there. Kevin -----Original Message----- From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] Sent: Monday, November 10, 2003 12:46 AM To: Boyle, Kevin [NCRTP:3Z40:EXCH]; ? ?; megaco@ietf.org Subject: RE: [Megaco] a problem about audit IMO,It depends on the MTU size. If the message larger than it, gateway can trigger the reply message with error code 533 "RSP EXCEEDS MAX TRANSPORT PDU SIZE" . >>-----Original Message----- >>From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] >>Sent: Monday, November 10, 2003 11:26 AM >>To: å® ä»; megaco@ietf.org >>Subject: RE: [Megaco] a problem about audit >> >> >>If you use TCP, there really isn't a limit to the message length, >>since the transport will segment the message. >> >>For UDP, I can suggest using short form tokens and removing all >>non-mandatory whitespace. This will help keep the message size down. >>Other than that, at this moment, there's not a lot you can do about >>the message size. >> >>Kevin >> >>-----Original Message----- >>From: å® ä» [mailto:juniperfu@hotmail.com] >>Sent: Sunday, November 09, 2003 8:01 PM >>To: megaco@ietf.org >>Subject: [Megaco] a problem about audit >> >>All, >>When MGC restart or HA, Maybe it need audit the context and >>termination of MG, and it can send the command Context = * { >>AuditValue= ROOT {Audit { } } and the MG should return Context = 100 { >>AuditValue= TermA, TermB } Context = 200 { AuditValue= TermC, TermD } >>Context = 300 { AuditValue= TermE, TermF } And my problem is if the MG >>has a lot of context and a >megaco message >>can't include them, So how do the mg return all its context, thanks! >> >>juniper >> >>_________________________________________________________________ >>Add photos to your messages with MSN 8. Get 2 months FREE*. >>http://join.msn.com/?page=features/featuredemail >> >> >>_______________________________________________ >>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 exim@www1.ietf.org Mon Nov 10 10:05:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22160 for ; Mon, 10 Nov 2003 10:05:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJDbF-0000LS-EH for megaco-archive@odin.ietf.org; Mon, 10 Nov 2003 10:05:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAAF55mn001326 for megaco-archive@odin.ietf.org; Mon, 10 Nov 2003 10:05:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJDbF-0000LJ-Ap for megaco-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 10:05:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22081 for ; Mon, 10 Nov 2003 10:04:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJDbC-0005bt-00 for megaco-web-archive@ietf.org; Mon, 10 Nov 2003 10:05:02 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJDbC-0005bq-00 for megaco-web-archive@ietf.org; Mon, 10 Nov 2003 10:05:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJDbB-0000Ki-ND; Mon, 10 Nov 2003 10:05:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJDaQ-0000J2-JW for megaco@optimus.ietf.org; Mon, 10 Nov 2003 10:04:15 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22000 for ; Mon, 10 Nov 2003 10:04:00 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJDaO-0005bT-00 for megaco@ietf.org; Mon, 10 Nov 2003 10:04:12 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AJDaO-0005bP-00 for megaco@ietf.org; Mon, 10 Nov 2003 10:04:12 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAAF3ee24513 for ; Mon, 10 Nov 2003 10:03:40 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 10 Nov 2003 10:03:40 -0500 Message-ID: From: "Kevin Boyle" To: FND-AD Wang JuLin , ? ? , megaco@ietf.org Subject: RE: [Megaco] a problem about audit Date: Mon, 10 Nov 2003 10:03:38 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , The question was how to return all the contexts in existence on the MG. So, my answer still stands -- there's not a lot that can be done to overcome the MTU limitation in UDP. TCP segments its messages based on the MTU size, so there's not a problem there. Kevin -----Original Message----- From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] Sent: Monday, November 10, 2003 12:46 AM To: Boyle, Kevin [NCRTP:3Z40:EXCH]; ? ?; megaco@ietf.org Subject: RE: [Megaco] a problem about audit IMO,It depends on the MTU size. If the message larger than it, gateway can trigger the reply message with error code 533 "RSP EXCEEDS MAX TRANSPORT PDU SIZE" . >>-----Original Message----- >>From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] >>Sent: Monday, November 10, 2003 11:26 AM >>To: å® ä»; megaco@ietf.org >>Subject: RE: [Megaco] a problem about audit >> >> >>If you use TCP, there really isn't a limit to the message length, >>since the transport will segment the message. >> >>For UDP, I can suggest using short form tokens and removing all >>non-mandatory whitespace. This will help keep the message size down. >>Other than that, at this moment, there's not a lot you can do about >>the message size. >> >>Kevin >> >>-----Original Message----- >>From: å® ä» [mailto:juniperfu@hotmail.com] >>Sent: Sunday, November 09, 2003 8:01 PM >>To: megaco@ietf.org >>Subject: [Megaco] a problem about audit >> >>All, >>When MGC restart or HA, Maybe it need audit the context and >>termination of MG, and it can send the command Context = * { >>AuditValue= ROOT {Audit { } } and the MG should return Context = 100 { >>AuditValue= TermA, TermB } Context = 200 { AuditValue= TermC, TermD } >>Context = 300 { AuditValue= TermE, TermF } And my problem is if the MG >>has a lot of context and a >megaco message >>can't include them, So how do the mg return all its context, thanks! >> >>juniper >> >>_________________________________________________________________ >>Add photos to your messages with MSN 8. Get 2 months FREE*. >>http://join.msn.com/?page=features/featuredemail >> >> >>_______________________________________________ >>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-admin@ietf.org Mon Nov 10 10:16:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23688 for ; Mon, 10 Nov 2003 10:16:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJDlq-00011c-C9; Mon, 10 Nov 2003 10:16:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJDl2-00010i-5p for megaco@optimus.ietf.org; Mon, 10 Nov 2003 10:15:12 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23490 for ; Mon, 10 Nov 2003 10:14:58 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJDkz-0005oQ-00 for megaco@ietf.org; Mon, 10 Nov 2003 10:15:09 -0500 Received: from mail.tdsoft.com ([212.143.64.34] helo=tdsoft.com) by ietf-mx with smtp (Exim 4.12) id 1AJDky-0005oI-00 for megaco@ietf.org; Mon, 10 Nov 2003 10:15:09 -0500 Received: from exchange.td-soft.co.il ([IP=172.16.0.250]) by eSafe SMTP Relay 1068383901; Mon Nov 10 17:12:23 2003 Received: by exchange.td-soft.co.il with Internet Mail Service (5.5.2653.19) id ; Mon, 10 Nov 2003 17:11:09 +0200 Message-ID: From: Raphael Tryster To: "'MGCP Discussion List'" , megaco@ietf.org Date: Mon, 10 Nov 2003 17:11:04 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3A79C.DC107A30" Subject: [Megaco] Ambiguous digit map match in Megaco and MGCP Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , 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_01C3A79C.DC107A30 Content-Type: text/plain If I interpret the standards correctly, Megaco and MGCP seem to require different behaviour on an ambiguous digit map match. For example (using MGCP syntax: D: (0|[1-9]xxx|9|[*,#]xx[*,#]|*#xx[*,#]|[2-4]x#|[2-9]#|[2-4]xT|[2-9]T) Suppose the subscriber dials 9. In Megaco, the MG waits for a few seconds to see if the 9 will be followed by 3 digits or # or timeout. In MGCP, the MG is expected to NTFY the digit 9 immediately, and the alternatives of 9xxx, 9# and 9T are meaningless. Am I correct about this difference between the protocols, and if so, why does MGCP allow impossible alternatives? Raphael Tryster ------_=_NextPart_001_01C3A79C.DC107A30 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Ambiguous digit map match in Megaco and MGCP

If I interpret the standards correctly, = Megaco and MGCP seem to require different behaviour on an ambiguous digit= map match.  For example (using MGCP syntax:

D: (0|[1-9]xxx|9|[*,#]xx[*,#]|*#xx[*,#]|= [2-4]x#|[2-9]#|[2-4]xT|[2-9]T)=A0

Suppose the subscriber dials 9.  In= Megaco, the MG waits for a few seconds to see if the 9 will be followed = by 3 digits or # or timeout.  In MGCP, the MG is expected to NTFY th= e digit 9 immediately, and the alternatives of 9xxx, 9# and 9T are meanin= gless.

Am I correct about this difference betwe= en the protocols, and if so, why does MGCP allow impossible alternatives?=

Raphael Tryster

------_=_NextPart_001_01C3A79C.DC107A30-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Mon Nov 10 10:16:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23708 for ; Mon, 10 Nov 2003 10:16:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJDlt-00013x-Ph for megaco-archive@odin.ietf.org; Mon, 10 Nov 2003 10:16:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAAFG5YM004079 for megaco-archive@odin.ietf.org; Mon, 10 Nov 2003 10:16:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJDlt-00013i-L2 for megaco-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 10:16:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23600 for ; Mon, 10 Nov 2003 10:15:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJDlr-0005rx-00 for megaco-web-archive@ietf.org; Mon, 10 Nov 2003 10:16:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJDlr-0005ru-00 for megaco-web-archive@ietf.org; Mon, 10 Nov 2003 10:16:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJDlq-00011c-C9; Mon, 10 Nov 2003 10:16:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJDl2-00010i-5p for megaco@optimus.ietf.org; Mon, 10 Nov 2003 10:15:12 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23490 for ; Mon, 10 Nov 2003 10:14:58 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJDkz-0005oQ-00 for megaco@ietf.org; Mon, 10 Nov 2003 10:15:09 -0500 Received: from mail.tdsoft.com ([212.143.64.34] helo=tdsoft.com) by ietf-mx with smtp (Exim 4.12) id 1AJDky-0005oI-00 for megaco@ietf.org; Mon, 10 Nov 2003 10:15:09 -0500 Received: from exchange.td-soft.co.il ([IP=172.16.0.250]) by eSafe SMTP Relay 1068383901; Mon Nov 10 17:12:23 2003 Received: by exchange.td-soft.co.il with Internet Mail Service (5.5.2653.19) id ; Mon, 10 Nov 2003 17:11:09 +0200 Message-ID: From: Raphael Tryster To: "'MGCP Discussion List'" , megaco@ietf.org Date: Mon, 10 Nov 2003 17:11:04 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3A79C.DC107A30" Subject: [Megaco] Ambiguous digit map match in Megaco and MGCP Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , 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_01C3A79C.DC107A30 Content-Type: text/plain If I interpret the standards correctly, Megaco and MGCP seem to require different behaviour on an ambiguous digit map match. For example (using MGCP syntax: D: (0|[1-9]xxx|9|[*,#]xx[*,#]|*#xx[*,#]|[2-4]x#|[2-9]#|[2-4]xT|[2-9]T) Suppose the subscriber dials 9. In Megaco, the MG waits for a few seconds to see if the 9 will be followed by 3 digits or # or timeout. In MGCP, the MG is expected to NTFY the digit 9 immediately, and the alternatives of 9xxx, 9# and 9T are meaningless. Am I correct about this difference between the protocols, and if so, why does MGCP allow impossible alternatives? Raphael Tryster ------_=_NextPart_001_01C3A79C.DC107A30 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Ambiguous digit map match in Megaco and MGCP

If I interpret the standards correctly, = Megaco and MGCP seem to require different behaviour on an ambiguous digit= map match.  For example (using MGCP syntax:

D: (0|[1-9]xxx|9|[*,#]xx[*,#]|*#xx[*,#]|= [2-4]x#|[2-9]#|[2-4]xT|[2-9]T)=A0

Suppose the subscriber dials 9.  In= Megaco, the MG waits for a few seconds to see if the 9 will be followed = by 3 digits or # or timeout.  In MGCP, the MG is expected to NTFY th= e digit 9 immediately, and the alternatives of 9xxx, 9# and 9T are meanin= gless.

Am I correct about this difference betwe= en the protocols, and if so, why does MGCP allow impossible alternatives?=

Raphael Tryster

------_=_NextPart_001_01C3A79C.DC107A30-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Mon Nov 10 10:37:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25041 for ; Mon, 10 Nov 2003 10:37:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJE6A-0002co-4d; Mon, 10 Nov 2003 10:37:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJE63-0002cA-QV for megaco@optimus.ietf.org; Mon, 10 Nov 2003 10:36:55 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25004 for ; Mon, 10 Nov 2003 10:36:41 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJE61-0006BT-00 for megaco@ietf.org; Mon, 10 Nov 2003 10:36:53 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AJE60-0006Aq-00 for megaco@ietf.org; Mon, 10 Nov 2003 10:36:52 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAAFaKe28909 for ; Mon, 10 Nov 2003 10:36:20 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 10 Nov 2003 10:36:20 -0500 Message-ID: From: "Kevin Boyle" To: Raphael Tryster , megaco@ietf.org Subject: RE: [Megaco] Ambiguous digit map match in Megaco and MGCP Date: Mon, 10 Nov 2003 10:36:20 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , When writing digitmaps, some attention must be paid to whether the digitmap will be operating on a shortest possible match, or longest possible match. This will certainly have impact upon how the digitmap should look. I, personally, have problems with the longest possible match idea, because it leads to unnecessary delay for shorter digit patterns, and requires more complexity in the digitmap. H.248.16 outlines digit collection packages that allow shortest possible match behavior, as well as some other key functionality for digit collection. Kevin _____ From: Raphael Tryster [mailto:raphael@tdsoft.com] Sent: Monday, November 10, 2003 10:11 AM To: 'MGCP Discussion List'; megaco@ietf.org Subject: [Megaco] Ambiguous digit map match in Megaco and MGCP If I interpret the standards correctly, Megaco and MGCP seem to require different behaviour on an ambiguous digit map match. For example (using MGCP syntax: D: (0|[1-9]xxx|9|[*,#]xx[*,#]|*#xx[*,#]|[2-4]x#|[2-9]#|[2-4]xT|[2-9]T) Suppose the subscriber dials 9. In Megaco, the MG waits for a few seconds to see if the 9 will be followed by 3 digits or # or timeout. In MGCP, the MG is expected to NTFY the digit 9 immediately, and the alternatives of 9xxx, 9# and 9T are meaningless. Am I correct about this difference between the protocols, and if so, why does MGCP allow impossible alternatives? Raphael Tryster _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Mon Nov 10 10:37:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25045 for ; Mon, 10 Nov 2003 10:37:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJE6C-0002eF-FK for megaco-archive@odin.ietf.org; Mon, 10 Nov 2003 10:37:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAAFb4bB010175 for megaco-archive@odin.ietf.org; Mon, 10 Nov 2003 10:37:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJE6C-0002dw-6W for megaco-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 10:37:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25018 for ; Mon, 10 Nov 2003 10:36:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJE69-0006Bq-00 for megaco-web-archive@ietf.org; Mon, 10 Nov 2003 10:37:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJE69-0006Bn-00 for megaco-web-archive@ietf.org; Mon, 10 Nov 2003 10:37:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJE6A-0002co-4d; Mon, 10 Nov 2003 10:37:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJE63-0002cA-QV for megaco@optimus.ietf.org; Mon, 10 Nov 2003 10:36:55 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25004 for ; Mon, 10 Nov 2003 10:36:41 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJE61-0006BT-00 for megaco@ietf.org; Mon, 10 Nov 2003 10:36:53 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AJE60-0006Aq-00 for megaco@ietf.org; Mon, 10 Nov 2003 10:36:52 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAAFaKe28909 for ; Mon, 10 Nov 2003 10:36:20 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 10 Nov 2003 10:36:20 -0500 Message-ID: From: "Kevin Boyle" To: Raphael Tryster , megaco@ietf.org Subject: RE: [Megaco] Ambiguous digit map match in Megaco and MGCP Date: Mon, 10 Nov 2003 10:36:20 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , When writing digitmaps, some attention must be paid to whether the digitmap will be operating on a shortest possible match, or longest possible match. This will certainly have impact upon how the digitmap should look. I, personally, have problems with the longest possible match idea, because it leads to unnecessary delay for shorter digit patterns, and requires more complexity in the digitmap. H.248.16 outlines digit collection packages that allow shortest possible match behavior, as well as some other key functionality for digit collection. Kevin _____ From: Raphael Tryster [mailto:raphael@tdsoft.com] Sent: Monday, November 10, 2003 10:11 AM To: 'MGCP Discussion List'; megaco@ietf.org Subject: [Megaco] Ambiguous digit map match in Megaco and MGCP If I interpret the standards correctly, Megaco and MGCP seem to require different behaviour on an ambiguous digit map match. For example (using MGCP syntax: D: (0|[1-9]xxx|9|[*,#]xx[*,#]|*#xx[*,#]|[2-4]x#|[2-9]#|[2-4]xT|[2-9]T) Suppose the subscriber dials 9. In Megaco, the MG waits for a few seconds to see if the 9 will be followed by 3 digits or # or timeout. In MGCP, the MG is expected to NTFY the digit 9 immediately, and the alternatives of 9xxx, 9# and 9T are meaningless. Am I correct about this difference between the protocols, and if so, why does MGCP allow impossible alternatives? Raphael Tryster _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Mon Nov 10 11:50:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29478 for ; Mon, 10 Nov 2003 11:50:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJFEn-0000Fz-Aa; Mon, 10 Nov 2003 11:50:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ4r8-0007nx-Od for megaco@optimus.ietf.org; Mon, 10 Nov 2003 00:44:54 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26575 for ; Mon, 10 Nov 2003 00:44:40 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJ4r5-00070y-00 for megaco@ietf.org; Mon, 10 Nov 2003 00:44:52 -0500 Received: from [210.22.146.172] (helo=asbmx.sbell.com.cn) by ietf-mx with esmtp (Exim 4.12) id 1AJ4qu-00070K-00 for megaco@ietf.org; Mon, 10 Nov 2003 00:44:51 -0500 Received: from asbwebshld.sbell.com.cn (asbwebshld [172.24.208.38]) by asbmx.sbell.com.cn (8.12.2+Sun/8.12.3) with SMTP id hAA5dwZm010940 for ; Mon, 10 Nov 2003 13:40:04 +0800 (CST) Received: FROM bellnet-mail4.sbell.com.cn BY asbwebshld.sbell.com.cn ; Mon Nov 10 13:46:27 2003 +0800 Received: from bellnet-mail1.sbell.com.cn ([172.24.208.21]) by bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.6713); Mon, 10 Nov 2003 13:46:27 +0800 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Subject: RE: [Megaco] a problem about audit Date: Mon, 10 Nov 2003 13:46:26 +0800 Message-ID: Thread-Topic: [Megaco] a problem about audit Thread-Index: AcOnOqpTsZW+eHUIQhm5qAdA13CEhQADflygAAFK5NA= From: "FND-AD Wang JuLin" To: "Kevin Boyle" , =?utf-8?B?54C5IOa1oA==?= , X-OriginalArrivalTime: 10 Nov 2003 05:46:27.0036 (UTC) FILETIME=[FB80F9C0:01C3A74D] Content-Transfer-Encoding: base64 Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 SU1PLEl0IGRlcGVuZHMgb24gdGhlIE1UVSBzaXplLiBJZiB0aGUgbWVzc2FnZSBsYXJnZXIgdGhh biBpdCwgZ2F0ZXdheSBjYW4gdHJpZ2dlciB0aGUgcmVwbHkgbWVzc2FnZSB3aXRoIGVycm9yIGNv ZGUgNTMzICJSU1AgDQpFWENFRURTIE1BWCBUUkFOU1BPUlQgUERVIFNJWkUiIC4NCg0KPj4tLS0t LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj5Gcm9tOiBLZXZpbiBCb3lsZSBbbWFpbHRvOmtib3ls ZUBub3J0ZWxuZXR3b3Jrcy5jb21dDQo+PlNlbnQ6IE1vbmRheSwgTm92ZW1iZXIgMTAsIDIwMDMg MTE6MjYgQU0NCj4+VG86IOeAuSDmtaA7IG1lZ2Fjb0BpZXRmLm9yZw0KPj5TdWJqZWN0OiBSRTog W01lZ2Fjb10gYSBwcm9ibGVtIGFib3V0IGF1ZGl0DQo+Pg0KPj4NCj4+SWYgeW91IHVzZSBUQ1As IHRoZXJlIHJlYWxseSBpc24ndCBhIGxpbWl0IHRvIHRoZSBtZXNzYWdlIA0KPj5sZW5ndGgsIHNp bmNlIHRoZQ0KPj50cmFuc3BvcnQgd2lsbCBzZWdtZW50IHRoZSBtZXNzYWdlLg0KPj4NCj4+Rm9y IFVEUCwgSSBjYW4gc3VnZ2VzdCB1c2luZyBzaG9ydCBmb3JtIHRva2VucyBhbmQgcmVtb3Zpbmcg YWxsDQo+Pm5vbi1tYW5kYXRvcnkgd2hpdGVzcGFjZS4gIFRoaXMgd2lsbCBoZWxwIGtlZXAgdGhl IG1lc3NhZ2UgDQo+PnNpemUgZG93bi4gIE90aGVyDQo+PnRoYW4gdGhhdCwgYXQgdGhpcyBtb21l bnQsIHRoZXJlJ3Mgbm90IGEgbG90IHlvdSBjYW4gZG8gYWJvdXQgDQo+PnRoZSBtZXNzYWdlDQo+ PnNpemUuDQo+Pg0KPj5LZXZpbg0KPj4NCj4+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+ RnJvbTog54C5IOa1oCBbbWFpbHRvOmp1bmlwZXJmdUBob3RtYWlsLmNvbV0gDQo+PlNlbnQ6IFN1 bmRheSwgTm92ZW1iZXIgMDksIDIwMDMgODowMSBQTQ0KPj5UbzogbWVnYWNvQGlldGYub3JnDQo+ PlN1YmplY3Q6IFtNZWdhY29dIGEgcHJvYmxlbSBhYm91dCBhdWRpdA0KPj4NCj4+QWxsLA0KPj5X aGVuIE1HQyByZXN0YXJ0IG9yIEhBLCBNYXliZSBpdCBuZWVkIGF1ZGl0IHRoZSBjb250ZXh0IGFu ZCANCj4+dGVybWluYXRpb24gb2YNCj4+TUcsIGFuZCBpdCBjYW4gc2VuZCB0aGUgY29tbWFuZCBD b250ZXh0ID0gKiB7IEF1ZGl0VmFsdWU9IFJPT1QgDQo+PntBdWRpdCB7IH0gfQ0KPj5hbmQgdGhl IE1HIHNob3VsZCByZXR1cm4gQ29udGV4dCA9IDEwMCB7IEF1ZGl0VmFsdWU9IFRlcm1BLCANCj4+ VGVybUIgfSBDb250ZXh0DQo+Pj0gMjAwIHsgQXVkaXRWYWx1ZT0gVGVybUMsIFRlcm1EIH0gQ29u dGV4dCA9IDMwMCB7IEF1ZGl0VmFsdWU9IA0KPj5UZXJtRSwgVGVybUYNCj4+fSBBbmQgbXkgcHJv YmxlbSBpcyBpZiB0aGUgTUcgaGFzIGEgbG90IG9mIGNvbnRleHQgYW5kIGEgDQo+bWVnYWNvIG1l c3NhZ2UNCj4+Y2FuJ3QgaW5jbHVkZSB0aGVtLCBTbyBob3cgZG8gdGhlIG1nIHJldHVybiBhbGwg aXRzIGNvbnRleHQsIHRoYW5rcyENCj4+DQo+Pmp1bmlwZXINCj4+DQo+Pl9fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PkFk ZCBwaG90b3MgdG8geW91ciBtZXNzYWdlcyB3aXRoIE1TTiA4LiBHZXQgMiBtb250aHMgRlJFRSou IA0KPj5odHRwOi8vam9pbi5tc24uY29tLz9wYWdlPWZlYXR1cmVzL2ZlYXR1cmVkZW1haWwNCj4+ DQo+Pg0KPj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K Pj5NZWdhY28gbWFpbGluZyBsaXN0DQo+Pk1lZ2Fjb0BpZXRmLm9yZw0KPj5odHRwczovL3d3dzEu aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tZWdhY28NCj4+DQo+Pl9fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+Pk1lZ2FjbyBtYWlsaW5nIGxpc3QNCj4+ TWVnYWNvQGlldGYub3JnDQo+Pmh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv L21lZ2Fjbw0KPj4NCj4NCg== _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Mon Nov 10 11:50:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29498 for ; Mon, 10 Nov 2003 11:50:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJFEs-0000JJ-5v for megaco-archive@odin.ietf.org; Mon, 10 Nov 2003 11:50:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAAGo68p001187 for megaco-archive@odin.ietf.org; Mon, 10 Nov 2003 11:50:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJFEs-0000J4-2B for megaco-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 11:50:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29442 for ; Mon, 10 Nov 2003 11:49:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJFEo-00000b-00 for megaco-web-archive@ietf.org; Mon, 10 Nov 2003 11:50:02 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJFEo-00000Y-00 for megaco-web-archive@ietf.org; Mon, 10 Nov 2003 11:50:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJFEn-0000Fz-Aa; Mon, 10 Nov 2003 11:50:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJ4r8-0007nx-Od for megaco@optimus.ietf.org; Mon, 10 Nov 2003 00:44:54 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26575 for ; Mon, 10 Nov 2003 00:44:40 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJ4r5-00070y-00 for megaco@ietf.org; Mon, 10 Nov 2003 00:44:52 -0500 Received: from [210.22.146.172] (helo=asbmx.sbell.com.cn) by ietf-mx with esmtp (Exim 4.12) id 1AJ4qu-00070K-00 for megaco@ietf.org; Mon, 10 Nov 2003 00:44:51 -0500 Received: from asbwebshld.sbell.com.cn (asbwebshld [172.24.208.38]) by asbmx.sbell.com.cn (8.12.2+Sun/8.12.3) with SMTP id hAA5dwZm010940 for ; Mon, 10 Nov 2003 13:40:04 +0800 (CST) Received: FROM bellnet-mail4.sbell.com.cn BY asbwebshld.sbell.com.cn ; Mon Nov 10 13:46:27 2003 +0800 Received: from bellnet-mail1.sbell.com.cn ([172.24.208.21]) by bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.6713); Mon, 10 Nov 2003 13:46:27 +0800 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Subject: RE: [Megaco] a problem about audit Date: Mon, 10 Nov 2003 13:46:26 +0800 Message-ID: Thread-Topic: [Megaco] a problem about audit Thread-Index: AcOnOqpTsZW+eHUIQhm5qAdA13CEhQADflygAAFK5NA= From: "FND-AD Wang JuLin" To: "Kevin Boyle" , =?utf-8?B?54C5IOa1oA==?= , X-OriginalArrivalTime: 10 Nov 2003 05:46:27.0036 (UTC) FILETIME=[FB80F9C0:01C3A74D] Content-Transfer-Encoding: base64 Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Transfer-Encoding: base64 SU1PLEl0IGRlcGVuZHMgb24gdGhlIE1UVSBzaXplLiBJZiB0aGUgbWVzc2FnZSBsYXJnZXIgdGhh biBpdCwgZ2F0ZXdheSBjYW4gdHJpZ2dlciB0aGUgcmVwbHkgbWVzc2FnZSB3aXRoIGVycm9yIGNv ZGUgNTMzICJSU1AgDQpFWENFRURTIE1BWCBUUkFOU1BPUlQgUERVIFNJWkUiIC4NCg0KPj4tLS0t LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj5Gcm9tOiBLZXZpbiBCb3lsZSBbbWFpbHRvOmtib3ls ZUBub3J0ZWxuZXR3b3Jrcy5jb21dDQo+PlNlbnQ6IE1vbmRheSwgTm92ZW1iZXIgMTAsIDIwMDMg MTE6MjYgQU0NCj4+VG86IOeAuSDmtaA7IG1lZ2Fjb0BpZXRmLm9yZw0KPj5TdWJqZWN0OiBSRTog W01lZ2Fjb10gYSBwcm9ibGVtIGFib3V0IGF1ZGl0DQo+Pg0KPj4NCj4+SWYgeW91IHVzZSBUQ1As IHRoZXJlIHJlYWxseSBpc24ndCBhIGxpbWl0IHRvIHRoZSBtZXNzYWdlIA0KPj5sZW5ndGgsIHNp bmNlIHRoZQ0KPj50cmFuc3BvcnQgd2lsbCBzZWdtZW50IHRoZSBtZXNzYWdlLg0KPj4NCj4+Rm9y IFVEUCwgSSBjYW4gc3VnZ2VzdCB1c2luZyBzaG9ydCBmb3JtIHRva2VucyBhbmQgcmVtb3Zpbmcg YWxsDQo+Pm5vbi1tYW5kYXRvcnkgd2hpdGVzcGFjZS4gIFRoaXMgd2lsbCBoZWxwIGtlZXAgdGhl IG1lc3NhZ2UgDQo+PnNpemUgZG93bi4gIE90aGVyDQo+PnRoYW4gdGhhdCwgYXQgdGhpcyBtb21l bnQsIHRoZXJlJ3Mgbm90IGEgbG90IHlvdSBjYW4gZG8gYWJvdXQgDQo+PnRoZSBtZXNzYWdlDQo+ PnNpemUuDQo+Pg0KPj5LZXZpbg0KPj4NCj4+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+ RnJvbTog54C5IOa1oCBbbWFpbHRvOmp1bmlwZXJmdUBob3RtYWlsLmNvbV0gDQo+PlNlbnQ6IFN1 bmRheSwgTm92ZW1iZXIgMDksIDIwMDMgODowMSBQTQ0KPj5UbzogbWVnYWNvQGlldGYub3JnDQo+ PlN1YmplY3Q6IFtNZWdhY29dIGEgcHJvYmxlbSBhYm91dCBhdWRpdA0KPj4NCj4+QWxsLA0KPj5X aGVuIE1HQyByZXN0YXJ0IG9yIEhBLCBNYXliZSBpdCBuZWVkIGF1ZGl0IHRoZSBjb250ZXh0IGFu ZCANCj4+dGVybWluYXRpb24gb2YNCj4+TUcsIGFuZCBpdCBjYW4gc2VuZCB0aGUgY29tbWFuZCBD b250ZXh0ID0gKiB7IEF1ZGl0VmFsdWU9IFJPT1QgDQo+PntBdWRpdCB7IH0gfQ0KPj5hbmQgdGhl IE1HIHNob3VsZCByZXR1cm4gQ29udGV4dCA9IDEwMCB7IEF1ZGl0VmFsdWU9IFRlcm1BLCANCj4+ VGVybUIgfSBDb250ZXh0DQo+Pj0gMjAwIHsgQXVkaXRWYWx1ZT0gVGVybUMsIFRlcm1EIH0gQ29u dGV4dCA9IDMwMCB7IEF1ZGl0VmFsdWU9IA0KPj5UZXJtRSwgVGVybUYNCj4+fSBBbmQgbXkgcHJv YmxlbSBpcyBpZiB0aGUgTUcgaGFzIGEgbG90IG9mIGNvbnRleHQgYW5kIGEgDQo+bWVnYWNvIG1l c3NhZ2UNCj4+Y2FuJ3QgaW5jbHVkZSB0aGVtLCBTbyBob3cgZG8gdGhlIG1nIHJldHVybiBhbGwg aXRzIGNvbnRleHQsIHRoYW5rcyENCj4+DQo+Pmp1bmlwZXINCj4+DQo+Pl9fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PkFk ZCBwaG90b3MgdG8geW91ciBtZXNzYWdlcyB3aXRoIE1TTiA4LiBHZXQgMiBtb250aHMgRlJFRSou IA0KPj5odHRwOi8vam9pbi5tc24uY29tLz9wYWdlPWZlYXR1cmVzL2ZlYXR1cmVkZW1haWwNCj4+ DQo+Pg0KPj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K Pj5NZWdhY28gbWFpbGluZyBsaXN0DQo+Pk1lZ2Fjb0BpZXRmLm9yZw0KPj5odHRwczovL3d3dzEu aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tZWdhY28NCj4+DQo+Pl9fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+Pk1lZ2FjbyBtYWlsaW5nIGxpc3QNCj4+ TWVnYWNvQGlldGYub3JnDQo+Pmh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv L21lZ2Fjbw0KPj4NCj4NCg== _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Mon Nov 10 20:22:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27374 for ; Mon, 10 Nov 2003 20:22:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJNEH-0003K3-2e; Mon, 10 Nov 2003 20:22:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJNDU-0003JX-N8 for megaco@optimus.ietf.org; Mon, 10 Nov 2003 20:21:13 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27227 for ; Mon, 10 Nov 2003 20:20:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJNDS-0001cP-00 for megaco@ietf.org; Mon, 10 Nov 2003 20:21:10 -0500 Received: from law15-f109.law15.hotmail.com ([64.4.23.109] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 1AJNDR-0001bS-00 for megaco@ietf.org; Mon, 10 Nov 2003 20:21:09 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 10 Nov 2003 17:20:39 -0800 Received: from 210.21.224.54 by lw15fd.law15.hotmail.msn.com with HTTP; Tue, 11 Nov 2003 01:20:39 GMT X-Originating-IP: [210.21.224.54] X-Originating-Email: [juniperfu@hotmail.com] From: "å® ä»" To: kboyle@nortelnetworks.com, JuLin.Wang@alcatel-sbell.com.cn, megaco@ietf.org Subject: RE: [Megaco] a problem about audit Date: Tue, 11 Nov 2003 09:20:39 +0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 11 Nov 2003 01:20:39.0231 (UTC) FILETIME=[0448CCF0:01C3A7F2] Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id UAA27228 Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable So, If MGC can't audit all the context of the MG When MGC switchover, How= =20 can MGC keep the coherence in the context and termination with MG? >From: "Kevin Boyle" >To: FND-AD Wang JuLin , ? ?=20 >, megaco@ietf.org >Subject: RE: [Megaco] a problem about audit >Date: Mon, 10 Nov 2003 10:03:38 -0500 > >The question was how to return all the contexts in existence on the MG. = =20 >So, >my answer still stands -- there's not a lot that can be done to overcome= =20 >the >MTU limitation in UDP. TCP segments its messages based on the MTU size,= so >there's not a problem there. > >Kevin > >-----Original Message----- >From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] >Sent: Monday, November 10, 2003 12:46 AM >To: Boyle, Kevin [NCRTP:3Z40:EXCH]; ? ?; megaco@ietf.org >Subject: RE: [Megaco] a problem about audit > >IMO,It depends on the MTU size. If the message larger than it, gateway c= an >trigger the reply message with error code 533 "RSP EXCEEDS MAX TRANSPORT= =20 >PDU >SIZE" . > > >>-----Original Message----- > >>From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] > >>Sent: Monday, November 10, 2003 11:26 AM > >>To: =E5=AE =E4=BB; megaco@ietf.org > >>Subject: RE: [Megaco] a problem about audit > >> > >> > >>If you use TCP, there really isn't a limit to the message length, > >>since the transport will segment the message. > >> > >>For UDP, I can suggest using short form tokens and removing all > >>non-mandatory whitespace. This will help keep the message size down. > >>Other than that, at this moment, there's not a lot you can do about > >>the message size. > >> > >>Kevin > >> > >>-----Original Message----- > >>From: =E5=AE =E4=BB [mailto:juniperfu@hotmail.com] > >>Sent: Sunday, November 09, 2003 8:01 PM > >>To: megaco@ietf.org > >>Subject: [Megaco] a problem about audit > >> > >>All, > >>When MGC restart or HA, Maybe it need audit the context and > >>termination of MG, and it can send the command Context =3D * { > >>AuditValue=3D ROOT {Audit { } } and the MG should return Context =3D = 100 { > >>AuditValue=3D TermA, TermB } Context =3D 200 { AuditValue=3D TermC, T= ermD } > >>Context =3D 300 { AuditValue=3D TermE, TermF } And my problem is if t= he MG > >>has a lot of context and a > >megaco message > >>can't include them, So how do the mg return all its context, thanks! > >> > >>juniper > >> > >>_________________________________________________________________ > >>Add photos to your messages with MSN 8. Get 2 months FREE*. > >>http://join.msn.com/?page=3Dfeatures/featuredemail > >> > >> > >>_______________________________________________ > >>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 _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*.=20 http://join.msn.com/?page=3Dfeatures/featuredemail _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Mon Nov 10 20:22:40 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27421 for ; Mon, 10 Nov 2003 20:22:40 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJNEc-0003LT-7h for megaco-archive@odin.ietf.org; Mon, 10 Nov 2003 20:22:23 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAB1MMwL012855 for megaco-archive@odin.ietf.org; Mon, 10 Nov 2003 20:22:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJNEc-0003LG-4U for megaco-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 20:22:22 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27328 for ; Mon, 10 Nov 2003 20:22:08 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJNEZ-0001ey-00 for megaco-web-archive@ietf.org; Mon, 10 Nov 2003 20:22:19 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJNEL-0001eg-00 for megaco-web-archive@ietf.org; Mon, 10 Nov 2003 20:22:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJNEH-0003K3-2e; Mon, 10 Nov 2003 20:22:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJNDU-0003JX-N8 for megaco@optimus.ietf.org; Mon, 10 Nov 2003 20:21:13 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27227 for ; Mon, 10 Nov 2003 20:20:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJNDS-0001cP-00 for megaco@ietf.org; Mon, 10 Nov 2003 20:21:10 -0500 Received: from law15-f109.law15.hotmail.com ([64.4.23.109] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 1AJNDR-0001bS-00 for megaco@ietf.org; Mon, 10 Nov 2003 20:21:09 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 10 Nov 2003 17:20:39 -0800 Received: from 210.21.224.54 by lw15fd.law15.hotmail.msn.com with HTTP; Tue, 11 Nov 2003 01:20:39 GMT X-Originating-IP: [210.21.224.54] X-Originating-Email: [juniperfu@hotmail.com] From: "å® ä»" To: kboyle@nortelnetworks.com, JuLin.Wang@alcatel-sbell.com.cn, megaco@ietf.org Subject: RE: [Megaco] a problem about audit Date: Tue, 11 Nov 2003 09:20:39 +0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 11 Nov 2003 01:20:39.0231 (UTC) FILETIME=[0448CCF0:01C3A7F2] X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id UAA27228 Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable So, If MGC can't audit all the context of the MG When MGC switchover, How= =20 can MGC keep the coherence in the context and termination with MG? >From: "Kevin Boyle" >To: FND-AD Wang JuLin , ? ?=20 >, megaco@ietf.org >Subject: RE: [Megaco] a problem about audit >Date: Mon, 10 Nov 2003 10:03:38 -0500 > >The question was how to return all the contexts in existence on the MG. = =20 >So, >my answer still stands -- there's not a lot that can be done to overcome= =20 >the >MTU limitation in UDP. TCP segments its messages based on the MTU size,= so >there's not a problem there. > >Kevin > >-----Original Message----- >From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] >Sent: Monday, November 10, 2003 12:46 AM >To: Boyle, Kevin [NCRTP:3Z40:EXCH]; ? ?; megaco@ietf.org >Subject: RE: [Megaco] a problem about audit > >IMO,It depends on the MTU size. If the message larger than it, gateway c= an >trigger the reply message with error code 533 "RSP EXCEEDS MAX TRANSPORT= =20 >PDU >SIZE" . > > >>-----Original Message----- > >>From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] > >>Sent: Monday, November 10, 2003 11:26 AM > >>To: =E5=AE =E4=BB; megaco@ietf.org > >>Subject: RE: [Megaco] a problem about audit > >> > >> > >>If you use TCP, there really isn't a limit to the message length, > >>since the transport will segment the message. > >> > >>For UDP, I can suggest using short form tokens and removing all > >>non-mandatory whitespace. This will help keep the message size down. > >>Other than that, at this moment, there's not a lot you can do about > >>the message size. > >> > >>Kevin > >> > >>-----Original Message----- > >>From: =E5=AE =E4=BB [mailto:juniperfu@hotmail.com] > >>Sent: Sunday, November 09, 2003 8:01 PM > >>To: megaco@ietf.org > >>Subject: [Megaco] a problem about audit > >> > >>All, > >>When MGC restart or HA, Maybe it need audit the context and > >>termination of MG, and it can send the command Context =3D * { > >>AuditValue=3D ROOT {Audit { } } and the MG should return Context =3D = 100 { > >>AuditValue=3D TermA, TermB } Context =3D 200 { AuditValue=3D TermC, T= ermD } > >>Context =3D 300 { AuditValue=3D TermE, TermF } And my problem is if t= he MG > >>has a lot of context and a > >megaco message > >>can't include them, So how do the mg return all its context, thanks! > >> > >>juniper > >> > >>_________________________________________________________________ > >>Add photos to your messages with MSN 8. Get 2 months FREE*. > >>http://join.msn.com/?page=3Dfeatures/featuredemail > >> > >> > >>_______________________________________________ > >>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 _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*.=20 http://join.msn.com/?page=3Dfeatures/featuredemail _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Mon Nov 10 20:49:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28863 for ; Mon, 10 Nov 2003 20:49:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJNeP-0004l0-Nf; Mon, 10 Nov 2003 20:49:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJNeO-0004kn-4b for megaco@optimus.ietf.org; Mon, 10 Nov 2003 20:49:00 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28842 for ; Mon, 10 Nov 2003 20:48:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJNeL-0002Dp-00 for megaco@ietf.org; Mon, 10 Nov 2003 20:48:57 -0500 Received: from ish7.ericsson.com.au ([61.88.9.195]) by ietf-mx with esmtp (Exim 4.12) id 1AJNeK-0002Bc-00 for megaco@ietf.org; Mon, 10 Nov 2003 20:48:56 -0500 Received: from eaubrnt019.epa.ericsson.se ([146.11.31.193]) by ish7.ericsson.com.au (8.11.7+Sun/8.11.7) with ESMTP id hAB1ixp23607; Tue, 11 Nov 2003 12:44:59 +1100 (EST) Received: from ericsson.com.au (E0050DA878EDF [146.11.245.176]) by eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id WPNBN5D7; Tue, 11 Nov 2003 12:47:37 +1100 Message-ID: <3FB03E70.4070705@ericsson.com.au> Date: Tue, 11 Nov 2003 12:42:08 +1100 From: Christian Groves User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Troy Cauble CC: MEGACO list Subject: Re: [Megaco] discovering physical terminations References: <3FABE618.1020005@bell-labs.com> In-Reply-To: <3FABE618.1020005@bell-labs.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit G'Day Troy, There's no simple command that returns a list of all physical terminations. These terminations could be in the NULL context or being used in other contexts. I would think that most implementations would use a certain TID structure. So you could do an audit Context=ALL, TID=TDM/* and you should get back the individual contextID and TID. Regards, Christian Troy Cauble wrote: > > Can someone suggest a minimal, wildcarded request from the MGC > that would cause an MG to return the list of all physical > terminations? > > -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 exim@www1.ietf.org Mon Nov 10 20:49:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28878 for ; Mon, 10 Nov 2003 20:49:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJNeS-0004lp-5D for megaco-archive@odin.ietf.org; Mon, 10 Nov 2003 20:49:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAB1n4Zs018331 for megaco-archive@odin.ietf.org; Mon, 10 Nov 2003 20:49:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJNeR-0004la-VS for megaco-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 20:49:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28847 for ; Mon, 10 Nov 2003 20:48:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJNeP-0002Dy-00 for megaco-web-archive@ietf.org; Mon, 10 Nov 2003 20:49:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJNeP-0002Dv-00 for megaco-web-archive@ietf.org; Mon, 10 Nov 2003 20:49:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJNeP-0004l0-Nf; Mon, 10 Nov 2003 20:49:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJNeO-0004kn-4b for megaco@optimus.ietf.org; Mon, 10 Nov 2003 20:49:00 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28842 for ; Mon, 10 Nov 2003 20:48:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJNeL-0002Dp-00 for megaco@ietf.org; Mon, 10 Nov 2003 20:48:57 -0500 Received: from ish7.ericsson.com.au ([61.88.9.195]) by ietf-mx with esmtp (Exim 4.12) id 1AJNeK-0002Bc-00 for megaco@ietf.org; Mon, 10 Nov 2003 20:48:56 -0500 Received: from eaubrnt019.epa.ericsson.se ([146.11.31.193]) by ish7.ericsson.com.au (8.11.7+Sun/8.11.7) with ESMTP id hAB1ixp23607; Tue, 11 Nov 2003 12:44:59 +1100 (EST) Received: from ericsson.com.au (E0050DA878EDF [146.11.245.176]) by eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id WPNBN5D7; Tue, 11 Nov 2003 12:47:37 +1100 Message-ID: <3FB03E70.4070705@ericsson.com.au> Date: Tue, 11 Nov 2003 12:42:08 +1100 From: Christian Groves User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Troy Cauble CC: MEGACO list Subject: Re: [Megaco] discovering physical terminations References: <3FABE618.1020005@bell-labs.com> In-Reply-To: <3FABE618.1020005@bell-labs.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit G'Day Troy, There's no simple command that returns a list of all physical terminations. These terminations could be in the NULL context or being used in other contexts. I would think that most implementations would use a certain TID structure. So you could do an audit Context=ALL, TID=TDM/* and you should get back the individual contextID and TID. Regards, Christian Troy Cauble wrote: > > Can someone suggest a minimal, wildcarded request from the MGC > that would cause an MG to return the list of all physical > terminations? > > -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-admin@ietf.org Tue Nov 11 02:34:26 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22925 for ; Tue, 11 Nov 2003 02:34:26 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJT2J-0001VC-0Y; Tue, 11 Nov 2003 02:34:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJT2B-0001Uj-BA for megaco@optimus.ietf.org; Tue, 11 Nov 2003 02:33:55 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22889 for ; Tue, 11 Nov 2003 02:33:41 -0500 (EST) From: bvswamy@hss.hns.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJT26-0006wm-00 for megaco@ietf.org; Tue, 11 Nov 2003 02:33:50 -0500 Received: from [203.200.71.140] (helo=spark.hss.co.in) by ietf-mx with esmtp (Exim 4.12) id 1AJT24-0006wU-00 for megaco@ietf.org; Tue, 11 Nov 2003 02:33:49 -0500 Received: from ultra.hss.co.in (ultra.hss.hns.com [192.168.100.5]) by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id hAB7WpNG013517 for ; Tue, 11 Nov 2003 13:02:51 +0530 (IST) Received: from sandesh.hss.hns.com (localhost [127.0.0.1]) by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id hAB7XVN05493 for ; Tue, 11 Nov 2003 13:03:31 +0530 (IST) To: megaco@ietf.org Date: Tue, 11 Nov 2003 12:58:24 +0530 Message-ID: X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 11/11/2003 12:54:55 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Subject: [Megaco] Signal on Root termination Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Hi What is the significance of sending a signal on root termination. As per the H248.1 V2, signal can be sent on a root termination. It is specified somewhere that the suggested application is "Keep-alive" signalling. However the same purpose is now being met by Inactivity timer package I suppose (H248.14). So kindly clarify the issue and is there any plan to remove this item in subsequent implementor guides. Regards Venkat "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 exim@www1.ietf.org Tue Nov 11 02:34:34 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22940 for ; Tue, 11 Nov 2003 02:34:33 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJT2V-0001XA-Ps for megaco-archive@odin.ietf.org; Tue, 11 Nov 2003 02:34:15 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAB7YFQR005890 for megaco-archive@odin.ietf.org; Tue, 11 Nov 2003 02:34:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJT2U-0001Wr-24 for megaco-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 02:34:14 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22903 for ; Tue, 11 Nov 2003 02:34:00 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJT2O-0006xF-00 for megaco-web-archive@ietf.org; Tue, 11 Nov 2003 02:34:08 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJT2O-0006x4-00 for megaco-web-archive@ietf.org; Tue, 11 Nov 2003 02:34:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJT2J-0001VC-0Y; Tue, 11 Nov 2003 02:34:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJT2B-0001Uj-BA for megaco@optimus.ietf.org; Tue, 11 Nov 2003 02:33:55 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22889 for ; Tue, 11 Nov 2003 02:33:41 -0500 (EST) From: bvswamy@hss.hns.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJT26-0006wm-00 for megaco@ietf.org; Tue, 11 Nov 2003 02:33:50 -0500 Received: from [203.200.71.140] (helo=spark.hss.co.in) by ietf-mx with esmtp (Exim 4.12) id 1AJT24-0006wU-00 for megaco@ietf.org; Tue, 11 Nov 2003 02:33:49 -0500 Received: from ultra.hss.co.in (ultra.hss.hns.com [192.168.100.5]) by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id hAB7WpNG013517 for ; Tue, 11 Nov 2003 13:02:51 +0530 (IST) Received: from sandesh.hss.hns.com (localhost [127.0.0.1]) by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id hAB7XVN05493 for ; Tue, 11 Nov 2003 13:03:31 +0530 (IST) To: megaco@ietf.org Date: Tue, 11 Nov 2003 12:58:24 +0530 Message-ID: X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 11/11/2003 12:54:55 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Subject: [Megaco] Signal on Root termination Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Hi What is the significance of sending a signal on root termination. As per the H248.1 V2, signal can be sent on a root termination. It is specified somewhere that the suggested application is "Keep-alive" signalling. However the same purpose is now being met by Inactivity timer package I suppose (H248.14). So kindly clarify the issue and is there any plan to remove this item in subsequent implementor guides. Regards Venkat "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-admin@ietf.org Tue Nov 11 10:11:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04288 for ; Tue, 11 Nov 2003 10:11:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJaAX-0006eX-HQ; Tue, 11 Nov 2003 10:11:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJaAB-0006ad-5R for megaco@optimus.ietf.org; Tue, 11 Nov 2003 10:10:39 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04188 for ; Tue, 11 Nov 2003 10:10:26 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJaA8-0004JB-00 for megaco@ietf.org; Tue, 11 Nov 2003 10:10:37 -0500 Received: from auemail2.lucent.com ([192.11.223.163] helo=auemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AJaA8-0004Iw-00 for megaco@ietf.org; Tue, 11 Nov 2003 10:10:36 -0500 Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3]) by auemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hABF9fA08151 for ; Tue, 11 Nov 2003 09:10:03 -0600 (CST) Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id KAA12163; Tue, 11 Nov 2003 10:09:02 -0500 (EST) Cc: MEGACO list Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id KAA12154; Tue, 11 Nov 2003 10:09:00 -0500 (EST) Message-ID: <3FB0FAF5.9000103@bell-labs.com> Date: Tue, 11 Nov 2003 10:06:29 -0500 From: Troy Cauble User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christian Groves Original-CC: MEGACO list Subject: Re: [Megaco] discovering physical terminations References: <3FABE618.1020005@bell-labs.com> <3FB03E70.4070705@ericsson.com.au> In-Reply-To: <3FB03E70.4070705@ericsson.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Thanks, I'm pretty sure that Context=ALL doesn't include the NULL Context, so I'll have to send Context = * { AuditValue = TDM/* } AND Context = - { AuditValue = TDM/* } Yes? -troy Christian Groves wrote: > G'Day Troy, > > There's no simple command that returns a list of all physical > terminations. These terminations could be in the NULL context or being > used in other contexts. I would think that most implementations would > use a certain TID structure. So you could do an audit Context=ALL, > TID=TDM/* and you should get back the individual contextID and TID. > > Regards, Christian > > Troy Cauble wrote: > >> >> Can someone suggest a minimal, wildcarded request from the MGC >> that would cause an MG to return the list of all physical >> terminations? >> >> -troy _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Tue Nov 11 10:11:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04306 for ; Tue, 11 Nov 2003 10:11:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJaAb-0006il-Qd for megaco-archive@odin.ietf.org; Tue, 11 Nov 2003 10:11:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hABFB5Q5025831 for megaco-archive@odin.ietf.org; Tue, 11 Nov 2003 10:11:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJaAb-0006iY-Lv for megaco-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 10:11:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04236 for ; Tue, 11 Nov 2003 10:10:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJaAZ-0004JW-00 for megaco-web-archive@ietf.org; Tue, 11 Nov 2003 10:11:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJaAZ-0004JT-00 for megaco-web-archive@ietf.org; Tue, 11 Nov 2003 10:11:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJaAX-0006eX-HQ; Tue, 11 Nov 2003 10:11:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJaAB-0006ad-5R for megaco@optimus.ietf.org; Tue, 11 Nov 2003 10:10:39 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04188 for ; Tue, 11 Nov 2003 10:10:26 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJaA8-0004JB-00 for megaco@ietf.org; Tue, 11 Nov 2003 10:10:37 -0500 Received: from auemail2.lucent.com ([192.11.223.163] helo=auemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AJaA8-0004Iw-00 for megaco@ietf.org; Tue, 11 Nov 2003 10:10:36 -0500 Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3]) by auemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hABF9fA08151 for ; Tue, 11 Nov 2003 09:10:03 -0600 (CST) Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id KAA12163; Tue, 11 Nov 2003 10:09:02 -0500 (EST) Cc: MEGACO list Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id KAA12154; Tue, 11 Nov 2003 10:09:00 -0500 (EST) Message-ID: <3FB0FAF5.9000103@bell-labs.com> Date: Tue, 11 Nov 2003 10:06:29 -0500 From: Troy Cauble User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christian Groves Original-CC: MEGACO list Subject: Re: [Megaco] discovering physical terminations References: <3FABE618.1020005@bell-labs.com> <3FB03E70.4070705@ericsson.com.au> In-Reply-To: <3FB03E70.4070705@ericsson.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Thanks, I'm pretty sure that Context=ALL doesn't include the NULL Context, so I'll have to send Context = * { AuditValue = TDM/* } AND Context = - { AuditValue = TDM/* } Yes? -troy Christian Groves wrote: > G'Day Troy, > > There's no simple command that returns a list of all physical > terminations. These terminations could be in the NULL context or being > used in other contexts. I would think that most implementations would > use a certain TID structure. So you could do an audit Context=ALL, > TID=TDM/* and you should get back the individual contextID and TID. > > Regards, Christian > > Troy Cauble wrote: > >> >> Can someone suggest a minimal, wildcarded request from the MGC >> that would cause an MG to return the list of all physical >> terminations? >> >> -troy _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Tue Nov 11 10:54:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06830 for ; Tue, 11 Nov 2003 10:54:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJaq9-00017Y-1D; Tue, 11 Nov 2003 10:54:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJPyy-00077s-Gu for megaco@optimus.ietf.org; Mon, 10 Nov 2003 23:18:24 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04549 for ; Mon, 10 Nov 2003 23:18:11 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJPyw-0004QV-00 for Megaco@ietf.org; Mon, 10 Nov 2003 23:18:22 -0500 Received: from [80.191.2.2] (helo=laleh.itrc.ac.ir) by ietf-mx with esmtp (Exim 4.12) id 1AJPyv-0004Q7-00 for Megaco@ietf.org; Mon, 10 Nov 2003 23:18:21 -0500 Received: from switchsadeghi (yas.2.191.80.in-addr.arpa [80.191.2.7] (may be forged)) by laleh.itrc.ac.ir (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id hAB4ICS13535 for ; Tue, 11 Nov 2003 07:48:12 +0330 Message-ID: <000a01c3a80a$cb674d30$e502a8c0@switchsadeghi> From: "Azam Sadegh Zadeh" To: Date: Tue, 11 Nov 2003 07:47:56 +0330 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C3A828.1E7F18F0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4922.1500 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4925.2800 Subject: [Megaco] question Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C3A828.1E7F18F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello If is Resource Management unit into MG , what does command of megaco = into MG ? ------=_NextPart_000_0007_01C3A828.1E7F18F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello
If  is Resource Management unit = into MG , what=20 does command of megaco into MG ?
 
------=_NextPart_000_0007_01C3A828.1E7F18F0-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Tue Nov 11 10:54:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06847 for ; Tue, 11 Nov 2003 10:54:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJaqD-00018y-4X for megaco-archive@odin.ietf.org; Tue, 11 Nov 2003 10:54:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hABFs5eW004390 for megaco-archive@odin.ietf.org; Tue, 11 Nov 2003 10:54:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJaqC-00018j-VM for megaco-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 10:54:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06810 for ; Tue, 11 Nov 2003 10:53:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJaqA-000507-00 for megaco-web-archive@ietf.org; Tue, 11 Nov 2003 10:54:02 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJaqA-000504-00 for megaco-web-archive@ietf.org; Tue, 11 Nov 2003 10:54:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJaq9-00017Y-1D; Tue, 11 Nov 2003 10:54:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJPyy-00077s-Gu for megaco@optimus.ietf.org; Mon, 10 Nov 2003 23:18:24 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04549 for ; Mon, 10 Nov 2003 23:18:11 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJPyw-0004QV-00 for Megaco@ietf.org; Mon, 10 Nov 2003 23:18:22 -0500 Received: from [80.191.2.2] (helo=laleh.itrc.ac.ir) by ietf-mx with esmtp (Exim 4.12) id 1AJPyv-0004Q7-00 for Megaco@ietf.org; Mon, 10 Nov 2003 23:18:21 -0500 Received: from switchsadeghi (yas.2.191.80.in-addr.arpa [80.191.2.7] (may be forged)) by laleh.itrc.ac.ir (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id hAB4ICS13535 for ; Tue, 11 Nov 2003 07:48:12 +0330 Message-ID: <000a01c3a80a$cb674d30$e502a8c0@switchsadeghi> From: "Azam Sadegh Zadeh" To: Date: Tue, 11 Nov 2003 07:47:56 +0330 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C3A828.1E7F18F0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4922.1500 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4925.2800 Subject: [Megaco] question Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C3A828.1E7F18F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello If is Resource Management unit into MG , what does command of megaco = into MG ? ------=_NextPart_000_0007_01C3A828.1E7F18F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello
If  is Resource Management unit = into MG , what=20 does command of megaco into MG ?
 
------=_NextPart_000_0007_01C3A828.1E7F18F0-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Tue Nov 11 11:25:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08174 for ; Tue, 11 Nov 2003 11:25:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJbKA-0003yP-Rk; Tue, 11 Nov 2003 11:25:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJbJy-0003wo-8P for megaco@optimus.ietf.org; Tue, 11 Nov 2003 11:24:50 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08121 for ; Tue, 11 Nov 2003 11:24:38 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJbJx-0005P1-00 for megaco@ietf.org; Tue, 11 Nov 2003 11:24:49 -0500 Received: from motgate4.mot.com ([144.189.100.102]) by ietf-mx with esmtp (Exim 4.12) id 1AJbJv-0005Ov-00 for megaco@ietf.org; Tue, 11 Nov 2003 11:24:48 -0500 Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by motgate4.mot.com (Motorola/Motgate4) with ESMTP id hABGORj7017924; Tue, 11 Nov 2003 09:24:29 -0700 (MST) Received: from smilevm.motorola.com ([10.14.25.162]) by il06exr03.mot.com (Motorola/il06exr03) with ESMTP id hABGOJMj006390; Tue, 11 Nov 2003 10:24:19 -0600 Message-Id: <5.2.1.1.0.20031111103530.02560aa0@IL06EXM13.corp.mot.com> X-Sender: A19776@IL06EXM13.corp.mot.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Tue, 11 Nov 2003 11:22:08 -0500 To: Troy Cauble, MEGACO list From: Aleksandr Ryabin Subject: Re: [Megaco] discovering physical terminations Cc: Christian Groves In-Reply-To: <3FB03E70.4070705@ericsson.com.au> References: <3FABE618.1020005@bell-labs.com> <3FABE618.1020005@bell-labs.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_1807855819==.ALT" Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , --=====================_1807855819==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Hi, That is the closest would be as follows (substitute TerminationId * with your physical TerminationId wildcard, e.g. TDM/*). Note that AuditValue in NULL context should be marked as optional in case if there is no terminations in NULL context, such that MG would place an error for it, but will continue on to Context = * MEGACO/1 [10.1.2.3]:1234 Transaction = 168377 { Context = - { O-AuditValue = * { Audit {} } }, Context = * { AuditValue = * { Audit {} } } } MG could return TerminationIds in "condensed" form (as specified by the spec) for each context, e.g.: MEGACO/1 [10.1.2.5]:4321 Reply = 168377 { Context = - { AuditValue = Context { Term1, Term2, Term3 ; all terminations in context NULL } }, Context = 123 { AuditValue = Context { Term4, Term5; all terminations in context 123 } }, Context = 456 { AuditValue = Context { Term6, Term7 ; all terminations in context 456 } ; ... etc. } } Of course caution must be taken with the size of reply. E.g. TCP should be used, or request should be repeated with decreased TerminationId wildcard granularity if MG returns error 533 (Response exceeded max PDU size) BTW. I don't want to be pain, but I wish we could've added "split" package support, or one of the other solutions discussed on the list in "Segmentation" thread about a year ago. Regards, Aleks At 08:42 PM 11/10/2003, Christian Groves wrote: >G'Day Troy, > >There's no simple command that returns a list of all physical >terminations. These terminations could be in the NULL context or being >used in other contexts. I would think that most implementations would use >a certain TID structure. So you could do an audit Context=ALL, TID=TDM/* >and you should get back the individual contextID and TID. > >Regards, Christian > >Troy Cauble wrote: > >>Can someone suggest a minimal, wildcarded request from the MGC >>that would cause an MG to return the list of all physical >>terminations? >>-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 --=====================_1807855819==.ALT Content-Type: text/html; charset="us-ascii" Hi,

That is the closest would be as follows (substitute TerminationId * with
your physical TerminationId wildcard, e.g. TDM/*).

Note that AuditValue in NULL context should be marked as optional
in case if there is no terminations in NULL context, such that
MG would place an error for it, but will continue on to Context = *

MEGACO/1 [10.1.2.3]:1234
Transaction = 168377 {
  Context = - {
    O-AuditValue = * {
      Audit {}
    }
  },
  Context = * {
    AuditValue = * {
      Audit {}
    }
  }
}

MG could return TerminationIds in "condensed" form (as specified by
the spec) for each context, e.g.:

MEGACO/1 [10.1.2.5]:4321
Reply = 168377 {
  Context = - {
    AuditValue = Context {
      Term1, Term2, Term3 ; all terminations in context NULL
    }
  },
  Context = 123 {
    AuditValue = Context {
      Term4, Term5; all terminations in context 123
    }
  },
  Context = 456 {
    AuditValue = Context {
      Term6, Term7      ; all terminations in context 456
    }
    ; ... etc.
  }
}

Of course caution must be taken with the size of reply.
E.g. TCP should be used, or request should be repeated with
decreased TerminationId wildcard granularity if MG returns error
533 (Response exceeded max PDU size)

BTW. I don't want to be pain, but I wish we could've added "split"
package support, or one of the other solutions discussed on the
list in "Segmentation" thread about a year ago.

Regards,
        Aleks

At 08:42 PM 11/10/2003, Christian Groves wrote:
G'Day Troy,

There's no simple command that returns a list of all physical terminations. These terminations could be in the NULL context or being used in other contexts.  I would think that most implementations would use a certain TID structure. So you could do an audit Context=ALL, TID=TDM/* and you should get back the individual contextID and TID.

Regards, Christian

Troy Cauble wrote:

Can someone suggest a minimal, wildcarded request from the MGC
that would cause an MG to return the list of all physical
terminations?
-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
--=====================_1807855819==.ALT-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Tue Nov 11 11:25:27 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08192 for ; Tue, 11 Nov 2003 11:25:26 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJbKF-000402-9o for megaco-archive@odin.ietf.org; Tue, 11 Nov 2003 11:25:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hABGP7H3015373 for megaco-archive@odin.ietf.org; Tue, 11 Nov 2003 11:25:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJbKF-0003zs-5t for megaco-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 11:25:07 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08129 for ; Tue, 11 Nov 2003 11:24:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJbKE-0005PG-00 for megaco-web-archive@ietf.org; Tue, 11 Nov 2003 11:25:06 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJbKD-0005PD-00 for megaco-web-archive@ietf.org; Tue, 11 Nov 2003 11:25:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJbKA-0003yP-Rk; Tue, 11 Nov 2003 11:25:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJbJy-0003wo-8P for megaco@optimus.ietf.org; Tue, 11 Nov 2003 11:24:50 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08121 for ; Tue, 11 Nov 2003 11:24:38 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJbJx-0005P1-00 for megaco@ietf.org; Tue, 11 Nov 2003 11:24:49 -0500 Received: from motgate4.mot.com ([144.189.100.102]) by ietf-mx with esmtp (Exim 4.12) id 1AJbJv-0005Ov-00 for megaco@ietf.org; Tue, 11 Nov 2003 11:24:48 -0500 Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by motgate4.mot.com (Motorola/Motgate4) with ESMTP id hABGORj7017924; Tue, 11 Nov 2003 09:24:29 -0700 (MST) Received: from smilevm.motorola.com ([10.14.25.162]) by il06exr03.mot.com (Motorola/il06exr03) with ESMTP id hABGOJMj006390; Tue, 11 Nov 2003 10:24:19 -0600 Message-Id: <5.2.1.1.0.20031111103530.02560aa0@IL06EXM13.corp.mot.com> X-Sender: A19776@IL06EXM13.corp.mot.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Tue, 11 Nov 2003 11:22:08 -0500 To: Troy Cauble, MEGACO list From: Aleksandr Ryabin Subject: Re: [Megaco] discovering physical terminations Cc: Christian Groves In-Reply-To: <3FB03E70.4070705@ericsson.com.au> References: <3FABE618.1020005@bell-labs.com> <3FABE618.1020005@bell-labs.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_1807855819==.ALT" Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , --=====================_1807855819==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Hi, That is the closest would be as follows (substitute TerminationId * with your physical TerminationId wildcard, e.g. TDM/*). Note that AuditValue in NULL context should be marked as optional in case if there is no terminations in NULL context, such that MG would place an error for it, but will continue on to Context = * MEGACO/1 [10.1.2.3]:1234 Transaction = 168377 { Context = - { O-AuditValue = * { Audit {} } }, Context = * { AuditValue = * { Audit {} } } } MG could return TerminationIds in "condensed" form (as specified by the spec) for each context, e.g.: MEGACO/1 [10.1.2.5]:4321 Reply = 168377 { Context = - { AuditValue = Context { Term1, Term2, Term3 ; all terminations in context NULL } }, Context = 123 { AuditValue = Context { Term4, Term5; all terminations in context 123 } }, Context = 456 { AuditValue = Context { Term6, Term7 ; all terminations in context 456 } ; ... etc. } } Of course caution must be taken with the size of reply. E.g. TCP should be used, or request should be repeated with decreased TerminationId wildcard granularity if MG returns error 533 (Response exceeded max PDU size) BTW. I don't want to be pain, but I wish we could've added "split" package support, or one of the other solutions discussed on the list in "Segmentation" thread about a year ago. Regards, Aleks At 08:42 PM 11/10/2003, Christian Groves wrote: >G'Day Troy, > >There's no simple command that returns a list of all physical >terminations. These terminations could be in the NULL context or being >used in other contexts. I would think that most implementations would use >a certain TID structure. So you could do an audit Context=ALL, TID=TDM/* >and you should get back the individual contextID and TID. > >Regards, Christian > >Troy Cauble wrote: > >>Can someone suggest a minimal, wildcarded request from the MGC >>that would cause an MG to return the list of all physical >>terminations? >>-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 --=====================_1807855819==.ALT Content-Type: text/html; charset="us-ascii" Hi,

That is the closest would be as follows (substitute TerminationId * with
your physical TerminationId wildcard, e.g. TDM/*).

Note that AuditValue in NULL context should be marked as optional
in case if there is no terminations in NULL context, such that
MG would place an error for it, but will continue on to Context = *

MEGACO/1 [10.1.2.3]:1234
Transaction = 168377 {
  Context = - {
    O-AuditValue = * {
      Audit {}
    }
  },
  Context = * {
    AuditValue = * {
      Audit {}
    }
  }
}

MG could return TerminationIds in "condensed" form (as specified by
the spec) for each context, e.g.:

MEGACO/1 [10.1.2.5]:4321
Reply = 168377 {
  Context = - {
    AuditValue = Context {
      Term1, Term2, Term3 ; all terminations in context NULL
    }
  },
  Context = 123 {
    AuditValue = Context {
      Term4, Term5; all terminations in context 123
    }
  },
  Context = 456 {
    AuditValue = Context {
      Term6, Term7      ; all terminations in context 456
    }
    ; ... etc.
  }
}

Of course caution must be taken with the size of reply.
E.g. TCP should be used, or request should be repeated with
decreased TerminationId wildcard granularity if MG returns error
533 (Response exceeded max PDU size)

BTW. I don't want to be pain, but I wish we could've added "split"
package support, or one of the other solutions discussed on the
list in "Segmentation" thread about a year ago.

Regards,
        Aleks

At 08:42 PM 11/10/2003, Christian Groves wrote:
G'Day Troy,

There's no simple command that returns a list of all physical terminations. These terminations could be in the NULL context or being used in other contexts.  I would think that most implementations would use a certain TID structure. So you could do an audit Context=ALL, TID=TDM/* and you should get back the individual contextID and TID.

Regards, Christian

Troy Cauble wrote:

Can someone suggest a minimal, wildcarded request from the MGC
that would cause an MG to return the list of all physical
terminations?
-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
--=====================_1807855819==.ALT-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Tue Nov 11 17:07:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24000 for ; Tue, 11 Nov 2003 17:07:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJgf8-0001Oq-73; Tue, 11 Nov 2003 17:07:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJgeu-0001MS-Eb for megaco@optimus.ietf.org; Tue, 11 Nov 2003 17:06:48 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23972 for ; Tue, 11 Nov 2003 17:06:35 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJges-0002zv-00 for megaco@ietf.org; Tue, 11 Nov 2003 17:06:46 -0500 Received: from ish7.ericsson.com.au ([61.88.9.195]) by ietf-mx with esmtp (Exim 4.12) id 1AJgeq-0002zN-00 for megaco@ietf.org; Tue, 11 Nov 2003 17:06:45 -0500 Received: from eaubrnt019.epa.ericsson.se ([146.11.31.193]) by ish7.ericsson.com.au (8.11.7+Sun/8.11.7) with ESMTP id hABM3Dp21108; Wed, 12 Nov 2003 09:03:13 +1100 (EST) Received: from ericsson.com.au (146.11.245.220 [146.11.245.220]) by eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id WPNB3QHF; Wed, 12 Nov 2003 09:05:52 +1100 Message-ID: <3FB15BF2.3050405@ericsson.com.au> Date: Wed, 12 Nov 2003 09:00:18 +1100 From: Christian Groves User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Troy Cauble CC: MEGACO list Subject: Re: [Megaco] discovering physical terminations References: <3FABE618.1020005@bell-labs.com> <3FB03E70.4070705@ericsson.com.au> <3FB0FAF5.9000103@bell-labs.com> In-Reply-To: <3FB0FAF5.9000103@bell-labs.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Yes, I was too lazy to add NULL, the main thing was the audit on the partial TID. Christian Troy Cauble wrote: > > Thanks, > > I'm pretty sure that Context=ALL doesn't include the NULL Context, > so I'll have to send > Context = * { AuditValue = TDM/* } AND > Context = - { AuditValue = TDM/* } > > Yes? > > -troy > > > > > Christian Groves wrote: > >> G'Day Troy, >> >> There's no simple command that returns a list of all physical >> terminations. These terminations could be in the NULL context or being >> used in other contexts. I would think that most implementations would >> use a certain TID structure. So you could do an audit Context=ALL, >> TID=TDM/* and you should get back the individual contextID and TID. >> >> Regards, Christian >> >> Troy Cauble wrote: >> >>> >>> Can someone suggest a minimal, wildcarded request from the MGC >>> that would cause an MG to return the list of all physical >>> terminations? >>> >>> -troy > > > _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Tue Nov 11 17:07:25 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24016 for ; Tue, 11 Nov 2003 17:07:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJgfD-0001Qr-1C for megaco-archive@odin.ietf.org; Tue, 11 Nov 2003 17:07:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hABM766x005491 for megaco-archive@odin.ietf.org; Tue, 11 Nov 2003 17:07:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJgfB-0001QM-V3 for megaco-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 17:07:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23992 for ; Tue, 11 Nov 2003 17:06:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJgf9-00030S-00 for megaco-web-archive@ietf.org; Tue, 11 Nov 2003 17:07:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJgf9-00030P-00 for megaco-web-archive@ietf.org; Tue, 11 Nov 2003 17:07:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJgf8-0001Oq-73; Tue, 11 Nov 2003 17:07:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJgeu-0001MS-Eb for megaco@optimus.ietf.org; Tue, 11 Nov 2003 17:06:48 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23972 for ; Tue, 11 Nov 2003 17:06:35 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJges-0002zv-00 for megaco@ietf.org; Tue, 11 Nov 2003 17:06:46 -0500 Received: from ish7.ericsson.com.au ([61.88.9.195]) by ietf-mx with esmtp (Exim 4.12) id 1AJgeq-0002zN-00 for megaco@ietf.org; Tue, 11 Nov 2003 17:06:45 -0500 Received: from eaubrnt019.epa.ericsson.se ([146.11.31.193]) by ish7.ericsson.com.au (8.11.7+Sun/8.11.7) with ESMTP id hABM3Dp21108; Wed, 12 Nov 2003 09:03:13 +1100 (EST) Received: from ericsson.com.au (146.11.245.220 [146.11.245.220]) by eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id WPNB3QHF; Wed, 12 Nov 2003 09:05:52 +1100 Message-ID: <3FB15BF2.3050405@ericsson.com.au> Date: Wed, 12 Nov 2003 09:00:18 +1100 From: Christian Groves User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Troy Cauble CC: MEGACO list Subject: Re: [Megaco] discovering physical terminations References: <3FABE618.1020005@bell-labs.com> <3FB03E70.4070705@ericsson.com.au> <3FB0FAF5.9000103@bell-labs.com> In-Reply-To: <3FB0FAF5.9000103@bell-labs.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Yes, I was too lazy to add NULL, the main thing was the audit on the partial TID. Christian Troy Cauble wrote: > > Thanks, > > I'm pretty sure that Context=ALL doesn't include the NULL Context, > so I'll have to send > Context = * { AuditValue = TDM/* } AND > Context = - { AuditValue = TDM/* } > > Yes? > > -troy > > > > > Christian Groves wrote: > >> G'Day Troy, >> >> There's no simple command that returns a list of all physical >> terminations. These terminations could be in the NULL context or being >> used in other contexts. I would think that most implementations would >> use a certain TID structure. So you could do an audit Context=ALL, >> TID=TDM/* and you should get back the individual contextID and TID. >> >> Regards, Christian >> >> Troy Cauble wrote: >> >>> >>> Can someone suggest a minimal, wildcarded request from the MGC >>> that would cause an MG to return the list of all physical >>> terminations? >>> >>> -troy > > > _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Tue Nov 11 17:09:19 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24094 for ; Tue, 11 Nov 2003 17:09:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJgh3-0001yc-EH; Tue, 11 Nov 2003 17:09:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJggj-0001v5-6l for megaco@optimus.ietf.org; Tue, 11 Nov 2003 17:08:41 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24049 for ; Tue, 11 Nov 2003 17:08:28 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJggg-000319-00 for megaco@ietf.org; Tue, 11 Nov 2003 17:08:39 -0500 Received: from ish7.ericsson.com.au ([61.88.9.195]) by ietf-mx with esmtp (Exim 4.12) id 1AJggf-00030r-00 for megaco@ietf.org; Tue, 11 Nov 2003 17:08:38 -0500 Received: from eaubrnt019.epa.ericsson.se ([146.11.31.193]) by ish7.ericsson.com.au (8.11.7+Sun/8.11.7) with ESMTP id hABM55p21377; Wed, 12 Nov 2003 09:05:05 +1100 (EST) Received: from ericsson.com.au (146.11.245.220 [146.11.245.220]) by eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id WPNB3QJG; Wed, 12 Nov 2003 09:07:44 +1100 Message-ID: <3FB15C63.6020109@ericsson.com.au> Date: Wed, 12 Nov 2003 09:02:11 +1100 From: Christian Groves User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: bvswamy@hss.hns.com CC: megaco@ietf.org Subject: Re: [Megaco] Signal on Root termination References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hello Venkat, The signal on root was for situations where MGs send keep alives between each other to keep associations alive. The keep alive mechanism in H.248.14 is between the MG and MGC. There is no plan to remove this. Christian bvswamy@hss.hns.com wrote: > > > > Hi > What is the significance of sending a signal on root termination. As > per the H248.1 V2, signal can be sent on a root termination. > It is specified somewhere that the suggested application is "Keep-alive" > signalling. However the same purpose is now being met by > Inactivity timer package I suppose (H248.14). > So kindly clarify the issue and is there any plan to remove this item > in subsequent implementor guides. > > > Regards > Venkat > > > "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 From exim@www1.ietf.org Tue Nov 11 17:09:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24112 for ; Tue, 11 Nov 2003 17:09:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJgh4-000209-U9 for megaco-archive@odin.ietf.org; Tue, 11 Nov 2003 17:09:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hABM92Tn007687 for megaco-archive@odin.ietf.org; Tue, 11 Nov 2003 17:09:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJgh4-0001zu-Pr for megaco-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 17:09:02 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24057 for ; Tue, 11 Nov 2003 17:08:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJgh2-00031L-00 for megaco-web-archive@ietf.org; Tue, 11 Nov 2003 17:09:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJgh2-00031I-00 for megaco-web-archive@ietf.org; Tue, 11 Nov 2003 17:09:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJgh3-0001yc-EH; Tue, 11 Nov 2003 17:09:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJggj-0001v5-6l for megaco@optimus.ietf.org; Tue, 11 Nov 2003 17:08:41 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24049 for ; Tue, 11 Nov 2003 17:08:28 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJggg-000319-00 for megaco@ietf.org; Tue, 11 Nov 2003 17:08:39 -0500 Received: from ish7.ericsson.com.au ([61.88.9.195]) by ietf-mx with esmtp (Exim 4.12) id 1AJggf-00030r-00 for megaco@ietf.org; Tue, 11 Nov 2003 17:08:38 -0500 Received: from eaubrnt019.epa.ericsson.se ([146.11.31.193]) by ish7.ericsson.com.au (8.11.7+Sun/8.11.7) with ESMTP id hABM55p21377; Wed, 12 Nov 2003 09:05:05 +1100 (EST) Received: from ericsson.com.au (146.11.245.220 [146.11.245.220]) by eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id WPNB3QJG; Wed, 12 Nov 2003 09:07:44 +1100 Message-ID: <3FB15C63.6020109@ericsson.com.au> Date: Wed, 12 Nov 2003 09:02:11 +1100 From: Christian Groves User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: bvswamy@hss.hns.com CC: megaco@ietf.org Subject: Re: [Megaco] Signal on Root termination References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello Venkat, The signal on root was for situations where MGs send keep alives between each other to keep associations alive. The keep alive mechanism in H.248.14 is between the MG and MGC. There is no plan to remove this. Christian bvswamy@hss.hns.com wrote: > > > > Hi > What is the significance of sending a signal on root termination. As > per the H248.1 V2, signal can be sent on a root termination. > It is specified somewhere that the suggested application is "Keep-alive" > signalling. However the same purpose is now being met by > Inactivity timer package I suppose (H248.14). > So kindly clarify the issue and is there any plan to remove this item > in subsequent implementor guides. > > > Regards > Venkat > > > "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 From megaco-admin@ietf.org Wed Nov 12 08:28:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16783 for ; Wed, 12 Nov 2003 08:28:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJv2P-0001MW-4u; Wed, 12 Nov 2003 08:28:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJv1g-0001Lx-4J for megaco@optimus.ietf.org; Wed, 12 Nov 2003 08:27:16 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16738 for ; Wed, 12 Nov 2003 08:27:04 -0500 (EST) From: bvswamy@hss.hns.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJv1e-0006Qx-00 for megaco@ietf.org; Wed, 12 Nov 2003 08:27:14 -0500 Received: from [203.200.71.140] (helo=spark.hss.co.in) by ietf-mx with esmtp (Exim 4.12) id 1AJv1d-0006QE-00 for megaco@ietf.org; Wed, 12 Nov 2003 08:27:13 -0500 Received: from ultra.hss.co.in (ultra.hss.hns.com [192.168.100.5]) by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id hACDOfNG003804; Wed, 12 Nov 2003 18:54:41 +0530 (IST) Received: from sandesh.hss.hns.com (localhost [127.0.0.1]) by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id hACDPO012914; Wed, 12 Nov 2003 18:55:24 +0530 (IST) Subject: Re: [Megaco] Signal on Root termination To: Christian Groves Cc: megaco@ietf.org Date: Wed, 12 Nov 2003 18:50:05 +0530 Message-ID: X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 11/12/2003 18:46:47 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Hi Christian Thanks for your clarification. Can you please share which document captures the procedure for this and what will be the trigger for MGC to send a modify command with signal on root. As far as keeping association(control association between MG-MGC) alive and knowledge of association across redundant MG's is concerned it is more of implementation dependant issue and it is not clear how signal on root will be able to resolve this issue. Regards Venkat Christian Groves @ietf.org on 11/12/2003 03:32:11 AM Sent by: megaco-admin@ietf.org To: B Venkat S.R Swamy/HSS@HSS cc: megaco@ietf.org Subject: Re: [Megaco] Signal on Root termination Hello Venkat, The signal on root was for situations where MGs send keep alives between each other to keep associations alive. The keep alive mechanism in H.248.14 is between the MG and MGC. There is no plan to remove this. Christian bvswamy@hss.hns.com wrote: > > > > Hi > What is the significance of sending a signal on root termination. As > per the H248.1 V2, signal can be sent on a root termination. > It is specified somewhere that the suggested application is "Keep-alive" > signalling. However the same purpose is now being met by > Inactivity timer package I suppose (H248.14). > So kindly clarify the issue and is there any plan to remove this item > in subsequent implementor guides. > > > Regards > Venkat > > > "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 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Wed Nov 12 08:28:25 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16804 for ; Wed, 12 Nov 2003 08:28:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJv2T-0001NN-Up for megaco-archive@odin.ietf.org; Wed, 12 Nov 2003 08:28:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hACDS5sf005285 for megaco-archive@odin.ietf.org; Wed, 12 Nov 2003 08:28:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJv2T-0001NA-P7 for megaco-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 08:28:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16780 for ; Wed, 12 Nov 2003 08:27:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJv2S-0006RP-00 for megaco-web-archive@ietf.org; Wed, 12 Nov 2003 08:28:04 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJv2S-0006RL-00 for megaco-web-archive@ietf.org; Wed, 12 Nov 2003 08:28:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJv2P-0001MW-4u; Wed, 12 Nov 2003 08:28:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJv1g-0001Lx-4J for megaco@optimus.ietf.org; Wed, 12 Nov 2003 08:27:16 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16738 for ; Wed, 12 Nov 2003 08:27:04 -0500 (EST) From: bvswamy@hss.hns.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJv1e-0006Qx-00 for megaco@ietf.org; Wed, 12 Nov 2003 08:27:14 -0500 Received: from [203.200.71.140] (helo=spark.hss.co.in) by ietf-mx with esmtp (Exim 4.12) id 1AJv1d-0006QE-00 for megaco@ietf.org; Wed, 12 Nov 2003 08:27:13 -0500 Received: from ultra.hss.co.in (ultra.hss.hns.com [192.168.100.5]) by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id hACDOfNG003804; Wed, 12 Nov 2003 18:54:41 +0530 (IST) Received: from sandesh.hss.hns.com (localhost [127.0.0.1]) by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id hACDPO012914; Wed, 12 Nov 2003 18:55:24 +0530 (IST) Subject: Re: [Megaco] Signal on Root termination To: Christian Groves Cc: megaco@ietf.org Date: Wed, 12 Nov 2003 18:50:05 +0530 Message-ID: X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 11/12/2003 18:46:47 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Hi Christian Thanks for your clarification. Can you please share which document captures the procedure for this and what will be the trigger for MGC to send a modify command with signal on root. As far as keeping association(control association between MG-MGC) alive and knowledge of association across redundant MG's is concerned it is more of implementation dependant issue and it is not clear how signal on root will be able to resolve this issue. Regards Venkat Christian Groves @ietf.org on 11/12/2003 03:32:11 AM Sent by: megaco-admin@ietf.org To: B Venkat S.R Swamy/HSS@HSS cc: megaco@ietf.org Subject: Re: [Megaco] Signal on Root termination Hello Venkat, The signal on root was for situations where MGs send keep alives between each other to keep associations alive. The keep alive mechanism in H.248.14 is between the MG and MGC. There is no plan to remove this. Christian bvswamy@hss.hns.com wrote: > > > > Hi > What is the significance of sending a signal on root termination. As > per the H248.1 V2, signal can be sent on a root termination. > It is specified somewhere that the suggested application is "Keep-alive" > signalling. However the same purpose is now being met by > Inactivity timer package I suppose (H248.14). > So kindly clarify the issue and is there any plan to remove this item > in subsequent implementor guides. > > > Regards > Venkat > > > "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 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Wed Nov 12 14:09:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02182 for ; Wed, 12 Nov 2003 14:09:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK0MO-0008J2-Ty; Wed, 12 Nov 2003 14:09:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJspx-0002RC-HE for megaco@optimus.ietf.org; Wed, 12 Nov 2003 06:07:01 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13862 for ; Wed, 12 Nov 2003 06:06:47 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJspt-0004wl-00 for megaco@ietf.org; Wed, 12 Nov 2003 06:06:57 -0500 Received: from 205-158-62-67.outblaze.com ([205.158.62.67] helo=spf13.us4.outblaze.com) by ietf-mx with esmtp (Exim 4.12) id 1AJspt-0004wX-00 for megaco@ietf.org; Wed, 12 Nov 2003 06:06:57 -0500 Received: from 205-158-62-146.outblaze.com (205-158-62-146.outblaze.com [205.158.62.146]) by spf13.us4.outblaze.com (Postfix) with QMQP id 617F21801F4B for ; Wed, 12 Nov 2003 11:06:28 +0000 (GMT) Received: (qmail 3040 invoked from network); 12 Nov 2003 11:06:28 -0000 Received: from unknown (HELO ws3-4.us4.outblaze.com) (205.158.62.94) by 205-158-62-146.outblaze.com with SMTP; 12 Nov 2003 11:06:28 -0000 Received: (qmail 2368 invoked by uid 1001); 12 Nov 2003 11:06:28 -0000 Message-ID: <20031112110628.2367.qmail@email.com> Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Received: from [61.16.234.126] by ws3-4.us4.outblaze.com with http for harry_suede@email.com; Wed, 12 Nov 2003 06:06:28 -0500 From: "Harry Suede" To: megaco@ietf.org Date: Wed, 12 Nov 2003 06:06:28 -0500 X-Originating-Ip: 61.16.234.126 X-Originating-Server: ws3-4.us4.outblaze.com Content-Transfer-Encoding: 7bit Subject: [Megaco] g/sc Notification during Subtract Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi List, A signal is being applied on a termination in Non-NULL context. Then MGC sends Subtract command on the termination. The MG will stop the signal during processing of Subtract command. Should MG send the Notify command for g/sc event with "NC" (Not completed, other cause) towards MGC? I think , since all the active descriptors shall be reset during Subtract processing, so MG should **not** send g/sc notification as Events descriptor doesn't contain g/sc at that point of time. Pls. respond. Thanks Harry. -- __________________________________________________________ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup Search Smarter - get the new eXact Search Bar for free! http://www.exactsearchbar.com/ _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Wed Nov 12 14:09:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02200 for ; Wed, 12 Nov 2003 14:09:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK0MU-0008Jx-0R for megaco-archive@odin.ietf.org; Wed, 12 Nov 2003 14:09:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hACJ953e031981 for megaco-archive@odin.ietf.org; Wed, 12 Nov 2003 14:09:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK0MT-0008Jg-Qo for megaco-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 14:09:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02168 for ; Wed, 12 Nov 2003 14:08:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AK0MR-00040B-00 for megaco-web-archive@ietf.org; Wed, 12 Nov 2003 14:09:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AK0MQ-000408-00 for megaco-web-archive@ietf.org; Wed, 12 Nov 2003 14:09:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK0MO-0008J2-Ty; Wed, 12 Nov 2003 14:09:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJspx-0002RC-HE for megaco@optimus.ietf.org; Wed, 12 Nov 2003 06:07:01 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13862 for ; Wed, 12 Nov 2003 06:06:47 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJspt-0004wl-00 for megaco@ietf.org; Wed, 12 Nov 2003 06:06:57 -0500 Received: from 205-158-62-67.outblaze.com ([205.158.62.67] helo=spf13.us4.outblaze.com) by ietf-mx with esmtp (Exim 4.12) id 1AJspt-0004wX-00 for megaco@ietf.org; Wed, 12 Nov 2003 06:06:57 -0500 Received: from 205-158-62-146.outblaze.com (205-158-62-146.outblaze.com [205.158.62.146]) by spf13.us4.outblaze.com (Postfix) with QMQP id 617F21801F4B for ; Wed, 12 Nov 2003 11:06:28 +0000 (GMT) Received: (qmail 3040 invoked from network); 12 Nov 2003 11:06:28 -0000 Received: from unknown (HELO ws3-4.us4.outblaze.com) (205.158.62.94) by 205-158-62-146.outblaze.com with SMTP; 12 Nov 2003 11:06:28 -0000 Received: (qmail 2368 invoked by uid 1001); 12 Nov 2003 11:06:28 -0000 Message-ID: <20031112110628.2367.qmail@email.com> Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Received: from [61.16.234.126] by ws3-4.us4.outblaze.com with http for harry_suede@email.com; Wed, 12 Nov 2003 06:06:28 -0500 From: "Harry Suede" To: megaco@ietf.org Date: Wed, 12 Nov 2003 06:06:28 -0500 X-Originating-Ip: 61.16.234.126 X-Originating-Server: ws3-4.us4.outblaze.com Content-Transfer-Encoding: 7bit Subject: [Megaco] g/sc Notification during Subtract Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi List, A signal is being applied on a termination in Non-NULL context. Then MGC sends Subtract command on the termination. The MG will stop the signal during processing of Subtract command. Should MG send the Notify command for g/sc event with "NC" (Not completed, other cause) towards MGC? I think , since all the active descriptors shall be reset during Subtract processing, so MG should **not** send g/sc notification as Events descriptor doesn't contain g/sc at that point of time. Pls. respond. Thanks Harry. -- __________________________________________________________ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup Search Smarter - get the new eXact Search Bar for free! http://www.exactsearchbar.com/ _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Wed Nov 12 18:52:18 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18052 for ; Wed, 12 Nov 2003 18:52:17 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK4mG-0003jO-TY; Wed, 12 Nov 2003 18:52:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK4Sp-0001JF-Kg for megaco@optimus.ietf.org; Wed, 12 Nov 2003 18:31:55 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17151 for ; Wed, 12 Nov 2003 18:31:41 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AK4Sm-0000zg-00 for megaco@ietf.org; Wed, 12 Nov 2003 18:31:52 -0500 Received: from protext02.itu.ch ([156.106.192.19] helo=itu.ch) by ietf-mx with esmtp (Exim 4.12) id 1AK4Sl-0000zL-00 for megaco@ietf.org; Wed, 12 Nov 2003 18:31:52 -0500 Received: from protext02.exadir.itu.ch ([156.106.192.19]) by itu.ch with Microsoft SMTPSVC(5.0.2195.6713); Thu, 13 Nov 2003 00:31:21 +0100 Received: From mail6.itu.ch ([156.106.192.22]) by protext02.exadir.itu.ch (WebShield SMTP v4.5 MR1a); id 106867988081; Thu, 13 Nov 2003 00:31:20 +0100 Received: from ties.itu.ch (root@ties.itu.ch [156.106.192.33]) by mail6.itu.ch (8.12.10/8.12.10) with ESMTP id hACNVJaR475667 for ; Thu, 13 Nov 2003 00:31:19 +0100 (MET) Received: from localhost (sanaga.itu.ch [156.106.192.32]) by ties.itu.ch (8.12.9/8.12.9) with ESMTP id hACNVJQA031735 for ; Thu, 13 Nov 2003 00:31:19 +0100 (MET) Received: from 200.230.253.67 ( [200.230.253.67]) as user cardosow@ties.itu.ch by sanaga.itu.ch with HTTP; Thu, 13 Nov 2003 00:31:18 +0100 Message-ID: <1068679878.3fb2c2c6a67a2@sanaga.itu.ch> Date: Thu, 13 Nov 2003 00:31:18 +0100 From: wilson.cardoso@ties.itu.ch To: megaco@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.0 X-Originating-IP: 200.230.253.67 X-OriginalArrivalTime: 12 Nov 2003 23:31:21.0018 (UTC) FILETIME=[141C69A0:01C3A975] Content-Transfer-Encoding: 8bit Subject: [Megaco] Support to RFC 2833 Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Dear Colleagues, If a gateway has the DTMF detection Package implemented there is some reason to have the compliance with RFC 2833? _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Wed Nov 12 18:52:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18067 for ; Wed, 12 Nov 2003 18:52:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK4mK-0003mH-Jh for megaco-archive@odin.ietf.org; Wed, 12 Nov 2003 18:52:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hACNq4LH014517 for megaco-archive@odin.ietf.org; Wed, 12 Nov 2003 18:52:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK4mK-0003kQ-EI for megaco-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 18:52:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18033 for ; Wed, 12 Nov 2003 18:51:48 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AK4mF-0001K6-00 for megaco-web-archive@ietf.org; Wed, 12 Nov 2003 18:51:59 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AK4mF-0001K3-00 for megaco-web-archive@ietf.org; Wed, 12 Nov 2003 18:51:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK4mG-0003jO-TY; Wed, 12 Nov 2003 18:52:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK4Sp-0001JF-Kg for megaco@optimus.ietf.org; Wed, 12 Nov 2003 18:31:55 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17151 for ; Wed, 12 Nov 2003 18:31:41 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AK4Sm-0000zg-00 for megaco@ietf.org; Wed, 12 Nov 2003 18:31:52 -0500 Received: from protext02.itu.ch ([156.106.192.19] helo=itu.ch) by ietf-mx with esmtp (Exim 4.12) id 1AK4Sl-0000zL-00 for megaco@ietf.org; Wed, 12 Nov 2003 18:31:52 -0500 Received: from protext02.exadir.itu.ch ([156.106.192.19]) by itu.ch with Microsoft SMTPSVC(5.0.2195.6713); Thu, 13 Nov 2003 00:31:21 +0100 Received: From mail6.itu.ch ([156.106.192.22]) by protext02.exadir.itu.ch (WebShield SMTP v4.5 MR1a); id 106867988081; Thu, 13 Nov 2003 00:31:20 +0100 Received: from ties.itu.ch (root@ties.itu.ch [156.106.192.33]) by mail6.itu.ch (8.12.10/8.12.10) with ESMTP id hACNVJaR475667 for ; Thu, 13 Nov 2003 00:31:19 +0100 (MET) Received: from localhost (sanaga.itu.ch [156.106.192.32]) by ties.itu.ch (8.12.9/8.12.9) with ESMTP id hACNVJQA031735 for ; Thu, 13 Nov 2003 00:31:19 +0100 (MET) Received: from 200.230.253.67 ( [200.230.253.67]) as user cardosow@ties.itu.ch by sanaga.itu.ch with HTTP; Thu, 13 Nov 2003 00:31:18 +0100 Message-ID: <1068679878.3fb2c2c6a67a2@sanaga.itu.ch> Date: Thu, 13 Nov 2003 00:31:18 +0100 From: wilson.cardoso@ties.itu.ch To: megaco@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.0 X-Originating-IP: 200.230.253.67 X-OriginalArrivalTime: 12 Nov 2003 23:31:21.0018 (UTC) FILETIME=[141C69A0:01C3A975] Content-Transfer-Encoding: 8bit Subject: [Megaco] Support to RFC 2833 Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Dear Colleagues, If a gateway has the DTMF detection Package implemented there is some reason to have the compliance with RFC 2833? _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Wed Nov 12 19:52:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20222 for ; Wed, 12 Nov 2003 19:52:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK5iK-00075Q-FR; Wed, 12 Nov 2003 19:52:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK5i0-00074w-Tl for megaco@optimus.ietf.org; Wed, 12 Nov 2003 19:51:41 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20187 for ; Wed, 12 Nov 2003 19:51:29 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AK5hy-0002H2-00 for megaco@ietf.org; Wed, 12 Nov 2003 19:51:38 -0500 Received: from zcars0m9.nortelnetworks.com ([47.129.242.157]) by ietf-mx with esmtp (Exim 4.12) id 1AK5hy-0002Gr-00 for megaco@ietf.org; Wed, 12 Nov 2003 19:51:38 -0500 Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAD0osX19222; Wed, 12 Nov 2003 19:50:55 -0500 (EST) Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id W3H87WQX; Wed, 12 Nov 2003 19:50:55 -0500 Received: from nortelnetworks.com (acart05a.ca.nortel.com [47.130.16.167]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id SZW5NMXK; Wed, 12 Nov 2003 19:50:55 -0500 Message-ID: <3FB2D56E.3090303@nortelnetworks.com> Date: Wed, 12 Nov 2003 18:50:54 -0600 X-Sybari-Space: 00000000 00000000 00000000 00000000 From: Tom Taylor User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wilson.cardoso@ties.itu.ch CC: megaco@ietf.org Subject: Re: [Megaco] Support to RFC 2833 References: <1068679878.3fb2c2c6a67a2@sanaga.itu.ch> In-Reply-To: <1068679878.3fb2c2c6a67a2@sanaga.itu.ch> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Yes, I would say so. My view has always been that if the gateway has been told to detect DTMF digits, it must detect them whether they come in as audio coded samples, telephone events, or coded tones (the other payload type in RFC 2833. wilson.cardoso@ties.itu.ch wrote: > > Dear Colleagues, > > If a gateway has the DTMF detection Package implemented there is some reason to > have the compliance with RFC 2833? > > _______________________________________________ > 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 exim@www1.ietf.org Wed Nov 12 19:52:25 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20240 for ; Wed, 12 Nov 2003 19:52:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK5iP-00077D-Qu for megaco-archive@odin.ietf.org; Wed, 12 Nov 2003 19:52:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAD0q5MM027345 for megaco-archive@odin.ietf.org; Wed, 12 Nov 2003 19:52:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK5iP-00076y-KG for megaco-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 19:52:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20218 for ; Wed, 12 Nov 2003 19:51:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AK5iN-0002Hf-00 for megaco-web-archive@ietf.org; Wed, 12 Nov 2003 19:52:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AK5iN-0002Hc-00 for megaco-web-archive@ietf.org; Wed, 12 Nov 2003 19:52:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK5iK-00075Q-FR; Wed, 12 Nov 2003 19:52:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK5i0-00074w-Tl for megaco@optimus.ietf.org; Wed, 12 Nov 2003 19:51:41 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20187 for ; Wed, 12 Nov 2003 19:51:29 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AK5hy-0002H2-00 for megaco@ietf.org; Wed, 12 Nov 2003 19:51:38 -0500 Received: from zcars0m9.nortelnetworks.com ([47.129.242.157]) by ietf-mx with esmtp (Exim 4.12) id 1AK5hy-0002Gr-00 for megaco@ietf.org; Wed, 12 Nov 2003 19:51:38 -0500 Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAD0osX19222; Wed, 12 Nov 2003 19:50:55 -0500 (EST) Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id W3H87WQX; Wed, 12 Nov 2003 19:50:55 -0500 Received: from nortelnetworks.com (acart05a.ca.nortel.com [47.130.16.167]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id SZW5NMXK; Wed, 12 Nov 2003 19:50:55 -0500 Message-ID: <3FB2D56E.3090303@nortelnetworks.com> Date: Wed, 12 Nov 2003 18:50:54 -0600 X-Sybari-Space: 00000000 00000000 00000000 00000000 From: Tom Taylor User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wilson.cardoso@ties.itu.ch CC: megaco@ietf.org Subject: Re: [Megaco] Support to RFC 2833 References: <1068679878.3fb2c2c6a67a2@sanaga.itu.ch> In-Reply-To: <1068679878.3fb2c2c6a67a2@sanaga.itu.ch> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Yes, I would say so. My view has always been that if the gateway has been told to detect DTMF digits, it must detect them whether they come in as audio coded samples, telephone events, or coded tones (the other payload type in RFC 2833. wilson.cardoso@ties.itu.ch wrote: > > Dear Colleagues, > > If a gateway has the DTMF detection Package implemented there is some reason to > have the compliance with RFC 2833? > > _______________________________________________ > 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-admin@ietf.org Wed Nov 12 23:19:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26672 for ; Wed, 12 Nov 2003 23:19:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK8wg-00031n-59; Wed, 12 Nov 2003 23:19:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK8wb-00031Y-5Y for megaco@optimus.ietf.org; Wed, 12 Nov 2003 23:18:57 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26653 for ; Wed, 12 Nov 2003 23:18:44 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AK8wZ-0005Cx-00 for megaco@ietf.org; Wed, 12 Nov 2003 23:18:55 -0500 Received: from mail.utstar.com ([65.200.123.6]) by ietf-mx with esmtp (Exim 4.12) id 1AK8wY-0005Ct-00 for megaco@ietf.org; Wed, 12 Nov 2003 23:18:54 -0500 Received: from njtcbalal8 (bgp460182bgs.avenel01.nj.comcast.net [68.37.79.137]) by mail.utstar.com (8.11.3/8.11.3) with SMTP id hAD4KF018257; Wed, 12 Nov 2003 23:20:15 -0500 (EST) Reply-To: From: "Balasubramanian Pitchandi" To: "Aleksandr Ryabin" , Subject: RE: [Megaco] Megaco MIB: medGwyPropertyProfileTable property OIDs Date: Wed, 12 Nov 2003 23:18:42 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal In-Reply-To: <5.2.1.1.0.20031103161345.02936800@IL06EXM13.corp.mot.com> Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hello Aleks, There was another draft to this effect - package properties: http://sunsite.cnlab-switch.ch/ftp/mirror/internet-drafts/draft-pitchandi-me gaco-ringing-mib-00.txt But it has not been taken up as a WG activity. I dont know of any other package MIBs that are either being developed or being planned, unless the vendors are doing proprietary stuff. Thanks Bala PS: Sorry for the delay in responding. -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of Aleksandr Ryabin Sent: Monday, November 03, 2003 4:44 PM To: megaco@ietf.org Subject: [Megaco] Megaco MIB: medGwyPropertyProfileTable property OIDs Hi, In the latest MEGACO MIB draft http://www.ietf.org/internet-drafts/draft-ietf-megaco-mib-05.txt on page 22 in description of medGwyPropertyProfileTable there is a following statement: "-- (3) Each Property is defined as an Object Identifer in the various -- Package Mibs (like MEGACO-TONES-MIB etc)." I take it is a reference to expired "Tones MIB" draft, which can be found at: http://www.watersprings.org/pub/id/draft-doyle-megaco-tonesmib-00.txt Is there any other expired, or non-expired documents ever produced to be used for above MEGACO MIB table? Is there any work currently done, or planned to be done to define MIBs for any packages? Thanks Aleks _______________________________________________ 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 exim@www1.ietf.org Wed Nov 12 23:19:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26687 for ; Wed, 12 Nov 2003 23:19:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK8wi-00033A-9d for megaco-archive@odin.ietf.org; Wed, 12 Nov 2003 23:19:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAD4J42S011685 for megaco-archive@odin.ietf.org; Wed, 12 Nov 2003 23:19:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK8wi-00032O-18 for megaco-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 23:19:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26662 for ; Wed, 12 Nov 2003 23:18:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AK8wf-0005DF-00 for megaco-web-archive@ietf.org; Wed, 12 Nov 2003 23:19:02 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AK8wf-0005DC-00 for megaco-web-archive@ietf.org; Wed, 12 Nov 2003 23:19:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK8wg-00031n-59; Wed, 12 Nov 2003 23:19:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AK8wb-00031Y-5Y for megaco@optimus.ietf.org; Wed, 12 Nov 2003 23:18:57 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26653 for ; Wed, 12 Nov 2003 23:18:44 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AK8wZ-0005Cx-00 for megaco@ietf.org; Wed, 12 Nov 2003 23:18:55 -0500 Received: from mail.utstar.com ([65.200.123.6]) by ietf-mx with esmtp (Exim 4.12) id 1AK8wY-0005Ct-00 for megaco@ietf.org; Wed, 12 Nov 2003 23:18:54 -0500 Received: from njtcbalal8 (bgp460182bgs.avenel01.nj.comcast.net [68.37.79.137]) by mail.utstar.com (8.11.3/8.11.3) with SMTP id hAD4KF018257; Wed, 12 Nov 2003 23:20:15 -0500 (EST) Reply-To: From: "Balasubramanian Pitchandi" To: "Aleksandr Ryabin" , Subject: RE: [Megaco] Megaco MIB: medGwyPropertyProfileTable property OIDs Date: Wed, 12 Nov 2003 23:18:42 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal In-Reply-To: <5.2.1.1.0.20031103161345.02936800@IL06EXM13.corp.mot.com> Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello Aleks, There was another draft to this effect - package properties: http://sunsite.cnlab-switch.ch/ftp/mirror/internet-drafts/draft-pitchandi-me gaco-ringing-mib-00.txt But it has not been taken up as a WG activity. I dont know of any other package MIBs that are either being developed or being planned, unless the vendors are doing proprietary stuff. Thanks Bala PS: Sorry for the delay in responding. -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of Aleksandr Ryabin Sent: Monday, November 03, 2003 4:44 PM To: megaco@ietf.org Subject: [Megaco] Megaco MIB: medGwyPropertyProfileTable property OIDs Hi, In the latest MEGACO MIB draft http://www.ietf.org/internet-drafts/draft-ietf-megaco-mib-05.txt on page 22 in description of medGwyPropertyProfileTable there is a following statement: "-- (3) Each Property is defined as an Object Identifer in the various -- Package Mibs (like MEGACO-TONES-MIB etc)." I take it is a reference to expired "Tones MIB" draft, which can be found at: http://www.watersprings.org/pub/id/draft-doyle-megaco-tonesmib-00.txt Is there any other expired, or non-expired documents ever produced to be used for above MEGACO MIB table? Is there any work currently done, or planned to be done to define MIBs for any packages? Thanks Aleks _______________________________________________ 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-admin@ietf.org Thu Nov 13 20:21:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03192 for ; Thu, 13 Nov 2003 20:21:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKSdy-00006r-0O; Thu, 13 Nov 2003 20:21:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKSdi-000061-Vo for megaco@optimus.ietf.org; Thu, 13 Nov 2003 20:20:47 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03157 for ; Thu, 13 Nov 2003 20:20:35 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKSdg-0001ux-00 for megaco@ietf.org; Thu, 13 Nov 2003 20:20:44 -0500 Received: from law15-f60.law15.hotmail.com ([64.4.23.60] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 1AKSdg-0001uY-00 for megaco@ietf.org; Thu, 13 Nov 2003 20:20:44 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 13 Nov 2003 17:20:13 -0800 Received: from 210.21.224.54 by lw15fd.law15.hotmail.msn.com with HTTP; Fri, 14 Nov 2003 01:20:12 GMT X-Originating-IP: [210.21.224.54] X-Originating-Email: [juniperfu@hotmail.com] From: "å® ä»" To: juniperfu@hotmail.com, kboyle@nortelnetworks.com, JuLin.Wang@alcatel-sbell.com.cn, megaco@ietf.org Subject: RE: [Megaco] a problem about audit Date: Fri, 14 Nov 2003 09:20:12 +0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 14 Nov 2003 01:20:13.0124 (UTC) FILETIME=[73F67040:01C3AA4D] Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id UAA03158 Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable All, If MG found some connection has some problem, And How can MG notify = the=20 MGC? thanks! Mark >From: "=E5=AE =E4=BB" >To: kboyle@nortelnetworks.com, JuLin.Wang@alcatel-sbell.com.cn, =20 >megaco@ietf.org >Subject: RE: [Megaco] a problem about audit >Date: Tue, 11 Nov 2003 09:20:39 +0800 > >So, If MGC can't audit all the context of the MG When MGC switchover, Ho= w=20 >can MGC keep the coherence in the context and termination with MG? > > >>From: "Kevin Boyle" >>To: FND-AD Wang JuLin , ? ?=20 >>, megaco@ietf.org >>Subject: RE: [Megaco] a problem about audit >>Date: Mon, 10 Nov 2003 10:03:38 -0500 >> >>The question was how to return all the contexts in existence on the MG.= =20 >>So, >>my answer still stands -- there's not a lot that can be done to overcom= e=20 >>the >>MTU limitation in UDP. TCP segments its messages based on the MTU size= ,=20 >>so >>there's not a problem there. >> >>Kevin >> >>-----Original Message----- >>From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] >>Sent: Monday, November 10, 2003 12:46 AM >>To: Boyle, Kevin [NCRTP:3Z40:EXCH]; ? ?; megaco@ietf.org >>Subject: RE: [Megaco] a problem about audit >> >>IMO,It depends on the MTU size. If the message larger than it, gateway = can >>trigger the reply message with error code 533 "RSP EXCEEDS MAX TRANSPOR= T=20 >>PDU >>SIZE" . >> >> >>-----Original Message----- >> >>From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] >> >>Sent: Monday, November 10, 2003 11:26 AM >> >>To: =E5=AE =E4=BB; megaco@ietf.org >> >>Subject: RE: [Megaco] a problem about audit >> >> >> >> >> >>If you use TCP, there really isn't a limit to the message length, >> >>since the transport will segment the message. >> >> >> >>For UDP, I can suggest using short form tokens and removing all >> >>non-mandatory whitespace. This will help keep the message size down. >> >>Other than that, at this moment, there's not a lot you can do about >> >>the message size. >> >> >> >>Kevin >> >> >> >>-----Original Message----- >> >>From: =E5=AE =E4=BB [mailto:juniperfu@hotmail.com] >> >>Sent: Sunday, November 09, 2003 8:01 PM >> >>To: megaco@ietf.org >> >>Subject: [Megaco] a problem about audit >> >> >> >>All, >> >>When MGC restart or HA, Maybe it need audit the context and >> >>termination of MG, and it can send the command Context =3D * { >> >>AuditValue=3D ROOT {Audit { } } and the MG should return Context =3D= 100 { >> >>AuditValue=3D TermA, TermB } Context =3D 200 { AuditValue=3D TermC, = TermD } >> >>Context =3D 300 { AuditValue=3D TermE, TermF } And my problem is if = the MG >> >>has a lot of context and a >> >megaco message >> >>can't include them, So how do the mg return all its context, thanks! >> >> >> >>juniper >> >> >> >>_________________________________________________________________ >> >>Add photos to your messages with MSN 8. Get 2 months FREE*. >> >>http://join.msn.com/?page=3Dfeatures/featuredemail >> >> >> >> >> >>_______________________________________________ >> >>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 > >_________________________________________________________________ >Add photos to your e-mail with MSN 8. Get 2 months FREE*.=20 >http://join.msn.com/?page=3Dfeatures/featuredemail > > >_______________________________________________ >Megaco mailing list >Megaco@ietf.org >https://www1.ietf.org/mailman/listinfo/megaco _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE*=20 http://join.msn.com/?page=3Dfeatures/junkmail _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Thu Nov 13 20:21:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03208 for ; Thu, 13 Nov 2003 20:21:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKSe1-00007Z-D1 for megaco-archive@odin.ietf.org; Thu, 13 Nov 2003 20:21:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAE1L5QT000459 for megaco-archive@odin.ietf.org; Thu, 13 Nov 2003 20:21:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKSe1-00007K-7m for megaco-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 20:21:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03163 for ; Thu, 13 Nov 2003 20:20:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKSdy-0001vA-00 for megaco-web-archive@ietf.org; Thu, 13 Nov 2003 20:21:02 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKSdy-0001v6-00 for megaco-web-archive@ietf.org; Thu, 13 Nov 2003 20:21:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKSdy-00006r-0O; Thu, 13 Nov 2003 20:21:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKSdi-000061-Vo for megaco@optimus.ietf.org; Thu, 13 Nov 2003 20:20:47 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03157 for ; Thu, 13 Nov 2003 20:20:35 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKSdg-0001ux-00 for megaco@ietf.org; Thu, 13 Nov 2003 20:20:44 -0500 Received: from law15-f60.law15.hotmail.com ([64.4.23.60] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 1AKSdg-0001uY-00 for megaco@ietf.org; Thu, 13 Nov 2003 20:20:44 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 13 Nov 2003 17:20:13 -0800 Received: from 210.21.224.54 by lw15fd.law15.hotmail.msn.com with HTTP; Fri, 14 Nov 2003 01:20:12 GMT X-Originating-IP: [210.21.224.54] X-Originating-Email: [juniperfu@hotmail.com] From: "å® ä»" To: juniperfu@hotmail.com, kboyle@nortelnetworks.com, JuLin.Wang@alcatel-sbell.com.cn, megaco@ietf.org Subject: RE: [Megaco] a problem about audit Date: Fri, 14 Nov 2003 09:20:12 +0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 14 Nov 2003 01:20:13.0124 (UTC) FILETIME=[73F67040:01C3AA4D] X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id UAA03158 Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable All, If MG found some connection has some problem, And How can MG notify = the=20 MGC? thanks! Mark >From: "=E5=AE =E4=BB" >To: kboyle@nortelnetworks.com, JuLin.Wang@alcatel-sbell.com.cn, =20 >megaco@ietf.org >Subject: RE: [Megaco] a problem about audit >Date: Tue, 11 Nov 2003 09:20:39 +0800 > >So, If MGC can't audit all the context of the MG When MGC switchover, Ho= w=20 >can MGC keep the coherence in the context and termination with MG? > > >>From: "Kevin Boyle" >>To: FND-AD Wang JuLin , ? ?=20 >>, megaco@ietf.org >>Subject: RE: [Megaco] a problem about audit >>Date: Mon, 10 Nov 2003 10:03:38 -0500 >> >>The question was how to return all the contexts in existence on the MG.= =20 >>So, >>my answer still stands -- there's not a lot that can be done to overcom= e=20 >>the >>MTU limitation in UDP. TCP segments its messages based on the MTU size= ,=20 >>so >>there's not a problem there. >> >>Kevin >> >>-----Original Message----- >>From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] >>Sent: Monday, November 10, 2003 12:46 AM >>To: Boyle, Kevin [NCRTP:3Z40:EXCH]; ? ?; megaco@ietf.org >>Subject: RE: [Megaco] a problem about audit >> >>IMO,It depends on the MTU size. If the message larger than it, gateway = can >>trigger the reply message with error code 533 "RSP EXCEEDS MAX TRANSPOR= T=20 >>PDU >>SIZE" . >> >> >>-----Original Message----- >> >>From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] >> >>Sent: Monday, November 10, 2003 11:26 AM >> >>To: =E5=AE =E4=BB; megaco@ietf.org >> >>Subject: RE: [Megaco] a problem about audit >> >> >> >> >> >>If you use TCP, there really isn't a limit to the message length, >> >>since the transport will segment the message. >> >> >> >>For UDP, I can suggest using short form tokens and removing all >> >>non-mandatory whitespace. This will help keep the message size down. >> >>Other than that, at this moment, there's not a lot you can do about >> >>the message size. >> >> >> >>Kevin >> >> >> >>-----Original Message----- >> >>From: =E5=AE =E4=BB [mailto:juniperfu@hotmail.com] >> >>Sent: Sunday, November 09, 2003 8:01 PM >> >>To: megaco@ietf.org >> >>Subject: [Megaco] a problem about audit >> >> >> >>All, >> >>When MGC restart or HA, Maybe it need audit the context and >> >>termination of MG, and it can send the command Context =3D * { >> >>AuditValue=3D ROOT {Audit { } } and the MG should return Context =3D= 100 { >> >>AuditValue=3D TermA, TermB } Context =3D 200 { AuditValue=3D TermC, = TermD } >> >>Context =3D 300 { AuditValue=3D TermE, TermF } And my problem is if = the MG >> >>has a lot of context and a >> >megaco message >> >>can't include them, So how do the mg return all its context, thanks! >> >> >> >>juniper >> >> >> >>_________________________________________________________________ >> >>Add photos to your messages with MSN 8. Get 2 months FREE*. >> >>http://join.msn.com/?page=3Dfeatures/featuredemail >> >> >> >> >> >>_______________________________________________ >> >>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 > >_________________________________________________________________ >Add photos to your e-mail with MSN 8. Get 2 months FREE*.=20 >http://join.msn.com/?page=3Dfeatures/featuredemail > > >_______________________________________________ >Megaco mailing list >Megaco@ietf.org >https://www1.ietf.org/mailman/listinfo/megaco _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE*=20 http://join.msn.com/?page=3Dfeatures/junkmail _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Thu Nov 13 22:49:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09828 for ; Thu, 13 Nov 2003 22:49:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKUxB-000328-Dg; Thu, 13 Nov 2003 22:49:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKUwO-00030g-Ci for megaco@optimus.ietf.org; Thu, 13 Nov 2003 22:48:12 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09788 for ; Thu, 13 Nov 2003 22:47:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKUwK-0004fq-00 for megaco@ietf.org; Thu, 13 Nov 2003 22:48:08 -0500 Received: from [210.21.224.29] (helo=szsmtp.utstar.com.cn) by ietf-mx with esmtp (Exim 4.12) id 1AKUwH-0004fi-00 for megaco@ietf.org; Thu, 13 Nov 2003 22:48:05 -0500 Received: from sznssrasool ([172.19.17.174]) by szsmtp.utstar.com.cn (8.11.6/8.11.1) with SMTP id hAE3lIF09884 for ; Fri, 14 Nov 2003 11:47:18 +0800 Message-ID: <003001c3aa61$fff39910$c1a110ac@cn.utstar.com> From: "Rasool Wani" To: Date: Fri, 14 Nov 2003 11:47:17 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002D_01C3AAA5.0E017C50" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [Megaco] Alternate Properties in Annex C.11 SDP equivalent and C.1---etc properties Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_002D_01C3AAA5.0E017C50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable hi all, can any body help me to understand the following. 1. what is the reason of having alternate properties in = AnnexC-C.1------- etc and Annex C-C.11 SDP equivalent properties.=20 For e.g.. a=3DsilenceSupp in sdp and Silencesupp(1008) in C.1. 2. Shall protocol support the both the alternatives to convey the Media = related information.if yes, then in which context two methods are = differentiated. Thanks, Rasool Wani ------=_NextPart_000_002D_01C3AAA5.0E017C50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
hi all,
can any body help me to understand the = following.
1. what is the reason of having alternate properties = in=20 AnnexC-C.1------- etc and  Annex C-C.11 SDP equivalent=20 properties. 
For e.g.. a=3DsilenceSupp  in sdp and=20 Silencesupp(1008) in C.1.
2. Shall protocol support the both the alternatives to convey the = Media=20 related information.if yes, then in which context two methods are=20 differentiated.
Thanks,
Rasool Wani
 

------=_NextPart_000_002D_01C3AAA5.0E017C50-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Thu Nov 13 22:49:25 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09849 for ; Thu, 13 Nov 2003 22:49:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKUxG-00033f-A9 for megaco-archive@odin.ietf.org; Thu, 13 Nov 2003 22:49:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAE3n6CC011751 for megaco-archive@odin.ietf.org; Thu, 13 Nov 2003 22:49:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKUxG-00033S-6k for megaco-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 22:49:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09825 for ; Thu, 13 Nov 2003 22:48:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKUxC-0004gP-00 for megaco-web-archive@ietf.org; Thu, 13 Nov 2003 22:49:02 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKUxC-0004gM-00 for megaco-web-archive@ietf.org; Thu, 13 Nov 2003 22:49:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKUxB-000328-Dg; Thu, 13 Nov 2003 22:49:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKUwO-00030g-Ci for megaco@optimus.ietf.org; Thu, 13 Nov 2003 22:48:12 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09788 for ; Thu, 13 Nov 2003 22:47:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKUwK-0004fq-00 for megaco@ietf.org; Thu, 13 Nov 2003 22:48:08 -0500 Received: from [210.21.224.29] (helo=szsmtp.utstar.com.cn) by ietf-mx with esmtp (Exim 4.12) id 1AKUwH-0004fi-00 for megaco@ietf.org; Thu, 13 Nov 2003 22:48:05 -0500 Received: from sznssrasool ([172.19.17.174]) by szsmtp.utstar.com.cn (8.11.6/8.11.1) with SMTP id hAE3lIF09884 for ; Fri, 14 Nov 2003 11:47:18 +0800 Message-ID: <003001c3aa61$fff39910$c1a110ac@cn.utstar.com> From: "Rasool Wani" To: Date: Fri, 14 Nov 2003 11:47:17 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002D_01C3AAA5.0E017C50" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [Megaco] Alternate Properties in Annex C.11 SDP equivalent and C.1---etc properties Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_002D_01C3AAA5.0E017C50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable hi all, can any body help me to understand the following. 1. what is the reason of having alternate properties in = AnnexC-C.1------- etc and Annex C-C.11 SDP equivalent properties.=20 For e.g.. a=3DsilenceSupp in sdp and Silencesupp(1008) in C.1. 2. Shall protocol support the both the alternatives to convey the Media = related information.if yes, then in which context two methods are = differentiated. Thanks, Rasool Wani ------=_NextPart_000_002D_01C3AAA5.0E017C50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
hi all,
can any body help me to understand the = following.
1. what is the reason of having alternate properties = in=20 AnnexC-C.1------- etc and  Annex C-C.11 SDP equivalent=20 properties. 
For e.g.. a=3DsilenceSupp  in sdp and=20 Silencesupp(1008) in C.1.
2. Shall protocol support the both the alternatives to convey the = Media=20 related information.if yes, then in which context two methods are=20 differentiated.
Thanks,
Rasool Wani
 

------=_NextPart_000_002D_01C3AAA5.0E017C50-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Fri Nov 14 04:04:30 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02279 for ; Fri, 14 Nov 2003 04:04:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKZcY-0005e8-7O; Fri, 14 Nov 2003 03:48:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKZc2-0005cw-Ek for megaco@optimus.ietf.org; Fri, 14 Nov 2003 03:47:30 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01739 for ; Fri, 14 Nov 2003 03:47:17 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKZbz-0001CE-00 for megaco@ietf.org; Fri, 14 Nov 2003 03:47:27 -0500 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AKZbz-0001Bn-00 for megaco@ietf.org; Fri, 14 Nov 2003 03:47:27 -0500 Received: from cisco.com (171.71.177.237) by sj-iport-2.cisco.com with ESMTP; 14 Nov 2003 00:49:33 -0800 Received: from sampathkw2k02 (sjc-vpn3-201.cisco.com [10.21.64.201]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAE8kuAt026465; Fri, 14 Nov 2003 00:46:56 -0800 (PST) From: "Sampath Komanduri" To: "'Harry Suede'" , Subject: RE: [Megaco] g/sc Notification during Subtract Date: Fri, 14 Nov 2003 00:46:50 -0800 Message-ID: <000c01c3aa8b$dbdac6f0$210110ac@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <20031112110628.2367.qmail@email.com> Importance: Normal Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi Harry, Assuming that there *wasn't* an empty events descriptor in the Subtract, MG should send a g/sc event notification with method set to "NC" (Not completed, other cause). I don't find anything specified in the protocol with respect to special handling of g/sc for Subtract. Therefore, normal handling (notify MGC if Signal playout was aborted for any reason) of g/sc should apply. Thanks, Sampath -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of Harry Suede Sent: Wednesday, November 12, 2003 3:06 AM To: megaco@ietf.org Subject: [Megaco] g/sc Notification during Subtract Hi List, A signal is being applied on a termination in Non-NULL context. Then MGC sends Subtract command on the termination. The MG will stop the signal during processing of Subtract command. Should MG send the Notify command for g/sc event with "NC" (Not completed, other cause) towards MGC? I think , since all the active descriptors shall be reset during Subtract processing, so MG should **not** send g/sc notification as Events descriptor doesn't contain g/sc at that point of time. Pls. respond. Thanks Harry. -- __________________________________________________________ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup Search Smarter - get the new eXact Search Bar for free! http://www.exactsearchbar.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 exim@www1.ietf.org Fri Nov 14 04:04:32 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02294 for ; Fri, 14 Nov 2003 04:04:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKZsE-0006ag-UU for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 04:04:15 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAE94EeU025321 for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 04:04:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKZsE-0006aC-Lo for megaco-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 04:04:14 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02243 for ; Fri, 14 Nov 2003 04:04:01 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKZsB-0001RF-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 04:04:11 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKZsB-0001RC-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 04:04:11 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKZcY-0005e8-7O; Fri, 14 Nov 2003 03:48:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKZc2-0005cw-Ek for megaco@optimus.ietf.org; Fri, 14 Nov 2003 03:47:30 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01739 for ; Fri, 14 Nov 2003 03:47:17 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKZbz-0001CE-00 for megaco@ietf.org; Fri, 14 Nov 2003 03:47:27 -0500 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AKZbz-0001Bn-00 for megaco@ietf.org; Fri, 14 Nov 2003 03:47:27 -0500 Received: from cisco.com (171.71.177.237) by sj-iport-2.cisco.com with ESMTP; 14 Nov 2003 00:49:33 -0800 Received: from sampathkw2k02 (sjc-vpn3-201.cisco.com [10.21.64.201]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAE8kuAt026465; Fri, 14 Nov 2003 00:46:56 -0800 (PST) From: "Sampath Komanduri" To: "'Harry Suede'" , Subject: RE: [Megaco] g/sc Notification during Subtract Date: Fri, 14 Nov 2003 00:46:50 -0800 Message-ID: <000c01c3aa8b$dbdac6f0$210110ac@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <20031112110628.2367.qmail@email.com> Importance: Normal Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Harry, Assuming that there *wasn't* an empty events descriptor in the Subtract, MG should send a g/sc event notification with method set to "NC" (Not completed, other cause). I don't find anything specified in the protocol with respect to special handling of g/sc for Subtract. Therefore, normal handling (notify MGC if Signal playout was aborted for any reason) of g/sc should apply. Thanks, Sampath -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of Harry Suede Sent: Wednesday, November 12, 2003 3:06 AM To: megaco@ietf.org Subject: [Megaco] g/sc Notification during Subtract Hi List, A signal is being applied on a termination in Non-NULL context. Then MGC sends Subtract command on the termination. The MG will stop the signal during processing of Subtract command. Should MG send the Notify command for g/sc event with "NC" (Not completed, other cause) towards MGC? I think , since all the active descriptors shall be reset during Subtract processing, so MG should **not** send g/sc notification as Events descriptor doesn't contain g/sc at that point of time. Pls. respond. Thanks Harry. -- __________________________________________________________ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup Search Smarter - get the new eXact Search Bar for free! http://www.exactsearchbar.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-admin@ietf.org Fri Nov 14 08:22:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09313 for ; Fri, 14 Nov 2003 08:22:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKdti-000645-15; Fri, 14 Nov 2003 08:22:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKdtI-00063q-8X for megaco@optimus.ietf.org; Fri, 14 Nov 2003 08:21:36 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09294 for ; Fri, 14 Nov 2003 08:21:23 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKdtH-0004rx-00 for megaco@ietf.org; Fri, 14 Nov 2003 08:21:35 -0500 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AKdtG-0004rh-00 for megaco@ietf.org; Fri, 14 Nov 2003 08:21:34 -0500 Received: from cisco.com (171.71.177.254) by sj-iport-2.cisco.com with ESMTP; 14 Nov 2003 05:23:41 -0800 Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17]) by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id hAEDL2w5027760 for ; Fri, 14 Nov 2003 05:21:02 -0800 (PST) Received: from cisco.com (che-vpn-cluster-2-65.cisco.com [10.86.242.65]) by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AOF76537; Fri, 14 Nov 2003 05:21:01 -0800 (PST) Message-ID: <3FB4D6BB.8000206@cisco.com> Date: Fri, 14 Nov 2003 08:20:59 -0500 From: Sundar Bettadahalli Organization: Cisco Systems User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 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 Content-Transfer-Encoding: 7bit Subject: [Megaco] Signals/Events and Move Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit I understand that statistics must be preserved across contexts when a termination is "moved" from one context to another. But must signals and events also be preserved across a Move ? Or must they be removed by the MGC before "moving" the termination. Any information/pointers on this will be greatly appreciated. Thanks in advance, Sundar _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Fri Nov 14 08:22:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09328 for ; Fri, 14 Nov 2003 08:22:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKdtm-00067N-1p for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 08:22:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAEDM5lS023501 for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 08:22:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKdtl-00066l-Qk for megaco-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 08:22:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09305 for ; Fri, 14 Nov 2003 08:21:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKdtk-0004sA-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 08:22:04 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKdtk-0004s7-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 08:22:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKdti-000645-15; Fri, 14 Nov 2003 08:22:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKdtI-00063q-8X for megaco@optimus.ietf.org; Fri, 14 Nov 2003 08:21:36 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09294 for ; Fri, 14 Nov 2003 08:21:23 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKdtH-0004rx-00 for megaco@ietf.org; Fri, 14 Nov 2003 08:21:35 -0500 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AKdtG-0004rh-00 for megaco@ietf.org; Fri, 14 Nov 2003 08:21:34 -0500 Received: from cisco.com (171.71.177.254) by sj-iport-2.cisco.com with ESMTP; 14 Nov 2003 05:23:41 -0800 Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17]) by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id hAEDL2w5027760 for ; Fri, 14 Nov 2003 05:21:02 -0800 (PST) Received: from cisco.com (che-vpn-cluster-2-65.cisco.com [10.86.242.65]) by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AOF76537; Fri, 14 Nov 2003 05:21:01 -0800 (PST) Message-ID: <3FB4D6BB.8000206@cisco.com> Date: Fri, 14 Nov 2003 08:20:59 -0500 From: Sundar Bettadahalli Organization: Cisco Systems User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 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 Content-Transfer-Encoding: 7bit Subject: [Megaco] Signals/Events and Move Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I understand that statistics must be preserved across contexts when a termination is "moved" from one context to another. But must signals and events also be preserved across a Move ? Or must they be removed by the MGC before "moving" the termination. Any information/pointers on this will be greatly appreciated. Thanks in advance, Sundar _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Fri Nov 14 10:13:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14062 for ; Fri, 14 Nov 2003 10:13:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKfd7-0004v6-RU; Fri, 14 Nov 2003 10:13:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKfcr-0004uG-7O for megaco@optimus.ietf.org; Fri, 14 Nov 2003 10:12:45 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13791 for ; Fri, 14 Nov 2003 10:12:30 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKfco-0006Zc-00 for megaco@ietf.org; Fri, 14 Nov 2003 10:12:42 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AKfcn-0006WX-00 for megaco@ietf.org; Fri, 14 Nov 2003 10:12:42 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAEFC4m22336 for ; Fri, 14 Nov 2003 10:12:04 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 14 Nov 2003 10:12:04 -0500 Message-ID: From: "Kevin Boyle" To: Sundar Bettadahalli , megaco@ietf.org Subject: RE: [Megaco] Signals/Events and Move Date: Fri, 14 Nov 2003 10:12:02 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Everything is maintained during a Move command, including Signals and Events. This is what makes Move different from a Subtract/Add. Kevin -----Original Message----- From: Sundar Bettadahalli [mailto:sundarbs@cisco.com] Sent: Friday, November 14, 2003 8:21 AM To: megaco@ietf.org Subject: [Megaco] Signals/Events and Move I understand that statistics must be preserved across contexts when a termination is "moved" from one context to another. But must signals and events also be preserved across a Move ? Or must they be removed by the MGC before "moving" the termination. Any information/pointers on this will be greatly appreciated. Thanks in advance, Sundar _______________________________________________ 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 exim@www1.ietf.org Fri Nov 14 10:13:27 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14105 for ; Fri, 14 Nov 2003 10:13:27 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKfdD-0004x8-TQ for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 10:13:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAEFD7Nl019032 for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 10:13:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKfdD-0004wt-NN for megaco-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 10:13:07 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13916 for ; Fri, 14 Nov 2003 10:12:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKfdB-0006bw-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 10:13:05 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKfdB-0006bt-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 10:13:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKfd7-0004v6-RU; Fri, 14 Nov 2003 10:13:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKfcr-0004uG-7O for megaco@optimus.ietf.org; Fri, 14 Nov 2003 10:12:45 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13791 for ; Fri, 14 Nov 2003 10:12:30 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKfco-0006Zc-00 for megaco@ietf.org; Fri, 14 Nov 2003 10:12:42 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AKfcn-0006WX-00 for megaco@ietf.org; Fri, 14 Nov 2003 10:12:42 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAEFC4m22336 for ; Fri, 14 Nov 2003 10:12:04 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 14 Nov 2003 10:12:04 -0500 Message-ID: From: "Kevin Boyle" To: Sundar Bettadahalli , megaco@ietf.org Subject: RE: [Megaco] Signals/Events and Move Date: Fri, 14 Nov 2003 10:12:02 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Everything is maintained during a Move command, including Signals and Events. This is what makes Move different from a Subtract/Add. Kevin -----Original Message----- From: Sundar Bettadahalli [mailto:sundarbs@cisco.com] Sent: Friday, November 14, 2003 8:21 AM To: megaco@ietf.org Subject: [Megaco] Signals/Events and Move I understand that statistics must be preserved across contexts when a termination is "moved" from one context to another. But must signals and events also be preserved across a Move ? Or must they be removed by the MGC before "moving" the termination. Any information/pointers on this will be greatly appreciated. Thanks in advance, Sundar _______________________________________________ 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-admin@ietf.org Fri Nov 14 10:15:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14486 for ; Fri, 14 Nov 2003 10:15:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKff5-0005H6-9G; Fri, 14 Nov 2003 10:15:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKfe4-00057G-AU for megaco@optimus.ietf.org; Fri, 14 Nov 2003 10:14:00 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14180 for ; Fri, 14 Nov 2003 10:13:45 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKfe2-0006eN-00 for megaco@ietf.org; Fri, 14 Nov 2003 10:13:58 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AKfe1-0006co-00 for megaco@ietf.org; Fri, 14 Nov 2003 10:13:57 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAEFDQm22450 for ; Fri, 14 Nov 2003 10:13:26 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 14 Nov 2003 10:13:26 -0500 Message-ID: From: "Kevin Boyle" To: Rasool Wani , megaco@ietf.org Subject: RE: [Megaco] Alternate Properties in Annex C.11 SDP equivalent a nd C.1---etc properties Date: Fri, 14 Nov 2003 10:13:24 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , SDP is used with ABNF encoding. Annex C is used with ASN.1 coding. Kevin _____ From: Rasool Wani [mailto:rasool.wani@utstar.com] Sent: Thursday, November 13, 2003 10:47 PM To: megaco@ietf.org Subject: [Megaco] Alternate Properties in Annex C.11 SDP equivalent and C.1---etc properties hi all, can any body help me to understand the following. 1. what is the reason of having alternate properties in AnnexC-C.1------- etc and Annex C-C.11 SDP equivalent properties. For e.g.. a=silenceSupp in sdp and Silencesupp(1008) in C.1. 2. Shall protocol support the both the alternatives to convey the Media related information.if yes, then in which context two methods are differentiated. Thanks, Rasool Wani _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Fri Nov 14 10:15:27 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14508 for ; Fri, 14 Nov 2003 10:15:27 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKffB-0005Io-2B for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 10:15:11 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAEFF9A7020376 for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 10:15:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKffA-0005IZ-Qz for megaco-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 10:15:08 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14408 for ; Fri, 14 Nov 2003 10:14:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKff8-0006hz-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 10:15:06 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKff8-0006hw-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 10:15:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKff5-0005H6-9G; Fri, 14 Nov 2003 10:15:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKfe4-00057G-AU for megaco@optimus.ietf.org; Fri, 14 Nov 2003 10:14:00 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14180 for ; Fri, 14 Nov 2003 10:13:45 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKfe2-0006eN-00 for megaco@ietf.org; Fri, 14 Nov 2003 10:13:58 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AKfe1-0006co-00 for megaco@ietf.org; Fri, 14 Nov 2003 10:13:57 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAEFDQm22450 for ; Fri, 14 Nov 2003 10:13:26 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 14 Nov 2003 10:13:26 -0500 Message-ID: From: "Kevin Boyle" To: Rasool Wani , megaco@ietf.org Subject: RE: [Megaco] Alternate Properties in Annex C.11 SDP equivalent a nd C.1---etc properties Date: Fri, 14 Nov 2003 10:13:24 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , SDP is used with ABNF encoding. Annex C is used with ASN.1 coding. Kevin _____ From: Rasool Wani [mailto:rasool.wani@utstar.com] Sent: Thursday, November 13, 2003 10:47 PM To: megaco@ietf.org Subject: [Megaco] Alternate Properties in Annex C.11 SDP equivalent and C.1---etc properties hi all, can any body help me to understand the following. 1. what is the reason of having alternate properties in AnnexC-C.1------- etc and Annex C-C.11 SDP equivalent properties. For e.g.. a=silenceSupp in sdp and Silencesupp(1008) in C.1. 2. Shall protocol support the both the alternatives to convey the Media related information.if yes, then in which context two methods are differentiated. Thanks, Rasool Wani _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Fri Nov 14 10:16:19 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14647 for ; Fri, 14 Nov 2003 10:16:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKfg2-0005UY-2u; Fri, 14 Nov 2003 10:16:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKffc-0005TZ-56 for megaco@optimus.ietf.org; Fri, 14 Nov 2003 10:15:40 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14482 for ; Fri, 14 Nov 2003 10:15:21 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKffa-0006j4-00 for megaco@ietf.org; Fri, 14 Nov 2003 10:15:34 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AKffU-0006hI-00 for megaco@ietf.org; Fri, 14 Nov 2003 10:15:33 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAEFEtA01687 for ; Fri, 14 Nov 2003 10:14:55 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 14 Nov 2003 10:14:55 -0500 Message-ID: From: "Kevin Boyle" To: å® ä» , JuLin.Wang@alcatel-sbell.com.cn, megaco@ietf.org Subject: RE: [Megaco] a problem about audit Date: Fri, 14 Nov 2003 10:14:53 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , If the MGC has sent the netfail event in the Events descriptor, the MG can utilize that. The MG could also send a ServiceChange command. It would depend upon the situation and the current descriptor values of the termination in question. Kevin -----Original Message----- From: å® ä» [mailto:juniperfu@hotmail.com] Sent: Thursday, November 13, 2003 8:20 PM To: juniperfu@hotmail.com; Boyle, Kevin [NCRTP:3Z40:EXCH]; JuLin.Wang@alcatel-sbell.com.cn; megaco@ietf.org Subject: RE: [Megaco] a problem about audit All, If MG found some connection has some problem, And How can MG notify the MGC? thanks! Mark >From: "å® ä»" >To: kboyle@nortelnetworks.com, JuLin.Wang@alcatel-sbell.com.cn, >megaco@ietf.org >Subject: RE: [Megaco] a problem about audit >Date: Tue, 11 Nov 2003 09:20:39 +0800 > >So, If MGC can't audit all the context of the MG When MGC switchover, >How can MGC keep the coherence in the context and termination with MG? > > >>From: "Kevin Boyle" >>To: FND-AD Wang JuLin , ? ? >>, megaco@ietf.org >>Subject: RE: [Megaco] a problem about audit >>Date: Mon, 10 Nov 2003 10:03:38 -0500 >> >>The question was how to return all the contexts in existence on the MG. >>So, >>my answer still stands -- there's not a lot that can be done to >>overcome the MTU limitation in UDP. TCP segments its messages based >>on the MTU size, so there's not a problem there. >> >>Kevin >> >>-----Original Message----- >>From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] >>Sent: Monday, November 10, 2003 12:46 AM >>To: Boyle, Kevin [NCRTP:3Z40:EXCH]; ? ?; megaco@ietf.org >>Subject: RE: [Megaco] a problem about audit >> >>IMO,It depends on the MTU size. If the message larger than it, gateway >>can trigger the reply message with error code 533 "RSP EXCEEDS MAX >>TRANSPORT PDU SIZE" . >> >> >>-----Original Message----- >> >>From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] >> >>Sent: Monday, November 10, 2003 11:26 AM >> >>To: å® ä»; megaco@ietf.org >> >>Subject: RE: [Megaco] a problem about audit >> >> >> >> >> >>If you use TCP, there really isn't a limit to the message length, >> >>since the transport will segment the message. >> >> >> >>For UDP, I can suggest using short form tokens and removing all >> >>non-mandatory whitespace. This will help keep the message size down. >> >>Other than that, at this moment, there's not a lot you can do about >> >>the message size. >> >> >> >>Kevin >> >> >> >>-----Original Message----- >> >>From: å® ä» [mailto:juniperfu@hotmail.com] >> >>Sent: Sunday, November 09, 2003 8:01 PM >> >>To: megaco@ietf.org >> >>Subject: [Megaco] a problem about audit >> >> >> >>All, >> >>When MGC restart or HA, Maybe it need audit the context and >> >>termination of MG, and it can send the command Context = * { >> >>AuditValue= ROOT {Audit { } } and the MG should return Context = >> >>100 { AuditValue= TermA, TermB } Context = 200 { AuditValue= TermC, >> >>TermD } Context = 300 { AuditValue= TermE, TermF } And my problem >> >>is if the MG has a lot of context and a >> >megaco message >> >>can't include them, So how do the mg return all its context, thanks! >> >> >> >>juniper >> >> >> >>_________________________________________________________________ >> >>Add photos to your messages with MSN 8. Get 2 months FREE*. >> >>http://join.msn.com/?page=features/featuredemail >> >> >> >> >> >>_______________________________________________ >> >>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 > >_________________________________________________________________ >Add photos to your e-mail with MSN 8. Get 2 months FREE*. >http://join.msn.com/?page=features/featuredemail > > >_______________________________________________ >Megaco mailing list >Megaco@ietf.org >https://www1.ietf.org/mailman/listinfo/megaco _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Fri Nov 14 10:16:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14667 for ; Fri, 14 Nov 2003 10:16:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKfg3-0005XZ-Hu for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 10:16:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAEFG3ZO021291 for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 10:16:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKfg3-0005XK-Dw for megaco-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 10:16:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14582 for ; Fri, 14 Nov 2003 10:15:48 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKfg1-0006m6-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 10:16:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKfg0-0006m3-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 10:16:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKfg2-0005UY-2u; Fri, 14 Nov 2003 10:16:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKffc-0005TZ-56 for megaco@optimus.ietf.org; Fri, 14 Nov 2003 10:15:40 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14482 for ; Fri, 14 Nov 2003 10:15:21 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKffa-0006j4-00 for megaco@ietf.org; Fri, 14 Nov 2003 10:15:34 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AKffU-0006hI-00 for megaco@ietf.org; Fri, 14 Nov 2003 10:15:33 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAEFEtA01687 for ; Fri, 14 Nov 2003 10:14:55 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 14 Nov 2003 10:14:55 -0500 Message-ID: From: "Kevin Boyle" To: å® ä» , JuLin.Wang@alcatel-sbell.com.cn, megaco@ietf.org Subject: RE: [Megaco] a problem about audit Date: Fri, 14 Nov 2003 10:14:53 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , If the MGC has sent the netfail event in the Events descriptor, the MG can utilize that. The MG could also send a ServiceChange command. It would depend upon the situation and the current descriptor values of the termination in question. Kevin -----Original Message----- From: å® ä» [mailto:juniperfu@hotmail.com] Sent: Thursday, November 13, 2003 8:20 PM To: juniperfu@hotmail.com; Boyle, Kevin [NCRTP:3Z40:EXCH]; JuLin.Wang@alcatel-sbell.com.cn; megaco@ietf.org Subject: RE: [Megaco] a problem about audit All, If MG found some connection has some problem, And How can MG notify the MGC? thanks! Mark >From: "å® ä»" >To: kboyle@nortelnetworks.com, JuLin.Wang@alcatel-sbell.com.cn, >megaco@ietf.org >Subject: RE: [Megaco] a problem about audit >Date: Tue, 11 Nov 2003 09:20:39 +0800 > >So, If MGC can't audit all the context of the MG When MGC switchover, >How can MGC keep the coherence in the context and termination with MG? > > >>From: "Kevin Boyle" >>To: FND-AD Wang JuLin , ? ? >>, megaco@ietf.org >>Subject: RE: [Megaco] a problem about audit >>Date: Mon, 10 Nov 2003 10:03:38 -0500 >> >>The question was how to return all the contexts in existence on the MG. >>So, >>my answer still stands -- there's not a lot that can be done to >>overcome the MTU limitation in UDP. TCP segments its messages based >>on the MTU size, so there's not a problem there. >> >>Kevin >> >>-----Original Message----- >>From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] >>Sent: Monday, November 10, 2003 12:46 AM >>To: Boyle, Kevin [NCRTP:3Z40:EXCH]; ? ?; megaco@ietf.org >>Subject: RE: [Megaco] a problem about audit >> >>IMO,It depends on the MTU size. If the message larger than it, gateway >>can trigger the reply message with error code 533 "RSP EXCEEDS MAX >>TRANSPORT PDU SIZE" . >> >> >>-----Original Message----- >> >>From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] >> >>Sent: Monday, November 10, 2003 11:26 AM >> >>To: å® ä»; megaco@ietf.org >> >>Subject: RE: [Megaco] a problem about audit >> >> >> >> >> >>If you use TCP, there really isn't a limit to the message length, >> >>since the transport will segment the message. >> >> >> >>For UDP, I can suggest using short form tokens and removing all >> >>non-mandatory whitespace. This will help keep the message size down. >> >>Other than that, at this moment, there's not a lot you can do about >> >>the message size. >> >> >> >>Kevin >> >> >> >>-----Original Message----- >> >>From: å® ä» [mailto:juniperfu@hotmail.com] >> >>Sent: Sunday, November 09, 2003 8:01 PM >> >>To: megaco@ietf.org >> >>Subject: [Megaco] a problem about audit >> >> >> >>All, >> >>When MGC restart or HA, Maybe it need audit the context and >> >>termination of MG, and it can send the command Context = * { >> >>AuditValue= ROOT {Audit { } } and the MG should return Context = >> >>100 { AuditValue= TermA, TermB } Context = 200 { AuditValue= TermC, >> >>TermD } Context = 300 { AuditValue= TermE, TermF } And my problem >> >>is if the MG has a lot of context and a >> >megaco message >> >>can't include them, So how do the mg return all its context, thanks! >> >> >> >>juniper >> >> >> >>_________________________________________________________________ >> >>Add photos to your messages with MSN 8. Get 2 months FREE*. >> >>http://join.msn.com/?page=features/featuredemail >> >> >> >> >> >>_______________________________________________ >> >>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 > >_________________________________________________________________ >Add photos to your e-mail with MSN 8. Get 2 months FREE*. >http://join.msn.com/?page=features/featuredemail > > >_______________________________________________ >Megaco mailing list >Megaco@ietf.org >https://www1.ietf.org/mailman/listinfo/megaco _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Fri Nov 14 13:12:19 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23063 for ; Fri, 14 Nov 2003 13:12:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKiQN-0004S1-53 for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 13:12:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAEIC3D4017103 for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 13:12:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKiQN-0004Rm-1b for megaco-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 13:12:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23042 for ; Fri, 14 Nov 2003 13:11:47 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKiQK-00027z-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 13:12:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKiQK-00027w-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 13:12:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKiQK-0004R5-BO; Fri, 14 Nov 2003 13:12:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKiPN-00047n-E6 for megaco@optimus.ietf.org; Fri, 14 Nov 2003 13:11:01 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22956 for ; Fri, 14 Nov 2003 13:10:45 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKiPL-00026N-00 for megaco@ietf.org; Fri, 14 Nov 2003 13:10:59 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AKiPK-00025w-00 for megaco@ietf.org; Fri, 14 Nov 2003 13:10:58 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAEIARm24376 for ; Fri, 14 Nov 2003 13:10:27 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 14 Nov 2003 13:10:28 -0500 Message-ID: From: "Kevin Boyle" To: Sampath Komanduri , "'Harry Suede'" , megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Date: Fri, 14 Nov 2003 13:10:24 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , It is not possible to put an Events descriptor in a Subtract command. I believe Harry raises a good point -- the subtract results in the clearing of the descriptors -- including the Events descriptor. Since the MGC issued the Subtract command, it should know that the signal halted without being told by the MG. I agree with Harry that the notification is suppressed by the Subtract command, since there is the implied reset of the Events descriptor. Kevin -----Original Message----- From: Sampath Komanduri [mailto:sampathk@cisco.com] Sent: Friday, November 14, 2003 3:47 AM To: 'Harry Suede'; megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Hi Harry, Assuming that there *wasn't* an empty events descriptor in the Subtract, MG should send a g/sc event notification with method set to "NC" (Not completed, other cause). I don't find anything specified in the protocol with respect to special handling of g/sc for Subtract. Therefore, normal handling (notify MGC if Signal playout was aborted for any reason) of g/sc should apply. Thanks, Sampath -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of Harry Suede Sent: Wednesday, November 12, 2003 3:06 AM To: megaco@ietf.org Subject: [Megaco] g/sc Notification during Subtract Hi List, A signal is being applied on a termination in Non-NULL context. Then MGC sends Subtract command on the termination. The MG will stop the signal during processing of Subtract command. Should MG send the Notify command for g/sc event with "NC" (Not completed, other cause) towards MGC? I think , since all the active descriptors shall be reset during Subtract processing, so MG should **not** send g/sc notification as Events descriptor doesn't contain g/sc at that point of time. Pls. respond. Thanks Harry. -- __________________________________________________________ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup Search Smarter - get the new eXact Search Bar for free! http://www.exactsearchbar.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 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Fri Nov 14 13:12:19 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23071 for ; Fri, 14 Nov 2003 13:12:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKiQK-0004R5-BO; Fri, 14 Nov 2003 13:12:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKiPN-00047n-E6 for megaco@optimus.ietf.org; Fri, 14 Nov 2003 13:11:01 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22956 for ; Fri, 14 Nov 2003 13:10:45 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKiPL-00026N-00 for megaco@ietf.org; Fri, 14 Nov 2003 13:10:59 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AKiPK-00025w-00 for megaco@ietf.org; Fri, 14 Nov 2003 13:10:58 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAEIARm24376 for ; Fri, 14 Nov 2003 13:10:27 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 14 Nov 2003 13:10:28 -0500 Message-ID: From: "Kevin Boyle" To: Sampath Komanduri , "'Harry Suede'" , megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Date: Fri, 14 Nov 2003 13:10:24 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , It is not possible to put an Events descriptor in a Subtract command. I believe Harry raises a good point -- the subtract results in the clearing of the descriptors -- including the Events descriptor. Since the MGC issued the Subtract command, it should know that the signal halted without being told by the MG. I agree with Harry that the notification is suppressed by the Subtract command, since there is the implied reset of the Events descriptor. Kevin -----Original Message----- From: Sampath Komanduri [mailto:sampathk@cisco.com] Sent: Friday, November 14, 2003 3:47 AM To: 'Harry Suede'; megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Hi Harry, Assuming that there *wasn't* an empty events descriptor in the Subtract, MG should send a g/sc event notification with method set to "NC" (Not completed, other cause). I don't find anything specified in the protocol with respect to special handling of g/sc for Subtract. Therefore, normal handling (notify MGC if Signal playout was aborted for any reason) of g/sc should apply. Thanks, Sampath -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of Harry Suede Sent: Wednesday, November 12, 2003 3:06 AM To: megaco@ietf.org Subject: [Megaco] g/sc Notification during Subtract Hi List, A signal is being applied on a termination in Non-NULL context. Then MGC sends Subtract command on the termination. The MG will stop the signal during processing of Subtract command. Should MG send the Notify command for g/sc event with "NC" (Not completed, other cause) towards MGC? I think , since all the active descriptors shall be reset during Subtract processing, so MG should **not** send g/sc notification as Events descriptor doesn't contain g/sc at that point of time. Pls. respond. Thanks Harry. -- __________________________________________________________ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup Search Smarter - get the new eXact Search Bar for free! http://www.exactsearchbar.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 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Fri Nov 14 13:43:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24036 for ; Fri, 14 Nov 2003 13:43:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKiuL-0006bM-LK; Fri, 14 Nov 2003 13:43:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKily-0006C2-DN for megaco@optimus.ietf.org; Fri, 14 Nov 2003 13:34:22 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23898 for ; Fri, 14 Nov 2003 13:34:08 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKilw-0002Ro-00 for megaco@ietf.org; Fri, 14 Nov 2003 13:34:20 -0500 Received: from web8304.mail.in.yahoo.com ([203.199.122.34]) by ietf-mx with smtp (Exim 4.12) id 1AKilv-0002Rf-00 for megaco@ietf.org; Fri, 14 Nov 2003 13:34:19 -0500 Message-ID: <20031114183347.70086.qmail@web8304.mail.in.yahoo.com> Received: from [128.107.253.42] by web8304.mail.in.yahoo.com via HTTP; Fri, 14 Nov 2003 18:33:47 GMT Date: Fri, 14 Nov 2003 18:33:47 +0000 (GMT) From: =?iso-8859-1?q?Shobhit=20Bansal?= Subject: RE: [Megaco] g/sc Notification during Subtract To: Kevin Boyle , Sampath Komanduri , "'Harry Suede'" , megaco@ietf.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1021352084-1068834827=:69552" Content-Transfer-Encoding: 8bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , --0-1021352084-1068834827=:69552 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi Kevin, What should be the behaviour if a service change message is sent on the termination on which the signals were playing. Should a notification be sent to MGC in this scenario ? Thanks Shobhit Kevin Boyle wrote: It is not possible to put an Events descriptor in a Subtract command. I believe Harry raises a good point -- the subtract results in the clearing of the descriptors -- including the Events descriptor. Since the MGC issued the Subtract command, it should know that the signal halted without being told by the MG. I agree with Harry that the notification is suppressed by the Subtract command, since there is the implied reset of the Events descriptor. Kevin -----Original Message----- From: Sampath Komanduri [mailto:sampathk@cisco.com] Sent: Friday, November 14, 2003 3:47 AM To: 'Harry Suede'; megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Hi Harry, Assuming that there *wasn't* an empty events descriptor in the Subtract, MG should send a g/sc event notification with method set to "NC" (Not completed, other cause). I don't find anything specified in the protocol with respect to special handling of g/sc for Subtract. Therefore, normal handling (notify MGC if Signal playout was aborted for any reason) of g/sc should apply. Thanks, Sampath -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of Harry Suede Sent: Wednesday, November 12, 2003 3:06 AM To: megaco@ietf.org Subject: [Megaco] g/sc Notification during Subtract Hi List, A signal is being applied on a termination in Non-NULL context. Then MGC sends Subtract command on the termination. The MG will stop the signal during processing of Subtract command. Should MG send the Notify command for g/sc event with "NC" (Not completed, other cause) towards MGC? I think , since all the active descriptors shall be reset during Subtract processing, so MG should **not** send g/sc notification as Events descriptor doesn't contain g/sc at that point of time. Pls. respond. Thanks Harry. -- __________________________________________________________ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup Search Smarter - get the new eXact Search Bar for free! http://www.exactsearchbar.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 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco Yahoo! India Matrimony: Find your partner online.Post your profile. --0-1021352084-1068834827=:69552 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
Hi Kevin,
 
What should be the behaviour if a service change message is sent on the termination on which the signals were playing. Should a notification be sent to MGC in this scenario ?
 
Thanks
Shobhit

Kevin Boyle <kboyle@nortelnetworks.com> wrote:
It is not possible to put an Events descriptor in a Subtract command. I
believe Harry raises a good point -- the subtract results in the clearing of
the descriptors -- including the Events descriptor. Since the MGC issued
the Subtract command, it should know that the signal halted without being
told by the MG.

I agree with Harry that the notification is suppressed by the Subtract
command, since there is the implied reset of the Events descriptor.

Kevin

-----Original Message-----
From: Sampath Komanduri [mailto:sampathk@cisco.com]
Sent: Friday, November 14, 2003 3:47 AM
To: 'Harry Suede'; megaco@ietf.org
Subject: RE: [Megaco] g/sc Notification during Subtract

Hi Harry,
Assuming that there *wasn't* an empty events descriptor in the Subtract, MG
should send a g/sc event notification with method set to "NC" (Not
co! mpleted, other cause).

I don't find anything specified in the protocol with respect to special
handling of g/sc for Subtract. Therefore, normal handling (notify MGC if
Signal playout was aborted for any reason) of g/sc should apply.

Thanks,
Sampath


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Harry Suede
Sent: Wednesday, November 12, 2003 3:06 AM
To: megaco@ietf.org
Subject: [Megaco] g/sc Notification during Subtract


Hi List,

A signal is being applied on a termination in Non-NULL context. Then MGC
sends Subtract command on the termination. The MG will stop the signal
during processing of Subtract command. Should MG send the Notify command for
g/sc event with "NC" (Not completed, other cause) towards MGC?

I think , since all the active descriptors shall be reset during Subtract
processing, so MG should **not** send g/sc notification as Events descriptor
doesn't contain g/sc at that point of time.

Pls. respond.

Thanks
Harry.


--
__________________________________________________________
Sign-up for your own personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

Search Smarter - get the new eXact Search Bar for free!
http://www.exactsearchbar.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

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

Yahoo! India Matrimony: Find your partner online. Post your profile. --0-1021352084-1068834827=:69552-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Fri Nov 14 13:43:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24051 for ; Fri, 14 Nov 2003 13:43:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKiuP-0006cg-M8 for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 13:43:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAEIh5Ft025455 for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 13:43:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKiuP-0006cU-Fj for megaco-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 13:43:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24015 for ; Fri, 14 Nov 2003 13:42:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKiuN-0002VA-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 13:43:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKiuM-0002V7-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 13:43:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKiuL-0006bM-LK; Fri, 14 Nov 2003 13:43:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKily-0006C2-DN for megaco@optimus.ietf.org; Fri, 14 Nov 2003 13:34:22 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23898 for ; Fri, 14 Nov 2003 13:34:08 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKilw-0002Ro-00 for megaco@ietf.org; Fri, 14 Nov 2003 13:34:20 -0500 Received: from web8304.mail.in.yahoo.com ([203.199.122.34]) by ietf-mx with smtp (Exim 4.12) id 1AKilv-0002Rf-00 for megaco@ietf.org; Fri, 14 Nov 2003 13:34:19 -0500 Message-ID: <20031114183347.70086.qmail@web8304.mail.in.yahoo.com> Received: from [128.107.253.42] by web8304.mail.in.yahoo.com via HTTP; Fri, 14 Nov 2003 18:33:47 GMT Date: Fri, 14 Nov 2003 18:33:47 +0000 (GMT) From: =?iso-8859-1?q?Shobhit=20Bansal?= Subject: RE: [Megaco] g/sc Notification during Subtract To: Kevin Boyle , Sampath Komanduri , "'Harry Suede'" , megaco@ietf.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1021352084-1068834827=:69552" Content-Transfer-Encoding: 8bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , --0-1021352084-1068834827=:69552 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi Kevin, What should be the behaviour if a service change message is sent on the termination on which the signals were playing. Should a notification be sent to MGC in this scenario ? Thanks Shobhit Kevin Boyle wrote: It is not possible to put an Events descriptor in a Subtract command. I believe Harry raises a good point -- the subtract results in the clearing of the descriptors -- including the Events descriptor. Since the MGC issued the Subtract command, it should know that the signal halted without being told by the MG. I agree with Harry that the notification is suppressed by the Subtract command, since there is the implied reset of the Events descriptor. Kevin -----Original Message----- From: Sampath Komanduri [mailto:sampathk@cisco.com] Sent: Friday, November 14, 2003 3:47 AM To: 'Harry Suede'; megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Hi Harry, Assuming that there *wasn't* an empty events descriptor in the Subtract, MG should send a g/sc event notification with method set to "NC" (Not completed, other cause). I don't find anything specified in the protocol with respect to special handling of g/sc for Subtract. Therefore, normal handling (notify MGC if Signal playout was aborted for any reason) of g/sc should apply. Thanks, Sampath -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of Harry Suede Sent: Wednesday, November 12, 2003 3:06 AM To: megaco@ietf.org Subject: [Megaco] g/sc Notification during Subtract Hi List, A signal is being applied on a termination in Non-NULL context. Then MGC sends Subtract command on the termination. The MG will stop the signal during processing of Subtract command. Should MG send the Notify command for g/sc event with "NC" (Not completed, other cause) towards MGC? I think , since all the active descriptors shall be reset during Subtract processing, so MG should **not** send g/sc notification as Events descriptor doesn't contain g/sc at that point of time. Pls. respond. Thanks Harry. -- __________________________________________________________ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup Search Smarter - get the new eXact Search Bar for free! http://www.exactsearchbar.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 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco Yahoo! India Matrimony: Find your partner online.Post your profile. --0-1021352084-1068834827=:69552 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit

Hi Kevin,
 
What should be the behaviour if a service change message is sent on the termination on which the signals were playing. Should a notification be sent to MGC in this scenario ?
 
Thanks
Shobhit

Kevin Boyle <kboyle@nortelnetworks.com> wrote:
It is not possible to put an Events descriptor in a Subtract command. I
believe Harry raises a good point -- the subtract results in the clearing of
the descriptors -- including the Events descriptor. Since the MGC issued
the Subtract command, it should know that the signal halted without being
told by the MG.

I agree with Harry that the notification is suppressed by the Subtract
command, since there is the implied reset of the Events descriptor.

Kevin

-----Original Message-----
From: Sampath Komanduri [mailto:sampathk@cisco.com]
Sent: Friday, November 14, 2003 3:47 AM
To: 'Harry Suede'; megaco@ietf.org
Subject: RE: [Megaco] g/sc Notification during Subtract

Hi Harry,
Assuming that there *wasn't* an empty events descriptor in the Subtract, MG
should send a g/sc event notification with method set to "NC" (Not
co! mpleted, other cause).

I don't find anything specified in the protocol with respect to special
handling of g/sc for Subtract. Therefore, normal handling (notify MGC if
Signal playout was aborted for any reason) of g/sc should apply.

Thanks,
Sampath


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Harry Suede
Sent: Wednesday, November 12, 2003 3:06 AM
To: megaco@ietf.org
Subject: [Megaco] g/sc Notification during Subtract


Hi List,

A signal is being applied on a termination in Non-NULL context. Then MGC
sends Subtract command on the termination. The MG will stop the signal
during processing of Subtract command. Should MG send the Notify command for
g/sc event with "NC" (Not completed, other cause) towards MGC?

I think , since all the active descriptors shall be reset during Subtract
processing, so MG should **not** send g/sc notification as Events descriptor
doesn't contain g/sc at that point of time.

Pls. respond.

Thanks
Harry.


--
__________________________________________________________
Sign-up for your own personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

Search Smarter - get the new eXact Search Bar for free!
http://www.exactsearchbar.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

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

Yahoo! India Matrimony: Find your partner online. Post your profile. --0-1021352084-1068834827=:69552-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Fri Nov 14 13:49:18 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24184 for ; Fri, 14 Nov 2003 13:49:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKj08-00071V-UL; Fri, 14 Nov 2003 13:49:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKizi-0006sq-UZ for megaco@optimus.ietf.org; Fri, 14 Nov 2003 13:48:34 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24176 for ; Fri, 14 Nov 2003 13:48:21 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKizg-0002ad-00 for megaco@ietf.org; Fri, 14 Nov 2003 13:48:32 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AKizc-0002aT-00 for megaco@ietf.org; Fri, 14 Nov 2003 13:48:32 -0500 Received: from cisco.com (171.71.177.238) by sj-iport-3.cisco.com with ESMTP; 14 Nov 2003 10:55:14 -0800 Received: from sampathkw2k02 (dhcp-171-71-248-100.cisco.com [171.71.248.100]) by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id hAEIlttg000376 for ; Fri, 14 Nov 2003 10:47:56 -0800 (PST) From: "Sampath Komanduri" To: Date: Fri, 14 Nov 2003 10:47:51 -0800 Message-ID: <001901c3aadf$d1ac6130$64f847ab@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Content-Transfer-Encoding: 7bit Subject: [Megaco] Questions on CAS Signal type/durations Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi Kevin, Could you pls. shed some light on the time/duration parameter associated with the following CAS signals? A) Seize Signal (defined as brief and duration is specified to be "Not applicable"): Handling is clear and no problem. B) bcas/addr (defined as brief and duration is specified to be "Provisioned"): Is it acceptable for MG have the default configuration as "Not applicable" in which case if MGC request a g/sc with this signal, MG will report it whenever it is done with playing out the signal (no time bounds)? C) icasc/addr (defined as Timeout and duration is specified to be "depends on parameters supplied"): What does this mean? Can you suggest some examples on how will MGC decide on different values for different parameters? D) amet/em (defined as OnOff and duration is specified to be "Variable"): I am assuming that for all these signals 'duration' parameter will not be provided by MGC. Only the MG will know the duration of the signals to be applied. Is this assumption correct? E) amet/mpb (defined as Brief and duration is specified to be "Variable"): I am assuming that for all these signals 'duration' parameter will not be provided by MGC. Only the MG will know the duration of the signals to be applied (based on em duration (configured on MG) and bpc parameter of the signal). Is this assumption correct? Thanks, Sampath _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Fri Nov 14 13:49:19 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24196 for ; Fri, 14 Nov 2003 13:49:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKj0A-00072u-Sx for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 13:49:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAEIn2IL027078 for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 13:49:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKj0A-00072f-PZ for megaco-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 13:49:02 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24180 for ; Fri, 14 Nov 2003 13:48:48 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKj08-0002ao-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 13:49:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKj08-0002al-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 13:49:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKj08-00071V-UL; Fri, 14 Nov 2003 13:49:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKizi-0006sq-UZ for megaco@optimus.ietf.org; Fri, 14 Nov 2003 13:48:34 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24176 for ; Fri, 14 Nov 2003 13:48:21 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKizg-0002ad-00 for megaco@ietf.org; Fri, 14 Nov 2003 13:48:32 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AKizc-0002aT-00 for megaco@ietf.org; Fri, 14 Nov 2003 13:48:32 -0500 Received: from cisco.com (171.71.177.238) by sj-iport-3.cisco.com with ESMTP; 14 Nov 2003 10:55:14 -0800 Received: from sampathkw2k02 (dhcp-171-71-248-100.cisco.com [171.71.248.100]) by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id hAEIlttg000376 for ; Fri, 14 Nov 2003 10:47:56 -0800 (PST) From: "Sampath Komanduri" To: Date: Fri, 14 Nov 2003 10:47:51 -0800 Message-ID: <001901c3aadf$d1ac6130$64f847ab@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Content-Transfer-Encoding: 7bit Subject: [Megaco] Questions on CAS Signal type/durations Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Kevin, Could you pls. shed some light on the time/duration parameter associated with the following CAS signals? A) Seize Signal (defined as brief and duration is specified to be "Not applicable"): Handling is clear and no problem. B) bcas/addr (defined as brief and duration is specified to be "Provisioned"): Is it acceptable for MG have the default configuration as "Not applicable" in which case if MGC request a g/sc with this signal, MG will report it whenever it is done with playing out the signal (no time bounds)? C) icasc/addr (defined as Timeout and duration is specified to be "depends on parameters supplied"): What does this mean? Can you suggest some examples on how will MGC decide on different values for different parameters? D) amet/em (defined as OnOff and duration is specified to be "Variable"): I am assuming that for all these signals 'duration' parameter will not be provided by MGC. Only the MG will know the duration of the signals to be applied. Is this assumption correct? E) amet/mpb (defined as Brief and duration is specified to be "Variable"): I am assuming that for all these signals 'duration' parameter will not be provided by MGC. Only the MG will know the duration of the signals to be applied (based on em duration (configured on MG) and bpc parameter of the signal). Is this assumption correct? Thanks, Sampath _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Fri Nov 14 14:07:18 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24672 for ; Fri, 14 Nov 2003 14:07:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKjHZ-0008Tg-5Y; Fri, 14 Nov 2003 14:07:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKjGw-0008Sa-Lm for megaco@optimus.ietf.org; Fri, 14 Nov 2003 14:06:22 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24646 for ; Fri, 14 Nov 2003 14:06:08 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKjGu-0002n3-00 for megaco@ietf.org; Fri, 14 Nov 2003 14:06:20 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AKjGt-0002me-00 for megaco@ietf.org; Fri, 14 Nov 2003 14:06:19 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAEJ5mm03247 for ; Fri, 14 Nov 2003 14:05:48 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 14 Nov 2003 14:05:49 -0500 Message-ID: From: "Kevin Boyle" To: Sampath Komanduri , megaco@ietf.org Subject: RE: [Megaco] Questions on CAS Signal type/durations Date: Fri, 14 Nov 2003 14:05:45 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Comments inline. [KJBII] As a general note, when the signal completes on its own (not interrupted by an event, a new signals descriptor, or some "other reason"), the g/sc reports a timeout. This occurs upon completion of the signal, no matter the duration. Note that OnOff signals are not capable of timing out, so TO as a reason for g/sc is impossible for OO signals. OO signals must always be interrupted in some fashion. Kevin -----Original Message----- From: Sampath Komanduri [mailto:sampathk@cisco.com] Sent: Friday, November 14, 2003 1:48 PM To: megaco@ietf.org Subject: [Megaco] Questions on CAS Signal type/durations Hi Kevin, Could you pls. shed some light on the time/duration parameter associated with the following CAS signals? A) Seize Signal (defined as brief and duration is specified to be "Not applicable"): Handling is clear and no problem. B) bcas/addr (defined as brief and duration is specified to be "Provisioned"): Is it acceptable for MG have the default configuration as "Not applicable" in which case if MGC request a g/sc with this signal, MG will report it whenever it is done with playing out the signal (no time bounds)? [KJBII] There is no bcas/addr. I believe you mean bcasaddr/addr. Are you looking at H.248.25? Anyhow, I believe your description is acceptable. See my general note above. C) icasc/addr (defined as Timeout and duration is specified to be "depends on parameters supplied"): What does this mean? Can you suggest some examples on how will MGC decide on different values for different parameters? [KJBII] It depends upon what parameters are supplied as to how long the signal will last. This is digit outpulsing, so the number of digits to be outpulsed, along with the interaction with the far-end trunk will have an impact on how long the signal requires to play to completion. For description of the call processing functionality of CAS trunking, see the appropriate specification for the market you are targeting. D) amet/em (defined as OnOff and duration is specified to be "Variable"): I am assuming that for all these signals 'duration' parameter will not be provided by MGC. Only the MG will know the duration of the signals to be applied. Is this assumption correct? [KJBII] OnOff means "play until terminated", rather than "play until the signal duration expires". So your assumption is correct. E) amet/mpb (defined as Brief and duration is specified to be "Variable"): I am assuming that for all these signals 'duration' parameter will not be provided by MGC. Only the MG will know the duration of the signals to be applied (based on em duration (configured on MG) and bpc parameter of the signal). Is this assumption correct? [KJBII] For amet/mpb, the duration will depend upon how many pulses the MG is playing out. Generally, the MGC does not specify how metering pulses are applied -- just how many to apply. So this assumption is correct. Thanks, Sampath _______________________________________________ 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 exim@www1.ietf.org Fri Nov 14 14:07:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24687 for ; Fri, 14 Nov 2003 14:07:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKjHb-0008Ve-KV for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 14:07:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAEJ73EQ032709 for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 14:07:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKjHb-0008VI-8Y for megaco-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 14:07:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24661 for ; Fri, 14 Nov 2003 14:06:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKjHY-0002ny-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 14:07:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKjHY-0002nv-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 14:07:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKjHZ-0008Tg-5Y; Fri, 14 Nov 2003 14:07:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKjGw-0008Sa-Lm for megaco@optimus.ietf.org; Fri, 14 Nov 2003 14:06:22 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24646 for ; Fri, 14 Nov 2003 14:06:08 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKjGu-0002n3-00 for megaco@ietf.org; Fri, 14 Nov 2003 14:06:20 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AKjGt-0002me-00 for megaco@ietf.org; Fri, 14 Nov 2003 14:06:19 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAEJ5mm03247 for ; Fri, 14 Nov 2003 14:05:48 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 14 Nov 2003 14:05:49 -0500 Message-ID: From: "Kevin Boyle" To: Sampath Komanduri , megaco@ietf.org Subject: RE: [Megaco] Questions on CAS Signal type/durations Date: Fri, 14 Nov 2003 14:05:45 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Comments inline. [KJBII] As a general note, when the signal completes on its own (not interrupted by an event, a new signals descriptor, or some "other reason"), the g/sc reports a timeout. This occurs upon completion of the signal, no matter the duration. Note that OnOff signals are not capable of timing out, so TO as a reason for g/sc is impossible for OO signals. OO signals must always be interrupted in some fashion. Kevin -----Original Message----- From: Sampath Komanduri [mailto:sampathk@cisco.com] Sent: Friday, November 14, 2003 1:48 PM To: megaco@ietf.org Subject: [Megaco] Questions on CAS Signal type/durations Hi Kevin, Could you pls. shed some light on the time/duration parameter associated with the following CAS signals? A) Seize Signal (defined as brief and duration is specified to be "Not applicable"): Handling is clear and no problem. B) bcas/addr (defined as brief and duration is specified to be "Provisioned"): Is it acceptable for MG have the default configuration as "Not applicable" in which case if MGC request a g/sc with this signal, MG will report it whenever it is done with playing out the signal (no time bounds)? [KJBII] There is no bcas/addr. I believe you mean bcasaddr/addr. Are you looking at H.248.25? Anyhow, I believe your description is acceptable. See my general note above. C) icasc/addr (defined as Timeout and duration is specified to be "depends on parameters supplied"): What does this mean? Can you suggest some examples on how will MGC decide on different values for different parameters? [KJBII] It depends upon what parameters are supplied as to how long the signal will last. This is digit outpulsing, so the number of digits to be outpulsed, along with the interaction with the far-end trunk will have an impact on how long the signal requires to play to completion. For description of the call processing functionality of CAS trunking, see the appropriate specification for the market you are targeting. D) amet/em (defined as OnOff and duration is specified to be "Variable"): I am assuming that for all these signals 'duration' parameter will not be provided by MGC. Only the MG will know the duration of the signals to be applied. Is this assumption correct? [KJBII] OnOff means "play until terminated", rather than "play until the signal duration expires". So your assumption is correct. E) amet/mpb (defined as Brief and duration is specified to be "Variable"): I am assuming that for all these signals 'duration' parameter will not be provided by MGC. Only the MG will know the duration of the signals to be applied (based on em duration (configured on MG) and bpc parameter of the signal). Is this assumption correct? [KJBII] For amet/mpb, the duration will depend upon how many pulses the MG is playing out. Generally, the MGC does not specify how metering pulses are applied -- just how many to apply. So this assumption is correct. Thanks, Sampath _______________________________________________ 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-admin@ietf.org Fri Nov 14 14:29:18 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25335 for ; Fri, 14 Nov 2003 14:29:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKjcr-0001QO-Cl; Fri, 14 Nov 2003 14:29:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKjco-0001Q5-5C for megaco@optimus.ietf.org; Fri, 14 Nov 2003 14:28:58 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25327 for ; Fri, 14 Nov 2003 14:28:43 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKjcl-00036P-00 for megaco@ietf.org; Fri, 14 Nov 2003 14:28:55 -0500 Received: from [216.90.186.146] (helo=mail.ipnetfusion.com) by ietf-mx with esmtp (Exim 4.12) id 1AKjck-00036J-00 for megaco@ietf.org; Fri, 14 Nov 2003 14:28:55 -0500 Received: from pc187 (proxy.ipnetfusion.com [216.90.186.147]) (authenticated) by mail.ipnetfusion.com (8.11.6/8.11.6) with ESMTP id hAEJSsM21158 for ; Fri, 14 Nov 2003 13:28:54 -0600 From: "Manish Bhagwanani" To: Date: Fri, 14 Nov 2003 13:28:31 -0600 Message-ID: <001d01c3aae5$7fe96220$bb0201c0@pc187> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001E_01C3AAB3.354EF220" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 Importance: Normal Subject: [Megaco] Example of Notify on ROOT termination Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_001E_01C3AAB3.354EF220 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Can anyone give an example of what package/event can be sent for a ROOT termination in a Notify command? Can one of the property parms in the root package be modified and sent back by the Media Gateway ? Thanks, Manish Bhagwanani ------=_NextPart_000_001E_01C3AAB3.354EF220 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Can anyone give an example of what package/event can = be sent for a ROOT termination in a Notify command? Can one of the property = parms in the root package be modified and sent back by the Media Gateway = ?

 

Thanks,

 

Manish Bhagwanani

------=_NextPart_000_001E_01C3AAB3.354EF220-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Fri Nov 14 14:29:19 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25346 for ; Fri, 14 Nov 2003 14:29:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKjct-0001RD-J4 for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 14:29:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAEJT3li005521 for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 14:29:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKjct-0001Qy-Ev for megaco-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 14:29:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25331 for ; Fri, 14 Nov 2003 14:28:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKjcq-00036V-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 14:29:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKjcq-00036S-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 14:29:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKjcr-0001QO-Cl; Fri, 14 Nov 2003 14:29:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKjco-0001Q5-5C for megaco@optimus.ietf.org; Fri, 14 Nov 2003 14:28:58 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25327 for ; Fri, 14 Nov 2003 14:28:43 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKjcl-00036P-00 for megaco@ietf.org; Fri, 14 Nov 2003 14:28:55 -0500 Received: from [216.90.186.146] (helo=mail.ipnetfusion.com) by ietf-mx with esmtp (Exim 4.12) id 1AKjck-00036J-00 for megaco@ietf.org; Fri, 14 Nov 2003 14:28:55 -0500 Received: from pc187 (proxy.ipnetfusion.com [216.90.186.147]) (authenticated) by mail.ipnetfusion.com (8.11.6/8.11.6) with ESMTP id hAEJSsM21158 for ; Fri, 14 Nov 2003 13:28:54 -0600 From: "Manish Bhagwanani" To: Date: Fri, 14 Nov 2003 13:28:31 -0600 Message-ID: <001d01c3aae5$7fe96220$bb0201c0@pc187> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001E_01C3AAB3.354EF220" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 Importance: Normal Subject: [Megaco] Example of Notify on ROOT termination Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_001E_01C3AAB3.354EF220 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Can anyone give an example of what package/event can be sent for a ROOT termination in a Notify command? Can one of the property parms in the root package be modified and sent back by the Media Gateway ? Thanks, Manish Bhagwanani ------=_NextPart_000_001E_01C3AAB3.354EF220 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Can anyone give an example of what package/event can = be sent for a ROOT termination in a Notify command? Can one of the property = parms in the root package be modified and sent back by the Media Gateway = ?

 

Thanks,

 

Manish Bhagwanani

------=_NextPart_000_001E_01C3AAB3.354EF220-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Fri Nov 14 17:33:18 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02194 for ; Fri, 14 Nov 2003 17:33:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKmUv-0006jh-6Y; Fri, 14 Nov 2003 17:33:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKmUj-0006jU-T5 for megaco@optimus.ietf.org; Fri, 14 Nov 2003 17:32:50 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02183 for ; Fri, 14 Nov 2003 17:32:34 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKmUh-0005aA-00 for megaco@ietf.org; Fri, 14 Nov 2003 17:32:47 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AKmUf-0005Zy-00 for megaco@ietf.org; Fri, 14 Nov 2003 17:32:45 -0500 Received: from cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 14 Nov 2003 14:38:34 -0800 Received: from sampathkw2k02 (dhcp-171-71-248-100.cisco.com [171.71.248.100]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAEMVCAt025902; Fri, 14 Nov 2003 14:31:13 -0800 (PST) From: "Sampath Komanduri" To: "'Shobhit Bansal'" , "'Kevin Boyle'" , "'Harry Suede'" , Subject: RE: [Megaco] g/sc Notification during Subtract Date: Fri, 14 Nov 2003 14:31:07 -0800 Message-ID: <002901c3aaff$02d51fd0$64f847ab@amer.cisco.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002A_01C3AABB.F4B1DFD0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: <20031114183347.70086.qmail@web8304.mail.in.yahoo.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_002A_01C3AABB.F4B1DFD0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Shobhit, My answers are based on Kevin's response to earlier mail on this issue: There are two scenarios that we should consider: a) MGC initiated termination out-of-service: MG needn't send the g/sc notification to MGC (going by Kevin's logic that MGC can derive this information). I don't know what should be MGC's behavior if it receives g/sc (with any method) after it has sent SUBTRACT or ServiceChange message but before it receives the corresponding response (Kevin ??) b) MG initiated termination out-of-service: MG needn't send the g/sc notification to MGC since (again) MGC can derive this information. Sampath -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of Shobhit Bansal Sent: Friday, November 14, 2003 10:34 AM To: Kevin Boyle; Sampath Komanduri; 'Harry Suede'; megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Hi Kevin, What should be the behaviour if a service change message is sent on the termination on which the signals were playing. Should a notification be sent to MGC in this scenario ? Thanks Shobhit Kevin Boyle wrote: It is not possible to put an Events descriptor in a Subtract command. I believe Harry raises a good point -- the subtract results in the clearing of the descriptors -- including the Events descriptor. Since the MGC issued the Subtract command, it should know that the signal halted without being told by the MG. I agree with Harry that the notification is suppressed by the Subtract command, since there is the implied reset of the Events descriptor. Kevin -----Original Message----- From: Sampath Komanduri [mailto:sampathk@cisco.com] Sent: Friday, November 14, 2003 3:47 AM To: 'Harry Suede'; megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Hi Harry, Assuming that there *wasn't* an empty events descriptor in the Subtract, MG should send a g/sc event notification with method set to "NC" (Not co! mpleted, other cause). I don't find anything specified in the protocol with respect to special handling of g/sc for Subtract. Therefore, normal handling (notify MGC if Signal playout was aborted for any reason) of g/sc should apply. Thanks, Sampath -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of Harry Suede Sent: Wednesday, November 12, 2003 3:06 AM To: megaco@ietf.org Subject: [Megaco] g/sc Notification during Subtract Hi List, A signal is being applied on a termination in Non-NULL context. Then MGC sends Subtract command on the termination. The MG will stop the signal during processing of Subtract command. Should MG send the Notify command for g/sc event with "NC" (Not completed, other cause) towards MGC? I think , since all the active descriptors shall be reset during Subtract processing, so MG should **not** send g/sc notification as Events descriptor doesn't contain g/sc at that point of time. Pls. respond. Thanks Harry. -- __________________________________________________________ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup Search Smarter - get the new eXact Search Bar for free! http://www.exactsearchbar.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 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco Yahoo! India Matrimony: Find your partner online. Post your profile. ------=_NextPart_000_002A_01C3AABB.F4B1DFD0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
Shobhit,
My=20 answers are based on Kevin's response to earlier mail on this=20 issue:
 
There=20 are two scenarios that we should consider:
a) MGC=20 initiated termination out-of-service: MG needn't send the g/sc = notification to=20 MGC (going by Kevin's logic that MGC can derive this information).=20
I=20 don't know what should be MGC's behavior if it receives g/sc (with any = method)=20 after it has sent SUBTRACT or ServiceChange message but before it = receives the=20 corresponding response (Kevin ??)
b) MG=20 initiated termination out-of-service: MG needn't send the g/sc = notification to=20 MGC since (again) MGC can derive this information.
 
Sampath
 
-----Original = Message-----
From:=20 megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of = Shobhit=20 Bansal
Sent: Friday, November 14, 2003 10:34 AM
To: = Kevin=20 Boyle; Sampath Komanduri; 'Harry Suede'; = megaco@ietf.org
Subject: RE:=20 [Megaco] g/sc Notification during Subtract

Hi Kevin,
 
What should be the behaviour if a service change message is sent = on the=20 termination on which the signals were playing. Should a notification = be sent=20 to MGC in this scenario ?
 
Thanks
Shobhit

Kevin Boyle=20 <kboyle@nortelnetworks.com> wrote:
It=20 is not possible to put an Events descriptor in a Subtract command.=20 I
believe Harry raises a good point -- the subtract results in = the=20 clearing of
the descriptors -- including the Events descriptor. = Since the=20 MGC issued
the Subtract command, it should know that the signal = halted=20 without being
told by the MG.

I agree with Harry that the=20 notification is suppressed by the Subtract
command, since there = is the=20 implied reset of the Events descriptor.

Kevin =

-----Original=20 Message-----
From: Sampath Komanduri [mailto:sampathk@cisco.com]=20
Sent: Friday, November 14, 2003 3:47 AM
To: 'Harry Suede';=20 megaco@ietf.org
Subject: RE: [Megaco] g/sc Notification during=20 Subtract

Hi Harry,
Assuming that there *wasn't* an empty = events=20 descriptor in the Subtract, MG
should send a g/sc event = notification with=20 method set to "NC" (Not
co! mpleted, other cause).

I don't = find=20 anything specified in the protocol with respect to = special
handling of=20 g/sc for Subtract. Therefore, normal handling (notify MGC = if
Signal=20 playout was aborted for any reason) of g/sc should=20 apply.

Thanks,
Sampath


-----Original=20 Message-----
From: megaco-admin@ietf.org = [mailto:megaco-admin@ietf.org]=20 On Behalf Of
Harry Suede
Sent: Wednesday, November 12, 2003 = 3:06=20 AM
To: megaco@ietf.org
Subject: [Megaco] g/sc Notification = during=20 Subtract


Hi List,

A signal is being applied on a=20 termination in Non-NULL context. Then MGC
sends Subtract command = on the=20 termination. The MG will stop the signal
during processing of = Subtract=20 command. Should MG send the Notify command for
g/sc event with = "NC" (Not=20 completed, other cause) towards MGC?

I think , since all the = active=20 descriptors shall be reset during Subtract
processing, so MG = should=20 **not** send g/sc notification as Events descriptor
doesn't = contain g/sc=20 at that point of time.

Pls.=20 = respond.

Thanks
Harry.


--
_______________________= ___________________________________
Sign-up=20 for your own personalized E-mail at=20 Mail.com
http://www.mail.com/?sr=3Dsignup

Search Smarter - = get the=20 new eXact Search Bar for=20 = free!
http://www.exactsearchbar.com/


______________________= _________________________
Megaco=20 mailing=20 = list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco<= BR>

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

Yahoo! India Matrimony: Find your partner = online.=20 Post your profile.

= ------=_NextPart_000_002A_01C3AABB.F4B1DFD0-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Fri Nov 14 17:33:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02209 for ; Fri, 14 Nov 2003 17:33:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKmUy-0006kQ-Ev for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 17:33:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAEMX4qi025938 for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 17:33:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKmUy-0006kH-7c for megaco-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 17:33:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02191 for ; Fri, 14 Nov 2003 17:32:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKmUv-0005aG-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 17:33:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKmUv-0005aD-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 17:33:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKmUv-0006jh-6Y; Fri, 14 Nov 2003 17:33:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKmUj-0006jU-T5 for megaco@optimus.ietf.org; Fri, 14 Nov 2003 17:32:50 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02183 for ; Fri, 14 Nov 2003 17:32:34 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKmUh-0005aA-00 for megaco@ietf.org; Fri, 14 Nov 2003 17:32:47 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AKmUf-0005Zy-00 for megaco@ietf.org; Fri, 14 Nov 2003 17:32:45 -0500 Received: from cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 14 Nov 2003 14:38:34 -0800 Received: from sampathkw2k02 (dhcp-171-71-248-100.cisco.com [171.71.248.100]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAEMVCAt025902; Fri, 14 Nov 2003 14:31:13 -0800 (PST) From: "Sampath Komanduri" To: "'Shobhit Bansal'" , "'Kevin Boyle'" , "'Harry Suede'" , Subject: RE: [Megaco] g/sc Notification during Subtract Date: Fri, 14 Nov 2003 14:31:07 -0800 Message-ID: <002901c3aaff$02d51fd0$64f847ab@amer.cisco.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002A_01C3AABB.F4B1DFD0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: <20031114183347.70086.qmail@web8304.mail.in.yahoo.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_002A_01C3AABB.F4B1DFD0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Shobhit, My answers are based on Kevin's response to earlier mail on this issue: There are two scenarios that we should consider: a) MGC initiated termination out-of-service: MG needn't send the g/sc notification to MGC (going by Kevin's logic that MGC can derive this information). I don't know what should be MGC's behavior if it receives g/sc (with any method) after it has sent SUBTRACT or ServiceChange message but before it receives the corresponding response (Kevin ??) b) MG initiated termination out-of-service: MG needn't send the g/sc notification to MGC since (again) MGC can derive this information. Sampath -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of Shobhit Bansal Sent: Friday, November 14, 2003 10:34 AM To: Kevin Boyle; Sampath Komanduri; 'Harry Suede'; megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Hi Kevin, What should be the behaviour if a service change message is sent on the termination on which the signals were playing. Should a notification be sent to MGC in this scenario ? Thanks Shobhit Kevin Boyle wrote: It is not possible to put an Events descriptor in a Subtract command. I believe Harry raises a good point -- the subtract results in the clearing of the descriptors -- including the Events descriptor. Since the MGC issued the Subtract command, it should know that the signal halted without being told by the MG. I agree with Harry that the notification is suppressed by the Subtract command, since there is the implied reset of the Events descriptor. Kevin -----Original Message----- From: Sampath Komanduri [mailto:sampathk@cisco.com] Sent: Friday, November 14, 2003 3:47 AM To: 'Harry Suede'; megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Hi Harry, Assuming that there *wasn't* an empty events descriptor in the Subtract, MG should send a g/sc event notification with method set to "NC" (Not co! mpleted, other cause). I don't find anything specified in the protocol with respect to special handling of g/sc for Subtract. Therefore, normal handling (notify MGC if Signal playout was aborted for any reason) of g/sc should apply. Thanks, Sampath -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of Harry Suede Sent: Wednesday, November 12, 2003 3:06 AM To: megaco@ietf.org Subject: [Megaco] g/sc Notification during Subtract Hi List, A signal is being applied on a termination in Non-NULL context. Then MGC sends Subtract command on the termination. The MG will stop the signal during processing of Subtract command. Should MG send the Notify command for g/sc event with "NC" (Not completed, other cause) towards MGC? I think , since all the active descriptors shall be reset during Subtract processing, so MG should **not** send g/sc notification as Events descriptor doesn't contain g/sc at that point of time. Pls. respond. Thanks Harry. -- __________________________________________________________ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup Search Smarter - get the new eXact Search Bar for free! http://www.exactsearchbar.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 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco Yahoo! India Matrimony: Find your partner online. Post your profile. ------=_NextPart_000_002A_01C3AABB.F4B1DFD0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
Shobhit,
My=20 answers are based on Kevin's response to earlier mail on this=20 issue:
 
There=20 are two scenarios that we should consider:
a) MGC=20 initiated termination out-of-service: MG needn't send the g/sc = notification to=20 MGC (going by Kevin's logic that MGC can derive this information).=20
I=20 don't know what should be MGC's behavior if it receives g/sc (with any = method)=20 after it has sent SUBTRACT or ServiceChange message but before it = receives the=20 corresponding response (Kevin ??)
b) MG=20 initiated termination out-of-service: MG needn't send the g/sc = notification to=20 MGC since (again) MGC can derive this information.
 
Sampath
 
-----Original = Message-----
From:=20 megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of = Shobhit=20 Bansal
Sent: Friday, November 14, 2003 10:34 AM
To: = Kevin=20 Boyle; Sampath Komanduri; 'Harry Suede'; = megaco@ietf.org
Subject: RE:=20 [Megaco] g/sc Notification during Subtract

Hi Kevin,
 
What should be the behaviour if a service change message is sent = on the=20 termination on which the signals were playing. Should a notification = be sent=20 to MGC in this scenario ?
 
Thanks
Shobhit

Kevin Boyle=20 <kboyle@nortelnetworks.com> wrote:
It=20 is not possible to put an Events descriptor in a Subtract command.=20 I
believe Harry raises a good point -- the subtract results in = the=20 clearing of
the descriptors -- including the Events descriptor. = Since the=20 MGC issued
the Subtract command, it should know that the signal = halted=20 without being
told by the MG.

I agree with Harry that the=20 notification is suppressed by the Subtract
command, since there = is the=20 implied reset of the Events descriptor.

Kevin =

-----Original=20 Message-----
From: Sampath Komanduri [mailto:sampathk@cisco.com]=20
Sent: Friday, November 14, 2003 3:47 AM
To: 'Harry Suede';=20 megaco@ietf.org
Subject: RE: [Megaco] g/sc Notification during=20 Subtract

Hi Harry,
Assuming that there *wasn't* an empty = events=20 descriptor in the Subtract, MG
should send a g/sc event = notification with=20 method set to "NC" (Not
co! mpleted, other cause).

I don't = find=20 anything specified in the protocol with respect to = special
handling of=20 g/sc for Subtract. Therefore, normal handling (notify MGC = if
Signal=20 playout was aborted for any reason) of g/sc should=20 apply.

Thanks,
Sampath


-----Original=20 Message-----
From: megaco-admin@ietf.org = [mailto:megaco-admin@ietf.org]=20 On Behalf Of
Harry Suede
Sent: Wednesday, November 12, 2003 = 3:06=20 AM
To: megaco@ietf.org
Subject: [Megaco] g/sc Notification = during=20 Subtract


Hi List,

A signal is being applied on a=20 termination in Non-NULL context. Then MGC
sends Subtract command = on the=20 termination. The MG will stop the signal
during processing of = Subtract=20 command. Should MG send the Notify command for
g/sc event with = "NC" (Not=20 completed, other cause) towards MGC?

I think , since all the = active=20 descriptors shall be reset during Subtract
processing, so MG = should=20 **not** send g/sc notification as Events descriptor
doesn't = contain g/sc=20 at that point of time.

Pls.=20 = respond.

Thanks
Harry.


--
_______________________= ___________________________________
Sign-up=20 for your own personalized E-mail at=20 Mail.com
http://www.mail.com/?sr=3Dsignup

Search Smarter - = get the=20 new eXact Search Bar for=20 = free!
http://www.exactsearchbar.com/


______________________= _________________________
Megaco=20 mailing=20 = list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco<= BR>

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

Yahoo! India Matrimony: Find your partner = online.=20 Post your profile.

= ------=_NextPart_000_002A_01C3AABB.F4B1DFD0-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Fri Nov 14 17:56:18 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02861 for ; Fri, 14 Nov 2003 17:56:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKmrC-00008A-8s; Fri, 14 Nov 2003 17:56:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKmqv-00007j-DV for megaco@optimus.ietf.org; Fri, 14 Nov 2003 17:55:45 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02848 for ; Fri, 14 Nov 2003 17:55:30 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKmqs-0005tY-00 for megaco@ietf.org; Fri, 14 Nov 2003 17:55:42 -0500 Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AKmqs-0005sz-00 for megaco@ietf.org; Fri, 14 Nov 2003 17:55:42 -0500 Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3]) by hoemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hAEMsAq26357 for ; Fri, 14 Nov 2003 16:54:35 -0600 (CST) Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id RAA28582; Fri, 14 Nov 2003 17:54:29 -0500 (EST) Cc: megaco@ietf.org Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id RAA28573; Fri, 14 Nov 2003 17:54:26 -0500 (EST) Message-ID: <3FB55D86.1040301@bell-labs.com> Date: Fri, 14 Nov 2003 17:56:06 -0500 From: Troy Cauble User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Boyle Original-CC: megaco@ietf.org Subject: Re: [Megaco] g/sc Notification during Subtract References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Kevin Boyle wrote: > It is not possible to put an Events descriptor in a Subtract command. I > believe Harry raises a good point -- the subtract results in the clearing of > the descriptors -- including the Events descriptor. Since the MGC issued > the Subtract command, it should know that the signal halted without being > told by the MG. > > I agree with Harry that the notification is suppressed by the Subtract > command, since there is the implied reset of the Events descriptor. > > Kevin Also, from another thread.... Kevin Boyle wrote: > Everything is maintained during a Move command, including Signals and > Events. This is what makes Move different from a Subtract/Add. > > Kevin So does an Add clear Events and Signals as well? -troy _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Fri Nov 14 17:56:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02879 for ; Fri, 14 Nov 2003 17:56:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKmrE-00009Y-IO for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 17:56:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAEMu4ZB000582 for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 17:56:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKmrE-00008l-CK for megaco-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 17:56:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02854 for ; Fri, 14 Nov 2003 17:55:48 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKmrB-0005tm-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 17:56:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKmrB-0005tj-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 17:56:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKmrC-00008A-8s; Fri, 14 Nov 2003 17:56:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKmqv-00007j-DV for megaco@optimus.ietf.org; Fri, 14 Nov 2003 17:55:45 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02848 for ; Fri, 14 Nov 2003 17:55:30 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKmqs-0005tY-00 for megaco@ietf.org; Fri, 14 Nov 2003 17:55:42 -0500 Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AKmqs-0005sz-00 for megaco@ietf.org; Fri, 14 Nov 2003 17:55:42 -0500 Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3]) by hoemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hAEMsAq26357 for ; Fri, 14 Nov 2003 16:54:35 -0600 (CST) Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id RAA28582; Fri, 14 Nov 2003 17:54:29 -0500 (EST) Cc: megaco@ietf.org Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id RAA28573; Fri, 14 Nov 2003 17:54:26 -0500 (EST) Message-ID: <3FB55D86.1040301@bell-labs.com> Date: Fri, 14 Nov 2003 17:56:06 -0500 From: Troy Cauble User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Boyle Original-CC: megaco@ietf.org Subject: Re: [Megaco] g/sc Notification during Subtract References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Kevin Boyle wrote: > It is not possible to put an Events descriptor in a Subtract command. I > believe Harry raises a good point -- the subtract results in the clearing of > the descriptors -- including the Events descriptor. Since the MGC issued > the Subtract command, it should know that the signal halted without being > told by the MG. > > I agree with Harry that the notification is suppressed by the Subtract > command, since there is the implied reset of the Events descriptor. > > Kevin Also, from another thread.... Kevin Boyle wrote: > Everything is maintained during a Move command, including Signals and > Events. This is what makes Move different from a Subtract/Add. > > Kevin So does an Add clear Events and Signals as well? -troy _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Fri Nov 14 20:14:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08014 for ; Fri, 14 Nov 2003 20:14:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKp0k-0001UV-1A; Fri, 14 Nov 2003 20:14:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKp0H-0001Ts-Hz for megaco@optimus.ietf.org; Fri, 14 Nov 2003 20:13:34 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07992 for ; Fri, 14 Nov 2003 20:13:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKp0F-0007at-00 for megaco@ietf.org; Fri, 14 Nov 2003 20:13:31 -0500 Received: from law15-f67.law15.hotmail.com ([64.4.23.67] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 1AKp0E-0007aR-00 for megaco@ietf.org; Fri, 14 Nov 2003 20:13:30 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 14 Nov 2003 17:12:59 -0800 Received: from 210.21.224.54 by lw15fd.law15.hotmail.msn.com with HTTP; Sat, 15 Nov 2003 01:12:59 GMT X-Originating-IP: [210.21.224.54] X-Originating-Email: [juniperfu@hotmail.com] From: "å® ä»" To: kboyle@nortelnetworks.com, JuLin.Wang@alcatel-sbell.com.cn, megaco@ietf.org Subject: RE: [Megaco] a problem about audit Date: Sat, 15 Nov 2003 09:12:59 +0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 15 Nov 2003 01:12:59.0681 (UTC) FILETIME=[9C060910:01C3AB15] Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id UAA07993 Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Kevin, Thank you for help, So, If MG doubt the status of some connection = or=20 termination aren't coherence with the MGC, How MG audit these connection = or=20 termination with MGC? Mark >From: "Kevin Boyle" >To: =E5=AE =E4=BB , JuLin.Wang@alcatel-sbell.com.= cn, =20 >megaco@ietf.org >Subject: RE: [Megaco] a problem about audit >Date: Fri, 14 Nov 2003 10:14:53 -0500 > >If the MGC has sent the netfail event in the Events descriptor, the MG c= an >utilize that. The MG could also send a ServiceChange command. It would >depend upon the situation and the current descriptor values of the >termination in question. > >Kevin > >-----Original Message----- >From: =E5=AE =E4=BB [mailto:juniperfu@hotmail.com] >Sent: Thursday, November 13, 2003 8:20 PM >To: juniperfu@hotmail.com; Boyle, Kevin [NCRTP:3Z40:EXCH]; >JuLin.Wang@alcatel-sbell.com.cn; megaco@ietf.org >Subject: RE: [Megaco] a problem about audit > >All, > If MG found some connection has some problem, And How can MG notif= y=20 >the >MGC? thanks! > >Mark > > > >From: "=E5=AE =E4=BB" > >To: kboyle@nortelnetworks.com, JuLin.Wang@alcatel-sbell.com.cn, > >megaco@ietf.org > >Subject: RE: [Megaco] a problem about audit > >Date: Tue, 11 Nov 2003 09:20:39 +0800 > > > >So, If MGC can't audit all the context of the MG When MGC switchover, > >How can MGC keep the coherence in the context and termination with MG? > > > > > >>From: "Kevin Boyle" > >>To: FND-AD Wang JuLin , ? ? > >>, megaco@ietf.org > >>Subject: RE: [Megaco] a problem about audit > >>Date: Mon, 10 Nov 2003 10:03:38 -0500 > >> > >>The question was how to return all the contexts in existence on the M= G. > >>So, > >>my answer still stands -- there's not a lot that can be done to > >>overcome the MTU limitation in UDP. TCP segments its messages based > >>on the MTU size, so there's not a problem there. > >> > >>Kevin > >> > >>-----Original Message----- > >>From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] > >>Sent: Monday, November 10, 2003 12:46 AM > >>To: Boyle, Kevin [NCRTP:3Z40:EXCH]; ? ?; megaco@ietf.org > >>Subject: RE: [Megaco] a problem about audit > >> > >>IMO,It depends on the MTU size. If the message larger than it, gatewa= y > >>can trigger the reply message with error code 533 "RSP EXCEEDS MAX > >>TRANSPORT PDU SIZE" . > >> > >> >>-----Original Message----- > >> >>From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] > >> >>Sent: Monday, November 10, 2003 11:26 AM > >> >>To: =E5=AE =E4=BB; megaco@ietf.org > >> >>Subject: RE: [Megaco] a problem about audit > >> >> > >> >> > >> >>If you use TCP, there really isn't a limit to the message length, > >> >>since the transport will segment the message. > >> >> > >> >>For UDP, I can suggest using short form tokens and removing all > >> >>non-mandatory whitespace. This will help keep the message size do= wn. > >> >>Other than that, at this moment, there's not a lot you can do abou= t > >> >>the message size. > >> >> > >> >>Kevin > >> >> > >> >>-----Original Message----- > >> >>From: =E5=AE =E4=BB [mailto:juniperfu@hotmail.com] > >> >>Sent: Sunday, November 09, 2003 8:01 PM > >> >>To: megaco@ietf.org > >> >>Subject: [Megaco] a problem about audit > >> >> > >> >>All, > >> >>When MGC restart or HA, Maybe it need audit the context and > >> >>termination of MG, and it can send the command Context =3D * { > >> >>AuditValue=3D ROOT {Audit { } } and the MG should return Context =3D > >> >>100 { AuditValue=3D TermA, TermB } Context =3D 200 { AuditValue=3D= TermC, > >> >>TermD } Context =3D 300 { AuditValue=3D TermE, TermF } And my prob= lem > >> >>is if the MG has a lot of context and a > >> >megaco message > >> >>can't include them, So how do the mg return all its context, thank= s! > >> >> > >> >>juniper > >> >> > >> >>_________________________________________________________________ > >> >>Add photos to your messages with MSN 8. Get 2 months FREE*. > >> >>http://join.msn.com/?page=3Dfeatures/featuredemail > >> >> > >> >> > >> >>_______________________________________________ > >> >>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 > > > >_________________________________________________________________ > >Add photos to your e-mail with MSN 8. Get 2 months FREE*. > >http://join.msn.com/?page=3Dfeatures/featuredemail > > > > > >_______________________________________________ > >Megaco mailing list > >Megaco@ietf.org > >https://www1.ietf.org/mailman/listinfo/megaco > >_________________________________________________________________ >STOP MORE SPAM with the new MSN 8 and get 2 months FREE* >http://join.msn.com/?page=3Dfeatures/junkmail > > >_______________________________________________ >Megaco mailing list >Megaco@ietf.org >https://www1.ietf.org/mailman/listinfo/megaco _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*.=20 http://join.msn.com/?page=3Dfeatures/featuredemail _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Fri Nov 14 20:14:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08057 for ; Fri, 14 Nov 2003 20:14:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKp0n-0001Xf-4t for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 20:14:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAF1E5XS005921 for megaco-archive@odin.ietf.org; Fri, 14 Nov 2003 20:14:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKp0n-0001XQ-0t for megaco-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 20:14:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08003 for ; Fri, 14 Nov 2003 20:13:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKp0k-0007b8-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 20:14:02 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKp0k-0007b5-00 for megaco-web-archive@ietf.org; Fri, 14 Nov 2003 20:14:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKp0k-0001UV-1A; Fri, 14 Nov 2003 20:14:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKp0H-0001Ts-Hz for megaco@optimus.ietf.org; Fri, 14 Nov 2003 20:13:34 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07992 for ; Fri, 14 Nov 2003 20:13:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKp0F-0007at-00 for megaco@ietf.org; Fri, 14 Nov 2003 20:13:31 -0500 Received: from law15-f67.law15.hotmail.com ([64.4.23.67] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 1AKp0E-0007aR-00 for megaco@ietf.org; Fri, 14 Nov 2003 20:13:30 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 14 Nov 2003 17:12:59 -0800 Received: from 210.21.224.54 by lw15fd.law15.hotmail.msn.com with HTTP; Sat, 15 Nov 2003 01:12:59 GMT X-Originating-IP: [210.21.224.54] X-Originating-Email: [juniperfu@hotmail.com] From: "å® ä»" To: kboyle@nortelnetworks.com, JuLin.Wang@alcatel-sbell.com.cn, megaco@ietf.org Subject: RE: [Megaco] a problem about audit Date: Sat, 15 Nov 2003 09:12:59 +0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 15 Nov 2003 01:12:59.0681 (UTC) FILETIME=[9C060910:01C3AB15] X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id UAA07993 Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Kevin, Thank you for help, So, If MG doubt the status of some connection = or=20 termination aren't coherence with the MGC, How MG audit these connection = or=20 termination with MGC? Mark >From: "Kevin Boyle" >To: =E5=AE =E4=BB , JuLin.Wang@alcatel-sbell.com.= cn, =20 >megaco@ietf.org >Subject: RE: [Megaco] a problem about audit >Date: Fri, 14 Nov 2003 10:14:53 -0500 > >If the MGC has sent the netfail event in the Events descriptor, the MG c= an >utilize that. The MG could also send a ServiceChange command. It would >depend upon the situation and the current descriptor values of the >termination in question. > >Kevin > >-----Original Message----- >From: =E5=AE =E4=BB [mailto:juniperfu@hotmail.com] >Sent: Thursday, November 13, 2003 8:20 PM >To: juniperfu@hotmail.com; Boyle, Kevin [NCRTP:3Z40:EXCH]; >JuLin.Wang@alcatel-sbell.com.cn; megaco@ietf.org >Subject: RE: [Megaco] a problem about audit > >All, > If MG found some connection has some problem, And How can MG notif= y=20 >the >MGC? thanks! > >Mark > > > >From: "=E5=AE =E4=BB" > >To: kboyle@nortelnetworks.com, JuLin.Wang@alcatel-sbell.com.cn, > >megaco@ietf.org > >Subject: RE: [Megaco] a problem about audit > >Date: Tue, 11 Nov 2003 09:20:39 +0800 > > > >So, If MGC can't audit all the context of the MG When MGC switchover, > >How can MGC keep the coherence in the context and termination with MG? > > > > > >>From: "Kevin Boyle" > >>To: FND-AD Wang JuLin , ? ? > >>, megaco@ietf.org > >>Subject: RE: [Megaco] a problem about audit > >>Date: Mon, 10 Nov 2003 10:03:38 -0500 > >> > >>The question was how to return all the contexts in existence on the M= G. > >>So, > >>my answer still stands -- there's not a lot that can be done to > >>overcome the MTU limitation in UDP. TCP segments its messages based > >>on the MTU size, so there's not a problem there. > >> > >>Kevin > >> > >>-----Original Message----- > >>From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] > >>Sent: Monday, November 10, 2003 12:46 AM > >>To: Boyle, Kevin [NCRTP:3Z40:EXCH]; ? ?; megaco@ietf.org > >>Subject: RE: [Megaco] a problem about audit > >> > >>IMO,It depends on the MTU size. If the message larger than it, gatewa= y > >>can trigger the reply message with error code 533 "RSP EXCEEDS MAX > >>TRANSPORT PDU SIZE" . > >> > >> >>-----Original Message----- > >> >>From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] > >> >>Sent: Monday, November 10, 2003 11:26 AM > >> >>To: =E5=AE =E4=BB; megaco@ietf.org > >> >>Subject: RE: [Megaco] a problem about audit > >> >> > >> >> > >> >>If you use TCP, there really isn't a limit to the message length, > >> >>since the transport will segment the message. > >> >> > >> >>For UDP, I can suggest using short form tokens and removing all > >> >>non-mandatory whitespace. This will help keep the message size do= wn. > >> >>Other than that, at this moment, there's not a lot you can do abou= t > >> >>the message size. > >> >> > >> >>Kevin > >> >> > >> >>-----Original Message----- > >> >>From: =E5=AE =E4=BB [mailto:juniperfu@hotmail.com] > >> >>Sent: Sunday, November 09, 2003 8:01 PM > >> >>To: megaco@ietf.org > >> >>Subject: [Megaco] a problem about audit > >> >> > >> >>All, > >> >>When MGC restart or HA, Maybe it need audit the context and > >> >>termination of MG, and it can send the command Context =3D * { > >> >>AuditValue=3D ROOT {Audit { } } and the MG should return Context =3D > >> >>100 { AuditValue=3D TermA, TermB } Context =3D 200 { AuditValue=3D= TermC, > >> >>TermD } Context =3D 300 { AuditValue=3D TermE, TermF } And my prob= lem > >> >>is if the MG has a lot of context and a > >> >megaco message > >> >>can't include them, So how do the mg return all its context, thank= s! > >> >> > >> >>juniper > >> >> > >> >>_________________________________________________________________ > >> >>Add photos to your messages with MSN 8. Get 2 months FREE*. > >> >>http://join.msn.com/?page=3Dfeatures/featuredemail > >> >> > >> >> > >> >>_______________________________________________ > >> >>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 > > > >_________________________________________________________________ > >Add photos to your e-mail with MSN 8. Get 2 months FREE*. > >http://join.msn.com/?page=3Dfeatures/featuredemail > > > > > >_______________________________________________ > >Megaco mailing list > >Megaco@ietf.org > >https://www1.ietf.org/mailman/listinfo/megaco > >_________________________________________________________________ >STOP MORE SPAM with the new MSN 8 and get 2 months FREE* >http://join.msn.com/?page=3Dfeatures/junkmail > > >_______________________________________________ >Megaco mailing list >Megaco@ietf.org >https://www1.ietf.org/mailman/listinfo/megaco _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*.=20 http://join.msn.com/?page=3Dfeatures/featuredemail _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Mon Nov 17 13:12:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26435 for ; Mon, 17 Nov 2003 13:12:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALnqz-0004c9-ND; Mon, 17 Nov 2003 13:12:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALnqD-0004Zi-6H for megaco@optimus.ietf.org; Mon, 17 Nov 2003 13:11:13 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26356 for ; Mon, 17 Nov 2003 13:10:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ALnqA-0003aT-00 for megaco@ietf.org; Mon, 17 Nov 2003 13:11:10 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1ALnqA-0003Z9-00 for megaco@ietf.org; Mon, 17 Nov 2003 13:11:10 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAHI9QI09497 for ; Mon, 17 Nov 2003 13:09:27 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 17 Nov 2003 13:09:27 -0500 Message-ID: From: "Kevin Boyle" To: Troy Cauble Cc: megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Date: Mon, 17 Nov 2003 13:09:19 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Add only clears them if the descriptor in question is included. In that case, the descriptor is replaced with the new value. Kevin -----Original Message----- From: Troy Cauble [mailto:troy@bell-labs.com] Sent: Friday, November 14, 2003 5:56 PM To: Boyle, Kevin [NCRTP:3Z40:EXCH] Cc: megaco@ietf.org Subject: Re: [Megaco] g/sc Notification during Subtract Kevin Boyle wrote: > It is not possible to put an Events descriptor in a Subtract command. > I believe Harry raises a good point -- the subtract results in the > clearing of the descriptors -- including the Events descriptor. Since > the MGC issued the Subtract command, it should know that the signal > halted without being told by the MG. > > I agree with Harry that the notification is suppressed by the Subtract > command, since there is the implied reset of the Events descriptor. > > Kevin Also, from another thread.... Kevin Boyle wrote: > Everything is maintained during a Move command, including Signals and > Events. This is what makes Move different from a Subtract/Add. > > Kevin So does an Add clear Events and Signals as well? -troy _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Mon Nov 17 13:12:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26450 for ; Mon, 17 Nov 2003 13:12:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALnr3-0004d5-5q for megaco-archive@odin.ietf.org; Mon, 17 Nov 2003 13:12:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAHIC5jM017791 for megaco-archive@odin.ietf.org; Mon, 17 Nov 2003 13:12:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALnr3-0004cs-0y for megaco-web-archive@optimus.ietf.org; Mon, 17 Nov 2003 13:12:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26424 for ; Mon, 17 Nov 2003 13:11:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ALnr0-0003bo-00 for megaco-web-archive@ietf.org; Mon, 17 Nov 2003 13:12:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ALnr0-0003bh-00 for megaco-web-archive@ietf.org; Mon, 17 Nov 2003 13:12:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALnqz-0004c9-ND; Mon, 17 Nov 2003 13:12:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALnqD-0004Zi-6H for megaco@optimus.ietf.org; Mon, 17 Nov 2003 13:11:13 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26356 for ; Mon, 17 Nov 2003 13:10:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ALnqA-0003aT-00 for megaco@ietf.org; Mon, 17 Nov 2003 13:11:10 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1ALnqA-0003Z9-00 for megaco@ietf.org; Mon, 17 Nov 2003 13:11:10 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAHI9QI09497 for ; Mon, 17 Nov 2003 13:09:27 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 17 Nov 2003 13:09:27 -0500 Message-ID: From: "Kevin Boyle" To: Troy Cauble Cc: megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Date: Mon, 17 Nov 2003 13:09:19 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Add only clears them if the descriptor in question is included. In that case, the descriptor is replaced with the new value. Kevin -----Original Message----- From: Troy Cauble [mailto:troy@bell-labs.com] Sent: Friday, November 14, 2003 5:56 PM To: Boyle, Kevin [NCRTP:3Z40:EXCH] Cc: megaco@ietf.org Subject: Re: [Megaco] g/sc Notification during Subtract Kevin Boyle wrote: > It is not possible to put an Events descriptor in a Subtract command. > I believe Harry raises a good point -- the subtract results in the > clearing of the descriptors -- including the Events descriptor. Since > the MGC issued the Subtract command, it should know that the signal > halted without being told by the MG. > > I agree with Harry that the notification is suppressed by the Subtract > command, since there is the implied reset of the Events descriptor. > > Kevin Also, from another thread.... Kevin Boyle wrote: > Everything is maintained during a Move command, including Signals and > Events. This is what makes Move different from a Subtract/Add. > > Kevin So does an Add clear Events and Signals as well? -troy _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Mon Nov 17 13:54:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28057 for ; Mon, 17 Nov 2003 13:54:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALoVe-0006um-2Y; Mon, 17 Nov 2003 13:54:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALoUv-0006tL-TV for megaco@optimus.ietf.org; Mon, 17 Nov 2003 13:53:18 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28015 for ; Mon, 17 Nov 2003 13:53:05 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ALoUt-0004By-00 for megaco@ietf.org; Mon, 17 Nov 2003 13:53:15 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1ALoUt-0004Bg-00 for megaco@ietf.org; Mon, 17 Nov 2003 13:53:15 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAHIqhI14450 for ; Mon, 17 Nov 2003 13:52:44 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 17 Nov 2003 13:52:44 -0500 Message-ID: From: "Kevin Boyle" To: å® ä» , JuLin.Wang@alcatel-sbell.com.cn, megaco@ietf.org Subject: RE: [Megaco] a problem about audit Date: Mon, 17 Nov 2003 13:52:37 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , MGs cannot audit. It must wait for the MGC to figure out that something is not right. Kevin -----Original Message----- From: å® ä» [mailto:juniperfu@hotmail.com] Sent: Friday, November 14, 2003 8:13 PM To: Boyle, Kevin [NCRTP:3Z40:EXCH]; JuLin.Wang@alcatel-sbell.com.cn; megaco@ietf.org Subject: RE: [Megaco] a problem about audit Kevin, Thank you for help, So, If MG doubt the status of some connection or termination aren't coherence with the MGC, How MG audit these connection or termination with MGC? Mark >From: "Kevin Boyle" >To: å® ä» , JuLin.Wang@alcatel-sbell.com.cn, >megaco@ietf.org >Subject: RE: [Megaco] a problem about audit >Date: Fri, 14 Nov 2003 10:14:53 -0500 > >If the MGC has sent the netfail event in the Events descriptor, the MG >can utilize that. The MG could also send a ServiceChange command. It >would depend upon the situation and the current descriptor values of >the termination in question. > >Kevin > >-----Original Message----- >From: å® ä» [mailto:juniperfu@hotmail.com] >Sent: Thursday, November 13, 2003 8:20 PM >To: juniperfu@hotmail.com; Boyle, Kevin [NCRTP:3Z40:EXCH]; >JuLin.Wang@alcatel-sbell.com.cn; megaco@ietf.org >Subject: RE: [Megaco] a problem about audit > >All, > If MG found some connection has some problem, And How can MG >notify the MGC? thanks! > >Mark > > > >From: "å® ä»" > >To: kboyle@nortelnetworks.com, JuLin.Wang@alcatel-sbell.com.cn, > >megaco@ietf.org > >Subject: RE: [Megaco] a problem about audit > >Date: Tue, 11 Nov 2003 09:20:39 +0800 > > > >So, If MGC can't audit all the context of the MG When MGC switchover, > >How can MGC keep the coherence in the context and termination with MG? > > > > > >>From: "Kevin Boyle" > >>To: FND-AD Wang JuLin , ? ? > >>, megaco@ietf.org > >>Subject: RE: [Megaco] a problem about audit > >>Date: Mon, 10 Nov 2003 10:03:38 -0500 > >> > >>The question was how to return all the contexts in existence on the MG. > >>So, > >>my answer still stands -- there's not a lot that can be done to > >>overcome the MTU limitation in UDP. TCP segments its messages based > >>on the MTU size, so there's not a problem there. > >> > >>Kevin > >> > >>-----Original Message----- > >>From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] > >>Sent: Monday, November 10, 2003 12:46 AM > >>To: Boyle, Kevin [NCRTP:3Z40:EXCH]; ? ?; megaco@ietf.org > >>Subject: RE: [Megaco] a problem about audit > >> > >>IMO,It depends on the MTU size. If the message larger than it, > >>gateway can trigger the reply message with error code 533 "RSP > >>EXCEEDS MAX TRANSPORT PDU SIZE" . > >> > >> >>-----Original Message----- > >> >>From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] > >> >>Sent: Monday, November 10, 2003 11:26 AM > >> >>To: å® ä»; megaco@ietf.org > >> >>Subject: RE: [Megaco] a problem about audit > >> >> > >> >> > >> >>If you use TCP, there really isn't a limit to the message length, > >> >>since the transport will segment the message. > >> >> > >> >>For UDP, I can suggest using short form tokens and removing all > >> >>non-mandatory whitespace. This will help keep the message size down. > >> >>Other than that, at this moment, there's not a lot you can do > >> >>about the message size. > >> >> > >> >>Kevin > >> >> > >> >>-----Original Message----- > >> >>From: å® ä» [mailto:juniperfu@hotmail.com] > >> >>Sent: Sunday, November 09, 2003 8:01 PM > >> >>To: megaco@ietf.org > >> >>Subject: [Megaco] a problem about audit > >> >> > >> >>All, > >> >>When MGC restart or HA, Maybe it need audit the context and > >> >>termination of MG, and it can send the command Context = * { > >> >>AuditValue= ROOT {Audit { } } and the MG should return Context = > >> >>100 { AuditValue= TermA, TermB } Context = 200 { AuditValue= > >> >>TermC, TermD } Context = 300 { AuditValue= TermE, TermF } And my > >> >>problem is if the MG has a lot of context and a > >> >megaco message > >> >>can't include them, So how do the mg return all its context, thanks! > >> >> > >> >>juniper > >> >> > >> >>_________________________________________________________________ > >> >>Add photos to your messages with MSN 8. Get 2 months FREE*. > >> >>http://join.msn.com/?page=features/featuredemail > >> >> > >> >> > >> >>_______________________________________________ > >> >>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 > > > >_________________________________________________________________ > >Add photos to your e-mail with MSN 8. Get 2 months FREE*. > >http://join.msn.com/?page=features/featuredemail > > > > > >_______________________________________________ > >Megaco mailing list > >Megaco@ietf.org > >https://www1.ietf.org/mailman/listinfo/megaco > >_________________________________________________________________ >STOP MORE SPAM with the new MSN 8 and get 2 months FREE* >http://join.msn.com/?page=features/junkmail > > >_______________________________________________ >Megaco mailing list >Megaco@ietf.org >https://www1.ietf.org/mailman/listinfo/megaco _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Mon Nov 17 13:54:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28072 for ; Mon, 17 Nov 2003 13:54:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALoVg-0006wD-8N for megaco-archive@odin.ietf.org; Mon, 17 Nov 2003 13:54:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAHIs4b2026663 for megaco-archive@odin.ietf.org; Mon, 17 Nov 2003 13:54:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALoVg-0006vy-4W for megaco-web-archive@optimus.ietf.org; Mon, 17 Nov 2003 13:54:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28044 for ; Mon, 17 Nov 2003 13:53:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ALoVd-0004Cp-00 for megaco-web-archive@ietf.org; Mon, 17 Nov 2003 13:54:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ALoVd-0004Cm-00 for megaco-web-archive@ietf.org; Mon, 17 Nov 2003 13:54:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALoVe-0006um-2Y; Mon, 17 Nov 2003 13:54:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALoUv-0006tL-TV for megaco@optimus.ietf.org; Mon, 17 Nov 2003 13:53:18 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28015 for ; Mon, 17 Nov 2003 13:53:05 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ALoUt-0004By-00 for megaco@ietf.org; Mon, 17 Nov 2003 13:53:15 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1ALoUt-0004Bg-00 for megaco@ietf.org; Mon, 17 Nov 2003 13:53:15 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAHIqhI14450 for ; Mon, 17 Nov 2003 13:52:44 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 17 Nov 2003 13:52:44 -0500 Message-ID: From: "Kevin Boyle" To: å® ä» , JuLin.Wang@alcatel-sbell.com.cn, megaco@ietf.org Subject: RE: [Megaco] a problem about audit Date: Mon, 17 Nov 2003 13:52:37 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , MGs cannot audit. It must wait for the MGC to figure out that something is not right. Kevin -----Original Message----- From: å® ä» [mailto:juniperfu@hotmail.com] Sent: Friday, November 14, 2003 8:13 PM To: Boyle, Kevin [NCRTP:3Z40:EXCH]; JuLin.Wang@alcatel-sbell.com.cn; megaco@ietf.org Subject: RE: [Megaco] a problem about audit Kevin, Thank you for help, So, If MG doubt the status of some connection or termination aren't coherence with the MGC, How MG audit these connection or termination with MGC? Mark >From: "Kevin Boyle" >To: å® ä» , JuLin.Wang@alcatel-sbell.com.cn, >megaco@ietf.org >Subject: RE: [Megaco] a problem about audit >Date: Fri, 14 Nov 2003 10:14:53 -0500 > >If the MGC has sent the netfail event in the Events descriptor, the MG >can utilize that. The MG could also send a ServiceChange command. It >would depend upon the situation and the current descriptor values of >the termination in question. > >Kevin > >-----Original Message----- >From: å® ä» [mailto:juniperfu@hotmail.com] >Sent: Thursday, November 13, 2003 8:20 PM >To: juniperfu@hotmail.com; Boyle, Kevin [NCRTP:3Z40:EXCH]; >JuLin.Wang@alcatel-sbell.com.cn; megaco@ietf.org >Subject: RE: [Megaco] a problem about audit > >All, > If MG found some connection has some problem, And How can MG >notify the MGC? thanks! > >Mark > > > >From: "å® ä»" > >To: kboyle@nortelnetworks.com, JuLin.Wang@alcatel-sbell.com.cn, > >megaco@ietf.org > >Subject: RE: [Megaco] a problem about audit > >Date: Tue, 11 Nov 2003 09:20:39 +0800 > > > >So, If MGC can't audit all the context of the MG When MGC switchover, > >How can MGC keep the coherence in the context and termination with MG? > > > > > >>From: "Kevin Boyle" > >>To: FND-AD Wang JuLin , ? ? > >>, megaco@ietf.org > >>Subject: RE: [Megaco] a problem about audit > >>Date: Mon, 10 Nov 2003 10:03:38 -0500 > >> > >>The question was how to return all the contexts in existence on the MG. > >>So, > >>my answer still stands -- there's not a lot that can be done to > >>overcome the MTU limitation in UDP. TCP segments its messages based > >>on the MTU size, so there's not a problem there. > >> > >>Kevin > >> > >>-----Original Message----- > >>From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] > >>Sent: Monday, November 10, 2003 12:46 AM > >>To: Boyle, Kevin [NCRTP:3Z40:EXCH]; ? ?; megaco@ietf.org > >>Subject: RE: [Megaco] a problem about audit > >> > >>IMO,It depends on the MTU size. If the message larger than it, > >>gateway can trigger the reply message with error code 533 "RSP > >>EXCEEDS MAX TRANSPORT PDU SIZE" . > >> > >> >>-----Original Message----- > >> >>From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] > >> >>Sent: Monday, November 10, 2003 11:26 AM > >> >>To: å® ä»; megaco@ietf.org > >> >>Subject: RE: [Megaco] a problem about audit > >> >> > >> >> > >> >>If you use TCP, there really isn't a limit to the message length, > >> >>since the transport will segment the message. > >> >> > >> >>For UDP, I can suggest using short form tokens and removing all > >> >>non-mandatory whitespace. This will help keep the message size down. > >> >>Other than that, at this moment, there's not a lot you can do > >> >>about the message size. > >> >> > >> >>Kevin > >> >> > >> >>-----Original Message----- > >> >>From: å® ä» [mailto:juniperfu@hotmail.com] > >> >>Sent: Sunday, November 09, 2003 8:01 PM > >> >>To: megaco@ietf.org > >> >>Subject: [Megaco] a problem about audit > >> >> > >> >>All, > >> >>When MGC restart or HA, Maybe it need audit the context and > >> >>termination of MG, and it can send the command Context = * { > >> >>AuditValue= ROOT {Audit { } } and the MG should return Context = > >> >>100 { AuditValue= TermA, TermB } Context = 200 { AuditValue= > >> >>TermC, TermD } Context = 300 { AuditValue= TermE, TermF } And my > >> >>problem is if the MG has a lot of context and a > >> >megaco message > >> >>can't include them, So how do the mg return all its context, thanks! > >> >> > >> >>juniper > >> >> > >> >>_________________________________________________________________ > >> >>Add photos to your messages with MSN 8. Get 2 months FREE*. > >> >>http://join.msn.com/?page=features/featuredemail > >> >> > >> >> > >> >>_______________________________________________ > >> >>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 > > > >_________________________________________________________________ > >Add photos to your e-mail with MSN 8. Get 2 months FREE*. > >http://join.msn.com/?page=features/featuredemail > > > > > >_______________________________________________ > >Megaco mailing list > >Megaco@ietf.org > >https://www1.ietf.org/mailman/listinfo/megaco > >_________________________________________________________________ >STOP MORE SPAM with the new MSN 8 and get 2 months FREE* >http://join.msn.com/?page=features/junkmail > > >_______________________________________________ >Megaco mailing list >Megaco@ietf.org >https://www1.ietf.org/mailman/listinfo/megaco _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Mon Nov 17 14:41:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29836 for ; Mon, 17 Nov 2003 14:41:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALpF7-0000wR-LQ; Mon, 17 Nov 2003 14:41:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALpEk-0000w1-FZ for megaco@optimus.ietf.org; Mon, 17 Nov 2003 14:40:38 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29815 for ; Mon, 17 Nov 2003 14:40:25 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ALpEh-0004rX-00 for megaco@ietf.org; Mon, 17 Nov 2003 14:40:35 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1ALpEg-0004rB-00 for megaco@ietf.org; Mon, 17 Nov 2003 14:40:35 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAHJdvf24335 for ; Mon, 17 Nov 2003 14:39:57 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 17 Nov 2003 14:39:58 -0500 Message-ID: From: "Kevin Boyle" To: Sampath Komanduri , "'Shobhit Bansal'" , "'Harry Suede'" , megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Date: Mon, 17 Nov 2003 14:39:52 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Generally speaking, the signal complete event is for the benefit of the MGC, since it doesn't have any knowledge of exactly when a signal terminates. There are four reportable possibilities as to WHY a signal terminated: The signal reached the end of its natural duration (TO) The signals descriptor was replaced (IBS) An event was detected (IBE) Something else happened (OR) Remember that it may not be that the MGC wants to know just that the signal terminated. It may be that the MGC wants to know exactly WHEN the signal terminated. This can be determined by the timestamp on the Notify. So, returning the event is, in general, a good idea when at all possible. There arises a problem with Subtract, however. Subtract resets the values of the descriptors to a default value. This means that the Signals and Events descriptors are (generally) cleared. So the signal stops... but the event detection ALSO stops. So there is no event to be detected. This is similar to sending a Transaction where both the Signals and Events descriptors are cleared in the same Modify command -- I would think that the Notify would NOT be sent. So, in the case of ServiceChange, send the Notify as long as you have an Events descriptor that contains g/sc once the command has completed execution. Kevin _____ From: Sampath Komanduri [mailto:sampathk@cisco.com] Sent: Friday, November 14, 2003 5:31 PM To: 'Shobhit Bansal'; Boyle, Kevin [NCRTP:3Z40:EXCH]; 'Harry Suede'; megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Shobhit, My answers are based on Kevin's response to earlier mail on this issue: There are two scenarios that we should consider: a) MGC initiated termination out-of-service: MG needn't send the g/sc notification to MGC (going by Kevin's logic that MGC can derive this information). I don't know what should be MGC's behavior if it receives g/sc (with any method) after it has sent SUBTRACT or ServiceChange message but before it receives the corresponding response (Kevin ??) b) MG initiated termination out-of-service: MG needn't send the g/sc notification to MGC since (again) MGC can derive this information. Sampath -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of Shobhit Bansal Sent: Friday, November 14, 2003 10:34 AM To: Kevin Boyle; Sampath Komanduri; 'Harry Suede'; megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Hi Kevin, What should be the behaviour if a service change message is sent on the termination on which the signals were playing. Should a notification be sent to MGC in this scenario ? Thanks Shobhit Kevin Boyle wrote: It is not possible to put an Events descriptor in a Subtract command. I believe Harry raises a good point -- the subtract results in the clearing of the descriptors -- including the Events descriptor. Since the MGC issued the Subtract command, it should know that the signal halted without being told by the MG. I agree with Harry that the notification is suppressed by the Subtract command, since there is the implied reset of the Events descriptor. Kevin -----Original Message----- From: Sampath Komanduri [mailto:sampathk@cisco.com] Sent: Friday, November 14, 2003 3:47 AM To: 'Harry Suede'; megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Hi Harry, Assuming that there *wasn't* an empty events descriptor in the Subtract, MG should send a g/sc event notification with method set to "NC" (Not co! mpleted, other cause). I don't find anything specified in the protocol with respect to special handling of g/sc for Subtract. Therefore, normal handling (notify MGC if Signal playout was aborted for any reason) of g/sc should apply. Thanks, Sampath -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of Harry Suede Sent: Wednesday, November 12, 2003 3:06 AM To: megaco@ietf.org Subject: [Megaco] g/sc Notification during Subtract Hi List, A signal is being applied on a termination in Non-NULL context. Then MGC sends Subtract command on the termination. The MG will stop the signal during processing of Subtract command. Should MG send the Notify command for g/sc event with "NC" (Not completed, other cause) towards MGC? I think , since all the active descriptors shall be reset during Subtract processing, so MG should **not** send g/sc notification as Events descriptor doesn't contain g/sc at that point of time. Pls. respond. Thanks Harry. -- __________________________________________________________ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup Search Smarter - get the new eXact Search Bar for free! http://www.exactsearchbar.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 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco Yahoo! India Matrimony: Find your partner online. Post your profile. _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Mon Nov 17 14:43:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00042 for ; Mon, 17 Nov 2003 14:43:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALpH7-00016n-3V for megaco-archive@odin.ietf.org; Mon, 17 Nov 2003 14:43:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAHJh54D004255 for megaco-archive@odin.ietf.org; Mon, 17 Nov 2003 14:43:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALpH6-00016Y-UJ for megaco-web-archive@optimus.ietf.org; Mon, 17 Nov 2003 14:43:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29953 for ; Mon, 17 Nov 2003 14:42:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ALpH3-0004tt-00 for megaco-web-archive@ietf.org; Mon, 17 Nov 2003 14:43:01 -0500 Received: from manatick.foretec.com ([4.17.168.5] helo=manatick) by ietf-mx with esmtp (Exim 4.12) id 1ALpH3-0004tM-01 for megaco-web-archive@ietf.org; Mon, 17 Nov 2003 14:43:01 -0500 Received: from [132.151.6.22] (helo=optimus.ietf.org) by manatick with esmtp (Exim 4.24) id 1ALpF8-0002kH-6M for megaco-web-archive@ietf.org; Mon, 17 Nov 2003 14:41:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALpF7-0000wR-LQ; Mon, 17 Nov 2003 14:41:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALpEk-0000w1-FZ for megaco@optimus.ietf.org; Mon, 17 Nov 2003 14:40:38 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29815 for ; Mon, 17 Nov 2003 14:40:25 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ALpEh-0004rX-00 for megaco@ietf.org; Mon, 17 Nov 2003 14:40:35 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1ALpEg-0004rB-00 for megaco@ietf.org; Mon, 17 Nov 2003 14:40:35 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAHJdvf24335 for ; Mon, 17 Nov 2003 14:39:57 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 17 Nov 2003 14:39:58 -0500 Message-ID: From: "Kevin Boyle" To: Sampath Komanduri , "'Shobhit Bansal'" , "'Harry Suede'" , megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Date: Mon, 17 Nov 2003 14:39:52 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Generally speaking, the signal complete event is for the benefit of the MGC, since it doesn't have any knowledge of exactly when a signal terminates. There are four reportable possibilities as to WHY a signal terminated: The signal reached the end of its natural duration (TO) The signals descriptor was replaced (IBS) An event was detected (IBE) Something else happened (OR) Remember that it may not be that the MGC wants to know just that the signal terminated. It may be that the MGC wants to know exactly WHEN the signal terminated. This can be determined by the timestamp on the Notify. So, returning the event is, in general, a good idea when at all possible. There arises a problem with Subtract, however. Subtract resets the values of the descriptors to a default value. This means that the Signals and Events descriptors are (generally) cleared. So the signal stops... but the event detection ALSO stops. So there is no event to be detected. This is similar to sending a Transaction where both the Signals and Events descriptors are cleared in the same Modify command -- I would think that the Notify would NOT be sent. So, in the case of ServiceChange, send the Notify as long as you have an Events descriptor that contains g/sc once the command has completed execution. Kevin _____ From: Sampath Komanduri [mailto:sampathk@cisco.com] Sent: Friday, November 14, 2003 5:31 PM To: 'Shobhit Bansal'; Boyle, Kevin [NCRTP:3Z40:EXCH]; 'Harry Suede'; megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Shobhit, My answers are based on Kevin's response to earlier mail on this issue: There are two scenarios that we should consider: a) MGC initiated termination out-of-service: MG needn't send the g/sc notification to MGC (going by Kevin's logic that MGC can derive this information). I don't know what should be MGC's behavior if it receives g/sc (with any method) after it has sent SUBTRACT or ServiceChange message but before it receives the corresponding response (Kevin ??) b) MG initiated termination out-of-service: MG needn't send the g/sc notification to MGC since (again) MGC can derive this information. Sampath -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of Shobhit Bansal Sent: Friday, November 14, 2003 10:34 AM To: Kevin Boyle; Sampath Komanduri; 'Harry Suede'; megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Hi Kevin, What should be the behaviour if a service change message is sent on the termination on which the signals were playing. Should a notification be sent to MGC in this scenario ? Thanks Shobhit Kevin Boyle wrote: It is not possible to put an Events descriptor in a Subtract command. I believe Harry raises a good point -- the subtract results in the clearing of the descriptors -- including the Events descriptor. Since the MGC issued the Subtract command, it should know that the signal halted without being told by the MG. I agree with Harry that the notification is suppressed by the Subtract command, since there is the implied reset of the Events descriptor. Kevin -----Original Message----- From: Sampath Komanduri [mailto:sampathk@cisco.com] Sent: Friday, November 14, 2003 3:47 AM To: 'Harry Suede'; megaco@ietf.org Subject: RE: [Megaco] g/sc Notification during Subtract Hi Harry, Assuming that there *wasn't* an empty events descriptor in the Subtract, MG should send a g/sc event notification with method set to "NC" (Not co! mpleted, other cause). I don't find anything specified in the protocol with respect to special handling of g/sc for Subtract. Therefore, normal handling (notify MGC if Signal playout was aborted for any reason) of g/sc should apply. Thanks, Sampath -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of Harry Suede Sent: Wednesday, November 12, 2003 3:06 AM To: megaco@ietf.org Subject: [Megaco] g/sc Notification during Subtract Hi List, A signal is being applied on a termination in Non-NULL context. Then MGC sends Subtract command on the termination. The MG will stop the signal during processing of Subtract command. Should MG send the Notify command for g/sc event with "NC" (Not completed, other cause) towards MGC? I think , since all the active descriptors shall be reset during Subtract processing, so MG should **not** send g/sc notification as Events descriptor doesn't contain g/sc at that point of time. Pls. respond. Thanks Harry. -- __________________________________________________________ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup Search Smarter - get the new eXact Search Bar for free! http://www.exactsearchbar.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 _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco Yahoo! India Matrimony: Find your partner online. Post your profile. _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Tue Nov 18 15:24:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13092 for ; Tue, 18 Nov 2003 15:24:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMCOH-0005Vu-JW; Tue, 18 Nov 2003 15:24:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMCNd-0005Rz-C2 for megaco@optimus.ietf.org; Tue, 18 Nov 2003 15:23:21 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12985 for ; Tue, 18 Nov 2003 15:23:09 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMCNc-0004sD-00 for megaco@ietf.org; Tue, 18 Nov 2003 15:23:20 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AMCNb-0004ra-00 for megaco@ietf.org; Tue, 18 Nov 2003 15:23:19 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAIKMln13045 for ; Tue, 18 Nov 2003 15:22:47 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Tue, 18 Nov 2003 15:22:48 -0500 Message-ID: From: "Kevin Boyle" To: Manish Bhagwanani , megaco@ietf.org Subject: RE: [Megaco] Example of Notify on ROOT termination Date: Tue, 18 Nov 2003 15:22:45 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Properties are not autonomously sent to the MGC. The only way for MGCs to know about changes in property values is to change them itself (via a Modify) or to audit them. Notify commands only carry observed events. There is at least one standardized package that has an event meant for Root. See H.248.14. Kevin _____ From: Manish Bhagwanani [mailto:mbhagwanani@ipnetfusion.com] Sent: Friday, November 14, 2003 2:29 PM To: megaco@ietf.org Subject: [Megaco] Example of Notify on ROOT termination Can anyone give an example of what package/event can be sent for a ROOT termination in a Notify command? Can one of the property parms in the root package be modified and sent back by the Media Gateway ? Thanks, Manish Bhagwanani _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Tue Nov 18 15:24:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13107 for ; Tue, 18 Nov 2003 15:24:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMCOL-0005XF-IH for megaco-archive@odin.ietf.org; Tue, 18 Nov 2003 15:24:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAIKO5Ut021273 for megaco-archive@odin.ietf.org; Tue, 18 Nov 2003 15:24:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMCOL-0005X2-DS for megaco-web-archive@optimus.ietf.org; Tue, 18 Nov 2003 15:24:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13065 for ; Tue, 18 Nov 2003 15:23:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMCOK-0004tM-00 for megaco-web-archive@ietf.org; Tue, 18 Nov 2003 15:24:04 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AMCOJ-0004tH-00 for megaco-web-archive@ietf.org; Tue, 18 Nov 2003 15:24:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMCOH-0005Vu-JW; Tue, 18 Nov 2003 15:24:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMCNd-0005Rz-C2 for megaco@optimus.ietf.org; Tue, 18 Nov 2003 15:23:21 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12985 for ; Tue, 18 Nov 2003 15:23:09 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMCNc-0004sD-00 for megaco@ietf.org; Tue, 18 Nov 2003 15:23:20 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AMCNb-0004ra-00 for megaco@ietf.org; Tue, 18 Nov 2003 15:23:19 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAIKMln13045 for ; Tue, 18 Nov 2003 15:22:47 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Tue, 18 Nov 2003 15:22:48 -0500 Message-ID: From: "Kevin Boyle" To: Manish Bhagwanani , megaco@ietf.org Subject: RE: [Megaco] Example of Notify on ROOT termination Date: Tue, 18 Nov 2003 15:22:45 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Properties are not autonomously sent to the MGC. The only way for MGCs to know about changes in property values is to change them itself (via a Modify) or to audit them. Notify commands only carry observed events. There is at least one standardized package that has an event meant for Root. See H.248.14. Kevin _____ From: Manish Bhagwanani [mailto:mbhagwanani@ipnetfusion.com] Sent: Friday, November 14, 2003 2:29 PM To: megaco@ietf.org Subject: [Megaco] Example of Notify on ROOT termination Can anyone give an example of what package/event can be sent for a ROOT termination in a Notify command? Can one of the property parms in the root package be modified and sent back by the Media Gateway ? Thanks, Manish Bhagwanani _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Tue Nov 18 16:13:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16466 for ; Tue, 18 Nov 2003 16:13:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMD9j-00008t-SY; Tue, 18 Nov 2003 16:13:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMD9D-00007Z-Dt for megaco@optimus.ietf.org; Tue, 18 Nov 2003 16:12:31 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16414 for ; Tue, 18 Nov 2003 16:12:19 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMD9B-0006Bt-00 for megaco@ietf.org; Tue, 18 Nov 2003 16:12:29 -0500 Received: from mails.conexion.com.py ([65.198.40.5]) by ietf-mx with esmtp (Exim 4.12) id 1AMD99-0006Bn-00 for megaco@ietf.org; Tue, 18 Nov 2003 16:12:28 -0500 Received: from carlos (mf.conexion.com.py [65.198.40.11]) by mails.conexion.com.py (8.12.8/8.12.8) with SMTP id hAILEO9Q005320; Tue, 18 Nov 2003 18:14:26 -0300 Message-ID: <003601c3adf8$6b44c6f0$6600a8c0@carlos> From: =?iso-8859-1?Q?Carlos_Rodr=EDguez_Alcal=E1_Villagra?= To: Cc: Date: Tue, 18 Nov 2003 18:21:33 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0033_01C3AE00.CBB1DC50" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 X-ConeXion-MailScanner-Information: Please contact the ISP for more information X-ConeXion-MailScanner: Found to be clean X-ConeXion-MailScanner-SpamCheck: no es spam, SpamAssassin (puntuación=1, requerido 4, SPAM_PHRASE_00_01 0.78, SUPERLONG_LINE 0.01, USER_AGENT_OE 0.18) X-ConeXion-MailScanner-SpamScore: s Subject: [Megaco] Hi Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0033_01C3AE00.CBB1DC50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi there, I have read the RFC 3525. I am interested in understanding = a little better how the RTP Termination IDs are coded. I believe I = undestood pretty well how the Termination IDs are specified for the = Physical lines. They have wildcard, trunk and line specified. And it = could have a maximum of the 8 octets. Now, what about the RTP Termination IDs. I believe they also have the = same wildcarding scheme. But, they should not have trunk and line = paremeters, rigth? So, when I send an ADD command to a GW with the RTP Termination ID set = to Choose, what are the typical values that it should return? Would the GW have something like a counter from 0 to 2^64 ? I hope I made my question clear. thanks in advance, Carlos RAV ------=_NextPart_000_0033_01C3AE00.CBB1DC50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi there,
          &nbs= p; =20 I have read the RFC 3525. I am interested in understanding a little = better how=20 the RTP Termination IDs are coded. I believe I undestood pretty well how = the=20 Termination IDs are specified for the Physical lines. They have = wildcard, trunk=20 and line specified. And it could have a maximum of the 8 = octets.
Now, what about the RTP Termination = IDs. I believe=20 they also have the same wildcarding scheme. But, they should not have = trunk and=20 line paremeters, rigth?
So, when I send an ADD command to a GW = with the RTP=20 Termination ID set to Choose, what are the typical values that it should = return?
Would the GW have something like a = counter from 0=20 to 2^64 ?
I hope I made my question = clear.
          &nbs= p;            = ;  =20 thanks in advance,
          &nbs= p;            = ;            =             &= nbsp;        =20 Carlos RAV
------=_NextPart_000_0033_01C3AE00.CBB1DC50-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Tue Nov 18 16:13:30 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16488 for ; Tue, 18 Nov 2003 16:13:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMD9p-0000EZ-H1 for megaco-archive@odin.ietf.org; Tue, 18 Nov 2003 16:13:11 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAILD9SL000893 for megaco-archive@odin.ietf.org; Tue, 18 Nov 2003 16:13:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMD9p-0000Br-8v for megaco-web-archive@optimus.ietf.org; Tue, 18 Nov 2003 16:13:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16441 for ; Tue, 18 Nov 2003 16:12:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMD9k-0006Cj-00 for megaco-web-archive@ietf.org; Tue, 18 Nov 2003 16:13:04 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AMD9k-0006Cg-00 for megaco-web-archive@ietf.org; Tue, 18 Nov 2003 16:13:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMD9j-00008t-SY; Tue, 18 Nov 2003 16:13:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMD9D-00007Z-Dt for megaco@optimus.ietf.org; Tue, 18 Nov 2003 16:12:31 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16414 for ; Tue, 18 Nov 2003 16:12:19 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMD9B-0006Bt-00 for megaco@ietf.org; Tue, 18 Nov 2003 16:12:29 -0500 Received: from mails.conexion.com.py ([65.198.40.5]) by ietf-mx with esmtp (Exim 4.12) id 1AMD99-0006Bn-00 for megaco@ietf.org; Tue, 18 Nov 2003 16:12:28 -0500 Received: from carlos (mf.conexion.com.py [65.198.40.11]) by mails.conexion.com.py (8.12.8/8.12.8) with SMTP id hAILEO9Q005320; Tue, 18 Nov 2003 18:14:26 -0300 Message-ID: <003601c3adf8$6b44c6f0$6600a8c0@carlos> From: =?iso-8859-1?Q?Carlos_Rodr=EDguez_Alcal=E1_Villagra?= To: Cc: Date: Tue, 18 Nov 2003 18:21:33 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0033_01C3AE00.CBB1DC50" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 X-ConeXion-MailScanner-Information: Please contact the ISP for more information X-ConeXion-MailScanner: Found to be clean X-ConeXion-MailScanner-SpamCheck: no es spam, SpamAssassin (puntuación=1, requerido 4, SPAM_PHRASE_00_01 0.78, SUPERLONG_LINE 0.01, USER_AGENT_OE 0.18) X-ConeXion-MailScanner-SpamScore: s Subject: [Megaco] Hi Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0033_01C3AE00.CBB1DC50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi there, I have read the RFC 3525. I am interested in understanding = a little better how the RTP Termination IDs are coded. I believe I = undestood pretty well how the Termination IDs are specified for the = Physical lines. They have wildcard, trunk and line specified. And it = could have a maximum of the 8 octets. Now, what about the RTP Termination IDs. I believe they also have the = same wildcarding scheme. But, they should not have trunk and line = paremeters, rigth? So, when I send an ADD command to a GW with the RTP Termination ID set = to Choose, what are the typical values that it should return? Would the GW have something like a counter from 0 to 2^64 ? I hope I made my question clear. thanks in advance, Carlos RAV ------=_NextPart_000_0033_01C3AE00.CBB1DC50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi there,
          &nbs= p; =20 I have read the RFC 3525. I am interested in understanding a little = better how=20 the RTP Termination IDs are coded. I believe I undestood pretty well how = the=20 Termination IDs are specified for the Physical lines. They have = wildcard, trunk=20 and line specified. And it could have a maximum of the 8 = octets.
Now, what about the RTP Termination = IDs. I believe=20 they also have the same wildcarding scheme. But, they should not have = trunk and=20 line paremeters, rigth?
So, when I send an ADD command to a GW = with the RTP=20 Termination ID set to Choose, what are the typical values that it should = return?
Would the GW have something like a = counter from 0=20 to 2^64 ?
I hope I made my question = clear.
          &nbs= p;            = ;  =20 thanks in advance,
          &nbs= p;            = ;            =             &= nbsp;        =20 Carlos RAV
------=_NextPart_000_0033_01C3AE00.CBB1DC50-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Wed Nov 19 00:53:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07936 for ; Wed, 19 Nov 2003 00:53:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMLGv-0001yI-Ds; Wed, 19 Nov 2003 00:53:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMLG2-0001vy-0B for megaco@optimus.ietf.org; Wed, 19 Nov 2003 00:52:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07931 for ; Wed, 19 Nov 2003 00:51:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMLFz-0000t6-00 for megaco@ietf.org; Wed, 19 Nov 2003 00:52:03 -0500 Received: from nwd2mail2.analog.com ([137.71.25.51]) by ietf-mx with esmtp (Exim 4.12) id 1AMLFy-0000t3-00 for megaco@ietf.org; Wed, 19 Nov 2003 00:52:02 -0500 Received: from nwd2mhb1.analog.com (nwd2mhb1.analog.com [137.71.5.12]) by nwd2mail2.analog.com (8.12.10/8.12.10) with ESMTP id hAJ5pnV8002276 for ; Wed, 19 Nov 2003 00:52:09 -0500 Received: from jasmine.cpgindia.analog.com ([137.71.32.30]) by nwd2mhb1.analog.com (8.9.3 (PHNE_28810+JAGae91741)/8.9.3) with ESMTP id AAA14879 for ; Wed, 19 Nov 2003 00:31:54 -0500 (EST) Received: from kumard01 ([137.71.32.241]) by jasmine.cpgindia.analog.com (8.9.1/8.9.1) with SMTP id LAA14615 for ; Wed, 19 Nov 2003 11:11:27 +0530 (IST) From: "Kumar.U." To: Date: Wed, 19 Nov 2003 11:14:04 +0530 Message-ID: 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) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 X-Spam-Status: No, hits=0.0 required=10.0 tests=none version=2.60 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) X-Scanned-By: MIMEDefang 2.38 Content-Transfer-Encoding: 7bit Subject: [Megaco] when do I send TransactionResponseAck Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi All, We are implementing megaco MG with UDP and TCP as underlying transport layers. Sending TransactionResponseAck is little bit of confusing for me. When do I send TransactionResponseAck? .I feel that we need to send TransactionResponseAck when the underlying transport layer is UDP. Is it correct? Please clarify me on this. Thanks & Regards, Kumaraswamy.U. Senior S/W engineer, Analog Devices, INDIA. _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Wed Nov 19 00:54:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07969 for ; Wed, 19 Nov 2003 00:54:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMLHv-00028p-Nw for megaco-archive@odin.ietf.org; Wed, 19 Nov 2003 00:54:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJ5s3Yl008225 for megaco-archive@odin.ietf.org; Wed, 19 Nov 2003 00:54:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMLHv-00028a-E2 for megaco-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 00:54:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07956 for ; Wed, 19 Nov 2003 00:53:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMLHs-0000tS-00 for megaco-web-archive@ietf.org; Wed, 19 Nov 2003 00:54:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AMLHs-0000tA-00 for megaco-web-archive@ietf.org; Wed, 19 Nov 2003 00:54:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMLGv-0001yI-Ds; Wed, 19 Nov 2003 00:53:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMLG2-0001vy-0B for megaco@optimus.ietf.org; Wed, 19 Nov 2003 00:52:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07931 for ; Wed, 19 Nov 2003 00:51:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMLFz-0000t6-00 for megaco@ietf.org; Wed, 19 Nov 2003 00:52:03 -0500 Received: from nwd2mail2.analog.com ([137.71.25.51]) by ietf-mx with esmtp (Exim 4.12) id 1AMLFy-0000t3-00 for megaco@ietf.org; Wed, 19 Nov 2003 00:52:02 -0500 Received: from nwd2mhb1.analog.com (nwd2mhb1.analog.com [137.71.5.12]) by nwd2mail2.analog.com (8.12.10/8.12.10) with ESMTP id hAJ5pnV8002276 for ; Wed, 19 Nov 2003 00:52:09 -0500 Received: from jasmine.cpgindia.analog.com ([137.71.32.30]) by nwd2mhb1.analog.com (8.9.3 (PHNE_28810+JAGae91741)/8.9.3) with ESMTP id AAA14879 for ; Wed, 19 Nov 2003 00:31:54 -0500 (EST) Received: from kumard01 ([137.71.32.241]) by jasmine.cpgindia.analog.com (8.9.1/8.9.1) with SMTP id LAA14615 for ; Wed, 19 Nov 2003 11:11:27 +0530 (IST) From: "Kumar.U." To: Date: Wed, 19 Nov 2003 11:14:04 +0530 Message-ID: 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) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 X-Spam-Status: No, hits=0.0 required=10.0 tests=none version=2.60 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) X-Scanned-By: MIMEDefang 2.38 Content-Transfer-Encoding: 7bit Subject: [Megaco] when do I send TransactionResponseAck Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi All, We are implementing megaco MG with UDP and TCP as underlying transport layers. Sending TransactionResponseAck is little bit of confusing for me. When do I send TransactionResponseAck? .I feel that we need to send TransactionResponseAck when the underlying transport layer is UDP. Is it correct? Please clarify me on this. Thanks & Regards, Kumaraswamy.U. Senior S/W engineer, Analog Devices, INDIA. _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Wed Nov 19 02:10:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19383 for ; Wed, 19 Nov 2003 02:10:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMMTT-00061c-4f; Wed, 19 Nov 2003 02:10:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMMTF-0005yF-UA for megaco@optimus.ietf.org; Wed, 19 Nov 2003 02:09:49 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18600 for ; Wed, 19 Nov 2003 02:09:36 -0500 (EST) From: rui.suying@zte.com.cn Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMMTC-0001h3-00 for megaco@ietf.org; Wed, 19 Nov 2003 02:09:46 -0500 Received: from [210.21.227.66] (helo=zte.com.cn) by ietf-mx with esmtp (Exim 4.12) id 1AMMTB-0001gR-00 for megaco@ietf.org; Wed, 19 Nov 2003 02:09:45 -0500 To: MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.0 September 26, 2002 Message-ID: Date: Wed, 19 Nov 2003 14:36:28 +0800 X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 5.0.8 |June 18, 2001) at 2003-11-19 15:11:27, Serialize complete at 2003-11-19 15:11:27 Content-Type: multipart/alternative; boundary="=_alternative 002473E548256DE3_=" Subject: [Megaco] a Question about Pakcage andisp Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , This is a multipart message in MIME format. --=_alternative 002473E548256DE3_= Content-Type: text/plain; charset="US-ASCII" where can i get the description of parameter ddb? what is the meaning of "ddb"? for example: the following is a fraction of a H.248 message, Signals{andisp/dwa{ddb=802001083035313831363135020A3931393535353030303007084A6F686E20446F65D5,pattern=1}} when MG receives h.248 message including it, how does MG get the information included in the parameter "ddb"? thanks in advance! ********************************************** Rui Suying SoftSwitch Software Design Department Nanjing R&D Center ZTE Co. China Tel(O): 025-2871358 Mobile: 13851939625 ********************************************** --=_alternative 002473E548256DE3_= Content-Type: text/html; charset="US-ASCII"
where can i get the description of parameter ddb? what is the meaning of "ddb"?

for example:
the following is a fraction of a H.248 message,

Signals{andisp/dwa{ddb=802001083035313831363135020A3931393535353030303007084A6F686E20446F65D5,pattern=1}}

when MG receives h.248 message including it, how does MG get the information included in the parameter "ddb"?

thanks in advance!



**********************************************
                Rui Suying
   SoftSwitch Software Design Department
            Nanjing R&D Center
                ZTE Co. China
              Tel(O): 025-2871358
              Mobile: 13851939625    
**********************************************
 --=_alternative 002473E548256DE3_=-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Wed Nov 19 02:10:29 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19467 for ; Wed, 19 Nov 2003 02:10:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMMTa-00063F-EU for megaco-archive@odin.ietf.org; Wed, 19 Nov 2003 02:10:11 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJ7AANq023230 for megaco-archive@odin.ietf.org; Wed, 19 Nov 2003 02:10:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMMTY-00062b-OF for megaco-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 02:10:08 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18907 for ; Wed, 19 Nov 2003 02:09:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMMTU-0001hu-00 for megaco-web-archive@ietf.org; Wed, 19 Nov 2003 02:10:05 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AMMTU-0001hq-00 for megaco-web-archive@ietf.org; Wed, 19 Nov 2003 02:10:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMMTT-00061c-4f; Wed, 19 Nov 2003 02:10:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMMTF-0005yF-UA for megaco@optimus.ietf.org; Wed, 19 Nov 2003 02:09:49 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18600 for ; Wed, 19 Nov 2003 02:09:36 -0500 (EST) From: rui.suying@zte.com.cn Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMMTC-0001h3-00 for megaco@ietf.org; Wed, 19 Nov 2003 02:09:46 -0500 Received: from [210.21.227.66] (helo=zte.com.cn) by ietf-mx with esmtp (Exim 4.12) id 1AMMTB-0001gR-00 for megaco@ietf.org; Wed, 19 Nov 2003 02:09:45 -0500 To: MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.0 September 26, 2002 Message-ID: Date: Wed, 19 Nov 2003 14:36:28 +0800 X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 5.0.8 |June 18, 2001) at 2003-11-19 15:11:27, Serialize complete at 2003-11-19 15:11:27 Content-Type: multipart/alternative; boundary="=_alternative 002473E548256DE3_=" Subject: [Megaco] a Question about Pakcage andisp Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , This is a multipart message in MIME format. --=_alternative 002473E548256DE3_= Content-Type: text/plain; charset="US-ASCII" where can i get the description of parameter ddb? what is the meaning of "ddb"? for example: the following is a fraction of a H.248 message, Signals{andisp/dwa{ddb=802001083035313831363135020A3931393535353030303007084A6F686E20446F65D5,pattern=1}} when MG receives h.248 message including it, how does MG get the information included in the parameter "ddb"? thanks in advance! ********************************************** Rui Suying SoftSwitch Software Design Department Nanjing R&D Center ZTE Co. China Tel(O): 025-2871358 Mobile: 13851939625 ********************************************** --=_alternative 002473E548256DE3_= Content-Type: text/html; charset="US-ASCII"
where can i get the description of parameter ddb? what is the meaning of "ddb"?

for example:
the following is a fraction of a H.248 message,

Signals{andisp/dwa{ddb=802001083035313831363135020A3931393535353030303007084A6F686E20446F65D5,pattern=1}}

when MG receives h.248 message including it, how does MG get the information included in the parameter "ddb"?

thanks in advance!



**********************************************
                Rui Suying
   SoftSwitch Software Design Department
            Nanjing R&D Center
                ZTE Co. China
              Tel(O): 025-2871358
              Mobile: 13851939625    
**********************************************
 --=_alternative 002473E548256DE3_=-- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Wed Nov 19 10:12:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20629 for ; Wed, 19 Nov 2003 10:12:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMTzt-0008MB-4P; Wed, 19 Nov 2003 10:12:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMTzO-0008LN-FV for megaco@optimus.ietf.org; Wed, 19 Nov 2003 10:11:32 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20488 for ; Wed, 19 Nov 2003 10:11:16 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMTzM-0000oe-00 for megaco@ietf.org; Wed, 19 Nov 2003 10:11:28 -0500 Received: from ihemail2.lucent.com ([192.11.222.163] helo=ihemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AMTzL-0000o1-00 for megaco@ietf.org; Wed, 19 Nov 2003 10:11:27 -0500 Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3]) by ihemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hAJFArE14354 for ; Wed, 19 Nov 2003 09:10:53 -0600 (CST) Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id KAA29997; Wed, 19 Nov 2003 10:11:12 -0500 (EST) Cc: megaco@ietf.org Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id KAA29988; Wed, 19 Nov 2003 10:11:09 -0500 (EST) Message-ID: <3FBB886A.8030202@bell-labs.com> Date: Wed, 19 Nov 2003 10:12:42 -0500 From: Troy Cauble User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: rui.suying@zte.com.cn Original-CC: megaco@ietf.org Subject: Re: [Megaco] a Question about Pakcage andisp References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit rui.suying@zte.com.cn wrote: > > where can i get the description of parameter ddb? what is the meaning of > "ddb"? > > for example: > the following is a fraction of a H.248 message, > > Signals{andisp/dwa{ddb=802001083035313831363135020A3931393535353030303007084A6F686E20446F65D5,pattern=1}} ddb is a ascii hex encoding of a binary MDMF message. MDMF is defined in a Telcordia spec titled GR-30-CORE. (BTW, the checksum in the example is wrong.) -troy _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Wed Nov 19 10:12:34 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20657 for ; Wed, 19 Nov 2003 10:12:34 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMU01-0008TL-9X for megaco-archive@odin.ietf.org; Wed, 19 Nov 2003 10:12:18 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJFC9ec032561 for megaco-archive@odin.ietf.org; Wed, 19 Nov 2003 10:12:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMU01-0008T6-3W for megaco-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 10:12:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20549 for ; Wed, 19 Nov 2003 10:11:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMTzy-0000pB-00 for megaco-web-archive@ietf.org; Wed, 19 Nov 2003 10:12:06 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AMTzy-0000p8-00 for megaco-web-archive@ietf.org; Wed, 19 Nov 2003 10:12:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMTzt-0008MB-4P; Wed, 19 Nov 2003 10:12:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMTzO-0008LN-FV for megaco@optimus.ietf.org; Wed, 19 Nov 2003 10:11:32 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20488 for ; Wed, 19 Nov 2003 10:11:16 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMTzM-0000oe-00 for megaco@ietf.org; Wed, 19 Nov 2003 10:11:28 -0500 Received: from ihemail2.lucent.com ([192.11.222.163] helo=ihemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AMTzL-0000o1-00 for megaco@ietf.org; Wed, 19 Nov 2003 10:11:27 -0500 Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3]) by ihemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hAJFArE14354 for ; Wed, 19 Nov 2003 09:10:53 -0600 (CST) Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id KAA29997; Wed, 19 Nov 2003 10:11:12 -0500 (EST) Cc: megaco@ietf.org Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2) id KAA29988; Wed, 19 Nov 2003 10:11:09 -0500 (EST) Message-ID: <3FBB886A.8030202@bell-labs.com> Date: Wed, 19 Nov 2003 10:12:42 -0500 From: Troy Cauble User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: rui.suying@zte.com.cn Original-CC: megaco@ietf.org Subject: Re: [Megaco] a Question about Pakcage andisp References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit rui.suying@zte.com.cn wrote: > > where can i get the description of parameter ddb? what is the meaning of > "ddb"? > > for example: > the following is a fraction of a H.248 message, > > Signals{andisp/dwa{ddb=802001083035313831363135020A3931393535353030303007084A6F686E20446F65D5,pattern=1}} ddb is a ascii hex encoding of a binary MDMF message. MDMF is defined in a Telcordia spec titled GR-30-CORE. (BTW, the checksum in the example is wrong.) -troy _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Thu Nov 20 00:19:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04186 for ; Thu, 20 Nov 2003 00:19:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMhDZ-0004sN-Uq; Thu, 20 Nov 2003 00:19:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMhD8-0004rb-LZ for megaco@optimus.ietf.org; Thu, 20 Nov 2003 00:18:34 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04147 for ; Thu, 20 Nov 2003 00:18:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMhD6-0003ez-00 for megaco@ietf.org; Thu, 20 Nov 2003 00:18:32 -0500 Received: from ish7.ericsson.com.au ([61.88.9.195]) by ietf-mx with esmtp (Exim 4.12) id 1AMhD5-0003eb-00 for megaco@ietf.org; Thu, 20 Nov 2003 00:18:31 -0500 Received: from eaubrnt019.epa.ericsson.se ([146.11.31.193]) by ish7.ericsson.com.au (8.11.7+Sun/8.11.7) with ESMTP id hAK5F5p18701; Thu, 20 Nov 2003 16:15:05 +1100 (EST) Received: from ericsson.com.au (146.11.245.200 [146.11.245.200]) by eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id WPNB4M9Y; Thu, 20 Nov 2003 16:16:30 +1100 Message-ID: <3FBC0857.5070303@ericsson.com.au> Date: Thu, 20 Nov 2003 11:18:31 +1100 From: Christian Groves User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Kumar.U." CC: megaco@ietf.org Subject: Re: [Megaco] when do I send TransactionResponseAck References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hello Kumar, You are correct that TransactionResponseAck is sent for UDP ie. "D.1.2.2 Three-way handshake". For TCP you have a choice whether to implement it or not. ie. D.2.2 Christian Kumar.U. wrote: > Hi All, > We are implementing megaco MG with UDP and TCP as underlying transport > layers. Sending TransactionResponseAck is little bit of confusing for me. > When do I send TransactionResponseAck? .I feel that we need to send > TransactionResponseAck when the underlying transport layer is UDP. Is it > correct? Please clarify me on this. > > Thanks & Regards, > Kumaraswamy.U. > Senior S/W engineer, > Analog Devices, INDIA. > > > _______________________________________________ > 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 exim@www1.ietf.org Thu Nov 20 00:19:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04213 for ; Thu, 20 Nov 2003 00:19:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMhDd-0004vA-P6 for megaco-archive@odin.ietf.org; Thu, 20 Nov 2003 00:19:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAK5J5wt018910 for megaco-archive@odin.ietf.org; Thu, 20 Nov 2003 00:19:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMhDd-0004uu-KH for megaco-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 00:19:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04168 for ; Thu, 20 Nov 2003 00:18:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMhDa-0003fX-00 for megaco-web-archive@ietf.org; Thu, 20 Nov 2003 00:19:02 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AMhDa-0003fO-00 for megaco-web-archive@ietf.org; Thu, 20 Nov 2003 00:19:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMhDZ-0004s4-3k; Thu, 20 Nov 2003 00:19:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMhCb-0004rJ-T2 for megaco@optimus.ietf.org; Thu, 20 Nov 2003 00:18:02 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04134 for ; Thu, 20 Nov 2003 00:17:47 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMhCZ-0003eT-00 for megaco@ietf.org; Thu, 20 Nov 2003 00:17:59 -0500 Received: from ish7.ericsson.com.au ([61.88.9.195]) by ietf-mx with esmtp (Exim 4.12) id 1AMhCY-0003dy-00 for megaco@ietf.org; Thu, 20 Nov 2003 00:17:58 -0500 Received: from eaubrnt019.epa.ericsson.se ([146.11.31.193]) by ish7.ericsson.com.au (8.11.7+Sun/8.11.7) with ESMTP id hAK5Dxp18667; Thu, 20 Nov 2003 16:14:02 +1100 (EST) Received: from ericsson.com.au (146.11.245.200 [146.11.245.200]) by eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id WPNB4M9V; Thu, 20 Nov 2003 16:16:23 +1100 Message-ID: <3FBC06B7.2040504@ericsson.com.au> Date: Thu, 20 Nov 2003 11:11:35 +1100 From: Christian Groves User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rasool Wani CC: megaco@ietf.org Subject: Re: [Megaco] Alternate Properties in Annex C.11 SDP equivalent and C.1---etc properties References: <003001c3aa61$fff39910$c1a110ac@cn.utstar.com> In-Reply-To: <003001c3aa61$fff39910$c1a110ac@cn.utstar.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello Rasool, For the binary implementation Silencesupp (1008) would be preferential. C.11 was added so that element described in SDP and not in Annex C could be still sent by binary H.248.1. Christian Rasool Wani wrote: > hi all, > can any body help me to understand the following. > 1. what is the reason of having alternate properties in > AnnexC-C.1------- etc and Annex C-C.11 SDP equivalent properties. > For e.g.. a=silenceSupp in sdp and Silencesupp(1008) in C.1. > 2. Shall protocol support the both the alternatives to convey the Media > related information.if yes, then in which context two methods are > differentiated. > Thanks, > Rasool Wani > > _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Thu Nov 20 01:08:00 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04187 for ; Thu, 20 Nov 2003 00:19:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMhDZ-0004s4-3k; Thu, 20 Nov 2003 00:19:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMhCb-0004rJ-T2 for megaco@optimus.ietf.org; Thu, 20 Nov 2003 00:18:02 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04134 for ; Thu, 20 Nov 2003 00:17:47 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMhCZ-0003eT-00 for megaco@ietf.org; Thu, 20 Nov 2003 00:17:59 -0500 Received: from ish7.ericsson.com.au ([61.88.9.195]) by ietf-mx with esmtp (Exim 4.12) id 1AMhCY-0003dy-00 for megaco@ietf.org; Thu, 20 Nov 2003 00:17:58 -0500 Received: from eaubrnt019.epa.ericsson.se ([146.11.31.193]) by ish7.ericsson.com.au (8.11.7+Sun/8.11.7) with ESMTP id hAK5Dxp18667; Thu, 20 Nov 2003 16:14:02 +1100 (EST) Received: from ericsson.com.au (146.11.245.200 [146.11.245.200]) by eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id WPNB4M9V; Thu, 20 Nov 2003 16:16:23 +1100 Message-ID: <3FBC06B7.2040504@ericsson.com.au> Date: Thu, 20 Nov 2003 11:11:35 +1100 From: Christian Groves User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rasool Wani CC: megaco@ietf.org Subject: Re: [Megaco] Alternate Properties in Annex C.11 SDP equivalent and C.1---etc properties References: <003001c3aa61$fff39910$c1a110ac@cn.utstar.com> In-Reply-To: <003001c3aa61$fff39910$c1a110ac@cn.utstar.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hello Rasool, For the binary implementation Silencesupp (1008) would be preferential. C.11 was added so that element described in SDP and not in Annex C could be still sent by binary H.248.1. Christian Rasool Wani wrote: > hi all, > can any body help me to understand the following. > 1. what is the reason of having alternate properties in > AnnexC-C.1------- etc and Annex C-C.11 SDP equivalent properties. > For e.g.. a=silenceSupp in sdp and Silencesupp(1008) in C.1. > 2. Shall protocol support the both the alternatives to convey the Media > related information.if yes, then in which context two methods are > differentiated. > Thanks, > Rasool Wani > > _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Thu Nov 20 01:08:01 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04214 for ; Thu, 20 Nov 2003 00:19:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMhDd-0004vP-Sk for megaco-archive@odin.ietf.org; Thu, 20 Nov 2003 00:19:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAK5J5ln018925 for megaco-archive@odin.ietf.org; Thu, 20 Nov 2003 00:19:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMhDd-0004uv-Nl for megaco-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 00:19:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04170 for ; Thu, 20 Nov 2003 00:18:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMhDa-0003fa-00 for megaco-web-archive@ietf.org; Thu, 20 Nov 2003 00:19:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AMhDa-0003fP-00 for megaco-web-archive@ietf.org; Thu, 20 Nov 2003 00:19:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMhDZ-0004sN-Uq; Thu, 20 Nov 2003 00:19:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMhD8-0004rb-LZ for megaco@optimus.ietf.org; Thu, 20 Nov 2003 00:18:34 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04147 for ; Thu, 20 Nov 2003 00:18:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMhD6-0003ez-00 for megaco@ietf.org; Thu, 20 Nov 2003 00:18:32 -0500 Received: from ish7.ericsson.com.au ([61.88.9.195]) by ietf-mx with esmtp (Exim 4.12) id 1AMhD5-0003eb-00 for megaco@ietf.org; Thu, 20 Nov 2003 00:18:31 -0500 Received: from eaubrnt019.epa.ericsson.se ([146.11.31.193]) by ish7.ericsson.com.au (8.11.7+Sun/8.11.7) with ESMTP id hAK5F5p18701; Thu, 20 Nov 2003 16:15:05 +1100 (EST) Received: from ericsson.com.au (146.11.245.200 [146.11.245.200]) by eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id WPNB4M9Y; Thu, 20 Nov 2003 16:16:30 +1100 Message-ID: <3FBC0857.5070303@ericsson.com.au> Date: Thu, 20 Nov 2003 11:18:31 +1100 From: Christian Groves User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Kumar.U." CC: megaco@ietf.org Subject: Re: [Megaco] when do I send TransactionResponseAck References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello Kumar, You are correct that TransactionResponseAck is sent for UDP ie. "D.1.2.2 Three-way handshake". For TCP you have a choice whether to implement it or not. ie. D.2.2 Christian Kumar.U. wrote: > Hi All, > We are implementing megaco MG with UDP and TCP as underlying transport > layers. Sending TransactionResponseAck is little bit of confusing for me. > When do I send TransactionResponseAck? .I feel that we need to send > TransactionResponseAck when the underlying transport layer is UDP. Is it > correct? Please clarify me on this. > > Thanks & Regards, > Kumaraswamy.U. > Senior S/W engineer, > Analog Devices, INDIA. > > > _______________________________________________ > 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-admin@ietf.org Thu Nov 20 01:44:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06474 for ; Thu, 20 Nov 2003 01:44:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMiXp-0000Ng-4G; Thu, 20 Nov 2003 01:44:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMiX3-0000NI-Uk for megaco@optimus.ietf.org; Thu, 20 Nov 2003 01:43:13 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06460 for ; Thu, 20 Nov 2003 01:43:01 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMiX1-0004bi-00 for megaco@ietf.org; Thu, 20 Nov 2003 01:43:11 -0500 Received: from india-ironport-1.cisco.com ([64.104.129.195]) by ietf-mx with esmtp (Exim 4.12) id 1AMiX0-0004bV-00 for megaco@ietf.org; Thu, 20 Nov 2003 01:43:11 -0500 Received: from cisco.com (64.104.129.221) by india-ironport-1.cisco.com with ESMTP; 20 Nov 2003 12:22:29 +0530 Received: from samrat.cisco.com (samrat.cisco.com [192.135.241.21]) by india-msg-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAKCAF0s017429; Thu, 20 Nov 2003 12:10:15 GMT Received: from aniljw2k02 (dhcp-10-77-5-221.cisco.com [10.77.5.221]) by samrat.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id MAA05746; Thu, 20 Nov 2003 12:12:42 +0530 (IST) Reply-To: From: "Anil Jangam \(anilj\)" To: "'Kumar.U.'" , Subject: RE: [Megaco] when do I send TransactionResponseAck Date: Thu, 20 Nov 2003 12:12:35 +0530 Message-ID: <000001c3af31$7ba5af20$dd054d0a@apac.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi kumar, TransactionResponseAck is part of Three-way-handshake process, refer to D.1.2@rfc3525 broadly falling under the ALF. It is sent under two different cases. First when the ImmAckRequiredToken is explicitly specified in a TransactionReply and in second case when a provisional response for a Transaction Request is received, upon reception of final response, the TransactionResponseAck is sent. Refer to the appropriate sections of the rfc for more details. /anil. > -----Original Message----- > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On > Behalf Of Kumar.U. > Sent: Wednesday, November 19, 2003 11:14 AM > To: megaco@ietf.org > Subject: [Megaco] when do I send TransactionResponseAck > > > Hi All, > We are implementing megaco MG with UDP and TCP as > underlying transport layers. Sending TransactionResponseAck > is little bit of confusing for me. When do I send > TransactionResponseAck? .I feel that we need to send > TransactionResponseAck when the underlying transport layer is > UDP. Is it correct? Please clarify me on this. > > Thanks & Regards, > Kumaraswamy.U. > Senior S/W engineer, > Analog Devices, INDIA. > > > _______________________________________________ > 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 exim@www1.ietf.org Thu Nov 20 01:44:25 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06489 for ; Thu, 20 Nov 2003 01:44:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMiXv-0000P7-OO for megaco-archive@odin.ietf.org; Thu, 20 Nov 2003 01:44:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAK6i7sT001549 for megaco-archive@odin.ietf.org; Thu, 20 Nov 2003 01:44:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMiXv-0000Ot-IP for megaco-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 01:44:07 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06465 for ; Thu, 20 Nov 2003 01:43:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMiXt-0004bs-00 for megaco-web-archive@ietf.org; Thu, 20 Nov 2003 01:44:05 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AMiXs-0004bo-00 for megaco-web-archive@ietf.org; Thu, 20 Nov 2003 01:44:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMiXp-0000Ng-4G; Thu, 20 Nov 2003 01:44:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMiX3-0000NI-Uk for megaco@optimus.ietf.org; Thu, 20 Nov 2003 01:43:13 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06460 for ; Thu, 20 Nov 2003 01:43:01 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMiX1-0004bi-00 for megaco@ietf.org; Thu, 20 Nov 2003 01:43:11 -0500 Received: from india-ironport-1.cisco.com ([64.104.129.195]) by ietf-mx with esmtp (Exim 4.12) id 1AMiX0-0004bV-00 for megaco@ietf.org; Thu, 20 Nov 2003 01:43:11 -0500 Received: from cisco.com (64.104.129.221) by india-ironport-1.cisco.com with ESMTP; 20 Nov 2003 12:22:29 +0530 Received: from samrat.cisco.com (samrat.cisco.com [192.135.241.21]) by india-msg-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAKCAF0s017429; Thu, 20 Nov 2003 12:10:15 GMT Received: from aniljw2k02 (dhcp-10-77-5-221.cisco.com [10.77.5.221]) by samrat.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id MAA05746; Thu, 20 Nov 2003 12:12:42 +0530 (IST) Reply-To: From: "Anil Jangam \(anilj\)" To: "'Kumar.U.'" , Subject: RE: [Megaco] when do I send TransactionResponseAck Date: Thu, 20 Nov 2003 12:12:35 +0530 Message-ID: <000001c3af31$7ba5af20$dd054d0a@apac.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi kumar, TransactionResponseAck is part of Three-way-handshake process, refer to D.1.2@rfc3525 broadly falling under the ALF. It is sent under two different cases. First when the ImmAckRequiredToken is explicitly specified in a TransactionReply and in second case when a provisional response for a Transaction Request is received, upon reception of final response, the TransactionResponseAck is sent. Refer to the appropriate sections of the rfc for more details. /anil. > -----Original Message----- > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On > Behalf Of Kumar.U. > Sent: Wednesday, November 19, 2003 11:14 AM > To: megaco@ietf.org > Subject: [Megaco] when do I send TransactionResponseAck > > > Hi All, > We are implementing megaco MG with UDP and TCP as > underlying transport layers. Sending TransactionResponseAck > is little bit of confusing for me. When do I send > TransactionResponseAck? .I feel that we need to send > TransactionResponseAck when the underlying transport layer is > UDP. Is it correct? Please clarify me on this. > > Thanks & Regards, > Kumaraswamy.U. > Senior S/W engineer, > Analog Devices, INDIA. > > > _______________________________________________ > 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-admin@ietf.org Thu Nov 20 06:33:19 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29283 for ; Thu, 20 Nov 2003 06:33:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMn3V-0001EV-EN; Thu, 20 Nov 2003 06:33:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMn3K-0001E9-32 for megaco@optimus.ietf.org; Thu, 20 Nov 2003 06:32:50 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29233 for ; Thu, 20 Nov 2003 06:32:34 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMn3G-0000z1-00 for megaco@ietf.org; Thu, 20 Nov 2003 06:32:46 -0500 Received: from web41502.mail.yahoo.com ([66.218.93.85]) by ietf-mx with smtp (Exim 4.12) id 1AMn3G-0000yr-00 for megaco@ietf.org; Thu, 20 Nov 2003 06:32:46 -0500 Message-ID: <20031120113216.94837.qmail@web41502.mail.yahoo.com> Received: from [202.141.128.42] by web41502.mail.yahoo.com via HTTP; Thu, 20 Nov 2003 03:32:16 PST Date: Thu, 20 Nov 2003 03:32:16 -0800 (PST) From: vijayabama gurunathan To: megaco@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [Megaco] LONG-TIMER expiry handling Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , hi, from megaco version-2, "The copy of the responses may be destroyed either LONG-TIMER seconds after the response is issued, or when the entity receives a confirmation that the response has been received, through the "Response Acknowledgement parameter"." When the long timer expires, what should be done? *) Destroy the copy of the responses. or *) Resend the response and destroy the copy of the response. which one is correct? thanks in advance, bama __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Thu Nov 20 06:33:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29298 for ; Thu, 20 Nov 2003 06:33:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMn3Y-0001Fv-St for megaco-archive@odin.ietf.org; Thu, 20 Nov 2003 06:33:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKBX4k4004823 for megaco-archive@odin.ietf.org; Thu, 20 Nov 2003 06:33:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMn3Y-0001Fi-No for megaco-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 06:33:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29245 for ; Thu, 20 Nov 2003 06:32:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMn3V-0000zH-00 for megaco-web-archive@ietf.org; Thu, 20 Nov 2003 06:33:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AMn3V-0000zE-00 for megaco-web-archive@ietf.org; Thu, 20 Nov 2003 06:33:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMn3V-0001EV-EN; Thu, 20 Nov 2003 06:33:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMn3K-0001E9-32 for megaco@optimus.ietf.org; Thu, 20 Nov 2003 06:32:50 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29233 for ; Thu, 20 Nov 2003 06:32:34 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMn3G-0000z1-00 for megaco@ietf.org; Thu, 20 Nov 2003 06:32:46 -0500 Received: from web41502.mail.yahoo.com ([66.218.93.85]) by ietf-mx with smtp (Exim 4.12) id 1AMn3G-0000yr-00 for megaco@ietf.org; Thu, 20 Nov 2003 06:32:46 -0500 Message-ID: <20031120113216.94837.qmail@web41502.mail.yahoo.com> Received: from [202.141.128.42] by web41502.mail.yahoo.com via HTTP; Thu, 20 Nov 2003 03:32:16 PST Date: Thu, 20 Nov 2003 03:32:16 -0800 (PST) From: vijayabama gurunathan To: megaco@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [Megaco] LONG-TIMER expiry handling Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , hi, from megaco version-2, "The copy of the responses may be destroyed either LONG-TIMER seconds after the response is issued, or when the entity receives a confirmation that the response has been received, through the "Response Acknowledgement parameter"." When the long timer expires, what should be done? *) Destroy the copy of the responses. or *) Resend the response and destroy the copy of the response. which one is correct? thanks in advance, bama __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Thu Nov 20 06:50:26 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29862 for ; Thu, 20 Nov 2003 06:50:26 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMnK3-0002Cd-PF; Thu, 20 Nov 2003 06:50:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMnJ3-0002A5-I7 for megaco@optimus.ietf.org; Thu, 20 Nov 2003 06:49:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29812 for ; Thu, 20 Nov 2003 06:48:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMnJ0-0001Dk-00 for megaco@ietf.org; Thu, 20 Nov 2003 06:49:02 -0500 Received: from mta1.huawei.com ([61.144.161.40] helo=huawei.com) by ietf-mx with esmtp (Exim 4.12) id 1AMnIz-0001DO-00 for megaco@ietf.org; Thu, 20 Nov 2003 06:49:01 -0500 Received: from s70308 (huawei.com [172.17.1.60]) by mta1.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTPA id <0HON00JLRF44WZ@mta1.huawei.com> for megaco@ietf.org; Thu, 20 Nov 2003 19:40:53 +0800 (CST) Date: Thu, 20 Nov 2003 19:48:44 +0530 From: Suman Choudhary Subject: Re: [Megaco] LONG-TIMER expiry handling To: vijayabama gurunathan , megaco@ietf.org Message-id: <002c01c3af71$34c6e0c0$7800460a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Mailer: Microsoft Outlook Express 6.00.2800.1106 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <20031120113216.94837.qmail@web41502.mail.yahoo.com> Content-Transfer-Encoding: 7BIT Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7BIT Choice 1 is correct. Destroy the copy of the responses. --suman ----- Original Message ----- From: "vijayabama gurunathan" To: Sent: Thursday, November 20, 2003 5:02 PM Subject: [Megaco] LONG-TIMER expiry handling > hi, > from megaco version-2, > > "The copy of the responses may be destroyed either > LONG-TIMER seconds > after the response is issued, or when the entity > receives a > confirmation that the response has been received, > through the > "Response Acknowledgement parameter"." > > When the long timer expires, what should be done? > *) Destroy the copy of the responses. > or > *) Resend the response and destroy the copy of the > response. > > which one is correct? > > thanks in advance, > bama > > > __________________________________ > Do you Yahoo!? > Free Pop-Up Blocker - Get it now > http://companion.yahoo.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 exim@www1.ietf.org Thu Nov 20 06:50:31 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29886 for ; Thu, 20 Nov 2003 06:50:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMnK8-0002Ec-Gh for megaco-archive@odin.ietf.org; Thu, 20 Nov 2003 06:50:15 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKBoCxA008584 for megaco-archive@odin.ietf.org; Thu, 20 Nov 2003 06:50:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMnK8-0002EN-BN for megaco-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 06:50:12 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29835 for ; Thu, 20 Nov 2003 06:49:57 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMnK4-0001EZ-00 for megaco-web-archive@ietf.org; Thu, 20 Nov 2003 06:50:09 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AMnK4-0001EW-00 for megaco-web-archive@ietf.org; Thu, 20 Nov 2003 06:50:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMnK3-0002Cd-PF; Thu, 20 Nov 2003 06:50:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMnJ3-0002A5-I7 for megaco@optimus.ietf.org; Thu, 20 Nov 2003 06:49:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29812 for ; Thu, 20 Nov 2003 06:48:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMnJ0-0001Dk-00 for megaco@ietf.org; Thu, 20 Nov 2003 06:49:02 -0500 Received: from mta1.huawei.com ([61.144.161.40] helo=huawei.com) by ietf-mx with esmtp (Exim 4.12) id 1AMnIz-0001DO-00 for megaco@ietf.org; Thu, 20 Nov 2003 06:49:01 -0500 Received: from s70308 (huawei.com [172.17.1.60]) by mta1.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTPA id <0HON00JLRF44WZ@mta1.huawei.com> for megaco@ietf.org; Thu, 20 Nov 2003 19:40:53 +0800 (CST) Date: Thu, 20 Nov 2003 19:48:44 +0530 From: Suman Choudhary Subject: Re: [Megaco] LONG-TIMER expiry handling To: vijayabama gurunathan , megaco@ietf.org Message-id: <002c01c3af71$34c6e0c0$7800460a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Mailer: Microsoft Outlook Express 6.00.2800.1106 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <20031120113216.94837.qmail@web41502.mail.yahoo.com> Content-Transfer-Encoding: 7BIT Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7BIT Content-Transfer-Encoding: 7BIT Choice 1 is correct. Destroy the copy of the responses. --suman ----- Original Message ----- From: "vijayabama gurunathan" To: Sent: Thursday, November 20, 2003 5:02 PM Subject: [Megaco] LONG-TIMER expiry handling > hi, > from megaco version-2, > > "The copy of the responses may be destroyed either > LONG-TIMER seconds > after the response is issued, or when the entity > receives a > confirmation that the response has been received, > through the > "Response Acknowledgement parameter"." > > When the long timer expires, what should be done? > *) Destroy the copy of the responses. > or > *) Resend the response and destroy the copy of the > response. > > which one is correct? > > thanks in advance, > bama > > > __________________________________ > Do you Yahoo!? > Free Pop-Up Blocker - Get it now > http://companion.yahoo.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-admin@ietf.org Thu Nov 20 06:58:19 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00156 for ; Thu, 20 Nov 2003 06:58:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMnRi-0002uR-K4; Thu, 20 Nov 2003 06:58:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMnRe-0002u6-P3 for megaco@optimus.ietf.org; Thu, 20 Nov 2003 06:57:58 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00130 for ; Thu, 20 Nov 2003 06:57:43 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMnRb-0001LI-00 for megaco@ietf.org; Thu, 20 Nov 2003 06:57:55 -0500 Received: from [210.21.224.29] (helo=szsmtp.utstar.com.cn) by ietf-mx with esmtp (Exim 4.12) id 1AMnRa-0001KI-00 for megaco@ietf.org; Thu, 20 Nov 2003 06:57:54 -0500 Received: from sznssrasool ([172.19.17.174]) by szsmtp.utstar.com.cn (8.11.6/8.11.1) with SMTP id hAKBtsF06565; Thu, 20 Nov 2003 19:55:54 +0800 Message-ID: <004001c3af5d$403dd800$c1a110ac@cn.utstar.com> From: "Rasool Wani" To: "vijayabama gurunathan" , References: <20031120113216.94837.qmail@web41502.mail.yahoo.com> Subject: Re: [Megaco] LONG-TIMER expiry handling Date: Thu, 20 Nov 2003 19:55:53 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Destroy it, first one. Rasool Wani ----- Original Message ----- From: "vijayabama gurunathan" To: Sent: Thursday, November 20, 2003 7:32 PM Subject: [Megaco] LONG-TIMER expiry handling > hi, > from megaco version-2, > > "The copy of the responses may be destroyed either > LONG-TIMER seconds > after the response is issued, or when the entity > receives a > confirmation that the response has been received, > through the > "Response Acknowledgement parameter"." > > When the long timer expires, what should be done? > *) Destroy the copy of the responses. > or > *) Resend the response and destroy the copy of the > response. > > which one is correct? > > thanks in advance, > bama > > > __________________________________ > Do you Yahoo!? > Free Pop-Up Blocker - Get it now > http://companion.yahoo.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 exim@www1.ietf.org Thu Nov 20 06:58:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00175 for ; Thu, 20 Nov 2003 06:58:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMnRm-0002wG-J9 for megaco-archive@odin.ietf.org; Thu, 20 Nov 2003 06:58:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKBw6EN011290 for megaco-archive@odin.ietf.org; Thu, 20 Nov 2003 06:58:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMnRk-0002vw-V8 for megaco-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 06:58:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00140 for ; Thu, 20 Nov 2003 06:57:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMnRh-0001LZ-00 for megaco-web-archive@ietf.org; Thu, 20 Nov 2003 06:58:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AMnRh-0001LW-00 for megaco-web-archive@ietf.org; Thu, 20 Nov 2003 06:58:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMnRi-0002uR-K4; Thu, 20 Nov 2003 06:58:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMnRe-0002u6-P3 for megaco@optimus.ietf.org; Thu, 20 Nov 2003 06:57:58 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00130 for ; Thu, 20 Nov 2003 06:57:43 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMnRb-0001LI-00 for megaco@ietf.org; Thu, 20 Nov 2003 06:57:55 -0500 Received: from [210.21.224.29] (helo=szsmtp.utstar.com.cn) by ietf-mx with esmtp (Exim 4.12) id 1AMnRa-0001KI-00 for megaco@ietf.org; Thu, 20 Nov 2003 06:57:54 -0500 Received: from sznssrasool ([172.19.17.174]) by szsmtp.utstar.com.cn (8.11.6/8.11.1) with SMTP id hAKBtsF06565; Thu, 20 Nov 2003 19:55:54 +0800 Message-ID: <004001c3af5d$403dd800$c1a110ac@cn.utstar.com> From: "Rasool Wani" To: "vijayabama gurunathan" , References: <20031120113216.94837.qmail@web41502.mail.yahoo.com> Subject: Re: [Megaco] LONG-TIMER expiry handling Date: Thu, 20 Nov 2003 19:55:53 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Destroy it, first one. Rasool Wani ----- Original Message ----- From: "vijayabama gurunathan" To: Sent: Thursday, November 20, 2003 7:32 PM Subject: [Megaco] LONG-TIMER expiry handling > hi, > from megaco version-2, > > "The copy of the responses may be destroyed either > LONG-TIMER seconds > after the response is issued, or when the entity > receives a > confirmation that the response has been received, > through the > "Response Acknowledgement parameter"." > > When the long timer expires, what should be done? > *) Destroy the copy of the responses. > or > *) Resend the response and destroy the copy of the > response. > > which one is correct? > > thanks in advance, > bama > > > __________________________________ > Do you Yahoo!? > Free Pop-Up Blocker - Get it now > http://companion.yahoo.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-admin@ietf.org Thu Nov 20 12:23:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14293 for ; Thu, 20 Nov 2003 12:23:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMsWD-0001ss-Vj; Thu, 20 Nov 2003 12:23:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMsVK-0001rN-FU for megaco@optimus.ietf.org; Thu, 20 Nov 2003 12:22:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14173 for ; Thu, 20 Nov 2003 12:21:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMsVI-0006XO-00 for megaco@ietf.org; Thu, 20 Nov 2003 12:22:04 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AMsVI-0006X2-00 for megaco@ietf.org; Thu, 20 Nov 2003 12:22:04 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAKHLQn19845 for ; Thu, 20 Nov 2003 12:21:26 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Thu, 20 Nov 2003 12:21:26 -0500 Message-ID: From: "Kevin Boyle" To: anilj@cisco.com, "'Kumar.U.'" , megaco@ietf.org Subject: RE: [Megaco] when do I send TransactionResponseAck Date: Thu, 20 Nov 2003 12:21:20 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Actually, when using any non-guaranteed transport, the three-way handshake may be used -- not just in the cases of ImmAckReq. Kevin -----Original Message----- From: Anil Jangam (anilj) [mailto:anilj@cisco.com] Sent: Thursday, November 20, 2003 1:43 AM To: 'Kumar.U.'; megaco@ietf.org Subject: RE: [Megaco] when do I send TransactionResponseAck Hi kumar, TransactionResponseAck is part of Three-way-handshake process, refer to D.1.2@rfc3525 broadly falling under the ALF. It is sent under two different cases. First when the ImmAckRequiredToken is explicitly specified in a TransactionReply and in second case when a provisional response for a Transaction Request is received, upon reception of final response, the TransactionResponseAck is sent. Refer to the appropriate sections of the rfc for more details. /anil. > -----Original Message----- > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf > Of Kumar.U. > Sent: Wednesday, November 19, 2003 11:14 AM > To: megaco@ietf.org > Subject: [Megaco] when do I send TransactionResponseAck > > > Hi All, > We are implementing megaco MG with UDP and TCP as underlying > transport layers. Sending TransactionResponseAck is little bit of > confusing for me. When do I send TransactionResponseAck? .I feel that > we need to send TransactionResponseAck when the underlying transport > layer is UDP. Is it correct? Please clarify me on this. > > Thanks & Regards, > Kumaraswamy.U. > Senior S/W engineer, > Analog Devices, INDIA. > > > _______________________________________________ > 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 exim@www1.ietf.org Thu Nov 20 12:23:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14319 for ; Thu, 20 Nov 2003 12:23:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMsWH-0001u0-CV for megaco-archive@odin.ietf.org; Thu, 20 Nov 2003 12:23:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKHN5a6007306 for megaco-archive@odin.ietf.org; Thu, 20 Nov 2003 12:23:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMsWH-0001tl-7V for megaco-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 12:23:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14253 for ; Thu, 20 Nov 2003 12:22:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMsWF-0006ZH-00 for megaco-web-archive@ietf.org; Thu, 20 Nov 2003 12:23:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AMsWE-0006ZE-00 for megaco-web-archive@ietf.org; Thu, 20 Nov 2003 12:23:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMsWD-0001ss-Vj; Thu, 20 Nov 2003 12:23:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMsVK-0001rN-FU for megaco@optimus.ietf.org; Thu, 20 Nov 2003 12:22:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14173 for ; Thu, 20 Nov 2003 12:21:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMsVI-0006XO-00 for megaco@ietf.org; Thu, 20 Nov 2003 12:22:04 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AMsVI-0006X2-00 for megaco@ietf.org; Thu, 20 Nov 2003 12:22:04 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAKHLQn19845 for ; Thu, 20 Nov 2003 12:21:26 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Thu, 20 Nov 2003 12:21:26 -0500 Message-ID: From: "Kevin Boyle" To: anilj@cisco.com, "'Kumar.U.'" , megaco@ietf.org Subject: RE: [Megaco] when do I send TransactionResponseAck Date: Thu, 20 Nov 2003 12:21:20 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Actually, when using any non-guaranteed transport, the three-way handshake may be used -- not just in the cases of ImmAckReq. Kevin -----Original Message----- From: Anil Jangam (anilj) [mailto:anilj@cisco.com] Sent: Thursday, November 20, 2003 1:43 AM To: 'Kumar.U.'; megaco@ietf.org Subject: RE: [Megaco] when do I send TransactionResponseAck Hi kumar, TransactionResponseAck is part of Three-way-handshake process, refer to D.1.2@rfc3525 broadly falling under the ALF. It is sent under two different cases. First when the ImmAckRequiredToken is explicitly specified in a TransactionReply and in second case when a provisional response for a Transaction Request is received, upon reception of final response, the TransactionResponseAck is sent. Refer to the appropriate sections of the rfc for more details. /anil. > -----Original Message----- > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf > Of Kumar.U. > Sent: Wednesday, November 19, 2003 11:14 AM > To: megaco@ietf.org > Subject: [Megaco] when do I send TransactionResponseAck > > > Hi All, > We are implementing megaco MG with UDP and TCP as underlying > transport layers. Sending TransactionResponseAck is little bit of > confusing for me. When do I send TransactionResponseAck? .I feel that > we need to send TransactionResponseAck when the underlying transport > layer is UDP. Is it correct? Please clarify me on this. > > Thanks & Regards, > Kumaraswamy.U. > Senior S/W engineer, > Analog Devices, INDIA. > > > _______________________________________________ > 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-admin@ietf.org Thu Nov 20 12:52:19 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15407 for ; Thu, 20 Nov 2003 12:52:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMsyI-00045q-D3; Thu, 20 Nov 2003 12:52:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMsxc-00045P-L0 for megaco@optimus.ietf.org; Thu, 20 Nov 2003 12:51:22 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15363 for ; Thu, 20 Nov 2003 12:51:06 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMsxa-00070p-00 for megaco@ietf.org; Thu, 20 Nov 2003 12:51:18 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AMsxa-00070Z-00 for megaco@ietf.org; Thu, 20 Nov 2003 12:51:18 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAKHoln22674 for ; Thu, 20 Nov 2003 12:50:47 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Thu, 20 Nov 2003 12:50:47 -0500 Message-ID: From: "Kevin Boyle" To: Troy Cauble , rui.suying@zte.com.cn Cc: megaco@ietf.org Subject: RE: [Megaco] a Question about Pakcage andisp Date: Thu, 20 Nov 2003 12:50:40 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , For European versions, see ETSI EN 300 659-1, EN 300 659-2 and EN 300 659-3. Other regions may have their own specifications. I will see about getting the checksum on the example fixed during the next SG16 meeting. At the very least, I will include it in the IG. Kevin -----Original Message----- From: Troy Cauble [mailto:troy@bell-labs.com] Sent: Wednesday, November 19, 2003 10:13 AM To: rui.suying@zte.com.cn Cc: megaco@ietf.org Subject: Re: [Megaco] a Question about Pakcage andisp rui.suying@zte.com.cn wrote: > > where can i get the description of parameter ddb? what is the meaning > of "ddb"? > > for example: > the following is a fraction of a H.248 message, > > Signals{andisp/dwa{ddb=802001083035313831363135020A3931393535353030303 > 007084A6F686E20446F65D5,pattern=1}} ddb is a ascii hex encoding of a binary MDMF message. MDMF is defined in a Telcordia spec titled GR-30-CORE. (BTW, the checksum in the example is wrong.) -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 exim@www1.ietf.org Thu Nov 20 12:52:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15422 for ; Thu, 20 Nov 2003 12:52:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMsyK-00047Y-Dn for megaco-archive@odin.ietf.org; Thu, 20 Nov 2003 12:52:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKHq4Xx015834 for megaco-archive@odin.ietf.org; Thu, 20 Nov 2003 12:52:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMsyK-00046m-8Z for megaco-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 12:52:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15390 for ; Thu, 20 Nov 2003 12:51:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMsyI-000717-00 for megaco-web-archive@ietf.org; Thu, 20 Nov 2003 12:52:02 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AMsyH-000714-00 for megaco-web-archive@ietf.org; Thu, 20 Nov 2003 12:52:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMsyI-00045q-D3; Thu, 20 Nov 2003 12:52:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMsxc-00045P-L0 for megaco@optimus.ietf.org; Thu, 20 Nov 2003 12:51:22 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15363 for ; Thu, 20 Nov 2003 12:51:06 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMsxa-00070p-00 for megaco@ietf.org; Thu, 20 Nov 2003 12:51:18 -0500 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 1AMsxa-00070Z-00 for megaco@ietf.org; Thu, 20 Nov 2003 12:51:18 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAKHoln22674 for ; Thu, 20 Nov 2003 12:50:47 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Thu, 20 Nov 2003 12:50:47 -0500 Message-ID: From: "Kevin Boyle" To: Troy Cauble , rui.suying@zte.com.cn Cc: megaco@ietf.org Subject: RE: [Megaco] a Question about Pakcage andisp Date: Thu, 20 Nov 2003 12:50:40 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , For European versions, see ETSI EN 300 659-1, EN 300 659-2 and EN 300 659-3. Other regions may have their own specifications. I will see about getting the checksum on the example fixed during the next SG16 meeting. At the very least, I will include it in the IG. Kevin -----Original Message----- From: Troy Cauble [mailto:troy@bell-labs.com] Sent: Wednesday, November 19, 2003 10:13 AM To: rui.suying@zte.com.cn Cc: megaco@ietf.org Subject: Re: [Megaco] a Question about Pakcage andisp rui.suying@zte.com.cn wrote: > > where can i get the description of parameter ddb? what is the meaning > of "ddb"? > > for example: > the following is a fraction of a H.248 message, > > Signals{andisp/dwa{ddb=802001083035313831363135020A3931393535353030303 > 007084A6F686E20446F65D5,pattern=1}} ddb is a ascii hex encoding of a binary MDMF message. MDMF is defined in a Telcordia spec titled GR-30-CORE. (BTW, the checksum in the example is wrong.) -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-admin@ietf.org Mon Nov 24 02:24:26 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28043 for ; Mon, 24 Nov 2003 02:24:26 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOB4k-0004Ny-It; Mon, 24 Nov 2003 02:24:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOB4K-0004Mx-TH for megaco@optimus.ietf.org; Mon, 24 Nov 2003 02:23:37 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28016 for ; Mon, 24 Nov 2003 02:23:21 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOB4G-0007Lb-00 for megaco@ietf.org; Mon, 24 Nov 2003 02:23:32 -0500 Received: from fw.cdotb.ernet.in ([202.41.72.207] helo=ws9.cdotb.ernet.in) by ietf-mx with esmtp (Exim 4.12) id 1AOB4E-0007LV-00 for megaco@ietf.org; Mon, 24 Nov 2003 02:23:31 -0500 Received: from cdotb.ernet.in ([192.168.51.243]) by ws9.cdotb.ernet.in (8.12.9/8.12.9) with ESMTP id hAO7QNrD016931; Mon, 24 Nov 2003 12:26:24 +0500 (GMT+0500) Message-ID: <3FC24463.3030901@cdotb.ernet.in> Date: Mon, 24 Nov 2003 12:48:19 -0500 From: Krishnamurthy V User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1) Gecko/20020827 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rasool Wani CC: vijayabama gurunathan , megaco@ietf.org Subject: Re: [Megaco] LONG-TIMER expiry handling References: <20031120113216.94837.qmail@web41502.mail.yahoo.com> <004001c3af5d$403dd800$c1a110ac@cn.utstar.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit hi rasool, this is with respect to the document TSS&TP, ETSI TS 101 889-2, which says the valid behaviour of an MGC should be : "on expiry the Transaction Timer without the receipt of the corresponding Transaction Response Acknowledge, resends the previous Transaction Reply" refer the test case TP/MGC/TR/BV-02, i.e. 5.2.10.1. does it contradicts with the rfc or i got it wrong? please clarify. thank you. -krish. Rasool Wani wrote: >Destroy it, first one. >Rasool Wani > > > >----- Original Message ----- >From: "vijayabama gurunathan" >To: >Sent: Thursday, November 20, 2003 7:32 PM >Subject: [Megaco] LONG-TIMER expiry handling > > > > >>hi, >>from megaco version-2, >> >> "The copy of the responses may be destroyed either >>LONG-TIMER seconds >> after the response is issued, or when the entity >>receives a >> confirmation that the response has been received, >>through the >> "Response Acknowledgement parameter"." >> >>When the long timer expires, what should be done? >> *) Destroy the copy of the responses. >> or >> *) Resend the response and destroy the copy of the >>response. >> >>which one is correct? >> >>thanks in advance, >>bama >> >> >> -- ------------------------------------------------------------------------- V Krishnamurthy Phone (O): 080-2263399 Ext:255 Internet Telephony Group, (R): 080-3339368 C-DoT, 71/1, Miller Road, (M): 98453 79041 Bangalore - 560052 ------------------------------------------------------------------------- The very strength that protects the heart from injury is the strength that prevents the heart from enlarging to its intended greatness within. -Kahlil Gibran. ------------------------------------------------------------------------- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Mon Nov 24 02:24:35 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28058 for ; Mon, 24 Nov 2003 02:24:35 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOB4v-0004PY-Ai for megaco-archive@odin.ietf.org; Mon, 24 Nov 2003 02:24:19 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAO7ODQ2016955 for megaco-archive@odin.ietf.org; Mon, 24 Nov 2003 02:24:13 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOB4t-0004PG-Oj for megaco-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 02:24:11 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28035 for ; Mon, 24 Nov 2003 02:23:56 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOB4p-0007Lq-00 for megaco-web-archive@ietf.org; Mon, 24 Nov 2003 02:24:07 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AOB4p-0007Ll-00 for megaco-web-archive@ietf.org; Mon, 24 Nov 2003 02:24:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOB4k-0004Ny-It; Mon, 24 Nov 2003 02:24:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOB4K-0004Mx-TH for megaco@optimus.ietf.org; Mon, 24 Nov 2003 02:23:37 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28016 for ; Mon, 24 Nov 2003 02:23:21 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOB4G-0007Lb-00 for megaco@ietf.org; Mon, 24 Nov 2003 02:23:32 -0500 Received: from fw.cdotb.ernet.in ([202.41.72.207] helo=ws9.cdotb.ernet.in) by ietf-mx with esmtp (Exim 4.12) id 1AOB4E-0007LV-00 for megaco@ietf.org; Mon, 24 Nov 2003 02:23:31 -0500 Received: from cdotb.ernet.in ([192.168.51.243]) by ws9.cdotb.ernet.in (8.12.9/8.12.9) with ESMTP id hAO7QNrD016931; Mon, 24 Nov 2003 12:26:24 +0500 (GMT+0500) Message-ID: <3FC24463.3030901@cdotb.ernet.in> Date: Mon, 24 Nov 2003 12:48:19 -0500 From: Krishnamurthy V User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1) Gecko/20020827 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rasool Wani CC: vijayabama gurunathan , megaco@ietf.org Subject: Re: [Megaco] LONG-TIMER expiry handling References: <20031120113216.94837.qmail@web41502.mail.yahoo.com> <004001c3af5d$403dd800$c1a110ac@cn.utstar.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit hi rasool, this is with respect to the document TSS&TP, ETSI TS 101 889-2, which says the valid behaviour of an MGC should be : "on expiry the Transaction Timer without the receipt of the corresponding Transaction Response Acknowledge, resends the previous Transaction Reply" refer the test case TP/MGC/TR/BV-02, i.e. 5.2.10.1. does it contradicts with the rfc or i got it wrong? please clarify. thank you. -krish. Rasool Wani wrote: >Destroy it, first one. >Rasool Wani > > > >----- Original Message ----- >From: "vijayabama gurunathan" >To: >Sent: Thursday, November 20, 2003 7:32 PM >Subject: [Megaco] LONG-TIMER expiry handling > > > > >>hi, >>from megaco version-2, >> >> "The copy of the responses may be destroyed either >>LONG-TIMER seconds >> after the response is issued, or when the entity >>receives a >> confirmation that the response has been received, >>through the >> "Response Acknowledgement parameter"." >> >>When the long timer expires, what should be done? >> *) Destroy the copy of the responses. >> or >> *) Resend the response and destroy the copy of the >>response. >> >>which one is correct? >> >>thanks in advance, >>bama >> >> >> -- ------------------------------------------------------------------------- V Krishnamurthy Phone (O): 080-2263399 Ext:255 Internet Telephony Group, (R): 080-3339368 C-DoT, 71/1, Miller Road, (M): 98453 79041 Bangalore - 560052 ------------------------------------------------------------------------- The very strength that protects the heart from injury is the strength that prevents the heart from enlarging to its intended greatness within. -Kahlil Gibran. ------------------------------------------------------------------------- _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Mon Nov 24 05:49:19 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03322 for ; Mon, 24 Nov 2003 05:49:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOEH7-0000Bu-R6; Mon, 24 Nov 2003 05:49:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOEGX-0000AV-2t for megaco@optimus.ietf.org; Mon, 24 Nov 2003 05:48:25 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03288 for ; Mon, 24 Nov 2003 05:48:09 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOEGT-00028r-00 for megaco@ietf.org; Mon, 24 Nov 2003 05:48:21 -0500 Received: from india-ironport-1.cisco.com ([64.104.129.195]) by ietf-mx with esmtp (Exim 4.12) id 1AOEGS-00028N-00 for megaco@ietf.org; Mon, 24 Nov 2003 05:48:21 -0500 Received: from cisco.com (64.104.129.221) by india-ironport-1.cisco.com with ESMTP; 24 Nov 2003 16:27:55 +0530 Received: from samrat.cisco.com (samrat.cisco.com [192.135.241.21]) by india-msg-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAOGFM0s024174; Mon, 24 Nov 2003 16:15:22 GMT Received: from aniljw2k02 (dhcp-10-77-5-221.cisco.com [10.77.5.221]) by samrat.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id QAA19416; Mon, 24 Nov 2003 16:17:51 +0530 (IST) Reply-To: From: "Anil Jangam \(anilj\)" To: "'Krishnamurthy V'" , "'Rasool Wani'" Cc: "'vijayabama gurunathan'" , Subject: RE: [Megaco] LONG-TIMER expiry handling Date: Mon, 24 Nov 2003 16:17:43 +0530 Message-ID: <000001c3b278$63f77fd0$dd054d0a@apac.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal In-Reply-To: <3FC24463.3030901@cdotb.ernet.in> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi Krish, Upon the expiry of the retransmission timer, the given transaction should be repeated/retransmitted. See 8@h.248.1 (last para). According to this, in case of three-way-handshake, it is necessary to repeat the Transaction Reply if the timer expiry happens before you receive the TxnResAck. This behaviour will continue till the Long Timer associated with the Transaction Reply expires. /anil. > -----Original Message----- > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On > Behalf Of Krishnamurthy V > Sent: Monday, November 24, 2003 11:18 PM > To: Rasool Wani > Cc: vijayabama gurunathan; megaco@ietf.org > Subject: Re: [Megaco] LONG-TIMER expiry handling > > > hi rasool, > > this is with respect to the document TSS&TP, ETSI TS 101 > 889-2, which says the valid behaviour of an MGC should be : > > "on expiry the Transaction Timer without the receipt of the > corresponding Transaction Response Acknowledge, resends the > previous Transaction Reply" > > refer the test case TP/MGC/TR/BV-02, i.e. 5.2.10.1. > > does it contradicts with the rfc or i got it wrong? > > please clarify. thank you. > -krish. > > Rasool Wani wrote: > > >Destroy it, first one. > >Rasool Wani > > > > > > > >----- Original Message ----- > >From: "vijayabama gurunathan" > >To: > >Sent: Thursday, November 20, 2003 7:32 PM > >Subject: [Megaco] LONG-TIMER expiry handling > > > > > > > > > >>hi, > >>from megaco version-2, > >> > >> "The copy of the responses may be destroyed either > LONG-TIMER seconds > >> after the response is issued, or when the entity > >>receives a > >> confirmation that the response has been received, > >>through the > >> "Response Acknowledgement parameter"." > >> > >>When the long timer expires, what should be done? > >> *) Destroy the copy of the responses. > >> or > >> *) Resend the response and destroy the copy of the response. > >> > >>which one is correct? > >> > >>thanks in advance, > >>bama > >> > >> > >> > > -- > -------------------------------------------------------------- > ----------- > V Krishnamurthy Phone (O): 080-2263399 Ext:255 > Internet Telephony Group, (R): 080-3339368 > C-DoT, 71/1, Miller Road, (M): 98453 79041 > Bangalore - 560052 > -------------------------------------------------------------- > ----------- > The very strength that protects the heart from injury is the > strength that prevents the heart from enlarging to its > intended greatness within. -Kahlil Gibran. > -------------------------------------------------------------- > ----------- > > > > _______________________________________________ > 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 exim@www1.ietf.org Mon Nov 24 05:49:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03337 for ; Mon, 24 Nov 2003 05:49:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOEHC-0000DJ-FG for megaco-archive@odin.ietf.org; Mon, 24 Nov 2003 05:49:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAOAn68a000814 for megaco-archive@odin.ietf.org; Mon, 24 Nov 2003 05:49:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOEHC-0000Cr-7C for megaco-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 05:49:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03307 for ; Mon, 24 Nov 2003 05:48:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOEH8-00029R-00 for megaco-web-archive@ietf.org; Mon, 24 Nov 2003 05:49:02 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AOEH8-00029O-00 for megaco-web-archive@ietf.org; Mon, 24 Nov 2003 05:49:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOEH7-0000Bu-R6; Mon, 24 Nov 2003 05:49:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOEGX-0000AV-2t for megaco@optimus.ietf.org; Mon, 24 Nov 2003 05:48:25 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03288 for ; Mon, 24 Nov 2003 05:48:09 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOEGT-00028r-00 for megaco@ietf.org; Mon, 24 Nov 2003 05:48:21 -0500 Received: from india-ironport-1.cisco.com ([64.104.129.195]) by ietf-mx with esmtp (Exim 4.12) id 1AOEGS-00028N-00 for megaco@ietf.org; Mon, 24 Nov 2003 05:48:21 -0500 Received: from cisco.com (64.104.129.221) by india-ironport-1.cisco.com with ESMTP; 24 Nov 2003 16:27:55 +0530 Received: from samrat.cisco.com (samrat.cisco.com [192.135.241.21]) by india-msg-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAOGFM0s024174; Mon, 24 Nov 2003 16:15:22 GMT Received: from aniljw2k02 (dhcp-10-77-5-221.cisco.com [10.77.5.221]) by samrat.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id QAA19416; Mon, 24 Nov 2003 16:17:51 +0530 (IST) Reply-To: From: "Anil Jangam \(anilj\)" To: "'Krishnamurthy V'" , "'Rasool Wani'" Cc: "'vijayabama gurunathan'" , Subject: RE: [Megaco] LONG-TIMER expiry handling Date: Mon, 24 Nov 2003 16:17:43 +0530 Message-ID: <000001c3b278$63f77fd0$dd054d0a@apac.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal In-Reply-To: <3FC24463.3030901@cdotb.ernet.in> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Krish, Upon the expiry of the retransmission timer, the given transaction should be repeated/retransmitted. See 8@h.248.1 (last para). According to this, in case of three-way-handshake, it is necessary to repeat the Transaction Reply if the timer expiry happens before you receive the TxnResAck. This behaviour will continue till the Long Timer associated with the Transaction Reply expires. /anil. > -----Original Message----- > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On > Behalf Of Krishnamurthy V > Sent: Monday, November 24, 2003 11:18 PM > To: Rasool Wani > Cc: vijayabama gurunathan; megaco@ietf.org > Subject: Re: [Megaco] LONG-TIMER expiry handling > > > hi rasool, > > this is with respect to the document TSS&TP, ETSI TS 101 > 889-2, which says the valid behaviour of an MGC should be : > > "on expiry the Transaction Timer without the receipt of the > corresponding Transaction Response Acknowledge, resends the > previous Transaction Reply" > > refer the test case TP/MGC/TR/BV-02, i.e. 5.2.10.1. > > does it contradicts with the rfc or i got it wrong? > > please clarify. thank you. > -krish. > > Rasool Wani wrote: > > >Destroy it, first one. > >Rasool Wani > > > > > > > >----- Original Message ----- > >From: "vijayabama gurunathan" > >To: > >Sent: Thursday, November 20, 2003 7:32 PM > >Subject: [Megaco] LONG-TIMER expiry handling > > > > > > > > > >>hi, > >>from megaco version-2, > >> > >> "The copy of the responses may be destroyed either > LONG-TIMER seconds > >> after the response is issued, or when the entity > >>receives a > >> confirmation that the response has been received, > >>through the > >> "Response Acknowledgement parameter"." > >> > >>When the long timer expires, what should be done? > >> *) Destroy the copy of the responses. > >> or > >> *) Resend the response and destroy the copy of the response. > >> > >>which one is correct? > >> > >>thanks in advance, > >>bama > >> > >> > >> > > -- > -------------------------------------------------------------- > ----------- > V Krishnamurthy Phone (O): 080-2263399 Ext:255 > Internet Telephony Group, (R): 080-3339368 > C-DoT, 71/1, Miller Road, (M): 98453 79041 > Bangalore - 560052 > -------------------------------------------------------------- > ----------- > The very strength that protects the heart from injury is the > strength that prevents the heart from enlarging to its > intended greatness within. -Kahlil Gibran. > -------------------------------------------------------------- > ----------- > > > > _______________________________________________ > 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-admin@ietf.org Mon Nov 24 08:34:18 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07355 for ; Mon, 24 Nov 2003 08:34:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOGqn-0000Bu-3l; Mon, 24 Nov 2003 08:34:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOGqR-0000B0-5D for megaco@optimus.ietf.org; Mon, 24 Nov 2003 08:33:39 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07325 for ; Mon, 24 Nov 2003 08:33:24 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOGqP-0004mE-00 for megaco@ietf.org; Mon, 24 Nov 2003 08:33:37 -0500 Received: from [210.21.224.29] (helo=szsmtp.utstar.com.cn) by ietf-mx with esmtp (Exim 4.12) id 1AOGqM-0004ls-00 for megaco@ietf.org; Mon, 24 Nov 2003 08:33:37 -0500 Received: from sznssrasool ([172.19.17.174]) by szsmtp.utstar.com.cn (8.11.6/8.11.1) with SMTP id hAOCrkF20132; Mon, 24 Nov 2003 20:53:46 +0800 Message-ID: <00b101c3b28a$01972720$c1a110ac@cn.utstar.com> From: "Rasool Wani" To: , "'Krishnamurthy V'" Cc: "'vijayabama gurunathan'" , References: <000001c3b278$63f77fd0$dd054d0a@apac.cisco.com> Subject: Re: [Megaco] LONG-TIMER expiry handling Date: Mon, 24 Nov 2003 20:53:46 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit anil, you mean TransactionReply's are to be retransmitted too.but 8@H.248.1 (last para) reads like this: Applications SHOULD implement an application level timer per transaction. Expiration of the timer should cause a retransmission of the request. Receipt of a Reply should cancel the timer. Receipt of Pending should restart the timer. I understand it only says about the retransmission of TransactionRequest. Rasool wani ----- Original Message ----- From: "Anil Jangam (anilj)" To: "'Krishnamurthy V'" ; "'Rasool Wani'" Cc: "'vijayabama gurunathan'" ; Sent: Monday, November 24, 2003 6:47 PM Subject: RE: [Megaco] LONG-TIMER expiry handling > Hi Krish, > > Upon the expiry of the retransmission timer, the given transaction > should be repeated/retransmitted. See 8@h.248.1 (last para). > According to this, in case of three-way-handshake, it is necessary to > repeat the Transaction Reply if the timer expiry happens before you > receive the TxnResAck. This behaviour will continue till the Long Timer > associated with the Transaction Reply expires. > > /anil. > > > > > -----Original Message----- > > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On > > Behalf Of Krishnamurthy V > > Sent: Monday, November 24, 2003 11:18 PM > > To: Rasool Wani > > Cc: vijayabama gurunathan; megaco@ietf.org > > Subject: Re: [Megaco] LONG-TIMER expiry handling > > > > > > hi rasool, > > > > this is with respect to the document TSS&TP, ETSI TS 101 > > 889-2, which says the valid behaviour of an MGC should be : > > > > "on expiry the Transaction Timer without the receipt of the > > corresponding Transaction Response Acknowledge, resends the > > previous Transaction Reply" > > > > refer the test case TP/MGC/TR/BV-02, i.e. 5.2.10.1. > > > > does it contradicts with the rfc or i got it wrong? > > > > please clarify. thank you. > > -krish. > > > > Rasool Wani wrote: > > > > >Destroy it, first one. > > >Rasool Wani > > > > > > > > > > > >----- Original Message ----- > > >From: "vijayabama gurunathan" > > >To: > > >Sent: Thursday, November 20, 2003 7:32 PM > > >Subject: [Megaco] LONG-TIMER expiry handling > > > > > > > > > > > > > > >>hi, > > >>from megaco version-2, > > >> > > >> "The copy of the responses may be destroyed either > > LONG-TIMER seconds > > >> after the response is issued, or when the entity > > >>receives a > > >> confirmation that the response has been received, > > >>through the > > >> "Response Acknowledgement parameter"." > > >> > > >>When the long timer expires, what should be done? > > >> *) Destroy the copy of the responses. > > >> or > > >> *) Resend the response and destroy the copy of the response. > > >> > > >>which one is correct? > > >> > > >>thanks in advance, > > >>bama > > >> > > >> > > >> > > > > -- > > -------------------------------------------------------------- > > ----------- > > V Krishnamurthy Phone (O): 080-2263399 Ext:255 > > Internet Telephony Group, (R): 080-3339368 > > C-DoT, 71/1, Miller Road, (M): 98453 79041 > > Bangalore - 560052 > > -------------------------------------------------------------- > > ----------- > > The very strength that protects the heart from injury is the > > strength that prevents the heart from enlarging to its > > intended greatness within. -Kahlil Gibran. > > -------------------------------------------------------------- > > ----------- > > > > > > > > _______________________________________________ > > 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-admin@ietf.org Mon Nov 24 08:39:19 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07564 for ; Mon, 24 Nov 2003 08:39:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOGvd-0001IK-C2; Mon, 24 Nov 2003 08:39:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOGv4-0001Gn-Ka for megaco@optimus.ietf.org; Mon, 24 Nov 2003 08:38:28 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07510 for ; Mon, 24 Nov 2003 08:38:08 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOGv0-0004tE-00 for megaco@ietf.org; Mon, 24 Nov 2003 08:38:22 -0500 Received: from india-ironport-1.cisco.com ([64.104.129.195]) by ietf-mx with esmtp (Exim 4.12) id 1AOGuz-0004sl-00 for megaco@ietf.org; Mon, 24 Nov 2003 08:38:21 -0500 Received: from cisco.com (64.104.129.221) by india-ironport-1.cisco.com with ESMTP; 24 Nov 2003 19:17:55 +0530 Received: from samrat.cisco.com (samrat.cisco.com [192.135.241.21]) by india-msg-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAOJ5L0s008847; Mon, 24 Nov 2003 19:05:21 GMT Received: from aniljw2k02 (dhcp-10-77-5-221.cisco.com [10.77.5.221]) by samrat.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id TAA08334; Mon, 24 Nov 2003 19:07:45 +0530 (IST) Reply-To: From: "Anil Jangam \(anilj\)" To: "'Rasool Wani'" , "'Krishnamurthy V'" Cc: "'vijayabama gurunathan'" , , "'Kevin Boyle'" , "'Christian Groves'" Subject: RE: [Megaco] LONG-TIMER expiry handling Date: Mon, 24 Nov 2003 19:07:37 +0530 Message-ID: <000001c3b290$235c1d60$dd054d0a@apac.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal In-Reply-To: <00b101c3b28a$01972720$c1a110ac@cn.utstar.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit ***The retransmission of the TransactionReply is an exceptional case in Three-way-handshake only.*** In this perticular feature, unless you receive the TxnResAck for the given TxnReply, the Three-way-handshake is not completed. Once you send the TxnReply, how are you going to know that the other side has really received it or not? > -----Original Message----- > From: Rasool Wani [mailto:rasool.wani@utstar.com] > Sent: Monday, November 24, 2003 6:24 PM > To: anilj@cisco.com; 'Krishnamurthy V' > Cc: 'vijayabama gurunathan'; megaco@ietf.org > Subject: Re: [Megaco] LONG-TIMER expiry handling > > > anil, > you mean TransactionReply's are to be retransmitted > too.but 8@H.248.1 (last para) reads like this: > > Applications SHOULD implement an application level timer per > transaction. Expiration of the timer should cause a > retransmission of the request. Receipt of a Reply should > cancel the timer. Receipt of Pending should restart the timer. > > I understand it only says about the retransmission of > TransactionRequest. > > Rasool wani > > > ----- Original Message ----- > From: "Anil Jangam (anilj)" > To: "'Krishnamurthy V'" ; "'Rasool > Wani'" > Cc: "'vijayabama gurunathan'" ; > > Sent: Monday, November 24, 2003 6:47 PM > Subject: RE: [Megaco] LONG-TIMER expiry handling > > > > Hi Krish, > > > > Upon the expiry of the retransmission timer, the given transaction > > should be repeated/retransmitted. See 8@h.248.1 (last > para). According > > to this, in case of three-way-handshake, it is necessary to > repeat the > > Transaction Reply if the timer expiry happens before you > receive the > > TxnResAck. This behaviour will continue till the Long Timer > associated > > with the Transaction Reply expires. > > > > /anil. > > > > > > > > > -----Original Message----- > > > From: megaco-admin@ietf.org > [mailto:megaco-admin@ietf.org] On Behalf > > > Of Krishnamurthy V > > > Sent: Monday, November 24, 2003 11:18 PM > > > To: Rasool Wani > > > Cc: vijayabama gurunathan; megaco@ietf.org > > > Subject: Re: [Megaco] LONG-TIMER expiry handling > > > > > > > > > hi rasool, > > > > > > this is with respect to the document TSS&TP, ETSI TS 101 889-2, > > > which says the valid behaviour of an MGC should be : > > > > > > "on expiry the Transaction Timer without the receipt of the > > > corresponding Transaction Response Acknowledge, resends > the previous > > > Transaction Reply" > > > > > > refer the test case TP/MGC/TR/BV-02, i.e. 5.2.10.1. > > > > > > does it contradicts with the rfc or i got it wrong? > > > > > > please clarify. thank you. > > > -krish. > > > > > > Rasool Wani wrote: > > > > > > >Destroy it, first one. > > > >Rasool Wani > > > > > > > > > > > > > > > >----- Original Message ----- > > > >From: "vijayabama gurunathan" > > > >To: > > > >Sent: Thursday, November 20, 2003 7:32 PM > > > >Subject: [Megaco] LONG-TIMER expiry handling > > > > > > > > > > > > > > > > > > > >>hi, > > > >>from megaco version-2, > > > >> > > > >> "The copy of the responses may be destroyed either > > > LONG-TIMER seconds > > > >> after the response is issued, or when the entity receives a > > > >> confirmation that the response has been received, > > > >>through the > > > >> "Response Acknowledgement parameter"." > > > >> > > > >>When the long timer expires, what should be done? > > > >> *) Destroy the copy of the responses. > > > >> or > > > >> *) Resend the response and destroy the copy of the response. > > > >> > > > >>which one is correct? > > > >> > > > >>thanks in advance, > > > >>bama > > > >> > > > >> > > > >> > > > > > > -- > > > -------------------------------------------------------------- > > > ----------- > > > V Krishnamurthy Phone (O): 080-2263399 Ext:255 > > > Internet Telephony Group, (R): 080-3339368 > > > C-DoT, 71/1, Miller Road, (M): 98453 79041 > > > Bangalore - 560052 > > > -------------------------------------------------------------- > > > ----------- > > > The very strength that protects the heart from injury is the > > > strength that prevents the heart from enlarging to its intended > > > greatness within. -Kahlil Gibran. > > > -------------------------------------------------------------- > > > ----------- > > > > > > > > > > > > _______________________________________________ > > > 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 exim@www1.ietf.org Mon Nov 24 08:41:10 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07737 for ; Mon, 24 Nov 2003 08:41:10 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOGxQ-0001We-HJ for megaco-archive@odin.ietf.org; Mon, 24 Nov 2003 08:40:54 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAODeqe7005858 for megaco-archive@odin.ietf.org; Mon, 24 Nov 2003 08:40:52 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOGxQ-0001WP-B4 for megaco-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 08:40:52 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07612 for ; Mon, 24 Nov 2003 08:40:37 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOGxO-0004wV-00 for megaco-web-archive@ietf.org; Mon, 24 Nov 2003 08:40:50 -0500 Received: from manatick.foretec.com ([4.17.168.5] helo=manatick) by ietf-mx with esmtp (Exim 4.12) id 1AOGxN-0004vi-01 for megaco-web-archive@ietf.org; Mon, 24 Nov 2003 08:40:50 -0500 Received: from [132.151.6.22] (helo=optimus.ietf.org) by manatick with esmtp (Exim 4.24) id 1AOGvg-0002Gq-4J for megaco-web-archive@ietf.org; Mon, 24 Nov 2003 08:39:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOGvd-0001IK-C2; Mon, 24 Nov 2003 08:39:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOGv4-0001Gn-Ka for megaco@optimus.ietf.org; Mon, 24 Nov 2003 08:38:28 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07510 for ; Mon, 24 Nov 2003 08:38:08 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOGv0-0004tE-00 for megaco@ietf.org; Mon, 24 Nov 2003 08:38:22 -0500 Received: from india-ironport-1.cisco.com ([64.104.129.195]) by ietf-mx with esmtp (Exim 4.12) id 1AOGuz-0004sl-00 for megaco@ietf.org; Mon, 24 Nov 2003 08:38:21 -0500 Received: from cisco.com (64.104.129.221) by india-ironport-1.cisco.com with ESMTP; 24 Nov 2003 19:17:55 +0530 Received: from samrat.cisco.com (samrat.cisco.com [192.135.241.21]) by india-msg-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAOJ5L0s008847; Mon, 24 Nov 2003 19:05:21 GMT Received: from aniljw2k02 (dhcp-10-77-5-221.cisco.com [10.77.5.221]) by samrat.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id TAA08334; Mon, 24 Nov 2003 19:07:45 +0530 (IST) Reply-To: From: "Anil Jangam \(anilj\)" To: "'Rasool Wani'" , "'Krishnamurthy V'" Cc: "'vijayabama gurunathan'" , , "'Kevin Boyle'" , "'Christian Groves'" Subject: RE: [Megaco] LONG-TIMER expiry handling Date: Mon, 24 Nov 2003 19:07:37 +0530 Message-ID: <000001c3b290$235c1d60$dd054d0a@apac.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal In-Reply-To: <00b101c3b28a$01972720$c1a110ac@cn.utstar.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit ***The retransmission of the TransactionReply is an exceptional case in Three-way-handshake only.*** In this perticular feature, unless you receive the TxnResAck for the given TxnReply, the Three-way-handshake is not completed. Once you send the TxnReply, how are you going to know that the other side has really received it or not? > -----Original Message----- > From: Rasool Wani [mailto:rasool.wani@utstar.com] > Sent: Monday, November 24, 2003 6:24 PM > To: anilj@cisco.com; 'Krishnamurthy V' > Cc: 'vijayabama gurunathan'; megaco@ietf.org > Subject: Re: [Megaco] LONG-TIMER expiry handling > > > anil, > you mean TransactionReply's are to be retransmitted > too.but 8@H.248.1 (last para) reads like this: > > Applications SHOULD implement an application level timer per > transaction. Expiration of the timer should cause a > retransmission of the request. Receipt of a Reply should > cancel the timer. Receipt of Pending should restart the timer. > > I understand it only says about the retransmission of > TransactionRequest. > > Rasool wani > > > ----- Original Message ----- > From: "Anil Jangam (anilj)" > To: "'Krishnamurthy V'" ; "'Rasool > Wani'" > Cc: "'vijayabama gurunathan'" ; > > Sent: Monday, November 24, 2003 6:47 PM > Subject: RE: [Megaco] LONG-TIMER expiry handling > > > > Hi Krish, > > > > Upon the expiry of the retransmission timer, the given transaction > > should be repeated/retransmitted. See 8@h.248.1 (last > para). According > > to this, in case of three-way-handshake, it is necessary to > repeat the > > Transaction Reply if the timer expiry happens before you > receive the > > TxnResAck. This behaviour will continue till the Long Timer > associated > > with the Transaction Reply expires. > > > > /anil. > > > > > > > > > -----Original Message----- > > > From: megaco-admin@ietf.org > [mailto:megaco-admin@ietf.org] On Behalf > > > Of Krishnamurthy V > > > Sent: Monday, November 24, 2003 11:18 PM > > > To: Rasool Wani > > > Cc: vijayabama gurunathan; megaco@ietf.org > > > Subject: Re: [Megaco] LONG-TIMER expiry handling > > > > > > > > > hi rasool, > > > > > > this is with respect to the document TSS&TP, ETSI TS 101 889-2, > > > which says the valid behaviour of an MGC should be : > > > > > > "on expiry the Transaction Timer without the receipt of the > > > corresponding Transaction Response Acknowledge, resends > the previous > > > Transaction Reply" > > > > > > refer the test case TP/MGC/TR/BV-02, i.e. 5.2.10.1. > > > > > > does it contradicts with the rfc or i got it wrong? > > > > > > please clarify. thank you. > > > -krish. > > > > > > Rasool Wani wrote: > > > > > > >Destroy it, first one. > > > >Rasool Wani > > > > > > > > > > > > > > > >----- Original Message ----- > > > >From: "vijayabama gurunathan" > > > >To: > > > >Sent: Thursday, November 20, 2003 7:32 PM > > > >Subject: [Megaco] LONG-TIMER expiry handling > > > > > > > > > > > > > > > > > > > >>hi, > > > >>from megaco version-2, > > > >> > > > >> "The copy of the responses may be destroyed either > > > LONG-TIMER seconds > > > >> after the response is issued, or when the entity receives a > > > >> confirmation that the response has been received, > > > >>through the > > > >> "Response Acknowledgement parameter"." > > > >> > > > >>When the long timer expires, what should be done? > > > >> *) Destroy the copy of the responses. > > > >> or > > > >> *) Resend the response and destroy the copy of the response. > > > >> > > > >>which one is correct? > > > >> > > > >>thanks in advance, > > > >>bama > > > >> > > > >> > > > >> > > > > > > -- > > > -------------------------------------------------------------- > > > ----------- > > > V Krishnamurthy Phone (O): 080-2263399 Ext:255 > > > Internet Telephony Group, (R): 080-3339368 > > > C-DoT, 71/1, Miller Road, (M): 98453 79041 > > > Bangalore - 560052 > > > -------------------------------------------------------------- > > > ----------- > > > The very strength that protects the heart from injury is the > > > strength that prevents the heart from enlarging to its intended > > > greatness within. -Kahlil Gibran. > > > -------------------------------------------------------------- > > > ----------- > > > > > > > > > > > > _______________________________________________ > > > 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 exim@www1.ietf.org Mon Nov 24 08:41:15 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07797 for ; Mon, 24 Nov 2003 08:41:15 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOGxX-0001YY-Hw for megaco-archive@odin.ietf.org; Mon, 24 Nov 2003 08:40:59 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAODex1J005975 for megaco-archive@odin.ietf.org; Mon, 24 Nov 2003 08:40:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOGxX-0001YI-DL for megaco-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 08:40:59 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07657 for ; Mon, 24 Nov 2003 08:40:43 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOGxU-0004xg-00 for megaco-web-archive@ietf.org; Mon, 24 Nov 2003 08:40:56 -0500 Received: from manatick.foretec.com ([4.17.168.5] helo=manatick) by ietf-mx with esmtp (Exim 4.12) id 1AOGxU-0004x7-00 for megaco-web-archive@ietf.org; Mon, 24 Nov 2003 08:40:56 -0500 Received: from [132.151.6.22] (helo=optimus.ietf.org) by manatick with esmtp (Exim 4.24) id 1AOGqo-0002Cy-Gx for megaco-web-archive@ietf.org; Mon, 24 Nov 2003 08:34:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOGqn-0000Bu-3l; Mon, 24 Nov 2003 08:34:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOGqR-0000B0-5D for megaco@optimus.ietf.org; Mon, 24 Nov 2003 08:33:39 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07325 for ; Mon, 24 Nov 2003 08:33:24 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOGqP-0004mE-00 for megaco@ietf.org; Mon, 24 Nov 2003 08:33:37 -0500 Received: from [210.21.224.29] (helo=szsmtp.utstar.com.cn) by ietf-mx with esmtp (Exim 4.12) id 1AOGqM-0004ls-00 for megaco@ietf.org; Mon, 24 Nov 2003 08:33:37 -0500 Received: from sznssrasool ([172.19.17.174]) by szsmtp.utstar.com.cn (8.11.6/8.11.1) with SMTP id hAOCrkF20132; Mon, 24 Nov 2003 20:53:46 +0800 Message-ID: <00b101c3b28a$01972720$c1a110ac@cn.utstar.com> From: "Rasool Wani" To: , "'Krishnamurthy V'" Cc: "'vijayabama gurunathan'" , References: <000001c3b278$63f77fd0$dd054d0a@apac.cisco.com> Subject: Re: [Megaco] LONG-TIMER expiry handling Date: Mon, 24 Nov 2003 20:53:46 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit anil, you mean TransactionReply's are to be retransmitted too.but 8@H.248.1 (last para) reads like this: Applications SHOULD implement an application level timer per transaction. Expiration of the timer should cause a retransmission of the request. Receipt of a Reply should cancel the timer. Receipt of Pending should restart the timer. I understand it only says about the retransmission of TransactionRequest. Rasool wani ----- Original Message ----- From: "Anil Jangam (anilj)" To: "'Krishnamurthy V'" ; "'Rasool Wani'" Cc: "'vijayabama gurunathan'" ; Sent: Monday, November 24, 2003 6:47 PM Subject: RE: [Megaco] LONG-TIMER expiry handling > Hi Krish, > > Upon the expiry of the retransmission timer, the given transaction > should be repeated/retransmitted. See 8@h.248.1 (last para). > According to this, in case of three-way-handshake, it is necessary to > repeat the Transaction Reply if the timer expiry happens before you > receive the TxnResAck. This behaviour will continue till the Long Timer > associated with the Transaction Reply expires. > > /anil. > > > > > -----Original Message----- > > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On > > Behalf Of Krishnamurthy V > > Sent: Monday, November 24, 2003 11:18 PM > > To: Rasool Wani > > Cc: vijayabama gurunathan; megaco@ietf.org > > Subject: Re: [Megaco] LONG-TIMER expiry handling > > > > > > hi rasool, > > > > this is with respect to the document TSS&TP, ETSI TS 101 > > 889-2, which says the valid behaviour of an MGC should be : > > > > "on expiry the Transaction Timer without the receipt of the > > corresponding Transaction Response Acknowledge, resends the > > previous Transaction Reply" > > > > refer the test case TP/MGC/TR/BV-02, i.e. 5.2.10.1. > > > > does it contradicts with the rfc or i got it wrong? > > > > please clarify. thank you. > > -krish. > > > > Rasool Wani wrote: > > > > >Destroy it, first one. > > >Rasool Wani > > > > > > > > > > > >----- Original Message ----- > > >From: "vijayabama gurunathan" > > >To: > > >Sent: Thursday, November 20, 2003 7:32 PM > > >Subject: [Megaco] LONG-TIMER expiry handling > > > > > > > > > > > > > > >>hi, > > >>from megaco version-2, > > >> > > >> "The copy of the responses may be destroyed either > > LONG-TIMER seconds > > >> after the response is issued, or when the entity > > >>receives a > > >> confirmation that the response has been received, > > >>through the > > >> "Response Acknowledgement parameter"." > > >> > > >>When the long timer expires, what should be done? > > >> *) Destroy the copy of the responses. > > >> or > > >> *) Resend the response and destroy the copy of the response. > > >> > > >>which one is correct? > > >> > > >>thanks in advance, > > >>bama > > >> > > >> > > >> > > > > -- > > -------------------------------------------------------------- > > ----------- > > V Krishnamurthy Phone (O): 080-2263399 Ext:255 > > Internet Telephony Group, (R): 080-3339368 > > C-DoT, 71/1, Miller Road, (M): 98453 79041 > > Bangalore - 560052 > > -------------------------------------------------------------- > > ----------- > > The very strength that protects the heart from injury is the > > strength that prevents the heart from enlarging to its > > intended greatness within. -Kahlil Gibran. > > -------------------------------------------------------------- > > ----------- > > > > > > > > _______________________________________________ > > 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-admin@ietf.org Mon Nov 24 09:32:19 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09430 for ; Mon, 24 Nov 2003 09:32:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOHkw-0004gT-88; Mon, 24 Nov 2003 09:32:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOHkW-0004fj-0G for megaco@optimus.ietf.org; Mon, 24 Nov 2003 09:31:36 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09377 for ; Mon, 24 Nov 2003 09:31:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOHkU-0005yA-00 for megaco@ietf.org; Mon, 24 Nov 2003 09:31:34 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AOHkT-0005xV-00 for megaco@ietf.org; Mon, 24 Nov 2003 09:31:33 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAOEUsL08548 for ; Mon, 24 Nov 2003 09:30:54 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 24 Nov 2003 09:30:54 -0500 Message-ID: From: "Kevin Boyle" To: anilj@cisco.com, "'Rasool Wani'" , "'Krishnamurthy V'" Cc: "'vijayabama gurunathan'" , megaco@ietf.org, "'Christian Groves'" Subject: RE: [Megaco] LONG-TIMER expiry handling Date: Mon, 24 Nov 2003 09:30:53 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Well.... You'd know when the other side retransmits the transaction that the response was not received. In any case, the three way handshake is optional and dependent upon your transport. Any "conformance" test that requires use of the three way handshake is wrong. Kevin -----Original Message----- From: Anil Jangam (anilj) [mailto:anilj@cisco.com] Sent: Monday, November 24, 2003 8:38 AM To: 'Rasool Wani'; 'Krishnamurthy V' Cc: 'vijayabama gurunathan'; megaco@ietf.org; Boyle, Kevin [NCRTP:3Z40:EXCH]; 'Christian Groves' Subject: RE: [Megaco] LONG-TIMER expiry handling ***The retransmission of the TransactionReply is an exceptional case in Three-way-handshake only.*** In this perticular feature, unless you receive the TxnResAck for the given TxnReply, the Three-way-handshake is not completed. Once you send the TxnReply, how are you going to know that the other side has really received it or not? > -----Original Message----- > From: Rasool Wani [mailto:rasool.wani@utstar.com] > Sent: Monday, November 24, 2003 6:24 PM > To: anilj@cisco.com; 'Krishnamurthy V' > Cc: 'vijayabama gurunathan'; megaco@ietf.org > Subject: Re: [Megaco] LONG-TIMER expiry handling > > > anil, > you mean TransactionReply's are to be retransmitted too.but > 8@H.248.1 (last para) reads like this: > > Applications SHOULD implement an application level timer per > transaction. Expiration of the timer should cause a retransmission of > the request. Receipt of a Reply should cancel the timer. Receipt of > Pending should restart the timer. > > I understand it only says about the retransmission of > TransactionRequest. > > Rasool wani > > > ----- Original Message ----- > From: "Anil Jangam (anilj)" > To: "'Krishnamurthy V'" ; "'Rasool Wani'" > > Cc: "'vijayabama gurunathan'" ; > > Sent: Monday, November 24, 2003 6:47 PM > Subject: RE: [Megaco] LONG-TIMER expiry handling > > > > Hi Krish, > > > > Upon the expiry of the retransmission timer, the given transaction > > should be repeated/retransmitted. See 8@h.248.1 (last > para). According > > to this, in case of three-way-handshake, it is necessary to > repeat the > > Transaction Reply if the timer expiry happens before you > receive the > > TxnResAck. This behaviour will continue till the Long Timer > associated > > with the Transaction Reply expires. > > > > /anil. > > > > > > > > > -----Original Message----- > > > From: megaco-admin@ietf.org > [mailto:megaco-admin@ietf.org] On Behalf > > > Of Krishnamurthy V > > > Sent: Monday, November 24, 2003 11:18 PM > > > To: Rasool Wani > > > Cc: vijayabama gurunathan; megaco@ietf.org > > > Subject: Re: [Megaco] LONG-TIMER expiry handling > > > > > > > > > hi rasool, > > > > > > this is with respect to the document TSS&TP, ETSI TS 101 889-2, > > > which says the valid behaviour of an MGC should be : > > > > > > "on expiry the Transaction Timer without the receipt of the > > > corresponding Transaction Response Acknowledge, resends > the previous > > > Transaction Reply" > > > > > > refer the test case TP/MGC/TR/BV-02, i.e. 5.2.10.1. > > > > > > does it contradicts with the rfc or i got it wrong? > > > > > > please clarify. thank you. > > > -krish. > > > > > > Rasool Wani wrote: > > > > > > >Destroy it, first one. > > > >Rasool Wani > > > > > > > > > > > > > > > >----- Original Message ----- > > > >From: "vijayabama gurunathan" > > > >To: > > > >Sent: Thursday, November 20, 2003 7:32 PM > > > >Subject: [Megaco] LONG-TIMER expiry handling > > > > > > > > > > > > > > > > > > > >>hi, > > > >>from megaco version-2, > > > >> > > > >> "The copy of the responses may be destroyed either > > > LONG-TIMER seconds > > > >> after the response is issued, or when the entity receives a > > > >> confirmation that the response has been received, through the > > > >> "Response Acknowledgement parameter"." > > > >> > > > >>When the long timer expires, what should be done? > > > >> *) Destroy the copy of the responses. > > > >> or > > > >> *) Resend the response and destroy the copy of the response. > > > >> > > > >>which one is correct? > > > >> > > > >>thanks in advance, > > > >>bama > > > >> > > > >> > > > >> > > > > > > -- > > > -------------------------------------------------------------- > > > ----------- > > > V Krishnamurthy Phone (O): 080-2263399 Ext:255 > > > Internet Telephony Group, (R): 080-3339368 > > > C-DoT, 71/1, Miller Road, (M): 98453 79041 > > > Bangalore - 560052 > > > -------------------------------------------------------------- > > > ----------- > > > The very strength that protects the heart from injury is the > > > strength that prevents the heart from enlarging to its intended > > > greatness within. -Kahlil Gibran. > > > -------------------------------------------------------------- > > > ----------- > > > > > > > > > > > > _______________________________________________ > > > 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 exim@www1.ietf.org Mon Nov 24 09:32:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09445 for ; Mon, 24 Nov 2003 09:32:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOHkz-0004hZ-UI for megaco-archive@odin.ietf.org; Mon, 24 Nov 2003 09:32:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAOEW5V1018073 for megaco-archive@odin.ietf.org; Mon, 24 Nov 2003 09:32:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOHkz-0004hL-Im for megaco-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 09:32:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09411 for ; Mon, 24 Nov 2003 09:31:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOHkx-00060P-00 for megaco-web-archive@ietf.org; Mon, 24 Nov 2003 09:32:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AOHkx-00060L-00 for megaco-web-archive@ietf.org; Mon, 24 Nov 2003 09:32:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOHkw-0004gT-88; Mon, 24 Nov 2003 09:32:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOHkW-0004fj-0G for megaco@optimus.ietf.org; Mon, 24 Nov 2003 09:31:36 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09377 for ; Mon, 24 Nov 2003 09:31:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOHkU-0005yA-00 for megaco@ietf.org; Mon, 24 Nov 2003 09:31:34 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1AOHkT-0005xV-00 for megaco@ietf.org; Mon, 24 Nov 2003 09:31:33 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAOEUsL08548 for ; Mon, 24 Nov 2003 09:30:54 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 24 Nov 2003 09:30:54 -0500 Message-ID: From: "Kevin Boyle" To: anilj@cisco.com, "'Rasool Wani'" , "'Krishnamurthy V'" Cc: "'vijayabama gurunathan'" , megaco@ietf.org, "'Christian Groves'" Subject: RE: [Megaco] LONG-TIMER expiry handling Date: Mon, 24 Nov 2003 09:30:53 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Well.... You'd know when the other side retransmits the transaction that the response was not received. In any case, the three way handshake is optional and dependent upon your transport. Any "conformance" test that requires use of the three way handshake is wrong. Kevin -----Original Message----- From: Anil Jangam (anilj) [mailto:anilj@cisco.com] Sent: Monday, November 24, 2003 8:38 AM To: 'Rasool Wani'; 'Krishnamurthy V' Cc: 'vijayabama gurunathan'; megaco@ietf.org; Boyle, Kevin [NCRTP:3Z40:EXCH]; 'Christian Groves' Subject: RE: [Megaco] LONG-TIMER expiry handling ***The retransmission of the TransactionReply is an exceptional case in Three-way-handshake only.*** In this perticular feature, unless you receive the TxnResAck for the given TxnReply, the Three-way-handshake is not completed. Once you send the TxnReply, how are you going to know that the other side has really received it or not? > -----Original Message----- > From: Rasool Wani [mailto:rasool.wani@utstar.com] > Sent: Monday, November 24, 2003 6:24 PM > To: anilj@cisco.com; 'Krishnamurthy V' > Cc: 'vijayabama gurunathan'; megaco@ietf.org > Subject: Re: [Megaco] LONG-TIMER expiry handling > > > anil, > you mean TransactionReply's are to be retransmitted too.but > 8@H.248.1 (last para) reads like this: > > Applications SHOULD implement an application level timer per > transaction. Expiration of the timer should cause a retransmission of > the request. Receipt of a Reply should cancel the timer. Receipt of > Pending should restart the timer. > > I understand it only says about the retransmission of > TransactionRequest. > > Rasool wani > > > ----- Original Message ----- > From: "Anil Jangam (anilj)" > To: "'Krishnamurthy V'" ; "'Rasool Wani'" > > Cc: "'vijayabama gurunathan'" ; > > Sent: Monday, November 24, 2003 6:47 PM > Subject: RE: [Megaco] LONG-TIMER expiry handling > > > > Hi Krish, > > > > Upon the expiry of the retransmission timer, the given transaction > > should be repeated/retransmitted. See 8@h.248.1 (last > para). According > > to this, in case of three-way-handshake, it is necessary to > repeat the > > Transaction Reply if the timer expiry happens before you > receive the > > TxnResAck. This behaviour will continue till the Long Timer > associated > > with the Transaction Reply expires. > > > > /anil. > > > > > > > > > -----Original Message----- > > > From: megaco-admin@ietf.org > [mailto:megaco-admin@ietf.org] On Behalf > > > Of Krishnamurthy V > > > Sent: Monday, November 24, 2003 11:18 PM > > > To: Rasool Wani > > > Cc: vijayabama gurunathan; megaco@ietf.org > > > Subject: Re: [Megaco] LONG-TIMER expiry handling > > > > > > > > > hi rasool, > > > > > > this is with respect to the document TSS&TP, ETSI TS 101 889-2, > > > which says the valid behaviour of an MGC should be : > > > > > > "on expiry the Transaction Timer without the receipt of the > > > corresponding Transaction Response Acknowledge, resends > the previous > > > Transaction Reply" > > > > > > refer the test case TP/MGC/TR/BV-02, i.e. 5.2.10.1. > > > > > > does it contradicts with the rfc or i got it wrong? > > > > > > please clarify. thank you. > > > -krish. > > > > > > Rasool Wani wrote: > > > > > > >Destroy it, first one. > > > >Rasool Wani > > > > > > > > > > > > > > > >----- Original Message ----- > > > >From: "vijayabama gurunathan" > > > >To: > > > >Sent: Thursday, November 20, 2003 7:32 PM > > > >Subject: [Megaco] LONG-TIMER expiry handling > > > > > > > > > > > > > > > > > > > >>hi, > > > >>from megaco version-2, > > > >> > > > >> "The copy of the responses may be destroyed either > > > LONG-TIMER seconds > > > >> after the response is issued, or when the entity receives a > > > >> confirmation that the response has been received, through the > > > >> "Response Acknowledgement parameter"." > > > >> > > > >>When the long timer expires, what should be done? > > > >> *) Destroy the copy of the responses. > > > >> or > > > >> *) Resend the response and destroy the copy of the response. > > > >> > > > >>which one is correct? > > > >> > > > >>thanks in advance, > > > >>bama > > > >> > > > >> > > > >> > > > > > > -- > > > -------------------------------------------------------------- > > > ----------- > > > V Krishnamurthy Phone (O): 080-2263399 Ext:255 > > > Internet Telephony Group, (R): 080-3339368 > > > C-DoT, 71/1, Miller Road, (M): 98453 79041 > > > Bangalore - 560052 > > > -------------------------------------------------------------- > > > ----------- > > > The very strength that protects the heart from injury is the > > > strength that prevents the heart from enlarging to its intended > > > greatness within. -Kahlil Gibran. > > > -------------------------------------------------------------- > > > ----------- > > > > > > > > > > > > _______________________________________________ > > > 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-admin@ietf.org Mon Nov 24 20:47:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15917 for ; Mon, 24 Nov 2003 20:47:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOSI9-0001qw-OX; Mon, 24 Nov 2003 20:47:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOSHX-0001pz-Nf for megaco@optimus.ietf.org; Mon, 24 Nov 2003 20:46:23 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15893 for ; Mon, 24 Nov 2003 20:46:08 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOSHV-0002nA-00 for megaco@ietf.org; Mon, 24 Nov 2003 20:46:21 -0500 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1AOSHU-0002mH-00 for megaco@ietf.org; Mon, 24 Nov 2003 20:46:21 -0500 Received: from cisco.com (171.71.177.238) by sj-iport-5.cisco.com with ESMTP; 24 Nov 2003 17:45:44 -0800 Received: from sampathkw2k02 (dhcp-171-71-9-200.cisco.com [171.71.9.200]) by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id hAP1jmjq028970 for ; Mon, 24 Nov 2003 17:45:48 -0800 (PST) From: "Sampath Komanduri" To: Date: Mon, 24 Nov 2003 17:45:43 -0800 Message-ID: <003301c3b2f5$d9c16e10$c80947ab@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Subject: [Megaco] Descriptor processing on Termination OOS Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi, What should be the descriptors state when a termination is service changed to state OOS? Is it ok to remove all the descriptors that are currently applied on the termination or should MG keep the information of descriptors so that they can be re-applied if the termination comes to in-service state again. Thanks, Sampath _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Mon Nov 24 20:47:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15932 for ; Mon, 24 Nov 2003 20:47:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOSIH-0001sM-4c for megaco-archive@odin.ietf.org; Mon, 24 Nov 2003 20:47:09 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAP1l9aa007204 for megaco-archive@odin.ietf.org; Mon, 24 Nov 2003 20:47:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOSIG-0001s7-Qs for megaco-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 20:47:08 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15913 for ; Mon, 24 Nov 2003 20:46:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOSIE-0002q7-00 for megaco-web-archive@ietf.org; Mon, 24 Nov 2003 20:47:06 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AOSIE-0002q4-00 for megaco-web-archive@ietf.org; Mon, 24 Nov 2003 20:47:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOSI9-0001qw-OX; Mon, 24 Nov 2003 20:47:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOSHX-0001pz-Nf for megaco@optimus.ietf.org; Mon, 24 Nov 2003 20:46:23 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15893 for ; Mon, 24 Nov 2003 20:46:08 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOSHV-0002nA-00 for megaco@ietf.org; Mon, 24 Nov 2003 20:46:21 -0500 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1AOSHU-0002mH-00 for megaco@ietf.org; Mon, 24 Nov 2003 20:46:21 -0500 Received: from cisco.com (171.71.177.238) by sj-iport-5.cisco.com with ESMTP; 24 Nov 2003 17:45:44 -0800 Received: from sampathkw2k02 (dhcp-171-71-9-200.cisco.com [171.71.9.200]) by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id hAP1jmjq028970 for ; Mon, 24 Nov 2003 17:45:48 -0800 (PST) From: "Sampath Komanduri" To: Date: Mon, 24 Nov 2003 17:45:43 -0800 Message-ID: <003301c3b2f5$d9c16e10$c80947ab@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Subject: [Megaco] Descriptor processing on Termination OOS Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, What should be the descriptors state when a termination is service changed to state OOS? Is it ok to remove all the descriptors that are currently applied on the termination or should MG keep the information of descriptors so that they can be re-applied if the termination comes to in-service state again. Thanks, Sampath _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Tue Nov 25 09:40:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19218 for ; Tue, 25 Nov 2003 09:40:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOeMF-0004u9-QP; Tue, 25 Nov 2003 09:40:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOb2F-0001ep-NR for megaco@optimus.ietf.org; Tue, 25 Nov 2003 06:07:11 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12578 for ; Tue, 25 Nov 2003 06:06:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOb2B-00021r-00 for megaco@ietf.org; Tue, 25 Nov 2003 06:07:07 -0500 Received: from cvis162.marconicomms.com ([128.87.251.112]) by ietf-mx with esmtp (Exim 4.12) id 1AOb2A-00021f-00 for megaco@ietf.org; Tue, 25 Nov 2003 06:07:07 -0500 Received: from cvis156.mail.marconicomms.com by cvis162.marconicomms.com with ESMTP (8.11.7p1+Sun/mcig-4) id hAPB6a004436; Tue, 25 Nov 2003 11:06:36 GMT Received: from cvdgwy01.uk.marconicomms.com (unverified) by cvis154.mail.marconicomms.com (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Tue, 25 Nov 2003 11:06:29 +0000 To: megaco@ietf.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: "Wayne Cutler" Date: Tue, 25 Nov 2003 11:06:25 +0000 X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1 (5012HF354 | August 26, 2003) at 25/11/2003 11:06:25 MIME-Version: 1.0 Content-type: text/plain; charset="us-ascii" Subject: [Megaco] Embedded Events Behaviour Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , I would like to seek clarification as to when an "off-hook" event is reported when requested with a related Embedded Descriptor, e.g. something like the following (from the Call Flows document) :- Events = 1111 {al/of , Embed { signals {cg/dl}, Events=1112 { al/on}, {dd/ce {Dmap1}}} The Megaco Call Flows document shows the off-hook being reported to the MGC on detection followed by a subsequent notification to the MGC when the received/dialled digits match the digit map in the embedded request. Can it be confirmed that this is the correct behaviour? If so, where in the RFC is this behaviour explicitly described ? If this behaviour is correct, then it is noted that there is a difference between MGCP and MEGACO. MGCP would, when using an embedded request, have sent a single notification to the MGC containing botht the "off-hook" and dialled digits. Is there any historical reason for this difference between MGCP & MEGACO ? Reagards, Wayne. _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Tue Nov 25 09:40:25 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19233 for ; Tue, 25 Nov 2003 09:40:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOeMK-0004vh-VF for megaco-archive@odin.ietf.org; Tue, 25 Nov 2003 09:40:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAPEe8Vg018943 for megaco-archive@odin.ietf.org; Tue, 25 Nov 2003 09:40:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOeMK-0004vS-EL for megaco-web-archive@optimus.ietf.org; Tue, 25 Nov 2003 09:40:08 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19193 for ; Tue, 25 Nov 2003 09:39:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOeMI-0005xT-00 for megaco-web-archive@ietf.org; Tue, 25 Nov 2003 09:40:06 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AOeMI-0005xP-00 for megaco-web-archive@ietf.org; Tue, 25 Nov 2003 09:40:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOeMF-0004u9-QP; Tue, 25 Nov 2003 09:40:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOb2F-0001ep-NR for megaco@optimus.ietf.org; Tue, 25 Nov 2003 06:07:11 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12578 for ; Tue, 25 Nov 2003 06:06:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOb2B-00021r-00 for megaco@ietf.org; Tue, 25 Nov 2003 06:07:07 -0500 Received: from cvis162.marconicomms.com ([128.87.251.112]) by ietf-mx with esmtp (Exim 4.12) id 1AOb2A-00021f-00 for megaco@ietf.org; Tue, 25 Nov 2003 06:07:07 -0500 Received: from cvis156.mail.marconicomms.com by cvis162.marconicomms.com with ESMTP (8.11.7p1+Sun/mcig-4) id hAPB6a004436; Tue, 25 Nov 2003 11:06:36 GMT Received: from cvdgwy01.uk.marconicomms.com (unverified) by cvis154.mail.marconicomms.com (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Tue, 25 Nov 2003 11:06:29 +0000 To: megaco@ietf.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: "Wayne Cutler" Date: Tue, 25 Nov 2003 11:06:25 +0000 X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1 (5012HF354 | August 26, 2003) at 25/11/2003 11:06:25 MIME-Version: 1.0 Content-type: text/plain; charset="us-ascii" Subject: [Megaco] Embedded Events Behaviour Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , I would like to seek clarification as to when an "off-hook" event is reported when requested with a related Embedded Descriptor, e.g. something like the following (from the Call Flows document) :- Events = 1111 {al/of , Embed { signals {cg/dl}, Events=1112 { al/on}, {dd/ce {Dmap1}}} The Megaco Call Flows document shows the off-hook being reported to the MGC on detection followed by a subsequent notification to the MGC when the received/dialled digits match the digit map in the embedded request. Can it be confirmed that this is the correct behaviour? If so, where in the RFC is this behaviour explicitly described ? If this behaviour is correct, then it is noted that there is a difference between MGCP and MEGACO. MGCP would, when using an embedded request, have sent a single notification to the MGC containing botht the "off-hook" and dialled digits. Is there any historical reason for this difference between MGCP & MEGACO ? Reagards, Wayne. _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Wed Nov 26 03:01:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26658 for ; Wed, 26 Nov 2003 03:01:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOubg-0001x5-Cz; Wed, 26 Nov 2003 03:01:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOubE-0001vi-6J for megaco@optimus.ietf.org; Wed, 26 Nov 2003 03:00:36 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26624 for ; Wed, 26 Nov 2003 03:00:21 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOubA-00016w-00 for megaco@ietf.org; Wed, 26 Nov 2003 03:00:32 -0500 Received: from sess01.rdp.asi.alcatel.es ([194.224.48.69]) by ietf-mx with esmtp (Exim 4.12) id 1AOub9-00016S-00 for megaco@ietf.org; Wed, 26 Nov 2003 03:00:31 -0500 Received: from sers002.rpi.ses.alcatel.es (localhost [127.0.0.1]) by sess01.rdp.asi.alcatel.es (8.12.10/8.12.10) with ESMTP id hAQ7xvTJ002503; Wed, 26 Nov 2003 08:59:57 +0100 (MET) Received: from alcatel.es (serp3121.rpi.ses.alcatel.es [159.23.113.121]) by sers002.rpi.ses.alcatel.es (8.8.8+Sun/8.8.8) with ESMTP id JAA19414; Wed, 26 Nov 2003 09:00:36 +0100 (MET) Message-ID: <3FC45F87.99167FB6@alcatel.es> Date: Wed, 26 Nov 2003 09:08:39 +0100 From: Manuel Poza Organization: Alcatel X-Mailer: Mozilla 4.78 [es] (WinNT; U) X-Accept-Language: es MIME-Version: 1.0 To: Wayne Cutler CC: megaco@ietf.org Subject: Re: [Megaco] Embedded Events Behaviour References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi, Wayne, In section 7.1.9 of RFC 3525 is stated that: "When an event is processed against the contents of an active Events Descriptor and found to be present in that descriptor ("recognized"), the default action of the MG is to send a Notify command to the MGC. Notification may be deferred if the event is absorbed into the current dial string of an active digit map (see 7.1.14). Any other action is for further study." It can be concluded from this paragraph that, with the exception of digits detection, recognised events are notified by default. As fas as I know additional exceptions (for instance, for events included in an events descriptor containing an embedded descriptor) have not been considered so far. Manuel Wayne Cutler ha escrito: > I would like to seek clarification as to when an "off-hook" event is > reported when requested with a related Embedded Descriptor, e.g. > something like the following (from the Call Flows document) :- > > Events = 1111 {al/of , Embed { signals {cg/dl}, Events=1112 { al/on}, > {dd/ce {Dmap1}}} > > The Megaco Call Flows document shows the off-hook being reported to the MGC > on detection followed by a subsequent notification to the MGC > when the received/dialled digits match the digit map in the embedded > request. Can it be confirmed that this is the correct behaviour? If so, > where in the > RFC is this behaviour explicitly described ? > > If this behaviour is correct, then it is noted that there is a difference > between MGCP and MEGACO. MGCP would, when using an embedded request, have > sent a single notification to the MGC containing botht the "off-hook" and > dialled digits. Is there any historical reason for this difference > between MGCP & MEGACO ? > > Reagards, > Wayne. > > _______________________________________________ > 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 exim@www1.ietf.org Wed Nov 26 03:01:26 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26673 for ; Wed, 26 Nov 2003 03:01:26 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOubl-0001yS-Sa for megaco-archive@odin.ietf.org; Wed, 26 Nov 2003 03:01:10 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAQ8190Y007589 for megaco-archive@odin.ietf.org; Wed, 26 Nov 2003 03:01:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOubl-0001yK-Jr for megaco-web-archive@optimus.ietf.org; Wed, 26 Nov 2003 03:01:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26631 for ; Wed, 26 Nov 2003 03:00:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOubh-000175-00 for megaco-web-archive@ietf.org; Wed, 26 Nov 2003 03:01:05 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AOubh-000172-00 for megaco-web-archive@ietf.org; Wed, 26 Nov 2003 03:01:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOubg-0001x5-Cz; Wed, 26 Nov 2003 03:01:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOubE-0001vi-6J for megaco@optimus.ietf.org; Wed, 26 Nov 2003 03:00:36 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26624 for ; Wed, 26 Nov 2003 03:00:21 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOubA-00016w-00 for megaco@ietf.org; Wed, 26 Nov 2003 03:00:32 -0500 Received: from sess01.rdp.asi.alcatel.es ([194.224.48.69]) by ietf-mx with esmtp (Exim 4.12) id 1AOub9-00016S-00 for megaco@ietf.org; Wed, 26 Nov 2003 03:00:31 -0500 Received: from sers002.rpi.ses.alcatel.es (localhost [127.0.0.1]) by sess01.rdp.asi.alcatel.es (8.12.10/8.12.10) with ESMTP id hAQ7xvTJ002503; Wed, 26 Nov 2003 08:59:57 +0100 (MET) Received: from alcatel.es (serp3121.rpi.ses.alcatel.es [159.23.113.121]) by sers002.rpi.ses.alcatel.es (8.8.8+Sun/8.8.8) with ESMTP id JAA19414; Wed, 26 Nov 2003 09:00:36 +0100 (MET) Message-ID: <3FC45F87.99167FB6@alcatel.es> Date: Wed, 26 Nov 2003 09:08:39 +0100 From: Manuel Poza Organization: Alcatel X-Mailer: Mozilla 4.78 [es] (WinNT; U) X-Accept-Language: es MIME-Version: 1.0 To: Wayne Cutler CC: megaco@ietf.org Subject: Re: [Megaco] Embedded Events Behaviour References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, Wayne, In section 7.1.9 of RFC 3525 is stated that: "When an event is processed against the contents of an active Events Descriptor and found to be present in that descriptor ("recognized"), the default action of the MG is to send a Notify command to the MGC. Notification may be deferred if the event is absorbed into the current dial string of an active digit map (see 7.1.14). Any other action is for further study." It can be concluded from this paragraph that, with the exception of digits detection, recognised events are notified by default. As fas as I know additional exceptions (for instance, for events included in an events descriptor containing an embedded descriptor) have not been considered so far. Manuel Wayne Cutler ha escrito: > I would like to seek clarification as to when an "off-hook" event is > reported when requested with a related Embedded Descriptor, e.g. > something like the following (from the Call Flows document) :- > > Events = 1111 {al/of , Embed { signals {cg/dl}, Events=1112 { al/on}, > {dd/ce {Dmap1}}} > > The Megaco Call Flows document shows the off-hook being reported to the MGC > on detection followed by a subsequent notification to the MGC > when the received/dialled digits match the digit map in the embedded > request. Can it be confirmed that this is the correct behaviour? If so, > where in the > RFC is this behaviour explicitly described ? > > If this behaviour is correct, then it is noted that there is a difference > between MGCP and MEGACO. MGCP would, when using an embedded request, have > sent a single notification to the MGC containing botht the "off-hook" and > dialled digits. Is there any historical reason for this difference > between MGCP & MEGACO ? > > Reagards, > Wayne. > > _______________________________________________ > 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-admin@ietf.org Wed Nov 26 08:34:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06331 for ; Wed, 26 Nov 2003 08:34:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOznt-00020i-Vc; Wed, 26 Nov 2003 08:34:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOzlj-0001xN-Se for megaco@optimus.ietf.org; Wed, 26 Nov 2003 08:33:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06252 for ; Wed, 26 Nov 2003 08:31:34 -0500 (EST) From: Albrecht.Schwarz@alcatel.de Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOzli-0005XP-00 for megaco@ietf.org; Wed, 26 Nov 2003 08:31:46 -0500 Received: from mailrelay2.alcatel.de ([194.113.59.71] helo=mailrelay1.alcatel.de) by ietf-mx with esmtp (Exim 4.12) id 1AOzlh-0005V3-00 for megaco@ietf.org; Wed, 26 Nov 2003 08:31:46 -0500 Received: from slsas5.stgl.netd.alcatel.de (destgs0000c.ad1.ad.alcatel.com [149.204.45.57]) by mailrelay1.alcatel.de (8.12.10/8.12.10) with ESMTP id hAQDVBZo003755; Wed, 26 Nov 2003 13:31:11 GMT To: CHATRAS Bruno FTRD/DAC/ISS Cc: TISPAN_WG3@LIST.ETSI.ORG, tsg16q3@itu.int, tsg11ncap@itu.int, megaco@ietf.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: Date: Wed, 26 Nov 2003 14:31:06 +0100 X-MIMETrack: Serialize by Router on DEMTA001/DE/ALCATEL(Release 5.0.11 |July 24, 2002) at 11/26/2003 02:31:12 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Alcanet-virus-scanned: hAQDVBZo003755 at mailrelay1.alcatel.de Subject: [Megaco] TISPAN vs Q.NCAP?; Re: New draft on Gate Control protocol Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Dear Mr Chatras, due to the fact that I'm neither involved in TISPAN WG3 nor SG11 NCAP, I'm wondering how is the relation between Draft Q.NCAP3 and your TISPAN H.248 Profile? Are these complemental or disjoint activities? Thanks, Albrecht Schwarz ALCATEL |---------+---------------------------------> | | CHATRAS Bruno | | | FTRD/DAC/ISS | | | | | | Sent by: "TISPAN_WG3: | | | Protocols" | | | | | | | | | | | | 25.11.2003 18:49 | | | Please respond to | | | CHATRAS Bruno | | | FTRD/DAC/ISS | | | | |---------+---------------------------------> >------------------------------------------------------------------------------------------------------------| | | | To: TISPAN_WG3@LIST.ETSI.ORG | | cc: | | Subject: New draft on Gate Control protocol | >------------------------------------------------------------------------------------------------------------| Dear Colleagues, A new draft of the ETSI Gate Control protocol specification is available as TD070 at the following location. http://docbox.etsi.org/tispan/tispan/50-20031201-Sophia/02TD070%20H248Profile%20GC.zip I take the opportunity of this message to remind you that this ES has some dependencies on the EMP Package defined in TS 101 332. During the TISPAN meeting we agreed that this package should be registered by IANA and that a corrigendum to TS 101 332 should be issued. However, the EMP package is still missing on the IANA web site where packages are supposed to be registered (http://www.iana.org/assignments/megaco-h248), and apparently, there is no input contribution with a proposed corrigendum to TS 101 332. Regards, Bruno Mail archive for TISPAN_WG3 can be browsed at the following url : http://list.etsi.org/TISPAN_WG3.html _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Wed Nov 26 08:36:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06366 for ; Wed, 26 Nov 2003 08:36:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOzpF-00027W-HH for megaco-archive@odin.ietf.org; Wed, 26 Nov 2003 08:36:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAQDZPXI008149 for megaco-archive@odin.ietf.org; Wed, 26 Nov 2003 08:35:25 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOzpF-00027M-D1 for megaco-web-archive@optimus.ietf.org; Wed, 26 Nov 2003 08:35:25 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06312 for ; Wed, 26 Nov 2003 08:33:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOznv-0005Z9-00 for megaco-web-archive@ietf.org; Wed, 26 Nov 2003 08:34:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AOznu-0005Z6-00 for megaco-web-archive@ietf.org; Wed, 26 Nov 2003 08:34:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOznt-00020i-Vc; Wed, 26 Nov 2003 08:34:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOzlj-0001xN-Se for megaco@optimus.ietf.org; Wed, 26 Nov 2003 08:33:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06252 for ; Wed, 26 Nov 2003 08:31:34 -0500 (EST) From: Albrecht.Schwarz@alcatel.de Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOzli-0005XP-00 for megaco@ietf.org; Wed, 26 Nov 2003 08:31:46 -0500 Received: from mailrelay2.alcatel.de ([194.113.59.71] helo=mailrelay1.alcatel.de) by ietf-mx with esmtp (Exim 4.12) id 1AOzlh-0005V3-00 for megaco@ietf.org; Wed, 26 Nov 2003 08:31:46 -0500 Received: from slsas5.stgl.netd.alcatel.de (destgs0000c.ad1.ad.alcatel.com [149.204.45.57]) by mailrelay1.alcatel.de (8.12.10/8.12.10) with ESMTP id hAQDVBZo003755; Wed, 26 Nov 2003 13:31:11 GMT To: CHATRAS Bruno FTRD/DAC/ISS Cc: TISPAN_WG3@LIST.ETSI.ORG, tsg16q3@itu.int, tsg11ncap@itu.int, megaco@ietf.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: Date: Wed, 26 Nov 2003 14:31:06 +0100 X-MIMETrack: Serialize by Router on DEMTA001/DE/ALCATEL(Release 5.0.11 |July 24, 2002) at 11/26/2003 02:31:12 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Alcanet-virus-scanned: hAQDVBZo003755 at mailrelay1.alcatel.de Subject: [Megaco] TISPAN vs Q.NCAP?; Re: New draft on Gate Control protocol Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Dear Mr Chatras, due to the fact that I'm neither involved in TISPAN WG3 nor SG11 NCAP, I'm wondering how is the relation between Draft Q.NCAP3 and your TISPAN H.248 Profile? Are these complemental or disjoint activities? Thanks, Albrecht Schwarz ALCATEL |---------+---------------------------------> | | CHATRAS Bruno | | | FTRD/DAC/ISS | | | | | | Sent by: "TISPAN_WG3: | | | Protocols" | | | | | | | | | | | | 25.11.2003 18:49 | | | Please respond to | | | CHATRAS Bruno | | | FTRD/DAC/ISS | | | | |---------+---------------------------------> >------------------------------------------------------------------------------------------------------------| | | | To: TISPAN_WG3@LIST.ETSI.ORG | | cc: | | Subject: New draft on Gate Control protocol | >------------------------------------------------------------------------------------------------------------| Dear Colleagues, A new draft of the ETSI Gate Control protocol specification is available as TD070 at the following location. http://docbox.etsi.org/tispan/tispan/50-20031201-Sophia/02TD070%20H248Profile%20GC.zip I take the opportunity of this message to remind you that this ES has some dependencies on the EMP Package defined in TS 101 332. During the TISPAN meeting we agreed that this package should be registered by IANA and that a corrigendum to TS 101 332 should be issued. However, the EMP package is still missing on the IANA web site where packages are supposed to be registered (http://www.iana.org/assignments/megaco-h248), and apparently, there is no input contribution with a proposed corrigendum to TS 101 332. Regards, Bruno Mail archive for TISPAN_WG3 can be browsed at the following url : http://list.etsi.org/TISPAN_WG3.html _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Thu Nov 27 23:37:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01358 for ; Thu, 27 Nov 2003 23:37:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APaNJ-0000gc-Ig; Thu, 27 Nov 2003 23:37:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APaMT-0000fV-FU for megaco@optimus.ietf.org; Thu, 27 Nov 2003 23:36:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01330 for ; Thu, 27 Nov 2003 23:35:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1APaMR-0002f2-00 for megaco@ietf.org; Thu, 27 Nov 2003 23:36:07 -0500 Received: from wiproecmx1.wipro.com ([164.164.31.5]) by ietf-mx with esmtp (Exim 4.12) id 1APaMP-0002eo-00 for megaco@ietf.org; Thu, 27 Nov 2003 23:36:06 -0500 Received: from ecvwall7.wipro.com (ecvwall7.wipro.com [10.200.52.125]) by wiproecmx1.wipro.com (8.12.9-20031013/8.12.9) with SMTP id hAS4ZU1T012261 for ; Fri, 28 Nov 2003 10:05:31 +0530 (IST) Received: from blr-ec-bh2.wipro.com ([10.200.50.92]) by ecvwall7 with InterScan Messaging Security Suite; Fri, 28 Nov 2003 10:09:34 +0530 Received: from blr-ec-msg03.wipro.com ([10.200.52.99]) by blr-ec-bh2.wipro.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 28 Nov 2003 10:03:37 +0530 Received: from ushaiyer ([10.200.1.217]) by blr-ec-msg03.wipro.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 28 Nov 2003 10:03:37 +0530 Reply-To: From: "Usha Iyer" To: Subject: RE: [Megaco] Embedded Events Behaviour Date: Fri, 28 Nov 2003 10:04:56 +0530 Message-ID: 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.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: <3FC45F87.99167FB6@alcatel.es> Importance: Normal X-OriginalArrivalTime: 28 Nov 2003 04:33:37.0780 (UTC) FILETIME=[CAA8EB40:01C3B568] Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi Wayne, MGCP has a provision to associate action(s) with each of the requested event. So, specifying an embedded request alone would not result in a single notification. The off-hook event in the request should be qualified with action 'accumulate' and Digitmap event should be qualified with action 'notify imm' , for the MG to report the events in a single notification. Please correct me if my understanding is wrong. If you are looking for an event(s) buffering /accumulation mechanism, Megaco provides for this via EventsBufferDescriptor. You may want to refer sections 7.1.9 and 7.1.10 in the rfc for the same. Regards, Usha >-----Original Message----- >From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of >Manuel Poza >Sent: Wednesday, November 26, 2003 1:39 PM >To: Wayne Cutler >Cc: megaco@ietf.org >Subject: Re: [Megaco] Embedded Events Behaviour > > >Hi, Wayne, > >In section 7.1.9 of RFC 3525 is stated that: > >"When an event is processed against the contents of an active >Events Descriptor >and found to be present in that descriptor ("recognized"), the >default action >of the MG is to send a Notify command to the MGC. Notification may >be deferred >if the event is absorbed into the current dial string of an active >digit map >(see 7.1.14). Any other action is for further study." > >It can be concluded from this paragraph that, with the exception of digits >detection, recognised events are notified by default. As fas as I know >additional exceptions (for instance, for events included in an events >descriptor containing an embedded descriptor) have not been >considered so far. > >Manuel > >Wayne Cutler ha escrito: > >> I would like to seek clarification as to when an "off-hook" event is >> reported when requested with a related Embedded Descriptor, e.g. >> something like the following (from the Call Flows document) :- >> >> Events = 1111 {al/of , Embed { signals {cg/dl}, >Events=1112 { al/on}, >> {dd/ce {Dmap1}}} >> >> The Megaco Call Flows document shows the off-hook being reported >to the MGC >> on detection followed by a subsequent notification to the MGC >> when the received/dialled digits match the digit map in the embedded >> request. Can it be confirmed that this is the correct behaviour? If so, >> where in the >> RFC is this behaviour explicitly described ? >> >> If this behaviour is correct, then it is noted that there is a difference >> between MGCP and MEGACO. MGCP would, when using an embedded >request, have >> sent a single notification to the MGC containing botht the "off-hook" and >> dialled digits. Is there any historical reason for this difference >> between MGCP & MEGACO ? >> >> Reagards, >> Wayne. >> >> _______________________________________________ >> 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 exim@www1.ietf.org Thu Nov 27 23:37:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01373 for ; Thu, 27 Nov 2003 23:37:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APaNO-0000j6-VQ for megaco-archive@odin.ietf.org; Thu, 27 Nov 2003 23:37:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAS4b6xi002783 for megaco-archive@odin.ietf.org; Thu, 27 Nov 2003 23:37:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APaNO-0000io-MF for megaco-web-archive@optimus.ietf.org; Thu, 27 Nov 2003 23:37:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01349 for ; Thu, 27 Nov 2003 23:36:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1APaNM-0002fY-00 for megaco-web-archive@ietf.org; Thu, 27 Nov 2003 23:37:04 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1APaNM-0002fU-00 for megaco-web-archive@ietf.org; Thu, 27 Nov 2003 23:37:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APaNJ-0000gc-Ig; Thu, 27 Nov 2003 23:37:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APaMT-0000fV-FU for megaco@optimus.ietf.org; Thu, 27 Nov 2003 23:36:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01330 for ; Thu, 27 Nov 2003 23:35:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1APaMR-0002f2-00 for megaco@ietf.org; Thu, 27 Nov 2003 23:36:07 -0500 Received: from wiproecmx1.wipro.com ([164.164.31.5]) by ietf-mx with esmtp (Exim 4.12) id 1APaMP-0002eo-00 for megaco@ietf.org; Thu, 27 Nov 2003 23:36:06 -0500 Received: from ecvwall7.wipro.com (ecvwall7.wipro.com [10.200.52.125]) by wiproecmx1.wipro.com (8.12.9-20031013/8.12.9) with SMTP id hAS4ZU1T012261 for ; Fri, 28 Nov 2003 10:05:31 +0530 (IST) Received: from blr-ec-bh2.wipro.com ([10.200.50.92]) by ecvwall7 with InterScan Messaging Security Suite; Fri, 28 Nov 2003 10:09:34 +0530 Received: from blr-ec-msg03.wipro.com ([10.200.52.99]) by blr-ec-bh2.wipro.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 28 Nov 2003 10:03:37 +0530 Received: from ushaiyer ([10.200.1.217]) by blr-ec-msg03.wipro.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 28 Nov 2003 10:03:37 +0530 Reply-To: From: "Usha Iyer" To: Subject: RE: [Megaco] Embedded Events Behaviour Date: Fri, 28 Nov 2003 10:04:56 +0530 Message-ID: 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.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: <3FC45F87.99167FB6@alcatel.es> Importance: Normal X-OriginalArrivalTime: 28 Nov 2003 04:33:37.0780 (UTC) FILETIME=[CAA8EB40:01C3B568] Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Wayne, MGCP has a provision to associate action(s) with each of the requested event. So, specifying an embedded request alone would not result in a single notification. The off-hook event in the request should be qualified with action 'accumulate' and Digitmap event should be qualified with action 'notify imm' , for the MG to report the events in a single notification. Please correct me if my understanding is wrong. If you are looking for an event(s) buffering /accumulation mechanism, Megaco provides for this via EventsBufferDescriptor. You may want to refer sections 7.1.9 and 7.1.10 in the rfc for the same. Regards, Usha >-----Original Message----- >From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of >Manuel Poza >Sent: Wednesday, November 26, 2003 1:39 PM >To: Wayne Cutler >Cc: megaco@ietf.org >Subject: Re: [Megaco] Embedded Events Behaviour > > >Hi, Wayne, > >In section 7.1.9 of RFC 3525 is stated that: > >"When an event is processed against the contents of an active >Events Descriptor >and found to be present in that descriptor ("recognized"), the >default action >of the MG is to send a Notify command to the MGC. Notification may >be deferred >if the event is absorbed into the current dial string of an active >digit map >(see 7.1.14). Any other action is for further study." > >It can be concluded from this paragraph that, with the exception of digits >detection, recognised events are notified by default. As fas as I know >additional exceptions (for instance, for events included in an events >descriptor containing an embedded descriptor) have not been >considered so far. > >Manuel > >Wayne Cutler ha escrito: > >> I would like to seek clarification as to when an "off-hook" event is >> reported when requested with a related Embedded Descriptor, e.g. >> something like the following (from the Call Flows document) :- >> >> Events = 1111 {al/of , Embed { signals {cg/dl}, >Events=1112 { al/on}, >> {dd/ce {Dmap1}}} >> >> The Megaco Call Flows document shows the off-hook being reported >to the MGC >> on detection followed by a subsequent notification to the MGC >> when the received/dialled digits match the digit map in the embedded >> request. Can it be confirmed that this is the correct behaviour? If so, >> where in the >> RFC is this behaviour explicitly described ? >> >> If this behaviour is correct, then it is noted that there is a difference >> between MGCP and MEGACO. MGCP would, when using an embedded >request, have >> sent a single notification to the MGC containing botht the "off-hook" and >> dialled digits. Is there any historical reason for this difference >> between MGCP & MEGACO ? >> >> Reagards, >> Wayne. >> >> _______________________________________________ >> 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-admin@ietf.org Fri Nov 28 10:59:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02278 for ; Fri, 28 Nov 2003 10:59:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APl1J-0003AA-9N; Fri, 28 Nov 2003 10:59:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APl10-00036I-Te for megaco@optimus.ietf.org; Fri, 28 Nov 2003 10:58:43 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02232 for ; Fri, 28 Nov 2003 10:58:28 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1APl0y-00043u-00 for megaco@ietf.org; Fri, 28 Nov 2003 10:58:40 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1APl0x-00043k-00 for megaco@ietf.org; Fri, 28 Nov 2003 10:58:39 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hASFw2g28761 for ; Fri, 28 Nov 2003 10:58:02 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 28 Nov 2003 10:58:02 -0500 Message-ID: From: "Kevin Boyle" To: Wayne Cutler , megaco@ietf.org Subject: RE: [Megaco] Embedded Events Behaviour Date: Fri, 28 Nov 2003 10:58:00 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Your description is correct -- all events must be reported when detected, regardless of whether the event has signals and/or events embedded on it. I believe others have described the text where this is stated. I would point out that there are many differences between MGCP and H.248 -- this being one of the smaller differences. As for why, it is illegal to send a single Notify command with two Events descriptors. This means that the MG would have to build messages with two commands, and so really isn't saving much over sending one message at the time of each event detection. Further, I cannot understand why it is good practice for the MG to hold onto event notifications for any length of time. If the MGC wants to know an event occurred, then why wouldn't the MG send the event right away? The MGC may want to take action based upon the event, even if it had already embedded the next processing step. By holding onto the notification, the MG is limiting the MGC's abilities. Kevin -----Original Message----- From: Wayne Cutler [mailto:Wayne.Cutler@marconi.com] Sent: Tuesday, November 25, 2003 6:06 AM To: megaco@ietf.org Subject: [Megaco] Embedded Events Behaviour I would like to seek clarification as to when an "off-hook" event is reported when requested with a related Embedded Descriptor, e.g. something like the following (from the Call Flows document) :- Events = 1111 {al/of , Embed { signals {cg/dl}, Events=1112 { al/on}, {dd/ce {Dmap1}}} The Megaco Call Flows document shows the off-hook being reported to the MGC on detection followed by a subsequent notification to the MGC when the received/dialled digits match the digit map in the embedded request. Can it be confirmed that this is the correct behaviour? If so, where in the RFC is this behaviour explicitly described ? If this behaviour is correct, then it is noted that there is a difference between MGCP and MEGACO. MGCP would, when using an embedded request, have sent a single notification to the MGC containing botht the "off-hook" and dialled digits. Is there any historical reason for this difference between MGCP & MEGACO ? Reagards, Wayne. _______________________________________________ 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 exim@www1.ietf.org Fri Nov 28 10:59:26 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02300 for ; Fri, 28 Nov 2003 10:59:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APl1R-0003F0-Qj for megaco-archive@odin.ietf.org; Fri, 28 Nov 2003 10:59:10 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hASFx91R012452 for megaco-archive@odin.ietf.org; Fri, 28 Nov 2003 10:59:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APl1R-0003El-N9 for megaco-web-archive@optimus.ietf.org; Fri, 28 Nov 2003 10:59:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02249 for ; Fri, 28 Nov 2003 10:58:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1APl1O-00044O-00 for megaco-web-archive@ietf.org; Fri, 28 Nov 2003 10:59:07 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1APl1O-00044L-00 for megaco-web-archive@ietf.org; Fri, 28 Nov 2003 10:59:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APl1J-0003AA-9N; Fri, 28 Nov 2003 10:59:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APl10-00036I-Te for megaco@optimus.ietf.org; Fri, 28 Nov 2003 10:58:43 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02232 for ; Fri, 28 Nov 2003 10:58:28 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1APl0y-00043u-00 for megaco@ietf.org; Fri, 28 Nov 2003 10:58:40 -0500 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 1APl0x-00043k-00 for megaco@ietf.org; Fri, 28 Nov 2003 10:58:39 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hASFw2g28761 for ; Fri, 28 Nov 2003 10:58:02 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 28 Nov 2003 10:58:02 -0500 Message-ID: From: "Kevin Boyle" To: Wayne Cutler , megaco@ietf.org Subject: RE: [Megaco] Embedded Events Behaviour Date: Fri, 28 Nov 2003 10:58:00 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Your description is correct -- all events must be reported when detected, regardless of whether the event has signals and/or events embedded on it. I believe others have described the text where this is stated. I would point out that there are many differences between MGCP and H.248 -- this being one of the smaller differences. As for why, it is illegal to send a single Notify command with two Events descriptors. This means that the MG would have to build messages with two commands, and so really isn't saving much over sending one message at the time of each event detection. Further, I cannot understand why it is good practice for the MG to hold onto event notifications for any length of time. If the MGC wants to know an event occurred, then why wouldn't the MG send the event right away? The MGC may want to take action based upon the event, even if it had already embedded the next processing step. By holding onto the notification, the MG is limiting the MGC's abilities. Kevin -----Original Message----- From: Wayne Cutler [mailto:Wayne.Cutler@marconi.com] Sent: Tuesday, November 25, 2003 6:06 AM To: megaco@ietf.org Subject: [Megaco] Embedded Events Behaviour I would like to seek clarification as to when an "off-hook" event is reported when requested with a related Embedded Descriptor, e.g. something like the following (from the Call Flows document) :- Events = 1111 {al/of , Embed { signals {cg/dl}, Events=1112 { al/on}, {dd/ce {Dmap1}}} The Megaco Call Flows document shows the off-hook being reported to the MGC on detection followed by a subsequent notification to the MGC when the received/dialled digits match the digit map in the embedded request. Can it be confirmed that this is the correct behaviour? If so, where in the RFC is this behaviour explicitly described ? If this behaviour is correct, then it is noted that there is a difference between MGCP and MEGACO. MGCP would, when using an embedded request, have sent a single notification to the MGC containing botht the "off-hook" and dialled digits. Is there any historical reason for this difference between MGCP & MEGACO ? Reagards, Wayne. _______________________________________________ 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-admin@ietf.org Fri Nov 28 11:19:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02658 for ; Fri, 28 Nov 2003 11:19:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APlKf-00046H-Iz; Fri, 28 Nov 2003 11:19:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APlBg-0003tM-KA for megaco@optimus.ietf.org; Fri, 28 Nov 2003 11:09:44 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02474 for ; Fri, 28 Nov 2003 11:09:29 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1APlBd-0004Da-00 for megaco@ietf.org; Fri, 28 Nov 2003 11:09:41 -0500 Received: from cvis162.marconicomms.com ([128.87.251.112]) by ietf-mx with esmtp (Exim 4.12) id 1APlBc-0004DN-00 for megaco@ietf.org; Fri, 28 Nov 2003 11:09:40 -0500 Received: from cvis155.mail.marconicomms.com by cvis162.marconicomms.com with ESMTP (8.11.7p1+Sun/mcig-4) id hASG99022285; Fri, 28 Nov 2003 16:09:09 GMT Received: from cvdgwy01.uk.marconicomms.com (unverified) by cvis155.mail.marconicomms.com (Content Technologies SMTPRS 4.3.10) with ESMTP id ; Fri, 28 Nov 2003 16:09:07 +0000 Subject: RE: [Megaco] Embedded Events Behaviour To: kboyle@nortelnetworks.com Cc: megaco@ietf.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: "Wayne Cutler" Date: Fri, 28 Nov 2003 16:09:00 +0000 X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1 (5012HF354 | August 26, 2003) at 28/11/2003 16:08:56 MIME-Version: 1.0 Content-type: text/plain; charset="us-ascii" Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Thanks for the info. I agree that it is better practice for the MG not to hold onto notifications for any length of time. I was just trying to get to the bottom of why there was such a difference between MGCP & H248. Regards, Wayne _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From exim@www1.ietf.org Fri Nov 28 11:19:30 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02678 for ; Fri, 28 Nov 2003 11:19:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APlKp-00047x-VK for megaco-archive@odin.ietf.org; Fri, 28 Nov 2003 11:19:12 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hASGJBsN015859 for megaco-archive@odin.ietf.org; Fri, 28 Nov 2003 11:19:11 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APlKp-00047i-QT for megaco-web-archive@optimus.ietf.org; Fri, 28 Nov 2003 11:19:11 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02633 for ; Fri, 28 Nov 2003 11:18:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1APlKk-0004NO-00 for megaco-web-archive@ietf.org; Fri, 28 Nov 2003 11:19:06 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1APlKj-0004NI-00 for megaco-web-archive@ietf.org; Fri, 28 Nov 2003 11:19:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APlKf-00046H-Iz; Fri, 28 Nov 2003 11:19:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APlBg-0003tM-KA for megaco@optimus.ietf.org; Fri, 28 Nov 2003 11:09:44 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02474 for ; Fri, 28 Nov 2003 11:09:29 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1APlBd-0004Da-00 for megaco@ietf.org; Fri, 28 Nov 2003 11:09:41 -0500 Received: from cvis162.marconicomms.com ([128.87.251.112]) by ietf-mx with esmtp (Exim 4.12) id 1APlBc-0004DN-00 for megaco@ietf.org; Fri, 28 Nov 2003 11:09:40 -0500 Received: from cvis155.mail.marconicomms.com by cvis162.marconicomms.com with ESMTP (8.11.7p1+Sun/mcig-4) id hASG99022285; Fri, 28 Nov 2003 16:09:09 GMT Received: from cvdgwy01.uk.marconicomms.com (unverified) by cvis155.mail.marconicomms.com (Content Technologies SMTPRS 4.3.10) with ESMTP id ; Fri, 28 Nov 2003 16:09:07 +0000 Subject: RE: [Megaco] Embedded Events Behaviour To: kboyle@nortelnetworks.com Cc: megaco@ietf.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: "Wayne Cutler" Date: Fri, 28 Nov 2003 16:09:00 +0000 X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1 (5012HF354 | August 26, 2003) at 28/11/2003 16:08:56 MIME-Version: 1.0 Content-type: text/plain; charset="us-ascii" Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Thanks for the info. I agree that it is better practice for the MG not to hold onto notifications for any length of time. I was just trying to get to the bottom of why there was such a difference between MGCP & H248. Regards, Wayne _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco From megaco-admin@ietf.org Fri Nov 28 11:52:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03574 for ; Fri, 28 Nov 2003 11:52:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APlqb-00056a-NH; Fri, 28 Nov 2003 11:52:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APlqF-00056D-Vc for megaco@optimus.ietf.org; Fri, 28 Nov 2003 11:51:40 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03527 for ; Fri, 28 Nov 2003 11:51:26 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1APlqE-000520-00 for megaco@ietf.org; Fri, 28 Nov 2003 11:51:38 -0500 Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx with esmtp (Exim 4.12) id 1APlqE-00051J-00 for megaco@ietf.org; Fri, 28 Nov 2003 11:51:38 -0500 Received: from zcard307.ca.nortel.com (americasm03.nt.com [47.129.242.67]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hASGow320953; Fri, 28 Nov 2003 11:50:59 -0500 (EST) Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard307.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id XLYH882M; Fri, 28 Nov 2003 11:50:58 -0500 Received: from nortelnetworks.com (acart1ge.ca.nortel.com [47.129.129.189]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id XLPWM74A; Fri, 28 Nov 2003 11:50:59 -0500 Message-ID: <3FC77CF2.7030108@nortelnetworks.com> Date: Fri, 28 Nov 2003 11:50:58 -0500 X-Sybari-Space: 00000000 00000000 00000000 00000000 From: Tom Taylor User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Wayne Cutler CC: "Kevin Boyle" , megaco@ietf.org Subject: Re: [Megaco] Embedded Events Behaviour References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit The event model for Megaco was one of the really contentious items that took months to work out. The basic problem is that the MGCP mechanisms mix together some state machines that we in Megaco felt should be handled separately in the protocol. It's been a long time -- I would have to refresh myself on the details. Wayne Cutler wrote: > Thanks for the info. > > I agree that it is better practice for the MG not to hold onto > notifications for any length of time. I was just trying to get to the > bottom of why there was such a > difference between MGCP & H248. > > Regards, > Wayne > > > > _______________________________________________ > 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 exim@www1.ietf.org Fri Nov 28 11:52:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03589 for ; Fri, 28 Nov 2003 11:52:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APlqf-00057d-D6 for megaco-archive@odin.ietf.org; Fri, 28 Nov 2003 11:52:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hASGq5gm019683 for megaco-archive@odin.ietf.org; Fri, 28 Nov 2003 11:52:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APlqf-00057O-8P for megaco-web-archive@optimus.ietf.org; Fri, 28 Nov 2003 11:52:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03541 for ; Fri, 28 Nov 2003 11:51:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1APlqe-00052U-00 for megaco-web-archive@ietf.org; Fri, 28 Nov 2003 11:52:04 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1APlqd-00052R-00 for megaco-web-archive@ietf.org; Fri, 28 Nov 2003 11:52:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APlqb-00056a-NH; Fri, 28 Nov 2003 11:52:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APlqF-00056D-Vc for megaco@optimus.ietf.org; Fri, 28 Nov 2003 11:51:40 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03527 for ; Fri, 28 Nov 2003 11:51:26 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1APlqE-000520-00 for megaco@ietf.org; Fri, 28 Nov 2003 11:51:38 -0500 Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx with esmtp (Exim 4.12) id 1APlqE-00051J-00 for megaco@ietf.org; Fri, 28 Nov 2003 11:51:38 -0500 Received: from zcard307.ca.nortel.com (americasm03.nt.com [47.129.242.67]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hASGow320953; Fri, 28 Nov 2003 11:50:59 -0500 (EST) Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard307.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id XLYH882M; Fri, 28 Nov 2003 11:50:58 -0500 Received: from nortelnetworks.com (acart1ge.ca.nortel.com [47.129.129.189]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id XLPWM74A; Fri, 28 Nov 2003 11:50:59 -0500 Message-ID: <3FC77CF2.7030108@nortelnetworks.com> Date: Fri, 28 Nov 2003 11:50:58 -0500 X-Sybari-Space: 00000000 00000000 00000000 00000000 From: Tom Taylor User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Wayne Cutler CC: "Kevin Boyle" , megaco@ietf.org Subject: Re: [Megaco] Embedded Events Behaviour References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: megaco-admin@ietf.org Errors-To: megaco-admin@ietf.org X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Media Gateway Control List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit The event model for Megaco was one of the really contentious items that took months to work out. The basic problem is that the MGCP mechanisms mix together some state machines that we in Megaco felt should be handled separately in the protocol. It's been a long time -- I would have to refresh myself on the details. Wayne Cutler wrote: > Thanks for the info. > > I agree that it is better practice for the MG not to hold onto > notifications for any length of time. I was just trying to get to the > bottom of why there was such a > difference between MGCP & H248. > > Regards, > Wayne > > > > _______________________________________________ > 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