<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On 14 Oct 2014, at 15:51, Matt Jordan <<a href="mailto:reviewboard@asterisk.org">reviewboard@asterisk.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><pre style="margin-left: 2em; white-space: pre-wrap; word-wrap: break-word;">exten => hint,SIP/alice&CustomPresence:alice
Will *always* use the presence provided by SIP/alice, instead of the custom presence provider. That feels like a loss of functionality.
Prior to this patch, we would only use the presence information provided by a single custom presence provider, since presence information could only come from custom presence providers. If the channel drivers provide that as well, there probably needs to be some mechanism to aggregate that together.</pre></div><br class="Apple-interchange-newline"></blockquote></div>THis looks insane to me, but I must surely have missed something. Have we discussed the definition of "presence" ?<div>In the old days we had extension states and device states - for me that's not presence, but can be input to personal presence.</div><div>What is this stuff?</div><div><br></div><div>Curious. But maybe too late to jump into the discussion :-)</div><div><br></div><div>/O</div></body></html>