Kevin Boyle | 30 May 06:09 2006

RE: continuity package

Quite simply, it loops the data entering a termination back the
direction it come from out of the termination.

Note that Loopback is a value of the Mode Property, and does not
necessarily indicate a continuity test is occurring.

Kevin

________________________________

From: Rahul Ruikar [mailto:rahul.ruikar <at> gmail.com] 
Sent: Monday, May 29, 2006 11:19 AM
To: megaco <at> ietf.org
Subject: [Megaco] continuity package

Can someone explain "LOOPBACK" provision of megaco continuity test..?

--

-- 
Regards,
Rahul Ruikar
Rahul Ruikar | 30 May 10:04 2006
Picon

Continuity tests

Hi,

in following document for megaco callflow.
http://tools.ietf.org/wg/megaco/draft-ietf-megaco-callflows/draft-ietf-megaco-callflows-04.txt

I found all the parameters for continuity tests are mentioned in "Modify" command. Can we give it in "Add" command . Is there any specific reason for this..?

Thanks,
Rahul Ruikar

_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Kevin Boyle | 30 May 13:57 2006

RE: Segmentation error

I think the best way to fix this will be to have the error text carry
the TransID.  I will see about taking this to Ottawa in August to be
fixed.

Kevin

________________________________

From: B Venkat S.R Swamy [mailto:b.swamy <at> flextronicssoftware.com] 
Sent: Thursday, May 25, 2006 11:40 PM
To: Ron Ho
Cc: megaco
Subject: Re: [Megaco] Segmentation error

Hi

You are right, currently the grammar does not allow for the transaction
ID to be given with "459" error.

Solutions could be:
1) Include the transaction ID in the error text in error descriptor,
currently only missing segment numbers are given. Here the first element
can be transaction id and then list of segments missing.

2) Modify the grammar and include error descriptor also in the new
segment reply message as shown below.
!/3 [12.34.56.79]:2944 SM=1{ER=459{"2,3"}}

 
regards
B Venkat S.R Swamy     
Senior Technical Leader
Flextronics Software Systems
Phone:  +91-124- 4176213
Fax: +91-124-4300247
web: www.flextronicssoftware.com

-----"Ron Ho" <ron.ho.megaco <at> gmail.com> wrote: -----

	To: megaco <megaco <at> ietf.org>
	From: "Ron Ho" <ron.ho.megaco <at> gmail.com>
	Date: 05/26/2006 03:23AM
	Subject: [Megaco] Segmentation error
	
	Hi All,
	
	V3 segmentation procedure specifies that we need to send error
459 if
	we don't get all the segmented responses. However, the sample
call
	flow does not show which transaction the error message is
addressing
	to. Is it correct? Should there be the transaction id in the
error
	message returned?
	
	Thanks,
	Ron.
	
	_______________________________________________
	Megaco mailing list
	Megaco <at> ietf.org
	https://www1.ietf.org/mailman/listinfo/megaco
	

" DISCLAIMER: This message is proprietary to Flextronics Software
Systems Limited (FSS) 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. FSS accepts no responsibility for loss or damage arising
from the use of the information transmitted by this email including
damage from virus."
B Venkat S.R Swamy | 31 May 06:38 2006

Re: Continuity tests

Hi Rahul

It is important to note in the call flow document you are referring , that the continuity test is being done when the termination is in Null context and state as Test, i,e
it is not involved in any call and a maintainance activity is initiated by the operator. Therefore only Modify command is applicable.
There can be a scenario where continuity is to be done in context of a call. In this case all the continuity parameters shall be applied either in the
Add or Modify command and with a valid context(can be Choose also).

regards
B Venkat S.R Swamy
Senior Technical Leader
Flextronics Software Systems
Phone: +91-124- 4176213
Fax: +91-124-4300247
web: www.flextronicssoftware.com
"Rahul Ruikar" <rahul.ruikar <at> gmail.com>


          "Rahul Ruikar" <rahul.ruikar <at> gmail.com>

          05/30/2006 01:34 PM


To

megaco <at> ietf.org

cc


Subject

[Megaco] Continuity tests

Hi,

in following document for megaco callflow.
http://tools.ietf.org/wg/megaco/draft-ietf-megaco-callflows/draft-ietf-megaco-callflows-04.txt

I found all the parameters for continuity tests are mentioned in "Modify" command. Can we give it in "Add" command . Is there any specific reason for this..?

Thanks,
Rahul Ruikar
_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco



*********************** FSS-Restricted ***********************
"DISCLAIMER: This message is proprietary to Flextronics Software
Systems Limited (FSS) 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. FSS 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 <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Albrecht.Schwarz | 31 May 15:01 2006
Picon
Picon

Re: Continuity tests


Rahul,

just a side note that the ServiceState must not be "Test".

See clarification in latest IMG:

T05-SG16-060403-TD-PLEN-0225!!MSW-E

Draft new H.248.1 Version 2 Implementors' Guide

6.23  ServiceStates clarification for continuity testing
"The termination under test does not need to have its ServiceStates
Property set to Test."

