One step at a time...

[Paul E. Jones]

Wolfgang,

The Remote Activation procedures (activateDiversionQ.inv) were intended to
be used for remote activation.
For local activation of diversion at the endpoint, activation is of local
significance only and is thus out of the scope of the recommendation.
However, the Remote Activation procedures may be used for activation of
diversion from a activating/served endpoint at its lokal GK. This has been
introduced in the late phase of H.450.3 standardization within clause 9.2.2.
>From the signalling point of view it is a regular H.450 non call related
SETUP including the activateDiversionQ.inv that is sent from the
activating/served EP to the GK.

Regards,
Karl Klaghofer

> -----Ursprüngliche Nachricht-----
> Von:  Wolfgang Bandow [SMTP:wolfgang.bandow at DETEWE.DE]
> Gesendet am:  Monday, June 05, 2000 15:24
> An:   ITU-SG16 at mailbag.cps.intel.com
> Betreff:      H.450-3
>
> Hello H.450-Experts!
>
> I've got a question concerning the activation of call forwarding in
> cases when the served endpoint
> shall be represented by a gatekeeper.
>
> The standard distinguishes between the activating and the served
> endpoint but does not give sufficient
> information for the case that activating and served endpoint are both
> the same.
> Is there any message flow when activating call forwarding by the served
> user (locally)?
> Is the corresponding gatekeeper somehow informed about this activation?
>
> Thanks a lot for your reply.
>
> Regards,
> Wolfgang Bandow   CT-B / Berlin
>  << Datei: Visitenkarte f|r Wolfgang Bandow >>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv at mailbag.intel.com