On Mon, Dec 29, 2014 at 11:12 AM, George Joseph <[email protected] > wrote:
<snip> > In basic scenarios, however, we do have a match between the inbound >> Contact header in the INVITE request and what was provided by that device's >> REGISTER request. >> >> It is possible, however, to not require Asterisk to make this decision in >> the first place. If there was a way to obtain: >> * What channels are associated with an endpoint (which we should know) >> * The Contact headers provided by those channels >> > > Maybe a simple xref container hashed by contact that contains the channel > id. It's populated by any INVITE whether incoming or outgoing? > > I think so. I'll reply with something a bit more concrete on Josh's reply. -- Matthew Jordan Digium, Inc. | Engineering Manager 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
