Avaya IP office new set up 1

[H3th3n]

Hello, I am brand new to installing any type of phone system. We do have IPO in use at our office and I manage the system through the GUI, but that is the extent.
We have added several offices and are looking to expand our IPO. The question is, besides the ip500v2 gateway and the phones, what other cards and licenses do I need to set up a purely IP environment for our new system. We want to establish SIP trunks in between our offices. Our existing phone system has some IP phones and some digital. We want all IP from now on.
Thank you in advance, and any ideas whatsoever would be greatly appreciated.

 

[Pepp77]

Become an Avaya partner and go on a course. Unfortunately you may struggle to get help on here because our jobs are to install and maintain these systems and we are paid by people who dont know how to do just that. Giving away what basically amounts to free support is not what Tek-Tips is for

| ACSS SME |

 

[emmitt2727]

If you are using Avaya IP phones, you will need enough Avaya IP endpoint licenses to cover each phone. Or 3rd party license if using non Avaya phones. Also, VCM resources will be key, as the number of IP phones increases.
Avaya uses what is calls Small Community Network or SCN to establish connections between systems. That requires an SCN license on each side. Not the only way, but an option. Hope this helps some.

 

[H3th3n]

Thank you for the information emmitt, we have a pretty good IT guy who has installed lots of PBX's, just not Avaya. We will figure it out even without Pepp's help.

 

[sizbut]

You'll have to figure it out without mine also if that's your attitude. You may not like an answer to get properly trained but don't get snide and snarky about it.

Stuck in a never ending cycle of file copying.

 

[H3th3n]

Ahh, I meant no ill will, just playing around. I do not want to offend anyone, my apologies if I did.

 

[intrigrant]

For each IP phone you need a license, there are two types, one for Avaya phones and one for 3th party phones (SIP).
If the remote sites have a decent VPN connection and you use VLANs then the setup is quite easy.
There are different scenario's on deploying IP Phones in respect to IP Adressing:
1 - with a local DHCP server capable of handling scope options
2 - with the "ip helper" option in the local gateway for the VLAN pointing to the DHCP server for the voice VLAN used on the main site
3 - static (manual) programming of the IP Phones.
In either way the IP Phones must be able to connect to the main telephone system to register.
Beside the licenses you need VCM resources which are only needed for IP > TDM calls or between IP devices using different codecs and for call signal sounds like dial tone and busy tone. IP to IP calls use direct media path were the IP voice traffic routes direct between the IP phones and not through the media gateway of the phone system.
For any type of trunks you need one VCM channel per trunk channel as direct media path is most likely not used/supported.

There are plenty of instructions to find on the net os take your advantage there and for specific configuration questions come back here but as you noticed we are not into helping to installing a complete system for novices, giving handouts is not a problem.