Subject: [Megaco] RE:Add Command

From: "Liu Ti,SLC Com FN RDC NA(BJ)" <[email-masked]>
Date: Tue, 1 Aug 2006 11:23:23 +0800

Hi all:

To this ADD Command question, I find an explanation from http://quimby.gnus.org/internet-drafts/draft-rosen-megaco-interop-1-report-00.txt  no 6：

  An MG should always accept a command which has no descriptors, 
  assuming that the contextId and the terminationIds are legal.  
  It's a NOP, but it's legal. 

What is your opinion on this?

If this is a NOP, then whether the termination should be added to the context or just ignore it. What kind of reply should the MG return to MGC when it receives an ADD command without a descriptior.

B.R.
Liu Ti

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] 
Sent: Friday, July 28, 2006 12:00 AM
To: [email-masked]
Subject: Megaco Digest, Vol 27, Issue 35

Send Megaco mailing list submissions to
	[email-masked]

To subscribe or unsubscribe via the World Wide Web, visit
	https://www1.ietf.org/mailman/listinfo/megaco
or, via email, send a message with subject or body 'help' to
	[email-masked]

You can reach the person managing the list at
	[email-masked]

When replying, please edit your Subject line so it is more specific than "Re: Contents of Megaco digest..."

Today's Topics:

   1. Re: Error format (Ashish Singh)
   2. RE: Error format (Wainwright, John (Com US))
   3. Re: Error format (Ashish Singh)
   4. Add Command (Liu Ti,SLC Com FN RDC NA(BJ))

----------------------------------------------------------------------

Message: 1
Date: Wed, 26 Jul 2006 09:36:07 -0700
From: Ashish Singh <[email-masked]>
Subject: Re: [Megaco] Error format
To: "Wainwright, John (Com US)" <[email-masked]>
Cc: [email-masked]
Message-ID: <[email-masked]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi John,

The response is correct from syntax point of view. But H.248.8 mentions 
to include "stream ID" as Error text for this particular error code.

There are many other error codes, for which extra information is 
required. Like with error codes 433 and 435, contextID is returned, so 
that MGC can synchronize its database.

Thanks
Ashish

Wainwright, John (Com US) wrote:
> Is the following format 'valid' for a response to an ADD request
> containing an unsupported codec in the Local descriptor?  Would the 
> same format apply, apart from the error code and text, for any other 
> type of error in the SDP data within the Local descriptor ?
>  
> MEGACO/2 [20.0.4.32]:2084
> REPLY = 269820167 {
>   CONTEXT = 13 {
>     ADD = port_1
>   ,
>     ADD = eph/00337 { 
>           ERROR = 515 {"Unsupported Media Type"} 
>     }
>   }
> }
>  
> Thanks
> John
>  
> ----------------------------------------------------------------------
> --
>
> _______________________________________________
> Megaco mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/megaco
>   

------------------------------

Message: 2
Date: Wed, 26 Jul 2006 11:44:47 -0700
From: "Wainwright, John \(Com US\)" <[email-masked]>
Subject: RE: [Megaco] Error format
To: "Ashish Singh" <[email-masked]>
Cc: [email-masked]
Message-ID:
	<[email-masked]>
	
Content-Type: text/plain;	charset="us-ascii"

