Re: [sipcore] Types of Call

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 03 May 2012 16:17 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C889721F8639 for <sipcore@ietfa.amsl.com>; Thu, 3 May 2012 09:17:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.487
X-Spam-Level:
X-Spam-Status: No, score=-2.487 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O-Cp9s7kpMdS for <sipcore@ietfa.amsl.com>; Thu, 3 May 2012 09:17:52 -0700 (PDT)
Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by ietfa.amsl.com (Postfix) with ESMTP id 337CC21F8625 for <sipcore@ietf.org>; Thu, 3 May 2012 09:17:52 -0700 (PDT)
Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by qmta08.westchester.pa.mail.comcast.net with comcast id 5NMd1j0021YDfWL58UHn3X; Thu, 03 May 2012 16:17:47 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.229.5]) by omta20.westchester.pa.mail.comcast.net with comcast id 5UHr1j00i07duvL3gUHrab; Thu, 03 May 2012 16:17:52 +0000
Message-ID: <4FA2AFAE.2050600@alum.mit.edu>
Date: Thu, 03 May 2012 12:17:50 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: sipcore@ietf.org
References: <CAB0vbd0-dFqV+QJGaD3Luj_whWBnyXOdDcB_TMdBj1-QCbuDcg@mail.gmail.com>
In-Reply-To: <CAB0vbd0-dFqV+QJGaD3Luj_whWBnyXOdDcB_TMdBj1-QCbuDcg@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [sipcore] Types of Call
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 May 2012 16:17:52 -0000

salini,

I'm not certain of the context in which you are asking this question.
In general I think such things are better discussed on 
sip-implementors@lists.cs.columbia.edu. So if you want to have an 
extended discussion I ask you to go there. But I'll give you the short 
version of my opinion:

In practical/real-life we don't have a clear way to indicate this prior 
to answering the call. After answering, it gets handled informally 
in-band. In some cases I suppose it is inferred based on indicated 
identity of the caller.

SIP provides some mechanisms for this, but whether they are useful in 
practice is debatable. The Priority header allows the caller to indicate 
his opinion of the priority of the call. But the callee may choose not 
to believe this because of possibility for abuse. Even if it is 
believed, there is no guarantee that it will be acted on at the callee 
end of the call, or how.

There is also 
http://datatracker.ietf.org/doc/draft-ietf-salud-alert-info-urns/ which 
specifies how to use Alert-Info to cause differing sorts of alerting, 
that can be used to alert differently due to call priority.

Again, if you want to discuss this further, please do it on 
sip-implementors, unless you have a specific issue to make about a 
specific core sip capability.

	Thanks,
	Paul

On 5/3/12 11:44 AM, salini singh wrote:
> Hi,
>
> How do we distinguish URGENT,NON_URGENT,NORMAL,EMERGENCY calls in our
> day to day practical/real-life?
>
> Regards
> -salini
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>