1. 19 March 2003draft-burger-sipping-netann-05.txt1 Network Announcements with SIP IETF 56 Eric Burger eburger@snowshore.com

2. 19 March 2003draft-burger-sipping-netann-05.txt2 Open Issue: Media on Hold What Does Media Server Do When It Receives Hold Requests? [RFC3264] –Option 1: Suspend Play; Time Stops for VoiceXML –Option 2: Time Moves Forward (Same as PSTN) –Option 3: Invoker Specified –Option 4: a:sendonly/recvonly Silently Play Media (no RTP); Time Moves Forward a:inactive Suspend Play (Better than PSTN?) Call Waiting Interaction w/IVR Not An Issue w/ Early Media Propose Option 1

3. 19 March 2003draft-burger-sipping-netann-05.txt3 Open Issue: 409 Result Code 487 Reserved for Response to CANCEL Virtual CANCEL idea didn’t fly Would 480 Be Better? –Looks like out of resource, but –Distinct from 503 Only Issue for annc Proposal: New Result Code –409 REQUEST REJECTED –The UAS has, for whatever reason, rejected the request. Use cases for this result code include the user at the UAS explicitly rejecting the request (e.g., releasing the call before answering) or to terminate a session that occurs before the session is fully established.

4. 19 March 2003draft-burger-sipping-netann-05.txt4 Open Issue: Multiple Media Streams Netann describes a mechanism with associating a single URI for play or IVR with the given SDP. What about audio and video? –Associate SDP m=lines with URI parameters –Embed play/script targets in SDP –Punt Not an issue if play URI is a composite object (e.g., MPEG-2 or MPEG-4) –Is this is predominant use case?

5. 19 March 2003draft-burger-sipping-netann-05.txt5 Planned Changes for –06 Show full early media exchanges (OK to PRACK) VoiceXML Keywords w/o Values Generates 404 With Explanation Eradicate stray 487’s Describe Overload Behavior (503)