Re: [Sip] Connected Destination in SIP

Frank Derks <frank.derks@philips.com> Thu, 29 September 2005 14:37 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKzXn-00042A-GY; Thu, 29 Sep 2005 10:37:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKzXl-00041u-F4; Thu, 29 Sep 2005 10:37:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15661; Thu, 29 Sep 2005 10:37:50 -0400 (EDT)
Received: from gw-eur4.philips.com ([161.85.125.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKzfN-0003xM-VR; Thu, 29 Sep 2005 10:45:49 -0400
Received: from smtpscan-eur4.philips.com (smtpscan-eur4.mail.philips.com [130.144.57.167]) by gw-eur4.philips.com (Postfix) with ESMTP id 1543D49784; Thu, 29 Sep 2005 14:37:32 +0000 (UTC)
Received: from smtpscan-eur4.philips.com (localhost [127.0.0.1]) by localhost.philips.com (Postfix) with ESMTP id DC1DE16B8C; Thu, 29 Sep 2005 14:37:31 +0000 (GMT)
Received: from smtprelay-eur2.philips.com (smtprelay-eur2.philips.com [130.144.57.171]) by smtpscan-eur4.philips.com (Postfix) with ESMTP id C1CBC16B53; Thu, 29 Sep 2005 14:37:31 +0000 (GMT)
Received: from ehvrmh02.diamond.philips.com (ehvrmh02-srv.diamond.philips.com [130.139.27.125]) by smtprelay-eur2.philips.com (Postfix) with ESMTP id 9BE613F; Thu, 29 Sep 2005 14:37:31 +0000 (GMT)
In-Reply-To: <433BF37C.6090208@cisco.com>
To: Jonathan Rosenberg <jdrosen@cisco.com>
Subject: Re: [Sip] Connected Destination in SIP
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0.3 September 26, 2003
Message-ID: <OF9F0236D4.D66D53D3-ONC125708B.004FD378-C125708B.00505648@philips.com>
From: Frank Derks <frank.derks@philips.com>
Date: Thu, 29 Sep 2005 16:35:36 +0200
X-MIMETrack: Serialize by Router on ehvrmh02/H/SERVER/PHILIPS(Release 6.5.3FP1HF287 | September 13, 2005) at 29/09/2005 16:35:36, Serialize complete at 29/09/2005 16:35:36
Content-Type: text/plain; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: sip@ietf.org, sip-bounces@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>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi Jonathan,

Thanks for the quick response. I will read through these drafts and see 
what 
I can do with it.

The fact that it "remains controversial" sounds like there is not a lot 
agreement on whether this should be supported by SIP or that the proposed 
solutions aren't good enough (whether technically or politically). 

What is the real problem?

Frank











Jonathan Rosenberg <jdrosen@cisco.com> 
Sent by:
sip-bounces@ietf.org
2005-09-29 04:00 PM

To
Frank Derks/HVS/BE/PHILIPS@PHILIPS
cc
sip@ietf.org
Subject
Re: [Sip] Connected Destination in SIP
Classification







This subject has gotten a fair bit of discussion and remains a somewhat 
controversial one. Some of the recent drafts on it:

http://www.watersprings.org/pub/id/draft-peterson-sipping-retarget-00.txt
http://www.watersprings.org/pub/id/draft-jennings-sipping-connected-00.txt

There remains strong interest in solving this "connected party problem", 
however.

-Jonathan R.

Frank Derks wrote:

> Hi,
> 
> I went through several SIP specifications to find out how the following 
> could be achieved, but thusfar I have not been able to find this is 
> supposed to be done with SIP. Hopefully someone has an idea.
> 
> When an INVITE is retargeted by a SIP proxy, the actual destination 
> changes. The sender of the INVITE, however, remains unaware of this. 
> I.e. the original sender of the INVITE has no clue as to "who" is at
> the other end. E.g. Alice calls Bob, but Bob has instructed the SIP 
> proxy to forward his calls to Carl. Alice ends up being connected to 
> Carl, but SIP does not communicate this. Only when Carl answers the 
> phone, Alice realises that she's not talking to Bob. 
> 
> I have not seen an obvious way to inform Alice about the identity of 
> the actual destination. Does anyone have ideas?
> 
> Cheers,
> 
> Frank
> 
> _______________________________________________
> 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
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

_______________________________________________
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