> -----Original Message-----
> From: Worley, Dale (BL60:9D30)
> Sent: Thursday, July 09, 2009 3:33 PM
> To: Beeton, Carolyn (CAR:9D60)
> Cc: [email protected]
> Subject: Re: [sipX-dev] Patches for sipXsaa
>
> Can you give a short explanation (or pointer thereto) as to
> how you deal with "dialog;sla" events? My memory is that you
> want a SubscribeServer to provide different content for
> subscribers to "dialog;sla" than to subscribers to "dialog",
> but that the SubscribeServer machinery currently strips off
> all parameters of the event type, in order to make sure that
> the 'id' parameter and unknown parameters do not cause
> failure to find the content in the internal database.
>
> Dale
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.
Carolyn
_______________________________________________
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/