- Albrecht

                                                                                                                                         
                      "B Venkat S.R Swamy"                                                                                               
                      <b.swamy <at> flextronicsso         To:      "Rahul Ruikar" <rahul.ruikar <at> gmail.com>                                    
                      ftware.com>                    cc:      megaco <at> ietf.org                                                            
                                                     Subject: Re: [Megaco] Continuity tests                                              
                      31.05.2006 06:38                                                                                                   

Hi Rahul

It is important to note in the call flow document you are referring , that
the continuity test is being done when the termination is in Null context
and state as Test, i,e
it is not involved in any call and a maintainance activity is initiated by
the operator. Therefore only Modify command is applicable.
There can be a scenario where continuity is to be done in context of a
call. In this case all the continuity parameters shall be applied either in
the
Add or Modify command and with a valid context(can be Choose also).

regards
B Venkat S.R Swamy
Senior Technical Leader
Flextronics Software Systems
Phone: +91-124- 4176213
Fax: +91-124-4300247
web: www.flextronicssoftware.com
(Embedded image moved to file: pic03313.gif)"Rahul Ruikar"
<rahul.ruikar <at> gmail.com>

                                                                           
                         "Rahul Ruikar"                                    
                         <rahul.ruikar <at>                                     
                         gmail.com>                                        
                                        (Embedded image moved to file:     
                                        pic01466.gif)                      
                         05/30/2006                                     To 
                         01:34 PM                       (Embedded image    
                                                        moved to file:     
                                                        pic16783.gif)      
                                                        megaco <at> ietf.org    
                                        (Embedded image moved to file:     
                                        pic14163.gif)                      
                                                                        cc 
                                                        (Embedded image    
                                                        moved to file:     
                                                        pic16549.gif)      
                                        (Embedded image moved to file:     
                                        pic25546.gif)                      
                                                                   Subject 
                                                        (Embedded image    
                                                        moved to file:     
                                                        pic00787.gif)      
                                                        [Megaco]           
                                                        Continuity tests   

                                                                           
                                        (Embedded image moved to file:     
                                        pic26231.gif)                      
                                               (Embedded image moved to    
                                               file: pic23111.gif)         

Hi,

in following document for megaco callflow.
http://tools.ietf.org/wg/megaco/draft-ietf-megaco-callflows/draft-ietf-megaco-callflows-04.txt

I found all the parameters for continuity tests are mentioned in "Modify"
command. Can we give it in "Add" command . Is there any specific reason for
this..?

Thanks,
Rahul Ruikar
_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco

*********************** FSS-Restricted ***********************
"DISCLAIMER: This message is proprietary to Flextronics Software
Systems Limited (FSS) 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. FSS 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 <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco

_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Albrecht.Schwarz | 31 May 17:27 2006
Picon
Picon

RE: V.90//V.92 on Megaco


An H.248-controlled Network Access Server (NAS, or RAS), specifically a
Narrwoband-RAS would have the requirement for data/modem termination and
was also originally considered by the MEGACO community (see e.g. the
"available modems" property in the expired "NAS ROOT" package,
http://www.watersprings.org/pub/id/draft-ietf-megaco-naspkg-04.txt).

But H.248-controlled Network Access Servers never really came up, -
certainly one reason why the NAS package wasn't finalized, and certainly
one reason why the modem descriptor was deprecated.

This is also more a DoIP application, but Noel is explicitly wondering
about modem support in VoIP trunking environments, therefore I guess it
comes down to V.150.1 or V.152 or sth else.

- Albrecht

                                                                                                                                   
                      "Kevin Boyle"                                                                                                
                      <kboyle <at> nortel.c         To:      "Rahul Ruikar" <rahul.ruikar <at> gmail.com>, <megaco <at> ietf.org>                 
                      om>                      cc:                                                                                 
                                               Subject: RE: [Megaco] V.90//V.92 on Megaco                                          
                      30.05.2006 06:08                                                                                             

The Modem Descriptor was deprecated in H.248.1 Version 2 in May 2002.

Kevin

________________________________

From: Rahul Ruikar [mailto:rahul.ruikar <at> gmail.com]
Sent: Monday, May 29, 2006 3:39 AM
To: megaco <at> ietf.org
Subject: Re: [Megaco] V.90//V.92 on Megaco

chapter 7.1.2 of Megaco specs ( RFC 3525 ) specifies modem type V.90 you
mentioned can be used.

7.1.2 Modem descriptor

   The Modem descriptor specifies the modem type and parameters, if any,
   required for use in e.g., H.324 and text conversation.  The
   descriptor includes the following modem types: V.18, V.22, V.22 bis,
   V.32, V.32 bis, V.34, V.90, V.91, Synchronous ISDN, and allows for
   extensions.  By default, no Modem descriptor is present in a
   Termination.

Regards,
Rahul Ruikar

Noel Keith wrote:

             Hi All:

             If anybody knows about v.90 and v.92 modems can they
             be used on VoIP Trunking using Megaco like Call
             Control  please clear my doubts...

             Ran

             _________________________________________________________

             Horóscopos, Salud y belleza, Chistes, Consejos de amor:
             el contenido más divertido para tu celular está en Yahoo!
Móvil.

             Obtenelo en http://movil.yahoo.com.ar

             _______________________________________________

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

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


Gmane