innovaphone wiki - User contributions [en]

Howto:Maintaining a Phone Directory in the PBX

2010-03-09T10:35:14Z

Rscholer: /* Node */

==Applies To==
This information applies to

* PBX, all platforms, V7 and later



==More Information==

===Problem Details===
A shared phone directory for all users is a common requirement in PBX systems. Although there are sophisticated solutions based on LDAP services available (e.g. [[Howto:ESTOS_MetaDirectory%2C_iCE_Information | Metadirectory]]), some customers ask for a small and easy solution which is implemented directly in the PBX and does not require any external components. Here is how to do it.
===System Requirements===
The goal is to make the global phone book available in the phone's directory client for outgoing calls and for reverse identifaction of incoming calls. You will need a PBX and you will need to configure the phone's external LDAP client accordingly. The solution will also work with the LDAP [[Reference8:Administration/PBX/Objects/Directory_Search | Directory Search ]] object.

===Configuration===
The idea is to configure directory entries as normal user objects. These will be looked up by the phone's directory client. Unfortunately, all these numbers obviously start with the trunk access prefix (usually <code>0</code>) and would thus conflict with your trunk object. The solution is to create a separate [[Reference8:Administration/PBX/Objects/Node|node]] for phone book entries (say <code>telbook</code> for example). This eliminates the conflict as there will be no trunk object in this node. All phone book entries must be configured with the <code>node</code> property set to <code>telbook</code> then.

==== Node ====
To create the [[Reference8:Administration/PBX/Objects/Node|node]], you need to:
* Add a ''Node'' entry with:
* ''Name'' set to e.g. <code>telbook</code>
* '' Long Name''set to e.g. <code>telbook</code>
* ''Number'' to a available number in the dialing plan. The actual number is not used for the phonebook
* Check the ''Hide from LDAP'' check-mark so the node doesn't appear in LDAP searches.
Rest can be left default.

==== Entries ====
To add an entry, you would create a user [[Reference7:Administration/PBX/Objects|object]] and configure it as follows
* Set ''Long Name'' to some unique id, e.g. <code>telbook-donaldd-mgm</code>
* Set ''Display Name'' to the name you want to appear in the phone display (e.g. <code>Donald Duck, Metro-Goldwyn-Mayer</code>)
* Set ''Number'' to the number to dial (including trunk prefixes, e.g. <code>007031730090</code>)
* Set ''Node'' to the phone book node you created (e.g. <code>telbook</code>)
* Leave ''PBX'' empty
* Make sure the ''Hide from LDAP'' check-mark is ''Unchecked''

==== Telephone LDAP Directory Client ====
On the client side, you need to configure the LDAP directory client in <code>Configuration / Registration x / Directories</code> accordingly. Here it goes:
* You may want to clear the ''enable'' check-mark in the ''PBX'' box if you want the phone to display phone book entries only. However, leaving it checked will nicely show a merged list of PBX extensions and phone book entries
* You need to check the ''enable'' check-mark in the ''External LDAP Server'' box
* Set ''Server'' to the IP address of your PBX
* Set ''Port'' to 389
* Set ''Username'' and ''Password'' to the credentials of an LDAP server account with at least read privileges (usually <code>ldap-guest</code> and <code>ipxxx</code>)
* Set ''Search Base'' to <code>cn=PBX0</code>
* Set ''Mode'' to <code>basic</code>
* Set ''Object Filter'' to <code>(node=telbook)</code>
* Set ''Name Attributes'' to <code>dn</code>
* Set ''Number Attributes'' to <code>e164</code>

==== Administrative Access ====
Maintenance of the phone book now requires admin rights in the PBX. However, this maintenance is usually delegated to personel that should not have modify rights on the system's overall configuration. To work around that problem, you would create a special PBX user (say <code>telbook-admin</code>) with limited access rights. You need to
* Create a new ''User'' object
* Set ''Long Name'' and ''Name'' and to the desired name (e.g. <code>telbook-admin</code>)
* Leave ''Number'' empty
* Set ''Password'' to the desired password
* Set ''Node'' to you standard node, but ''not'' to the node you are using for the phone book (e.g. to <code>root</code>, not <code>telbook</code>)
* Leave ''PBX'' empty

