This topic provides answers to frequently asked questions about applications that are being developed against Avaya IP Office.
The integrated Avaya IP Office Auto Attendant will only work with the embedded voicemail. Hence, if an external voicemail system (e.g. WinExpress) is used, the Avaya IP Office Auto Attendant feature is not available.
There can be only one voicemail server configured per Avaya IP Office system. Hence, if an external voicemail is configured, the external application needs to be capable of providing Auto Attendant features.
If the embedded Auto Attendant provided with Avaya IP Office is to be utilized, then it would be required to configure the embedded voicemail to be used as system voicemail. Phones can then be configured to use call forward any calls to the external voicemail under the conditions that the phone is busy or the call is not answered.
The username/password for opening the Avaya IP Office configuration in the Manager Application is for the 'Configuration Service User'. When performing an 'Upgrade' using the Manager Application, you will be prompted for the 'System Password'.
The System Password can be changed by accessing the Security Settings of the Manager Application. For more details on how to access the Security Settings and the default System Password; please refer the Security Mode section Avaya IP Office Manager Manual available at www.avaya.com/support.
It is not necessary to discover your Avaya IP Office systems every time. Avaya IP Office Manager can be configured to record details of discovered Avaya IP Office systems and then display a list of those previously discovered ('known') systems.
The use of the known systems functionality is not enabled by default. The Avaya IP Office Manager must be configured for the feature with the file location where the list of known systems can be stored and retrieved. To enable this feature:
After starting Manager Application, the Select IP Office screen is displayed; click on Known Units and then select the desired Avaya IP Office system.
Note: The primary key used by the Known Systems file is the Avaya IP Office system's IP address. The file cannot contain entries for separate systems that use the same IP address for access.
The Avaya IP Office MIBs are provided with the Admin CD for each release of Avaya IP Office. The Admin CD can be downloaded from www.avaya.com/support.
This behavior is controlled by an option in Avaya IP Office. To disable this behavior:
No, as of Avaya IP Office Release 8.0 the TAPI Wave Driver is not supported on 64 bit operating systems.
Avaya IP Office does not support sending SMDR (Station Message Detail Reporting) information to multiple destinations simultaneously. A single destination can be configured for SMDR data.
Both Avaya IP Office System Monitor and System Status interfaces are proprietary and no public API documents are available for them.
SMDR records are generated when a call ends, therefore the order of the SMDR records output does not match the call start times.
Please refer the Appendix: SMDR section Avaya IP Office Manager Manual available at www.avaya.com/support for more details regarding Avaya IP Office's SMDR specifications.
The GUID is supplied while adding a new user or group, is only valid for the request. Avaya
IP Office will allocate a
new GUID for the record as it is added. Configuration Web Service applications must make use
of GetUnitConfiguration'
to obtain the settings (i.e. GUID) of current users/groups and then design
SetUnitConfiguration
requests accordingly.
Avaya IP Office supports software-based support for voice processing. For this purpose, TAPI Wave driver (with TAPI 2.1 applications) or Media Service Provider (MSP) interface (for TAPI 3.0 applications) can be used.
Media streaming capabilities are only available to addresses (i.e. extensions) that are specifically named as WAV users. The media streaming capability allows a TAPI application to send and receive voice data on calls that are present on WAV users' lines. Which means, the Avaya IP Office switch will attempt to stream RTP audio to WAV users when they are involved in calls.
In addition to audio streaming, WAV users are required in order to utilize TAPI functions
like lineGenerateTone
(to generate a
beep on the line) and lineMonitorDigits
(to enable the detection of DTMF
digits).
Note: Please refer to the FAQ:"How do I configure a WAV user to handle media streaming?" for more details on WAV user configuration.
The number of simultaneously active media streams is limited by:
The IP Office Configuration Web service allowss an application to send requests to IP Office programmatically to retrieve and alter some IP Office configuration information. As a first step, download the released version of the Configuration Web Service SDK that aligns with the release of IP Office you are working with from the DevConnect portal. Expand the SDK, and note that it contains the following items (note that this description is written against release 8.0 of the SDK):
You will need to have a running version of IP Office. The Configuration Service associated
with IP Office release 8.0 has been tested and
verified to work with Windows 2003 SP1 32 bit OS. It is possible that other 32 bit Windows
OS will work with the SDK, however it is known
that 64 bit Windows OS versions do not work with the SDK. The PC should have connect to the
private LAN 'side' of IP Office (It is not
recommended to starting with testing the WAN side since it is simpler to start by testing
the Configuration Web Service with the LAN side
of IP Office. Please use the Configuration Web Service PDF to check OS support for later IP
Office Configuration Service SDK versions. On
The PC navigate to the SDK's Sample_Host\bin\Release
directory and double click
ConfigServiceHost.exe
. It is not
necessary to change the ConfigServiceHost.exe.config
settings file. This should
open a shell window on the PC and the output
should show:
Service Host has started, press any key to endBase Address Hosted by the servicehttp://localhost:8085/IPOConfigurationServicTimeout : 00:01:00
Locate a User that you would like to make a change to. A simple change is to alter a user's name. Take the GUID associated with that User and use it to formulate a XML web service request message body. Place the XML content in the lower window pane, and remove the default text "Configuration Changes".
<?xml version="1.0" encoding="utf-8"?> <AvayaIPOConfiguration> <Users> <User Guid="1b6dd700f12111cd825e00e007056264" Opp="Update"> <Name>Mick the Quick</Name> <User> </Users> </AvayaIPOConfiguration>
Click on the Send Config button at the bottom edge of the user interface to send the request to IP Office.
The response is displayed in the upper panel:
<?xml version="1.0" encoding="utf-8"?> <av:ValidationResults xmlns:av="http://Avaya/Validation/IPOffice/2007/01"> <SummaryResults> <PreValidationErrors>0</PreValidationErrors> <Errors>0</Errors> <Warning>0</Warning> <Informational>0</Informational> <RebootDetected>False</RebootDetected> <ConfigTransferred>True</ConfigTransferred> </SummaryResults> </av:ValidationResults>
Do another Get Unit Configuration to verify IP Office accepted the change.
The reason only one line is visible in the application is because the default installation of
Windows 2008 does not assign Local System as
the Telephony user. To correct this run mmc services.msc
from the Windows
command prompt and select Properties on the
Telephony Service. Select the LogOn tab and check the radio button next to Local
System account. Restart the telephony service and
run the application again. All lines configured on IP Office should now be visible to the
application.
With the introduction of IP Office 9.1, application control security settings, including TAPI, are defaulted to Off/Disabled status for new installations. However, when upgrading systems from 8.x or 9.0, the pre-existing security settings of “Enabled” are preserved.
As a result, new installations may block TAPI client access, until such time as they are enabled. For more information see IP Office Technical Tip #282 (published 4 August 2015).
The "Get Extensions" API function only returns the MAC address of an extension if the extension is logged in on a physical phone (e.g., a J.179 phone – see extension number 3004 in the image below). For an extension logged in on a soft phone (e.g., Avaya Workplace - extension number 3001 below), the API function only returns an "all-zero" MAC address. While undocumented, the IP Office product team states that since the MAC address is not available to IP Office when the extension registers, this is working as designed.
As of the current writing, up through release 11.1 of IP Office, Location API registration events (login/logout) are only generated for SIP extension using a soft phone (e.g., Avaya Workplace). Location API registration events are provided for both H.323 desk and soft phones.
However, for SIP extension login using physical phone (hard phone), the registration event is only generated for ‘login’ action, but no event is provided for 'logout' action. A JIRA was raised for tracking this issue (IPOFFICE-174449) against release 11.1; please check the IP Office Release Notes to verify when the issue is fixed in a future IP Office release.