Avaya IP Office creates a 46xxsettings.txt automatically based on the settings you made in it’s configuration. Additionally the file looks different based on the network from where a client downloads the file. Within any local network the file contains the local IP address in the file while behind any NAT router (access from public) the configured public IP and FQDNs are reflected.
Even if the auto generated 46xxsettings.txt has a good set of configuration parameters you will probably add some individual settings. You can for example add a dial plan configuration so that trunk access codes are added to the dialled number. Or you can configure EC500 settings to be able to use the app to reach your call destination through IP Office, even if the data connectivity is bad or some ports are blocked. You will dial a special number in your IP Office, get an internal dial tone and the app will dial the destination number as DTMF digits afterward. Boom… the called party will only see your office number.
This post describes you how to use the different status of a hunt group (in service, night service, out of service) as a switch within Voicemail Pro call flows.
Didn’t you have the challenge that the local users should be able to switch between different ways a call should flow through Voicemail Pro? And wouldn’t it be nice if it were possible to do this through a phone button? And furthermore… shouldn’t it be possible to light the button if a chosen condition is set? And all that from different users and phones?
The Challenge – Voicemail Pro client can’t connect
Recently I deployed a fresh IP Office Anywhere release 11.1 to test some new features. While I tried to connect the Voicemail Pro client I figured out that the login always wasn’t impossible. The client showed me the error message that the client “Failed to connect to server”.
Very often the customers want to have their individual holdmusic in their IP Office system. They usually deliver the file as MP3 or any other audio format. Avaya describes the format with the following bullet points:
It’s the same as needed for Voicemail Pro.
Depending on the IP Office system the holdmusic must not be longer than 90sec (IP500V2) or 600sec (Server Edition).
In this post I will describe how to use the free Audacity audio editor, to convert audio files to meet the needs of IP Office.
Some time ago I published a post that describes the new rules a certificate has to follow to be accepted by Apple’s current devices (iPhone, iPad, MacOS PCs). Besides some rules about algorithms and bit length, that are usually met by all certificate authorities, there are some requirements, you will probably not see at first view. A certificate generated later than July 1st 2019 must not be longer valid than 825 days and the certificate must contain the value “Server Authentication” (OID 22.214.171.124.126.96.36.199.1) as Extended Key Usage (EKU).
In my last post I
mentioned that the IP Office certificate authority is able to create
certificates that work with iPhones and other Apple devices. That was only half the truth, because only IP
Office servers (Server Edition or Application Server) on at least release
188.8.131.52 create valid certificates.
You can see Voicemail Pro kind of like a swiss army knife of an IP Office installation. Besides the common functionalities of a voicemail system and those to build automatic assistants, you have the options to read and write several user or group settings.
post I will describe you, how you can configure call forwarding for other users
using Voicemail Pro. This can be helpful for example for assistants who have to
divert the phone of the boss if needed.
Recently I faced an interesting problem again,
that I want to share with you. Should you ever have the same problem, I hope
you will find this post and that you can save some time searching for the root
cause. There had been a customer call, that Media Manager plays no recording.
A short look into the recordings page seemed
to be fine. The system showed all made recordings. But as soon as you clicked
the play button the small player window appeared. Unfortunately you couldn’t
hear anything. It looked similar to the following picture with the
exception that the length of the recording has been shown as zero seconds.
In the Tek-Tips IP Office forum I recently read about an issue with the latest update of an IP500V2 to the latest 11.0 FP4 SP1. Upgrade fails and during file transfer you can see a HTTP error message “400 Bad Request”.
User splittingcodec found the reason for the issue and posted a workaround. He found out that some files in the Manager’s MemoryCards folder are empty. The solution was to just add some content to those files. For example just use the file name as content and save the files.
Recently Avaya informed about the stronger certificate rules in upcoming mobile operating systems iOS 13 and Android Q as well as on MacOS 10.15 through this PSN: https://downloads.avaya.com/css/P8/documents/101058839. Avaya announced that those stronger rules may affect the commonly used Avaya apps on smartphones and tablets as well as on MAC PCs.
A valid certificate must match the following criteria:
Recently we ran into an issue we didn’t figure out before.
But from the beginning… With the switch from 9.0 to 9.1 Avaya started to support the use of PLDS licenses in IP Office, even if the good old ADI licenses were still working. PLDS licenses have only been delivered dir systems with contact centers like IPOCC or ACCS. With the upgrade to 10.0 ADI licenses became obsolete and we had to migrate to PLDS licensing during the upgrade. After a few challenges with the first few license sets everything worked fine and I like PLDS.
Privacy & Cookies Policy
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.