Reference9:Phone/User/Directories: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
m (New page: In this menu, there are three options for how the telephone can access telephone directories. '''local enable''' * A private telephone directory can be created on the device itself and us...)
 
No edit summary
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
In this menu, there are three options for how the telephone can access telephone directories.
In this menu the directories to be searched for telephone numbers of remote parties can be configured and enabled.


'''local enable'''
'''Local'''
* A private telephone directory can be created on the device itself and used.
* Enable: enable usage of the private local telephone directory


'''PBX enable'''
'''PBX'''
* Furthermore, all subscribers of the innovaphone PBX can be made available as a telephone directory entry.
** User name: User name required for registration that is stored on the innovaphone PBX. (Default = ldap-guest)
** Password: Password for the user name, which you confirm in the Retype box. (Default = ipxxx)


An external database is usable as a telephone directory via the LDAP protocol.
The innovaphone PBX directory can be used to find the number of a PBX user by name (Long 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  
* User name: User name for authentication at the PBX directory (Default = ldap-guest)
* Password/Retype: Password for authentication at PBX directory (Default = ipxxx)


'''External LDAP server'''
'''External LDAP Server'''
* Here, you enter the LDAP access parameters for the external telephone directory.
* Enable: enable usage of the the external LDAP server
** Server: IP address of the LDAP server.
* Access Parameters
** Port: Port number assigned to the LDAP service.
** Server: IP address of the LDAP server  
** User name: User name for authentication at the LDAP server.
** Port: Port number assigned to the LDAP service  
** Password: Password that goes with the user name.
** User name: User name for authentication at the LDAP server
** Retype: Confirmation of the password.
** Password/Retype: Password for authentication at the LDAP server


The following parameters are necessary for searching within the external database. Contact the administrator of the remote database for information.
* 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.
** H.323 ID attribute: Name of an attribute containing a H323-ID which can be used to set up a call.  


* Search base
With some very specific numbering schemes the PBX provided name-id (Long Name of a PBX user object) is not appropriate to be displayed on the phone. Thus it should be possible to use an external LDAP server also for the name resolution of internal numbers. Further it should be possible to define the name display format for inbound and outbound calls separately.  
* 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.
* H.323 ID attribute: Name of an attribute containing a H323-ID which can be used to set up a call.  


with some very specific numbering schemes the PBX provided name-id (Long Name of a PBX user object) is not appropriate to be displayed on the phone. Thus it should be possible to use an external LDAP server also for the name resolution of internal numbers. Further it should be possible to define the name display format for inbound and outbound calls separately.  
Solution:
 
"config add PHONE SIG /no-name-id" hides the PBX provided name-id and thus a directory search is performed for PBX internal numbers to resolve the name.
 
"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 local directory is searched for any number if enabled.


solution:
"config add PHONE SIG /no-name-id" hides the PBX provided name-id and thus name resolution for internal numbers is performed via the external LDAP server.
"config add PHONE APP /name-display-in <format-in> /name-display-out <format-out>" specifies the name attributes to be displayed and their order. The default format is "123", i.e. all name attributes are displayed in their configured order, "3" would display only the third attribute.
"config add PHONE APP /name-display-in <format-in> /name-display-out <format-out>" specifies the name attributes to be displayed and their order. The default format is "123", i.e. all name attributes are displayed in their configured order, "3" would display only the third attribute.


'''Dialling location'''
'''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 diallable number with all the required prefixes.
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).
* '''Country Code''': The country code (e.g. ''49'' for Germany).
* '''Area Code''': The area code (e.g. ''30'' for Berlin).
* '''Area Code''': The area code (e.g. ''30'' for Berlin).

Latest revision as of 10:54, 2 April 2012

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

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 (Long 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
  • User name: User name for authentication at the PBX directory (Default = ldap-guest)
  • Password/Retype: Password for authentication at PBX directory (Default = ipxxx)

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
    • 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.
    • H.323 ID attribute: Name of an attribute containing a H323-ID which can be used to set up a call.

With some very specific numbering schemes the PBX provided name-id (Long Name of a PBX user object) is not appropriate to be displayed on the phone. Thus it should be possible to use an external LDAP server also for the name resolution of internal numbers. Further it should be possible to define the name display format for inbound and outbound calls separately.

Solution:

"config add PHONE SIG /no-name-id" hides the PBX provided name-id and thus a directory search is performed for PBX internal numbers to resolve the name.

"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 local directory is searched for any number if enabled.

"config add PHONE APP /name-display-in <format-in> /name-display-out <format-out>" specifies the name attributes to be displayed and their order. The default format is "123", i.e. all name attributes are displayed in their configured order, "3" would display only the third attribute.

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, the relevant subscriber numbers (comma-separated) may be configured here (E.g +49703173009).