On that user object, you would set special access rights. To do so, you open the ''Rights'' dialogue (by clicking the <code>+</code> sign in the ''Rights'' column) and
* Select ''Administration of all Objects'' from the drop-down list
* Set ''Limit to Node'' to your phone book node (e.g. <code>telbook</code>)
* Leave ''Limit to PBX'' empty

The person in charge of the directory administration can now log in to the PBX using this restricted account and safely edit all entries with no risk of doing harm to the rest of the configuration.



[[Category:Howto|{{PAGENAME}}]]

Howto:Maintaining a Phone Directory in the PBX

2010-03-09T10:34:19Z

Rscholer:

==Applies To==
This information applies to

* PBX, all platforms, V7 and later



==More Information==

===Problem Details===
A shared phone directory for all users is a common requirement in PBX systems. Although there are sophisticated solutions based on LDAP services available (e.g. [[Howto:ESTOS_MetaDirectory%2C_iCE_Information | Metadirectory]]), some customers ask for a small and easy solution which is implemented directly in the PBX and does not require any external components. Here is how to do it.
===System Requirements===
The goal is to make the global phone book available in the phone's directory client for outgoing calls and for reverse identifaction of incoming calls. You will need a PBX and you will need to configure the phone's external LDAP client accordingly. The solution will also work with the LDAP [[Reference8:Administration/PBX/Objects/Directory_Search | Directory Search ]] object.

===Configuration===
The idea is to configure directory entries as normal user objects. These will be looked up by the phone's directory client. Unfortunately, all these numbers obviously start with the trunk access prefix (usually <code>0</code>) and would thus conflict with your trunk object. The solution is to create a separate [[Reference8:Administration/PBX/Objects/Node|node]] for phone book entries (say <code>telbook</code> for example). This eliminates the conflict as there will be no trunk object in this node. All phone book entries must be configured with the <code>node</code> property set to <code>telbook</code> then.

==== Node ====
To create the [[Reference8:Administration/PBX/Objects/Node|node]], you need to:
* Add a ''Node'' entry with:
* ''Name'' set to e.g. <code>telbook</code>
* '' Long Name''set to e.g. <code>telbook</code>
* ''Number'' to a available number in the dialing plan.
* Check the ''Hide from LDAP'' check-mark so the node doesn't appear in LDAP searches.
Rest can be left default.

==== Entries ====
To add an entry, you would create a user [[Reference7:Administration/PBX/Objects|object]] and configure it as follows
* Set ''Long Name'' to some unique id, e.g. <code>telbook-donaldd-mgm</code>
* Set ''Display Name'' to the name you want to appear in the phone display (e.g. <code>Donald Duck, Metro-Goldwyn-Mayer</code>)
* Set ''Number'' to the number to dial (including trunk prefixes, e.g. <code>007031730090</code>)
* Set ''Node'' to the phone book node you created (e.g. <code>telbook</code>)
* Leave ''PBX'' empty
* Make sure the ''Hide from LDAP'' check-mark is ''Unchecked''

==== Telephone LDAP Directory Client ====
On the client side, you need to configure the LDAP directory client in <code>Configuration / Registration x / Directories</code> accordingly. Here it goes:
* You may want to clear the ''enable'' check-mark in the ''PBX'' box if you want the phone to display phone book entries only. However, leaving it checked will nicely show a merged list of PBX extensions and phone book entries
* You need to check the ''enable'' check-mark in the ''External LDAP Server'' box
* Set ''Server'' to the IP address of your PBX
* Set ''Port'' to 389
* Set ''Username'' and ''Password'' to the credentials of an LDAP server account with at least read privileges (usually <code>ldap-guest</code> and <code>ipxxx</code>)
* Set ''Search Base'' to <code>cn=PBX0</code>
* Set ''Mode'' to <code>basic</code>
* Set ''Object Filter'' to <code>(node=telbook)</code>
* Set ''Name Attributes'' to <code>dn</code>
* Set ''Number Attributes'' to <code>e164</code>

