IETF Logo Mail Archive

Re: [sipcore] SBC-friendliness of 4244bis

"Worley, Dale R (Dale)" <dworley@avaya.com> Tue, 07 September 2010 17:58 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B670E3A6A9A for <sipcore@core3.amsl.com>; Tue, 7 Sep 2010 10:58:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.465
X-Spam-Level:
X-Spam-Status: No, score=-102.465 tagged_above=-999 required=5 tests=[AWL=0.134, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Wzs3yrvl4m3Q for <sipcore@core3.amsl.com>; Tue, 7 Sep 2010 10:58:07 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id AB4D93A6A96 for <sipcore@ietf.org>; Tue, 7 Sep 2010 10:58:07 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,329,1280721600"; d="scan'208";a="33477286"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 07 Sep 2010 13:58:35 -0400
X-IronPort-AV: E=Sophos;i="4.56,329,1280721600"; d="scan'208";a="513566608"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 07 Sep 2010 13:58:35 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.129]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Tue, 7 Sep 2010 13:58:34 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Date: Tue, 07 Sep 2010 13:56:45 -0400
Thread-Topic: [sipcore] SBC-friendliness of 4244bis
Thread-Index: ActLPZLG7oqcbr2GR8yCxbA+k46q9gDeHXgD
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FFC79C2A@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B21FFC79C10@DC-US1MBEX4.global.avaya.com>, <1DB54B42-D77D-447F-84DF-A9D05237047A@acmepacket.com> <CD5674C3CD99574EBA7432465FC13C1B21FFC79C13@DC-US1MBEX4.global.avaya.com>, <EE54A874-863F-4A24-BF1A-8FDC626456D7@acmepacket.com>
In-Reply-To: <EE54A874-863F-4A24-BF1A-8FDC626456D7@acmepacket.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] SBC-friendliness of 4244bis
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 07 Sep 2010 17:58:08 -0000

________________________________________
From: Hadriel Kaplan [HKaplan@acmepacket.com]

And I see them being removed from responses all-together, especially in call centers where they don't want the caller to know the specific agent it was sent to.
________________________________________

That would be unfortunate -- the handling of H-I in responses is as important as handling of H-I in requests, and in principle, the H-I in an outgoing response can be edited to show precisely what the service provider wishes to show about the call's handling.  In any case, the service provider shouldn't edit the H-I entries concerning routing in any other service provider's network (unless there is some sort of joint operating agreement).

Dale

v2.23.0 | Report a Bug | By Email