What i use: Yeastar S20 & 4x Yealink T48S & 1x Yealink W56P
With Firmware 30.7.0.27 outgoing calls drop after 30 seconds.
Back to the Firmware 30.6.0.20 everything is OK again.
I didn't change any other settings on the S20, the phones or the network - i just updated the firmware.
Is there a known bug?
Hello Patrik,
I met the same problem, Yeastar gave me a new firmware, please try update and see if this would help.
http://www.yeastar.com/download/temp/30.7.0.28.bin
Noted: This is not a official released firmware so I am not sure if there would be some other issues. So I don't suggest you to install this firmware to your customer's in use system.
Hi Oscar
Thanks a lot!
I downloaded, installed and tested this firmware with four calls... after 3-4 minutes i ended the calls manually.
I think that this issue is solved.
So it should also have been solved in the next official release, i think...
Cool! Glad to know it helps. Yes, my Yeastar Support contact told me they will release a new firmware and this will be include in the next official released.
I'm having the same issue with only outgoing calls getting terminated after 30 seconds. Incoming calls are fine. The S100 is running firmware 30.7.0.35
I tried rolling the firmware back to 30.7.0.28.bin as the previous user had done, but I'm still having the same issue.
I would suggest you to get some pcap logs and post the logs here.
Or submit a ticket to get help from Yeastar Support team.
What we discovered is that the client had recently switched ISP's and their static IP had changed. Once we adjusted this in the S100 (General > SIP ), the problem with outgoing calls dropping was solved.
hello there, recently i have been experienced the same problem i have the capture and sees that s20 sends a sip goodbye request to my client. however tell me how i can send you the pcap archive. thanks
firmware 30.10.0.51 also droopping calls after 30 seconds. Is there a fix yet?
I have the same issue Louis. Some calls drops after 30sec after this update.
I believe the problem is resolved by "Please disable the 'P Asserted Identity and remote party ID' in SIP settings -> advanced page, then check if all good.
The reason is caused by the 200OK headers didn't get the ACK"
hi everobody, i just reviewing if the problem was otuside the pbx, and in my particular case it seems it was rigth, all the route trough internet i follow from s20, to dsl modem (routers and balancer) i just disabled the SIP ALG option on firewall /nat sections, and it works, hope this could help
Louis, did you fix the issue by disabling the 'P Asserted Identity and remote party ID' in SIP settings -> advanced page?
My customer had been experienced the same issue, I did found there are un-recognized SIP Header in 200 OK and didn't received ACK.
Oscar, yes I believe that fixed the problem. Have not had same issue reported since.