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

[Ofir Roth <[e-mail]>]

Thanks Ram.

I have posted two scenarios which are aligned according to the metadata draft.
Have you had a chance to check them?

BR,
Ofir.

-----Original Message-----
From: Ram Mohan R (rmohanr) [mailto:[e-mail]] 
Sent: Saturday, October 20, 2012 3:03 PM
To: Ofir Roth; Parthasarathi R; [e-mail]
Subject: Re: [siprec] draft-ram-siprec-callflows-01

Ofir,

The schema in the ver 08 is the latest one. The examples in callflows-01 are not yet in sync with that.

We will publish soon the call flows.
As paul mentioned in the other thread, we appreciate if you have any call flows from the implementation/software that we can use.

Regards,
Ram

> On 20/10/12 12:35 AM, "Ofir Roth" <[e-mail]> wrote:

>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:[e-mail]]
>Sent: Wednesday, October 17, 2012 5:28 PM
>To: Ofir Roth; [e-mail]
>Subject: RE: [siprec] draft-ram-siprec-callflows-01
>
>
> 
>Hi Ofir,
> 
>Thanks for your review. Please read inline.
> 
>Thanks
>Partha
> 
>From: [e-mail] [mailto:[e-mail]] On 
>Behalf Of Ofir Roth
>Sent: Wednesday, October 17, 2012 4:46 PM
>To: [e-mail]
>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 mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/siprec
>