[asterisk-dev] Asterisk and external SIP subscribtions

[Matthew Jordan]

On Wed, Mar 19, 2014 at 10:00 AM, Olle E. Johansson <oej at edvina.net> wrote:
>
> On 19 Mar 2014, at 15:55, Olle E. Johansson <oej at edvina.net> wrote:
>
>>
>> On 19 Mar 2014, at 15:41, Matthew Jordan <mjordan at digium.com> wrote:
>>
>>> On Wed, Mar 19, 2014 at 9:26 AM, Olle E. Johansson <oej at edvina.net> wrote:
>>>
>>> <snip>
>>>

<snip>

>>>
>>> Fundamentally, I've been thinking about this problem more around
>>> device states: that is, if all Asterisk instances have the ability to
>>> share their device states - whatever those device states happen to
>>> derive from - then every Asterisk instance can build the same
>>> extension states if they so choose to. Or not - but it ends up being a
>>> function of the Asterisk dialplan at each instance, as opposed to
>>> something forced.
>>>
>>> In a world where all Asterisk instances know of the device states for
>>> any other Asterisk instance, can you explain why publishing extension
>>> states are needed?
>>
>> As I said - to off load NOTIFications to phones for blinking lamps.
>> Asterisk PUBLISH extension state to the proxy. The proxy manages
>> all the subscriptions. Everyone is happy and do what they do best.
>
> BTW the PUBLISH is in the good ol' dialog-info XML format.
>

That makes sense. Thanks!

In Asterisk 12/trunk, both the extension state as well as device state
have a subscription based API in Asterisk, so both should be readily
doable without any changes in the core.

I looked in both pinana-initialize-devstate-1.8 as well as
pinana-initialize-devstate-trunk, but I didn't find where the
configuration for publishing device state/extension state was
documented. Admittedly, I was looking at sip.conf.sample - should I be
looking elsewhere?

-- 
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