RE: [Sip] Extension mobility in SIP

"Steve Langstaff" <steve.langstaff@citel.com> Thu, 31 January 2008 13:05 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JKZ77-0002yb-L7; Thu, 31 Jan 2008 08:05:57 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JKZ76-0002yG-2Y for sip-confirm+ok@megatron.ietf.org; Thu, 31 Jan 2008 08:05:56 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JKZ75-0002xw-Cq for sip@ietf.org; Thu, 31 Jan 2008 08:05:55 -0500
Received: from sea02-mxf01.citel.com ([205.234.66.116]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JKZ74-0001wC-Lv for sip@ietf.org; Thu, 31 Jan 2008 08:05:55 -0500
Received: from [10.8.50.21] (helo=sea02-mxc01.citel.com) by sea02-mxf01.citel.com with smtp (Exim 4.43) id 1JKZ7D-0004Og-2h; Thu, 31 Jan 2008 05:06:03 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] Extension mobility in SIP
Date: Thu, 31 Jan 2008 05:05:46 -0800
Message-ID: <0D4E483A0E6E0A46861409E5D6C2011C01119B22@sea02-mxc01.citel.com>
In-reply-to: <47A1C5C1.3090401@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Extension mobility in SIP
Thread-Index: AchkCMckwyG070J8QwStexagsOPzsAAAQ9rQ
References: <9A1299C7A40D7447A108107E951450CA05AF8A98@MAIL-TVM.tvm.nestgroup.net> <47A1C5C1.3090401@cisco.com>
From: Steve Langstaff <steve.langstaff@citel.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, Anisha Kumar <anisha.kumar@nestgroup.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: sip@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

Or maybe it's a SIPPING config framework question, after some local
conversation?

http://tools.ietf.org/html/draft-ietf-sipping-config-framework-14

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
> Sent: 31 January 2008 12:58
> To: Anisha Kumar
> Cc: sip@ietf.org
> Subject: Re: [Sip] Extension mobility in SIP
> 
> This is largely not a sip question. The UA can register with 
> any AOR (phone number) it wants after some local conversation 
> with the user determine what that AOR should be.
> 
> 	Paul
> 
> Anisha Kumar wrote:
> > Hi,
> > 
> > The Extension Mobility feature dynamically configures a phone 
> > according to the current user. Once a user logs in, the 
> phone adopts 
> > the user individual user default device profile 
> information, including 
> > line numbers, speed dials, services links, and other user-specific 
> > properties of a phone.
> > 
> > For example, when user A occupies a desk and logs in to the 
> phone, her 
> > directory number(s), services, speed dials, and other properties 
> > appear on that phone; but when user B uses the same desk at a 
> > different time, his information appears.
> > 
> > Hope this is clear. How is this achieved in SIP ?
> > 
> > Thanks & Regards,
> > Anisha
> > 
> > -----Original Message-----
> > From: James M. Polk [mailto:jmpolk@cisco.com]
> > Sent: Thursday, January 31, 2008 11:58 AM
> > To: Dean Willis; Anisha Kumar
> > Cc: sip@ietf.org
> > Subject: Re: [Sip] Extension mobility in SIP
> > 
> > At 11:28 PM 1/30/2008, Dean Willis wrote:
> > 
> >> On Jan 30, 2008, at 10:30 PM, Anisha Kumar wrote:
> >>
> >>> Hi ,
> >>>
> >>>  Is there a separate RFC for the implementation of extension 
> >>> mobility
> > 
> >>> in SIP Uas ? If not, is it possible to achieve that ?
> >> What do you mean "extension mobility"? Are you thinking of the use 
> >> case
> > 
> >> where a SIP user agent is moving around and occasionally 
> changes its 
> >> IP
> > 
> >> address and point of attachment to the Internet? Do you 
> expect call 
> >> continuity in such a case, quick recovery of the call 
> afterward, or 
> >> call drop?
> > 
> > A lot of times, 'extension mobility' means the number to 
> call a phone
> > (UA) changes based on who logged (or registered) onto it -- 
> which is 
> > very different that what is above.
> > 
> > 
> >> --
> >> Dean
> >>
> >>
> >> _______________________________________________
> >> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> >> This list is for NEW development of the core SIP Protocol Use 
> >> sip-implementors@cs.columbia.edu for questions on current sip Use 
> >> sipping@ietf.org for new developments on the application of sip
> > 
> > 
> > 
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol Use 
> > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > sipping@ietf.org for new developments on the application of sip
> > 
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip 
> Use sipping@ietf.org for new developments on the application of sip
> 


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