380.57 & SIP problems

[RR-texas]

I have Merlin installed on an Asus RT-AC87U that serves my business. The Merlin firmware has been rock solid across many, many versions.

Two days ago I installed 380.57, which then killed the office VOIP service. We use cloud based PBX solution called Onsip. I also have a couple of phones registered with VOIP.MS for testing purposes and for backup in case of onsip itself going down. Onsip is rock-solid and a great solution.

Under 380.57, the onsip phones could not register with onsip. The VOIP.MS phones could register, but could not actually make calls.

I spent a couple hours tracking down the trouble, which I foolishly assumed could not possibly be the router firmware, since we've never had this trouble before. But in the end, it was clearly the firmware update to the router.

Changing WAN/NAT Passthrough/SIP Passthrough to "Enable" allowed the Onsip phones to register and calls to occasionally work. The VOIP.MS regsitered phones lost the ability to register with that service.

(Basically all cloud based VOIP providers advise turning off SIP ALG features, as about 98% of the implementations by router manufacturers don't actually work.)

Re-installed 378.56_2 and everything is back to normal.

This is deal breaker for me. Killing off the office phones means I have to stay with 378.56_2 until things settle down.

I was looking forward to the updates to OpenVPN in 380.57. But, that will have to wait for now.

Robert

 

[lifeisfun]

I was just pulling my hair out, same problem here.
Do we need to report it anywhere else?

Thanks

 

[hggomes]

ASUS, that problem is probably also present then on stock ASUS FW 380.1031 version.

 

[RMerlin]

My SIP ATA is working flawlessly here with 380.57.

 

[zaxcom]

I had the same problem. Had to enable the SIP ALG to make voip work. Which is not how it ever worked. Downgraded to the prior version of Merlin and my voip went back to proper operation.

 

[Aeradore]

WOW! I was just browsing the forums and found this post. I experienced this same issue using SIP a few days ago! I thought I was going to lose my mind trying to figure out what was going wrong. I even had VoIPo and VOIP.ms tech support trying to help me out. LOL! ObiTalk would lose calls a minute or so into the call, VOIP.ms couldn't register on port 5060 so I had to use port 5080 and then I couldn't make calls or it would drop a minute or less into the call, and VoIPo couldn't receive calls and would drop when trying to make a call. At the time it didn't even pop into my head that I had just popped Merlin's 380 version on our AC87U.

I have a unique setup in my house with multiple WiMax ISPs, a TP-Link r470t+ load balancing those WiMax ISPs and shooting them to a router for our home office and to the AC87U for the rest of our house. I allocate the office to use no more than 40Mbps/20Mbps and the house to use 60Mbps/20Mbps. The SIP phones worked on our other 2 routers however wouldn't work on the AC87U. I popped ASUSWRT on the AC87U and the SIP phones worked fine. Then I put the previous version of Merlin on it and the SIP phones still worked fine. When I put the 380 version of Merlin back on the SIP phones had the exact same issues again. I did try turning ON SIP Passthrough (which would normally kill the connections on our SIP adapters) but that didn't help any.

In the end I just reverted to placing our SIP phones directly on the office router and kept Merlin (380) on the home router.

 

[lifeisfun]

My SIP ATA is working flawlessly here with 380.57.

Just for the fun of it tried 3 ATA all fail to register
obi200, obi202, spa3000
On the older version no problem.
What ATA you using ?

Thanks

 

[RMerlin]

Just for the fun of it tried 3 ATA all fail to register
obi200, obi202, spa3000
On the older version no problem.
What ATA you using ?

Thanks

Cisco SPA112.

It's configured based on the Wiki page from voip.ms.

 

[Mavster]

I'm glad i found this thread, after upgrade to 380.57 my voip running SIP stopped working. It says registration failed. Sometimes i could just change ip of the Gigaset A510 SIP and it registered again but it didn´t work now. But switching SIP passthrough On made it work again so something have changed regarding SIP functioality since 378.56_2. Im using a RT-AC68U.

 

[Bohemus]

Not sure if this may be related to the issue outlined here, but my wife uses T-Mobile wifi calling and on 380.57 her iphone 6 shows that the phone is connected to T-mobile's wifi calling service, but when she tries to make a call wifi calling immediately disconnects. If I put her phone into airplane mode and enable wifi so calls can only be made over wifi calling, she cant make any calls nor receive them.

 

[lifeisfun]

Enabling SIP ALG on the new version fixed my VoIP registration problem.
Before it was always recommended to have it disabled.

Thanks

 

[lifeisfun]

Not sure if this may be related to the issue outlined here, but my wife uses T-Mobile wifi calling and on 380.57 her iphone 6 shows that the phone is connected to T-mobile's wifi calling service, but when she tries to make a call wifi calling immediately disconnects. If I put her phone into airplane mode and enable wifi so calls can only be made over wifi calling, she cant make any calls nor receive them.

Try to enable SIP ALG
Its in the last tab under WAN second from the bottom.

 

[Bohemus]

Try to enable SIP ALG
Its in the last tab under WAN second from the bottom.

Thanks, I'll give that a shot and see if it makes a difference. Appreciate the reply.

 

[Ache]

SIP Passthrough = off becomes broken in this version (and SIP Passthrough = on always was broken by design, wrong digest for auth).
See discussion started from here http://www.snbforums.com/threads/asuswrt-merlin-380-57-is-now-available.29308/page-19#post-228182
up to reply #367

SIP ALG also break digest and STUN, the best way is to not touch SIP headers at all, SIP client already have a tons of methods to bypass NATs by itself.

 

[lifeisfun]

SIP Passthrough = off becomes broken in this version (and SIP Passthrough = on always was broken by design, wrong digest for auth).
See discussion started from here http://www.snbforums.com/threads/asuswrt-merlin-380-57-is-now-available.29308/page-19#post-228182
up to reply #367

SIP ALG also break digest and STUN, the best way is to not touch SIP headers at all, SIP client already have a tons of methods to bypass NATs by itself.

Sadly you are right, I thought my problem is fixed but it still doesn't work right, sometimes it refuses to register. Will have to flash back to previous version

 

[NomadTech]

Sadly you are right, I thought my problem is fixed but it still doesn't work right, sometimes it refuses to register. Will have to flash back to previous version

With SIP Passthrough=ON and SIP ALG =Enabled, my 2 Galaxy S5 use WiFi calling without any issues. Once in a blue moon I'd get DNS error but that's from T-mo servers. Also have 3 VOIP acounts that have no problems registering. All on 380.57. Your issue might be somewhere else.

 

[Ache]

With SIP Passthrough=ON and SIP ALG =Enabled, my 2 Galaxy S5 use WiFi calling without any issues. Once in a blue moon I'd get DNS error but that's from T-mo servers. Also have 3 VOIP acounts that have no problems registering. All on 380.57. Your issue might be somewhere else.

In this version SIP Passthrough=OFF is non-functional (works nice before). Your Passthrough=ON success results are off topic (topic starter have it OFF initially as me too) and very depends on your provider, some of them ignores headers damage.

 

[lifeisfun]

With SIP Passthrough=ON and SIP ALG =Enabled, my 2 Galaxy S5 use WiFi calling without any issues. Once in a blue moon I'd get DNS error but that's from T-mo servers. Also have 3 VOIP acounts that have no problems registering. All on 380.57. Your issue might be somewhere else.

Well, why it works without a glitch then on the previous version?
I think Ache explained it well above

 

[Ache]

It seems it is fixed in the 380.58_beta1

 

[lifeisfun]

It seems it is fixed in the 380.58_beta1

Thanks! Will try later today