https://wiki.innovaphone.com/api.php?action=feedcontributions&user=Tsr&feedformat=atominnovaphone wiki - User contributions [en]2024-03-28T10:17:05ZUser contributionsMediaWiki 1.39.1https://wiki.innovaphone.com/index.php?title=Howto:Innovaphone_gateways_and_DSS1_advice_of_charge_IEs&diff=21254Howto:Innovaphone gateways and DSS1 advice of charge IEs2011-06-07T15:22:06Z<p>Tsr: </p>
<hr />
<div>Handling of DSS1 AOC (advice of charge) in innovaphone Gateways depends on call routing<br />
<br />
<!-- keywords impulse takt taktung clock clocking impuls--><br />
<br />
<br />
==Applies To==<br />
This information applies to<br />
<br />
* All innovaphone gateways and PBX platforms<br />
<br />
All builds since version 5.<br />
<br />
==More Information==<br />
===Problem Details===<br />
DSS1 (Euro-ISDN, E-DSS1) advice of charge information elements (AOC-x) are transparently passed through innovaphone gateways when a call is routed through the gateway routing component (aka “Relay”). However, when a call is routed through the PBX, AOC information gets lost.<br />
<br />
When for example an innovaphone gateways is tied in to the trunk line of a legacy PBX, AOC is passed from the carrier’s trunk line to the PBX. However, when the call is routed through the PBX, then AOC information will be stripped. Note that this limitation is in the PBX, not the IP / H.323 protocol. That is, if a call is passed from one gateway to the other via IP, AOC is retained.<br />
<br />
===Resolution===<br />
If AOC is critical, do not route calls through the innovaphone PBX.<br />
<br />
<br />
<!--*[[Main_Page|wiki-innovaphone]]--><br />
<br />
[[Category:Problem|{{PAGENAME}}]]<br />
<br />
<!-- keywords<br />
in-path inpath Einschleifen loop in isdn BRI PRI old PBX Gebührenimpuls impuls cdr taktung --></div>Tsrhttps://wiki.innovaphone.com/index.php?title=Howto:Moh_and_waiting_queue_files_for_testing&diff=21123Howto:Moh and waiting queue files for testing2011-05-12T14:08:14Z<p>Tsr: </p>
<hr />
<div>==Applies To==<br />
This information applies to<br />
<br />
* innovaphone pbx<br />
<br />
<!-- Keywords: enter keywords, foreign translations and/or synoyms not appearing in the article here for better search results --><br />
<br />
==More Information==<br />
When you are testing Music on Hold (MOH) and/or waiting queue announcements and you are not sure if your files are o.k or you have no files for testing.<br />
<br />
Here are some example files for testing [[media:Ten-test-announcements_1.zip|ten-test-announcements.zip ]], they are in wav and also coded in g.711 and g.729.<br />
<br />
== Related Articles ==<br />
<br />
[[Howto:Installing the voicemail/music on hold on a compact flash card]]<br />
<br />
[[Reference:Administration/PBX/Objects/Waiting Queue]]<br />
<br />
<br />
[[Category:Howto|{{PAGENAME}}]]</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Howto:Moh_and_waiting_queue_files_for_testing&diff=21122Howto:Moh and waiting queue files for testing2011-05-12T14:07:25Z<p>Tsr: </p>
<hr />
<div>==Applies To==<br />
This information applies to<br />
<br />
* innovaphone pbx<br />
<br />
<!-- Keywords: enter keywords, foreign translations and/or synoyms not appearing in the article here for better search results --><br />
<br />
==More Information==<br />
When you are testing Music on Hold (MOH) and/or waiting queue announcements and you are not sure if your files are o.k or you have no files for testing.<br />
<br />
Here are some example files for testing [[media:Moh_and_waiting_queue_files_for_testing_Ten-test-announcements_1.zip|ten-test-announcements.zip ]], they are in wav and also coded in g.711 and g.729.<br />
<br />
== Related Articles ==<br />
<br />
[[Howto:Installing the voicemail/music on hold on a compact flash card]]<br />
<br />
[[Reference:Administration/PBX/Objects/Waiting Queue]]<br />
<br />
<br />
[[Category:Howto|{{PAGENAME}}]]</div>Tsrhttps://wiki.innovaphone.com/index.php?title=File:Ten-test-announcements_1.zip&diff=21121File:Ten-test-announcements 1.zip2011-05-12T14:06:51Z<p>Tsr: </p>
<hr />
<div></div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:Concept_myPBX&diff=21120Reference9:Concept myPBX2011-05-12T08:45:21Z<p>Tsr: /* Windows launcher */</p>
<hr />
<div>= Overview =<br />
myPBX is a web application that comes with the innovaphone PBX starting from V9. It is intended for assisting typical phone users with a number of common tasks like managing calls and contacts, setting their presence or instant messaging.<br />
<br />
== Requirements ==<br />
A current web browser is needed. We support current versions of Firefox, Internet Explorer (from Version 8), Safari, Chrome and Opera. JavaScript must be enabled.<br />
<br />
== Web application ==<br />
myPBX consists of two parts. On the one hand there is the user interface. It is an AJAX application that runs in a web browser. On the other hand the PBX holds a session object for each running user interface. This is where the actual logic is implemented. Both parts talk to each other using HTTP requests.<br />
<br />
The picture shows how call control is done. The myPBX session has access to the phone registration as they are both located in the same PBX. Thus it can monitor and create or modify calls.<br />
<br />
[[Image:Mypbx_overview.png]]<br />
<br />
== Windows launcher ==<br />
The launcher is a tool for integrating myPBX into the Windows desktop. It is not needed in order to use myPBX but it adds some convenient functions that are not available otherwise.<br />
<br />
At startup it opens myPBX in a window that can be minimized to the system tray. The system tray icon also shows notifications on events like alerting calls or incoming chat messages. Additionally you can define a hotkey for dialling numbers out of any Windows application.<br />
<br />
[[Image:Mypbx_launcher.png]]<br />
<br />
* Note: When you run the windows launcher, it opens only with the Microsoft IE browser. Also when you have set another browser as standard browser. myPBX supports the Internet Explorer from Version 8<br />
<br />
= Details =<br />
== Profiles ==<br />
The user can create multiple profiles, each with a differnt contact list. This is useful for using myPBX on more than one device. For example people might want to have different contact lists on their computer in the office and on their smart phone. The selected profile is stored together with the login so it is remembered until the next logout.<br />
<br />
== Contacts ==<br />
The contact list works similar to a buddy list. You can add people in order to monitor their presence and calls. You can also call them, start a chat session or send them an email from the contact list.<br />
<br />
There are three types of contacts: Internal, external phone number and external SIP.<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
|-<br />
! <br />
! Internal<br />
! External phone number<br />
! External SIP<br />
|-<br />
! Start call using<br />
| Name or number<br />
| Number<br />
| Email<br />
|-<br />
! Start chat using<br />
| Name or number<br />
| Email<br />
| Email<br />
|-<br />
! Send email using<br />
| Name<br />
| Email<br />
| Email<br />
|-<br />
! Monitor presence and calls using<br />
| Name or number<br />
| Email<br />
| Email<br />
|}<br />
<br />
For external contacts we assume that the Email-Address is the same as the SIP-Address (e.g. user@example.com). If the "use as domain" checkmark is set in the PBX we assume for internal contacts that the username matches the email name and the system name of the PBX matches the email domain.<br />
<br />
== Presence ==<br />
In myPBX the presence of users consists of the following items:<br />
* Activity (e.g. lunch, vacation, ...)<br />
* Note (a free text)<br />
* Phone status (open when the user has at least one registered phone)<br />
* IM status (open when the user is logged-in using myPBX or another instant messaging client)<br />
<br />
The phone an IM status can have three states: open (green icon), closed (no icon) and unknown (grey icon).<br />
<br />
The presence can be monitored by other users if they are allowed to do so (see [[#Visibility]]).<br />
<br />
== Visibility ==<br />
Other people can add you to their contact list but they can't see your presence or call information if you don't give them a permission. In myPBX the set of monitoring rights that you gave to other people is called visibility.<br />
<br />
There are three types of rights: Presence, Busy state and Calls.<br />
<br />
Rights can be given to:<br />
* Users (by name, <code>alice</code> or <code>alice@example.com</code>)<br />
* All users of a domain (by domain suffix, <code>@example.com</code>)<br />
* All active users of a group (by group name)<br />
<br />
If someone tries to monitor you who has no allow or unallow defined you are notified, so you can define rights for that user.<br />
<br />
== Call control ==<br />
[[Image:MyPBX_call_control.png|frame|'''Call control'''<br>Call actions: disconnect, hold/retrieve, 3PTY conference, transfer, park to own number, DTMF keypad]]<br />
[[Image:MyPBX_call_control_number.png|frame|'''Call control with entered number'''<br>Call actions: disconnect, hold/retrieve, 3PTY conference, transfer to number or name, park to number or name, DTMF keypad]]<br />
<br />
myPBX displays the calls on all phones of the user. For initiating and accepting calls the selected device is used. As a consequence the user object should have one device for each phone registration. For dialling or transfer the user can either type a number or take if from LDAP search, the call list or from the contacts.<br />
<br />
Mobile phones can be integrated using the mobility object. When initiating calls the PBX calls the mobile phone and then transfers it to the dialled number. It is mandatory that the mobility has a device name in the fork configuration at the user object. CLIP no screening must be configured so that the mobile phone can display the dialled number correctly.<br />
<br />
The user can do the following actions on calls:<br />
* Initiate new calls by number or name<br />
* Accept incoming calls that are alerting<br />
* Disconnect calls<br />
* Hold calls<br />
* Retrieve calls that are on hold<br />
* Start a three party conference<br />
* End a three party conference<br />
* Transfer one call with another call<br />
* Transfer a call to a specified number or name<br />
* Park a call to line that is specified by number or name<br />
* Park a call to the user's own number<br />
* Unpark calls that have been parked to the user's own number<br />
* Open a keypad for creating DTMF tones (if this is supported by the phone)<br />
<br />
The user can connect calls or switch between calls by clicking the name or number of a call.<br />
<br />
== Directory search ==<br />
Users can search for phone numbers in an internal and an external LDAP directory. myPBX uses the same search filter format and returns equivalent search results as the phones. Therefore the directories must be configured in the phone config that is stored in the user object in the PBX. Templates can be used to share the same configuration across multiple users.<br />
<br />
== Call list ==<br />
myPBX can be configured to obtain the user's call list from an instance of the [[Reference9:Concept_Reporting|innovaphone Reporting]] service. The call list contains all calls of the user, including the call flow before and after the user was connected. When a user calls someone back from the call list, the call is marked as answered in the reporting database. As this is done by the conference ID of the call even other users that have the same call in their list can see who has called back at what time. <br />
<br />
myPBX notifies the user if there were missed calls since the last time the call list was viewed. On startup it asks the reporting service if there were missed calls in the time that myPBX was not running.<br />
<br />
Only users who have the "reporting" flag checked have the call list in myPBX.<br />
<br />
== Instant messaging ==<br />
Instant messaging is session based in myPBX and works similar to phone calls. If the user starts a chat session, the other party can either accept or reject it. When the chat session is established, messages can be exchanged in both direction until one of the parties closes the session by closing the chat window. The PBX does not store chat messages, so both users have to be online at the same time.<br />
<br />
Each party can add additional users to a chat session. This is called a chat conference. In this case myPBX forwards the messages it receives from one user to all other users it is connected to.<br />
<br />
== Audio conferences ==<br />
The innovaphone conference interface can be integrated into myPBX. This feature is enabled if the administrator has configured the number that shall be dialled to create a new audio conference room.<br />
<br />
If activated users can start an unplanned audio conference from a chat session by clicking a button in the chat window. myPBX initiates a phone call to the conference interface using the configured number. The conference interface creates a conference room and connects the call. The connected number is the same that other users have to dial to join the audio conference. This number is sent to all users in the chat using a tel link.<br />
<br />
In order to ensure that there are enough slots in the audio conference myPBX reserves one more slot as there are participants in the chat. The user can also specify the desired number of slots, if needed.<br />
<br />
== Application sharing ==<br />
Similar to audio conferences the user can start a meeting in an external application sharing solution from a chat session. myPBX connects to the application sharing service using a HTTP interface and creates the meeting. If that was successful it sends links for joining the meeting to the participants of the chat session.<br />
<br />
Currently we support Microsoft Office LiveMeeting and WebEx.<br />
<br />
== User password ==<br />
The user can change the password of the user object in myPBX. The changes applies for the next login. The user is not logged out by changing the password.<br />
<br />
Please note that changing the user password affects phone registrations using the user password. In v9 it is recommended to register the dedicated phones of users with the admin password. Only temporary logins at shared phones should be done with the user password.<br />
<br />
== Email integration ==<br />
Depending on configuration emails can be sent to contacts from the contact list. For external contacts the email function is available as long as an email address is configured. For internal contacts the email function is activated when the "use as domain" checkmark in the PBX configuration is checked. In this case it is assumed that the name of the user object (H.323 id) matches the email name and the PBX system name matches the email domain.<br />
<br />
== Login in a multi PBX scenario ==<br />
In a multi PBX scenario myPBX must be connected to the same PBX as the phones. Therefore after login the user is redirected like follows:<br />
<br />
* PBXes accept the login if they are in charge.<br />
* Slaves redirect to the master if they are not in charge.<br />
* The master redirects to the slave that is in charge.<br />
* Inactive standby PBXes redirect to the master.<br />
* Active standby PBXes accept the login.<br />
<br />
Additionally you can configure an alternative URL in the myPBX launcher that shall be used when myPBX can't connect to the primary URL.<br />
<br />
= Configuration hints =<br />
* myPBX has to be enabled in the configuration of the PBX. It is disabled by default.<br />
* Only users with a password can login to myPBX.<br />
* There should be a dedicated device configured at the user object for each phone registration.<br />
* To use mobile phones, the mobility device must have a name in the fork config at the user object.<br />
* The LDAP configuration is taken from the phone config at the user object.<br />
* Phones should be registered using the admin password so that user can change their login password without affecting the phone registrations.<br />
* If federation is used ("use as domain" checked), the user names and the PBX system name should match the email addresses of people.<br />
<br />
= Licensing =<br />
* myPBX does not need a special license. It is covered by the PBX license.<br />
* The innovaphone reporting that can be used for call lists needs separate licenses.<br />
* For integrating mobile phones mobility licenses are needed.<br />
<br />
See [[Reference9:Licenses]] for details.<br />
<br />
= Included open source software =<br />
The myPBX web application contains the following open source software:<br />
* '''rc4.js'''<br />
* RC4 symmetric cipher encryption/decryption<br />
* Copyright (c) 2006 by Ali Farhadi.<br />
* released under the terms of the Gnu Public License.<br />
* see the GPL for details.<br />
*<br />
* Email: ali[at]farhadi[dot]ir<br />
* Website: http://farhadi.ir/<br />
<br />
* '''sha1.js'''<br />
* Secure Hash Algorithm (SHA1)<br />
* http://www.webtoolkit.info/<br />
<br />
[[Category:Concept9|{{PAGENAME}}]]</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference:Administration/PBX/Objects/Edit_Rights&diff=21113Reference:Administration/PBX/Objects/Edit Rights2011-05-11T08:55:35Z<p>Tsr: </p>
<hr />
<div>With this page PBX administration rights can be configured for a user. The user may login to the system using the 'Name' and the 'Password' configured in the User object as authentication.<br />
<br />
== Levels ==<br />
<br />
See note on [[Reference8:Configuration/General/HTTP-Server | ''Password protect all HTTP pages'' ]] for limitations when this flag is used. <br />
<br />
=== Full PBX Administration ===<br />
<br />
All settings of the PBX and PBX objects may be changed the same way as a system administrator can do. Including the rights for users.<br />
<br />
=== Administration of all Objects ===<br />
<br />
All settings of all PBX objects may be changed. The 'General', 'Password' and 'Filter' settings may not be changed.<br />
<br />
=== Administration of non critical Objects ===<br />
<br />
Objects which are marked as 'critical' and the 'critical' flag itself may not be changed.<br />
<br />
=== Groups/Call Forwards only ===<br />
<br />
Only group memberships and call forward settings of non-critical objects may be changed.<br />
<br />
== Limit to Node ==<br />
<br />
Except for the 'Full PBX Administration' right the rights to change any objects can also be limited to a single node.</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference:Administration/PBX/Objects/Edit_Rights&diff=21112Reference:Administration/PBX/Objects/Edit Rights2011-05-11T08:52:51Z<p>Tsr: </p>
<hr />
<div>With this page PBX administration rights can be configured for a user. The user may login to the system using the 'Name' and the 'Password' configured in the User object as authentication.<br />
<br />
== Levels ==<br />
<br />
See note on [[Reference9:Services/HTTP/Server | ''Password protect all HTTP pages'' ]] for limitations when this flag is used. <br />
<br />
=== Full PBX Administration ===<br />
<br />
All settings of the PBX and PBX objects may be changed the same way as a system administrator can do. Including the rights for users.<br />
<br />
=== Administration of all Objects ===<br />
<br />
All settings of all PBX objects may be changed. The 'General', 'Password' and 'Filter' settings may not be changed.<br />
<br />
=== Administration of non critical Objects ===<br />
<br />
Objects which are marked as 'critical' and the 'critical' flag itself may not be changed.<br />
<br />
=== Groups/Call Forwards only ===<br />
<br />
Only group memberships and call forward settings of non-critical objects may be changed.<br />
<br />
== Limit to Node ==<br />
<br />
Except for the 'Full PBX Administration' right the rights to change any objects can also be limited to a single node.</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference:Administration/PBX/Objects/Edit_Rights&diff=21104Reference:Administration/PBX/Objects/Edit Rights2011-05-10T16:01:26Z<p>Tsr: </p>
<hr />
<div>With this page PBX administration rights can be configured for a user. The user may login to the system using the 'Name' and the 'Password' configured in the User object as authentication.<br />
<br />
== Levels ==<br />
<br />
=== Full PBX Administration ===<br />
<br />
All settings of the PBX and PBX objects may be changed the same way as a system administrator can do. Including the rights for users.<br />
<br />
=== Administration of all Objects ===<br />
<br />
All settings of all PBX objects may be changed. The 'General', 'Password' and 'Filter' settings may not be changed.<br />
<br />
=== Administration of non critical Objects ===<br />
<br />
Objects which are marked as 'critical' and the 'critical' flag itself may not be changed.<br />
<br />
=== Groups/Call Forwards only ===<br />
<br />
Only group memberships and call forward settings of non-critical objects may be changed.<br />
<br />
== Limit to Node ==<br />
<br />
Except for the 'Full PBX Administration' right the rights to change any objects can also be limited to a single node.<br />
<br />
* Note: If [[Reference9:Services/HTTP/Server | Password protect all HTTP pages]] is enabled, the administration rights won´t work. Only the ''Full PBX administration'' rights level will work.</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:PBX/Objects/Edit_Rights&diff=21103Reference9:PBX/Objects/Edit Rights2011-05-10T15:59:51Z<p>Tsr: </p>
<hr />
<div>With this page PBX administration rights can be configured for a user. The user may login to the system using the 'Name' and the 'Password' configured in the User object as authentication.<br />
<br />
== Levels ==<br />
<br />
=== Full PBX Administration ===<br />
<br />
All settings of the PBX and PBX objects may be changed the same way as a system administrator can do. Including the rights for users.<br />
<br />
=== Administration of all Objects ===<br />
<br />
All settings of all PBX objects may be changed. The 'General', 'Password' and 'Filter' settings may not be changed.<br />
<br />
=== Administration of non critical Objects ===<br />
<br />
Objects which are marked as 'critical' and the 'critical' flag itself may not be changed.<br />
<br />
=== Groups/Call Forwards only ===<br />
<br />
Only group memberships and call forward settings of non-critical objects may be changed.<br />
<br />
== Limit to Node ==<br />
<br />
Except for the 'Full PBX Administration' right the rights to change any objects can also be limited to a single node.<br />
<br />
<br />
* Note: If [[Reference9:Services/HTTP/Server | Password protect all HTTP pages]] is enabled, the administration rights won´t work. Only the ''Full PBX administration'' rights level will work.</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Howto:How_to_configure_the_Phones_LDAP_client&diff=21062Howto:How to configure the Phones LDAP client2011-05-04T07:23:20Z<p>Tsr: /* innovaphone PBX */</p>
<hr />
<div>The IP200 (also the IP110 ,IP202 and IP230) features a powerful telephone number directory. <br />
<br />
It will perform number-to-name resolution for incoming calls and name-to-number resolution for outgoing calls (using the IP200 built-in alphanumeric keyboard). <br />
<br />
The directory can access up to 3 sources for lookup: the internal (flash-based) list, the PBX user list and an external LDAP server.<br />
<br />
This article describes how to configure the IP200’s LDAP interface for various application scenarios. <br />
<br />
It is meant as a complement to the existing standard product documentation, so please refer to this for general configuration issues.<br />
<br />
<br />
==Applies To==<br />
This information applies to<br />
<br />
* IP110<br />
* IP200<br />
* IP202<br />
* IP230<br />
* IP240<br />
* IP240-1000<br />
* IP72<br />
<br />
==More Information==<br />
<br />
===Quick start===<br />
<br />
This topic is for people with good understanding of LDAP and with little time for reading, who simply want to see immediate results in the IP200. <br />
<br />
Needed: IP address of target LDAP server, distinguished Name and password of LDAP user entry with read access to the directory, distinguished Name as starting point for LDAP searches (base DN).<br />
<br />
*Open the IP200’s applet, proceed to directory/LDAP from external Server<br />
*Check Enable External LDAP server access<br />
*Enter the target server’s IP address<br />
*Leave port empty (default 389 is used)<br />
*Enter the Distinguished Name and Password or leave both fields empty, if an anonymous search is to be performed.<br />
*As LDAP Mode select basic <br />
*Disable Sort by 1st LDAP Name attribute<br />
*As Base enter the base DN<br />
*For Object Filter try with either inetorgperson or user or organizationalperson<br />
*Leave all remaining fields empty, save and activate the new configuration<br />
*On the IP200’s alphabetic keypad hit an arbitrary letter-key and verify whether results are shown in the display. The letter should be the first letter of a person’s surname known to be present in the directory. <br />
<br />
If nothing happens, you’ll need to work yourself through the remainder of this article.<br />
<br />
===LDAP===<br />
LDAP stands for Lightweight Directory Access Protocol; a small-footprint descendant of ITU’s older X.500 series, respectively DAP (directory access protocol). Originally developed by a group at the University of Michigan LDAP is now the de-facto standard for accessing information held within so-called Directory Servers. The protocol standardization is harboured by the IETF and specified by several RFCs. RFC 2251 is the least to name, it covers LDAPv3 - the current culmination which is implemented in innovaphone products.<br />
<br />
The protocol is made up of operations like: Bind, Search, Add, Delete,…. The operations in turn are realized through messages. The two most notable operations are listed below. <br />
<br />
All of those can be taking place between a client and a server, immediately after a TCP connection (port 389) has been established towards the server end.<br />
*Bind Operation: This Operation is handling authentication issues. It is accomplished once throughout a session. While LDAP itself is offering a wealth of authentication methods the innovaphone products currently just support clear-text authentication.<br />
<br />
The Messages are: Bind Request and Bind Result<br />
<br />
*Search Operation: A client is sending a so-called LDAP Search Filter within a Search Request. This filter details what is being searched for.<br />
<br />
The Messages are: A single Search Request, zero or more Search Result Entry messages and a completing Search Result Done.<br />
<br />
===LDAP query modes===<br />
The IP200 term LDAP mode refers to what is known in the LDAP world as LDAP control. The most important to know is that searches can fail if the server does not support the selected mode. See “LDAP Mode not supported by remote Server” below for more details on that.<br />
<br />
The next thing to keep in mind is that the paged results and virtual list view will not be used (even if configured), if both an external LDAP server and the PBX user list are queried.<br />
<br />
To benefit from these modes, there are 2 options:<br />
*Disable e.g. the LDAP access to the IP-PBX permanently (in the applet)<br />
*In the telephones user interface, enter the menu Search (Extern), (Suche (Extern)). This will query only the external LDAP server and thus use the configured mode (if available).<br />
<br />
Here is how the 3 available modes work:<br />
*Basic: No further functionality, search results can only be narrowed by entering more letters like in an advance list.<br />
*Paged Results: The down-arrow key should work. From the point a search result has been received and the telephone display shows the content, a user can scroll down further. Upward scrolling is not possible.<br />
*Virtual List View: Both scrolling directions, upwards and downwards should work after a search result came back.<br />
<br />
===Storing telephone numbers in your LDAP directory===<br />
There are virtually endless variations to store telephone numbers in directories. Just to name a few +49 (7031) 73009-0, +497031730090, (07031) 730090, 0049 (0) 7031 73009-0... <br />
<br />
Most LDAP servers do not apply magic when searching for telephony numbers, that is, they treat them as plain text. So if you have +49 (7031) 73009-0 in your directory and you search for +497031730090 via LDAP, there will be no match. It is thus critical to store telephone numbers in a proper format.<br />
<br />
Here is how the IP200 is setting up the LDAP search request for resolution of an incoming number (CLI):<br />
<br />
*Based on the phones location information, the incoming number is expanded to a full E.164 number. This is - assumed the CLI is 0070317300999 and the phone location is set to country code 49, area code 7031, national line prefix 0, international line prefix 00, trunk access prefix 0 and trunk subscriber number 73009 – normalized to +4970317300999. (For more information on the location settings, please refer to the IP200’s administrator manual)<br />
<br />
*An LDAP search expression is created which will search for 3 patterns<br />
<br />
#The raw number as received in the call (please note that this will include the trunk access prefix): 0070317300999<br />
#A pattern which will search for the normalized number with some decoration: +49*7*0*3*1*7*300999<br />
#A pattern which will search for the normalized number with full decoration: +49*7*0*3*1*7*3*0*0*9*9*9<br />
<br />
This expression will find all reasonable notations for a normalized number in the LDAP server. <br />
<br />
As a side note: when the directory searches the local flash directory, it will only use pattern 1 above.<br />
<br />
===Multiple numbers for a single contact===<br />
The way the IP200 constructs its search pattern actually forbids storing multiple numbers in a single attribute. In order to work around this a server must either allow for multiple instantiation of the respective telephone number attribute (e.g. telephoneNumber). Each instance of the attribute would contain a single number. Or the server maintains several telephone attributes with different names.<br />
<br />
For instance the Active Directory™ does both. If a new user is configured to the system, a dialogue with lots of tab-dialogues and user properties can be edited. The number that can be entered on the General page will later settle in the attribute telephoneNumber. More instances of this attribute will be created, if you clicked on Other.. right next to it. The Telephones page will allow you to configure a home phone number, a mobile phone number and so on. These latter numbers will result in additional attributes like homePhone, mobile and so on. On the IP200, the effect is that a single user shows up multiple times in the telephone display, once for each telephone number found in the directory.<br />
<br />
For more information regarding the attributes used for searching, see the IP200’s administrator manual.<br />
<br />
==LDAP Servers==<br />
===Active Directory™===<br />
<br />
Supported LDAP Modes: basic and paged results.<br />
<br />
To access the database, you will need a DN of a Windows™ domain user with read access to the directory. <br />
<br />
The IP200 will use this DN, together with the users password to authenticate itself against the Active Directory.<br />
<br />
Distinguished Name and Password: It is assumed you are logged in to Windows domain with administrator privileges on one of your domain controllers.<br />
<br />
Open a command prompt and enter:<br />
<br />
ldifde.exe -s 127.0.0.1 -f user.ldf<br />
<br />
[ See below for information regarding ldifde.exe ]<br />
<br />
As a result user.ldf will contain the entire user database as stored within the Active Directory. <br />
<br />
Open the file with a text editor and search for the user, whose credentials you want to configure in the ip200 (you may want to create a pseudo user with limited rights for this).<br />
<br />
Look for the users line beginning with dn:. The content behind is what we’re looking for.<br />
<br />
Here is an excerpt for a user named test:<br />
<br />
dn: CN=test,CN=Users,DC=inno-bln,DC=com<br />
changetype: add<br />
memberOf: CN=Administrators,CN=Builtin,DC=inno-bln,DC=com<br />
accountExpires: 9223372036854775807<br />
adminCount: 1<br />
badPasswordTime: 0<br />
badPwdCount: 0<br />
codePage: 0<br />
cn: test<br />
countryCode: 0<br />
displayName: test<br />
dSCorePropagationData: 20010725142708.0Z<br />
dSCorePropagationData: 16010101000001.0Z<br />
mail: test@inno-bln.com<br />
<br />
As Distinguished Name we’re configuring CN=test,CN=Users,DC=inno-bln,DC=com in the IP200. <br />
<br />
The password cannot be learned from the file.<br />
<br />
You can select paged results as LDAP mode (see above for details on LDAP modes). <br />
<br />
As Base you should enter what you configured as domain during the Active Directory installation. <br />
<br />
Usually something of the form: dc=mycompany,dc=com. If in doubt, you can use ldp.exe to determine the base DN. <br />
<br />
Connect to your domain controller and look for the attribute defaultNamingContext respectively namingContexts.<br />
<br />
If the IP200 shall search for Active Directory users, enter user as object filter. If it shall search for contacts only, use contact. To search both, enter <code>(|(objectclass=user)(objectclass=contact))</code>. The latter is an “Or” filter string. Using the field “objectcategory” in the filter prefix can be more efficient for the server than using “objectclass” (the default value), since the former is indexed on the Active Directory server by default, whereas the latter is not indexed by default.<br />
<br />
The Attribute 1..3 settings can be left empty, the internal default should suffice. <br />
<br />
However, if e.g. Surnames (sn) aren’t properly maintained in the Active Directory you eventually will have to fall back to a common attribute.<br />
<br />
In this case try with cn as Attribute 1, leave the other fields empty.<br />
<br />
Leave Phone 1 .. 4 empty. <br />
<br />
Leave Mail empty.<br />
<br />
===iPlanet Directory Server 5.0===<br />
[ iPlanet currently seems to be known as Sun Java System Directory Server 5.2 ]<br />
<br />
The product is the successor of Netscape’s Directory Server 4.12, so some or all of the recommendations may apply to this product too.<br />
<br />
Supported LDAP Modes: basic and virtual list view.<br />
<br />
To access the database, you will need a DN of an iPlanet user with read access to the directory. The IP200 will use this DN, together with the users password to authenticate itself against the iPlanet. It is suggested to create a dummy user with restricted privileges for this. You will need to use the value of the entrydn configuration attribute (from the iPlanet property editor) as distinguished name in the IP200 configuration.<br />
<br />
It is recommended to select basic as LDAP mode (see above for details on LDAP modes). If you intend to use virtual list view, be sure to read the next chapter carefully. We found this mode to be slow on the iPlanet.<br />
<br />
As Base you will need to configure the value entrydn property of the iPlanet sub tree containing the objects to be searched. This will be something of the form: ou=tree,dc=domain,dc=tld. If in doubt, use iPlanet’s property editor to determine proper value. <br />
<br />
All users are stored as objects of type inetOrgPerson. So simply enter inetOrgPerson as object filter.<br />
<br />
The Attribute 1..3 settings can be left empty, the internal default should suffice. You may want to experiment with either cn or sn for Attribute 1 for better results.<br />
<br />
Leave Phone 1 .. 4 empty unless you add telephone numbers to different numbers in the iPlanet management console. If so, you need to specify the respective attribute names as Phone 1 .. 4, starting with telephoneNumber.<br />
<br />
Leave Mail empty.<br />
<br />
===Using virtual list views with iPlanet===<br />
To use virtual list views on an iPlanet server, there must be a browsing index for the sub tree used as base dn. This can be created using the iPlanet management console. However, performance can be slow. The remainder of this chapter aims at helping get the best performance out of the iPlanet.<br />
<br />
To take advantage of the created index for virtual list view queries, the query must match exactly the index created. To assure best performance, it is critical thus to configure the IP200’s LDAP search expression so that it in fact will trigger the index. When an index is created, the iPlanet server internally creates two new directory entries. One is of objectclass vlvSearch and the other of objectclass vlvIndex. You will need to find some attributes of these nodes. The simplest way to get at this information is to have a look at the file <code>..\bin\slapd-xxx\config\dse.ldif</code>. You will need to find the data related to the newly created index. <br />
<br />
Here is an example:<br />
<br />
dn: cn=by MCC ou=People dc=inno-bln dc=com,cn=MCC ou=People dc=inno-bln dc=com, cn=userRoot, cn=ldbm database, cn=plugins, cn=config<br />
objectClass: top<br />
objectClass: vlvIndex<br />
cn: by MCC ou=People dc=inno-bln dc=com<br />
vlvSort: cn,givenname,o,ou,sn<br />
creatorsName: uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot<br />
modifiersName: uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot<br />
createTimestamp: 20011114120401Z<br />
modifyTimestamp: 20011114120401Z<br />
<br />
and<br />
<br />
dn: cn=MCC ou=People dc=inno-bln dc=com, cn=userRoot, cn=ldbm database, cn=plugins, cn=config<br />
objectClass: top<br />
objectClass: vlvSearch<br />
cn: MCC ou=People dc=inno-bln dc=com<br />
vlvBase: ou=People,dc=inno-bln,dc=com<br />
vlvScope: 1<br />
vlvFilter: (|(objectclass=*)(objectclass=ldapsubentry))<br />
creatorsName: uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot<br />
modifiersName: uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot<br />
createTimestamp: 20011114120400Z<br />
modifyTimestamp: 20011114120400Z<br />
numSubordinates: 1<br />
<br />
Based on this information, we can fine-tune the IP200’s configuration as follows. As Base you will need to specify the value of the vlvBase attribute. In our example, we would need to configure ou=People,dc=inno-bln,dc=com. Please note the value 1 for the vlvScope attribute above. This means the server does not recurse down from the base to look for potential search hits. <br />
<br />
Instead of inetOrgPerson you need to specify the value of the vlvFilter as object filter. <br />
<br />
In our example, we would need to configure (|(objectclass=*)(objectclass=ldapsubentry)). This will restrict the search to what is covered by the index. <br />
<br />
However, we still need to request the proper search order for the index to be used. This defined by the value of the vlvSort attribute. <br />
<br />
In our example, we would need to configure cn,givenname,o,ou,sn as sort order. Unfortunately, this cannot be configured via the phone’s applet. Instead, you need to change the respective line in the IP200’s configuration file. <br />
<br />
You will need to append the /ldap-sort sortmode option to the config file line:<br />
config change PHONEDIR0 <br />
<br />
In our example, it would look like <br />
<br />
config change PHONEDIR0 /ldap-sort cn,givenname,o,ou,sn other options<br />
<br />
Please note that in iPlanet, vlv entries can have an ACL associated. If you get Insufficient Access Rights replies, you may need to inspect the access rights.<br />
<br />
===MS Exchange 5.5===<br />
Microsoft™’s Exchange 5.5 incorporates an LDAP server, known as the Directory Store (DS). <br />
<br />
There are a few limitations, with one being really annoying: The DS does not expose everything to LDAP the Exchange 5.5 might know. In particular, the public folders used to store contact records are not accessible via LDAP. The only data that can be queried is the global address list. We thus recommend using [[Howto:ESTOS MetaDirectory, iCE Information| ESTOS MetaDirectory]] to access Exchange contact data.<br />
<br />
LDAP Modes supported: basic and paged results<br />
<br />
Distinguished Name and Password: our tests were done without any authentication, i.e. with empty user information and with an empty password.<br />
<br />
Base: use the exchange domain as base. <br />
<br />
Use ldp.exe to examine the rootDSE and retrieve the value of the namingContext attribute.<br />
<br />
This is usually something of the form: <br />
<br />
o=myexchangedomain<br />
Object Filter: we recommend using a filter, which restricts results to objects, which actually have a telephone number. <br />
This will remove confusing entries like distribution lists and the like: (&(objectclass=organizationalperson)(telephonenumber=*))<br />
Attribute 1..3: Enter: cn for Attribute 1<br />
Phone 1 .. 4: Leave empty.<br />
Mail: Leave empty.<br />
<br />
===OpenLDAP 2.07 or later===<br />
Distinguished Name and Password: enter cn=useraccount-you-want-to-use,dc=host,dc=tld as Distinguished Name and configure the respective secret as password.<br />
<br />
LDAP Mode: basic.<br />
Base: use dc=host,dc=tld, as in the distinguished name above.<br />
Object Filter: use inetorgperson.<br />
Attribute 1..3: leave empty.<br />
Phone 1 .. 4: leave empty<br />
Mail: leave empty<br />
<br />
===Lotus Domino R5===<br />
Very much like Exchange 5.5 the Domino Server does not speak LDAP natively. And like OpenLDAP: not a single LDAP control is supported. Also, certain Domino fields need to be configured for read-access. <br />
<br />
For the anonymous search requests to work, the field OfficePhoneNumber had to be configured explicitly. Without this hand-crafting, the LDAP attribute telephoneNumber never made its way towards the ip200. In the Lotus Notes Server Configuration, you will need to make sure the attributes FirstName, FullName, LastName, MailDomain and OfficePhoneNumber are listed under Anonymous users can query: in the LDAP property tab with at least Read access.<br />
<br />
LDAP Modes supported: basic<br />
<br />
Distinguished Name and Password: the tests done using anonymous LDAP search requests, i.e. with an empty user information and password.<br />
<br />
Base: please consult your local Domino Administrator for the desired organization name – it will be something of the form o=myorganization.<br />
<br />
Experience with a Domino R6 did show, that the Base had to be left empty. <br />
<br />
That is, the Domino did not offer any naming context, except an empty one.<br />
<br />
Object Filter: user inetOrgPerson or leave empty (inetorgperson is default).<br />
Attribute 1..3: Can be left empty, since the default will suffice (sn,givenName,Company).<br />
Phone 1 .. 4: leave empty.<br />
Mail: leave empty.<br />
<br />
===Cisco call manager===<br />
The Cisco Call Manager (CM) also incorporates an LDAP server, that’s meant to be queried by Cisco’s’ IP phones. <br />
<br />
Note that it’ll be likely to run on a different port than 389.<br />
<br />
LDAP Mode: use basic.<br />
<br />
Distinguished Name and Password: please query your CM Administrator for the desired information – it will be something like cn=Directory Manager,o=cisco.com accompanied by a password.<br />
<br />
Base: Please query your CM Administrator for the desired information – it will be something like: ou=users,o=cisco.com<br />
<br />
Object Filter: leave empty (inetorgperson is default).<br />
Attribute 1..3: Can be left empty, since the default will suffice (sn,givenName,Company).<br />
Phone 1 .. 4: Leave empty<br />
Mail: Leave empty<br />
<br />
===Estos MetaDirectory===<br />
MetaDirectory is an LDAP server and also a data consolidation tool. That is, it will retrieve contact data from various sources and replicate it into a single LDAP database for search and retrieval. This is a very powerful tool.<br />
<br />
Please find more information here:<br />
*[[Howto:ESTOS MetaDirectory, iCE Information]]<br />
*[[Howto:Maintain Quickdial Numbers In Estos MetaDirectory]]<br />
<br />
===innovaphone PBX===<br />
An IP200 will by default query its own PBX for directory data. There is no special configuration required to do this (except that it must be enabled in the config applet). However, in complex multi-PBX scenarios it may be necessary to query a different PBX for directory data (e.g. a master PBX in a location scenario).<br />
<br />
Here is how to configure an innovaphone PBX as external LDAP server:<br />
<br />
*Server: IP address of the PBX<br />
*Port: 389 <br />
*User Name and Password: use what is configured as valid LDAP server access in the PBX under Config/LDAP Server. Read-only access is sufficient.<br />
*Search Base: use cn=pbx0<br />
*LDAP Mode: use virtual list view.<br />
*Object Filter: use (objectclass=*)<br />
*Name Attributes : use cn as attribute<br />
*Number Attributes :use e164 as attribute<br />
*H323 ID Attr :use h323 as attribute, if you have objects to call with no number <br />
*Mail: use h323<br />
<br />
==Troubleshooting==<br />
Ldifde.exe is a standard command-line LDAP client. It is part of the Windows 2000 server software. The program allows exporting and importing the contents of an Active Directory into/from so-called LDIF files. <br />
<br />
The LDIF data format is standardized by an RFC and has the benefit to be readable with a text editor. We’re using ldifde to read out some information that in turn is required for the configuration of the telephone.<br />
<br />
Ldp.exe is an unsupported Microsoft Win32 application that can be installed from the support\tools folder of the Windows 2000 server CD. Actually it is a fairly well featured LDAP client. Despite of poor documentation it is very valuable in handling the first LDAP configuration questions. <br />
<br />
Ldp.exe may be helpful in reading a servers rootDSE, browsing a servers directory, determining potential LDAP Search Bases and so on. To see a servers rootDSE simply select Connection/connect within ldp.exe. The application then automatically queries the server for the rootDSE and presents it in the right pane window. The rootDSEs namingContexts attribute lists some possible values for the base DN.<br />
<br />
Once connected you can authenticate to a server by choosing Connection/Bind.<br />
<br />
The default (no Advanced, Domain not checked) conducts a clear-text or SIMPLE authentication (what the ip200 is doing).<br />
<br />
In contrast to MS Internet Explorer the Netscape Browser may serve as a fairly well featured LDAP client. Beyond Netscape Messenger’s LDAP capabilities the Browser does support the LDAP-URL specified in RFC1959. The only constraint is the necessity for anonymous read access. The browser even does not give any error message if the LDAP Bind operation fails.<br />
<br />
Here’s how you can read an LDAP server’s rootDSE:<br />
<br />
ldap://server/??base<br />
<br />
Every object underneath a hypothetical DN o=myorg:<br />
<br />
ldap://server/o=myorg??sub<br />
<br />
To obtain meaningful traces from the IP200, you will need to switch on the /trace and /ldap-trace options of the IP200’s PHONEDIR0 config line. <br />
<br />
Make sure to append these traces to your current configuration, such that it looks something like<br />
<br />
config change PHONEDIR0 /trace /ldap-trace further-options<br />
<br />
===Common Problems===<br />
0:1607:171:3 - ldir(S): LDAP BIND failed=> 49,"Invalid Credentials"<br />
<br />
Either the distinguished name/password for the server login is wrong or the server does not support clear text authentication.<br />
<br />
0:1153:561:4 - ldir(S): LDAP SEARCH failed=> 12,"A Critical Extension (LDAP Control) Is Unavailable"<br />
<br />
The server does not support a search control you are using. <br />
<br />
Make sure the Sort by 1st LDAP name attribute is unchecked and there is no /ldap-sort option in the config file. <br />
<br />
If this does not help, try basic as LDAP mode.<br />
<br />
== Related Articles ==<br />
*[http://www.microsoft.com/windowsserver2003/techinfo/overview/ldapcomp.mspx Ldap for beginners]<br />
*[[Howto:ESTOS MetaDirectory, iCE Information]]<br />
*[[Howto:Maintain Quickdial Numbers In Estos MetaDirectory]]<br />
<br />
[[Category:Howto|{{PAGENAME}}]]</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Howto:How_to_configure_the_Phones_LDAP_client&diff=21061Howto:How to configure the Phones LDAP client2011-05-04T07:22:36Z<p>Tsr: /* innovaphone PBX */</p>
<hr />
<div>The IP200 (also the IP110 ,IP202 and IP230) features a powerful telephone number directory. <br />
<br />
It will perform number-to-name resolution for incoming calls and name-to-number resolution for outgoing calls (using the IP200 built-in alphanumeric keyboard). <br />
<br />
The directory can access up to 3 sources for lookup: the internal (flash-based) list, the PBX user list and an external LDAP server.<br />
<br />
This article describes how to configure the IP200’s LDAP interface for various application scenarios. <br />
<br />
It is meant as a complement to the existing standard product documentation, so please refer to this for general configuration issues.<br />
<br />
<br />
==Applies To==<br />
This information applies to<br />
<br />
* IP110<br />
* IP200<br />
* IP202<br />
* IP230<br />
* IP240<br />
* IP240-1000<br />
* IP72<br />
<br />
==More Information==<br />
<br />
===Quick start===<br />
<br />
This topic is for people with good understanding of LDAP and with little time for reading, who simply want to see immediate results in the IP200. <br />
<br />
Needed: IP address of target LDAP server, distinguished Name and password of LDAP user entry with read access to the directory, distinguished Name as starting point for LDAP searches (base DN).<br />
<br />
*Open the IP200’s applet, proceed to directory/LDAP from external Server<br />
*Check Enable External LDAP server access<br />
*Enter the target server’s IP address<br />
*Leave port empty (default 389 is used)<br />
*Enter the Distinguished Name and Password or leave both fields empty, if an anonymous search is to be performed.<br />
*As LDAP Mode select basic <br />
*Disable Sort by 1st LDAP Name attribute<br />
*As Base enter the base DN<br />
*For Object Filter try with either inetorgperson or user or organizationalperson<br />
*Leave all remaining fields empty, save and activate the new configuration<br />
*On the IP200’s alphabetic keypad hit an arbitrary letter-key and verify whether results are shown in the display. The letter should be the first letter of a person’s surname known to be present in the directory. <br />
<br />
If nothing happens, you’ll need to work yourself through the remainder of this article.<br />
<br />
===LDAP===<br />
LDAP stands for Lightweight Directory Access Protocol; a small-footprint descendant of ITU’s older X.500 series, respectively DAP (directory access protocol). Originally developed by a group at the University of Michigan LDAP is now the de-facto standard for accessing information held within so-called Directory Servers. The protocol standardization is harboured by the IETF and specified by several RFCs. RFC 2251 is the least to name, it covers LDAPv3 - the current culmination which is implemented in innovaphone products.<br />
<br />
The protocol is made up of operations like: Bind, Search, Add, Delete,…. The operations in turn are realized through messages. The two most notable operations are listed below. <br />
<br />
All of those can be taking place between a client and a server, immediately after a TCP connection (port 389) has been established towards the server end.<br />
*Bind Operation: This Operation is handling authentication issues. It is accomplished once throughout a session. While LDAP itself is offering a wealth of authentication methods the innovaphone products currently just support clear-text authentication.<br />
<br />
The Messages are: Bind Request and Bind Result<br />
<br />
*Search Operation: A client is sending a so-called LDAP Search Filter within a Search Request. This filter details what is being searched for.<br />
<br />
The Messages are: A single Search Request, zero or more Search Result Entry messages and a completing Search Result Done.<br />
<br />
===LDAP query modes===<br />
The IP200 term LDAP mode refers to what is known in the LDAP world as LDAP control. The most important to know is that searches can fail if the server does not support the selected mode. See “LDAP Mode not supported by remote Server” below for more details on that.<br />
<br />
The next thing to keep in mind is that the paged results and virtual list view will not be used (even if configured), if both an external LDAP server and the PBX user list are queried.<br />
<br />
To benefit from these modes, there are 2 options:<br />
*Disable e.g. the LDAP access to the IP-PBX permanently (in the applet)<br />
*In the telephones user interface, enter the menu Search (Extern), (Suche (Extern)). This will query only the external LDAP server and thus use the configured mode (if available).<br />
<br />
Here is how the 3 available modes work:<br />
*Basic: No further functionality, search results can only be narrowed by entering more letters like in an advance list.<br />
*Paged Results: The down-arrow key should work. From the point a search result has been received and the telephone display shows the content, a user can scroll down further. Upward scrolling is not possible.<br />
*Virtual List View: Both scrolling directions, upwards and downwards should work after a search result came back.<br />
<br />
===Storing telephone numbers in your LDAP directory===<br />
There are virtually endless variations to store telephone numbers in directories. Just to name a few +49 (7031) 73009-0, +497031730090, (07031) 730090, 0049 (0) 7031 73009-0... <br />
<br />
Most LDAP servers do not apply magic when searching for telephony numbers, that is, they treat them as plain text. So if you have +49 (7031) 73009-0 in your directory and you search for +497031730090 via LDAP, there will be no match. It is thus critical to store telephone numbers in a proper format.<br />
<br />
Here is how the IP200 is setting up the LDAP search request for resolution of an incoming number (CLI):<br />
<br />
*Based on the phones location information, the incoming number is expanded to a full E.164 number. This is - assumed the CLI is 0070317300999 and the phone location is set to country code 49, area code 7031, national line prefix 0, international line prefix 00, trunk access prefix 0 and trunk subscriber number 73009 – normalized to +4970317300999. (For more information on the location settings, please refer to the IP200’s administrator manual)<br />
<br />
*An LDAP search expression is created which will search for 3 patterns<br />
<br />
#The raw number as received in the call (please note that this will include the trunk access prefix): 0070317300999<br />
#A pattern which will search for the normalized number with some decoration: +49*7*0*3*1*7*300999<br />
#A pattern which will search for the normalized number with full decoration: +49*7*0*3*1*7*3*0*0*9*9*9<br />
<br />
This expression will find all reasonable notations for a normalized number in the LDAP server. <br />
<br />
As a side note: when the directory searches the local flash directory, it will only use pattern 1 above.<br />
<br />
===Multiple numbers for a single contact===<br />
The way the IP200 constructs its search pattern actually forbids storing multiple numbers in a single attribute. In order to work around this a server must either allow for multiple instantiation of the respective telephone number attribute (e.g. telephoneNumber). Each instance of the attribute would contain a single number. Or the server maintains several telephone attributes with different names.<br />
<br />
For instance the Active Directory™ does both. If a new user is configured to the system, a dialogue with lots of tab-dialogues and user properties can be edited. The number that can be entered on the General page will later settle in the attribute telephoneNumber. More instances of this attribute will be created, if you clicked on Other.. right next to it. The Telephones page will allow you to configure a home phone number, a mobile phone number and so on. These latter numbers will result in additional attributes like homePhone, mobile and so on. On the IP200, the effect is that a single user shows up multiple times in the telephone display, once for each telephone number found in the directory.<br />
<br />
For more information regarding the attributes used for searching, see the IP200’s administrator manual.<br />
<br />
==LDAP Servers==<br />
===Active Directory™===<br />
<br />
Supported LDAP Modes: basic and paged results.<br />
<br />
To access the database, you will need a DN of a Windows™ domain user with read access to the directory. <br />
<br />
The IP200 will use this DN, together with the users password to authenticate itself against the Active Directory.<br />
<br />
Distinguished Name and Password: It is assumed you are logged in to Windows domain with administrator privileges on one of your domain controllers.<br />
<br />
Open a command prompt and enter:<br />
<br />
ldifde.exe -s 127.0.0.1 -f user.ldf<br />
<br />
[ See below for information regarding ldifde.exe ]<br />
<br />
As a result user.ldf will contain the entire user database as stored within the Active Directory. <br />
<br />
Open the file with a text editor and search for the user, whose credentials you want to configure in the ip200 (you may want to create a pseudo user with limited rights for this).<br />
<br />
Look for the users line beginning with dn:. The content behind is what we’re looking for.<br />
<br />
Here is an excerpt for a user named test:<br />
<br />
dn: CN=test,CN=Users,DC=inno-bln,DC=com<br />
changetype: add<br />
memberOf: CN=Administrators,CN=Builtin,DC=inno-bln,DC=com<br />
accountExpires: 9223372036854775807<br />
adminCount: 1<br />
badPasswordTime: 0<br />
badPwdCount: 0<br />
codePage: 0<br />
cn: test<br />
countryCode: 0<br />
displayName: test<br />
dSCorePropagationData: 20010725142708.0Z<br />
dSCorePropagationData: 16010101000001.0Z<br />
mail: test@inno-bln.com<br />
<br />
As Distinguished Name we’re configuring CN=test,CN=Users,DC=inno-bln,DC=com in the IP200. <br />
<br />
The password cannot be learned from the file.<br />
<br />
You can select paged results as LDAP mode (see above for details on LDAP modes). <br />
<br />
As Base you should enter what you configured as domain during the Active Directory installation. <br />
<br />
Usually something of the form: dc=mycompany,dc=com. If in doubt, you can use ldp.exe to determine the base DN. <br />
<br />
Connect to your domain controller and look for the attribute defaultNamingContext respectively namingContexts.<br />
<br />
If the IP200 shall search for Active Directory users, enter user as object filter. If it shall search for contacts only, use contact. To search both, enter <code>(|(objectclass=user)(objectclass=contact))</code>. The latter is an “Or” filter string. Using the field “objectcategory” in the filter prefix can be more efficient for the server than using “objectclass” (the default value), since the former is indexed on the Active Directory server by default, whereas the latter is not indexed by default.<br />
<br />
The Attribute 1..3 settings can be left empty, the internal default should suffice. <br />
<br />
However, if e.g. Surnames (sn) aren’t properly maintained in the Active Directory you eventually will have to fall back to a common attribute.<br />
<br />
In this case try with cn as Attribute 1, leave the other fields empty.<br />
<br />
Leave Phone 1 .. 4 empty. <br />
<br />
Leave Mail empty.<br />
<br />
===iPlanet Directory Server 5.0===<br />
[ iPlanet currently seems to be known as Sun Java System Directory Server 5.2 ]<br />
<br />
The product is the successor of Netscape’s Directory Server 4.12, so some or all of the recommendations may apply to this product too.<br />
<br />
Supported LDAP Modes: basic and virtual list view.<br />
<br />
To access the database, you will need a DN of an iPlanet user with read access to the directory. The IP200 will use this DN, together with the users password to authenticate itself against the iPlanet. It is suggested to create a dummy user with restricted privileges for this. You will need to use the value of the entrydn configuration attribute (from the iPlanet property editor) as distinguished name in the IP200 configuration.<br />
<br />
It is recommended to select basic as LDAP mode (see above for details on LDAP modes). If you intend to use virtual list view, be sure to read the next chapter carefully. We found this mode to be slow on the iPlanet.<br />
<br />
As Base you will need to configure the value entrydn property of the iPlanet sub tree containing the objects to be searched. This will be something of the form: ou=tree,dc=domain,dc=tld. If in doubt, use iPlanet’s property editor to determine proper value. <br />
<br />
All users are stored as objects of type inetOrgPerson. So simply enter inetOrgPerson as object filter.<br />
<br />
The Attribute 1..3 settings can be left empty, the internal default should suffice. You may want to experiment with either cn or sn for Attribute 1 for better results.<br />
<br />
Leave Phone 1 .. 4 empty unless you add telephone numbers to different numbers in the iPlanet management console. If so, you need to specify the respective attribute names as Phone 1 .. 4, starting with telephoneNumber.<br />
<br />
Leave Mail empty.<br />
<br />
===Using virtual list views with iPlanet===<br />
To use virtual list views on an iPlanet server, there must be a browsing index for the sub tree used as base dn. This can be created using the iPlanet management console. However, performance can be slow. The remainder of this chapter aims at helping get the best performance out of the iPlanet.<br />
<br />
To take advantage of the created index for virtual list view queries, the query must match exactly the index created. To assure best performance, it is critical thus to configure the IP200’s LDAP search expression so that it in fact will trigger the index. When an index is created, the iPlanet server internally creates two new directory entries. One is of objectclass vlvSearch and the other of objectclass vlvIndex. You will need to find some attributes of these nodes. The simplest way to get at this information is to have a look at the file <code>..\bin\slapd-xxx\config\dse.ldif</code>. You will need to find the data related to the newly created index. <br />
<br />
Here is an example:<br />
<br />
dn: cn=by MCC ou=People dc=inno-bln dc=com,cn=MCC ou=People dc=inno-bln dc=com, cn=userRoot, cn=ldbm database, cn=plugins, cn=config<br />
objectClass: top<br />
objectClass: vlvIndex<br />
cn: by MCC ou=People dc=inno-bln dc=com<br />
vlvSort: cn,givenname,o,ou,sn<br />
creatorsName: uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot<br />
modifiersName: uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot<br />
createTimestamp: 20011114120401Z<br />
modifyTimestamp: 20011114120401Z<br />
<br />
and<br />
<br />
dn: cn=MCC ou=People dc=inno-bln dc=com, cn=userRoot, cn=ldbm database, cn=plugins, cn=config<br />
objectClass: top<br />
objectClass: vlvSearch<br />
cn: MCC ou=People dc=inno-bln dc=com<br />
vlvBase: ou=People,dc=inno-bln,dc=com<br />
vlvScope: 1<br />
vlvFilter: (|(objectclass=*)(objectclass=ldapsubentry))<br />
creatorsName: uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot<br />
modifiersName: uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot<br />
createTimestamp: 20011114120400Z<br />
modifyTimestamp: 20011114120400Z<br />
numSubordinates: 1<br />
<br />
Based on this information, we can fine-tune the IP200’s configuration as follows. As Base you will need to specify the value of the vlvBase attribute. In our example, we would need to configure ou=People,dc=inno-bln,dc=com. Please note the value 1 for the vlvScope attribute above. This means the server does not recurse down from the base to look for potential search hits. <br />
<br />
Instead of inetOrgPerson you need to specify the value of the vlvFilter as object filter. <br />
<br />
In our example, we would need to configure (|(objectclass=*)(objectclass=ldapsubentry)). This will restrict the search to what is covered by the index. <br />
<br />
However, we still need to request the proper search order for the index to be used. This defined by the value of the vlvSort attribute. <br />
<br />
In our example, we would need to configure cn,givenname,o,ou,sn as sort order. Unfortunately, this cannot be configured via the phone’s applet. Instead, you need to change the respective line in the IP200’s configuration file. <br />
<br />
You will need to append the /ldap-sort sortmode option to the config file line:<br />
config change PHONEDIR0 <br />
<br />
In our example, it would look like <br />
<br />
config change PHONEDIR0 /ldap-sort cn,givenname,o,ou,sn other options<br />
<br />
Please note that in iPlanet, vlv entries can have an ACL associated. If you get Insufficient Access Rights replies, you may need to inspect the access rights.<br />
<br />
===MS Exchange 5.5===<br />
Microsoft™’s Exchange 5.5 incorporates an LDAP server, known as the Directory Store (DS). <br />
<br />
There are a few limitations, with one being really annoying: The DS does not expose everything to LDAP the Exchange 5.5 might know. In particular, the public folders used to store contact records are not accessible via LDAP. The only data that can be queried is the global address list. We thus recommend using [[Howto:ESTOS MetaDirectory, iCE Information| ESTOS MetaDirectory]] to access Exchange contact data.<br />
<br />
LDAP Modes supported: basic and paged results<br />
<br />
Distinguished Name and Password: our tests were done without any authentication, i.e. with empty user information and with an empty password.<br />
<br />
Base: use the exchange domain as base. <br />
<br />
Use ldp.exe to examine the rootDSE and retrieve the value of the namingContext attribute.<br />
<br />
This is usually something of the form: <br />
<br />
o=myexchangedomain<br />
Object Filter: we recommend using a filter, which restricts results to objects, which actually have a telephone number. <br />
This will remove confusing entries like distribution lists and the like: (&(objectclass=organizationalperson)(telephonenumber=*))<br />
Attribute 1..3: Enter: cn for Attribute 1<br />
Phone 1 .. 4: Leave empty.<br />
Mail: Leave empty.<br />
<br />
===OpenLDAP 2.07 or later===<br />
Distinguished Name and Password: enter cn=useraccount-you-want-to-use,dc=host,dc=tld as Distinguished Name and configure the respective secret as password.<br />
<br />
LDAP Mode: basic.<br />
Base: use dc=host,dc=tld, as in the distinguished name above.<br />
Object Filter: use inetorgperson.<br />
Attribute 1..3: leave empty.<br />
Phone 1 .. 4: leave empty<br />
Mail: leave empty<br />
<br />
===Lotus Domino R5===<br />
Very much like Exchange 5.5 the Domino Server does not speak LDAP natively. And like OpenLDAP: not a single LDAP control is supported. Also, certain Domino fields need to be configured for read-access. <br />
<br />
For the anonymous search requests to work, the field OfficePhoneNumber had to be configured explicitly. Without this hand-crafting, the LDAP attribute telephoneNumber never made its way towards the ip200. In the Lotus Notes Server Configuration, you will need to make sure the attributes FirstName, FullName, LastName, MailDomain and OfficePhoneNumber are listed under Anonymous users can query: in the LDAP property tab with at least Read access.<br />
<br />
LDAP Modes supported: basic<br />
<br />
Distinguished Name and Password: the tests done using anonymous LDAP search requests, i.e. with an empty user information and password.<br />
<br />
Base: please consult your local Domino Administrator for the desired organization name – it will be something of the form o=myorganization.<br />
<br />
Experience with a Domino R6 did show, that the Base had to be left empty. <br />
<br />
That is, the Domino did not offer any naming context, except an empty one.<br />
<br />
Object Filter: user inetOrgPerson or leave empty (inetorgperson is default).<br />
Attribute 1..3: Can be left empty, since the default will suffice (sn,givenName,Company).<br />
Phone 1 .. 4: leave empty.<br />
Mail: leave empty.<br />
<br />
===Cisco call manager===<br />
The Cisco Call Manager (CM) also incorporates an LDAP server, that’s meant to be queried by Cisco’s’ IP phones. <br />
<br />
Note that it’ll be likely to run on a different port than 389.<br />
<br />
LDAP Mode: use basic.<br />
<br />
Distinguished Name and Password: please query your CM Administrator for the desired information – it will be something like cn=Directory Manager,o=cisco.com accompanied by a password.<br />
<br />
Base: Please query your CM Administrator for the desired information – it will be something like: ou=users,o=cisco.com<br />
<br />
Object Filter: leave empty (inetorgperson is default).<br />
Attribute 1..3: Can be left empty, since the default will suffice (sn,givenName,Company).<br />
Phone 1 .. 4: Leave empty<br />
Mail: Leave empty<br />
<br />
===Estos MetaDirectory===<br />
MetaDirectory is an LDAP server and also a data consolidation tool. That is, it will retrieve contact data from various sources and replicate it into a single LDAP database for search and retrieval. This is a very powerful tool.<br />
<br />
Please find more information here:<br />
*[[Howto:ESTOS MetaDirectory, iCE Information]]<br />
*[[Howto:Maintain Quickdial Numbers In Estos MetaDirectory]]<br />
<br />
===innovaphone PBX===<br />
An IP200 will by default query its own PBX for directory data. There is no special configuration required to do this (except that it must be enabled in the config applet). However, in complex multi-PBX scenarios it may be necessary to query a different PBX for directory data (e.g. a master PBX in a location scenario).<br />
<br />
Here is how to configure an innovaphone PBX as external LDAP server:<br />
<br />
*Server: IP address of the PBX<br />
*Port: 389 <br />
*User Name and Password: use what is configured as valid LDAP server access in the PBX under Config/LDAP Server. Read-only access is sufficient.<br />
*Search Base: use cn=pbx0<br />
*LDAP Mode: use virtual list view.<br />
*Object Filter: use (objectclass=*)<br />
*Name Attributes : use cn as Attribute<br />
*Number Attributes :use e164 as Attribute<br />
*H323 ID Attr :use h323 as attributes, if you have objects to call with no number <br />
*Mail: use h323<br />
<br />
==Troubleshooting==<br />
Ldifde.exe is a standard command-line LDAP client. It is part of the Windows 2000 server software. The program allows exporting and importing the contents of an Active Directory into/from so-called LDIF files. <br />
<br />
The LDIF data format is standardized by an RFC and has the benefit to be readable with a text editor. We’re using ldifde to read out some information that in turn is required for the configuration of the telephone.<br />
<br />
Ldp.exe is an unsupported Microsoft Win32 application that can be installed from the support\tools folder of the Windows 2000 server CD. Actually it is a fairly well featured LDAP client. Despite of poor documentation it is very valuable in handling the first LDAP configuration questions. <br />
<br />
Ldp.exe may be helpful in reading a servers rootDSE, browsing a servers directory, determining potential LDAP Search Bases and so on. To see a servers rootDSE simply select Connection/connect within ldp.exe. The application then automatically queries the server for the rootDSE and presents it in the right pane window. The rootDSEs namingContexts attribute lists some possible values for the base DN.<br />
<br />
Once connected you can authenticate to a server by choosing Connection/Bind.<br />
<br />
The default (no Advanced, Domain not checked) conducts a clear-text or SIMPLE authentication (what the ip200 is doing).<br />
<br />
In contrast to MS Internet Explorer the Netscape Browser may serve as a fairly well featured LDAP client. Beyond Netscape Messenger’s LDAP capabilities the Browser does support the LDAP-URL specified in RFC1959. The only constraint is the necessity for anonymous read access. The browser even does not give any error message if the LDAP Bind operation fails.<br />
<br />
Here’s how you can read an LDAP server’s rootDSE:<br />
<br />
ldap://server/??base<br />
<br />
Every object underneath a hypothetical DN o=myorg:<br />
<br />
ldap://server/o=myorg??sub<br />
<br />
To obtain meaningful traces from the IP200, you will need to switch on the /trace and /ldap-trace options of the IP200’s PHONEDIR0 config line. <br />
<br />
Make sure to append these traces to your current configuration, such that it looks something like<br />
<br />
config change PHONEDIR0 /trace /ldap-trace further-options<br />
<br />
===Common Problems===<br />
0:1607:171:3 - ldir(S): LDAP BIND failed=> 49,"Invalid Credentials"<br />
<br />
Either the distinguished name/password for the server login is wrong or the server does not support clear text authentication.<br />
<br />
0:1153:561:4 - ldir(S): LDAP SEARCH failed=> 12,"A Critical Extension (LDAP Control) Is Unavailable"<br />
<br />
The server does not support a search control you are using. <br />
<br />
Make sure the Sort by 1st LDAP name attribute is unchecked and there is no /ldap-sort option in the config file. <br />
<br />
If this does not help, try basic as LDAP mode.<br />
<br />
== Related Articles ==<br />
*[http://www.microsoft.com/windowsserver2003/techinfo/overview/ldapcomp.mspx Ldap for beginners]<br />
*[[Howto:ESTOS MetaDirectory, iCE Information]]<br />
*[[Howto:Maintain Quickdial Numbers In Estos MetaDirectory]]<br />
<br />
[[Category:Howto|{{PAGENAME}}]]</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:Phone/User/Function-Keys/Partner&diff=21049Reference9:Phone/User/Function-Keys/Partner2011-05-02T08:58:18Z<p>Tsr: /* Partner */</p>
<hr />
<div>== Partner ==<br />
<br />
The Partner function is divided into three states.<br />
<br />
* '''Idle''': In the Idle state, this key performs a direct dial.<br />
<br />
* '''Alerting''': This state indicates that the partner's telephone is ringing; the call can be picked up with this key.<br />
<br />
* '''Busy''': In the Busy state, the function key is used only to display the partner state.<br />
<br />
With the following functions, you can use the Partner function as described.<br />
<br />
'''Partner identification'''<br />
* You define the partner telephone with the corresponding number or name.<br />
<br />
'''Partner Type'''<br />
* '''Default''' - normal partner key<br />
* '''Executive''' - use the CLIP (extension) of the partners executive object to execute calls<br />
* '''Secretary''' - see CFX (call diversion) state and primary secretary join/leave group state. This feature uses ''Subscribe for Presence'' functionality (''Subscribe for Presence'' must be enabled). Also you need to set the name ( and not the number) of the '''Partner identification''' to get the presence subscription work with the '''Secretary''' parter type.<br />
<br />
'''Perform intrusion if partner is busy'''<br />
* If the partner’s line is already active, an intrusion call is sent with a preceding alert signal. The current call is automatically put on hold.<br />
Type ''Conference'' or ''silent monitoring''<br />
<br />
'''Subscribe for Presence'''<br />
* Needed to be activated when the presence status of the partner or call diversion and group state of the secretary should be monitored. The field ''Partner identification'' must be configured with name only (no number) so that ''Subscribe for Presence'' can be used.<br />
<br />
'''Subscribe for Dialog Info'''<br />
* Needed to be activated to get the partner informations of users from other PBXs. When ''Subscribe for Dialog Info'' is turned, the partner's busy state will be retrieved using a subscription. No group indications are required nor evaluated then. Otherwise, the partner's busy state is derived from group indications received. As a result, the partner key will work only if [[Reference9:PBX/Objects#Object_Properties | group indications ]] are configured for the user. <br />
<br />
There are 4 modes to subscribe for dialog info (no need for group indications )<br />
<br />
* the user (that should be monitored) is in the same group, and you are active in this group<br />
* one of the own active groups added in the access list² of the monitored user<br />
* added the own domain in the access list (e.g @innovaphone.com)<br />
* added the own name in the access list of the monitored user<br />
<br />
² The access list is used for the my PBX client to [[Reference9:PBX/Objects/Edit Allow]] the call state and presence status of other users.<br />
<br />
<br />
<br />
<br />
'''Hide calling party in alerting state'''<br />
* The number of the incoming call is hidden for the partner.<br />
<br />
'''Hide calling party in ringback state'''<br />
<br />
'''Show connected party in busy state'''<br />
* Unlike with the preceding function, the number of the active line is visible only to the partner.<br />
<br />
'''Do not pick up an alerting Call</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:Phone/User/Function-Keys/Partner&diff=21048Reference9:Phone/User/Function-Keys/Partner2011-05-02T08:57:52Z<p>Tsr: /* Partner */</p>
<hr />
<div>== Partner ==<br />
<br />
The Partner function is divided into three states.<br />
<br />
* '''Idle''': In the Idle state, this key performs a direct dial.<br />
<br />
* '''Alerting''': This state indicates that the partner's telephone is ringing; the call can be picked up with this key.<br />
<br />
* '''Busy''': In the Busy state, the function key is used only to display the partner state.<br />
<br />
With the following functions, you can use the Partner function as described.<br />
<br />
'''Partner identification'''<br />
* You define the partner telephone with the corresponding number or name.<br />
<br />
'''Partner Type'''<br />
* '''Default''' - normal partner key<br />
* '''Executive''' - use the CLIP (extension) of the partners executive object to execute calls<br />
* '''Secretary''' - see CFX (call diversion) state and primary secretary join/leave group state. This feature uses ''Subscribe for Presence'' functionality (''Subscribe for Presence'' must be enabled). Also you need to set the name of the '''Partner identification''' to get the presence subscription work with the '''Secretary''' parter type.<br />
<br />
'''Perform intrusion if partner is busy'''<br />
* If the partner’s line is already active, an intrusion call is sent with a preceding alert signal. The current call is automatically put on hold.<br />
Type ''Conference'' or ''silent monitoring''<br />
<br />
'''Subscribe for Presence'''<br />
* Needed to be activated when the presence status of the partner or call diversion and group state of the secretary should be monitored. The field ''Partner identification'' must be configured with name only (no number) so that ''Subscribe for Presence'' can be used.<br />
<br />
'''Subscribe for Dialog Info'''<br />
* Needed to be activated to get the partner informations of users from other PBXs. When ''Subscribe for Dialog Info'' is turned, the partner's busy state will be retrieved using a subscription. No group indications are required nor evaluated then. Otherwise, the partner's busy state is derived from group indications received. As a result, the partner key will work only if [[Reference9:PBX/Objects#Object_Properties | group indications ]] are configured for the user. <br />
<br />
There are 4 modes to subscribe for dialog info (no need for group indications )<br />
<br />
* the user (that should be monitored) is in the same group, and you are active in this group<br />
* one of the own active groups added in the access list² of the monitored user<br />
* added the own domain in the access list (e.g @innovaphone.com)<br />
* added the own name in the access list of the monitored user<br />
<br />
² The access list is used for the my PBX client to [[Reference9:PBX/Objects/Edit Allow]] the call state and presence status of other users.<br />
<br />
<br />
<br />
<br />
'''Hide calling party in alerting state'''<br />
* The number of the incoming call is hidden for the partner.<br />
<br />
'''Hide calling party in ringback state'''<br />
<br />
'''Show connected party in busy state'''<br />
* Unlike with the preceding function, the number of the active line is visible only to the partner.<br />
<br />
'''Do not pick up an alerting Call</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Howto:Feature_Liste_in_Deutsch&diff=21033Howto:Feature Liste in Deutsch2011-04-28T14:06:21Z<p>Tsr: /* Neu in V9 */</p>
<hr />
<div>innovaphone Feature Liste <br />
<br />
==Applies To==<br />
Diese Information ist für<br />
<br />
− Alle innovaphone Produkte basierend auf V7,V8 und V9<br />
<br />
<br />
==Download==<br />
[[Media:innovaphone_V8_Featureliste_de.pdf]] <br />
<br />
<br />
==More Information==<br />
<br />
===System Features – IP302 / IP305 / IP800 / IP2000 / IP6000 /IP1060 / IP3010 / IP6010 / IPVA ===<br />
<br />
ACD Gruppen <br />
<br />
Active Directory Replikation <br />
<br />
Alarm und Error Events <br />
<br />
Alternative Wegesuche <br />
<br />
Ankommender Direktruf zu Teilnehmer oder Gruppe <br />
<br />
Anrufumleitung über Web einrichten / ändern / löschen <br />
<br />
Automatische Anrufverteilung (ACD) <br />
<br />
Automatische Nachtschaltung mit Wochenuhr <br />
<br />
Automatische Wegewahl (ARS) <br />
<br />
Automatisches Durchbrechen von Anrufschutz für bevorzugte Nummern <br />
<br />
Berechtigungen der Teilnehmer <br />
<br />
Berechtigungen der Teilnehmer zeitbasierend<br />
<br />
Berechtigungsgruppen (class of service) <br />
<br />
Bootcode mit minifirmware (nicht supported mit IP3000) <br />
<br />
Call Detail Records (CDR) intern und extern <br />
<br />
Config Templates für PBX User <br />
<br />
DTMF Erkennung abschaltbar <br />
<br />
DTMF-Nachwahl/Durchwahl <br />
<br />
Durchwahl (mit und ohne Ziffernumwertung) <br />
<br />
Eingebaute Musik in Wartestellung <br />
<br />
Einstellbare Töne <br />
<br />
Einzelziffernwahl (overlapped sending)<br />
<br />
Erweiterte H.323 Features nach H.450.x <br />
<br />
Erweitertes DTMF Objekt (Leistungsmerkmale via DTMF Wahl) <br />
<br />
Erweitertes Error Reporting (SIP, QOS Parameter, Router Error Reporting)<br />
<br />
Externe Kommunikation <br />
<br />
Fernüberwachung und Ferndiagnose <br />
<br />
Filialen (virtuelle zentrale PBX) <br />
<br />
Firmware Upload in DRAM (nicht supported mit IP3000) <br />
<br />
Flexibler Rufnummernplan <br />
<br />
Floating Lizenzmodell <br />
<br />
Gebührenerfassung (CDR) <br />
<br />
Gemischte Wahlverfahren (overlap- und Blockwahl) <br />
<br />
Generalnachtschaltung <br />
<br />
Gesprächsrückgabe zur Vermittlung <br />
<br />
Gruppenruf (alle, zyklisch)<br />
<br />
Heimarbeitsplatz <br />
<br />
HTTP / HTTPS Erlaubte Subnetze<br />
<br />
Identifikation der rufenden Leitung (CLIP) <br />
<br />
Interaktive Rufannahme (*) <br />
<br />
Interface für externe Durchsageeinrichtung (#) <br />
<br />
Interne Kommunikation <br />
<br />
Kurzwahl (individuell, Gruppe, systemweit) <br />
<br />
LDAP replikation<br />
<br />
Least Cost Routing (LCR) <br />
<br />
Leitungsbündel <br />
<br />
Log Weiterleitung/Zentralisierung<br />
<br />
Mehrfachkonferenz (IP800, IP6000, IP1060, IP3010, IP6010, IP0010)<br />
<br />
Mehrstufiges Login (multi-user) <br />
<br />
Messaging <br />
<br />
Messaging (SIP und H.323) <br />
<br />
MS-chap V1/V2 <br />
<br />
Multilevel Admin Access (Detaillierte mehrstufige Rechte-Vergabe zur Konfiguration der PBX) <br />
<br />
Multiple System Admin (Mehrere Viewer und Mehrere Admins , Viewer oder Admin Rechte) <br />
<br />
Multiprotokoll (H.323, SIP) <br />
<br />
Musik/Ansage in Wartestellung von analoger Quelle (#) <br />
<br />
Musik/Ansage in Wartestellung von HTTP-Quelle (*) <br />
<br />
MWI (Message Waiting Indication) <br />
<br />
Message Center (H.450.7 oder DTMF) <br />
<br />
Netzwerkweite Features (Master/Slave mit virtueller PBX) <br />
<br />
Nichtanzeigen von Objekten im LDAP-Telefonbuch <br />
<br />
Nur anrufbarer Teilnehmer (Passivschaltung) <br />
<br />
PBX Directory Search (LDAP Suche via DTMF) <br />
<br />
QSIG <br />
<br />
QSIG-Interworking <br />
<br />
QSIG-Trunking (Punkt zu Punkt, Punkt zu Mehrpunkt) <br />
<br />
Querverbindungen über IP <br />
<br />
Querverbindungen über ISDN <br />
<br />
Redundanz der ISDN-Leitungen <br />
<br />
Redundanz der PBX <br />
<br />
Remote Software-Upgrade <br />
<br />
Ringruf mit Ringrufabfrage (#) <br />
<br />
RTP Proxy <br />
<br />
Rückfrage <br />
<br />
Rückfrage auch bei Internanruf <br />
<br />
Rufen nach E.164 <br />
<br />
Rufen über ENUM (H.323 und SIP) <br />
<br />
Rufnummernunterdrückung (CLIR) <br />
<br />
SDP Transit (für Video und andere Codecs) <br />
<br />
Silent Intrusion <br />
<br />
SIP Medial-Relay (RTP stream routing via Gateway) <br />
<br />
SIP-Trunking <br />
<br />
SIP via TCP <br />
<br />
SIPS (SIP-Secure) – SIP via TCP/TLS (nicht supported mit IP3000) <br />
<br />
SNMP Traps (Alarm Events)<br />
<br />
SOAP-API <br />
<br />
SRTP (Verschlüsselung des Medienkanals) für H.323 und SIP (nicht supported mit IP3000) <br />
<br />
Standard Protokolle bis zum Endgerät <br />
<br />
Systemzeit/Datum über Timeserver (LAN oder Web) <br />
<br />
Taktsynchronisation über IP-Strecke <br />
<br />
TAPI / Multi line TAPI (über mehrere PBXen / Lokationen)<br />
<br />
Teilnehmergruppen mit progressivem Ruf (parallel, zyklisch, sequenziell)<br />
<br />
Telefonbuch interne oder aus externer Quelle (LDAP) <br />
<br />
Text vor Melden (*) <br />
<br />
Textansagen (*) <br />
<br />
Torsprecheinrichtung mit Toröffnerfunktion (#) <br />
<br />
Twin Phones <br />
<br />
Überlauf von Teilnehmer und Querverbindungen <br />
<br />
Übersiedlung des Terminals <br />
<br />
Übertragung der Rufnummer <br />
<br />
Umschalten auf Tag-/Nachtbetrieb mit Kennziffern von Teilnehmer <br />
<br />
Unterschiedlicher Ruf (extern, intern) <br />
<br />
US-Standard (T1 und CAS) <br />
<br />
Verwaltung über einheitliches Interface <br />
<br />
VoIP-CAPI <br />
<br />
Waiting Queue – call busy Operators / CFU disable Operators <br />
<br />
Zentrales Backup /Firmware update/ Config update<br />
<br />
Zugriff auf die einzelne Vermittlung über Individualnummer <br />
<br />
Zugriff auf die Vermittlung über Gruppennummer <br />
<br />
802.1x <br />
<br />
====Neu in V8====<br />
<br />
Ansage der Warteposition in einer Waiting Queue <br />
<br />
Auslagern von Dialtone (externes Gateway)<br />
<br />
Auslagern von Media Relay (externes Gateway)<br />
<br />
Auslagern von MOH (externes Gateway)<br />
<br />
Customized Visual Appearance (frei gestaltbare Oberfläche)<br />
<br />
Dual Forking (OCS Integration) <br />
<br />
Dynamic PBX (Mehrere PBXen auf einer Device ) Mandanten/PBX Virtualisierung <br />
<br />
Kerberos based Authentication und Cross REALM Authentication<br />
<br />
Message an Gruppe senden <br />
<br />
Mobility (GSM Integration) <br />
- anklopfen <br />
- halten <br />
- vermitteln <br />
- parken <br />
- group pickup <br />
- Gruppen ein-/ausloggen <br />
- mobility ein/aus <br />
- Präsenzstatus setzten <br />
<br />
Presence (SIP, H.323)<br />
<br />
Recording an den ISDN und Analog Interfaces <br />
<br />
Roaming Phone Profiles <br />
<br />
RSTP (Rapid Spanning Tree) <br />
<br />
Rückruf bei frei/besetzt ins ISDN <br />
<br />
SIP error detection (alarm/event updated) <br />
<br />
SIP Federation <br />
<br />
SIP Video multiside support<br />
<br />
====Neu in V9====<br />
<br />
Chef/SekretärIn Erweiterungen<br />
<br />
* SekretärIn kann Rufe mit CLIP von Chef ausführen<br />
<br />
* Chef sieht die Anrufumleitungen der SekretärIn<br />
<br />
* Chef sieht ob SekretärIn an Gruppe an oder abgemeldet ist<br />
<br />
* Chef kann Anklopfschutz der SekretärIn durchbrechen<br />
<br />
UC Client (myPBX) web-basierend sowie Windows Launcher<br />
''Unterstützte Sprachen: Deutsch, Dänisch, Englisch, Estnisch, Finnisch, Französisch, Italienisch, Lettisch, Niederländisch, Norwegisch, Polnisch, Portugiesisch, Spanisch, Tschechisch – weitere Sprachen auf Anfrage.'<br />
<br />
* CTI (Ruf initiieren, Ruf annehmen, beenden, halten,zurückholen, transferieren, parken, 3er Konferenz)<br />
* eigene Rufumleitungen verwalten<br />
* Rufliste<br />
* Präsenz (Eigenen Präsenzstatus verwalten)<br />
* Buddyliste (Kontaktliste - mit Präsenz sowie Ruf Status)<br />
* Chat (Multipartychat)<br />
* Audiokonferenz (via innovaphone Audio Conference Interface)<br />
* Videokonferenz (via Einbindung von Webex oder Microsoft OLM)<br />
* Application sharing (via Einbindung von Webex oder Microsoft OLM)<br />
<br />
Reporting <br />
<br />
* Plattform IP1060, IP3010, IP6010, oder externe Linux Plattform- innovaphone Application Plattform.<br />
* Basierend auf PBX CDR´s<br />
* Vorkonfigurierbare Filter<br />
* Reports (exportierbar als PDF, XML) aus Filter, kombinierbarer Filter, Datum und Zeit<br />
<br />
Import/Export PBX User Datenbank (CSV/XML)<br />
<br />
Individuelle MOH (Kontextbezogen auf Objekt, Node oder PBX)<br />
<br />
IP Filter für Registrierungen mit sowie IP Filter für Registrierungen ohne Passwort<br />
<br />
IPv6 Support (IPv6 Routing, 6to4 Routing, http Zugriff sowie Telnet)<br />
<br />
LDAP über TLS<br />
<br />
MTLS <br />
<br />
Notrufnummern Priorität<br />
<br />
NTP Redundanz<br />
<br />
Partnertasten via mehrere Pbx´en<br />
<br />
Wideband Audio (IP0010, IP1060, IP3010, IP6010)<br />
<br />
Erweitertes Boolean (call forward, filter und diversion filter) nach Datum<br />
<br />
Maximale Gesprächsdauer<br />
<br />
===Features IP-Telefone – IP110 / IP200 / IP230 / IP240 / IP240-1000 / IP241 / IP222 / IP232===<br />
<br />
Alphanumerisches Telefonbuch <br />
<br />
Anklopfen (Signalisieren und Abfrage, visuell und/oder akustisch, Anklopfen aus)<br />
<br />
Anrufschutz <br />
<br />
Anrufübernahme (selektiv, aus Gruppe)<br />
<br />
Anrufumleitung zu externer Rufnummer <br />
<br />
Anrufumleitung zu interner Rufnummer <br />
<br />
Anzeige Gesprächsdauer <br />
<br />
Anzeige Nachricht wartet (MWI) <br />
<br />
Aufschalten <br />
<br />
Automatische Wahlwiederholung <br />
<br />
Automatische Wahlwiederholung auf besetztes Leitungsbündel <br />
<br />
Automatischer Rückruf bei besetzt und frei <br />
<br />
Bevorzugte Teilnehmer <br />
<br />
Chef/Sekretär Einrichtung <br />
<br />
Datum- und Uhrzeit-Anzeige (automatische Sommer-/Winterzeit Anpassung) <br />
<br />
Direktwahl (sofort, intern/extern)<br />
<br />
Durchsage über Lautsprecher <br />
<br />
Einstellbare Klingeltöne sowie RTTTL und Midi Tonrufe <br />
<br />
Erzwungene Durchsage (priority call) <br />
<br />
Feste Anrufumleitung (sofort, nach Zeit (Rufweiterschaltung), bei besetzt)<br />
<br />
Freisprechen<br />
<br />
Funktionstasten (hier ist eine Vielzahl möglich – genaue Auflistung in den technischen Spezifikationen des jeweiligen IP-Phones)<br />
<br />
Identifizierung des Anrufers (Name, Nummer) <br />
<br />
Individuelle Konfiguration <br />
<br />
Individuelles Telefonbuch <br />
<br />
Intercom mit automatischer Rufannahme <br />
<br />
Konferenz (3er) <br />
<br />
Konfiguration der Sprachaufzeichnung via HTTP <br />
<br />
Kopfhörer <br />
<br />
Lauthören <br />
<br />
Lautstärke einstellbar <br />
<br />
Makeln <br />
<br />
Mehrfachkonferenz verkettet und unbegrenzt <br />
<br />
Mehrfachregistrierung mit selektiver Deregistrierung <br />
<br />
Mehrsprachig <br />
<br />
Messaging <br />
<br />
Multiprotokollfähig (SIP und H.323 gleichzeitig), Mehrfachregistrierung <br />
<br />
Namenswahl <br />
<br />
Parken von Gesprächen und Abfrage von anderen Teilnehmern<br />
<br />
Projektcode <br />
<br />
Rückruf löschen <br />
<br />
Rufaufschalten – Intrusion Call <br />
<br />
Ruflisten (ankommend, abgehend, nicht erreicht, nicht beantwortet)<br />
<br />
Silent Intrusion <br />
<br />
SIP via TCP <br />
<br />
SIPS (Secure SIP via TCP/TLS) <br />
<br />
SRTP (SIP, H.323)<br />
<br />
Statusanzeige von Teilnehmer (frei, besetzt, Ruf) <br />
<br />
Stummschaltung <br />
<br />
Teilnehmer mit mehreren Leitungen <br />
<br />
Teilnehmer mit mehreren Rufnummern <br />
<br />
Telefon sperren <br />
<br />
Übersiedlung des Terminals <br />
<br />
Variable Anrufumleitung <br />
<br />
Variable Anrufumleitung löschen <br />
<br />
Verbinden auf freien und besetzten Teilnehmer ohne Ankündigung <br />
<br />
Verbinden mit Ankündigung <br />
<br />
Verbinden ohne Melden <br />
<br />
Wahl einer IP-Adresse (mit und ohne RAS) <br />
<br />
Wahl mit Codeschlüssel vom nichtberechtigten Apparat <br />
<br />
Wahlwiederholung der letzten 100 gewählten Nummern <br />
<br />
Wechsel des zugeordneten Partners <br />
<br />
Zähler und Liste versäumter Anrufe <br />
<br />
802.1X<br />
<br />
==== Neu in V9 ====<br />
<br />
Farbdisplay Support (IP241 / IP222 / IP232)<br />
<br />
Individuelles Hintergrundbild (IP241 / IP222 / IP232)<br />
<br />
Konfigurierbarer Ton für automatisches verbunden, Announcement Rufe, Multicast Announcement und Textnachrichten.<br />
<br />
802.3az (IP222 / IP232)<br />
<br />
Wideband Audio (IP222 / IP232)<br />
<br />
===Features analoge Telefone – IP302 / IP22 / IP24 / IP28, DECT-Telefone – IP52 / IP54 / IP55 / IP56 und ISDN Telefon IP800===<br />
<br />
Anklopfen (Signalisierung und Abfrage)<br />
<br />
Anrufschutz <br />
<br />
Anrufübernahme; selektiv und aus Gruppe <br />
<br />
Anrufumleitung zu externer Rufnummer<br />
<br />
Anzeige Nachricht wartet (MWI) für DECT Telefone <br />
<br />
Bevorzugte Teilnehmer<br />
<br />
Clip auf analogen Telefonen<br />
<br />
Direktwahl (sofort, intern/extern)<br />
<br />
Feste Anrufumleitung (sofort, nach Zeit (Rufweiterschaltung), bei besetzt)<br />
<br />
Makeln <br />
<br />
Parken von Gesprächen und Abfrage von anderen Teilnehmern <br />
<br />
Projektcode <br />
<br />
Quittierungston (positiv und negativ) <br />
<br />
Sonderton bei aktiviertem Feature <br />
<br />
Rückruf bei besetzt <br />
<br />
Rückruf bei frei <br />
<br />
Ruhe vor dem Telefon (interne und externe Anrufe)<br />
<br />
SIP via TCP <br />
<br />
SIPS (Secure SIP via TCP/TLS) <br />
<br />
SRTP (SIP and H.323) <br />
<br />
Variable Anrufumleitung <br />
<br />
Variable Anrufumleitung löschen <br />
<br />
Verbinden auf freien und besetzten Teilnehmer ohne Ankündigung <br />
<br />
Verbinden mit Ankündigung <br />
<br />
Wahl mit Codeschlüssel vom nichtberechtigten Apparat <br />
<br />
802.1x<br />
<br />
===Features innovaphone Voicemail (*)===<br />
<br />
<br />
''Unterstützte Sprachen: Deutsch, Englisch, Französisch, Italienisch, Spanisch, Dänisch, Norwegisch, Holländisch, Polnisch, Schwedisch, Tschechisch – weitere Sprachen auf Anfrage.''<br />
''Voicemail läuft auf der Compact Flash (CF Einschub in der IP800, IP305, IP302, IP2000, IP6000, IP1060, IP3010, IP6010) oder auf Web Server''<br />
<br />
Abhören, Löschen und Speichern von Nachrichten über DTMF am Telefon <br />
<br />
Email Versand (mit oder ohne Nachricht) <br />
<br />
MWI (nach H.450.7) <br />
<br />
Personalisierte Begrüßung <br />
<br />
Sprachaufzeichnung<br />
<br />
==== Neu in V9 ====<br />
<br />
Voicemail Support SRTP<br />
<br />
===Features Operator (V8) software based===<br />
<br />
''Sprache: Deutsch, Englisch, Italienisch, Niederländisch – weitere Sprachen auf Anfrage''<br />
<br />
Anzeige der aktuellen Rufe <br />
<br />
Anzeige des Belegtstatus <br />
<br />
Anzeige des Präsenzstatus <br />
<br />
Anzeige von Rufumleitungen <br />
<br />
Besetztlampenfeld (nach Gruppen sortiert) <br />
<br />
Drag&Drop oder per Tastatur <br />
<br />
Integrierte Hilfsfunktion <br />
<br />
Monitoren blind vermittelter Rufe <br />
<br />
Monitoren von Warteschleifen <br />
<br />
Nachtschaltung <br />
<br />
Parken/Entparken <br />
<br />
Rückwärtige Namensauflösung in LDAP Verzeichnissen <br />
<br />
Rufjournal <br />
<br />
Senden von Nachrichten zu PBX Teilnehmern <br />
<br />
Setzen / Ändern von Anrufumleitungen für alle PBX Teilnehmer <br />
<br />
Setzen / Ändern von Präsenzstatus für alle PBX Teilnehmer <br />
<br />
State-of-the-Art User Interface <br />
<br />
Teilnehmersuche in allen PBXen im Verbund <br />
<br />
Teilnehmersuche in LDAP Verzeichnissen <br />
<br />
Unterstützt Master/Slave Szenarien <br />
<br />
Vermitteln (mit/ohne Konsultation (blind)) <br />
<br />
<br />
<br />
===Features Vermittlungsplatz – IP230 / IP240 / IP240-1000/ IP241 / IP222 / IP232===<br />
<br />
''Telefon als standalone Vermittlungsplatz oder in Verbindung mit dem software based Operator''<br />
<br />
Alphanumerisches Telefonbuch <br />
<br />
Anklopfen (Signalisierung und Abfrage, visuell und/oder akustisch, Anklopfen aus)<br />
<br />
Anrufschutz <br />
<br />
Anrufübernahme; selektiv und aus Gruppe <br />
<br />
Anrufumleitung zu externer Rufnummer <br />
<br />
Anrufumleitung zu interner Rufnummer <br />
<br />
Anzeige Gesprächsdauer <br />
<br />
Anzeige Nachricht wartet (MWI) <br />
<br />
Anzeige Rufnummer des Anrufers <br />
<br />
Aufschalten <br />
<br />
Automatische Wahlwiederholung <br />
<br />
Automatische Wahlwiederholung auf besetztes Leitungsbündel <br />
<br />
Automatischer Rückruf bei besetzt und frei <br />
<br />
Bevorzugte Teilnehmer <br />
<br />
Besetztlampenfeld <br />
<br />
Chef/Sekretär Einrichtung <br />
<br />
Datums- und Uhrzeitanzeige (automatische Sommer/Winterzeit Anpassung) <br />
<br />
Direktwahl; sofort, intern/extern <br />
<br />
Drängeanzeige (0-4) <br />
<br />
Durchsage über Lautsprecher <br />
<br />
Einstellbare Klingeltöne sowie RTTTL und Midi Tonrufe <br />
<br />
Erzwungene Durchsage (priority call) <br />
<br />
Feste Anrufumleitung (sofort, nach Zeit (Rufweiterschaltung), bei besetzt) <br />
<br />
Freisprechen <br />
<br />
Funktionstasten- hier ist eine Vielzahl möglich – genaue Auflistung in den technischen Spezifikaztionen des jeweiligen IP-Phones <br />
<br />
Identifizierung des Anrufers (Name/Nummer) <br />
<br />
Individuelle Konfiguration <br />
<br />
Individuelles Telefonbuch <br />
<br />
Intercom mit automatischer Rufannahme <br />
<br />
Konferenz (3er) <br />
<br />
Konfiguration der Sprachaufzeichnung via HTTP <br />
<br />
Kopfhörer mit Protokoll DHSG <br />
<br />
Kopfhörer und Handapparat parallel und unabhängig <br />
<br />
Lauthören <br />
<br />
Makeln <br />
<br />
Mehrere Vermittlungen <br />
<br />
Mehrfachkonferenz verkettet und unbegrenzt <br />
<br />
Mehrfachregistrierung <br />
<br />
Mehrfachregistrierung mit selektiver Deregistrierung <br />
<br />
Mehrsprachig <br />
<br />
Messaging <br />
<br />
Multiprotokollfähig (SIP und H.323 gleichzeitig)<br />
<br />
Namenswahl <br />
<br />
Lautstärke einstellbar <br />
<br />
Parken von Gesprächen und Abfrage von anderen Teilnehmer <br />
<br />
Projektcode <br />
<br />
Rufaufschalten (Call Intrusion)<br />
<br />
Rückruf löschen <br />
<br />
Rückfrage <br />
<br />
Rückfrage auf besetzten Teilnehmer <br />
<br />
Rückruf auf freien/besetzen Teilnehmer <br />
<br />
Rückruf löschen <br />
<br />
Ruflisten; ankommend, abgehend, nicht erreicht, nicht beantwortet <br />
<br />
Silent Intrusion <br />
<br />
SIP via TCP <br />
<br />
SIPS (Secure SIP via TCP/TLS) <br />
<br />
SRTP (SIP and H.323) <br />
<br />
Statusanzeige von Teilnehmer (frei/besetzt/Ruf) <br />
<br />
Stummschaltung <br />
<br />
Teilnehmer mit mehreren Leitungen <br />
<br />
Teilnehmer mit mehreren Rufnummern <br />
<br />
Telefon sperren <br />
<br />
Telefonbuch <br />
<br />
Übersiedlung des Terminals <br />
<br />
Übertragung der Rufnummer <br />
<br />
Umschaltung Tag/Nachbetrieb mit Anzeige des Status <br />
<br />
Unterschiedlicher Ruf extern/intern <br />
<br />
Variable Anrufumleitung <br />
<br />
Variable Anrufumleitung löschen <br />
<br />
Verbinden auf freien und besetzten Teilnehmer ohne Ankündigung <br />
<br />
Verbinden mit Ankündigung <br />
<br />
Verbinden ohne Melden <br />
<br />
Wahl einer IP-Adresse (mit und ohne RAS) <br />
<br />
Wahl mit Codeschlüssel vom nichtberechtigten Apparat <br />
<br />
Wahlwiederholung der letzten 100 gewählten Nummern <br />
<br />
Wechsel des zugeordneten Partners <br />
<br />
Zähler und Liste versäumte Anrufe <br />
<br />
802.1x<br />
<br />
===Features automatische Vermittlung (IVR) (*)===<br />
<br />
Abhören der Menüs auch von internen Teilnehmern<br />
<br />
Ansagen in Abhängigkeit des Anrufers (z.B. automatische oder manuelle Sprachauswahl)<br />
<br />
Mehrstufige Menüs <br />
<br />
Rufbehandlung nach Bündel und/oder rufender Nummer (CLI) <br />
<br />
Sprachmenüs bei Durchwahl (bei nichtmelden, besetzt, weiterschalten) <br />
<br />
Sprachmenüs mit auswählbaren Zielen (vordefiniert) <br />
<br />
Sprachmenüs mit Info und automatischer Wahl <br />
<br />
Sprachmenüs mit manueller Wahl des Ziels (DTMF) <br />
<br />
Überlauf von der Vermittlung zur automatischen Vermittlung <br />
<br />
<br />
<br />
==== Neu in V8 ====<br />
<br />
Ansage der Warteposition in einer Waiting Queue <br />
<br />
<br />
<br />
<br />
<br />
Anmerkung: <br />
<br />
(*) erfordert einen PC mit Windows XP (Web Server) oder via Compact Flash (CF Einschub in der IP800, IP305, IP302, IP2000, IP6000, IP1010, IP3010, IP6010) <br />
<br />
(#) erfordert eine IP21 <br />
<br />
<br />
<br />
[[Category:Faq|{{PAGENAME}}]]</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Howto:Feature_List_in_English&diff=21032Howto:Feature List in English2011-04-28T14:04:27Z<p>Tsr: /* New in V9 */</p>
<hr />
<div>innovaphone feature list<br />
<br />
<!-- featurelist --><br />
==Applies to==<br />
<br />
This information applies to<br />
<br />
− All innovaphone products based on V7, V8 and V9<br />
<br />
<br />
==Download==<br />
<br />
[[Media:innovaphone_V8_Featurelist_en.pdf]]<br />
<br />
==More information==<br />
<br />
<br />
<br />
===System Features – IP302 / IP305 / IP800 / IP2000 / IP6000 /IP1060 / IP3010 / IP6010 / IPVA===<br />
<br />
Access to exchange via group number <br />
<br />
Access to separate exchange via individual number <br />
<br />
ACD groups <br />
<br />
Active Directory Replication <br />
<br />
Administration via uniform interface <br />
<br />
Alarm and error events <br />
<br />
Alternate route selection <br />
<br />
Announcement before pickup (*) <br />
<br />
Announcements (*) <br />
<br />
Authorisation groups (class of service) <br />
<br />
Automatic break through for call protection for preferred numbers <br />
<br />
Automatic call distribution (ACD) <br />
<br />
Automatic night switching with week clock <br />
<br />
Automatic route selection (ARS) <br />
<br />
Bootcode with minifirmware (not supported with IP3000) <br />
<br />
Branches (virtual central PBX) <br />
<br />
Bunched circuit <br />
<br />
Call back <br />
<br />
Call back also if internal call <br />
<br />
Call detail recording (CDR) <br />
<br />
Calling line identification restriction (CLIR) <br />
<br />
Calling party identification (CLIP) <br />
<br />
Calling to E.164 <br />
<br />
Calling via ENUM (H.323 and SIP) <br />
<br />
Call Detail Records (CDR) external and internal <br />
<br />
centralized backup /firmware/config upload<br />
<br />
Circle call with circle call query (#) <br />
<br />
Clock synchronization via IP <br />
<br />
Config templates for PBX User <br />
<br />
Configurable tones <br />
<br />
Configure / change / delete call diversion via web <br />
<br />
Conversation return to operator <br />
<br />
Cross connection via IP <br />
<br />
Cross connection via ISDN <br />
<br />
Different call (external, internal) <br />
<br />
Direct dial (with and without number reassessment) <br />
<br />
Door bell interface with door opener function (#) <br />
<br />
DTMF detection disabling <br />
<br />
DTMF-post dial/direct dial <br />
<br />
Emigration of endpoint <br />
<br />
Enhanced error reporting (SIP, QOS parameter, router error reporting)<br />
<br />
Enhanced H.323 features according to H.450.x <br />
<br />
Extended DTMF Object (feature set via DTMF dial) <br />
<br />
External communication <br />
<br />
Firmware upload in DRAM (not supported with IP3000) <br />
<br />
Floating license model <br />
<br />
Flexible dial plan <br />
<br />
General night switching <br />
<br />
Group call (all, circular)<br />
<br />
Hide Objects from LDAP<br />
<br />
Home office integration <br />
<br />
HTTP/ HTTPS allowed stations<br />
<br />
Incoming direct call to subscriber or group <br />
<br />
Interactive call acceptance (*) <br />
<br />
Interface for external announcement construction (#) <br />
<br />
Internal communication <br />
<br />
Internal music on hold <br />
<br />
Least cost routing (LCR) <br />
<br />
Log forwadring<br />
<br />
LDAP replication<br />
<br />
Message center (H.450.7 or DTMF) <br />
<br />
Message Waiting Indication (MWI) <br />
<br />
Messaging <br />
<br />
Messaging (SIP and H.323) <br />
<br />
Mixed dial method (overlap and en-block dialing) <br />
<br />
MS-chap V1/V2 <br />
<br />
Multi conferencing (IP800, IP6000, IP0010, IP1060, IP3010, IP6010) <br />
<br />
Multi protocol (H.323, SIP) <br />
<br />
Multilevel admin access (detailed multilevel user rights for the PBX configuration) <br />
<br />
Multiple system admin (multiple admin and viewer rights possible for the whole system) <br />
<br />
Multistage login (multi-user) <br />
<br />
Music / announcement in standby from analogue resource (#) <br />
<br />
Music / announcement in standby from HTTP resource (*) <br />
<br />
Network wide features (Master/slave with virtual PBX) <br />
<br />
Only calling to registered subscribers (passive control) <br />
<br />
Overflow of subscribers and cross connection <br />
<br />
Overlapped sending <br />
<br />
PBX directory search (LDAP search via DTMF) <br />
<br />
Phonebook either from internal or from external source (LDAP) <br />
<br />
QSIG <br />
<br />
QSIG inter-working <br />
<br />
QSIG trunking (point to point and point to multipoint) <br />
<br />
Redundancy of the ISDN-lines <br />
<br />
Redundancy of the PBX <br />
<br />
Remote monitoring and remote diagnostics <br />
<br />
Remote software upgrade <br />
<br />
RTP Proxy <br />
<br />
SDP Transit (for video and other codecs) <br />
<br />
Short dial (individual, group, system wide) <br />
<br />
Silent intrusion <br />
<br />
SIP Medial Relay (RTP stream routing via gateway) <br />
<br />
SIP trunking <br />
<br />
SIP via TCP<br />
<br />
SIPS (SIP-Secure) – SIP via TCP/TLS (not supported with IP3000) <br />
<br />
SNMP Traps (alarm events) <br />
<br />
SOAP-API <br />
<br />
SRTP (Voice encryption) for H.323 and SIP (not supported with IP3000) <br />
<br />
Subscriber authorisation<br />
<br />
Standard protocols to the endpoint <br />
<br />
Subscriber groups with progressive call (parallel, circular, sequential)<br />
<br />
Switch between day/night with code digit from subscribers <br />
<br />
System time/date via timeserver (LAN or web) <br />
<br />
TAPI / Multi line TAPI (via several PBX’s / locations)<br />
<br />
Telephone number assignment <br />
<br />
Time based subscriber authorisation<br />
<br />
Twin Phones <br />
<br />
US standard (T1 and CAS) <br />
<br />
VoIP-CAPI<br />
<br />
Waiting queue – call busy operators / CFU disable operators <br />
<br />
802.1x<br />
<br />
==== New in V8 ====<br />
<br />
Announcing the queue position in a waiting queue <br />
<br />
Callback on busy/free to ISDN <br />
<br />
Customized Visual Appearance (individually designable user interface)<br />
<br />
Dual Forking (OCS Integration) <br />
<br />
Dynamic PBX (more PBXs on one Device ) PBX hosting / PBX virtualization <br />
<br />
Kerberos based authentication and Cross Realm authentication<br />
<br />
Mobility (GSM integration) <br />
- Call-waiting <br />
- hold <br />
- transfer <br />
- park <br />
- group login/logout <br />
- mobility on/off <br />
- setting presence status <br />
<br />
Off load Dialtone (external gateway)<br />
<br />
Off load Media Relay (external gateway) <br />
<br />
Off load MOH (external gateway)<br />
<br />
Presence <br />
<br />
Recording at the ISDN and analogue interfaces <br />
<br />
Roaming Phone Profiles <br />
<br />
RSTP (Rapid Spanning Tree) <br />
<br />
Send Message to group <br />
<br />
SIP error detection (alarm/event updated) <br />
<br />
SIP Federation <br />
<br />
SIP video multisite support<br />
<br />
====New in V9====<br />
<br />
Executive/secretary enhancements<br />
<br />
* Secretary can initiate calls with the CLIP from the executive. <br />
<br />
* Executive can see if the secretary is joined or unjoined in the primary secretary group. <br />
<br />
* Executive sees if a call diversion is set at the secretary.<br />
<br />
* Breakthrough disabled call waiting at secretary.<br />
<br />
Reporting <br />
<br />
* Based on plattform IP1060, IP3010, IP6010, or external Linux platform- innovaphone Application platform.<br />
* Based on PBX CDR´s<br />
* Predefined filter<br />
* Reports (export as PDF, XML) from filter, combined filter, date and time<br />
<br />
UC client (myPBX) web-based and Windows launcher<br />
<br />
''Languages supported: Danish / English / Estonian / Finnish / French / Italian / Latvian / Dutch / Norwegian / Polish / Portuguese / Spanish / Swedish / Czech – additional languages on demand.''<br />
<br />
* CTI (initiate call, accept call, terminate call, hold call, retrieve call, transfer call, park call, 3PTY conference)<br />
* Manage own call diversions<br />
* Call list<br />
* Presence (manage own presence state)<br />
* Buddylist (including partners presence and call status)<br />
* Chat (multiparty chat)<br />
* Audioconference (via innovaphone audio conference Interface)<br />
* Videoconferece (via integration of Webex or Microsoft OLM)<br />
* Application sharing (via integration of Webex or Microsoft OLM)<br />
<br />
Emergency calls priority<br />
<br />
Import/Export PBX user database (CSV/XML)<br />
<br />
Individual MOH (context sensitive based on object, node or PBX)<br />
<br />
IP filter for registrations with or without password <br />
<br />
IPv6 support (IPv6 routing, 6to4 routing and http access, telnet)<br />
<br />
LDAP via TLS<br />
<br />
MTLS <br />
<br />
NTP redundancy<br />
<br />
Partnerkeys via separate Pbx´s<br />
<br />
Wideband audio (IP0010, IP1060, IP3010, IP6010)<br />
<br />
Enhanced Boolean (call forward, filter and diversion filter) based also on date <br />
<br />
Maximum call duration<br />
<br />
===Features IP Phones – IP110 / IP200 / IP230 / IP240 / IP240-1000 / IP241 / IP222 / IP232===<br />
<br />
Adjustable loudness <br />
<br />
Adjustable ringing tones also possible, import RTTTL and midi files <br />
<br />
Alphanumeric phonebook <br />
<br />
Announcement via loudspeaker <br />
<br />
Automatic callback on busy and free <br />
<br />
Automatic redialing <br />
<br />
Automatic redialing to busy bunched circuit <br />
<br />
Blind transfer <br />
<br />
Call diversion to internal phone number <br />
<br />
Call hold / retrieve call diversion to external phone number <br />
<br />
Call intrusion <br />
<br />
Call list (outgoing, incoming, combined, not reached, not answered)<br />
<br />
Call park and enquiry from other subscribers <br />
<br />
Call prevention <br />
<br />
Call transfer / pickup (selective and from a group)<br />
<br />
Call waiting (acoustical and optical signaling of waiting calls)<br />
<br />
Caller identification (name/number) <br />
<br />
Changeover of the assigned partners <br />
<br />
Conference (3 way) <br />
<br />
Configuration of the voice recording via HTTP<br />
<br />
Connect to busy and free subscribers without notification <br />
<br />
Counter and list of missed calls <br />
<br />
Date and time display (automatic summer/winter time adjustment) <br />
<br />
Delete call back <br />
<br />
Delete variable call diversion <br />
<br />
Dialing an IP address (with and without RAS) <br />
<br />
Dialing with code key from an unauthorized phone <br />
<br />
Direct dialing (immediate, internal/external)<br />
<br />
Display duration of call <br />
<br />
Display calling number <br />
<br />
Emigration of subscriber/endpoint <br />
<br />
Fixed call diversion (unconditional, no answer (time adjustable) on busy)<br />
<br />
Forced announcement (priority call) <br />
<br />
Function keys – multitude possible – exact list can be found in the technical specification of each IP phone <br />
<br />
Hands free <br />
<br />
Headset <br />
<br />
Individual configuration <br />
<br />
Individual phonebook <br />
<br />
Intercom with automatic call pick up <br />
<br />
Interlinked and limitless multiple conference <br />
<br />
Manager/assistant feature <br />
<br />
Message waiting indication (MWI) <br />
<br />
Messaging <br />
<br />
Multi language <br />
<br />
Multi-protocol and multi-registration (SIP and H.323 concurrent)<br />
<br />
Multiple registrations with selective de-registration <br />
<br />
Mute (switch off the microphone) <br />
<br />
Name dialing <br />
<br />
Open listening <br />
<br />
Over plugging (connect call to a busy subscriber) <br />
<br />
Phone lock <br />
<br />
Preferred subscribers <br />
<br />
Project code <br />
<br />
Redialing of the last 100 dialed numbers <br />
<br />
Silent Intrusion <br />
<br />
SIP via TCP <br />
<br />
SIPS (Secure SIP via TCP/TLS) <br />
<br />
SRTP (SIP and H.323) <br />
<br />
Status indication of the subscriber (free/busy/call) <br />
<br />
Subscriber with several lines <br />
<br />
Subscriber with several numbers <br />
<br />
Transfer with consultation <br />
<br />
Variable call diversion <br />
<br />
802.1x<br />
<br />
==== New in V9 ====<br />
<br />
Colour display (IP241 / IP222 / IP232)<br />
<br />
Individual background picture (IP241 / IP222 / IP232)<br />
<br />
Individual audible signal for announcement calls /multicast announcements and messaging<br />
<br />
802.3az (IP222 / IP232)<br />
<br />
Wideband audio (IP222 / IP232)<br />
<br />
===Features: Analogue phones – IP302 / IP22 / IP24 / IP28, DECT phones – IP52 / IP54 / IP55 / IP65, ISDN phone – IP800===<br />
<br />
Call completion on busy <br />
<br />
Call completion on free <br />
<br />
Call diversion to internal/external number <br />
<br />
Call hold/retrieve <br />
<br />
Call park and enquiry from other subscribers <br />
<br />
Call protection <br />
<br />
Call transfer/pickup (selective and from a group)<br />
<br />
Call waiting (acoustic and optical signal of the waiting call)<br />
<br />
Clip to an analogue phone <br />
<br />
Confirmation tone (positive and negative) <br />
<br />
Connect to a free and busy subscriber without notification <br />
<br />
Delete variable call diversion <br />
<br />
Dial with code key from an unauthorized phone <br />
<br />
Direct dial immediate (internal, external)<br />
<br />
Do not disturb (internal and external calls)<br />
<br />
Fixed call diversion; unconditional, no answer (time adjustable), on busy <br />
<br />
Lock phone <br />
<br />
Message Waiting Indication (MWI) on DECT Phones<br />
<br />
Preferred subscriber <br />
<br />
Project code <br />
<br />
SIP via TCP <br />
<br />
SIPS (Secure SIP via TCP/TLS) <br />
<br />
Special tone when active feature <br />
<br />
SRTP (SIP and H.323) <br />
<br />
Transfer with consultation <br />
<br />
Variable call diversion <br />
<br />
802.1x<br />
<br />
===Features innovaphone Voice mail (*)===<br />
<br />
''Languages supported: German / English / Italian / French / Dutch / Spanish / Norwegian / Danish / Polish /Swedish / Czech – additional languages on demand.''<br />
''Voicemail runs on Compact Flash (CF slot in IP800, IP305, IP302, IP2000, IP6000, IP1060, IP3010, IP6010) or on external Web Server''<br />
<br />
Email notification (with or without attachment) <br />
<br />
Listen to/delete /store voice mails by means of DTMF input <br />
<br />
MWI (according to H.450.7) <br />
<br />
Personal greeting message <br />
<br />
Voice recording <br />
<br />
==== New in V9 ====<br />
<br />
Voicemail support SRTP<br />
<br />
===Features Operator (V8) software based===<br />
<br />
''Localized versions: German / English / Italian / Dutch – additional languages on demand''<br />
<br />
Busylampfield (divided into groups) <br />
<br />
Call journal <br />
<br />
Call transfer (with/without consultation (blind)) <br />
<br />
Drag&Drop or with keypad use <br />
<br />
Integrated help <br />
<br />
Monitor blind transferred calls <br />
<br />
Monitor of waiting queue <br />
<br />
Name display for incoming calls in LDAP directory <br />
<br />
Park/unpark <br />
<br />
Send messages to PBX users <br />
<br />
Searching within a LDAP directory <br />
<br />
Searching for PBX users in all PBX´s <br />
<br />
Set/change call forward for all PBX users <br />
<br />
Set/change presence status for all PBX users <br />
<br />
Show busy state <br />
<br />
Show call forward <br />
<br />
Show current call<br />
<br />
Show presence status <br />
<br />
State-of-the-art user interface <br />
<br />
Support of Master/Slave scenarios<br />
<br />
===Features Operator Phone – IP230 / IP240 / IP240-1000 / IP241 / IP222 / IP232===<br />
<br />
''Phone can be used as standalone Operator or in combination with the software based Operator''<br />
<br />
Adjustable volume <br />
<br />
Adjustable ringing tones also possible, import RTTTL and midi files<br />
<br />
Alphanumeric phonebook <br />
<br />
Announcement via loudspeaker <br />
<br />
Automatic callback on busy and free <br />
<br />
Automatic redialing <br />
<br />
Automatic redialing to busy bunched circuit <br />
<br />
Blind transfer <br />
<br />
Busy indicator lamp <br />
<br />
Call back (enquiry) <br />
<br />
Call back delete <br />
<br />
Call back on busy subscriber <br />
<br />
Call back to free/busy subscriber <br />
<br />
Call diversion to external phone number <br />
<br />
Call diversion to internal phone number <br />
<br />
Call hold/retrieve <br />
<br />
Call intrusion <br />
<br />
Call list (outgoing, incoming, not reached, not answered)<br />
<br />
Call parking and enquiry from other subscribers <br />
<br />
Call prevention <br />
<br />
Call transfer/pickup (selective and from a group)<br />
<br />
Call waiting (acoustical and optical signaling of waiting calls)<br />
<br />
Changeover day/night with status on phone display <br />
<br />
Changeover of the assigned partner <br />
<br />
Conference (3 way) <br />
<br />
Configuration of the Voice recording via HTTP <br />
<br />
Connect to busy and free subscribers without notification <br />
<br />
Date and time on display (automatic summer/winter time adjustment) <br />
<br />
Delete variable call diversion <br />
<br />
Dialing an IP address (with and without RAS) <br />
<br />
Dialing with code key from an unauthorised phone <br />
<br />
Different ringing tones (internal/external) <br />
<br />
Direct dialing; immediate internal/external <br />
<br />
Display duration of call <br />
<br />
Display calling number <br />
<br />
Emigration of the subscriber/endpoint <br />
<br />
Fixed call diversion; unconditional, no answer (time adjustable) on busy <br />
<br />
Forced announcement (priority call) <br />
<br />
Function keys – multitude possible – exact list can be found in the technical specification of each IP phone <br />
<br />
Hands free <br />
<br />
Headset protocol DHSG <br />
<br />
Headset and handset parallel and autonomous <br />
<br />
Identification of the caller (name/number) <br />
<br />
Individual configuration <br />
<br />
Individual phonebook <br />
<br />
Intercom with automatic call acceptance <br />
<br />
Manager/assistant feature <br />
<br />
Message waiting indication (MWI) <br />
<br />
Messaging <br />
<br />
Multi language <br />
<br />
Multi protocol and multi-registration (SIP and H.323 concurrent) <br />
<br />
Multiple conference interlinked and limitless <br />
<br />
Multiple operators <br />
<br />
Multiple registrations with selective de-registration <br />
<br />
Mute (switch off the microphone) <br />
<br />
Name dialing <br />
<br />
Open listening <br />
<br />
Over plugging (connect call to a busy subscriber) <br />
<br />
Phone lock <br />
<br />
Preferred subscriber <br />
<br />
Project code<br />
<br />
Redialing of the last 100 dialed numbers <br />
<br />
Rush display (0-4) <br />
<br />
Silent Intrusion <br />
<br />
SIP via TCP <br />
<br />
SIPS (Secure SIP via TCP/TLS) <br />
<br />
SRTP (SIP and H.323) <br />
<br />
Status indication of the subscriber (free, busy, call) <br />
<br />
Subscriber with several lines <br />
<br />
Subscriber with several numbers <br />
<br />
Telephone book <br />
<br />
Transfer of the subscriber phone number <br />
<br />
Transfer with consultation <br />
<br />
Variable call diversion <br />
<br />
802.1x<br />
<br />
===Features Interactive Voice Response (IVR) (*)===<br />
<br />
Announcements depending on the caller (e.g. automatic or manual language selection) <br />
<br />
Call handling according to lines and/or calling number (CLI)<br />
<br />
Listen to the menu also from internal subscribers <br />
<br />
Multi level menu <br />
<br />
Overflow from the operator to an automatic operator <br />
<br />
Voice menu at extension (if no answer, busy, unconditional) <br />
<br />
Voice menu with information and automatic dialing <br />
<br />
Voice menu with predefined destinations <br />
<br />
Voice menu with manual dialing of the destination (DTMF) <br />
<br />
<br />
==== New in V8====<br />
<br />
Announcing the queue position in a waiting queue <br />
<br />
<br />
<br />
<br />
Note: <br />
<br />
(*) PC with WIN XP (web server) required or via Compact Flash (CF slot in IP800, IP305, IP302, IP2000, IP6000) <br />
<br />
(#) innovaphone IP21 required <br />
<br />
<br />
<br />
<br />
[[Category:News|{{PAGENAME}}]]</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Howto:Feature_List_in_English&diff=21031Howto:Feature List in English2011-04-28T14:04:17Z<p>Tsr: /* New in V9 */</p>
<hr />
<div>innovaphone feature list<br />
<br />
<!-- featurelist --><br />
==Applies to==<br />
<br />
This information applies to<br />
<br />
− All innovaphone products based on V7, V8 and V9<br />
<br />
<br />
==Download==<br />
<br />
[[Media:innovaphone_V8_Featurelist_en.pdf]]<br />
<br />
==More information==<br />
<br />
<br />
<br />
===System Features – IP302 / IP305 / IP800 / IP2000 / IP6000 /IP1060 / IP3010 / IP6010 / IPVA===<br />
<br />
Access to exchange via group number <br />
<br />
Access to separate exchange via individual number <br />
<br />
ACD groups <br />
<br />
Active Directory Replication <br />
<br />
Administration via uniform interface <br />
<br />
Alarm and error events <br />
<br />
Alternate route selection <br />
<br />
Announcement before pickup (*) <br />
<br />
Announcements (*) <br />
<br />
Authorisation groups (class of service) <br />
<br />
Automatic break through for call protection for preferred numbers <br />
<br />
Automatic call distribution (ACD) <br />
<br />
Automatic night switching with week clock <br />
<br />
Automatic route selection (ARS) <br />
<br />
Bootcode with minifirmware (not supported with IP3000) <br />
<br />
Branches (virtual central PBX) <br />
<br />
Bunched circuit <br />
<br />
Call back <br />
<br />
Call back also if internal call <br />
<br />
Call detail recording (CDR) <br />
<br />
Calling line identification restriction (CLIR) <br />
<br />
Calling party identification (CLIP) <br />
<br />
Calling to E.164 <br />
<br />
Calling via ENUM (H.323 and SIP) <br />
<br />
Call Detail Records (CDR) external and internal <br />
<br />
centralized backup /firmware/config upload<br />
<br />
Circle call with circle call query (#) <br />
<br />
Clock synchronization via IP <br />
<br />
Config templates for PBX User <br />
<br />
Configurable tones <br />
<br />
Configure / change / delete call diversion via web <br />
<br />
Conversation return to operator <br />
<br />
Cross connection via IP <br />
<br />
Cross connection via ISDN <br />
<br />
Different call (external, internal) <br />
<br />
Direct dial (with and without number reassessment) <br />
<br />
Door bell interface with door opener function (#) <br />
<br />
DTMF detection disabling <br />
<br />
DTMF-post dial/direct dial <br />
<br />
Emigration of endpoint <br />
<br />
Enhanced error reporting (SIP, QOS parameter, router error reporting)<br />
<br />
Enhanced H.323 features according to H.450.x <br />
<br />
Extended DTMF Object (feature set via DTMF dial) <br />
<br />
External communication <br />
<br />
Firmware upload in DRAM (not supported with IP3000) <br />
<br />
Floating license model <br />
<br />
Flexible dial plan <br />
<br />
General night switching <br />
<br />
Group call (all, circular)<br />
<br />
Hide Objects from LDAP<br />
<br />
Home office integration <br />
<br />
HTTP/ HTTPS allowed stations<br />
<br />
Incoming direct call to subscriber or group <br />
<br />
Interactive call acceptance (*) <br />
<br />
Interface for external announcement construction (#) <br />
<br />
Internal communication <br />
<br />
Internal music on hold <br />
<br />
Least cost routing (LCR) <br />
<br />
Log forwadring<br />
<br />
LDAP replication<br />
<br />
Message center (H.450.7 or DTMF) <br />
<br />
Message Waiting Indication (MWI) <br />
<br />
Messaging <br />
<br />
Messaging (SIP and H.323) <br />
<br />
Mixed dial method (overlap and en-block dialing) <br />
<br />
MS-chap V1/V2 <br />
<br />
Multi conferencing (IP800, IP6000, IP0010, IP1060, IP3010, IP6010) <br />
<br />
Multi protocol (H.323, SIP) <br />
<br />
Multilevel admin access (detailed multilevel user rights for the PBX configuration) <br />
<br />
Multiple system admin (multiple admin and viewer rights possible for the whole system) <br />
<br />
Multistage login (multi-user) <br />
<br />
Music / announcement in standby from analogue resource (#) <br />
<br />
Music / announcement in standby from HTTP resource (*) <br />
<br />
Network wide features (Master/slave with virtual PBX) <br />
<br />
Only calling to registered subscribers (passive control) <br />
<br />
Overflow of subscribers and cross connection <br />
<br />
Overlapped sending <br />
<br />
PBX directory search (LDAP search via DTMF) <br />
<br />
Phonebook either from internal or from external source (LDAP) <br />
<br />
QSIG <br />
<br />
QSIG inter-working <br />
<br />
QSIG trunking (point to point and point to multipoint) <br />
<br />
Redundancy of the ISDN-lines <br />
<br />
Redundancy of the PBX <br />
<br />
Remote monitoring and remote diagnostics <br />
<br />
Remote software upgrade <br />
<br />
RTP Proxy <br />
<br />
SDP Transit (for video and other codecs) <br />
<br />
Short dial (individual, group, system wide) <br />
<br />
Silent intrusion <br />
<br />
SIP Medial Relay (RTP stream routing via gateway) <br />
<br />
SIP trunking <br />
<br />
SIP via TCP<br />
<br />
SIPS (SIP-Secure) – SIP via TCP/TLS (not supported with IP3000) <br />
<br />
SNMP Traps (alarm events) <br />
<br />
SOAP-API <br />
<br />
SRTP (Voice encryption) for H.323 and SIP (not supported with IP3000) <br />
<br />
Subscriber authorisation<br />
<br />
Standard protocols to the endpoint <br />
<br />
Subscriber groups with progressive call (parallel, circular, sequential)<br />
<br />
Switch between day/night with code digit from subscribers <br />
<br />
System time/date via timeserver (LAN or web) <br />
<br />
TAPI / Multi line TAPI (via several PBX’s / locations)<br />
<br />
Telephone number assignment <br />
<br />
Time based subscriber authorisation<br />
<br />
Twin Phones <br />
<br />
US standard (T1 and CAS) <br />
<br />
VoIP-CAPI<br />
<br />
Waiting queue – call busy operators / CFU disable operators <br />
<br />
802.1x<br />
<br />
==== New in V8 ====<br />
<br />
Announcing the queue position in a waiting queue <br />
<br />
Callback on busy/free to ISDN <br />
<br />
Customized Visual Appearance (individually designable user interface)<br />
<br />
Dual Forking (OCS Integration) <br />
<br />
Dynamic PBX (more PBXs on one Device ) PBX hosting / PBX virtualization <br />
<br />
Kerberos based authentication and Cross Realm authentication<br />
<br />
Mobility (GSM integration) <br />
- Call-waiting <br />
- hold <br />
- transfer <br />
- park <br />
- group login/logout <br />
- mobility on/off <br />
- setting presence status <br />
<br />
Off load Dialtone (external gateway)<br />
<br />
Off load Media Relay (external gateway) <br />
<br />
Off load MOH (external gateway)<br />
<br />
Presence <br />
<br />
Recording at the ISDN and analogue interfaces <br />
<br />
Roaming Phone Profiles <br />
<br />
RSTP (Rapid Spanning Tree) <br />
<br />
Send Message to group <br />
<br />
SIP error detection (alarm/event updated) <br />
<br />
SIP Federation <br />
<br />
SIP video multisite support<br />
<br />
====New in V9====<br />
<br />
Executive/secretary enhancements<br />
<br />
* Secretary can initiate calls with the CLIP from the executive. <br />
<br />
* Executive can see if the secretary is joined or unjoined in the primary secretary group. <br />
<br />
* Executive sees if a call diversion is set at the secretary.<br />
<br />
* Breakthrough disabled call waiting at secretary.<br />
<br />
Reporting <br />
<br />
* Based on plattform IP1060, IP3010, IP6010, or external Linux platform- innovaphone Application platform.<br />
* Based on PBX CDR´s<br />
* Predefined filter<br />
* Reports (export as PDF, XML) from filter, combined filter, date and time<br />
<br />
UC client (myPBX) web-based and Windows launcher<br />
<br />
''Languages supported: Danish / English / Estonian / Finnish / French / Italian / Latvian / Dutch / Norwegian / Polish / Portuguese / Spanish / Swedish / Czech – additional languages on demand.''<br />
<br />
* CTI (initiate call, accept call, terminate call, hold call, retrieve call, transfer call, park call, 3PTY conference)<br />
* Manage own call diversions<br />
* Call list<br />
* Presence (manage own presence state)<br />
* Buddylist (including partners presence and call status)<br />
* Chat (multiparty chat)<br />
* Audioconference (via innovaphone audio conference Interface)<br />
* Videoconferece (via integration of Webex or Microsoft OLM)<br />
* Application sharing (via integration of Webex or Microsoft OLM)<br />
<br />
Emergency calls priority<br />
<br />
Import/Export PBX user database (CSV/XML)<br />
<br />
Individual MOH (context sensitive based on object, node or PBX)<br />
<br />
IP filter for registrations with or without password <br />
<br />
IPv6 support (IPv6 routing, 6to4 routing and http access, telnet)<br />
<br />
LDAP via TLS<br />
<br />
MTLS <br />
<br />
NTP redundancy<br />
<br />
Partnerkeys via separate Pbx´s<br />
<br />
Wideband audio (IP0010, IP1060, IP3010, IP6010)<br />
<br />
Enhanced Boolean (call forward, filter and diversion filter) based also on date <br />
<br />
Maxim call duration<br />
<br />
===Features IP Phones – IP110 / IP200 / IP230 / IP240 / IP240-1000 / IP241 / IP222 / IP232===<br />
<br />
Adjustable loudness <br />
<br />
Adjustable ringing tones also possible, import RTTTL and midi files <br />
<br />
Alphanumeric phonebook <br />
<br />
Announcement via loudspeaker <br />
<br />
Automatic callback on busy and free <br />
<br />
Automatic redialing <br />
<br />
Automatic redialing to busy bunched circuit <br />
<br />
Blind transfer <br />
<br />
Call diversion to internal phone number <br />
<br />
Call hold / retrieve call diversion to external phone number <br />
<br />
Call intrusion <br />
<br />
Call list (outgoing, incoming, combined, not reached, not answered)<br />
<br />
Call park and enquiry from other subscribers <br />
<br />
Call prevention <br />
<br />
Call transfer / pickup (selective and from a group)<br />
<br />
Call waiting (acoustical and optical signaling of waiting calls)<br />
<br />
Caller identification (name/number) <br />
<br />
Changeover of the assigned partners <br />
<br />
Conference (3 way) <br />
<br />
Configuration of the voice recording via HTTP<br />
<br />
Connect to busy and free subscribers without notification <br />
<br />
Counter and list of missed calls <br />
<br />
Date and time display (automatic summer/winter time adjustment) <br />
<br />
Delete call back <br />
<br />
Delete variable call diversion <br />
<br />
Dialing an IP address (with and without RAS) <br />
<br />
Dialing with code key from an unauthorized phone <br />
<br />
Direct dialing (immediate, internal/external)<br />
<br />
Display duration of call <br />
<br />
Display calling number <br />
<br />
Emigration of subscriber/endpoint <br />
<br />
Fixed call diversion (unconditional, no answer (time adjustable) on busy)<br />
<br />
Forced announcement (priority call) <br />
<br />
Function keys – multitude possible – exact list can be found in the technical specification of each IP phone <br />
<br />
Hands free <br />
<br />
Headset <br />
<br />
Individual configuration <br />
<br />
Individual phonebook <br />
<br />
Intercom with automatic call pick up <br />
<br />
Interlinked and limitless multiple conference <br />
<br />
Manager/assistant feature <br />
<br />
Message waiting indication (MWI) <br />
<br />
Messaging <br />
<br />
Multi language <br />
<br />
Multi-protocol and multi-registration (SIP and H.323 concurrent)<br />
<br />
Multiple registrations with selective de-registration <br />
<br />
Mute (switch off the microphone) <br />
<br />
Name dialing <br />
<br />
Open listening <br />
<br />
Over plugging (connect call to a busy subscriber) <br />
<br />
Phone lock <br />
<br />
Preferred subscribers <br />
<br />
Project code <br />
<br />
Redialing of the last 100 dialed numbers <br />
<br />
Silent Intrusion <br />
<br />
SIP via TCP <br />
<br />
SIPS (Secure SIP via TCP/TLS) <br />
<br />
SRTP (SIP and H.323) <br />
<br />
Status indication of the subscriber (free/busy/call) <br />
<br />
Subscriber with several lines <br />
<br />
Subscriber with several numbers <br />
<br />
Transfer with consultation <br />
<br />
Variable call diversion <br />
<br />
802.1x<br />
<br />
==== New in V9 ====<br />
<br />
Colour display (IP241 / IP222 / IP232)<br />
<br />
Individual background picture (IP241 / IP222 / IP232)<br />
<br />
Individual audible signal for announcement calls /multicast announcements and messaging<br />
<br />
802.3az (IP222 / IP232)<br />
<br />
Wideband audio (IP222 / IP232)<br />
<br />
===Features: Analogue phones – IP302 / IP22 / IP24 / IP28, DECT phones – IP52 / IP54 / IP55 / IP65, ISDN phone – IP800===<br />
<br />
Call completion on busy <br />
<br />
Call completion on free <br />
<br />
Call diversion to internal/external number <br />
<br />
Call hold/retrieve <br />
<br />
Call park and enquiry from other subscribers <br />
<br />
Call protection <br />
<br />
Call transfer/pickup (selective and from a group)<br />
<br />
Call waiting (acoustic and optical signal of the waiting call)<br />
<br />
Clip to an analogue phone <br />
<br />
Confirmation tone (positive and negative) <br />
<br />
Connect to a free and busy subscriber without notification <br />
<br />
Delete variable call diversion <br />
<br />
Dial with code key from an unauthorized phone <br />
<br />
Direct dial immediate (internal, external)<br />
<br />
Do not disturb (internal and external calls)<br />
<br />
Fixed call diversion; unconditional, no answer (time adjustable), on busy <br />
<br />
Lock phone <br />
<br />
Message Waiting Indication (MWI) on DECT Phones<br />
<br />
Preferred subscriber <br />
<br />
Project code <br />
<br />
SIP via TCP <br />
<br />
SIPS (Secure SIP via TCP/TLS) <br />
<br />
Special tone when active feature <br />
<br />
SRTP (SIP and H.323) <br />
<br />
Transfer with consultation <br />
<br />
Variable call diversion <br />
<br />
802.1x<br />
<br />
===Features innovaphone Voice mail (*)===<br />
<br />
''Languages supported: German / English / Italian / French / Dutch / Spanish / Norwegian / Danish / Polish /Swedish / Czech – additional languages on demand.''<br />
''Voicemail runs on Compact Flash (CF slot in IP800, IP305, IP302, IP2000, IP6000, IP1060, IP3010, IP6010) or on external Web Server''<br />
<br />
Email notification (with or without attachment) <br />
<br />
Listen to/delete /store voice mails by means of DTMF input <br />
<br />
MWI (according to H.450.7) <br />
<br />
Personal greeting message <br />
<br />
Voice recording <br />
<br />
==== New in V9 ====<br />
<br />
Voicemail support SRTP<br />
<br />
===Features Operator (V8) software based===<br />
<br />
''Localized versions: German / English / Italian / Dutch – additional languages on demand''<br />
<br />
Busylampfield (divided into groups) <br />
<br />
Call journal <br />
<br />
Call transfer (with/without consultation (blind)) <br />
<br />
Drag&Drop or with keypad use <br />
<br />
Integrated help <br />
<br />
Monitor blind transferred calls <br />
<br />
Monitor of waiting queue <br />
<br />
Name display for incoming calls in LDAP directory <br />
<br />
Park/unpark <br />
<br />
Send messages to PBX users <br />
<br />
Searching within a LDAP directory <br />
<br />
Searching for PBX users in all PBX´s <br />
<br />
Set/change call forward for all PBX users <br />
<br />
Set/change presence status for all PBX users <br />
<br />
Show busy state <br />
<br />
Show call forward <br />
<br />
Show current call<br />
<br />
Show presence status <br />
<br />
State-of-the-art user interface <br />
<br />
Support of Master/Slave scenarios<br />
<br />
===Features Operator Phone – IP230 / IP240 / IP240-1000 / IP241 / IP222 / IP232===<br />
<br />
''Phone can be used as standalone Operator or in combination with the software based Operator''<br />
<br />
Adjustable volume <br />
<br />
Adjustable ringing tones also possible, import RTTTL and midi files<br />
<br />
Alphanumeric phonebook <br />
<br />
Announcement via loudspeaker <br />
<br />
Automatic callback on busy and free <br />
<br />
Automatic redialing <br />
<br />
Automatic redialing to busy bunched circuit <br />
<br />
Blind transfer <br />
<br />
Busy indicator lamp <br />
<br />
Call back (enquiry) <br />
<br />
Call back delete <br />
<br />
Call back on busy subscriber <br />
<br />
Call back to free/busy subscriber <br />
<br />
Call diversion to external phone number <br />
<br />
Call diversion to internal phone number <br />
<br />
Call hold/retrieve <br />
<br />
Call intrusion <br />
<br />
Call list (outgoing, incoming, not reached, not answered)<br />
<br />
Call parking and enquiry from other subscribers <br />
<br />
Call prevention <br />
<br />
Call transfer/pickup (selective and from a group)<br />
<br />
Call waiting (acoustical and optical signaling of waiting calls)<br />
<br />
Changeover day/night with status on phone display <br />
<br />
Changeover of the assigned partner <br />
<br />
Conference (3 way) <br />
<br />
Configuration of the Voice recording via HTTP <br />
<br />
Connect to busy and free subscribers without notification <br />
<br />
Date and time on display (automatic summer/winter time adjustment) <br />
<br />
Delete variable call diversion <br />
<br />
Dialing an IP address (with and without RAS) <br />
<br />
Dialing with code key from an unauthorised phone <br />
<br />
Different ringing tones (internal/external) <br />
<br />
Direct dialing; immediate internal/external <br />
<br />
Display duration of call <br />
<br />
Display calling number <br />
<br />
Emigration of the subscriber/endpoint <br />
<br />
Fixed call diversion; unconditional, no answer (time adjustable) on busy <br />
<br />
Forced announcement (priority call) <br />
<br />
Function keys – multitude possible – exact list can be found in the technical specification of each IP phone <br />
<br />
Hands free <br />
<br />
Headset protocol DHSG <br />
<br />
Headset and handset parallel and autonomous <br />
<br />
Identification of the caller (name/number) <br />
<br />
Individual configuration <br />
<br />
Individual phonebook <br />
<br />
Intercom with automatic call acceptance <br />
<br />
Manager/assistant feature <br />
<br />
Message waiting indication (MWI) <br />
<br />
Messaging <br />
<br />
Multi language <br />
<br />
Multi protocol and multi-registration (SIP and H.323 concurrent) <br />
<br />
Multiple conference interlinked and limitless <br />
<br />
Multiple operators <br />
<br />
Multiple registrations with selective de-registration <br />
<br />
Mute (switch off the microphone) <br />
<br />
Name dialing <br />
<br />
Open listening <br />
<br />
Over plugging (connect call to a busy subscriber) <br />
<br />
Phone lock <br />
<br />
Preferred subscriber <br />
<br />
Project code<br />
<br />
Redialing of the last 100 dialed numbers <br />
<br />
Rush display (0-4) <br />
<br />
Silent Intrusion <br />
<br />
SIP via TCP <br />
<br />
SIPS (Secure SIP via TCP/TLS) <br />
<br />
SRTP (SIP and H.323) <br />
<br />
Status indication of the subscriber (free, busy, call) <br />
<br />
Subscriber with several lines <br />
<br />
Subscriber with several numbers <br />
<br />
Telephone book <br />
<br />
Transfer of the subscriber phone number <br />
<br />
Transfer with consultation <br />
<br />
Variable call diversion <br />
<br />
802.1x<br />
<br />
===Features Interactive Voice Response (IVR) (*)===<br />
<br />
Announcements depending on the caller (e.g. automatic or manual language selection) <br />
<br />
Call handling according to lines and/or calling number (CLI)<br />
<br />
Listen to the menu also from internal subscribers <br />
<br />
Multi level menu <br />
<br />
Overflow from the operator to an automatic operator <br />
<br />
Voice menu at extension (if no answer, busy, unconditional) <br />
<br />
Voice menu with information and automatic dialing <br />
<br />
Voice menu with predefined destinations <br />
<br />
Voice menu with manual dialing of the destination (DTMF) <br />
<br />
<br />
==== New in V8====<br />
<br />
Announcing the queue position in a waiting queue <br />
<br />
<br />
<br />
<br />
Note: <br />
<br />
(*) PC with WIN XP (web server) required or via Compact Flash (CF slot in IP800, IP305, IP302, IP2000, IP6000) <br />
<br />
(#) innovaphone IP21 required <br />
<br />
<br />
<br />
<br />
[[Category:News|{{PAGENAME}}]]</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:PBX/Objects/Edit_Profiles&diff=20915Reference9:PBX/Objects/Edit Profiles2011-04-19T09:04:20Z<p>Tsr: </p>
<hr />
<div>You can set various profiles per user, for each profile you can have a [[Reference9:Concept_myPBX#Contacts |buddy list (aka contacts)]] in the myPBX client.<br />
<br />
'''Name''' Name of the profile, the myPBX user can choose from profile names if more are configured. <br />
<br />
== Properties of a Profile==<br />
<br />
{|<br />
|valign=top nowrap=true|'''Name'''<br />
|Name of the user that shows up in the buddy list<br />
|-<br />
|valign=top nowrap=true|'''No'''<br />
|Number of that user that shows up in the buddy list<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Display'''<br />
|How the user should be named in the buddy list<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Extern'''<br />
|If its not an user from the PBX choose '''tel''' for a external phone number, or '''sip''' for an external sip user via federation<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Presence'''<br />
|If you want to monitor the users presence state (that is only for external users), for internal you see the presence state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]], used for federstion<br />
|-<br />
|valign=top nowrap=true|'''Dialog'''<br />
|If you want to monitor the users call state (that is only for external users), for internal you see the call state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]], used for federation<br />
|-<br />
|}<br />
<br />
<br />
* Note: For internal users configure either name or number.</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:PBX/Objects/Edit_Profiles&diff=20914Reference9:PBX/Objects/Edit Profiles2011-04-19T09:03:43Z<p>Tsr: </p>
<hr />
<div>You can set various profiles per user, for each profile you can have a [[Reference9:Concept_myPBX#Contacts |buddy list (aka contacts)]] in the myPBX client.<br />
<br />
'''Name''' Name of the profile, the myPBX user can choose from profile names if more are configured. <br />
<br />
== Properties of a Profile==<br />
<br />
{|<br />
|valign=top nowrap=true|'''Name'''<br />
|Name of the user that shows up in the buddy list<br />
|-<br />
|valign=top nowrap=true|'''No'''<br />
|Number of that user that shows up in the buddy list<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Display'''<br />
|How the user should be named in the buddy list<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Extern'''<br />
|If its not an user from the PBX choose '''tel''' for a external phone number, or '''sip''' for an external sip user via federation<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Presence'''<br />
|If you want to monitor the users presence state (that is only for external users), for internal you see the presence state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]], used for federstion<br />
|-<br />
|valign=top nowrap=true|'''Dialog'''<br />
|If you want to monitor the users call state (that is only for external users), for internal you see the call state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]], used for federation<br />
|-<br />
|}<br />
<br />
<br />
* Note: For internal users configure only name or number.</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:PBX/Objects/Edit_Profiles&diff=20913Reference9:PBX/Objects/Edit Profiles2011-04-19T09:03:33Z<p>Tsr: </p>
<hr />
<div>You can set various profiles per user, for each profile you can have a [[Reference9:Concept_myPBX#Contacts |buddy list (aka contacts)]] in the myPBX client.<br />
<br />
'''Name''' Name of the profile, the myPBX user can choose from profile names if more are configured. <br />
<br />
== Properties of a Profile==<br />
<br />
{|<br />
|valign=top nowrap=true|'''Name'''<br />
|Name of the user that shows up in the buddy list<br />
|-<br />
|valign=top nowrap=true|'''No'''<br />
|Number of that user that shows up in the buddy list<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Display'''<br />
|How the user should be named in the buddy list<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Extern'''<br />
|If its not an user from the PBX choose '''tel''' for a external phone number or '''sip''' for an external sip user via federation<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Presence'''<br />
|If you want to monitor the users presence state (that is only for external users), for internal you see the presence state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]], used for federstion<br />
|-<br />
|valign=top nowrap=true|'''Dialog'''<br />
|If you want to monitor the users call state (that is only for external users), for internal you see the call state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]], used for federation<br />
|-<br />
|}<br />
<br />
<br />
* Note: For internal users configure only name or number.</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:PBX/Objects/Edit_Profiles&diff=20912Reference9:PBX/Objects/Edit Profiles2011-04-19T09:03:23Z<p>Tsr: </p>
<hr />
<div>You can set various profiles per user, for each profile you can have a [[Reference9:Concept_myPBX#Contacts |buddy list (aka contacts)]] in the myPBX client.<br />
<br />
'''Name''' Name of the profile, the myPBX user can choose from profile names if more are configured. <br />
<br />
== Properties of a Profile==<br />
<br />
{|<br />
|valign=top nowrap=true|'''Name'''<br />
|Name of the user that shows up in the buddy list<br />
|-<br />
|valign=top nowrap=true|'''No'''<br />
|Number of that user that shows up in the buddy list<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Display'''<br />
|How the user should be named in the buddy list<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Extern'''<br />
|If its not an user from the PBX choose '''tel'''for a external phone number or '''sip''' for an external sip user via federation<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Presence'''<br />
|If you want to monitor the users presence state (that is only for external users), for internal you see the presence state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]], used for federstion<br />
|-<br />
|valign=top nowrap=true|'''Dialog'''<br />
|If you want to monitor the users call state (that is only for external users), for internal you see the call state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]], used for federation<br />
|-<br />
|}<br />
<br />
<br />
* Note: For internal users configure only name or number.</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:PBX/Objects/Edit_Profiles&diff=20911Reference9:PBX/Objects/Edit Profiles2011-04-19T09:01:41Z<p>Tsr: </p>
<hr />
<div>You can set various profiles per user, for each profile you can have a [[Reference9:Concept_myPBX#Contacts |buddy list (aka contacts)]] in the myPBX client.<br />
<br />
'''Name''' Name of the profile, the myPBX user can choose from profile names if more are configured. <br />
<br />
== Properties of a Profile==<br />
<br />
{|<br />
|valign=top nowrap=true|'''Name'''<br />
|Name of the user that shows up in the buddy list<br />
|-<br />
|valign=top nowrap=true|'''No'''<br />
|Number of that user that shows up in the buddy list<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Display'''<br />
|How the user should be named in the buddy list<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Extern'''<br />
|If its not an user from the PBX<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Presence'''<br />
|If you want to monitor the users presence state (that is only for external users), for internal you see the presence state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]]<br />
|-<br />
|valign=top nowrap=true|'''Dialog'''<br />
|If you want to monitor the users call state (that is only for external users), for internal you see the call state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]]<br />
|-<br />
|}<br />
<br />
<br />
* Note: For internal users configure only name or number.</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:PBX/Objects/Edit_Profiles&diff=20910Reference9:PBX/Objects/Edit Profiles2011-04-19T09:01:04Z<p>Tsr: </p>
<hr />
<div>You can set various profiles per user, for each profile you can have a [[Reference9:Concept_myPBX#Contacts |buddy list (aka contacts)]] in the myPBX client.<br />
<br />
'''Name''' Name of the profile, the myPBX user can choose from profile names if more are configured. <br />
<br />
== Properties of a Profile==<br />
<br />
{|<br />
|valign=top nowrap=true|'''Name'''<br />
|Name of the user that shows up in the buddy list<br />
|-<br />
|valign=top nowrap=true|'''No'''<br />
|Number of that user that shows up in the buddy list<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Display'''<br />
|How the suer should be named in the buddy list<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Extern'''<br />
|If its not an user from the PBX<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Presence'''<br />
|If you want to monitor the users presence state (that is only for external users), for internal you see the presence state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]]<br />
|-<br />
|valign=top nowrap=true|'''Dialog'''<br />
|If you want to monitor the users call state (that is only for external users), for internal you see the call state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]]<br />
|-<br />
|}<br />
<br />
<br />
* Note: For internal users configure only name or number.</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:PBX/Objects/Edit_Profiles&diff=20909Reference9:PBX/Objects/Edit Profiles2011-04-19T08:59:38Z<p>Tsr: </p>
<hr />
<div>You can set various profiles per user, for each profile you can have a [[Reference9:Concept_myPBX#Contacts |buddy list(aka contacts)]].<br />
<br />
'''Name''' Name of the profile, the myPBX user can choose from profile names if more are configured. <br />
<br />
== Properties of a Profile==<br />
<br />
{|<br />
|valign=top nowrap=true|'''Name'''<br />
|Name of the user that shows up in the buddy list<br />
|-<br />
|valign=top nowrap=true|'''No'''<br />
|Number of that user that shows up in the buddy list<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Display'''<br />
|How the suer should be named in the buddy list<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Extern'''<br />
|If its not an user from the PBX<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Presence'''<br />
|If you want to monitor the users presence state (that is only for external users), for internal you see the presence state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]]<br />
|-<br />
|valign=top nowrap=true|'''Dialog'''<br />
|If you want to monitor the users call state (that is only for external users), for internal you see the call state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]]<br />
|-<br />
|}<br />
<br />
<br />
* Note: For internal users configure only name or number.</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:PBX/Objects/Edit_Profiles&diff=20908Reference9:PBX/Objects/Edit Profiles2011-04-19T08:59:26Z<p>Tsr: </p>
<hr />
<div>{{FIXME|reason=needs content}}<br />
<br />
You can set various profiles per user, for each profile you can have a [[Reference9:Concept_myPBX#Contacts |buddy list(aka contacts)]].<br />
<br />
'''Name''' Name of the profile, the myPBX user can choose from profile names if more are configured. <br />
<br />
== Properties of a Profile==<br />
<br />
{|<br />
|valign=top nowrap=true|'''Name'''<br />
|Name of the user that shows up in the buddy list<br />
|-<br />
|valign=top nowrap=true|'''No'''<br />
|Number of that user that shows up in the buddy list<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Display'''<br />
|How the suer should be named in the buddy list<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Extern'''<br />
|If its not an user from the PBX<br />
|<br />
|-<br />
|valign=top nowrap=true|'''Presence'''<br />
|If you want to monitor the users presence state (that is only for external users), for internal you see the presence state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]]<br />
|-<br />
|valign=top nowrap=true|'''Dialog'''<br />
|If you want to monitor the users call state (that is only for external users), for internal you see the call state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]]<br />
|-<br />
|}<br />
<br />
<br />
* Note: For internal users configure only name or number.</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:PBX/Objects/Call_Broadcast_Conference&diff=20899Reference9:PBX/Objects/Call Broadcast Conference2011-04-18T14:38:29Z<p>Tsr: </p>
<hr />
<div>A broadcast conference object uses a local or remote conferencing resource (e.g. a [[Reference7:Administration/Gateway/Interfaces#Conferencing_interface_.28CONF.29|CONF interface]]) to implement an automatic multi-party conference. When the object is called, calls to all members of the groups the broadcast conference object is an active member itself are initiated. Moreover the Call Broadcast Conference will only make calls to PBX object having the following type:<br />
* PBX User object(used in most scenarios)<br />
* Call Broadcast object<br />
* Executive object<br />
* Waiting Queue object<br />
* Multicast announce object<br />
<br />
These calls then all participate in a single conference. <br />
<br />
This object is built-in to the PBX and thus does not need a registration to work. It will run on the PBX that is set in the ''PBX'' field. <br />
<br />
{|<br />
|valign=top nowrap=true|'''External Conference Resource Name'''<br />
If the conference resource local to the broadcast conference object shall be used, you can leave this field empty. Otherwise, you must configure the object ''Name'' of an existing resource. When a called conference member picks up the call, it gets transferred to this object. This object will usually be either a conference resource on another innovaphone PBX or a 3rd party conferencing unit.<br />
<br />
The call sent to the conferencing ressource will have a called party number that consists of the ''Conference Id Prefix'' + ''Conference Id'' + ''Conference Id Suffix''. There will be no calling party number.<br />
<br />
|-<br />
|valign=top nowrap=true|'''Create Dynamic Conference Id'''<br />
Each individual conference running on a conferencing resource (a.k.a. ''conference room'') needs a distinct conference-id. If this check box is ticked, conference ids will be created dynamically for new conferences. Please note that a single broadcast conference object never uses more than one conference object at a time.<br />
<br />
|-<br />
|valign=top nowrap=true|'''Conference Id'''<br />
If no ''Create Dynamic Conference Id'' is not checked, then you need to specify the conference id to be used here.<br />
|-<br />
|valign=top nowrap=true|'''3rd Party Conferencing Unit'''<br />
Enables the next 2 check marks (which are not required if the conferencing resource is an innovaphone device).<br />
|-<br />
|valign=top nowrap=true|'''Conference Id Prefix'''<br />
See above. Leave '*3' for the innovaphone CONF interface.<br />
|-<br />
|valign=top nowrap=true|'''Conference Id Suffix'''<br />
See above. Leave '#' for the innovaphone CONF interface.<br />
|-<br />
|valign=top nowrap=true|'''Alert Timeout'''<br />
The broadcast conference object will call members and wait ''Alert Timeout'' seconds for the user to pick up the call.<br />
|-<br />
|valign=top nowrap=true|'''Connecting Mode'''<br />
This setting defines when members are connected to the conferencing unit.<br />
{|left=3<br />
|-<br />
| '''Direct after calling''' ||Members (including the initiator) are connected immediately. <br />
|-<br />
| '''With the first response'''||Members are connected after the first called member picks up. The initiator will hear a tone meanwhile.<br />
|-<br />
| '''When all users have answered'''||Members are connected only after all called member picked up. The initiator and all but the last called member will hear a tone meanwhile.<br />
|-<br />
| '''When all users have answered, or at least one and after timeout'''||Same as above, except that if there are at least 2 members who have picked up and the timeout expired the members are connected.<br />
|}<br />
|-<br />
|valign=top|'''Alert only at conference begin'''<br />
If this is ticked, unconnected group members aren't alerted again with a new call to the conference if the conference is still running.<br />
|-<br />
|valign=top nowrap=true|'''Only Group Members allowed'''<br />
If this check box is not ticked, anyone can initiate the conference by calling the broadcast conference object. If it is ticked, only group members can.<br />
|-<br />
|valign=top nowrap=true|'''Allow Announcement Calls'''<br />
If this is ticked, initiating announcement calls will trigger outgoing member invitation calls as announcement calls too.<br />
|-<br />
|valign=top nowrap=true|'''Call always as Announcement Call'''<br />
If this is ticked, all outgoing member invitation calls are sent as announcement calls.<br />
|}<br />
<br />
Only Ip6010, IP3010, IP1060, IP0010, IP6000, IP800 and IP305 support local conferencing, one DSP is in use for each user in a conference call.<br />
Some early IP6000 do not support this feature. Refer to the [[Howto:Multi-Party Conferencing with early IP6000|upgrade details]] if you consider upgrading your hardware.<br />
<br />
Please refer to [[Reference7:Administration/Gateway/Interfaces#Conferencing_interface_.28CONF.29|Administration/Gateway/Interfaces]] for access to a generic conferencing resource if no ''Broadcast Conference'' is required.</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Howto:SAMwin_CCO_5.1&diff=20855Howto:SAMwin CCO 5.12011-04-14T13:06:45Z<p>Tsr: /* Summary */</p>
<hr />
<div><!-- this text is a comment that is not visible on normal view at the article. --><br />
<!-- to create a new entry here,<br />
- fill in all sections marked as "by vendor"<br />
- innovaphone will then complete the remaining sections (marked as "by inno")<br />
<br />
Please note that this article is in English only!<br />
feel free to ask presales in case you have any difficulties on editing wiki articles <br />
--><br />
<br />
<!-- by vendor:<br />
- upload your company and product logo (if any) in a suitable size (.pgn preferred)<br />
- replace images below with your logo<br />
--><br />
[[Image:Howto-SAMwin_CCO_samiwn_.png|right]]<br />
==Product Name==<br />
<!-- by vendor:<br />
Place here Official Product Name, as used in vendors product collateral <br />
If you have a dedicated product page (not a generic vendor page) in English, also put the link below<br />
--><br />
[http://www.telecomsoftware.com/samwin/Home/tabid/38/language/en-US/Default.aspx Samwin Contact Center Suite 5.1 ]<br />
<br />
==Certification Status==<br />
<!-- by inno<br />
- uncomment one of the stati below <br />
- update date below<br />
--><br />
<!-- {{Template:Compat Status "planned"}} --><br />
<!-- {{Template:Compat Status "in progress"}} --><br />
<!-- {{Template:Compat Status "certified"|certificate=Product_-_Vendor_-_3rd_Party_Product_-_Desc-product-cert.pdf}} --><br />
<!-- {{Template:Compat Status "tested"(sip provider)}} --><br />
<!-- {{Template:Compat Status "rejected"}} --><br />
{{Template:Compat Status "customer-testimonial"}}<br />
<br />
Testing of this product has been finalized February 7th, 2011.<br />
<br />
==Category==<br />
<!-- by inno:<br />
- select one or more of the available recommended product categories <br />
a list of valid Categories can be found in <br />
Special Pages / Prefix Index / Display pages with prefix = RecProd, Display pages with prefix = Category <br />
(you need to apply it twice, first as template {{..}}, seconds as category [[..]])<br />
--><br />
{{Category:RecProd Call Center Applications}}<br />
[[Category:RecProd|{{PAGENAME}}]]<br />
[[Category:RecProd Call Center Applications|{{PAGENAME}}]]<br />
[[Category:Referral Product|{{PAGENAME}}]]<br />
<br />
<br />
==Functions==<br />
<!-- by vendor:<br />
- place here a short and concise list of features that are supported by your product <br />
--><br />
Short summary of the most famous features:<br />
<br />
Standard console functions<br />
* Receive calls and transferring calls<br />
* Non consultation call<br />
* Call always returns to the same operator<br />
* Caller identification by name and number<br />
* Call hold<br />
* Conference<br />
* Call park with notification when retrieving the call from the parking position<br />
* Public system wide parking queue customizable<br />
* Directory lookup<br />
* Transfer to external subscribers<br />
* Search in multiple columns<br />
* Identification of call type (internal, external, no answer, busy, call back, etc.)<br />
* Arbitrary selection of calls in the waiting queue by the operator<br />
* Manual night service<br />
* Automatic night service<br />
<br />
Professional console functions<br />
<br />
* Context-sensitive greeting texts (“telecomsoftware, How can I help you.”)<br />
* Different greeting texts for different trunks / members<br />
* Malicious call recording<br />
* Automatic mail to the supervisor in case of a recorded call<br />
* Automatic voice greeting with prerecorded announcements for each operator<br />
* Automatic voice greeting depending on time of day, caller id, trunk, called number, operator, etc.<br />
* Braille support (for visually impaired )<br />
* Multi-user, multi-site and multi-PBX support<br />
* Multi-customer support<br />
* Override call forward<br />
* Set call forward<br />
* Keyword database<br />
* Alternative extensions<br />
* Directory view restricted by the location of the console<br />
* Interposition calls/transfers<br />
* Graphical Busy Lamp Field (BLF)<br />
* BLF’s information is configurable (number, name, status, colors, appointments, etc.)<br />
* Supported extension status: idle, busy, dialing, ringing, etc.<br />
* BLF is synchronized with the directory (auto-scroll function)<br />
* BLF can be detached from the main console window and run on a 2nd screen or wall display<br />
* Busy information is shown not only in the BLF but also in all directory lists<br />
* Number in the extensions display shows the number of the external caller, not the number of the operator<br />
* Call history for frequent callers (3rd call for today, last call to xxxxxxx, at xxxx)<br />
* Powerful SQL-based directory, up to 20 hierarchy levels, auto synchronization with master database<br />
* One click transfer to alternative targets, like cell phone, mailbox, home number, etc.<br />
* Identification of all callers via area code database<br />
* Integration of telephone book CD APIs with reverse lookup function (e.g. Swisscom Directory, KlickTel, etc.)<br />
* Supports GSM cell phones and any other external phone for night service<br />
* Configurable waiting time between each call<br />
<br />
<br />
==Vendor==<br />
<!-- by vendor<br />
- Official name of your company, at best linked to your companies web site url, Official name of the vendors web site <br />
- you may also add a logo<br />
- upload your company logo (.png preferred, suitable size)<br />
- replace logo below with yours <br />
--><br />
<br />
[http://www.telecomsoftware.com/samwin/Home/tabid/38/language/en-US/Default.aspx telecommunication software gmbh]<br />
<br />
==Summary==<br />
<!-- by inno:<br />
- add remarks regarding the product, such as special features, firmware versions or licenses required on the inno side, <br />
parts of the product that has not been tested or limitations discovered. very short and concise (everything else is in <br />
the test report) <br />
- add link to product test report here<br />
--><br />
<br />
This solution was tested by [http://www.telecomsoftware.com/samwin/Home/tabid/38/language/en-US/Default.aspx telecommunication software ] .<br />
<br />
SAMwin CCO version 5.1 R2 (version 5.1.11.) tested with innovaphone PBX <br />
<br />
*V7 Hotfix 21, innovaphone TSP build 7531 [[media:SAMwin.CCO_PBX_Certification_-_Innovaphone_v7.pdf| innovaphone V7 Certification/Testreport]]<br />
*V8 Hotfix 8, innovaphone TSP build 8058 [[media:SAMwin.CCO_PBX_Certification_-_Innovaphone_v8.pdf| innovaphone V8 Certification/Testreport]]<br />
<br />
The hot standby solution from telecommunication software was not conceptional implemented by the time of writing, thus it shows "not available" in the testreport.<br />
<br />
==Contact==<br />
<!-- by vendor:<br />
- add name, address, phone, fax, email, web of primary recommended sales contact<br />
if suitable, you may consider specifying several contacs, depending on your sales structure <br />
(e.g. by country or vertical market)<br />
- in case of a customer testimonial the contact details of the reseller are not disclosed here. As contact person should act sales@innovaphone.com. In order to find the reseller responsible for this product, enter also the corresponding mantis ticket number in invisible tags. <br />
--><br />
<br />
For further informations on this test, please contact the [mailto:office@telecomsoftware.com vendor] directly.<br />
<br />
<!-- mantis: 50651--><br />
<br />
[[Category:Compat|{{PAGENAME}}]]</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:Licenses&diff=20835Reference9:Licenses2011-04-14T06:54:30Z<p>Tsr: /* Example IPVA */</p>
<hr />
<div>Licenses are used on the innovaphone gateways to enable specific features so that the customers have to pay for features only, which they actually use. There are 3 different types of licenses: For the Gateway (Relay), the PBX and DECT.<br />
<br />
== Gateway Licenses ==<br />
<br />
{|<br />
|valign=top nowrap=true|'''Channels'''<br />
|Enables the use of the number of DSP channels as specified in the license. A DSP channel is needed for each call to a ISDN interface, an analog Interface or a conference interface. If no license is availabe the call is rejected.<br />
|-<br />
|valign=top nowrap=true|'''BRIs'''<br />
|Enables the use of a ISDN Basic Rate Interface. Only licensed interfaces are displayed in the user interface and can be used for calls. Which interface is enabled is chosen by a default sequence. If other interfaces are desired, interfaces can be disabled, which means they do not consume a license.<br />
|-<br />
|valign=top nowrap=true|'''PRIs'''<br />
|Enables the use of a ISDN Primary Rate Interface. Only licensed interfaces are displayed in the user interface and can be used for calls. Which interface is enabled is chosen by a default sequence. If other interfaces are desired, interfaces can be disabled, which means they do not consume a license.<br />
|-<br />
|valign=top nowrap=true|'''Gatekeeper7'''<br />
|Enables the gatekeeper functionality on version 7,8 and version 9. Which means the gateway VOIP interface type 'Gatekeeper/Registrar' is available.<br />
|}<br />
<br />
===Built in Licenses===<br />
<br />
Since the release of version 7 some hardware platforms already come fully equipped with all necessary interface licenses. The units are:<br />
<br />
* IP22<br />
* IP24<br />
* IP28<br />
* IP302<br />
<br />
This includes also the required ''Channel'' licenses. Built-in licenses are not shown in the ''Licenses'' table in [[Reference7:Administration/Gateway/General|''Gateway / General'']].<br />
<br />
== PBX Licenses ==<br />
<br />
{|<br />
|valign=top nowrap=true|'''PORT9*20'''<br />
|Port License. To register endpoints at PBX objects. This SMB version can not be installed at a slave PBX and can only be used for one device/project. Maximum 20 Ports of this SMB version are possible, for more ports normal port licenses must be added.<br />
|-<br />
|valign=top nowrap=true|'''PORT9'''<br />
|Port License. To register endpoints at PBX objects. Many endpoints can register at one object and only one port license is in use. A port license gets in use when at least one object has a registration. Configuring objects without registration do not need licenses.<br />
|-<br />
|valign=top nowrap=true|'''IPVA9'''<br />
|IPVA License. To allow registrations at the PBX running on IPVA, this license is needed in combination with the '''PORT9''' ('''PORT9*20''') license. As much as PORT9 licenses are in use as much IPVA9 licenses are needed. The IPVA9 license must not be the same size as PORT licenses installed.<br />
|-<br />
|valign=top nowrap=true|'''Mobility9'''<br />
|License to enable Mobility function for a user object.<br />
|-<br />
|valign=top nowrap=true|'''SoftwarePhones9'''<br />
|License to use a innovaphone software phone (not for the Bria softphone)<br />
|-<br />
|valign=top nowrap=true|'''Operator9'''<br />
|License to use the innovaphone operator software.<br />
|-<br />
|valign=top nowrap=true|'''Voicemail9'''<br />
|License to use the innovaphone voicemail script. Must be at least the same as the port license.<br />
|-<br />
|valign=top nowrap=true|'''Standby9'''<br />
|License to enable Standby operation. Must be at least the same as the port license. With this license a PBX accepts registrations from endpoints not configured for this PBX, which should happen only if the PBX where the endpoint is configured for, is not available. A standby license installed without a port license does not do anything.<br />
|-<br />
|valign=top nowrap=true|'''GSM-n'''<br />
|License to use a GSM client of the version n on the GSM phone<br />
|-<br />
|valign=top nowrap=true|'''PBX-QueueMonitor'''<br />
|License to use the [[Howto:PBX-QueueMonitor |PBX queue monitor ]], one license needed per queue monitor.<br />
|-<br />
|valign=top nowrap=true|'''PBX-Reporting9'''<br />
|License to use the [[Reference9:Concept Reporting |reporting application]]. For each object that reports are generated for, a license is needed. The reporting license must not be the same size as the port license.<br />
|-<br />
|}<br />
<br />
Port licenses are used for trunk, executive, gateway ,user and PBX objects (for registering slave and dyn PBXs).<br />
<br />
** Note : If you do any License changing, adding or deleting licenses. The PBX needs an reboot that the license changes become effective.<br />
<br />
==== Example IPVA====<br />
<br />
Running a PBX on IPVA with 100 port licenses, 90 port licenses are in use (there are registrations on 90 objects), then also 90 IPVA licenses are needed. When a new endpoint try´s to register at a new object, the registration will be denied. There are enough port licenses that a endpoint could register but not enough ipva licenses. If there are more registrations on one user object only one port license is in use and thus only one ipva license needed. <br />
<br />
===== VMware HA and FT =====<br />
<br />
Using the VMware HA (high availability solution) or the FA (Fault Tolerance) with the innovaphone IPVA, no extra innovaphone licenses are needed (even no standby license).<br />
* Note : This VWware features are not yet tested by innovaphone<br />
<br />
==== Example PBX-QueueMonitor====<br />
<br />
This is a concurrent licence, means if one queue monitor connects at the PBX one license is consumed, if the queue monitor is off the licence gets released. Example 1: One waiting queue should be monitored by 5 PBX-queue monitor, so 5 licenses are needed. Example 2: 3 waiting queues, on the first waiting queue 3 PBX queue monitor ,on the second one PBX monitor and on the third no PBX monitor.<br />
So 4 licenses are needed.<br />
<br />
====Example Reporting====<br />
<br />
A PBX with 100 port licenses, but only for the waiting queue and 10 user objects reports should be done. Therefore only 11 reporting licenses need to be purchased.<br />
On the waiting queue and the 10 user objects the reporting chek-mark must be set, then the innovaphone reporting can generate reports for that objects.<br />
<br />
====Example Mobility====<br />
A user object requires a Port license if there is at least one registration on it. A user using a mobility object (that is, a forking destination and a mobility object is defined) requires a Mobility license per destination. A forking destination with no mobility object defined require no Mobility license. The mobility client (which is to be installed on the mobile phone) will require a GSM license.<br />
<br />
So if you create a user object with a VoIP terminal registration and a forking destination with mobility, then you will need 1 Port license and 1 Mobility license. If on the user object there are no registrations but a forking destination with mobility enabled, then it will need 1 Mobility license but no Port license. If there are no registrations and a forking destination without mobility, then no license at all is required.<br />
<br />
The standard configuration (a user object with registrations and a mobility enabled forking destination and a mobile phone with mobile client installed) requires 1 Port plus 1 Mobility plus 1 GSM license.<br />
<br />
In summary you also can have more Mobility lics than you have port lics.<br />
<br />
=== PBX Floating mechanism===<br />
<br />
If no Port license is installed locally on a slave/standby PBX it obtains automatically all PBX licenses from the master. If this option is used, Port licenses need to be installed for the total number of endpoints in the system on the master.<br />
<br />
Slaves with locally installed licenses can be mixed with Slaves obtaining their licenses from the master.<br />
<br />
A slave/standby stores the received license in flash memory so it can still operate even if the master is not available.<br />
<br />
License updates between master and slaves are sent in intervals of approximately 10min to limit the bandwidth usage. Because of this it may happen that temporarily more licenses can be used than actually available.<br />
<br />
It is not necessary/possible to buy floating licenses. You can use them without a balance in my.innovaphone.com. There is no license needed at all to use the floating mechanism.<br />
<br />
=== Licensing for Standby operation ===<br />
<br />
If a PBX shall operate as standby (either as dedicated standby or as a master being standby for a slave, or as a slave being standby for a master), a standby license with at least the value of the Port license must be available. This Standby license can be obtained from the Master by the use of the Floating mechanism.<br />
<br />
==== Examples ====<br />
<br />
'''Dedicated Standby (Standby/Standby-Slave)'''<br />
<br />
No PBX licenses should be installed on the Standby, to obtain the licenses from the master and a Standby license of the correct size has to be installed on the master.<br />
<br />
'''Master acting as Standby'''<br />
<br />
If a master should accept registrations which are configured for slaves, in case the slaves are not available a Standby license of at least the size of the Port licenses needs to be installed on this master.<br />
<br />
'''Slave acting as Standby for Master'''<br />
<br />
If a slave should accept registrations which are not configured for this slave, in case the master is not available, a standby license of at least the size of the Port license must be available on the slave. If the licenses are obtained from the master by the use of the Floating mechanism the Standby license must be installed on the master, if local licenses are used, the standby license must be installed on the slave.<br />
<br />
== DECT Licenses ==<br />
<br />
{|<br />
|valign=top nowrap=true|'''Multicell'''<br />
|The Multicell license enables the Multicell master and defines the System Identification (ARI) on the wireless side, installed on the IP1200.<br />
|}</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:Licenses&diff=20834Reference9:Licenses2011-04-14T06:51:51Z<p>Tsr: </p>
<hr />
<div>Licenses are used on the innovaphone gateways to enable specific features so that the customers have to pay for features only, which they actually use. There are 3 different types of licenses: For the Gateway (Relay), the PBX and DECT.<br />
<br />
== Gateway Licenses ==<br />
<br />
{|<br />
|valign=top nowrap=true|'''Channels'''<br />
|Enables the use of the number of DSP channels as specified in the license. A DSP channel is needed for each call to a ISDN interface, an analog Interface or a conference interface. If no license is availabe the call is rejected.<br />
|-<br />
|valign=top nowrap=true|'''BRIs'''<br />
|Enables the use of a ISDN Basic Rate Interface. Only licensed interfaces are displayed in the user interface and can be used for calls. Which interface is enabled is chosen by a default sequence. If other interfaces are desired, interfaces can be disabled, which means they do not consume a license.<br />
|-<br />
|valign=top nowrap=true|'''PRIs'''<br />
|Enables the use of a ISDN Primary Rate Interface. Only licensed interfaces are displayed in the user interface and can be used for calls. Which interface is enabled is chosen by a default sequence. If other interfaces are desired, interfaces can be disabled, which means they do not consume a license.<br />
|-<br />
|valign=top nowrap=true|'''Gatekeeper7'''<br />
|Enables the gatekeeper functionality on version 7,8 and version 9. Which means the gateway VOIP interface type 'Gatekeeper/Registrar' is available.<br />
|}<br />
<br />
===Built in Licenses===<br />
<br />
Since the release of version 7 some hardware platforms already come fully equipped with all necessary interface licenses. The units are:<br />
<br />
* IP22<br />
* IP24<br />
* IP28<br />
* IP302<br />
<br />
This includes also the required ''Channel'' licenses. Built-in licenses are not shown in the ''Licenses'' table in [[Reference7:Administration/Gateway/General|''Gateway / General'']].<br />
<br />
== PBX Licenses ==<br />
<br />
{|<br />
|valign=top nowrap=true|'''PORT9*20'''<br />
|Port License. To register endpoints at PBX objects. This SMB version can not be installed at a slave PBX and can only be used for one device/project. Maximum 20 Ports of this SMB version are possible, for more ports normal port licenses must be added.<br />
|-<br />
|valign=top nowrap=true|'''PORT9'''<br />
|Port License. To register endpoints at PBX objects. Many endpoints can register at one object and only one port license is in use. A port license gets in use when at least one object has a registration. Configuring objects without registration do not need licenses.<br />
|-<br />
|valign=top nowrap=true|'''IPVA9'''<br />
|IPVA License. To allow registrations at the PBX running on IPVA, this license is needed in combination with the '''PORT9''' ('''PORT9*20''') license. As much as PORT9 licenses are in use as much IPVA9 licenses are needed. The IPVA9 license must not be the same size as PORT licenses installed.<br />
|-<br />
|valign=top nowrap=true|'''Mobility9'''<br />
|License to enable Mobility function for a user object.<br />
|-<br />
|valign=top nowrap=true|'''SoftwarePhones9'''<br />
|License to use a innovaphone software phone (not for the Bria softphone)<br />
|-<br />
|valign=top nowrap=true|'''Operator9'''<br />
|License to use the innovaphone operator software.<br />
|-<br />
|valign=top nowrap=true|'''Voicemail9'''<br />
|License to use the innovaphone voicemail script. Must be at least the same as the port license.<br />
|-<br />
|valign=top nowrap=true|'''Standby9'''<br />
|License to enable Standby operation. Must be at least the same as the port license. With this license a PBX accepts registrations from endpoints not configured for this PBX, which should happen only if the PBX where the endpoint is configured for, is not available. A standby license installed without a port license does not do anything.<br />
|-<br />
|valign=top nowrap=true|'''GSM-n'''<br />
|License to use a GSM client of the version n on the GSM phone<br />
|-<br />
|valign=top nowrap=true|'''PBX-QueueMonitor'''<br />
|License to use the [[Howto:PBX-QueueMonitor |PBX queue monitor ]], one license needed per queue monitor.<br />
|-<br />
|valign=top nowrap=true|'''PBX-Reporting9'''<br />
|License to use the [[Reference9:Concept Reporting |reporting application]]. For each object that reports are generated for, a license is needed. The reporting license must not be the same size as the port license.<br />
|-<br />
|}<br />
<br />
Port licenses are used for trunk, executive, gateway ,user and PBX objects (for registering slave and dyn PBXs).<br />
<br />
** Note : If you do any License changing, adding or deleting licenses. The PBX needs an reboot that the license changes become effective.<br />
<br />
==== Example IPVA====<br />
<br />
Running a PBX on IPVA with 100 port licenses, 90 port licenses are in use (there are registrations on 90 objects), then also 90 IPVA licenses are needed. When a new endpoint try´s to register at a new object, the registration will be denied. There are enough port licenses that a endpoint could register but not enough ipva licenses. If there are more registrations on one user object only one port license is in use and thus only one ipva license needed. <br />
<br />
===== VMware HA and FT =====<br />
<br />
Using the VMware HA (high availability solution) or the FA (Fault Tolerance) with the innovaphone IPVA, no extra innovaphone licenses are needed (even no standby license).<br />
* Note : This VWware features are not yet tested innovaphone<br />
<br />
==== Example PBX-QueueMonitor====<br />
<br />
This is a concurrent licence, means if one queue monitor connects at the PBX one license is consumed, if the queue monitor is off the licence gets released. Example 1: One waiting queue should be monitored by 5 PBX-queue monitor, so 5 licenses are needed. Example 2: 3 waiting queues, on the first waiting queue 3 PBX queue monitor ,on the second one PBX monitor and on the third no PBX monitor.<br />
So 4 licenses are needed.<br />
<br />
====Example Reporting====<br />
<br />
A PBX with 100 port licenses, but only for the waiting queue and 10 user objects reports should be done. Therefore only 11 reporting licenses need to be purchased.<br />
On the waiting queue and the 10 user objects the reporting chek-mark must be set, then the innovaphone reporting can generate reports for that objects.<br />
<br />
====Example Mobility====<br />
A user object requires a Port license if there is at least one registration on it. A user using a mobility object (that is, a forking destination and a mobility object is defined) requires a Mobility license per destination. A forking destination with no mobility object defined require no Mobility license. The mobility client (which is to be installed on the mobile phone) will require a GSM license.<br />
<br />
So if you create a user object with a VoIP terminal registration and a forking destination with mobility, then you will need 1 Port license and 1 Mobility license. If on the user object there are no registrations but a forking destination with mobility enabled, then it will need 1 Mobility license but no Port license. If there are no registrations and a forking destination without mobility, then no license at all is required.<br />
<br />
The standard configuration (a user object with registrations and a mobility enabled forking destination and a mobile phone with mobile client installed) requires 1 Port plus 1 Mobility plus 1 GSM license.<br />
<br />
In summary you also can have more Mobility lics than you have port lics.<br />
<br />
=== PBX Floating mechanism===<br />
<br />
If no Port license is installed locally on a slave/standby PBX it obtains automatically all PBX licenses from the master. If this option is used, Port licenses need to be installed for the total number of endpoints in the system on the master.<br />
<br />
Slaves with locally installed licenses can be mixed with Slaves obtaining their licenses from the master.<br />
<br />
A slave/standby stores the received license in flash memory so it can still operate even if the master is not available.<br />
<br />
License updates between master and slaves are sent in intervals of approximately 10min to limit the bandwidth usage. Because of this it may happen that temporarily more licenses can be used than actually available.<br />
<br />
It is not necessary/possible to buy floating licenses. You can use them without a balance in my.innovaphone.com. There is no license needed at all to use the floating mechanism.<br />
<br />
=== Licensing for Standby operation ===<br />
<br />
If a PBX shall operate as standby (either as dedicated standby or as a master being standby for a slave, or as a slave being standby for a master), a standby license with at least the value of the Port license must be available. This Standby license can be obtained from the Master by the use of the Floating mechanism.<br />
<br />
==== Examples ====<br />
<br />
'''Dedicated Standby (Standby/Standby-Slave)'''<br />
<br />
No PBX licenses should be installed on the Standby, to obtain the licenses from the master and a Standby license of the correct size has to be installed on the master.<br />
<br />
'''Master acting as Standby'''<br />
<br />
If a master should accept registrations which are configured for slaves, in case the slaves are not available a Standby license of at least the size of the Port licenses needs to be installed on this master.<br />
<br />
'''Slave acting as Standby for Master'''<br />
<br />
If a slave should accept registrations which are not configured for this slave, in case the master is not available, a standby license of at least the size of the Port license must be available on the slave. If the licenses are obtained from the master by the use of the Floating mechanism the Standby license must be installed on the master, if local licenses are used, the standby license must be installed on the slave.<br />
<br />
== DECT Licenses ==<br />
<br />
{|<br />
|valign=top nowrap=true|'''Multicell'''<br />
|The Multicell license enables the Multicell master and defines the System Identification (ARI) on the wireless side, installed on the IP1200.<br />
|}</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:Licenses&diff=20833Reference9:Licenses2011-04-14T06:39:13Z<p>Tsr: /* PBX Licenses */</p>
<hr />
<div>Licenses are used on the innovaphone gateways to enable specific features so that the customers have to pay for features only, which they actually use. There are 3 different types of licenses: For the Gateway (Relay), the PBX and DECT.<br />
<br />
== Gateway Licenses ==<br />
<br />
{|<br />
|valign=top nowrap=true|'''Channels'''<br />
|Enables the use of the number of DSP channels as specified in the license. A DSP channel is needed for each call to a ISDN interface, an analog Interface or a conference interface. If no license is availabe the call is rejected.<br />
|-<br />
|valign=top nowrap=true|'''BRIs'''<br />
|Enables the use of a ISDN Basic Rate Interface. Only licensed interfaces are displayed in the user interface and can be used for calls. Which interface is enabled is chosen by a default sequence. If other interfaces are desired, interfaces can be disabled, which means they do not consume a license.<br />
|-<br />
|valign=top nowrap=true|'''PRIs'''<br />
|Enables the use of a ISDN Primary Rate Interface. Only licensed interfaces are displayed in the user interface and can be used for calls. Which interface is enabled is chosen by a default sequence. If other interfaces are desired, interfaces can be disabled, which means they do not consume a license.<br />
|-<br />
|valign=top nowrap=true|'''Gatekeeper7'''<br />
|Enables the gatekeeper functionality on version 7,8 and version 9. Which means the gateway VOIP interface type 'Gatekeeper/Registrar' is available.<br />
|}<br />
<br />
===Built in Licenses===<br />
<br />
Since the release of version 7 some hardware platforms already come fully equipped with all necessary interface licenses. The units are:<br />
<br />
* IP22<br />
* IP24<br />
* IP28<br />
* IP302<br />
<br />
This includes also the required ''Channel'' licenses. Built-in licenses are not shown in the ''Licenses'' table in [[Reference7:Administration/Gateway/General|''Gateway / General'']].<br />
<br />
== PBX Licenses ==<br />
<br />
{|<br />
|valign=top nowrap=true|'''PORT9*20'''<br />
|Port License. To register endpoints at PBX objects. This SMB version can not be installed at a slave PBX and can only be used for one device/project. Maximum 20 Ports of this SMB version are possible, for more ports normal port licenses must be added.<br />
|-<br />
|valign=top nowrap=true|'''PORT9'''<br />
|Port License. To register endpoints at PBX objects. Many endpoints can register at one object and only one port license is in use. A port license gets in use when at least one object has a registration. Configuring objects without registration do not need licenses.<br />
|-<br />
|valign=top nowrap=true|'''IPVA9'''<br />
|IPVA License. To allow registrations at the PBX running on IPVA, this license is needed in combination with the '''PORT9''' ('''PORT9*20''') license. As much as PORT9 licenses are in use as much IPVA9 licenses are needed. The IPVA9 license must not be the same size as PORT licenses installed.<br />
|-<br />
|valign=top nowrap=true|'''Mobility9'''<br />
|License to enable Mobility function for a user object.<br />
|-<br />
|valign=top nowrap=true|'''SoftwarePhones9'''<br />
|License to use a innovaphone software phone (not for the Bria softphone)<br />
|-<br />
|valign=top nowrap=true|'''Operator9'''<br />
|License to use the innovaphone operator software.<br />
|-<br />
|valign=top nowrap=true|'''Voicemail9'''<br />
|License to use the innovaphone voicemail script. Must be at least the same as the port license.<br />
|-<br />
|valign=top nowrap=true|'''Standby9'''<br />
|License to enable Standby operation. Must be at least the same as the port license. With this license a PBX accepts registrations from endpoints not configured for this PBX, which should happen only if the PBX where the endpoint is configured for, is not available. A standby license installed without a port license does not do anything.<br />
|-<br />
|valign=top nowrap=true|'''GSM-n'''<br />
|License to use a GSM client of the version n on the GSM phone<br />
|-<br />
|valign=top nowrap=true|'''PBX-QueueMonitor'''<br />
|License to use the [[Howto:PBX-QueueMonitor |PBX queue monitor ]], one license needed per queue monitor.<br />
|-<br />
|valign=top nowrap=true|'''PBX-Reporting9'''<br />
|License to use the [[Reference9:Concept Reporting |reporting application]]. For each object that reports are generated for, a license is needed. The reporting license must not be the same size as the port license.<br />
|-<br />
|}<br />
<br />
Port licenses are used for trunk, executive, gateway ,user and PBX objects (for registering slave and dyn PBXs).<br />
<br />
** Note : If you do any License changing, adding or deleting licenses. The PBX needs an reboot that the license changes become effective.<br />
<br />
==== Example PBX-QueueMonitor====<br />
<br />
This is a concurrent licence, means if one queue monitor connects at the PBX one license is consumed, if the queue monitor is off the licence gets released. Example 1: One waiting queue should be monitored by 5 PBX-queue monitor, so 5 licenses are needed. Example 2: 3 waiting queues, on the first waiting queue 3 PBX queue monitor ,on the second one PBX monitor and on the third no PBX monitor.<br />
So 4 licenses are needed.<br />
<br />
====Example Reporting====<br />
<br />
A PBX with 100 port licenses, but only for the waiting queue and 10 user objects reports should be done. Therefore only 11 reporting licenses need to be purchased.<br />
On the waiting queue and the 10 user objects the reporting chek-mark must be set, then the innovaphone reporting can generate reports for that objects.<br />
<br />
====Example Mobility====<br />
A user object requires a Port license if there is at least one registration on it. A user using a mobility object (that is, a forking destination and a mobility object is defined) requires a Mobility license per destination. A forking destination with no mobility object defined require no Mobility license. The mobility client (which is to be installed on the mobile phone) will require a GSM license.<br />
<br />
So if you create a user object with a VoIP terminal registration and a forking destination with mobility, then you will need 1 Port license and 1 Mobility license. If on the user object there are no registrations but a forking destination with mobility enabled, then it will need 1 Mobility license but no Port license. If there are no registrations and a forking destination without mobility, then no license at all is required.<br />
<br />
The standard configuration (a user object with registrations and a mobility enabled forking destination and a mobile phone with mobile client installed) requires 1 Port plus 1 Mobility plus 1 GSM license.<br />
<br />
In summary you also can have more Mobility lics than you have port lics.<br />
<br />
=== PBX Floating mechanism===<br />
<br />
If no Port license is installed locally on a slave/standby PBX it obtains automatically all PBX licenses from the master. If this option is used, Port licenses need to be installed for the total number of endpoints in the system on the master.<br />
<br />
Slaves with locally installed licenses can be mixed with Slaves obtaining their licenses from the master.<br />
<br />
A slave/standby stores the received license in flash memory so it can still operate even if the master is not available.<br />
<br />
License updates between master and slaves are sent in intervals of approximately 10min to limit the bandwidth usage. Because of this it may happen that temporarily more licenses can be used than actually available.<br />
<br />
It is not necessary/possible to buy floating licenses. You can use them without a balance in my.innovaphone.com. There is no license needed at all to use the floating mechanism.<br />
<br />
=== Licensing for Standby operation ===<br />
<br />
If a PBX shall operate as standby (either as dedicated standby or as a master being standby for a slave, or as a slave being standby for a master), a standby license with at least the value of the Port license must be available. This Standby license can be obtained from the Master by the use of the Floating mechanism.<br />
<br />
==== Examples ====<br />
<br />
'''Dedicated Standby (Standby/Standby-Slave)'''<br />
<br />
No PBX licenses should be installed on the Standby, to obtain the licenses from the master and a Standby license of the correct size has to be installed on the master.<br />
<br />
'''Master acting as Standby'''<br />
<br />
If a master should accept registrations which are configured for slaves, in case the slaves are not available a Standby license of at least the size of the Port licenses needs to be installed on this master.<br />
<br />
'''Slave acting as Standby for Master'''<br />
<br />
If a slave should accept registrations which are not configured for this slave, in case the master is not available, a standby license of at least the size of the Port license must be available on the slave. If the licenses are obtained from the master by the use of the Floating mechanism the Standby license must be installed on the master, if local licenses are used, the standby license must be installed on the slave.<br />
<br />
== DECT Licenses ==<br />
<br />
{|<br />
|valign=top nowrap=true|'''Multicell'''<br />
|The Multicell license enables the Multicell master and defines the System Identification (ARI) on the wireless side, installed on the IP1200.<br />
|}</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:PBX/Config/General&diff=20819Reference9:PBX/Config/General2011-04-12T13:47:44Z<p>Tsr: /* Common */</p>
<hr />
<div>The fundamental operating modes of the PBX are configured on this page. <br />
<br />
== Configuration ==<br />
<br />
=== Common ===<br />
<br />
{|<br />
|valign=top nowrap=true|'''PBX Mode'''<br />
|The PBX operating mode<br />
* '''Off''' - The PBX is disabled. After enabling the PBX a browser refresh is needed to activate additional PBX webpages.<br />
* '''Master''' - The PBX on this device acts as Master. Within a multisite installation exactly one PBX must be configured as Master.<br />
* '''Standby''' - The PBX on this device acts as Standby for the Master. As long as the master is available, this PBX is not active, but just monitors the Master. If the Master is not availabe this PBX is active.<br />
* '''Standby-Slave''' - The PBX on this device acts as Standby for a Slave. As long as the slave is available, this PBX is not active, but just monitors the slave. If the slave is not availabe this PBX is active.<br />
|-<br />
|valign=top nowrap=true|'''System Name'''<br />
| The system Name. On all PBX within a multisite installation the same System Name must be configured. For H.323 endpoints this name is the gatekeeper identifier, for SIP endpoints it is the server name.<br />
|-<br />
|valign=top nowrap=true|'''Use as Domain'''<br />
|Uses the ''System Name'' as domain name, together with the name field in the user object the PBX constructs the email address (used for sending emails out ox myPBX). This mechanism is also used for Federation, to federate with other domains.<br />
|-<br />
|valign=top nowrap=true|'''PBX Name'''<br />
|The name of the PBX on this device. With this name a PBX is associated to a node. The field 'Name' (not Long Name) of a PBX Node object relates to this name.<br />
|-<br />
|valign=top nowrap=true|'''Unknown Registrations'''<br />
|If this checkmark is set, the PBX accepts 'unknown' registrations. This means registrations with no matching object configured. If from an endpoint registered in this way a number of an object is dialed, which has no registration active and no 'HW-ID' configured the name used for the registration is configured as 'HW-ID' of this object. This is an easy way to deploy large numbers of phones.<br />
|-<br />
|valign=top nowrap=true|'''Music On Hold URL'''<br />
|A URL for the Music On Hold. This file is read by the PBX using HTTP and sent to a held endpoint via RTP. The format of this URL is<br />
''<nowiki>http://<addr>/<file>.$coder?coder=g729,g711a,g711u,g723&repeat=true</nowiki>''. <addr> is the IP address of the http server, no dns name is allowed here. <file> is the filename. $coder will be replaced by the actual coder used.<br />
Parameters: ''coder=g729,g711a,g711u,g723'' is the list of available coders. Only these coders must be specified for which a corresponding file exists. ''repeat=true'' should be specified in order to loop the file endlessly. ''random=true'' can be used to start the music on hold on a random point (this will work only if the URL is not local though).<br />
<br />
By default the built-in Music-On-Hold is played (Pseudo URL: "MOH?coder=g729,g711a,g723&repeat=true"). You can also play a dial tone (Pseudo URL "TONE") or a ring-back tone (Pseudo URL "TONE?tone=ringback"). <br />
If you configure a wrong (or invalid) URL then you will have silence as MOH.<br />
<br />
Within the URL %<id> can be used to put in some context information of the call. The information refers to the party which has put the receiving party on hold. For information about the receiving party itself, the id has to be preceeded by '.' (e.g. '''.l''').<br />
<br />
'''l''' Long Name<br />
<br />
'''h''' Name (H.323 id)<br />
<br />
'''n''' Number<br />
<br />
'''N''' Node<br />
<br />
'''P''' PBX<br />
|-<br />
|valign=top nowrap=true|'''External Music On Hold'''<br />
|To offload the device from playing the Music on hold, the Music On Hold can be played by a seperate device. This device can register with a name configured here. To retrieve the Music On Hold a call is sent to this device. For each held endpoint a call is sent.<br />
|-<br />
|valign=top nowrap=true|'''Response Timeout'''<br />
|Global timeout (in seconds) after which any action for no response is taken (e.g. Call Forward on No Response). A timeout configured at any object overrides this value.<br />
|-<br />
|valign=top nowrap=true|'''Dial Complete Timeout'''<br />
|Global timeout (in seconds) after which any action for incomplete dialed number is taken (e.g. incomplete destination at trunk object).<br />
|-<br />
|valign=top nowrap=true|'''No. of Regs w/o Pwd'''<br />
|Number of registration without password authentication which are allowed per user. If 0 is configured no registration without password is possible.<br />
|-<br />
|valign=top nowrap=true|'''Recall Timeout'''<br />
|A value configured here enables recall after transfer. If a call is transfered and not answered within this time, the call is sent back to the transfering endpoint.<br />
|-<br />
|valign=top nowrap=true|'''Pickup Prefix V7'''<br />
|In V7, the pickup prefix is obsolete. Please use the pbx object [[:Reference7:Administration/PBX/Objects/DTMF Features|DTMF Featurecodes]].<br />
|-<br />
|valign=top nowrap=true|'''Enable External Transfer'''<br />
|Unless this checkbox is set any attempt to transfer an external call back to an external destination will result in disconnection of the call.<br />
|-<br />
|valign=top nowrap=true|'''No CLIR on Internal calls'''<br />
|If checked numbers are displayed even if received with presentation restricted. When sending a call presentation restricted can still be set and should be honored by a public network.<br />
|-<br />
|valign=top nowrap=true|'''RTP Proxy'''<br />
|If this checkbox is set, all media traffic is routed thru the PBX. Check this only if you need to have this, since it creates CPU load on the PBX.<br />
|-<br />
|valign=top nowrap=true|'''Generate CDRs'''<br />
|If this checkbox is set, the PBX generates CDRs for all calls. See [[Reference:Call_Detail_Record_CDR_PBX]] for a description of the CDRs.<br />
|-<br />
|valign=top nowrap=true|'''Route Root-Node External Calls to'''<br />
|Destination object (Long Name) of Root-Node external calls. This configuration option is available on the Master or Standby PBX only. Any call call which cannot be terminated inside the PBX is sent to this destination as long as neither the source nor the destination of the call can be associated with a node with a PBX configured. This object must be assigned to this PBX.<br />
|-<br />
|valign=top nowrap=true|'''Route PBX-Node External Calls to'''<br />
|Destination object (Long Name) of PBX-Node external calls. Any call which cannot be terminated inside the PBX is sent to this destination as long as the source nor the destination of the call can be associated with the node of this PBX. If a call is sent from or to an object defined inside the node of this PBX or in a node hierachically below the node of this PBX the call is associated to the node of this PBX. This object must be assigned to this PBX, that is, it has to register to this PBX.<br />
|-<br />
|valign=top nowrap=true|'''Route Internal Calls to'''<br />
|Destination object (Long Name) to which any call is sent for which a PBX internal destination was found, except for those calls that originated from that object. This can be used to apply special routing on PBX internal calls.<br />
|-<br />
|valign=top nowrap=true|'''Escape Dialtone from'''<br />
|The PBX object (Long Name) to which a call is made to get a dialtone if a dialtone is configured for the escape of a node. As above, this object must be assigned to this PBX.<br />
|-<br />
|valign=top nowrap=true|'''Prefix for Intl/Ntl/Subscriber'''<br />
|Prefixes to be used to map International, National and Subscriber numbers.<br />
* '''International Prefix''' (''000'' in Germany).<br />
* '''National Prefix''' (''00'' in Germany).<br />
* '''Subscriber Numbers''' (E.g ''073009'').<br />
|}<br />
<br />
=== Slave PBX ===<br />
<br />
If the PBX is operated in Slave mode, then the Slave PBX section is displayed<br />
{|<br />
|valign=top nowrap=true|'''Master'''<br />
|The IP address of the PBX master<br />
|-<br />
|valign=top nowrap=true|'''Alternate Master'''<br />
|The IP address of an alternative PBX master (standby, if available<br />
|-<br />
|valign=top nowrap=true|'''Password'''<br />
|The password to be used for registration at the Master as configured in the corresponding PBX Object<br />
|-<br />
|valign=top nowrap=true|'''Route Master calls if no Master to'''<br />
|If the master is not available, master calls are sent to this destination<br />
|-<br />
|valign=top nowrap=true|'''Max Calls to Master/No Reroute'''<br />
|This parameter can be used to limit the calls to the master. If a call is sent to the master and there are already calls to/from the master equal to or exceeding this value, the call is rejected if '''No Reroute''' is set or is handled as if the master was not available otherwise.<br />
|-<br />
|valign=top nowrap=true|'''Replication'''<br />
|This parameter allows you to select the replication style for the slave PBX: either ''All'' or ''Local'' (only users that need to be known in this PBX)<br />
|}<br />
The following figure shows the relation between master's PBX object and the slave's configuration. [[Media:PBX-Master-Slave_registration.PNG|Click to view screenshot of Master - Slave registration]]<br />
<br />
For complete replication from master to slave, check also password in [[Reference8:Administration/PBX/Security]]<br />
<br />
=== Standby PBX ===<br />
<br />
If the PBX is operated in Standby mode, then the Standby PBX section is displayed<br />
{|<br />
|valign=top nowrap=true|'''Master'''<br />
|The IP address of the PBX master<br />
|-<br />
|valign=top nowrap=true|'''Replicate from Master'''<br />
|Turns on full replication from the master PBX<br />
|}<br />
The following figure shows the relation between master and the standby unit's configuration. [[Media:PBX-Standby_General.PNG|Click to view screenshot of Master - Standby registration]]<br />
<br />
For complete replication from master to standby, check also password in [[Reference8:Administration/PBX/Security]]<br />
<br />
== License Status ==<br />
<br />
=== Licenses ===<br />
<br />
A list of all installed PBX license with their current usage is displayed here.<br />
<br />
{|<br />
|valign=top nowrap=true|'''Count'''<br />
|The total number of installed licenses of this type.<br />
|-<br />
|valign=top nowrap=true|'''Usage'''<br />
|The total usage of this license type<br />
|-<br />
|valign=top nowrap=true|'''Local'''<br />
|The usage of this license on this PBX<br />
|-<br />
|valign=top nowrap=true|'''Slaves'''<br />
|The usage of this license on PBX's registered to this PBX.<br />
|}<br />
<br />
see [[Reference8:Licenses]] for a description of the licenses.<br />
<br />
=== Registrations ===<br />
<br />
The current number of registrations and the limit as defined by the base license is displayed here. Because this limit is defined by the base license it includes any registrations because of standby as well, which require no registration license.</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:PBX/Objects&diff=20818Reference9:PBX/Objects2011-04-12T13:33:09Z<p>Tsr: /* General Object Properties */</p>
<hr />
<div>This page is used for the administration of PBX objects. A list of already configured objects can be displayed filtered by various criterias. New objects can be created and existing objects can be changed or deleted.<br />
<br />
== Display of existing Objects ==<br />
By pressing the show link, existing objects are displayed. With the filter field (the input field left to the show link) the displayed objects are limited to those matching the filter. The filter is first applied to the 'Long Name' of the objects meaning a non case sensitive head match of the filter and the 'Long Name' is performed. If there are matching objects these are displayed.<br />
<br />
If there are no matching objects the filter is used to match the Number of the objects including any node prefixes. This way objects of a given node with all subnodes can be displayed by entering the prefix of a node here.<br />
<br />
Below the filter input field is a list of all PBXs in the system (at least the part of the system which is replicated to this device). By clicking on a PBX in the list only the objects which are assigned to this PBX are displayed and the groups configured on this PBX are displayed as well. By clicking on a group only the members of this group are displayed.<br />
<br />
=== List of Objects ===<br />
On the right side the list of objects is displayed. The most important configuration properties are displayed in this list to provide an overview. To view the full configuration of a given object it must be opened for editing by clicking the Long Name. The list can be sorted by clicking the table headers.<br />
<br />
The Number of the objects in this list is not the number configured in the object but it is expanded with the prefixes of the nodes in which the object is configured.<br />
<br />
Group memberships and Call Forwarding for an object are changed by clicking on the 'Groups' or 'CF*' link of the object. A '*' appended to a group displayed in this list means that the active flag of this group membership is set.<br />
A '!' appended to a group displayed in this list means that group indications are configured for this group.<br />
<br />
Fork number appended by a '*' indicates a mobility enabled user. In case the number is displayed in grey, the user consumes no mobility license on local PBX (e.g. because the user registers on other PBX).<br />
<br />
The last column are the IP addresses of registered endpoints for a given object. If the physical location of the endpoint is not the same as the PBX, the physical location is indicated by @<physical-location> added to the IP address. A '*' appended to this field means that this is an password authenticated registration.<br />
Registrations which are because of a standby situation, which means they are not at the PBX for which they are configured, are marked with a special colour (by default this is red).<br />
<br />
=== New Objects ===<br />
New objects are created by selecting the type of object in the drop down list and clicking the new link. If the list of displayed objects is limited to a PBX/Group (see above), the PBX property of the new object is preset accordingly and the group membership is added to the object.<br />
<br />
== General Object Properties ==<br />
<br />
Some configuration properties are specific to the type of object, some are common to all objects. Not each object type supports all general configuration properties.<br />
<br />
;Description: Any text which can be used to describe the objects. Nothing is done with this text on the PBX.<br />
<br />
;Hide from LDAP: When this checkmark is set, this object is available with a read-only LDAP access, which means it does not show up in the PBX phonebook on the phones.<br />
<br />
;Long Name: This name is used to identify the object in the database and for display purposes. The long name must be unique throughout the system. For practical reasons, you should limit it to ''20 - extension length'' characters. <br />
<br />
;Name: The name of the object. This name is used for signalling (like a call number) and must be unique throughout the system. The character '@' should not be used.<br />
;: Note that from V8 on, clients ''cannot'' use the '''Name''' property as registration name. They must use one of the devices. Likewise, for those objects that have a '''Number''' property, when a registration is attempted using this number, the corresponding object is looked up, the '''Name''' property retrieved and a registration tried. As a result, the registration will fail if the object does not have a device with a hardware-id identical to the objects '''Name'''.<br />
* Note: from V9 it is recommended to use the ''Name'' field for the email address (everything prior the @) in combination with the ''Use as Domain'' flag at the System Name. <br />
With that configuration you can send emails out of the myPBX client buddy list to other PBX members. The PBX creates then the email address from the name field and system name.<br />
<br />
;Hardware ID: The Hardware Id from v7 is replaced by the Devices configuration.<br />
<br />
;Number: The telephone number of the object. This is the number by which this object can be dialed within the same node. Which means it does not include any Node prefixes.<br />
<br />
;Critical: If marked as critical the object can only be changed by administrators allowed to edit critical objects<br />
<br />
;Password / Retype Password: If a registration password is allocated here, then it must be specified during registration, or otherwise the registration will fail.<br />
<br />
;Node: The node that the object is assigned to. A Node hierarchy can be configured using Node Objects. Objects which are assigned to the same node can call each other with just the number. To call an object in a different node escapes and node prefixes have to be used. If no node is configured, the object is assigned to the node of the respective local pbx.<br />
<br />
;PBX: The PBX that the object is assigned to. This PBX accepts registrations for the object. If no PBX is configured, the object is assigned to the respective local PBX.<br />
<br />
;Reject ext. Calls: Calls from external sources to this object are rejected.<br />
<br />
;Local: Marks an object as local. Local means that it can be called from endpoints physically located at the same PBX without prefixes even if the calling endpoint is in a different node. Where the endpoint is physical located is defined by the PBX the endpoint contacts first (it may be redirected to another PBX then for registration). If the object does not have a PBX configured the call is routed to the PBX where the calling endpoint is registered.<br />
<br />
;Send Number: If an object does a call, the calling party number for this call will be replaced by the number given (if any). Used to hide an extension. Currently works for non-gateway object types only.<br />
<br />
;URL: A url configured here is send with any call from this object as source url. Only H.323 support sending a URL. Some called endpoints may make use of the URL. The URL is also availabe within the CDRs generated by the gateway.<br />
<br />
;Group Indications: The group for which group indications are sent to the registered endpoints. The object must be active member in this group. The other objects (for which group indications are sent) need not to be active. To monitor other endpoints on a phone with a Partner/Pickup function key group indications are needed for the endpoints. The maximal length of the Group Indication Name in V7 is set to 48 characters.<br />
<br />
== Devices ==<br />
<br />
With the devices configuration it is possible to identify the different devices, which may register for a user. The Hardware Id is used to match the incoming registration. The Text can be used for a description of the device. On the SOAP/TAPI interface Text can be used to let the user select the device which shall be controlled. If no device is configured the Name and v7 Hardware Id are used for default devices to ensure v7 configuration compatibility.<br />
<br />
To allow an endpoint to register with the objects Name or Number, a device must be configured with a hardware id identical to the object Name.<br />
<br />
=== Security issues ===<br />
<br />
There are security build in mechanisms :<br />
<br />
* If the '''AdminPwd''' check-mark is set, registration to this device is only possible with the PBX password, which is configured in PBX/Config/Security.<br />
<br />
* If this object will have no registration, leave the device field empty (for security reasons). Nobody can abuse and register at that object.<br />
<br />
* If a registration request comes with the wrong password the object deny´s '''all''' registration requests (with the reason REGISTER-REJ : Reason=PBX missing Authentication) for 20 seconds. After that time it is possible to register (with the right password).<br />
<br />
== Objects with empty node or PBX ==<br />
If an object has no '''PBX''' configured, it will be replicated (if replication is turned on) to all slaves. Furthermore, any PBX will satisfy incoming registration requests. Calls to such objects that are built-in to the PBX and thus do not require a registration to work (e.g. Waiting Queue) will be processed by each PBX the call is presented to.<br />
<br />
If an object has no '''Node''' configured, it will be considered to live in the node of each PBX is known to. So if an object has neither '''Node''' nor '''PBX''' configured, it will be present in all nodes that have a PBX and calls to such objects will be processed locally for objects that are built-in to the PBX.<br />
<br />
== PBX Object Types ==<br />
<br />
{{Special:Prefixindex/Reference9:PBX/Objects}}</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:PBX/Objects&diff=20817Reference9:PBX/Objects2011-04-12T13:32:33Z<p>Tsr: /* General Object Properties */</p>
<hr />
<div>This page is used for the administration of PBX objects. A list of already configured objects can be displayed filtered by various criterias. New objects can be created and existing objects can be changed or deleted.<br />
<br />
== Display of existing Objects ==<br />
By pressing the show link, existing objects are displayed. With the filter field (the input field left to the show link) the displayed objects are limited to those matching the filter. The filter is first applied to the 'Long Name' of the objects meaning a non case sensitive head match of the filter and the 'Long Name' is performed. If there are matching objects these are displayed.<br />
<br />
If there are no matching objects the filter is used to match the Number of the objects including any node prefixes. This way objects of a given node with all subnodes can be displayed by entering the prefix of a node here.<br />
<br />
Below the filter input field is a list of all PBXs in the system (at least the part of the system which is replicated to this device). By clicking on a PBX in the list only the objects which are assigned to this PBX are displayed and the groups configured on this PBX are displayed as well. By clicking on a group only the members of this group are displayed.<br />
<br />
=== List of Objects ===<br />
On the right side the list of objects is displayed. The most important configuration properties are displayed in this list to provide an overview. To view the full configuration of a given object it must be opened for editing by clicking the Long Name. The list can be sorted by clicking the table headers.<br />
<br />
The Number of the objects in this list is not the number configured in the object but it is expanded with the prefixes of the nodes in which the object is configured.<br />
<br />
Group memberships and Call Forwarding for an object are changed by clicking on the 'Groups' or 'CF*' link of the object. A '*' appended to a group displayed in this list means that the active flag of this group membership is set.<br />
A '!' appended to a group displayed in this list means that group indications are configured for this group.<br />
<br />
Fork number appended by a '*' indicates a mobility enabled user. In case the number is displayed in grey, the user consumes no mobility license on local PBX (e.g. because the user registers on other PBX).<br />
<br />
The last column are the IP addresses of registered endpoints for a given object. If the physical location of the endpoint is not the same as the PBX, the physical location is indicated by @<physical-location> added to the IP address. A '*' appended to this field means that this is an password authenticated registration.<br />
Registrations which are because of a standby situation, which means they are not at the PBX for which they are configured, are marked with a special colour (by default this is red).<br />
<br />
=== New Objects ===<br />
New objects are created by selecting the type of object in the drop down list and clicking the new link. If the list of displayed objects is limited to a PBX/Group (see above), the PBX property of the new object is preset accordingly and the group membership is added to the object.<br />
<br />
== General Object Properties ==<br />
<br />
Some configuration properties are specific to the type of object, some are common to all objects. Not each object type supports all general configuration properties.<br />
<br />
;Description: Any text which can be used to describe the objects. Nothing is done with this text on the PBX.<br />
<br />
;Hide from LDAP: When this checkmark is set, this object is available with a read-only LDAP access, which means it does not show up in the PBX phonebook on the phones.<br />
<br />
;Long Name: This name is used to identify the object in the database and for display purposes. The long name must be unique throughout the system. For practical reasons, you should limit it to ''20 - extension length'' characters. <br />
<br />
;Name: The name of the object. This name is used for signalling (like a call number) and must be unique throughout the system. The character '@' should not be used.<br />
;: Note that from V8 on, clients ''cannot'' use the '''Name''' property as registration name. They must use one of the devices. Likewise, for those objects that have a '''Number''' property, when a registration is attempted using this number, the corresponding object is looked up, the '''Name''' property retrieved and a registration tried. As a result, the registration will fail if the object does not have a device with a hardware-id identical to the objects '''Name'''.<br />
* Note: from V9 it is recommended to use the ''Name'' field for the email address (everything prior the @) in combination with the ''Use as Domain'' flag at the System Name. With that configuration you can send emails out of the myPBX client buddy list to other PBX members. The PBX creates then the email address from the name field and system name.<br />
<br />
;Hardware ID: The Hardware Id from v7 is replaced by the Devices configuration.<br />
<br />
;Number: The telephone number of the object. This is the number by which this object can be dialed within the same node. Which means it does not include any Node prefixes.<br />
<br />
;Critical: If marked as critical the object can only be changed by administrators allowed to edit critical objects<br />
<br />
;Password / Retype Password: If a registration password is allocated here, then it must be specified during registration, or otherwise the registration will fail.<br />
<br />
;Node: The node that the object is assigned to. A Node hierarchy can be configured using Node Objects. Objects which are assigned to the same node can call each other with just the number. To call an object in a different node escapes and node prefixes have to be used. If no node is configured, the object is assigned to the node of the respective local pbx.<br />
<br />
;PBX: The PBX that the object is assigned to. This PBX accepts registrations for the object. If no PBX is configured, the object is assigned to the respective local PBX.<br />
<br />
;Reject ext. Calls: Calls from external sources to this object are rejected.<br />
<br />
;Local: Marks an object as local. Local means that it can be called from endpoints physically located at the same PBX without prefixes even if the calling endpoint is in a different node. Where the endpoint is physical located is defined by the PBX the endpoint contacts first (it may be redirected to another PBX then for registration). If the object does not have a PBX configured the call is routed to the PBX where the calling endpoint is registered.<br />
<br />
;Send Number: If an object does a call, the calling party number for this call will be replaced by the number given (if any). Used to hide an extension. Currently works for non-gateway object types only.<br />
<br />
;URL: A url configured here is send with any call from this object as source url. Only H.323 support sending a URL. Some called endpoints may make use of the URL. The URL is also availabe within the CDRs generated by the gateway.<br />
<br />
;Group Indications: The group for which group indications are sent to the registered endpoints. The object must be active member in this group. The other objects (for which group indications are sent) need not to be active. To monitor other endpoints on a phone with a Partner/Pickup function key group indications are needed for the endpoints. The maximal length of the Group Indication Name in V7 is set to 48 characters.<br />
<br />
== Devices ==<br />
<br />
With the devices configuration it is possible to identify the different devices, which may register for a user. The Hardware Id is used to match the incoming registration. The Text can be used for a description of the device. On the SOAP/TAPI interface Text can be used to let the user select the device which shall be controlled. If no device is configured the Name and v7 Hardware Id are used for default devices to ensure v7 configuration compatibility.<br />
<br />
To allow an endpoint to register with the objects Name or Number, a device must be configured with a hardware id identical to the object Name.<br />
<br />
=== Security issues ===<br />
<br />
There are security build in mechanisms :<br />
<br />
* If the '''AdminPwd''' check-mark is set, registration to this device is only possible with the PBX password, which is configured in PBX/Config/Security.<br />
<br />
* If this object will have no registration, leave the device field empty (for security reasons). Nobody can abuse and register at that object.<br />
<br />
* If a registration request comes with the wrong password the object deny´s '''all''' registration requests (with the reason REGISTER-REJ : Reason=PBX missing Authentication) for 20 seconds. After that time it is possible to register (with the right password).<br />
<br />
== Objects with empty node or PBX ==<br />
If an object has no '''PBX''' configured, it will be replicated (if replication is turned on) to all slaves. Furthermore, any PBX will satisfy incoming registration requests. Calls to such objects that are built-in to the PBX and thus do not require a registration to work (e.g. Waiting Queue) will be processed by each PBX the call is presented to.<br />
<br />
If an object has no '''Node''' configured, it will be considered to live in the node of each PBX is known to. So if an object has neither '''Node''' nor '''PBX''' configured, it will be present in all nodes that have a PBX and calls to such objects will be processed locally for objects that are built-in to the PBX.<br />
<br />
== PBX Object Types ==<br />
<br />
{{Special:Prefixindex/Reference9:PBX/Objects}}</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Howto:Feature_List_in_English&diff=20816Howto:Feature List in English2011-04-12T12:53:33Z<p>Tsr: /* New in V9 */</p>
<hr />
<div>innovaphone feature list<br />
<br />
<!-- featurelist --><br />
==Applies to==<br />
<br />
This information applies to<br />
<br />
− All innovaphone products based on V7, V8 and V9<br />
<br />
<br />
==Download==<br />
<br />
[[Media:innovaphone_V8_Featurelist_en.pdf]]<br />
<br />
==More information==<br />
<br />
<br />
<br />
===System Features – IP302 / IP305 / IP800 / IP2000 / IP6000 /IP1060 / IP3010 / IP6010 / IPVA===<br />
<br />
Access to exchange via group number <br />
<br />
Access to separate exchange via individual number <br />
<br />
ACD groups <br />
<br />
Active Directory Replication <br />
<br />
Administration via uniform interface <br />
<br />
Alarm and error events <br />
<br />
Alternate route selection <br />
<br />
Announcement before pickup (*) <br />
<br />
Announcements (*) <br />
<br />
Authorisation groups (class of service) <br />
<br />
Automatic break through for call protection for preferred numbers <br />
<br />
Automatic call distribution (ACD) <br />
<br />
Automatic night switching with week clock <br />
<br />
Automatic route selection (ARS) <br />
<br />
Bootcode with minifirmware (not supported with IP3000) <br />
<br />
Branches (virtual central PBX) <br />
<br />
Bunched circuit <br />
<br />
Call back <br />
<br />
Call back also if internal call <br />
<br />
Call detail recording (CDR) <br />
<br />
Calling line identification restriction (CLIR) <br />
<br />
Calling party identification (CLIP) <br />
<br />
Calling to E.164 <br />
<br />
Calling via ENUM (H.323 and SIP) <br />
<br />
Call Detail Records (CDR) external and internal <br />
<br />
centralized backup /firmware/config upload<br />
<br />
Circle call with circle call query (#) <br />
<br />
Clock synchronization via IP <br />
<br />
Config templates for PBX User <br />
<br />
Configurable tones <br />
<br />
Configure / change / delete call diversion via web <br />
<br />
Conversation return to operator <br />
<br />
Cross connection via IP <br />
<br />
Cross connection via ISDN <br />
<br />
Different call (external, internal) <br />
<br />
Direct dial (with and without number reassessment) <br />
<br />
Door bell interface with door opener function (#) <br />
<br />
DTMF detection disabling <br />
<br />
DTMF-post dial/direct dial <br />
<br />
Emigration of endpoint <br />
<br />
Enhanced error reporting (SIP, QOS parameter, router error reporting)<br />
<br />
Enhanced H.323 features according to H.450.x <br />
<br />
Extended DTMF Object (feature set via DTMF dial) <br />
<br />
External communication <br />
<br />
Firmware upload in DRAM (not supported with IP3000) <br />
<br />
Floating license model <br />
<br />
Flexible dial plan <br />
<br />
General night switching <br />
<br />
Group call (all, circular)<br />
<br />
Hide Objects from LDAP<br />
<br />
Home office integration <br />
<br />
HTTP/ HTTPS allowed stations<br />
<br />
Incoming direct call to subscriber or group <br />
<br />
Interactive call acceptance (*) <br />
<br />
Interface for external announcement construction (#) <br />
<br />
Internal communication <br />
<br />
Internal music on hold <br />
<br />
Least cost routing (LCR) <br />
<br />
Log forwadring<br />
<br />
LDAP replication<br />
<br />
Message center (H.450.7 or DTMF) <br />
<br />
Message Waiting Indication (MWI) <br />
<br />
Messaging <br />
<br />
Messaging (SIP and H.323) <br />
<br />
Mixed dial method (overlap and en-block dialing) <br />
<br />
MS-chap V1/V2 <br />
<br />
Multi conferencing (IP800, IP6000, IP0010, IP1060, IP3010, IP6010) <br />
<br />
Multi protocol (H.323, SIP) <br />
<br />
Multilevel admin access (detailed multilevel user rights for the PBX configuration) <br />
<br />
Multiple system admin (multiple admin and viewer rights possible for the whole system) <br />
<br />
Multistage login (multi-user) <br />
<br />
Music / announcement in standby from analogue resource (#) <br />
<br />
Music / announcement in standby from HTTP resource (*) <br />
<br />
Network wide features (Master/slave with virtual PBX) <br />
<br />
Only calling to registered subscribers (passive control) <br />
<br />
Overflow of subscribers and cross connection <br />
<br />
Overlapped sending <br />
<br />
PBX directory search (LDAP search via DTMF) <br />
<br />
Phonebook either from internal or from external source (LDAP) <br />
<br />
QSIG <br />
<br />
QSIG inter-working <br />
<br />
QSIG trunking (point to point and point to multipoint) <br />
<br />
Redundancy of the ISDN-lines <br />
<br />
Redundancy of the PBX <br />
<br />
Remote monitoring and remote diagnostics <br />
<br />
Remote software upgrade <br />
<br />
RTP Proxy <br />
<br />
SDP Transit (for video and other codecs) <br />
<br />
Short dial (individual, group, system wide) <br />
<br />
Silent intrusion <br />
<br />
SIP Medial Relay (RTP stream routing via gateway) <br />
<br />
SIP trunking <br />
<br />
SIP via TCP<br />
<br />
SIPS (SIP-Secure) – SIP via TCP/TLS (not supported with IP3000) <br />
<br />
SNMP Traps (alarm events) <br />
<br />
SOAP-API <br />
<br />
SRTP (Voice encryption) for H.323 and SIP (not supported with IP3000) <br />
<br />
Subscriber authorisation<br />
<br />
Standard protocols to the endpoint <br />
<br />
Subscriber groups with progressive call (parallel, circular, sequential)<br />
<br />
Switch between day/night with code digit from subscribers <br />
<br />
System time/date via timeserver (LAN or web) <br />
<br />
TAPI / Multi line TAPI (via several PBX’s / locations)<br />
<br />
Telephone number assignment <br />
<br />
Time based subscriber authorisation<br />
<br />
Twin Phones <br />
<br />
US standard (T1 and CAS) <br />
<br />
VoIP-CAPI<br />
<br />
Waiting queue – call busy operators / CFU disable operators <br />
<br />
802.1x<br />
<br />
==== New in V8 ====<br />
<br />
Announcing the queue position in a waiting queue <br />
<br />
Callback on busy/free to ISDN <br />
<br />
Customized Visual Appearance (individually designable user interface)<br />
<br />
Dual Forking (OCS Integration) <br />
<br />
Dynamic PBX (more PBXs on one Device ) PBX hosting / PBX virtualization <br />
<br />
Kerberos based authentication and Cross Realm authentication<br />
<br />
Mobility (GSM integration) <br />
- Call-waiting <br />
- hold <br />
- transfer <br />
- park <br />
- group login/logout <br />
- mobility on/off <br />
- setting presence status <br />
<br />
Off load Dialtone (external gateway)<br />
<br />
Off load Media Relay (external gateway) <br />
<br />
Off load MOH (external gateway)<br />
<br />
Presence <br />
<br />
Recording at the ISDN and analogue interfaces <br />
<br />
Roaming Phone Profiles <br />
<br />
RSTP (Rapid Spanning Tree) <br />
<br />
Send Message to group <br />
<br />
SIP error detection (alarm/event updated) <br />
<br />
SIP Federation <br />
<br />
SIP video multisite support<br />
<br />
====New in V9====<br />
<br />
Executive/secretary enhancements<br />
<br />
* Secretary can initiate calls with the CLIP from the executive. <br />
<br />
* Executive can see if the secretary is joined or unjoined in the primary secretary group. <br />
<br />
* Executive sees if a call diversion is set at the secretary.<br />
<br />
* Breakthrough disabled call waiting at secretary.<br />
<br />
Reporting <br />
<br />
* Based on plattform IP1060, IP3010, IP6010, or external Linux platform- innovaphone Application platform.<br />
* Based on PBX CDR´s<br />
* Predefined filter<br />
* Reports (export as PDF, XML) from filter, combined filter, date and time<br />
<br />
UC client (myPBX) web-based and Windows launcher<br />
<br />
''Languages supported: Danish / English / Estonian / Finnish / French / Italian / Latvian / Dutch / Norwegian / Polish / Portuguese / Spanish / Swedish / Czech – additional languages on demand.''<br />
<br />
* CTI (initiate call, accept call, terminate call, hold call, retrieve call, transfer call, park call, 3PTY conference)<br />
* Manage own call diversions<br />
* Call list<br />
* Presence (manage own presence state)<br />
* Buddylist (including partners presence and call status)<br />
* Chat (multiparty chat)<br />
* Audioconference (via innovaphone audio conference Interface)<br />
* Videoconferece (via integration of Webex or Microsoft OLM)<br />
* Application sharing (via integration of Webex or Microsoft OLM)<br />
<br />
Emergency calls priority<br />
<br />
Import/Export PBX user database (CSV/XML)<br />
<br />
Individual MOH (context sensitive based on object, node or PBX)<br />
<br />
IP filter for registrations with or without password <br />
<br />
IPv6 support (IPv6 routing, 6to4 routing and http access, telnet)<br />
<br />
LDAP via TLS<br />
<br />
MTLS <br />
<br />
NTP redundancy<br />
<br />
Partnerkeys via separate Pbx´s<br />
<br />
Wideband audio (IP0010, IP1060, IP3010, IP6010)<br />
<br />
===Features IP Phones – IP110 / IP200 / IP230 / IP240 / IP240-1000 / IP241 / IP222 / IP232===<br />
<br />
Adjustable loudness <br />
<br />
Adjustable ringing tones also possible, import RTTTL and midi files <br />
<br />
Alphanumeric phonebook <br />
<br />
Announcement via loudspeaker <br />
<br />
Automatic callback on busy and free <br />
<br />
Automatic redialing <br />
<br />
Automatic redialing to busy bunched circuit <br />
<br />
Blind transfer <br />
<br />
Call diversion to internal phone number <br />
<br />
Call hold / retrieve call diversion to external phone number <br />
<br />
Call intrusion <br />
<br />
Call list (outgoing, incoming, combined, not reached, not answered)<br />
<br />
Call park and enquiry from other subscribers <br />
<br />
Call prevention <br />
<br />
Call transfer / pickup (selective and from a group)<br />
<br />
Call waiting (acoustical and optical signaling of waiting calls)<br />
<br />
Caller identification (name/number) <br />
<br />
Changeover of the assigned partners <br />
<br />
Conference (3 way) <br />
<br />
Configuration of the voice recording via HTTP<br />
<br />
Connect to busy and free subscribers without notification <br />
<br />
Counter and list of missed calls <br />
<br />
Date and time display (automatic summer/winter time adjustment) <br />
<br />
Delete call back <br />
<br />
Delete variable call diversion <br />
<br />
Dialing an IP address (with and without RAS) <br />
<br />
Dialing with code key from an unauthorized phone <br />
<br />
Direct dialing (immediate, internal/external)<br />
<br />
Display duration of call <br />
<br />
Display calling number <br />
<br />
Emigration of subscriber/endpoint <br />
<br />
Fixed call diversion (unconditional, no answer (time adjustable) on busy)<br />
<br />
Forced announcement (priority call) <br />
<br />
Function keys – multitude possible – exact list can be found in the technical specification of each IP phone <br />
<br />
Hands free <br />
<br />
Headset <br />
<br />
Individual configuration <br />
<br />
Individual phonebook <br />
<br />
Intercom with automatic call pick up <br />
<br />
Interlinked and limitless multiple conference <br />
<br />
Manager/assistant feature <br />
<br />
Message waiting indication (MWI) <br />
<br />
Messaging <br />
<br />
Multi language <br />
<br />
Multi-protocol and multi-registration (SIP and H.323 concurrent)<br />
<br />
Multiple registrations with selective de-registration <br />
<br />
Mute (switch off the microphone) <br />
<br />
Name dialing <br />
<br />
Open listening <br />
<br />
Over plugging (connect call to a busy subscriber) <br />
<br />
Phone lock <br />
<br />
Preferred subscribers <br />
<br />
Project code <br />
<br />
Redialing of the last 100 dialed numbers <br />
<br />
Silent Intrusion <br />
<br />
SIP via TCP <br />
<br />
SIPS (Secure SIP via TCP/TLS) <br />
<br />
SRTP (SIP and H.323) <br />
<br />
Status indication of the subscriber (free/busy/call) <br />
<br />
Subscriber with several lines <br />
<br />
Subscriber with several numbers <br />
<br />
Transfer with consultation <br />
<br />
Variable call diversion <br />
<br />
802.1x<br />
<br />
==== New in V9 ====<br />
<br />
Colour display (IP241 / IP222 / IP232)<br />
<br />
Individual background picture (IP241 / IP222 / IP232)<br />
<br />
Individual audible signal for announcement calls /multicast announcements and messaging<br />
<br />
802.3az (IP222 / IP232)<br />
<br />
Wideband audio (IP222 / IP232)<br />
<br />
===Features: Analogue phones – IP302 / IP22 / IP24 / IP28, DECT phones – IP52 / IP54 / IP55 / IP65, ISDN phone – IP800===<br />
<br />
Call completion on busy <br />
<br />
Call completion on free <br />
<br />
Call diversion to internal/external number <br />
<br />
Call hold/retrieve <br />
<br />
Call park and enquiry from other subscribers <br />
<br />
Call protection <br />
<br />
Call transfer/pickup (selective and from a group)<br />
<br />
Call waiting (acoustic and optical signal of the waiting call)<br />
<br />
Clip to an analogue phone <br />
<br />
Confirmation tone (positive and negative) <br />
<br />
Connect to a free and busy subscriber without notification <br />
<br />
Delete variable call diversion <br />
<br />
Dial with code key from an unauthorized phone <br />
<br />
Direct dial immediate (internal, external)<br />
<br />
Do not disturb (internal and external calls)<br />
<br />
Fixed call diversion; unconditional, no answer (time adjustable), on busy <br />
<br />
Lock phone <br />
<br />
Message Waiting Indication (MWI) on DECT Phones<br />
<br />
Preferred subscriber <br />
<br />
Project code <br />
<br />
SIP via TCP <br />
<br />
SIPS (Secure SIP via TCP/TLS) <br />
<br />
Special tone when active feature <br />
<br />
SRTP (SIP and H.323) <br />
<br />
Transfer with consultation <br />
<br />
Variable call diversion <br />
<br />
802.1x<br />
<br />
===Features innovaphone Voice mail (*)===<br />
<br />
''Languages supported: German / English / Italian / French / Dutch / Spanish / Norwegian / Danish / Polish /Swedish / Czech – additional languages on demand.''<br />
''Voicemail runs on Compact Flash (CF slot in IP800, IP305, IP302, IP2000, IP6000, IP1060, IP3010, IP6010) or on external Web Server''<br />
<br />
Email notification (with or without attachment) <br />
<br />
Listen to/delete /store voice mails by means of DTMF input <br />
<br />
MWI (according to H.450.7) <br />
<br />
Personal greeting message <br />
<br />
Voice recording <br />
<br />
==== New in V9 ====<br />
<br />
Voicemail support SRTP<br />
<br />
===Features Operator (V8) software based===<br />
<br />
''Localized versions: German / English / Italian / Dutch – additional languages on demand''<br />
<br />
Busylampfield (divided into groups) <br />
<br />
Call journal <br />
<br />
Call transfer (with/without consultation (blind)) <br />
<br />
Drag&Drop or with keypad use <br />
<br />
Integrated help <br />
<br />
Monitor blind transferred calls <br />
<br />
Monitor of waiting queue <br />
<br />
Name display for incoming calls in LDAP directory <br />
<br />
Park/unpark <br />
<br />
Send messages to PBX users <br />
<br />
Searching within a LDAP directory <br />
<br />
Searching for PBX users in all PBX´s <br />
<br />
Set/change call forward for all PBX users <br />
<br />
Set/change presence status for all PBX users <br />
<br />
Show busy state <br />
<br />
Show call forward <br />
<br />
Show current call<br />
<br />
Show presence status <br />
<br />
State-of-the-art user interface <br />
<br />
Support of Master/Slave scenarios<br />
<br />
===Features Operator Phone – IP230 / IP240 / IP240-1000 / IP241 / IP222 / IP232===<br />
<br />
''Phone can be used as standalone Operator or in combination with the software based Operator''<br />
<br />
Adjustable volume <br />
<br />
Adjustable ringing tones also possible, import RTTTL and midi files<br />
<br />
Alphanumeric phonebook <br />
<br />
Announcement via loudspeaker <br />
<br />
Automatic callback on busy and free <br />
<br />
Automatic redialing <br />
<br />
Automatic redialing to busy bunched circuit <br />
<br />
Blind transfer <br />
<br />
Busy indicator lamp <br />
<br />
Call back (enquiry) <br />
<br />
Call back delete <br />
<br />
Call back on busy subscriber <br />
<br />
Call back to free/busy subscriber <br />
<br />
Call diversion to external phone number <br />
<br />
Call diversion to internal phone number <br />
<br />
Call hold/retrieve <br />
<br />
Call intrusion <br />
<br />
Call list (outgoing, incoming, not reached, not answered)<br />
<br />
Call parking and enquiry from other subscribers <br />
<br />
Call prevention <br />
<br />
Call transfer/pickup (selective and from a group)<br />
<br />
Call waiting (acoustical and optical signaling of waiting calls)<br />
<br />
Changeover day/night with status on phone display <br />
<br />
Changeover of the assigned partner <br />
<br />
Conference (3 way) <br />
<br />
Configuration of the Voice recording via HTTP <br />
<br />
Connect to busy and free subscribers without notification <br />
<br />
Date and time on display (automatic summer/winter time adjustment) <br />
<br />
Delete variable call diversion <br />
<br />
Dialing an IP address (with and without RAS) <br />
<br />
Dialing with code key from an unauthorised phone <br />
<br />
Different ringing tones (internal/external) <br />
<br />
Direct dialing; immediate internal/external <br />
<br />
Display duration of call <br />
<br />
Display calling number <br />
<br />
Emigration of the subscriber/endpoint <br />
<br />
Fixed call diversion; unconditional, no answer (time adjustable) on busy <br />
<br />
Forced announcement (priority call) <br />
<br />
Function keys – multitude possible – exact list can be found in the technical specification of each IP phone <br />
<br />
Hands free <br />
<br />
Headset protocol DHSG <br />
<br />
Headset and handset parallel and autonomous <br />
<br />
Identification of the caller (name/number) <br />
<br />
Individual configuration <br />
<br />
Individual phonebook <br />
<br />
Intercom with automatic call acceptance <br />
<br />
Manager/assistant feature <br />
<br />
Message waiting indication (MWI) <br />
<br />
Messaging <br />
<br />
Multi language <br />
<br />
Multi protocol and multi-registration (SIP and H.323 concurrent) <br />
<br />
Multiple conference interlinked and limitless <br />
<br />
Multiple operators <br />
<br />
Multiple registrations with selective de-registration <br />
<br />
Mute (switch off the microphone) <br />
<br />
Name dialing <br />
<br />
Open listening <br />
<br />
Over plugging (connect call to a busy subscriber) <br />
<br />
Phone lock <br />
<br />
Preferred subscriber <br />
<br />
Project code<br />
<br />
Redialing of the last 100 dialed numbers <br />
<br />
Rush display (0-4) <br />
<br />
Silent Intrusion <br />
<br />
SIP via TCP <br />
<br />
SIPS (Secure SIP via TCP/TLS) <br />
<br />
SRTP (SIP and H.323) <br />
<br />
Status indication of the subscriber (free, busy, call) <br />
<br />
Subscriber with several lines <br />
<br />
Subscriber with several numbers <br />
<br />
Telephone book <br />
<br />
Transfer of the subscriber phone number <br />
<br />
Transfer with consultation <br />
<br />
Variable call diversion <br />
<br />
802.1x<br />
<br />
===Features Interactive Voice Response (IVR) (*)===<br />
<br />
Announcements depending on the caller (e.g. automatic or manual language selection) <br />
<br />
Call handling according to lines and/or calling number (CLI)<br />
<br />
Listen to the menu also from internal subscribers <br />
<br />
Multi level menu <br />
<br />
Overflow from the operator to an automatic operator <br />
<br />
Voice menu at extension (if no answer, busy, unconditional) <br />
<br />
Voice menu with information and automatic dialing <br />
<br />
Voice menu with predefined destinations <br />
<br />
Voice menu with manual dialing of the destination (DTMF) <br />
<br />
<br />
==== New in V8====<br />
<br />
Announcing the queue position in a waiting queue <br />
<br />
<br />
<br />
<br />
Note: <br />
<br />
(*) PC with WIN XP (web server) required or via Compact Flash (CF slot in IP800, IP305, IP302, IP2000, IP6000) <br />
<br />
(#) innovaphone IP21 required <br />
<br />
<br />
<br />
<br />
[[Category:News|{{PAGENAME}}]]</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:PBX/Objects/Config_Template&diff=20772Reference9:PBX/Objects/Config Template2011-04-08T12:39:43Z<p>Tsr: /* Configuration Options available for Templates */</p>
<hr />
<div>Config templates can be used to set certain parameters for many users in an uniform fashion. Templates can be defined and then assigned to users in the from the '''Config Template''' list. All parameters that are not set (that is, are empty) in the user configuration will be inherited from the template. <br />
<br />
Config templates can be nested by assigning a previously defined config template to another config template.<br />
<br />
== Configuration Options available for Templates ==<br />
<br />
The following configuration options can be configured thru templates:<br />
<br />
;Filter: The filter configured here restricts the numbers which may be called by a endpoint registered to this object<br />
<br />
;Diversion FDilter: The filter configured here restricts the numbers which calls may be diverted to by a endpoint registered to this object<br />
<br />
;Response Timeout: Overides the PBX global response timeout for this object<br />
<br />
;Busy on ... Calls: If this value is set a call to this user object is rejected with User Busy if n or more calls are active on this user object. If the object is of the gateway type (Gateway, Trunk, ...) calls from endpoints registered to this object are rejected as well in this case.<br />
<br />
;External UC: A '''Long Name''' of a External UC object can be configured here. Presence Information for this user is then obtained from a UC Server which is registered to this Object. Instant messaging Sessions for this user are also forwarded to the External UC interface.<br />
<br />
;No Inband Disconnect: If this checkmark is set, a call disconect with inband information will not be forwarded to the endpoint registered to the user, but the call will be cleared immediatelly without the inband information beeing sent.<br />
<br />
;Discard Phone Config: If this checkmark is set in addition to ''Store Phone Config'' the local config stored at the phone is discarded but not returned to the PBX when the phone registers the first time, i.e. the phone is configured with the config predefined at the PBX. <br />
<br />
;Store Phone Config: If this checkmark is set, the PBX stores the config of the phone. The first time a phone registers the predefined config at the PBX is sent to the phone even if it is empty. Then the local config stored at the phone is merged into the received config and the result is returned to the PBX. After this the local config is deleted and no local config is stored on the phone anymore. Later config changes on the phone will be sent to the PBX and stored there. On registration the PBX sends the complete config to the phone again.<br />
<br />
;Twin Phones: With this checkmark the twin phone mode is enabled for this object, which means that one user uses different phones. The main difference is, that if one phone is busy and additional call is sent to the busy phone only as call waiting and not to the other phones.<br />
;:If "Call Waiting" is disabled on the busy phone a second call gets a busy tone and a missed call is displayed when the active call is terminated.<br />
<br />
;Reporting: Enables Reporting for this user. A reporting license is needed to activate this. To show up the call-list at the myPBX client, you also need to activate the ''reporting'' flag.<br />
<br />
;Reject ext. Calls: If this checkmark is set a call from an external source to this object is rejected. A calling party numbering plan private is used to decide that the call is coming from an internal source. An invalid number destination is excuted for calls rejected because of this.</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:PBX/Objects/Config_Template&diff=20768Reference9:PBX/Objects/Config Template2011-04-08T12:37:31Z<p>Tsr: /* Configuration Options available for Templates */</p>
<hr />
<div>Config templates can be used to set certain parameters for many users in an uniform fashion. Templates can be defined and then assigned to users in the from the '''Config Template''' list. All parameters that are not set (that is, are empty) in the user configuration will be inherited from the template. <br />
<br />
Config templates can be nested by assigning a previously defined config template to another config template.<br />
<br />
== Configuration Options available for Templates ==<br />
<br />
The following configuration options can be configured thru templates:<br />
<br />
;Filter: The filter configured here restricts the numbers which may be called by a endpoint registered to this object<br />
<br />
;Diversion FDilter: The filter configured here restricts the numbers which calls may be diverted to by a endpoint registered to this object<br />
<br />
;Response Timeout: Overides the PBX global response timeout for this object<br />
<br />
;Busy on ... Calls: If this value is set a call to this user object is rejected with User Busy if n or more calls are active on this user object. If the object is of the gateway type (Gateway, Trunk, ...) calls from endpoints registered to this object are rejected as well in this case.<br />
<br />
;External UC: A '''Long Name''' of a External UC object can be configured here. Presence Information for this user is then obtained from a UC Server which is registered to this Object. Instant messaging Sessions for this user are also forwarded to the External UC interface.<br />
<br />
;No Inband Disconnect: If this checkmark is set, a call disconect with inband information will not be forwarded to the endpoint registered to the user, but the call will be cleared immediatelly without the inband information beeing sent.<br />
<br />
;Discard Phone Config: If this checkmark is set in addition to ''Store Phone Config'' the local config stored at the phone is discarded but not returned to the PBX when the phone registers the first time, i.e. the phone is configured with the config predefined at the PBX. <br />
<br />
;Store Phone Config: If this checkmark is set, the PBX stores the config of the phone. The first time a phone registers the predefined config at the PBX is sent to the phone even if it is empty. Then the local config stored at the phone is merged into the received config and the result is returned to the PBX. After this the local config is deleted and no local config is stored on the phone anymore. Later config changes on the phone will be sent to the PBX and stored there. On registration the PBX sends the complete config to the phone again.<br />
<br />
;Twin Phones: With this checkmark the twin phone mode is enabled for this object, which means that one user uses different phones. The main difference is, that if one phone is busy and additional call is sent to the busy phone only as call waiting and not to the other phones.<br />
;:If "Call Waiting" is disabled on the busy phone a second call gets a busy tone and a missed call is displayed when the active call is terminated.<br />
<br />
;Reporting: Enables Reporting for this user. A reporting license is needed to activate this. It is also needed to show up the call-list at the myPBX client.<br />
<br />
;Reject ext. Calls: If this checkmark is set a call from an external source to this object is rejected. A calling party numbering plan private is used to decide that the call is coming from an internal source. An invalid number destination is excuted for calls rejected because of this.</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Reference9:PBX/Objects/Config_Template&diff=20767Reference9:PBX/Objects/Config Template2011-04-08T12:37:14Z<p>Tsr: /* Configuration Options available for Templates */</p>
<hr />
<div>Config templates can be used to set certain parameters for many users in an uniform fashion. Templates can be defined and then assigned to users in the from the '''Config Template''' list. All parameters that are not set (that is, are empty) in the user configuration will be inherited from the template. <br />
<br />
Config templates can be nested by assigning a previously defined config template to another config template.<br />
<br />
== Configuration Options available for Templates ==<br />
<br />
The following configuration options can be configured thru templates:<br />
<br />
;Filter: The filter configured here restricts the numbers which may be called by a endpoint registered to this object<br />
<br />
;Diversion FDilter: The filter configured here restricts the numbers which calls may be diverted to by a endpoint registered to this object<br />
<br />
;Response Timeout: Overides the PBX global response timeout for this object<br />
<br />
;Busy on ... Calls: If this value is set a call to this user object is rejected with User Busy if n or more calls are active on this user object. If the object is of the gateway type (Gateway, Trunk, ...) calls from endpoints registered to this object are rejected as well in this case.<br />
<br />
;External UC: A '''Long Name''' of a External UC object can be configured here. Presence Information for this user is then obtained from a UC Server which is registered to this Object. Instant messaging Sessions for this user are also forwarded to the External UC interface.<br />
<br />
;No Inband Disconnect: If this checkmark is set, a call disconect with inband information will not be forwarded to the endpoint registered to the user, but the call will be cleared immediatelly without the inband information beeing sent.<br />
<br />
;Discard Phone Config: If this checkmark is set in addition to ''Store Phone Config'' the local config stored at the phone is discarded but not returned to the PBX when the phone registers the first time, i.e. the phone is configured with the config predefined at the PBX. <br />
<br />
;Store Phone Config: If this checkmark is set, the PBX stores the config of the phone. The first time a phone registers the predefined config at the PBX is sent to the phone even if it is empty. Then the local config stored at the phone is merged into the received config and the result is returned to the PBX. After this the local config is deleted and no local config is stored on the phone anymore. Later config changes on the phone will be sent to the PBX and stored there. On registration the PBX sends the complete config to the phone again.<br />
<br />
;Twin Phones: With this checkmark the twin phone mode is enabled for this object, which means that one user uses different phones. The main difference is, that if one phone is busy and additional call is sent to the busy phone only as call waiting and not to the other phones.<br />
;:If "Call Waiting" is disabled on the busy phone a second call gets a busy tone and a missed call is displayed when the active call is terminated.<br />
<br />
;Reporting: Enables Reporting for this user. A reporting license is needed to activate this. It is also needed to show up the call-list at the myPBX client<br />
<br />
;Reject ext. Calls: If this checkmark is set a call from an external source to this object is rejected. A calling party numbering plan private is used to decide that the call is coming from an internal source. An invalid number destination is excuted for calls rejected because of this.</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Howto:Multiple_PBX_Redundancy&diff=20623Howto:Multiple PBX Redundancy2011-03-31T10:29:35Z<p>Tsr: /* from V9 recommended 2way redundancy without Multicast routing */</p>
<hr />
<div>This article describes a multipe PBX redundacy <br />
<br />
<br />
==Applies To==<br />
This information applies to<br />
<br />
* innovaphone PBX V7,V8 and later<br />
<br />
<!-- Keywords: mehrfach redundanz mehrfachredundanz 3 weg 4 weg 3weg 4weg 3way 2way redundancy triple redundancy --><br />
<br />
==More Information==<br />
innovaphone supports redundancy for its PBX. A Master PBX has its Standby PBX and also a Slave PBX has its Standby-Slave PBX.<br />
Even a Master PBX can act as a Standby PBX for its Slave PBX and vice versa. Now this article describes how to solve a multiple PBX redundancy.<br />
<br />
===Problem Details===<br />
For the standby scenario to work, it is essential that all affected clients (phones, gateways, etc.) are able to register with both the master PBX and the standby PBX. Apart from the fact that there must be appropriate IP routings, the clients either need to know both PBX's IP addresses or need to be able to find them dynamically. <br />
<br />
Registration mechanism: When a slave PBX gets a registration request (e.g from a Phone) that does not belong to itself it redirects the registration request to the Master PBX. Also when a Master PBX gets a registration request (and not belonging to it) it redirects it to the according slave PBX. See also [[Reference:PBX_Locations#The_registration_PBX]]. <br />
<br />
The following methods exist to make the PBX's IP addresses known to clients:<br />
Both for H.323 and SIP devices, a dynamic, IP multicast based discovery mechanism is available (based on IGMPv2). This is known as gatekeeper discovery in H.323 and also available in SIP. For innovaphone devices, discovery is enabled when there is no gatekeeper IP address or no SIP domain configured. If you have a Layer 2 or multicast enabled network between you PBX´s you can use the Discovery mechanism (configured Gatekeeper ID) <br />
<br />
In an routed network (without multicast forwarding) where the standby PBX is in another Network you must work with the entries of primary and secondary Gatekeeper at your endpoint. This is often the only method available for 3rd party devices. For SIP devices, the 2 IP addresses are usually retrieved from the domain name system (DNS) based on the domain provided. The advantage here is that on the innovaphone phone you see on the display if its´s registered at it´s primary or it´s secondary PBX (this feature is not available when you work with the gatekeeper Id)<br />
<br />
[[Image:Howto-Multiple PBX Redundancy Reg.png]]<br />
<br />
===System Requirements===<br />
<br />
A Standby Licence is needed (must be the same size as the Port licences), this Standby Licence should be installed at the master PBX and with the floating mechanism distributed to all slave and standby PBX´s. This has the advantage that you need only one Standby Licence even if you want to have multiple redundancy. See also [[Reference8:Licenses#Licensing_for_Standby_operation]]<br />
<br />
==Scenario==<br />
Having two data center sites, the endpoints should have redundancy in-between the data center. But also if one data center is completely down the endpoints should register at the remote data center.<br />
<br />
<br />
===3 way redundancy with layer 2 or Multicast routing enabled networks ===<br />
<br />
* When having a Layer 2 network between the data centers you can work with the Gatekeeper ID. Take care about the physical location (see [[Howto:Multiple_PBX_Redundancy#Known_Problems | Knowm Problems]] below), so that local PBX getting first the registration request of their local phones. In an Layer2 Network you can not control what PBX gets the Gatekeeper discovery first.<br />
<br />
<br />
* In an Multicast enabled Wan network it is also possible to work with the Gatekeeper ID (as the endpoint makes a Gatekeeper discovery via the Multicast address 224.0.1.41).Be aware that multicast enabled wan networks requires deep network know how specialists to get it work right. We recommend to use [[http://en.wikipedia.org/wiki/Protocol_Independent_Multicast |Protocol Independent Multicast (PIM)]] solution. Be in mind that you have to take care about the physical location (like in the layer 2 network).<br />
<br />
You only need to work with the Gatekeeper ID (Gatekeeper discovery) at the endpoints. First the registration is always at the local PBX, if the local PBX is down the corresponding Standby will take over, if both PBX´s fails the PBX of the remote side will take over. If the remote PBX also fails the remote Standby will take over. You need to replicate all Objects between those two data centers have redundancy between them.<br />
Be in mind that a Standby PBX if its idle (so its corresponding PBX is active) never accepts or forwards any registration requests/gatekeeper discovery's. The Standby PBX only gets active when it´s PBX is down.<br />
<br />
<br />
[[Image:Howto-Multiple_PBX_Redundancy_Layer2.png]]<br />
<br />
===3 way redundancy without Multicast routing networks ===<br />
<br />
When having no Multicast routing enabled Network, Gatekeeper discovery via different sites is not possible. So here we describe the recommended configuration for 3 way redundancy. <br />
<br />
* Note if the local Datacenter fails at all (Master & Standby or Slave &Slave Standby )- the remote Datacenter will NOT take over<br />
<br />
You can still work with Gatekeeper discovery, to have 3 way redundancy you must register the local Phones at the remote location, see the picture below. With that configuration you do not have problems with the Physical-location. <br />
<br />
[[Image:Howto-Multiple_PBX_Redundancy_Layer3.png]]<br />
<br />
<br />
====Alternative====<br />
You can configure also a redundancy when the local Datacenter is completely down, but then you only have a 2 way redundancy and a problem with the physical -location.<br />
The phones having fixed Ip addresses configured (primary & secondary gatekeeper). Primary Gatekeeper is the remote PBX, this PBX redirects to the local PBX. If the local PBX fails the registration request will be redirected to the local standby (or standby slave). If the remote Datacenter fails at all, you configure as secondary gatekeeper the local PBX.<br />
<br />
With that solution you have redundancy between the Datacenters but only 2 way redundancy.<br />
<br />
===from V9 recommended 2way redundancy without Multicast routing ===<br />
Starting from V9 (on the phones) it is possible to configure additional to the Gatekeeper discovery a fixed IP for the secondary gatekeeper address, see [[Reference9:Phone/User/General]]. With that configuration we can do a 2 way redundancy without the physical location problem. This is the recommended way.<br />
Primary the gatekeeper discovery will search for the local PBX, if the local PBX is down (and its standby or standby-slave) the phone will use the configured IP address of the secondary gatekeeper address. This is the remote PBX. If the local PBX or it´s standby is up again then the remote PBX will unregister this phone and so the phone registers locally again.<br />
<br />
<br />
[[Image:Howto-Multiple PBX Redundancy No multicast V9 1.png]]<br />
<br />
===Known Problems===<br />
<br />
====Physical location====<br />
The physical-location is not configured but determined for each device on runtime depending on the PBX the original registration was sent to. This physical-location is not necessarily identical to the registration PBX since if the registration is sent first to a PBX which is not the registration PBX for this object, it will be the physical-location anyway, but the registration is redirected to the registration PBX. The callers physical location is determined, if there is a matching local object defined in the numbering node that is the physical location of the caller, then this object will hide any other object that would normally be found in the callers scope. This is often used for locations with local trunk lines. The trunk line object is put into the numbering node of the PBX serving the location and the local flag is turned on. This way, all calls from users who are located in this location will use the local trunk when dialing the trunk prefix, regardless of their node. So you need to be sure that local Ip Phones that need to get the Local Trunk Object - having its local PBX as physical location.<br />
<br />
====Standby PBX====<br />
<br />
A Standby (or Slave-Standby) PBX only gets active (accept and/or forward gatekeeper discovery as registrationr requests) when its associated PBX is down. As long as it´s associated PBX is up the Standby PBX is inactive (and so even does not forward gatekeeper discovery's).<br />
<br />
<br />
== Related Articles == <br />
<br />
[[Howto:How to tweak the RAS and TCP Keepalive timers]]<br />
<br />
[[Category:Howto|{{PAGENAME}}]]</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Howto:Multiple_PBX_Redundancy&diff=20622Howto:Multiple PBX Redundancy2011-03-31T08:47:37Z<p>Tsr: /* from V9 recommended 2way redundancy without Multicast routing */</p>
<hr />
<div>This article describes a multipe PBX redundacy <br />
<br />
<br />
==Applies To==<br />
This information applies to<br />
<br />
* innovaphone PBX V7,V8 and later<br />
<br />
<!-- Keywords: mehrfach redundanz mehrfachredundanz 3 weg 4 weg 3weg 4weg 3way 2way redundancy triple redundancy --><br />
<br />
==More Information==<br />
innovaphone supports redundancy for its PBX. A Master PBX has its Standby PBX and also a Slave PBX has its Standby-Slave PBX.<br />
Even a Master PBX can act as a Standby PBX for its Slave PBX and vice versa. Now this article describes how to solve a multiple PBX redundancy.<br />
<br />
===Problem Details===<br />
For the standby scenario to work, it is essential that all affected clients (phones, gateways, etc.) are able to register with both the master PBX and the standby PBX. Apart from the fact that there must be appropriate IP routings, the clients either need to know both PBX's IP addresses or need to be able to find them dynamically. <br />
<br />
Registration mechanism: When a slave PBX gets a registration request (e.g from a Phone) that does not belong to itself it redirects the registration request to the Master PBX. Also when a Master PBX gets a registration request (and not belonging to it) it redirects it to the according slave PBX. See also [[Reference:PBX_Locations#The_registration_PBX]]. <br />
<br />
The following methods exist to make the PBX's IP addresses known to clients:<br />
Both for H.323 and SIP devices, a dynamic, IP multicast based discovery mechanism is available (based on IGMPv2). This is known as gatekeeper discovery in H.323 and also available in SIP. For innovaphone devices, discovery is enabled when there is no gatekeeper IP address or no SIP domain configured. If you have a Layer 2 or multicast enabled network between you PBX´s you can use the Discovery mechanism (configured Gatekeeper ID) <br />
<br />
In an routed network (without multicast forwarding) where the standby PBX is in another Network you must work with the entries of primary and secondary Gatekeeper at your endpoint. This is often the only method available for 3rd party devices. For SIP devices, the 2 IP addresses are usually retrieved from the domain name system (DNS) based on the domain provided. The advantage here is that on the innovaphone phone you see on the display if its´s registered at it´s primary or it´s secondary PBX (this feature is not available when you work with the gatekeeper Id)<br />
<br />
[[Image:Howto-Multiple PBX Redundancy Reg.png]]<br />
<br />
===System Requirements===<br />
<br />
A Standby Licence is needed (must be the same size as the Port licences), this Standby Licence should be installed at the master PBX and with the floating mechanism distributed to all slave and standby PBX´s. This has the advantage that you need only one Standby Licence even if you want to have multiple redundancy. See also [[Reference8:Licenses#Licensing_for_Standby_operation]]<br />
<br />
==Scenario==<br />
Having two data center sites, the endpoints should have redundancy in-between the data center. But also if one data center is completely down the endpoints should register at the remote data center.<br />
<br />
<br />
===3 way redundancy with layer 2 or Multicast routing enabled networks ===<br />
<br />
* When having a Layer 2 network between the data centers you can work with the Gatekeeper ID. Take care about the physical location (see [[Howto:Multiple_PBX_Redundancy#Known_Problems | Knowm Problems]] below), so that local PBX getting first the registration request of their local phones. In an Layer2 Network you can not control what PBX gets the Gatekeeper discovery first.<br />
<br />
<br />
* In an Multicast enabled Wan network it is also possible to work with the Gatekeeper ID (as the endpoint makes a Gatekeeper discovery via the Multicast address 224.0.1.41).Be aware that multicast enabled wan networks requires deep network know how specialists to get it work right. We recommend to use [[http://en.wikipedia.org/wiki/Protocol_Independent_Multicast |Protocol Independent Multicast (PIM)]] solution. Be in mind that you have to take care about the physical location (like in the layer 2 network).<br />
<br />
You only need to work with the Gatekeeper ID (Gatekeeper discovery) at the endpoints. First the registration is always at the local PBX, if the local PBX is down the corresponding Standby will take over, if both PBX´s fails the PBX of the remote side will take over. If the remote PBX also fails the remote Standby will take over. You need to replicate all Objects between those two data centers have redundancy between them.<br />
Be in mind that a Standby PBX if its idle (so its corresponding PBX is active) never accepts or forwards any registration requests/gatekeeper discovery's. The Standby PBX only gets active when it´s PBX is down.<br />
<br />
<br />
[[Image:Howto-Multiple_PBX_Redundancy_Layer2.png]]<br />
<br />
===3 way redundancy without Multicast routing networks ===<br />
<br />
When having no Multicast routing enabled Network, Gatekeeper discovery via different sites is not possible. So here we describe the recommended configuration for 3 way redundancy. <br />
<br />
* Note if the local Datacenter fails at all (Master & Standby or Slave &Slave Standby )- the remote Datacenter will NOT take over<br />
<br />
You can still work with Gatekeeper discovery, to have 3 way redundancy you must register the local Phones at the remote location, see the picture below. With that configuration you do not have problems with the Physical-location. <br />
<br />
[[Image:Howto-Multiple_PBX_Redundancy_Layer3.png]]<br />
<br />
<br />
====Alternative====<br />
You can configure also a redundancy when the local Datacenter is completely down, but then you only have a 2 way redundancy and a problem with the physical -location.<br />
The phones having fixed Ip addresses configured (primary & secondary gatekeeper). Primary Gatekeeper is the remote PBX, this PBX redirects to the local PBX. If the local PBX fails the registration request will be redirected to the local standby (or standby slave). If the remote Datacenter fails at all, you configure as secondary gatekeeper the local PBX.<br />
<br />
With that solution you have redundancy between the Datacenters but only 2 way redundancy.<br />
<br />
===from V9 recommended 2way redundancy without Multicast routing ===<br />
Starting from V9 (on the Phones) it is possible to configure additional to the Gatekeeper discovery a fixed Ip for the secondary Gatekeeper address, see [[Reference9:Phone/User/General]].With that configuration we can make a 2 way redundancy without the physical location problem. This is the recommended way.<br />
Primary the Gatekeeper discovery will search for the local PBX, if the local PBX is down (and its Standby or Standby Slave) the Phone will use the configured Ip address of the secondary Gatekeeper address. This is the remote PBX. If the local PBX or it´s standby is up again then the remote PBX will unregister this Phone and so the Phone registers locally again.<br />
<br />
<br />
[[Image:Howto-Multiple PBX Redundancy No multicast V9 1.png]]<br />
<br />
===Known Problems===<br />
<br />
====Physical location====<br />
The physical-location is not configured but determined for each device on runtime depending on the PBX the original registration was sent to. This physical-location is not necessarily identical to the registration PBX since if the registration is sent first to a PBX which is not the registration PBX for this object, it will be the physical-location anyway, but the registration is redirected to the registration PBX. The callers physical location is determined, if there is a matching local object defined in the numbering node that is the physical location of the caller, then this object will hide any other object that would normally be found in the callers scope. This is often used for locations with local trunk lines. The trunk line object is put into the numbering node of the PBX serving the location and the local flag is turned on. This way, all calls from users who are located in this location will use the local trunk when dialing the trunk prefix, regardless of their node. So you need to be sure that local Ip Phones that need to get the Local Trunk Object - having its local PBX as physical location.<br />
<br />
====Standby PBX====<br />
<br />
A Standby (or Slave-Standby) PBX only gets active (accept and/or forward gatekeeper discovery as registrationr requests) when its associated PBX is down. As long as it´s associated PBX is up the Standby PBX is inactive (and so even does not forward gatekeeper discovery's).<br />
<br />
<br />
== Related Articles == <br />
<br />
[[Howto:How to tweak the RAS and TCP Keepalive timers]]<br />
<br />
[[Category:Howto|{{PAGENAME}}]]</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Howto:Prefixer_Client_Android_-_253%C2%B0Below_-_Testreport&diff=20453Howto:Prefixer Client Android - 253°Below - Testreport2011-03-24T15:22:00Z<p>Tsr: /* Summary */</p>
<hr />
<div>==Summary==<br />
Prefixer client for android enables a user friendly access to the functions of the mobility object and PBX DTMF-features from mobile phones.<br />
This client is for '''free''', available in the android market.<br />
<!-- keywords gsmclient gsm client --><br />
<br />
==Current test state==<br />
<!--{{Template:Compat Status "tested"}}--><br />
{{Template:Compat Status "in progress"}}<br />
<!--{{Template:Compat Status "certified"|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}}--><br />
<!--{{Template:Compat Status "tested"}} --><br />
<!--{{Template:Compat Status "rejected"}} --><br />
<br />
<!--{{Testing of this product has been finalized September 15, 2010.}} --><br />
<br />
==Version==<br />
Product name: <br />
Prefixer<br />
<br />
Vendor: <br />
[[http://www.253below.com/prefixer |253°Below]]<br />
<br />
Version: <br />
0.9.3<br />
<br />
Testdevice: <br />
HTC Magic, Android Version 2.2.1<br />
<br />
innovaphone Firmware:<br />
V9 Build 90484<br />
<br />
==Configured Scenario==<br />
<!--insert here a graphical description(png - format) of the test scenario--><br />
<!--also try to describe the purpose of the implemented network setup--><br />
The client test based on a simple configuration scenario with flat numbering plan and single dial-in trunk. The Mobility Object and DTMF-Features are accessible via PBX prefix.<br />
<br />
==Test Result==<br />
<br />
===Call Methods===<br />
* No - The default value. No popup will trigger.<br />
* Yes - A confirmation dialog will popup asking you to verify that you really want to make the call.<br />
* Manual - The standard dialing application will popup allowing you to make manual adjustments to the number.<br />
* Challenge (Party filter) - A confirmation dialog will popup challenging you with a mathematical question. Unless you know the answer to the question, you will not be able to make the call.<br />
<br />
===Call Through (2-stage-dialling via mobility object)===<br />
Numbers can be dialled via the native android mobile phone application by dialling a number, select a number from phone book or call list. The call will be intercepted by android client and terminated. Then a call to access number (mobility object) will be established, followed by the original number dialled via DTMF.<br />
<br />
For internal calls you have to dial only the extension without the main number.<br />
<br />
The client can set rules for outgoing calls based on:<br />
<br />
* matching number on regular expressions (example: outgoing rule should only work for 3 digits --> [0-9] {3} )<br />
* on time and day<br />
* number in contact list<br />
* Roaming (if the phone is currently roaming or not)<br />
<br />
===Calls from PBX Users to Client===<br />
Incoming calls can be configured by incoming rules.<br />
{{FIXME|reason="Test not finished yet"}}<br />
<br />
===DTMF Features===<br />
<br />
<br />
==Installation==<br />
We installed the prefixer client on a HTC Magic from the android market.<br />
<br />
==Configuration==<br />
<br />
===PBX Settings===<br />
{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"<br />
|-<br />
|External Trunk Number||0049703173009<br />
|-<br />
|Internal Trunk Access Number||0<br />
|-<br />
|PBX Prefix||2200<br />
|-<br />
|Mobility Object||2200.69<br />
|-<br />
|DTMF-Features||2200.6xx<br />
|-<br />
|}<br />
<br />
===Product Settings===<br />
<br />
Outgoing call rule<br />
{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:shown;"<br />
!'''Operational Settings'''!!<br />
|-<br />
|Call Method||no<br />
|-<br />
|Add prefix||0049703173009<br />
|-<br />
|}<br />
<br />
<br />
==Related Articles==<br />
<br />
[[http://www.253below.com/prefixer/help | Prefixer help]]<br />
<br />
[[http://www.253below.com/prefixer/rule-templates | Prefixer rule templates]]<br />
<br />
<br />
<br />
[[Category:Compat|{{PAGENAME}}]]</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Howto:Prefixer_Client_Android_-_253%C2%B0Below_-_Testreport&diff=20452Howto:Prefixer Client Android - 253°Below - Testreport2011-03-24T15:21:46Z<p>Tsr: /* Summary */</p>
<hr />
<div>==Summary==<br />
Prefixer client for android enables a user friendly access to the functions of the mobility object and PBX DTMF-features from mobile phones.<br />
This client is for '''free''' , available in the android market.<br />
<!-- keywords gsmclient gsm client --><br />
<br />
==Current test state==<br />
<!--{{Template:Compat Status "tested"}}--><br />
{{Template:Compat Status "in progress"}}<br />
<!--{{Template:Compat Status "certified"|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}}--><br />
<!--{{Template:Compat Status "tested"}} --><br />
<!--{{Template:Compat Status "rejected"}} --><br />
<br />
<!--{{Testing of this product has been finalized September 15, 2010.}} --><br />
<br />
==Version==<br />
Product name: <br />
Prefixer<br />
<br />
Vendor: <br />
[[http://www.253below.com/prefixer |253°Below]]<br />
<br />
Version: <br />
0.9.3<br />
<br />
Testdevice: <br />
HTC Magic, Android Version 2.2.1<br />
<br />
innovaphone Firmware:<br />
V9 Build 90484<br />
<br />
==Configured Scenario==<br />
<!--insert here a graphical description(png - format) of the test scenario--><br />
<!--also try to describe the purpose of the implemented network setup--><br />
The client test based on a simple configuration scenario with flat numbering plan and single dial-in trunk. The Mobility Object and DTMF-Features are accessible via PBX prefix.<br />
<br />
==Test Result==<br />
<br />
===Call Methods===<br />
* No - The default value. No popup will trigger.<br />
* Yes - A confirmation dialog will popup asking you to verify that you really want to make the call.<br />
* Manual - The standard dialing application will popup allowing you to make manual adjustments to the number.<br />
* Challenge (Party filter) - A confirmation dialog will popup challenging you with a mathematical question. Unless you know the answer to the question, you will not be able to make the call.<br />
<br />
===Call Through (2-stage-dialling via mobility object)===<br />
Numbers can be dialled via the native android mobile phone application by dialling a number, select a number from phone book or call list. The call will be intercepted by android client and terminated. Then a call to access number (mobility object) will be established, followed by the original number dialled via DTMF.<br />
<br />
For internal calls you have to dial only the extension without the main number.<br />
<br />
The client can set rules for outgoing calls based on:<br />
<br />
* matching number on regular expressions (example: outgoing rule should only work for 3 digits --> [0-9] {3} )<br />
* on time and day<br />
* number in contact list<br />
* Roaming (if the phone is currently roaming or not)<br />
<br />
===Calls from PBX Users to Client===<br />
Incoming calls can be configured by incoming rules.<br />
{{FIXME|reason="Test not finished yet"}}<br />
<br />
===DTMF Features===<br />
<br />
<br />
==Installation==<br />
We installed the prefixer client on a HTC Magic from the android market.<br />
<br />
==Configuration==<br />
<br />
===PBX Settings===<br />
{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"<br />
|-<br />
|External Trunk Number||0049703173009<br />
|-<br />
|Internal Trunk Access Number||0<br />
|-<br />
|PBX Prefix||2200<br />
|-<br />
|Mobility Object||2200.69<br />
|-<br />
|DTMF-Features||2200.6xx<br />
|-<br />
|}<br />
<br />
===Product Settings===<br />
<br />
Outgoing call rule<br />
{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:shown;"<br />
!'''Operational Settings'''!!<br />
|-<br />
|Call Method||no<br />
|-<br />
|Add prefix||0049703173009<br />
|-<br />
|}<br />
<br />
<br />
==Related Articles==<br />
<br />
[[http://www.253below.com/prefixer/help | Prefixer help]]<br />
<br />
[[http://www.253below.com/prefixer/rule-templates | Prefixer rule templates]]<br />
<br />
<br />
<br />
[[Category:Compat|{{PAGENAME}}]]</div>Tsrhttps://wiki.innovaphone.com/index.php?title=Howto:Prefixer_Client_Android_-_253%C2%B0Below_-_Testreport&diff=20451Howto:Prefixer Client Android - 253°Below - Testreport2011-03-24T15:21:38Z<p>Tsr: /* Summary */</p>
<hr />
<div>==Summary==<br />
Prefixer client for android enables a user friendly access to the functions of the mobility Object and PBX DTMF-features from mobile phones.<br />
This client is for '''free''' , available in the android market.<br />
<!-- keywords gsmclient gsm client --><br />
<br />
==Current test state==<br />
<!--{{Template:Compat Status "tested"}}--><br />
{{Template:Compat Status "in progress"}}<br />
<!--{{Template:Compat Status "certified"|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}}--><br />
<!--{{Template:Compat Status "tested"}} --><br />
<!--{{Template:Compat Status "rejected"}} --><br />
<br />
<!--{{Testing of this product has been finalized September 15, 2010.}} --><br />
<br />
==Version==<br />
Product name: <br />
Prefixer<br />
<br />
Vendor: <br />
[[http://www.253below.com/prefixer |253°Below]]<br />
<br />
Version: <br />
0.9.3<br />
<br />
Testdevice: <br />
HTC Magic, Android Version 2.2.1<br />
<br />
innovaphone Firmware:<br />
V9 Build 90484<br />
<br />
==Configured Scenario==<br />
<!--insert here a graphical description(png - format) of the test scenario--><br />
<!--also try to describe the purpose of the implemented network setup--><br />
The client test based on a simple configuration scenario with flat numbering plan and single dial-in trunk. The Mobility Object and DTMF-Features are accessible via PBX prefix.<br />
<br />
==Test Result==<br />
<br />
===Call Methods===<br />
* No - The default value. No popup will trigger.<br />
* Yes - A confirmation dialog will popup asking you to verify that you really want to make the call.<br />
* Manual - The standard dialing application will popup allowing you to make manual adjustments to the number.<br />
* Challenge (Party filter) - A confirmation dialog will popup challenging you with a mathematical question. Unless you know the answer to the question, you will not be able to make the call.<br />
<br />
===Call Through (2-stage-dialling via mobility object)===<br />
Numbers can be dialled via the native android mobile phone application by dialling a number, select a number from phone book or call list. The call will be intercepted by android client and terminated. Then a call to access number (mobility object) will be established, followed by the original number dialled via DTMF.<br />
<br />
For internal calls you have to dial only the extension without the main number.<br />
<br />
The client can set rules for outgoing calls based on:<br />
<br />
* matching number on regular expressions (example: outgoing rule should only work for 3 digits --> [0-9] {3} )<br />
* on time and day<br />
* number in contact list<br />
* Roaming (if the phone is currently roaming or not)<br />
<br />
===Calls from PBX Users to Client===<br />
Incoming calls can be configured by incoming rules.<br />
{{FIXME|reason="Test not finished yet"}}<br />
<br />
===DTMF Features===<br />
<br />
<br />
==Installation==<br />
We installed the prefixer client on a HTC Magic from the android market.<br />
<br />
==Configuration==<br />
<br />
===PBX Settings===<br />
{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"<br />
|-<br />
|External Trunk Number||0049703173009<br />
|-<br />
|Internal Trunk Access Number||0<br />
|-<br />
|PBX Prefix||2200<br />
|-<br />
|Mobility Object||2200.69<br />
|-<br />
|DTMF-Features||2200.6xx<br />
|-<br />
|}<br />
<br />
===Product Settings===<br />
<br />
Outgoing call rule<br />
{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:shown;"<br />
!'''Operational Settings'''!!<br />
|-<br />
|Call Method||no<br />
|-<br />
|Add prefix||0049703173009<br />
|-<br />
|}<br />
<br />
<br />
==Related Articles==<br />
<br />
[[http://www.253below.com/prefixer/help | Prefixer help]]<br />
<br />
[[http://www.253below.com/prefixer/rule-templates | Prefixer rule templates]]<br />
<br />
<br />
<br />
[[Category:Compat|{{PAGENAME}}]]</div>Tsr