[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sip] sip call model



Mahesh Govind wrote:

> Hi,
> can we map sip  calls to any particular call model  ?

Yes.  A complete one-to-one mapping between states will almost
always be impossible, though.  This is because you will seldom
have two call models with the same number of states and
transitions (if you did, why map them at all?)

The utility of the resulting mapping will depend on how
granular the states are between the call models.  For instance,
a call model with less number of states and low cardinality
transitions can still be mapped to a call model with a high
number of states and many transitions through state splitting.
However, introducing an artificial state in this fashion is
problematic at best.  It raises many additional questions: how
does the new state behave in principle with the rest of
the states of the call model in which it was introduced?  The
call model may not be amenable to such an artificial
introduction of a new state. How does the designer of the new
state decide on the amount of functionality that should be
in it, in relation to the state it was carved out from? How
easy will it be to realize such a system in working software?

SIP has been mapped to a PSTN call model quite effectively
for certain services (see RFC3976.)

Hope that helps.

- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg at {alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs
___________________________________________From sip-bounces at ietf.org  Tue Aug 12 08:43:19 2008
Return-Path: <sip-bounces at ietf.org>
X-Original-To: sip-archive at optimus.ietf.org
Delivered-To: ietfarch-sip-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A1203A69D1;
	Tue, 12 Aug 2008 08:43:19 -0700 (PDT)
X-Original-To: sip at core3.amsl.com
Delivered-To: sip at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8CFBA3A6A28
	for <sip at core3.amsl.com>; Tue, 12 Aug 2008 08:43:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OjVllEkWFYVT for <sip at core3.amsl.com>;
	Tue, 12 Aug 2008 08:43:17 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39])
	by core3.amsl.com (Postfix) with ESMTP id 68C003A63C9
	for <sip at ietf.org>; Tue, 12 Aug 2008 08:43:17 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id m7CFhBfc027726
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 12 Aug 2008 10:43:12 -0500 (CDT)
Received: from [135.185.244.90] (il0015vkg1.ih.lucent.com [135.185.244.90])
	by umail.lucent.com (8.13.8/TPES) with ESMTP id m7CFh69R019221;
	Tue, 12 Aug 2008 10:43:06 -0500 (CDT)
Message-ID: <48A1AF8F.50805 at alcatel-lucent.com>
Date: Tue, 12 Aug 2008 10:43:11 -0500
From: "Vijay K. Gurbani" <vkg at alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: vu3mmg at gmail.com
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: IETF SIP List <sip at ietf.org>
Subject: Re: [Sip] sip call model
X-BeenThere: sip at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:sip at ietf.org>
List-Help: <mailto:sip-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request at ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org

Mahesh Govind wrote:

> Hi,
> can we map sip  calls to any particular call model  ?

Yes.  A complete one-to-one mapping between states will almost
always be impossible, though.  This is because you will seldom
have two call models with the same number of states and
transitions (if you did, why map them at all?)

The utility of the resulting mapping will depend on how
granular the states are between the call models.  For instance,
a call model with less number of states and low cardinality
transitions can still be mapped to a call model with a high
number of states and many transitions through state splitting.
However, introducing an artificial state in this fashion is
problematic at best.  It raises many additional questions: how
does the new state behave in principle with the rest of
the states of the call model in which it was introduced?  The
call model may not be amenable to such an artificial
introduction of a new state. How does the designer of the new
state decide on the amount of functionality that should be
in it, in relation to the state it was carved out from? How
easy will it be to realize such a system in working software?

SIP has been mapped to a PSTN call model quite effectively
for certain services (see RFC3976.)

Hope that helps.

- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg at {alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs
_______________________________________________
Sip____
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip


mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip