Re: [sipcore] reg event package
"Worley, Dale R (Dale)" <dworley@avaya.com> Mon, 25 October 2010 18:16 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 E9FE43A68B0 for <sipcore@core3.amsl.com>; Mon, 25 Oct 2010 11:16:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.429
X-Spam-Level:
X-Spam-Status: No, score=-102.429 tagged_above=-999 required=5 tests=[AWL=0.170, 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 TIoSNqqK8l8o for <sipcore@core3.amsl.com>; Mon, 25 Oct 2010 11:16:03 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 88C5F3A692A for <sipcore@ietf.org>; Mon, 25 Oct 2010 11:16:02 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.58,236,1286164800"; d="scan'208";a="214054948"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 25 Oct 2010 14:17:46 -0400
X-IronPort-AV: E=Sophos;i="4.58,236,1286164800"; d="scan'208";a="528007435"
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 25 Oct 2010 14:17:46 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Mon, 25 Oct 2010 14:17:45 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Dean Willis <dean.willis@softarmor.com>
Date: Mon, 25 Oct 2010 14:14:19 -0400
Thread-Topic: [sipcore] reg event package
Thread-Index: ActyLIhhcbjAfh8gSyWThHzITX34sgCQ+iLC
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B2202288980@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B2202288963@DC-US1MBEX4.global.avaya.com>, <A76B5965-FE19-47DA-9FEF-FA93F9DC07F5@softarmor.com>
In-Reply-To: <A76B5965-FE19-47DA-9FEF-FA93F9DC07F5@softarmor.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] reg event package
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: Mon, 25 Oct 2010 18:16:04 -0000
________________________________________ From: Dean Willis [dean.willis@softarmor.com] > Are there extensions for the reg (registration) event package to > report the Path for the registration, or the reg-id for SIP Outbound? There SHOULD be. Please start typing... ________________________________________ One can carry "reg-id" in an <unknown-param> element. And I discovered that our reg event server uses <unknown-param> to carry the "path" value as well, which is probably not kosher. Dale
- [sipcore] reg event package Worley, Dale R (Dale)
- Re: [sipcore] reg event package Paul Kyzivat
- Re: [sipcore] reg event package Dean Willis
- Re: [sipcore] reg event package Worley, Dale R (Dale)
- Re: [sipcore] reg event package Dean Willis