So would a more accurate response have something like the following
	ERROR = 515 {"Unsupported Media Type.  Stream = xxx"

If "Stream = 1" can it be omitted and assumed by default ?

Thanks
John

-----Original Message-----
From: Ashish Singh [mailto:[email-masked]] 
Sent: Wednesday, July 26, 2006 11:36 AM
To: Wainwright, John (Com US)
Cc: [email-masked]
Subject: Re: [Megaco] Error format

Hi John,

The response is correct from syntax point of view. But H.248.8 mentions 
to include "stream ID" as Error text for this particular error code.

There are many other error codes, for which extra information is 
required. Like with error codes 433 and 435, contextID is returned, so 
that MGC can synchronize its database.

Thanks
Ashish

Wainwright, John (Com US) wrote:
> Is the following format 'valid' for a response to an ADD request
> containing an unsupported codec in the Local descriptor?  Would the 
> same format apply, apart from the error code and text, for any other 
> type of error in the SDP data within the Local descriptor ?
>  
> MEGACO/2 [20.0.4.32]:2084
> REPLY = 269820167 {
>   CONTEXT = 13 {
>     ADD = port_1
>   ,
>     ADD = eph/00337 { 
>           ERROR = 515 {"Unsupported Media Type"} 
>     }
>   }
> }
>  
> Thanks
> John
>  
>
------------------------------------------------------------------------
>
> _______________________________________________
> Megaco mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/megaco
>   

------------------------------

Message: 3
Date: Wed, 26 Jul 2006 11:55:11 -0700
From: Ashish Singh <[email-masked]>
Subject: Re: [Megaco] Error format
To: "Wainwright, John (Com US)" <[email-masked]>
Cc: [email-masked]
Message-ID: <[email-masked]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

I guess it will be easier for MGC to parse, if we only include 
"streamID" and no other text. IMO, error descriptor should look like:

ERROR = 515 {"xxx"}

Thanks
Ashish

Wainwright, John (Com US) wrote:
> So would a more accurate response have something like the following
> 	ERROR = 515 {"Unsupported Media Type.  Stream = xxx"
>
> If "Stream = 1" can it be omitted and assumed by default ?
>
> Thanks
> John
>
>
> -----Original Message-----
> From: Ashish Singh [mailto:[email-masked]]
> Sent: Wednesday, July 26, 2006 11:36 AM
> To: Wainwright, John (Com US)
> Cc: [email-masked]
> Subject: Re: [Megaco] Error format
>
> Hi John,
>
> The response is correct from syntax point of view. But H.248.8 
> mentions
> to include "stream ID" as Error text for this particular error code.
>
> There are many other error codes, for which extra information is
> required. Like with error codes 433 and 435, contextID is returned, so 
> that MGC can synchronize its database.
>
> Thanks
> Ashish
>
>
> Wainwright, John (Com US) wrote:
>   
>> Is the following format 'valid' for a response to an ADD request
>> containing an unsupported codec in the Local descriptor?  Would the 
>> same format apply, apart from the error code and text, for any other 
>> type of error in the SDP data within the Local descriptor ?
>>  
>> MEGACO/2 [20.0.4.32]:2084
>> REPLY = 269820167 {
>>   CONTEXT = 13 {
>>     ADD = port_1
>>   ,
>>     ADD = eph/00337 { 
>>           ERROR = 515 {"Unsupported Media Type"} 
>>     }
>>   }
>> }
>>  
>> Thanks
>> John
>>  
>>
>>     
> ----------------------------------------------------------------------
> --
>   
>> _______________________________________________
>> Megaco mailing list
>> [email-masked] https://www1.ietf.org/mailman/listinfo/megaco
>>   
>>     
>
>
>   

------------------------------

Message: 4
Date: Wed, 26 Jul 2006 16:29:41 +0800
From: "Liu Ti,SLC Com FN RDC NA(BJ)" <[email-masked]>
Subject: [Megaco] Add Command
To: [email-masked], [email-masked]
Message-ID:
	<[email-masked]>
Content-Type: text/plain; charset="us-ascii"

Hi All:

Does there exist such situation: 
1 An Add Command does not have any descriptor as parameters.
2 An Add command,used to create a Termination, does not have any descriptor as parameters.

Thanks in advance.

B.R
Ti

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www1.ietf.org/pipermail/megaco/attachments/20060726/8e22cac4/attachment.html

------------------------------

_______________________________________________
Megaco mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/megaco

End of Megaco Digest, Vol 27, Issue 35
**************************************

_______________________________________________
Megaco mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/megaco