Hi Wolfgang, H.450.x use H.225.0 call control messages for transport and the usual aliasAddress types in address fields. So there is no restriction imposed by H.450.x - what is possible for H.323 basic calls is also possible for H.450 supplementary services. Ernst Horvath Siemens AG

-----Ursprüngliche Nachricht----- Von: Wolfgang Bandow [mailto:wolfgang.bandow@DETEWE.DE] Gesendet am: Mittwoch, 12. April 2000 13:41 An: ITU-SG16@mailbag.cps.intel.com Betreff: H.450.x

Hello H.450-Experts,

H.450.1 says "The generic functional protocol defined in this Recommendation provides the means to exchange signalling information for the control of supplementary services over a LAN" (cf. chapter 5).

Is my assumption right, that the terminals and Gatekeepers being part of a H.450-connection do not necessarily have to be connected to the same LAN, but may be connected via several routers?

Whould the following configuration be possible?

terminal 1 gatekeeper 1 terminal 2 gatekeeper 2 terminal 3 | | | | | ----------------------------------LAN 1 LAN 2 -----------------------------------------

| | router 1 router 2 |------------- ip link ------------|

E.G. terminal 3 calls terminal 1 which has activated a call diversion to terminal 2. The gatekeeper routed call model is used.

Is this allowed? What will happen?

Thanks a lot in advance for your reply.

Regards, Wolfgang Bandow CT-B, Berlin