IP office Remote Access Options

The following are the Avaya recommended remote access options.

• Remote Manager: Default RAS connection to the IP Office. 
• Dameware: 3rd party application supplied with each IP Office application CD and is a free install. This software needs to be installed on any PC on which the application requiring support is running. For example, if Voicemail Pro is installed on a separate PC from that of Manager, then 
Dameware needs to be installed on both PCs for access to both applications. 
• PC Anywhere: Third party application that is licensed to the host and client. PC Anywhere is NOT provided by or licensed through Avaya. This software needs to be installed on any PC on which the application requiring support is running. For example, if Voicemail Pro is installed on a separate PC from that of Manager, then PC Anywhere needs to be installed on both PCs for access to both applications. Avaya Technical Support will use PC Anywhere to aid in the troubleshooting of certain issues, but the business partner must provide connectivity to the site 
and username and password information. 
• Webex: This third party application is a client service and requires customer interaction. This application is NOT provided by or licensed through Avaya. Avaya Technical Support can also use Webex as a remote desktop client for troubleshooting and data collection. With this application, the Avaya Tier 3 engineer assigned to the trouble ticket will provide access information to an Avaya qualified BP engineer. Internet Explorer 6.0 or newer must be available to use Webex. 

Remote Manager Setup

IP Office has default settings for remote access. This section walks you through those settings and setup for the remote dialup PC. Once connected, the remote PC is part of the IP Office network and can run many of the IP Office applications. 

A remote user must exist on the Manager PC as an initial step to setting up remote access. A remote user (Remote Manager) is available by default on Manager. This default user can be used for remote access or another user created if necessary.

To make use of the Remote Manager user, do the following to change the user password. 
1. Log onto Manager and open the IP Office configuration. 
2. Click User from the Configuration Tree. A list of users are displayed. 
3. Double-click the Remote Manager user (default user for dial-in access). 
4. On the User tab: 
• Extension: Leave blank 
• Password/Confirm Password: A default password is displayed, for security purposes, enter a new password. Make note of this password in a secure location as this is a remote access link into the customer’s network. 
5. On the Dial In tab, ensure that the Dial In On option is enabled/checked. 
6. Click OK and then to save the changes. 

To create a new remote user: 
1. Log onto Manager and open the IP Office configuration. 
2. Click the User form within the Configuration Tree to display the list of existing users. 
3. Right-click on the list area and select New. 
4. On the User tab, enter a Name and Password. IP Office is case sensitive. Make note of this password in a secure location as this is a remote access link into the customer’s network. 
5. In the Dial In tab, ensure that Dial In On is checked. 
6. Click OK and then to save the changes. 

Procedure – Step II

A RAS (Remote Access Service) is also required to enable remote access. Within Manager, a RAS entry called Dialln is available by default. There is no need to create a new RAS entry. The existence of this RAS entry can be verified by clicking the RAS form on the Manager Configuration Tree. A sample RAS configuration is provided below: 

Procedure III

A incoming call route for dial-in access (labelled DialIn) is available by default. Additional configuration (Bearer Capability setting) is available if necessary. 
To view or configure the incoming call route: 
1. Log onto Manager and open the IP Office configuration. 
2. Click the Incoming Call Route form within the Configuration Tree to display the list of existing call routes. One is labelled DialIn under the Destination heading. Double-click on the DialIn option. A window similar to the following appears: 
3. If using an analog modem, set the Bearer Capability to AnyVoice. If using Digital TA for any digital dial up (BRI, PRI or T1), set to AnyData. If using AnyVoice ensure that you don’t have another ‘Blank’ incoming number with a different destination in the LCR table. It is recommended the use of a specific DDI/DID with bearer set to Any. This is so all types of Dialn can be used. This requires a spare DDI/DID number. 
4. In the Destination drop-down box, leave as the default, Dialln. 
5. The values entered for any of the other fields depend on whether the remote user will be calling in on a particular line, phone number or from a set CLID. 
6. Click OK and then to save the changes. 

Procedure IV

The steps above are sufficient for an incoming digital data connection. However, if the remote user has an IP address that is not in the same domain as the IP Office, then an IP Route is needed for outgoing return data. If the remote user has an IP Address on the same subnet as the IP Office that was statically assigned you will need an IP Route within a 32bit mask configured with a destination of the RAS. Otherwise the IP 
Office will look to it’s local LAN for the local IP Range. 
• This is not necessary if the remote user has an IP address on same domain as the IP Office. 
• This is not necessary if the remote user’s dial-up connection method is set to ‘Obtain an IP Address Automatically’ and the IP Office’s DHCP mode is set to Server or DialIn. 

To create an IP Route:

1. Log onto Manager and open the IP Office configuration. 
2. Click IP Route from the Configuration Tree. 
3. Right-click on the list area and select New to enter the routing information. 
4. In the IP Address and IP Mask fields, enter the information of the remote system. 
5. In the Destination drop-down list, select the appropriate remote user (default is Remote Manager). 
6. Click OK and then to save the changes.   

SSL VPN

For IP Office release 8.1 and higher, the IP500v2 (v2 only, not v1) is capable of connecting to the Avaya VPN Gateway appliance.  This appliance can either be Avaya, for Backbone (tier3 or 4) access OR at the partner site.  For more information on the AVG, see this document:  SSLVPNSolutionsGuide.

Print Friendly, PDF & Email