
From emil@prolancer.com.au  Thu Dec 11 15:32:35 2014
Return-Path: <emil@prolancer.com.au>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 257121A1A5E for <siprec@ietfa.amsl.com>; Thu, 11 Dec 2014 15:32:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.422
X-Spam-Level: ***
X-Spam-Status: No, score=3.422 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FH_RELAY_NODNS=1.451, HELO_EQ_AU=0.377, HTML_MESSAGE=0.001, RDNS_NONE=0.793] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TOWLdZFHAm9t for <siprec@ietfa.amsl.com>; Thu, 11 Dec 2014 15:32:32 -0800 (PST)
Received: from mail.prolancer.com.au (unknown [58.108.227.239]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C19141A0018 for <siprec@ietf.org>; Thu, 11 Dec 2014 15:32:31 -0800 (PST)
Received: from buswst001 (bus-wst-001.wsn.prolancer.com.au [192.168.120.56]) by mail.prolancer.com.au (8.13.8/8.13.8) with ESMTP id sBBNWRq9026311 for <siprec@ietf.org>; Fri, 12 Dec 2014 10:32:28 +1100
From: "Emil Andonov" <member@prolancer.com.au>
Sender: "Emil Andonov" <emil@prolancer.com.au>
To: <siprec@ietf.org>
Date: Fri, 12 Dec 2014 10:32:29 +1100
Message-ID: <009101d0159a$babdeb60$3039c220$@prolancer.com.au>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0092_01D015F6.EE2FEA00"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdAVmLhzTjEflC/AQsiXzva/9L6KNQ==
Content-Language: en-au
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/yBzodDiaZGk9-a2rO9VG-N02KIQ
Subject: [siprec] CS caller and callee in metadata
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec/>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 23:35:44 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0092_01D015F6.EE2FEA00
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

 

I may be missing something very obvious, but I do not see how the SRS will
determine who called whom in a communications session from the metadata it
receives from the SRC. Did Bob call Alice in section "3.2.1. Example 1:
Basic Call", or vice versa?  

 

Recorders store this information for each recording to help with searches
such as "give me all recordings of calls to Alice on  the dd/mm/yyyy .".

 

Unless I am missing something obvious, this information  can be part of the
"session" element - just a suggestion.

 

The issue becomes a bit more complex for recordings of calls with transfer.
Recorders store information such as "Bob called Alice. Alice transferred the
call to Emil ." about the recording. Again, this information is not
available in the metadata.

 

Thank you

Emil

--

Emil Andonov

Prolancer Pty Ltd

 


------=_NextPart_000_0092_01D015F6.EE2FEA00
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-AU link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal>Hi,<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I may be =
missing something very obvious, but I do not see how the SRS will =
determine who called whom in a communications session from the metadata =
it receives from the SRC. Did Bob call Alice in section &#8220;3.2.1. =
Example 1: Basic Call&#8221;, or vice versa? &nbsp;<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Recorders =
store this information for each recording to help with searches such as =
&#8220;give me all recordings of calls to Alice on&nbsp; the dd/mm/yyyy =
&#8230;&#8221;.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Unless I am =
missing something obvious, this information&nbsp; can be part of the =
&#8220;session&#8221; element &#8211; just a =
suggestion.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>The issue becomes a bit more complex for recordings of =
calls with transfer. Recorders store information such as &#8220;Bob =
called Alice. Alice transferred the call to Emil &#8230;&#8221; about =
the recording. Again, this information is not available in the =
metadata.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Thank you<o:p></o:p></p><p =
class=3DMsoNormal>Emil<o:p></o:p></p><p class=3DMsoNormal><b><span =
lang=3DEN-CA =
style=3D'font-size:9.0pt;color:#1F497D;mso-fareast-language:EN-GB'>--<o:p=
></o:p></span></b></p><p class=3DMsoNormal><b><span lang=3DEN-CA =
style=3D'font-size:9.0pt;color:#1F497D;mso-fareast-language:EN-GB'>Emil =
Andonov<o:p></o:p></span></b></p><p class=3DMsoNormal><b><span =
lang=3DEN-CA =
style=3D'font-size:9.0pt;color:#1F497D;mso-fareast-language:EN-GB'>Prolan=
cer Pty Ltd<o:p></o:p></span></b></p><p class=3DMsoNormal><b><span =
lang=3DEN-CA =
style=3D'font-size:9.0pt;color:#1F497D;mso-fareast-language:EN-GB'><o:p>&=
nbsp;</o:p></span></b></p></div></body></html>
------=_NextPart_000_0092_01D015F6.EE2FEA00--


From nobody Mon Dec 15 08:03:46 2014
Return-Path: <andrew.hutton@unify.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FCCD1A8034 for <siprec@ietfa.amsl.com>; Mon, 15 Dec 2014 08:03:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level: 
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nKCK43GovFk9 for <siprec@ietfa.amsl.com>; Mon, 15 Dec 2014 08:03:39 -0800 (PST)
Received: from mx12.unify.com (mx12.unify.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id ECB971A7D83 for <siprec@ietf.org>; Mon, 15 Dec 2014 08:03:09 -0800 (PST)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by mx12.unify.com (Server) with ESMTP id 4718B23F048B; Mon, 15 Dec 2014 17:03:09 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.192]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0195.001; Mon, 15 Dec 2014 17:03:09 +0100
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: Emil Andonov <member@prolancer.com.au>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] CS caller and callee in metadata
Thread-Index: AdAVmLhzTjEflC/AQsiXzva/9L6KNQC4IrHQ
Date: Mon, 15 Dec 2014 16:03:08 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF1E63FDC8@MCHP04MSX.global-ad.net>
References: <009101d0159a$babdeb60$3039c220$@prolancer.com.au>
In-Reply-To: <009101d0159a$babdeb60$3039c220$@prolancer.com.au>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/T1YKIOUwsfws865leQLJfiklc_0
Subject: Re: [siprec] CS caller and callee in metadata
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec/>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Dec 2014 16:03:42 -0000

