On Fri, 2009-07-10 at 12:38 -0400, Beeton, Carolyn (CAR:9D60) wrote:
> I think the key is the EventTypeKey, which does contain the parameter.
> This is how I think it works: but I have not tried with different types
> of dialog parameters.
>
> The SubscribeServer is told to accept subscriptions to "dialog" (any
> parameters will do). Both the event type and the key (event with
> parameters, e.g. "dialog;sla") are extracted from the subscription
> message (in AppAgentSubscribePolicy). (Perhaps it is missing a check in
> here: only accept subscriptions for flavours of dialog that we support).
> Then when NOTIFYs are received, only "dialog;sla" events are processed
> (in AppAgentTask).
>
> When new info is published, both the EventType ("dialog") and the
> EventTypeKey ("dialog;sla") are specified (in AppearanceGroup).
>
> Eventually we may handle the other flavours of dialog: "dialog;ma" or
> "dialog;shared". Then we will publish several times with the slightly
> different formats required by each spec.
That's right. And the application provides SipSubscribeServer with a
callback that determines the correct EventTypeKey for every incoming
subscription, so the application can discern the proper data format for
each. I think sipXsaa is the first non-trivial use of the EventTypeKey
mechanism.
Dale
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
