Re: T.38 session name in examples

"Kevin Boyle" <[email protected]>
Newsgroups gmane.ietf.megaco
Message-ID <34B3EAA5B3066A42914D28C5ECF5FEA414F03A8E@zrtphxm2.corp.nortel.com>
This misconception continues to pervade, and it is worrisome.
 
The s= line (and other mandatory portions of the SDP specification) are
*NOT* optional in H.248.  They are only optional in the MGC->MG
direction.  In communications from the MG to the MGC, the SDP must be
conformant to RFC 2327.  
 
The text in Clause 7.1.8 is explicit that the exceptions to SDP are
valid only in the MGC->MG direction.  This is to allow the MGC to
provide over- or under-specified SDP.
 
Kevin

________________________________

From: [email protected] [mailto:[email protected]] On Behalf
Of RUIKAR RAHUL A
Sent: Sunday, May 11, 2008 6:07 AM
To: [email protected]
Cc: Schwarz Albrecht
Subject: [Megaco] T.38 session name in examples


Just an observation about ITU-T Rec. T.38 (09/2005)
according to SIP RFC "s" line in SIP messages is mandatory, it is
missing in examples 
given in document. 
Though for H248 this attribute is optional but for messages
sent/received from/to SIP agent 
shall have session name attribute present.
 
 
Regards,
Rahul Ruikar
Alcatel-Lucent
Email: [email protected]
Alcanet: 2721 4732

_______________________________________________
Megaco mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/megaco
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.