Re: [Sipping] I-D Action:draft-ietf-sipping-service-examples-15.txt

[Paul Kyzivat <[e-mail]>]

I agree with Andy here. A lot of people seem to think that you must use 
sendonly for hold - that inactive is inappropriate. But that is silly. 
Of course if you really want to you can negotiate sendonly and then not 
send anything. But IMO that shouldn't be held out as best practice. 
Doing so encourages people to build UAs that don't work when offered 
a=inactive.

	Thanks,
	Paul

Hutton, Andrew wrote:
>  
> This new draft still includes the following text in section 2.1 (Call
> Hold).
> 
> "However, a UA that places the other party on hold will generally also
> stop sending media, resulting in no media exchange between the UAs.
> Older UAs may set the connection address to 0.0.0.0 when initiating
> hold.  However, this behavior has been deprecated in favor of using the
> a=sendonly SDP attribute."
> 
> The problem with this statement it indicates that a UA that stops
> sending media when placing a call on hold should use the a=sendonly SDP
> attribute which is incorrect. If a UA does not wish to send or receive
> media then it should use the a=inactive attribute. A UA can use
> a=sendonly for call hold but not in the case when it stops sending
> media. I would really like to see the draft updated to fix this and
> state that a=inactive is the attribute to use when the UA stops sending
> media.
> 
> Regards
> Andy
> 
> 
> 
> 
> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On
> Behalf Of [e-mail]
> Sent: 11 July 2008 19:30
> To: [e-mail]
> Cc: [e-mail]
> Subject: [Sipping] I-D Action:draft-ietf-sipping-service-examples-15.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Session Initiation Proposal
> Investigation Working Group of the IETF.
> 
> 
> 	Title           : Session Initiation Protocol Service Examples
> 	Author(s)       : A. Johnston, et al.
> 	Filename        : draft-ietf-sipping-service-examples-15.txt
> 	Pages           : 167
> 	Date            : 2008-07-11
> 
> This document gives examples of Session Initiation Protocol (SIP)
> services.  This covers most features offered in so-called IP Centrex
> offerings from local exchange carriers and PBX (Private Branch
> Exchange) features.  Most of the services shown in this document are
> implemented in the SIP User Agents, although some require the
> assistance of a SIP Proxy.  Some require some extensions to SIP
> including the REFER, SUBSCRIBE, and NOTIFY methods and the Replaces
> and Join header fields.  These features are not intended to be an
> exhaustive set, but rather show implementations of common features
> likely to be implemented on SIP IP telephones in a business
> environment.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-service-examples-
> 15.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> _______________________________________________
> Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use [e-mail] for questions on current sip
> Use [e-mail] for new developments of core SIP
> 
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [e-mail] for questions on current sip
Use [e-mail] for new developments of core SIP