Manager: Configuration Settings > System > Directory Services
|
|
System | Directory Services | HTTP |
IP Office 5.0+ systems can use HTTP to import the directory records held by another IP Office system.
Imported Records
| • | Imported directory records are temporary until the next import refresh. They are not added to the IP Office system's configuration. |
| • | They cannot be viewed or edited using IP Office Manager or edited by a System Phone user. |
| • | The temporary records are lost if IP Office is restarted. However the IP Office will request a new set of imported directory records after an IP Office restart. |
| • | The temporary records are lost if an IP Office configuration containing Directory changes is merged. The IP Office will then import a new set of temporary records without waiting for the Resync Interval. |
| • | If an configuration record is edited by a System Phone user to match the name or number of a temporary record, the matching temporary record is discarded. |
Importation Rules
When a set of directory records is imported by HTTP or LDAP, the following rules are applied to the new records:
| • | Imported records with a blank name or number are discarded. |
| • | Imported records that match the name or number of any existing record are discarded. |
| • | When the total number of directory records has reached the system limit, any further imported records are discarded. |
IP Office |
Number of Directory Records |
Total Number of Directory Records |
||
IP Office Configuration |
LDAP Import |
HTTP Import |
||
IP500 |
2500 |
5000 |
5000 |
5000 |
IP412 |
2500 |
2500 |
2500 |
2500 |
IP406 V2 |
2500 |
2500 |
2500 |
2500 |
Note that support for HTTP can be disabled. The Avaya HTTP Clients Only setting (System | System) can restrict an IP Office system from responding to HTTP requests. The IP Office system's Unsecured Interface security settings also included controls for HTTP access (HTTP Directory Read and HTTP Directory Write).
System | Directory Services | HTTP |
|
Control Unit |
SOE |
Software Level |
5.0+. |
Mergeable |
|
| • | Directory Type: Default = None (No HTTP import) Set whether HTTP import should be used and the method of importation. |
| • | None Do not use HTTP import. |
| • | IP Office Import from the IP Office at the IP address set in the Source field. |
| • | IP Office SCN Import from an IP Office in a Small Community network. The Source field is used to select the Outgoing Line ID that matches the H323 SCN line to the remote IP Office. |
| • | Source: Default = Blank The form of this field changes according to the Directory Type selection above. |
| • | List: Default = All This field sets what types of directory record should be imported. |
| • | All Import the full set of directory records from the remote IP Office. |
| • | Config Only Import just directory records that are part of the remote IP Office's configuration. Note that these will be treated as imported records and will not be added to the local systems own configuration records. |
| • | LDAP Only Import just directory records that the remote IP Office has obtained as the result of its own LDAP import. This allows LDAP directory records to be relayed from one IP Office to another. |
| • | HTTP Only Import just directory records that the remote IP Office has obtained as the result of its own HTTP import. This allows HTTP directory records to be relayed from one IP Office to another. |
| • | URI: Default = /system/dir/complete_dir_list This field is for information only and cannot be adjusted. The path shown changes to match the List setting above. |
| • | Resync Interval (secs): Default = 3600 seconds. Set how often the IP Office should request an updated import. When a new import is received, all previously imported records are discarded and the newly imported records are processed. |
|
© 2009 AVAYA 15-601011 Issue 23.p.- 07:06, 30 October 2009 (http.htm) Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others. All trademarks identified by (R) or TM are registered trademarks or trademarks respectively of Avaya Inc. All other trademarks are the property of their respective owners. Last Modified: 18/03/2009 |