[SIPForum-techwg] Proposal for Action Item 8 from SIPconnectface-to-face

[Elwell, John]

David,
 
No specific comments, except that 12.2 "Retargeting-related services"
seems like it will need to cover a multitude of sins, so may need to
break down further. But let's see what it looks like.
 
Also, if 10 and 11 are going to disregard retargeted calls, they should
at least make it clear that additional requirements for retargeted calls
occur later.
 
John


________________________________

	From: techwg-bounces at sipforum.org
[mailto:techwg-bounces at sipforum.org] On Behalf Of David Hancock
	Sent: 15 October 2008 23:13
	To: techwg at sipforum.org
	Subject: [SIPForum-techwg] Proposal for Action Item 8 from
SIPconnectface-to-face
	
	

	Regarding action-item 8 from SIPconnect face-to-face...

	 

	8.    Action Item to integrate/align sections 10,11,12,13. Dave
Hancock

	and Jamie Palmer of Broadsoft to lead.

	 

	Jamie and I reviewed these sections and the various technical
comments against them, and propose that the 4 existing sections be
collapsed into 2 sections. The organization of the two new sections will
follow the organization of the existing 12 & 13, so that the
new/combined section 10 covers SP Network --> SIP-PBX calls, and the new
11 covers calls from the SIP-PBX --> SP Network calls.

	 

	One of the v00 review comments noted that the procedures in the
existing 10/11/12/13 don't account for the use-case where the SIP-PBX
forwards an incoming call from the SP network back to the SP network in
a new INVITE. For example, the procedures don't support the case where
the PAI of the new INVITE sent from SIP-PBX identifies a user external
to the SIP-PBX. Another comment noted that the procedures don't align
w.r.t., handling of emergency calls. We decided to resolve these issues
by limiting the scope of the new section 11 to basic 2-way calls
originated by a user in the SIP-PBX. Calls incoming to the SIP-PBX that
are forwarded back to the SP network will be described in the subsequent
"Retargeting" section (currently 15.5). Emergency calls will be covered
in a subsequent separate chapter dedicated to emergency calls (currently
15.6.1).

	 

	Another review comment noted that existing section 15.3 "Basic
2-way Calling" contained duplicate material to existing sections
10/11/12/13. We decided to move any unique text from 15.3 into the new
sections 10/11, and delete 15.3.

	 

	With this (proposed) re-org, sections 10 and beyond describe
call signaling for different call types, such as  

	-          basic 2-way calls originating from or terminating to
SIP-PBX, 

	-          calls retargeted by SIP-PBX, 

	-          emergency calls originated by SIP-PBX

	-          etc

	 

	Existing section 14 "Media Attributes and Minimum Requirements"
seems like an odd-man-out in this series. Therefore, we propose that
this media-centric section 14 be moved to later in the document, so that
all the sections related to call signaling can be grouped together. 

	 

	 The new proposed document organization would then look like
this...

	 

	10 Incoming Calls from the Service Provider to the Enterprise

	  {covers basic 2-way DOD calls originated locally by SIP-PBX
user}

	 

	11 Outgoing Calls from the Enterprise to the Service Provider

	  {covers basic 2-way DID calls into SIP-PBX}

	 

	12 Service Interactions

	12.1 Call Hold

	12.2 Retargeting Related Services

	    {includes call-fwding & xfer, and redirect to SP-based voice
message server}

	12.3 Regulatory Services

	     {Describes everything related to emergency calls}

	12.4 Message Waiting Indication 

	    {Describes how to signal the signal message-waiting info to
the SIP-PBX when 

	     the SP network provides the voice-mail service. This wasn't
in the v00 version - 

	     did we miss it, or agree to leave it out?)

	 

	13. Media Requirements

	 

	I'll submit the proposed text for new sections 10 & 11 in a
subsequent email. Once we see how that looks, we may want to make
additional changes (such as moving 10 and 11 into level-2 subsections of
section 12, and change the level-1 name to something like "Call
Signaling Requirements").

	 

	Comments welcome. 

	 

	David

	 

	 

	 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://sipforum.org/pipermail/techwg/attachments/20081016/62f84897/attachment-0001.html