TP-Link TL-ER5120 V2.0 - issue with SIP/VOIP after failover / fallback - only restart of router helps

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

TP-Link TL-ER5120 V2.0 - issue with SIP/VOIP after failover / fallback - only restart of router helps

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
TP-Link TL-ER5120 V2.0 - issue with SIP/VOIP after failover / fallback - only restart of router helps
TP-Link TL-ER5120 V2.0 - issue with SIP/VOIP after failover / fallback - only restart of router helps
2016-09-28 15:30:52 - last edited 2021-08-21 05:51:10
Model : TL-ER5120

Hardware Version :

Firmware Version : latest

ISP :

TP-Link TL-ER5120 V2.0

Latest Firmware.

we have setup 2 primary WAN (WAN1, WAN2) and one as backup (WAN3). Enabled policy routing and set all clients to use WAN1.

Failover/falback works - but we have issues with sip /pbx.

Here are the steps and problems that we have:


[*]unplugged WAN1
[*]failover to WAN2 works
[*]outgoing traffic is from WAN2 (whatismyip.com)
[*]PBX reports no registration to provider
[*]waited 5 minutes - still no connection to sip provider
[*]surfing/browsing works correctly
[*]connected WAN1 again
[*]fallback to WAN1
[*]outgoing traffic is from WAN1 (whatismyip.com)
[*]Checked PBx again - still no registration to sip provider
[*]waited additional 5 minutes
[*]disabled provider / enabled provider in pbx
[*]checked pbx again - still no registration to sip provider
[*]restarted complete PBX
[*]check pbx again - still no registration to sip provider
[*]restarted TP-Link router
[*]disabled provider / enabled provider in pbx
[*]PBX works and providers registered.

Any help is greatly appreciated.
  0      
  0      
#1
Options
1 Reply
Re:TP-Link TL-ER5120 V2.0 - issue with SIP/VOIP after failover / fallback - only restart of router helps
2016-10-04 15:16:40 - last edited 2021-08-21 05:51:10
I could verify that this is a bug. Here are the details and a workaround:

After failover from WAN1 to WAN2, the Router is using the wrong Source-IP for outgoing SIP/UDP packages.

Router is using on WAN2 its source-ip from WAN1. So for the upstream router, this is an unknown package and the return packages are dropped.

I fixed it with an additional route at the upstream router at WAN2.

WAN1 = 172.16.0.
WAN2 = 172.16.1

So my route is 172.16.0.0/24 via 172.16.1.1 (tp link routers wan2 interface).

I hope this get fixed soon.
  0  
  0  
#2
Options

Information

Helpful: 0

Views: 1011

Replies: 1