teminalAlias in RegistrationConfirm?

Frank Derks frank.derks at PHILIPS.COM
Mon Jan 24 10:36:45 EST 2000


Hi Chris,

I was a bit to hasty with sending out this question. Reading on a bit made it a bit clearer how this field should be interpreted.
According to the H.323 text it would "typically" be used when an endpoint does not provide an alias at all. I would say that
your example is probably a bit more realistic. I suppose it could also be used to "create" an (unique)  E-mail ID and
associate with the enpoint to which it is conveyed, so that address can be used in environments where this sort of
address is more appropriate.

Regards,

Frank

-----------------------------------------------------
Frank Derks                    |Tel  +31 35 6893238 |
Advanced Development           |Fax  +31 35 6891030 |
Philips Business Communications|P.O. Box 32         |
                               |1200 JD  Hilversum  |
                               |The Netherlands     |
----------------------------------------------------|
E-mail: mailto:frank.derks at philips.com              |
WWW: http://www.sopho.philips.com                   |
-----------------------------------------------------





cwp at ISDN-COMMS.CO.UK@SMTP at MAILBAG.INTEL.COM on 24/01/2000 16:23:02
Please respond to ITU-SG16 at MAILBAG.INTEL.COM@SMTP
Sent by:        ITU-SG16 at MAILBAG.INTEL.COM
To:     ITU-SG16 at MAILBAG.INTEL.COM@SMTP
cc:
Subject:        Re: teminalAlias in RegistrationConfirm?
Classification: Restricted
Frank,

You should interpret this as meaning exactly what it says.
A gatekeeper may give an endpoint more, fewer, or simply different aliases from
what it requests in RRQ - for whatever reason.  The most common reason is
probably that an endpoint registers with an E.164 address only (say "9007"),
and the gatekeeper might work out from that who is referred to, decide it's me,
and associate with it the publicPartyNumber +44 1344 899 007 and the emailID
cwp at isdn-comms.co.uk
It's only polite for the gatekeeper to TELL the terminal it has done this!
What the terminal will do with the information is a little less certain
(probably a simple endpoint will not care!).

Regards,
Chris

Frank Derks wrote:
>
> The RCF contains an optional field with the name: "terminalAlias". The description of this field for this message states: "This optional value is a list of alias addresses, by which other terminals may identify this terminal". Should I interpret this by
> assuming that the last word of this description ("terminal) should be "Gatekeeper", does this field have another purpose or should I ignore it alltogether?
>
> Frank
>
> -----------------------------------------------------
> Frank Derks                    |Tel  +31 35 6893238 |
> Advanced Development           |Fax  +31 35 6891030 |
> Philips Business Communications|P.O. Box 32         |
>                                |1200 JD  Hilversum  |
>                                |The Netherlands     |
> ----------------------------------------------------|
> E-mail: mailto:frank.derks at philips.com              |
> WWW: http://www.sopho.philips.com                   |
> -----------------------------------------------------

--
Dr Chris Purvis -- Development Manager
ISDN Communications Ltd, The Stable Block, Ronans, Chavey Down Road
Winkfield Row, Berkshire.  RG42 6LY  ENGLAND
Phone: +44 1344 899 007
Fax:   +44 1344 899 001



More information about the sg16-avd mailing list