IP office R12 with TP-Link Sip router

[dave_jey2004]

Hi,

Is there integration or admin document between AVAYA IP office R12 and 3rd party SIP router (TP-LINK router) connect with Service provider(DID).

Sample diagram below

 

[Mo. Abdullah]

i think you want to create a SIP trunk between IPO and the service provider. I haven't noticed a document like this before.
but others can help you here. what do you need?

 

[dave_jey2004]

Hi Mo. Abdullah,

As per sample diagram, i would to know how to configure IP office with SIP router (using TP-Link router). Is there document or guidance that i can follow steps.

thank you in advance

 

[ACSscott]

Who is the SIP provider? What model is the TP-Link? Generally it would be the SIP provider who has gotten their trunks certified with Avaya, and thus a whitepaper is generated from the SIP testing and certification which details all of the settings. Without this you're shooting in the dark a bit.

Also, I just thought of this as well... Is this TP-Link being used like an SBC? Where the SIP trunk provider is connecting to the TP-Link through your WAN and then the IP Office would be making a LAN connection to the TP-Link? Or is the TP-Link your router in general, and the SIP trunk provider's information is what's getting inputted into the IP Office? Those are two rather different setups.

 

[dave_jey2004]

Hi @ACSscott,

This is the TP link model

TP-LINK > AX1800 Dual-Band Wi-Fi 6 Router
Model : Archer AX23(US) Ver:1.20


Yes, the TP-Link is used like SBCE (customer on budget site).

Where the SIP trunk provider is connecting to the TP-Link through your WAN and then the IP Office would be making a LAN connection to the TP-Link? Yes this correct

 

[TouchToneTommy]

I can't give any advice specific to TP-Link, but here is the general information that we provide to our customers to give to their IT support:
(I can give specific advice on SonicWall, I know everyone hates them, but we have been successful with them 100%)
Take this and translate it for TP-Link:

A public IP address must be reserved on the customer’s network to communicate with the SIP trunk
     Public IPs can be shared between services, so long as no other service is using the following ports:
          5060 UDP and TCP
          46750-50750 UDP  (Check actual RTP range in IPO and match)
The following firewall policies need to be configured on the customer's firewall
     ALLOW:
          Inbound traffic to the Avaya IPO public iP address on port 5060 UDP and TCP from the following IP addresses
               1. List the SIP Trunk's Signaling IP's
          Inbound traffic to the Avaya IPO public IP address on ports 46750-50750 UDP from the following IP addresses
               1. List the SIP Trunk's Media IP's
               2. If the SIP Trunk Provider uses "Direct Audio" from the PSTN, list this as ANY IP ADDRESS
          Outbound traffic from the Avaya IP Office private IP address on ports 5060 UDP and TCP, and 46750-50750 UDP to ANY IP address
     DENY:
          All other inbound traffic

The following NAT policies need to be configured on the customer's firewall
     5060 UDP & TCP from SIP Trunk Provider's Signaling IP to the IP Office Private IP
     5060 UDP & TCP from the IP Office Private IP to the SIP Trunk Provider's Signaling IP
     46750-50750 UDP from the SIP Trunk Provider's Media IP's (or ANY if using Direct Audio) to the IP Office private IP
     46750-50750 UDP from the IP Office Private IP to the SIP Trunk Provider's Media IP (or ANY if using Direct Audio)

All SIP Transformations, fix-ups, inspections, or ALG's must be disabled on customer's firewalls, routers, and switches.

In the IP Office, you will use Network Topology for the LAN port that is connecting to the firewall, don't use STUN but instead clear the field and manually input the public IP, ports 5060 UDP and TCP, set firewall type as Unknown or Open Internet.