I think you are right.

http://tools.ietf.org/html/draft-ietf-siprec-metadata-16#section-6.5.1 stat=
es that the roles of participants, which I assume could include calling/cal=
led party, are not specified here and would be the subject of some extensio=
n data.

So this would be a proprietary extension unless somebody defines additional=
 standard metadata for this.

Andy




> -----Original Message-----
> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Emil Andonov
> Sent: 11 December 2014 23:32
> To: siprec@ietf.org
> Subject: [siprec] CS caller and callee in metadata
>=20
> Hi,
>=20
> I may be missing something very obvious, but I do not see how the SRS
> will determine who called whom in a communications session from the
> metadata it receives from the SRC. Did Bob call Alice in section
> "3.2.1. Example 1: Basic Call", or vice versa?
>=20
> Recorders store this information for each recording to help with
> searches such as "give me all recordings of calls to Alice on=A0 the
> dd/mm/yyyy .".
>=20
> Unless I am missing something obvious, this information=A0 can be part of
> the "session" element - just a suggestion.
>=20
> The issue becomes a bit more complex for recordings of calls with
> transfer. Recorders store information such as "Bob called Alice. Alice
> transferred the call to Emil ." about the recording. Again, this
> information is not available in the metadata.
>=20
> Thank you
> Emil
> --
> Emil Andonov
> Prolancer Pty Ltd


