The OpenNET Project / Index page

[ новости /+++ | форум | теги | ]

Поиск:  Каталог документации

A. LDAP attributes used by NetMeeting

Distinguished Names (DNs) used by NetMeeting must always end in "objectclass=rtperson". The following LDAP attributes are used by NetMeeting:

Table A-1. NetMeeting LDAP attributes

objectClassmust be "RTPerson"
cnalias used for directory lookups; must be present
sappidmust be "ms-netmeeting"
sprotidmust be "h323"
sprotmimetypetypically "text/h323"; unused
smimetypetypically "text/iuls"; unused
sflagsmust be 1
sappguidunknown
smodopunknown
sipaddressdecimal IP address
sportTCP port number; unused
ssecurityunknown
sttlentry timeout value in minutes
ctwo digit country code
rfc822mailboxemail address
givennameoptional
surnameoptional
commentoptional
locationoptional
ilsa393216301 = personal; 2 = business; 4 = adult
ilsa328335660 = not audio capable; 1 = audio capable
ilsa329646380 = not video capable; 1 = video capable
ilsa262144300 = not in a call; 1 = currently in a call
ilsa26279966unknown

NetMeeting uses a non-standard means of refreshing dynamic entries. The Microsoft server maintains an "sttl" attribute, which is a time to live for the entry in minutes. A search request for attribute "sttl" resets the timer. If the timer goes to zero, the entry is supposed to disappear from the database. Of course, the sttl attribute doesn't actually exist in the database, and the client doesn't bother to give us the whole DN it wants updated, only supplying the "cn" component in the search request.




Партнёры:
PostgresPro
Inferno Solutions
Hosting by Hoster.ru
Хостинг:

Закладки на сайте
Проследить за страницей
Created 1996-2024 by Maxim Chirkov
Добавить, Поддержать, Вебмастеру