Log into Administration for IP Office
To log in and connect to your IP Office system follow the steps below:
Note: the default user name and password is Administrator.
Category: IP Office
Note: the default user name and password is Administrator.
My IP Office system is not on a network. How do I connect & log in?
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:
Important note:
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.
SCN Dialing
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
- 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
- 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)
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:
- 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):
- VoIP Settings
- 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:
- VoIP Settings
Setting Up A Conference On A B149
This How-To covers setting up a conference on an Avaya B149 Analog Conference Handset. These handsets are supported from R7.0.
I have personally tested these steps on R9.0 and R9.1, but they should apply to any release the handsets are supported on.
Required Configuration:
Check there is a *47 Short Code in the IP Office configuration with the Feature set to Conference Add. If *47 is being used by something else other than Conference Add, create a new Short Code and use this new Short Code in the below steps.
Migrate Windows Voicemail Pro to Linux
With the UCM and the introduction of the Application Server, we no longer need to give money to Bill Gates or the Evil Empire (Microsoft). Then, once that took off, Avaya used that as a base, for Server Edition.
If you are scared that you will need to learn Linux, in order to work on treh UCM/Application Server/Server Edition, then fear no more. Think about it, we just use clients to program things….One-X Portal uses WebAdmin; IP Office uses Manager (or web manager); Voicemail Pro uses a client. SO nothing Linux yet.
Enable console output via telnet
Sometimes you can’t get a serial cable connected to an IPO but you need access to the debug port, ie, no serial cable or physical access. This doesn’t help if you’re looking for startup logs but it gets you access to an IPO that’s up and running.
Paging Via Voicemail Pro
Voicemail Pro can be used to deliver pre-recorded announcements. This can be useful when the same announcement is repeated frequently. This method requires the paging port to be an analog extension.
This method also removes the feedback loop that can occur on some sites as the page is first recorded and then played.
Example 1
-
In Voicemail Pro, a new Module was added and named Page.
-
-
A Post Dial action was added to the module. The properties of the Specific tab were set as shown:
Short Code: *80
-
IP Office Server Edition Backup
Often, we get questions from customers on how to do a backup to Server Edition. It is pretty easy, but most commonly I am finding that people are trying to save the Primary servers backup on the secondary and vice-a-verse.
Get Fingerprint Info!
IMPORTANT! If you might be restoring the backup to different server hardware, it is vital to get the fingerprint/UUID information with these 2 commands per Avaya’s documentation:
ipoffice get_fingerparms 2>&1 | grep “^FP_”
ipoffice get_fingerprint
FNE Codes Decrypted
With mobility (Mobile Twinning) becoming such a common part of life for workers, IP Office can do this with ease, even on Essential Edition.
Remembering that everyone can have Mobile Twinning for free, once the platform is licensed for Essential Edition and higher (Essential, Preferred and Server Edition).
| FNE Number | Feature | DID Numbers |
| 00 | System Dial Tone | 513-555-1000 |
| 01 | Steal Call | 513-555-1001 |
| 02 | Auto Call Back | 513-555-1002 |
| 04 | Forward All Calls | 513-555-1003 |
| 05 | Forward Busy and No Answer Calls | 513-555-1004 |
| 06 | Call Forward Disable | 513-555-1005 |
| 07 | Park Call | 513-555-1006 |
| 08 | Call UnPark | 513-555-1007 |
| 09 | Pick Up Group | 513-555-1008 |
| 10 | Directed Call Pick Up | 513-555-1009 |
| 12 | Withheld CLI (To External Calls off IPO) | 513-555-1010 |
| 13 | Enable CLI (To External Calls off IPO) | 513-555-1011 |
| 14 | Conference Add | 513-555-1012 |
| 15 | Drop Call | 513-555-1013 |
| 16 | Private Call (cannot be intruded or recorded) | 513-555-1014 |
| 17 | Held Appearance Select | 513-555-1015 |
| 18 | Same as FNE 00 – Dial Tone Appearance (a=) | 513-555-1016 |
| 19 | Enable Twinning | 513-555-1017 |
| 20 | Disable Twinning | 513-555-1018 |
| 24 | DND On | 513-555-1019 |
| 25 | DND Off | 513-555-1020 |
| 26 | Blind Transfer | 513-555-1021 |
| 27 | Transfer to Voicemail | 513-555-1022 |
As you can see by the above table, we need to assign every feature we want to use, to it’s very own DID number. Once set up, you just call that number to activate the feature. For instance, to turn o Twinning, you would dial 513-555-1017, from the phone number that is set up for mobile twinning….soo lets look at the IP Office side of things.
Click to call from Outlook
IP Office, back in the day, used to use TAPI to allow users to dial from Outlook Contacts. Now that Microsoft has entered the voice telephony, they have enhanced capabilities in their products.
With IP office Release 9, Avaya allowed the One-X portal desktop clients to enable the Smart Tag feature set. So, to have the ability that a user can click on a number in Outlook, Word or Excel, you first need to enable the Smart Tag options in Microsoft
Microsoft Outlook 2007:
1. In the Tools menu, select Options.