From nobody Mon Dec 15 08:38:22 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F4FD1A6FC4 for <siprec@ietfa.amsl.com>; Mon, 15 Dec 2014 08:38:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DoQ0tV8F_sut for <siprec@ietfa.amsl.com>; Mon, 15 Dec 2014 08:38:19 -0800 (PST)
Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C90441A797C for <siprec@ietf.org>; Mon, 15 Dec 2014 08:38:19 -0800 (PST)
Received: from resomta-ch2-18v.sys.comcast.net ([69.252.207.114]) by resqmta-ch2-04v.sys.comcast.net with comcast id Tsci1p0022Udklx01seK6q; Mon, 15 Dec 2014 16:38:19 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-18v.sys.comcast.net with comcast id TseJ1p00H3Ge9ey01seJb7; Mon, 15 Dec 2014 16:38:19 +0000
Message-ID: <548F0E7A.1080601@alum.mit.edu>
Date: Mon, 15 Dec 2014 11:38:18 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: siprec@ietf.org
References: <009101d0159a$babdeb60$3039c220$@prolancer.com.au> <9F33F40F6F2CD847824537F3C4E37DDF1E63FDC8@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF1E63FDC8@MCHP04MSX.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1418661499; bh=eo/q7pI3fDw4C56e+JEXEVhSDDLq9Xcyzrms8bUYzHw=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=jJpT5CcD6C9G+EUKLyp16tE7gKJifioFskCOayniBLCswAHauTqTwLoRIQL71JZuy OALyAYTcHio1CmC8ZIFHffphcyCsTZKhC+SAksSMWf2al0q1GraYoRRzaCUIrGAPbr iVTvwubUaxCzgMFjstNSTr4wn7Hxq0aI0ujbu+hJEqdhS3Ay7M/VMmr/rK2v0me/TG IsAX5XkNaK/ziTloIl40Qml00aunur57RMsDG34PTxlO/pifav3RiQIBNmEGqd9Tfm y4cDrYaZ8H/8bP74zEzy8JCsaPHxIge8oFPTXmECi3FgT8Q3QXPwXqIuvkcGzXYcxS 7cMModqlyZVUg==
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/Xp4WTNmF96gDx-7ZEfZ9FnOUbF4
Subject: Re: [siprec] CS caller and callee in metadata
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec/>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Dec 2014 16:38:21 -0000

On 12/15/14 11:03 AM, Hutton, Andrew wrote:
> I think you are right.
>
> http://tools.ietf.org/html/draft-ietf-siprec-metadata-16#section-6.5.1 states that the roles of participants, which I assume could include calling/called party, are not specified here and would be the subject of some extension data.
>
> So this would be a proprietary extension unless somebody defines additional standard metadata for this.

I think I recall a long discussion about this quite some time ago.
IIRC, as we got into it the roles got confusing and we sidestepped the 
effort of figuring it out. I *think* some of the issues were:
- in call centers the desired distinction is customer/vendor, not
   caller/callee. Sometimes the caller is the customer, sometimes the
   callee is.
- in the case of multiparty calls it gets hard to know who is caller
   and who is callee.

I can imagine that some work could be done to define some useful 
attributes here. But it will take work.

	Thanks,
	Paul

> Andy
>
>
>
>
>> -----Original Message-----
>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Emil Andonov
>> Sent: 11 December 2014 23:32
>> To: siprec@ietf.org
>> Subject: [siprec] CS caller and callee in metadata
>>
>> Hi,
>>
>> I may be missing something very obvious, but I do not see how the SRS
>> will determine who called whom in a communications session from the
>> metadata it receives from the SRC. Did Bob call Alice in section
>> "3.2.1. Example 1: Basic Call", or vice versa?
>>
>> Recorders store this information for each recording to help with
>> searches such as "give me all recordings of calls to Alice on  the
>> dd/mm/yyyy .".
>>
>> Unless I am missing something obvious, this information  can be part of
>> the "session" element - just a suggestion.
>>
>> The issue becomes a bit more complex for recordings of calls with
>> transfer. Recorders store information such as "Bob called Alice. Alice
>> transferred the call to Emil ." about the recording. Again, this
>> information is not available in the metadata.
>>
>> Thank you
>> Emil
>> --
>> Emil Andonov
>> Prolancer Pty Ltd
>
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>


