Re: [siprec] draft-ram-siprec-callflows-01

Ofir Roth <Ofir.Roth@nice.com> Fri, 19 October 2012 19:05 UTC

From: Ofir Roth <Ofir.Roth@nice.com>
To: Parthasarathi R <partha@parthasarathi.co.in>, "siprec@ietf.org" <siprec@ietf.org>
Date: Fri, 19 Oct 2012 21:05:35 +0200
Thread-Topic: [siprec] draft-ram-siprec-callflows-01
Thread-Index: Ac2sV49ORvpLdO1+SSymgnCxmyNtBQAIdO/AAGyk/3A=
Message-ID: <D6FF53BFD24F6F448C70DEF68DB4E6655A8BC75BD1@TLVMBX01.nice.com>
References: <D6FF53BFD24F6F448C70DEF68DB4E6655A8BC055A3@TLVMBX01.nice.com> <003401cdac7b$f98d3bf0$eca7b3d0$@co.in>
In-Reply-To: <003401cdac7b$f98d3bf0$eca7b3d0$@co.in>
Accept-Language: en-US, he-IL
Content-Language: en-US
acceptlanguage: en-US, he-IL
Content-Type: multipart/alternative; boundary="_000_D6FF53BFD24F6F448C70DEF68DB4E6655A8BC75BD1TLVMBX01nicec_"
MIME-Version: 1.0
Subject: Re: [siprec] draft-ram-siprec-callflows-01
Precedence: list

Hi,

According to the metadata scheme:

<xs:complexType name="participant">
       <xs:sequence>
           <xs:element name="nameID" type="nameID"
             maxOccurs="1"/>
        <xs:any namespace='##other'
                   minOccurs='0'
                   maxOccurs='unbounded'
                   processContents='lax'/>
       </xs:sequence>
       <xs:attribute name="participant_id" type="xs:base64Binary"
            use="required"/>
       <xs:attribute name="session_id" type="xs:base64Binary"
            use="required"/>
   </xs:complexType>
There is no associate/disassociate time as part of the participant definition while it appears in the call flow example of section 4.5.

And session is defined as follow:

<xs:complexType name="session">
       <xs:sequence>
         <xs:element name="reason" type="xs:string"
                minOccurs="0"/>
         <xs:element name="group-ref" type="xs:base64Binary"
                minOccurs="0" maxOccurs="1"/>
           <xs:any namespace='##other'
                   minOccurs='0'
                   maxOccurs='unbounded'
                   processContents='lax'/>
       </xs:sequence>
       <xs:attribute name="session_id" type="xs:base64Binary"
            use="required"/>
   </xs:complexType>

According to the session definition, session does not contain start/stop time while it appears in call flow document.

I am interested which is the up to date version that should be used (call flow or metadata scheme).

Thanks,
Ofir.

From: Parthasarathi R [mailto:partha@parthasarathi.co.in]
Sent: Wednesday, October 17, 2012 5:28 PM
To: Ofir Roth; siprec@ietf.org
Subject: RE: [siprec] draft-ram-siprec-callflows-01

Hi Ofir,

Thanks for your review. Please read inline.

Thanks
Partha

From: siprec-bounces@ietf.org<mailto:siprec-bounces@ietf.org> [mailto:siprec-bounces@ietf.org] On Behalf Of Ofir Roth
Sent: Wednesday, October 17, 2012 4:46 PM
To: siprec@ietf.org<mailto:siprec@ietf.org>
Subject: [siprec] draft-ram-siprec-callflows-01

Hello,

I am reviewing the examples provided in draft-ram-siprec-callflows-01 and noticed that it is not aligned according to draft-ietf-siprec-metadata-07.

For example:


1.       Session element does not contain start/stop time
<Partha> I guess that you wish to see the example with start/stop time. We will add in the
 next revision.

BTW,start/stop time are optional elements in session.  So, the callflow is
inline with metadata -07 draft.

</Partha>


2.       Participant does not include disassociate-time (as in section 4.5)
<Partha> Sec 4.5 is call disconnect example and so, disassociate-time exists. Please let me know the exact location where disassociate-time is missing. </Partha>

If those are known issues, I will appreciate if someone can let me know.

Thanks,
Ofir.

[siprec] draft-ram-siprec-callflows-01 Ofir Roth
Re: [siprec] draft-ram-siprec-callflows-01 Parthasarathi R
Re: [siprec] draft-ram-siprec-callflows-01 Ofir Roth
Re: [siprec] draft-ram-siprec-callflows-01 Ram Mohan R (rmohanr)
Re: [siprec] draft-ram-siprec-callflows-01 Ofir Roth
Re: [siprec] draft-ram-siprec-callflows-01 Parthasarathi R