RFC 3944:H.350 Directory Services
RFC-Ref

call server


Click on the red underlined text to get to the source

... maintain a canonical source of users and their multimedia conferencing systems, so that multiple call servers from multiple vendors, supporting multiple protocols, can all access the same data ...


... The following terms are used throughout the document: * call server: a protocol-specific signalling engine that routes video or voice ...
... entity is a SIP Proxy Server. Note that not all signalling protocols use a call server. * endpoint ...


... voice-specific directories, enterprise directories, call servers and endpoints. ...
... endpoints. The use of a common, authoritative data source for call server, endpoint, user, authentication ...
... IP telephones produced by a second provider, with signalling managed by a call server produced by yet a third provider. Each of these disparate systems can access the same underlying data source, ...
... endpoint. LDAP provides a convenient storage location that can be accessed by both call server and endpoint; thus it is possible to use the directory to support ...
... middleware. Service administrators need call servers that are aware of enterprise directories to avoid duplication of account management ...
... endpoint information to be stored in a canonical data source (the Directory), rather than local to the call server, so that endpoints can be managed through manipulations of an ...
... endpoints can be managed through manipulations of an enterprise directory, rather than by direct entry into the call server; 4) support the creation of very large-scale distributed ...


... Annex D and HTTP Digest, respectively). These approaches require that the call server have access to the password. Thus, if the call server or H.350 ...
... that the call server have access to the password. Thus, if the call server or H.350 directory is compromised, passwords also may become ...
... compromised. These weaknesses may be due to weaknesses in the systems (H.350 directory or call servers) and their operation rather than in H.350 per se. ...
... 5]. It is strongly encouraged that call servers and an H.350 directory mutually authenticate ...
... Further, it is strongly encouraged that communications between H.350 directories and call servers or endpoints happen over secure communication channels ...



Google
Web
RFC-Ref