From nobody Mon Dec 15 22:42:51 2014
Return-Path: <rmohanr@cisco.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E5ED1ACD37 for <siprec@ietfa.amsl.com>; Mon, 15 Dec 2014 22:42:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nJUVWoQkVq0t for <siprec@ietfa.amsl.com>; Mon, 15 Dec 2014 22:42:48 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CB991ACD35 for <siprec@ietf.org>; Mon, 15 Dec 2014 22:42:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3030; q=dns/txt; s=iport; t=1418712168; x=1419921768; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=2OdUqGrlz95DkXceMaGazSQBKYCCWtAuB2EoiulPeD0=; b=Qus6y/py5/Xdn9m//aWFuoZglIHfaxqmR/NhCmPoIP5b9tMLbJAUih2+ 4aUPPo0LNtYLmKMAwOeERFWsTtDoisi5169116vZG4fgmMV/w/EZgZdZE W3f7rPPLhCUFzHnuWd+iaeEG1Bi34O/QYo7jnaA8OVkdOz7qqdP3TJIwZ s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoYFANHTj1StJV2R/2dsb2JhbABaDoJ4UlgExWYKhShKAoEZFgEBAQEBfYQMAQEBBAEBAWsXBAIBCA4DAwEBAQEnBycLFAkIAgQBCQmILA3UJQEBAQEBAQEBAQEBAQEBAQEBAQEBARePeQaEIwWJFYRtgz6FMYE7j3wigy89bgEBgUN+AQEB
X-IronPort-AV: E=Sophos;i="5.07,584,1413244800"; d="scan'208";a="380642900"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-4.cisco.com with ESMTP; 16 Dec 2014 06:42:47 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id sBG6gkra026398 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 16 Dec 2014 06:42:47 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.28]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0195.001; Tue, 16 Dec 2014 00:42:46 -0600
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] CS caller and callee in metadata
Thread-Index: AQHQGPuAAikMa3MMcEODIjMEIq/44Q==
Date: Tue, 16 Dec 2014 06:42:46 +0000
Message-ID: <D0B5D12E.1C635%rmohanr@cisco.com>
References: <009101d0159a$babdeb60$3039c220$@prolancer.com.au> <9F33F40F6F2CD847824537F3C4E37DDF1E63FDC8@MCHP04MSX.global-ad.net> <548F0E7A.1080601@alum.mit.edu>
In-Reply-To: <548F0E7A.1080601@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.3.140616
x-originating-ip: [10.196.64.103]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <C36B0B67F5CBEB45B145DEF50AE7379A@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/HhIo_cOYY5bGWxoSwDG2yIs_Cxg
Subject: Re: [siprec] CS caller and callee in metadata
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec/>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Dec 2014 06:42:50 -0000

+1 to Paul=B9s comments. The main reason we did not include this in the
standard metadata was after several discussions we figured out it is not
always possible to determine the caller/callee properly. So it was decided
that this best conveyed as extension data to participant XML element.

Ram

-----Original Message-----
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Date: Monday, 15 December 2014 10:08 pm
To: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] CS caller and callee in metadata

>On 12/15/14 11:03 AM, Hutton, Andrew wrote:
>> I think you are right.
>>
>> http://tools.ietf.org/html/draft-ietf-siprec-metadata-16#section-6.5.1
>>states that the roles of participants, which I assume could include
>>calling/called party, are not specified here and would be the subject of
>>some extension data.
>>
>> So this would be a proprietary extension unless somebody defines
>>additional standard metadata for this.
>
>I think I recall a long discussion about this quite some time ago.
>IIRC, as we got into it the roles got confusing and we sidestepped the
>effort of figuring it out. I *think* some of the issues were:
>- in call centers the desired distinction is customer/vendor, not
>   caller/callee. Sometimes the caller is the customer, sometimes the
>   callee is.
>- in the case of multiparty calls it gets hard to know who is caller
>   and who is callee.
>
>I can imagine that some work could be done to define some useful
>attributes here. But it will take work.
>
>	Thanks,
>	Paul
>
>> Andy
>>
>>
>>
>>
>>> -----Original Message-----
>>> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Emil Andonov
>>> Sent: 11 December 2014 23:32
>>> To: siprec@ietf.org
>>> Subject: [siprec] CS caller and callee in metadata
>>>
>>> Hi,
>>>
>>> I may be missing something very obvious, but I do not see how the SRS
>>> will determine who called whom in a communications session from the
>>> metadata it receives from the SRC. Did Bob call Alice in section
>>> "3.2.1. Example 1: Basic Call", or vice versa?
>>>
>>> Recorders store this information for each recording to help with
>>> searches such as "give me all recordings of calls to Alice on  the
>>> dd/mm/yyyy .".
>>>
>>> Unless I am missing something obvious, this information  can be part of
>>> the "session" element - just a suggestion.
>>>
>>> The issue becomes a bit more complex for recordings of calls with
>>> transfer. Recorders store information such as "Bob called Alice. Alice
>>> transferred the call to Emil ." about the recording. Again, this
>>> information is not available in the metadata.
>>>
>>> Thank you
>>> Emil
>>> --
>>> Emil Andonov
>>> Prolancer Pty Ltd
>>
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec
>>
>
>_______________________________________________
>siprec mailing list
>siprec@ietf.org
>https://www.ietf.org/mailman/listinfo/siprec

