each site will need a networkng license for you to link them and they will need to be on there own number range
ie 1xx or 2 xx . or 11xx or 12xx etc .
you need to build the networking tables up .
each site will need its own static ip address .
and you will need portforwarding in place for networking as well set up on each router with firewall rules in place as well . as lg systems love to get hacked on the networking ports so you need to tie them down to each others site etc .
its quite easy to do once you know how.
you will alo need the voim resources on each system to do this and decide how many intersite trunks you want to give them .
this will be determined by the size of the site normally .
for small sites i normally set up 2 trunks for intersite calls .
for larger sites this can be anything.
if youre unsure how to do this i suggest you contact a local reseller with trained engineers.
You can get basic functionality by using SIP peering. Create some SIP trunks and have the registration address as the IP of the other system, this would work better with a VPN type connection between sites.
Don't need a network license to connect systems, but if the call goes to the other system and then is returned back to the original system it doesn't drop those voip channels until the call is finished, so you'll use 2 channels going out, and 2 more coming back in again. With a network license it just drops the voip channels when it drops back to the main system. I think there's a couple things that don't work, but I've done it several times and it works fine. A vpn connection avoids all the port setup stuff, of which you'll need I think 1720 udp open to connect the 2 systems as well as the rtp channels.
if you network them correctly its tcp 1717-1720 tcp you need to forward to each system and if you want the busy lamp fields to work you also need udp/tcp 9500-9501 as well .
but you will need to get teh network licenses and this way you will be able to transfer calls and route calls accross sites with out the need for building loads of tables lol
Yes, It's 1720 TCP, not UDP. Portusage docs don't mention 1717-1719, only 1720 if you go external. Not sure about BLF, don't see those ports in the doc either, but I've not been asked for that feature. I'll have to test that stuff sometime.
A vpn between sites makes things way better, more secure and no ports to open. You still need to build tables though. I've put in a few network systems with and without licensing. For just intercom calls it works fine without licensing. If you're transferring outside calls between systems a license means less problems, full tech support and a happier customer/boss. I'd set it up without networking, try some calls and then activate demo mode(60 days) which turns on full networking amongst other things, and try that out. You have 6 shots at demo mode on emg80's or ucp, so use them sparingly. Make sure to turn networking mode on in system network settings and turn off the attendant alarms for demo mode and networking expiry to make your life easier.
You can also do features like paging across the network, and remote dial tone from the other system, but get networking working first then try the tricky stuff.
The number of total active voip channels between sites, remote phones and sip lines will affect service. Default on an emg80 is 2 channels, so only 2 calls at a time. It needs at least 4-6 channels if you're networking, have a couple sip lines and a couple of remote phones, or people will get dead air and not be happy.
The built in networking works well, use sip for in and outgoing calls and that's it.
Apparently you can also network these to other systems. Never tried it but you never know...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.