Re: [martini] An event-package for GIN

Paul Kyzivat <> Fri, 29 October 2010 21:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 905D73A6803 for <>; Fri, 29 Oct 2010 14:21:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -110.476
X-Spam-Status: No, score=-110.476 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 6FzDJCMQvLZJ for <>; Fri, 29 Oct 2010 14:21:56 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 7E6E73A6827 for <>; Fri, 29 Oct 2010 14:21:56 -0700 (PDT)
Authentication-Results:; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiMFAE/YykxAZnwM/2dsb2JhbACTWI15caNmnBSFSASKU4MI
X-IronPort-AV: E=Sophos;i="4.58,261,1286150400"; d="scan'208";a="176726973"
Received: from ([]) by with ESMTP; 29 Oct 2010 21:23:51 +0000
Received: from [] ( []) by (8.13.8/8.14.3) with ESMTP id o9TLNp9o007907 for <>; Fri, 29 Oct 2010 21:23:51 GMT
Message-ID: <>
Date: Fri, 29 Oct 2010 17:23:51 -0400
From: Paul Kyzivat <>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20101013 Thunderbird/3.1.5
MIME-Version: 1.0
References: <>
In-Reply-To: <>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [martini] An event-package for GIN
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of en-mass SIP PBX registration mechanisms <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 29 Oct 2010 21:21:57 -0000

I support going through the requirements process.
Hopefully it can be quick. If not, its probably because it isn't as 
straightforward as we think.


On 10/29/2010 3:02 PM, Hadriel Kaplan wrote:
> Howdy,
> At the last Martini meeting in Maastricht, there was general consensus that we need to provide a way for the IP-PBX (or any authorized SIP device) to learn the AoRs/names the SSP has provisioned for expansion a la GIN - i.e., what the SSP will route to the IP-PBX.  The initial proposal in Vermouth-00 was to re-use the reg-event package for this purpose, with some hacks to handle wildcard/range situations.  In Maastricht, there was general agreement to not do that, and instead define a new event package specific to the problem at hand, and unrelated to registration state - effectively just the provisioning info.  Vermouth-01 is a straw-man based on that idea, but it really needs more careful thought, and it raises some bigger questions.  This email is an attempt to start discussion of those.
> 1) In theory, an event-package for this doesn't have to be specific for a GIN-model to begin with, nor any registration-based SIP trunk.  It's really just about learning basic AoR/name provisioning info in a registrar's database.  So the first question is: is Martini the right WG for this work?
> 2) Does it need a list of requirements?  My gut says it probably does, even if it's only a small handful.
> -hadriel
> _______________________________________________
> martini mailing list