Connect two IP offices offsite?

[TheWiz002]

Hello

I know you can establish connects via IP phones to one local IPO but can the following be accomplished?

Site A:
IPO 412


CONNECT TO

SITE B:
IPO 406

The goal here is to have 2 systems and connect them so each site can call each others extension.

On a definity they called it a EPN (extended private network)

Thanks

 

[kwing112000]

this is called SCN.

Start here

http://marketingtools.avaya.com/knowledgebase

You will need to create an IP trunk between the 2.

Kevin Wing
ACA- Implement IP Office
Carousel Industries

 

[mikegillespie]

This is very commonly done and it does it well. See Kwing's recommendations. The knowlegbase will guide you through this

 

[TheWiz002]

i searched that above site for "SCN" nothing came up for any type of site to site trunking or similar..?

 

[TheWiz002]

Maybe you meant this..

Small Community Networking

When connecting IP Offices together over IP or Packet based networks, Small Community Networking enhances feature transparency. These networks can support up to a maximum of 500 users across 16 sites. The following additional features are available.
• Busy Lamp Field.
• Camp-on.
• Call Back When Free.
• Paging.
• Call Pick-up.
• Centralized Voice Mail (VoiceMail Pro)
Support for mailboxes, call recording, dial by name and auto attendants. Remote queuing on remote systems is also supported with the Advanced Small Community Networking license (see below).
• Internal Directory.
• Absent Text Message.
• Anti-Tromboning.

scn

For Small Community Networks VCM modules are required in all systems being connected. The IP lines should be configured to connect the IP Offices in a star configuration, however the data network itself can be meshed. Also the names and numbers (groups, line, services, etc) on the separate IP Office systems should be unique to reduce potential maintenance confusion.

Each IP Office system broadcasts UDP messages on Port 50795. These broadcasts typically recur every 30 seconds but BLF updates are potentially more frequent. There are no updates if there is no activity and the overall level of traffic is very low – typically less than 1 kbps per system.

From IP Office Release 2.1(35) and higher, SCN is supported between IP Office systems with differing software levels but network features will be based on the lowest level of software within the network. This option is intended to allow the phased upgrading of sites within a SCN and it is still recommended that all systems within a network are upgraded to the same level where possible.

If larger networks are required QSIG can be used to link multiple Small Community Networks together. Functionality between the communities is governed by the QSIG feature set.

Note: On IP500 systems, Small Community Networking requires one or more additional licenses.



Small Community Networking - Advanced Networking Features

IP Office R4.0 allows a number of additional feature to be enabled by addition of an Advanced Small Community Networking license. Those features are:
• Distributed Hunt Groups
Hunt groups can include users located on other IP Office systems within the network.
• Remote Hot Desking
Users can hot desk between IP Office systems within the network. The system on which the user configured is termed their 'home' IP Office; all other systems are 'remote' IP Offices. To log on at a remote IP Office requires that IP Office to have an Advanced Small Community Networking license. A license is not necessary on the user's home IP Office.
• Breakout Dialing
This feature allows the user to select an IP Office system in the network from a displayed list and then dial a subsequent number as if dialing locally on the select system. This feature is triggered either by a programmable button or short code.



Note that both Distributed Hunt Groups and Remote Hot Desking are not supported for use with CBC and CCC.

The Advanced Small Community Networking license is required in every IP Office site where remote workers are expected to hot desk to as well as on every site where members are included in distributed groups.

 

[kwing112000]

Correct. What you will need to do is go into lines and then create a new IP line. I usually start my IP lines at 100 and work upwards from there. each site will need a line that has a unique line group and incomming and outgoing group ID. Then on the VOIP tab you will need to put the gateway address in. this is the address of your far end IPO. THen choose your codec. Usually 729A on the WAN. THen for the check boxes. Make sure fast start, Out of Band DTMF, Voice Networking(this is the SCN) are turned on. Also you will need to make sure nothing overlaps for extensions and hunt groups. THen you should be able to dial to the other extensions. if you need to dial hunt groups then you will need short codes.

Kevin Wing
ACA- Implement IP Office
Carousel Industries

 

[TheWiz002]

Kwing

where is the 729A your referring to and the only similar Voice Netorking i have is VoIP silence suppression...?

 

[Westi]

the settings are under the IP Line - VoIP settings - Compression mode
by default it comes up with Automatic.
The gateway is the other IP Office, make sure you have an IP route in the IP Office setup to be able to reach the other network.
then do as Kwing112000 said with the other points and try calling an extension on the other IP Office (after BOTH are setup), The IP Offices exchange information via AVRIP packages on the network to learn each others extensions.

Joe W.

FHandw., ACS

If you can't be good, be good at it!

 

[Westi]

http://support.avaya.com/elmodocs2/ip_office/job_aids/19_small_community_networking.pdf

this might help, it is a few years old but still has all the basics in it.

Joe W.

FHandw., ACS

If you can't be good, be good at it!

 

[TheWiz002]

PERFECT THANKS !