Avaya IPO Call2Teams Setup Commsplus

Avaya IPO Call2Teams Setup Commsplus

CommsPlus DistributionA picture containing text, clipartDescription automatically generated


Avaya IPO Call2Teams Setup

Port Forwarding

Call2Teams registers users as SIP extensions on the Avaya IPO

The Call2Teams public IP addresses will be provided when you setup the PBX in Call2Teams

These public IP addresses will need to be allowed through the firewall to the Avaya IPO internal IP address to allow registration and voice traffic.

Depending on the method of registration, you will need to configure one of the below ports on the firewall.

5060 UDP (if registering via UDP)

5060 TCP (if registering via TCP)

Additionally, you will need to allow the below UDP port range (RTP ports for voice traffic)

46750 through to 50750 UDP (if using an Avaya IP500v2 PBX)

40750 through to 50750 UDP (if using an Avaya IPO Server Edition)


FQDN or Public IP Address

An FQDN or Public IP address can be used with Call2Teams. In our guide we have used an FQDN for the SIP Domain and FQDN


Additional Requirements


Avaya IP500v2 PBX will require a VCM card
Avaya IPOSE does not require VCM card (the VCM channels are built in)

Avaya IP500v2 PBX with PLDS licensing will require a 3rd Party IP Endpoint License for each Call2Teams extension
If Call2Teams extensions are remote, the first 4 users can have Remote Extension enabled to allow registration
If additional remote Call2Teams extensions are required, then a Preferred Edition license is required on the IP500v2, plus a Teleworker or Power User license per Call2Teams extension, to allow Remote Extension


Avaya IPOSE with PLDS licensing will require a 3rd Party IP Endpoint License for each Call2Teams extension
If Call2Teams extensions are remote, then the user will need Remote Extension enabled (all basic user on IPOSE can have Remote Extension enabled, there is no requirement for User License)

Avaya IPOSE with Subscription licensing will require a Basic Telephone User License (or Telephony Plus or UC) for each Call2Teams extension
If Call2Teams extensions are remote, then the user will need Remote Extension enabled (all Basic Telephone Users on IPOSE can have Remote Extension enabled)

Call2Teams User License (per user)

Microsoft365 Phone License (per user)


IPO SetupSystem, LAN1, VoIP

Tick the box for SIP Registrar Enable

Tick the box for SIP Remote Extn Enable

Enter a valid SIP Domain Name (this can be a Domain or Public IP address)

Enter a valid SIP Registrar FQDN (this can be a FQDN or Public IP address)

Tick the boxes to enable UDP, TCP


Enable RTCP Monitoring on Port 5005

Set Keepalives Scope to RTP-RTCP

Set Initial Keepalives to Enabled

Set Periodic Timeout to 5 (seconds)

A screenshot of a computerDescription automatically generated


IPO SetupSystem, Network Topology

Set Firewall/NAT Type to One-To-One NAT

Set Public IP Address (this will be the public IP address of where the IPO is located)

A screenshot of a computerDescription automatically generated

IPO SetupLicenses

If using PLDS Licensing, confirm there is a valid 3rd Party IP Endpoint License per user.

If using Subscription licensing, a valid Telephony, Telephony Plus or UC license will be required per user.

A screenshot of a computerDescription automatically generated


IPO Setup  Users - User

Create a User with Name and Full Name

Set a Password

Set an Extension

Enable Remote Worker

A screenshot of a computerDescription automatically generated

IPO Setup – Users - Voicemail

Set a Voicemail Code (confirm voicemail code)

A screenshot of a computerDescription automatically generated with medium confidence


IPO Setup – Users – Telephony – Supervisor Settings

Set a Login Code (confirm login code)

IPO Setup – Extensions

Create a SIP Extension, set a Phone Password, and confirm (make this the same as the User Login Code)

A screenshot of a computerDescription automatically generated with medium confidence

Un-tick Allow Direct Media Path

A screenshot of a computerDescription automatically generated with medium confidence

Save the Config


Call2Teams Setup – PBX

Select Services, PBX

Select Add Additional PBX

Setup the PBX details and select Add PBX, Select Custom

Enter a Service Name and set the Country.

In SIP Domain, enter the SIP Domain configured in the Avaya IPO

In SIP Proxy, enter the SIP Proxy configured in the Avaya IPO 

Note: if you are using different ports for UDP or TCP in the Avaya IPO (to the default 5060). Then the SIP Proxy will need the port used.

Example, if the TCP port on the Avaya IPO was configured as 5070.

The SIP Proxy would be.

ipo.cawoodcomms.xyz:5070


Setup the Calling Policy and select Save.

Set the Protocol as required

Set the Propagate Refer as Teams handles transfers

Note: The IP ranges assigned to the service, these are the public IP addresses for Call2Teams and these will need to be allowed in the firewall to allow SIP registration to the Avaya IPO


Users

Select Add User

A screenshot of a computerDescription automatically generated with low confidence


Select the User from the drop-down list.

Enter the Users phone number (this number is the one assigned to the User in Avaya IPO)

Select the PBX to register against

Set the SIP Username and Auth Username as the Extension Number in the Avaya IPO

Set the Password as the Extension Password in the Avaya IPO (the User Login Code in the Avaya IPO should be the same)

A screenshot of a computerDescription automatically generated with medium confidence

Select Add


The User Registration will be green if registration to the PBX is successful.

Avaya IPO System Status

Check in Avaya System Status to confirm the User is registered.

A screenshot of a computerDescription automatically generated

Once registration has been confirmed, login to Teams to make and receive calls.



Microsoft Teams 

Open Microsoft Teams

Select Calls

Enter a number and test calls outbound.

Test inbound calls to confirm working also.