Reference12r1:Phone/User/Directories

From innovaphone-wiki

Jump to: navigation, search
There are other versions of this article: Reference | Reference9 | Reference10 | Reference12r1 (this version) | Reference13r1

In this menu the directories to be searched for telephone numbers of remote parties can be configured and enabled.

Contents

Local

  • Enable: enable usage of the private local telephone directory

PBX

The innovaphone PBX directory can be used to find the number of a PBX user by name by searching either the Long Name or the Display Name of the PBX user object. The number returned provides all escapes and prefixes required to dial the user, with the number configured at the PBX as the last (or only) part.

  • Enable: enable usage of the the innovaphone PBX directory
  • Use TLS: User secure LDAP connection via TLS
  • Port: Port number assigned to the LDAP service
  • User name: User name for authentication at the PBX directory (Default = ldap-guest).
  • Password/Retype: Password for authentication at PBX directory (Default = ipxxx).
  • Address: the address of the PBX holding the complete user database (a.k.a. LDAP master). By default, this field is left empty and the address of the PBX where the phone is registered to is used. However, if this is a partially replicated PBX, it will not have the complete information.
  • Gatekeeper Identifier: the System Name of the PBX holding the complete user database. By default this field is left empty. However, if the phone is registered to a dynPBX the Gatekeeper Identifier must be specified.
  • Name Attribute: attribute to be searched for a name (Default = Long Name).

External LDAP Server

  • Enable: enable usage of the the external LDAP server
  • Access Parameters
    • Server: IP address of the LDAP server
    • Port: Port number assigned to the LDAP service (Default: 389 for LDAP, 636 for LDAPS)
    • User name: User name for authentication at the LDAP server
    • Password/Retype: Password for authentication at the LDAP server
  • Search Parameters (Contact the administrator of the remote database for information)
    • Search base
    • Mode
    • Object filter
    • Sort results (by 1st LDAP name attribute)
    • Name attributes: Comma separated list of up to 3 names of attributes identifying a person, for example ``sn,givenName,company´´. Search results are sorted in the order given by this list.
    • Number attributes: Comma separated list of up to 10 attribute names for phone numbers. Each entry consists of the attribute name and an optional tag (starting with a colon). The tag is used to identify the type of number on the phone display. ``telephoneNumber:O,homePhone:H,mobile:M,:@´´ specifies that a ``telephoneNumber´´ should be identified by 'O' (like Office), a ``homePhone´´ number by 'H' (like Home), a ``mobile´´ number by 'M' (like Mobile phone) and a directory entry without any number by '@'. The ",:@" part is optional
    NumberAttributes are identified by different icons in the phone search result:
    • Attribut name contains "mobile" - icon "mobile phone" is displayed
    • Attribut name contains "home" or "private" - icon "house" is displayed
    • if none of above characteristics matches to the attribute name, icon "company" is displayed
    • Detail attributes: A list of up to 10 attributes that contain arbitrary additional information, for example ``title,streetAddress,postalCode l,c,mail,url´´. The detail attributes are just displayed and are not used for searching. If two attributes should be displayed in different lines they are separated by a comma. If they shall be displayed in the same line they are separated by a space. myPBX shows an email button on the search result if it finds an email address here.
    • H.323 ID attribute: Name of an attribute containing a H323-ID which can be used to set up a call.
    • Meta Name Attribute: A single attribute. If configured only this attribute containing the search string entered by the user is sent to the LDAP server. The configured name and number attributes are only used for formatting the displayed results. This mode of operation is only supported by some LDAP servers.
    • Meta Number Attribute: A single attribute. If configured only this attribute containing the unmodified phone number is sent to the LDAP server. The configured name and number attributes are only used for formatting the displayed results. This mode of operation is only supported by some LDAP servers.
    • Hold Server Connection: A TCP/LDAP connection is going to be disconnected in the aftermath of a search request+response handshake and after the configured timeout expired.

An external LDAP server can be used to resolve names to numbers for outgoing calls and numbers to names for incoming calls.


Please note:

  • For performance reasons, the external LDAP server is not queried for incoming calls if the call includes a name identification (which is usually the case for PBX-internal calls)
config add PHONE SIG /no-name-id hides the PBX provided name-id and thus a directory search is performed for PBX internal numbers too.
  • The external LDAP server is not queried for incoming calls, if the calling number does not match the External Line according to the configured dialling location.
config add PHONE DIR /dont-skip-ext forces to search the external LDAP server also for numbers not looking like external numbers according to the ``Dialing Location´´ (the directory is searched for any number if enabled)
  • For incoming calls the phone tries to display surname givenname organization
This is done by guessing the meaning of the LDAP attributes you configured as Name attributes. However, this fails if you use rather exotic attributes. In this case, you can specify the order:
config add PHONE APP /name-display-in xxx /name-display-out xxx specifies the name attributes to be displayed in your own order.
To display all name attributes in your configured order use "123"
To display only the third attribute use "3"

Dialing location

The Dialing Location is an optional setting. If a directory maintains telephone numbers in international form with a leading '+' sign, a mechanism must be available to convert or normalize such a number into a dialable number with all the required prefixes.

  • Country Code: The country code (e.g. 49 for Germany).
  • Area Code: The area code (e.g. 30 for Berlin).
  • National Prefix: The national trunk prefix (0 in Germany).
  • International Prefix: The international trunk prefix (00 in Germany).
  • External Line: The prefix, necessary to access a trunk line. This prefix equals 0 in most PBX configurations.
  • Subscriber Numbers: For the conversion of international numbers to internal extensions.
    List all subscriber numbers comma separated which are located within your configured area code.
    If you have additional subscriber numbers with another area code add these as full qualified number like ",+49703173009".
  • Max Internal Number Length: The maximum number of digits used for internal numbers. This can be used by applications like myPBX to detect internal numbers that don't need the external line prefix to be dialled.
Personal tools