==== Administrative Access ====
Maintenance of the phone book now requires admin rights in the PBX. However, this maintenance is usually delegated to personel that should not have modify rights on the system's overall configuration. To work around that problem, you would create a special PBX user (say <code>telbook-admin</code>) with limited access rights. You need to
* Create a new ''User'' object
* Set ''Long Name'' and ''Name'' and to the desired name (e.g. <code>telbook-admin</code>)
* Leave ''Number'' empty
* Set ''Password'' to the desired password
* Set ''Node'' to you standard node, but ''not'' to the node you are using for the phone book (e.g. to <code>root</code>, not <code>telbook</code>)
* Leave ''PBX'' empty

On that user object, you would set special access rights. To do so, you open the ''Rights'' dialogue (by clicking the <code>+</code> sign in the ''Rights'' column) and
* Select ''Administration of all Objects'' from the drop-down list
* Set ''Limit to Node'' to your phone book node (e.g. <code>telbook</code>)
* Leave ''Limit to PBX'' empty

The person in charge of the directory administration can now log in to the PBX using this restricted account and safely edit all entries with no risk of doing harm to the rest of the configuration.



[[Category:Howto|{{PAGENAME}}]]

Howto:We are currently using Innovaphone IP6000 Gateway and couple days ago we upgraded to v6. Problem is that if I have set a diversion to my mobile it doesnt show the caller ID, just the number that call was diverted from.

2008-07-30T11:20:03Z

Rscholer:

'''FAQ:'''

We are currently using Innovaphone IP6000 Gateway and other innovaphone products (IP 230, IP 110, IP 50 DECT etc.) and couple days ago we upgraded our version v5 to v6. Problem is that if I have set a diversion to my mobile it doesnt show the caller ID, just the number that call was diverted from.

'''Answer:'''

Please have a look at http://wiki.innovaphone.com/index.php?search=partial+rerouting&go=Go and http://wiki.innovaphone.com/index.php?title=Howto:How_does_%22CLIP_no_screening%22_work%3F

[[Category:Faq|{{PAGENAME}}]]

Howto:How ISDN wiring works

2008-06-19T08:59:30Z

Rscholer: /* Details */

ISDN Primary rate (PRI) wiring differs from Ethernet and from ISDN Basic rate (BRI) wiring. Here is how to do primary rate and basic rate wiring correctly.

==Applies To==
This information applies to

*IP3000
*IP3000DD
*IP6000
*IP400
*IP800
*IP202
*IP302
*IP305

==More Information==
===Details===
With a newer ISDN PRI network termination, the IP3000 can be connected using a straight, 8-wire category 5 cable. A 4 wire cable, either LAN or telephony cable, will often not work. Also, some network terminations do not feature an RJ45 connector, so an individual cable must be created.

On the IP3000 box bottom, there is a wiring diagram. If you are unclear about the pinout, the following pinout picture will probably help:

[[Image:How_ISDN_wiring_works_-_RJ45.gif]]

PRI uses pairs 1 and 2 according to the following picture (pair 1: 4+5, pair 2: 1+2), as opposed to BRI, which uses pairs 1 and 3.

[[Image:How_ISDN_wiring_works_-_Rj45-pairs.gif]]

To check the cable you are going to use, simply plug it into PRI1 and PRI2 of the same IP3000. Both PRI1/2 leds must light, otherwise the cable is broken or unsuited. This even works if the 2 PRIs are not licensed.



[[Category:Howto|{{PAGENAME}}]]