With SIP remote worker, there a re a few things that need to be done, prior to anything working. If using TLS, you need a certificate (Here we created a 3rd party certificate for IP Office).
Once the certificate is set, you need some settings in the IP Office. Once those are set, your 46xxsettings.txt file should auto-generate.
Here are the settings for the IP Office:
Sometimes IP Office Short Codes can be a little tough to understand. Lets dissect them for a minute.
The IP Office uses short codes to match the number dialed to an action. The number dialed or part of the number dialed, can be used as parameter for the feature.
The following types of short code applied to on-switch dialing. The result may be an action to be performed by the IP Office, a change to the user’s settings or a number to be dialed. The order below is the order of priority in which they are used when applied to user dialing.
Using Lets Encrypt Certificates for Signed Certificates in
IP Office Contact Center
The purpose of this document is to provide guidelines for configuring Lets Encrypt certificates in IP Office Contact Center (IPOCC) and enable automatic updates to provide Signed Certificate validation for clients
Setting up Equinox on IP Office R11 Server Edition/hosted with Self Signed Certificate
In order to get Equinox client to securely connect to Server Edition or Hosted IP Office, we need to have a certificate. In a previous document, we showed how to create a 3rd party certificate, but maybe you don’t want to use 3rd party, maybe you want to leverage IP Office’s ability to create a self-signed certificate.
1 million foot view of the differences.Certificates that have been signed by a Certificate Authority go through some level of validation and there are only a finite number of Certificate Authorities worldwide. Most devices / browsers already have the Certificate Authorities Intermediate Certificate installed and can therefore easily validate the authorities certificate chain. Depending on the purpose / usage of a certificate would define the level of validation (and cost) associated with those certificates. The plus side to Signed Certificates is that there is no need to load self signed certificates onto most browsers or devices as they are already trusted. The Downside however is that signed certificates have to be maintained on an annual basis and updated before they expire.
With IP Office Release 11, Avaya Introduced Equinox as the UC/Soft-phone App. differing from other UC clients for IPO office, Equinox gets its IM/Presence components from the cloud. More specifically, the Zang Cloud, or Zang Spaces (http://zang.io/products/spaces). With Spaces you can sign up for a free account, and have some feature rich collaboration similar to the likes of Slack or Microsoft Teams.
If you like a video rather than reading….
As you can see in the diagram below, the Equinox client connects to the Cloud for IM/Presence needs, while connecting to the local IP Office (premise or hosted) for its telephony features.
Equinox on IP Office R11, seems to be giving everyone some fits. For this example, I defaulted an IP500 licensed for Essential Edition.
The installation will be part of the SIP Extensions guide. (https://downloads.avaya.com/css/P8/documents/101048082)
First, we will work on Essential Edition, so, see below for what licenses we need.
So, we obviously need the Essential Edition License. For the user, we need a “SoftPhone License” (Avaya Part number 383113, IPO R10+ SFTPHN 1 LIC)
For IP Office, with all the new applications and need for security, certificates are becoming more of a common place for iP Office programmers. Every certificate provider will do things a bit differently, but the basics and flows are the same.
For a signing authority, you need:
- Certificate Signing Request (CSR) and Private Key used to create the CSR
- Verification of Domain Ownership
IP Office Linux servers and IP500 V2 do not support the manual generation of a Certificate Signing Request (CSR) where the private key is retained within the server. Either a web form based request or a third party tool to create a CSR can be used.
To log in and connect to your IP Office system follow the steps below:
Note: the default user name and password is Administrator.
If your IP Office is not on a network and you wish to log in and connect to your IP Office system follow the steps below:
The WAN (LAN2) default IP address is 192.168.43.1
The LAN (LAN1) default IP address is 192.168.42.1
Note: the default Username and Password is Administrator.