SIP Remote Worker

Posted Posted in IP Office

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:

read more

Short Codes Explained

Posted Posted in 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.

read more

Equinox on IPO R11 with Self Signed Certificate

Posted Posted in IP Office

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.

read more

Automate Spaces Install on Avaya R11 Equinox

Posted Posted in IP Office

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.

read more

Equinox on IP Office R11 Essential Edition

Posted Posted in IP Office

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)

read more

Create 3rd party Certificate for IP Office

Posted Posted in IP Office

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.

read more

Log into Administration for IP Office

Posted Posted in IP Office

To log in and connect to your IP Office system follow the steps below:

  • Double click on the IP Office Manager icon on your PC’s desktop or click on Start > All Programs > IP Office > Manager.
  • If a Windows Security Alert appears, select Unblock to allow the program to run.
  • Click on Open Configuration from the System.
  • Leave the TCP Discovery as the default IP address 255.255.255.255 and click on the Refresh button.
  • If the Manager locates an IP Office system it will show the IP Address of the IP Office system.If it doesn’t locate your IP Office system see My IP Office system is not on a network. How do I connect & log in?
  • In the top left hand corner, tick the box and press Ok. This will open the Configuration Service User Log in.
  • Enter the Administrative Server user name and password and click Ok to access the system’s configuration.

    Note
    : the default user name and password is Administrator.
  • read more

    My IP Office system is not on a network. How do I connect & log in?

    Posted Posted in IP Office

    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:

  • Connect an Ethernet cable to the LAN or the WAN(LAN2) Port, and to a stand-alone PC. The ports are located at the back of the IP Office System.
  • Ensure the PC is DHCP enabled.
  • Double click on the IP Office Manager icon on your PC’s desktop or click on Start > All Programs > IP Office > Manager.
  • When opening IP Office Manager it will check for the IP Office System. If the PC doesn’t locate the IP Office system, leave the TCP Discovery default IP address as 255.255.255.255 and click the Refresh button.
    Important note:
    The WAN (LAN2) default IP address is 192.168.43.1
    The LAN (LAN1) default IP address is 192.168.42.1
  • If a Windows Security Alert appears, select Unblock to allow the program to run.
  • If the manager locates an IP Office system, tick the box next to the default IP address and click Ok. This will open the configuration log on page.
  • Enter the Administrative Server username and password and click Ok to access the system’s configuration.
    Note: the default Username and Password is Administrator.
  • The IP Office configuration will now load and you can make any necessary changes.
  • read more

    SCN Dialing

    Posted Posted in IP Office

    This tutorial explains how to configure an SCN, and the ability to dial from a remote site, across an SCN network, to the main site’s trunks. The tutorial is divided into two sections, the first of which explains the configuration of Site A (the main site where the external trunks reside), and the second of which explains the configuration of site B (the remote site which needs to dial across the SCN, in order to utilize Site A’s trunks).

    Site A:

    • Address scheme:
      • IP Office LAN 1: 192.168.42.1
      • Subnet Mask: 255.255.255.0
      • Default Gateway: 192.168.42.200
      • Licenses/Hardware:
        • Confirm a valid Voice Networking license is installed.
        • Confirm a VCM or Combo card is installed.
        • Create a new H.323 Line:
          • VoIP Settings
            • Gateway IP Address: 192.168.43.1 (Site B IP Office address)
            • Supplementary Services: IP Office SCN
            Short Codes (sub-tab of H.323 line – this code is used for inbound matching – this tells the system how to handle calls when the digits 9N are matched, coming from site B)
            • Code: 9N
            • Feature: Dial
            • Telephone: N
            • LGID: 50:Main (local ARS table where external calls are routed)
            • Create a new IP Route:
              • This is a default route that will route traffic from any IP address/mask via LAN1. In cases where more granular routing is required, this route may need to be changed, but this works for most deployments:
                • IP Address: 0.0.0.0
                • Subnet Mask: 0.0.0.0
                • Gateway IP Address: 192.168.42.200 (local gateway on this network)
                • Destination: LAN1

                Site B:

                • Address scheme:
                  • IP Office LAN 1: 192.168.43.1
                  • Subnet Mask: 255.255.255.0
                  • Default Gateway: 192.168.43.200
                  • Licenses/Hardware:
                    • Confirm a valid Voice Networking license is installed.
                    • Confirm a VCM or Combo card is installed.
                    • Create a new H.323 Line:
                      • VoIP Settings
                        • Gateway IP Address: 192.168.42.1 (Site A IP Office address)
                        • Supplementary Services: IP Office SCN
                        VoIP line
                        • Outgoing Group ID: 1
                        • IP Route:
                          • IP Address: 0.0.0.0
                          • Subnet Mask: 0.0.0.0
                          • Gateway IP Address: 192.168.43.200 (local gateway on this network)
                          • ARS Table:
                            • Edit the existing ARS codes (in this example the 1N code is used, but the same must be done for all of the other ARS codes as well):
                              • Code: 1N
                              • Feature: Dial
                              • Telephone: 9N (send an extra 9 to trigger outbound dialing rules when the call is received by Site A)
                              • LGID: 1 (the LGID of the local H.323 line)
                              An ARS table with all of the codes changed is displayed below. Please note that dial emergency codes are not configured in this example, but it is always a good idea to have a local trunking solution for emergency calls.

                              Troubleshooting:

                              You should now be able to make calls from Site B, out of site A’s trunks. If you are unable to make calls, here are some troubleshooting steps:

                              read more