[SLOVED] RT-AC87U 380.61 SIP:55566 Registration failed

[amrhf]

Hi all,
Great router, great firmware, but I have problem with my IP phone Gigaset S685IP.
I have public IPv4 on WAN port and private range on br0:

12: br0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether 1c:cc:cc:cc:cc:cc brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global br0
inet 169.254.39.17/24 brd 169.254.39.255 scope global br0:0

THe IP phone has got assign static IP, and I have port forwarding setup for traffic comming in:
3478 3478 192.168.1.2 3478 UDP
5060 5060 192.168.1.2 5060 UDP
16384-32767 16384:32767 192.168.1.68 ---- UDP



On one account, rest of them work great on standard 5060, I am getting "Registration failed"
yes I have checked everyting many times, setup same account on Tablet with cSIPSimle clinet
and that does not work either when connected via RT-AC87U WI-Fi, but if I connect the tablet via another
network/mobile network it will register on those credential, bit when I disconnect and connect back
to RT-AC87U it dones not work and fails to connect


I think the problem is that that SIP account is using specific port 55566 rather than 5060, but I'm
not good with iptables.

Trying "iptables -t nat -L" I can't see anywhere that outgoing udp on 55566 port should be blocked .....

Any ideas anyone?


I have on:
WAN - NAT Passthrough enabled SIP Passthrough ONLY.
Firewall - General NAT Loopback: Merlin


I have acces to SSH on the router as well as Web GUI on WAN side.

Thanx in advance.

 

[Sunny]

I have a Gigaset S685IP running on a rt-ac68u (merlin)

I occasionally see random "Registration failed" on some of my sip accounts and usually a reboot of the router fixes it... not sure what causes it too ?

However lately running the latest merlin I haven't seen the issue for a while?

 

[amrhf]

I have a Gigaset S685IP running on a rt-ac68u (merlin)

I occasionally see random "Registration failed" on some of my sip accounts and usually a reboot of the router fixes it... not sure what causes it too ?

However lately running the latest merlin I haven't seen the issue for a while?

It turn out to be problem with my Asterisk IP configuration and Asus was the only router refusing to talk to it, unless it was corrected.