Toggle sidebar Toggle sidebar

V16 Update 2 is Out with New SBC and Improved Website Chat

For those guys that had problems could you please tell me how many nameserver do you have in /etc/resolv.conf? Furthermore if you go to /var/lib/3cxsbc do you have core file?
 
MichaelB said:
For those guys that had problems could you please tell me how many nameserver do you have in /etc/resolv.conf? Furthermore if you go to /var/lib/3cxsbc do you have core file?
Click to expand...
The one we had an issue with has 3 nameservers. ISP, google, level3
In /var/lib/ there is a 3cxsbc directory with no files in it. However, we have now ran the install script since we had the issue this morning so I'm not sure if that changed anything.
 
Did you run the script 3cxsbc.zip or 3cxsbcV15.zip?
 
MichaelB said:
Did you run the script 3cxsbc.zip or 3cxsbcV15.zip?
Click to expand...
I ran the 3cxsbc.zip command.
When I was first made aware of the issue, I checked the SBC version and it was running 16.0.x and the 3CX system was running v16sp1.
After I tried restarting the 3cxsbc service and rebooting the sbc without any progress, I went ahead and upgraded the 3cx system to v16sp2 and then ran the 3cxsbc.zip command to configure the device.
At that point, all the phones began coming online.
 
  • Like
Reactions: accentlogic, Evolute IT and jed
Is there any update on the Virtual Extension number for Call Flow Designer Applications? Currently our only option is to create an inbound rule to redirect a specific number to the application which is not always ideal solution for us.
 
ibrahim akgün said:
Is there any update on the Virtual Extension number for Call Flow Designer Applications? Currently our only option is to create an inbound rule to redirect a specific number to the application which is not always ideal solution for us.
Click to expand...

Hello @ibrahim akgün ,

Thank you for your feedback first of all. We are examining internally the approach that we will improve the configuration points of CFD Applications. Stay tuned and we hope that soon we will have an update on this.
 
Yes experiencing something very similar, auto updates pushed 16.0.910 to 3cx from 16.0.273, SBC 15.5 stopped functioning. Uninstalled SBC pushed in SBCv16. new auth key etc. Every hour the SBC stops communicating with 3cx server and i need to kick the Service over to get it to register all the phones again.
Also noticed settings reverting in 3cx. Phones being removed I installed the previous day. ??

Just want to roll back to 16.0.273 cant have customer offline line this.

Anyone know how to roll back , 3cx dont have resource here in AU that can assist i have config backup prior

Thanks
 
Joseph Oimi said:
Yes experiencing something very similar, auto updates pushed 16.0.910 to 3cx from 16.0.273, SBC 15.5 stopped functioning. Uninstalled SBC pushed in SBCv16. new auth key etc. Every hour the SBC stops communicating with 3cx server and i need to kick the Service over to get it to register all the phones again.
Also noticed settings reverting in 3cx. Phones being removed I installed the previous day. ??

Just want to roll back to 16.0.273 cant have customer offline line this.

Anyone know how to roll back , 3cx dont have resource here in AU that can assist i have config backup prior

Thanks
Click to expand...
I would suggest the following, leave the PBX on v16.0.2.910 (Update 2), that is most likely not your problem.
A few minutes ago we released a minor update for the new SBC software which is v16.0.386. This should address most issue some of you reported. The issue from what we could determine was due to nameservers existing on the SBC machine that were not valid, causing the SBC software to eventually timeout and generally misbehave.
Upgrade the SBC to v16.0.386 and check if it is still happening.

IT make take a few hours for the update to become available to all, but it will show up in the Management Console eventually.
Also because there has been some talk about SBCs auto-updating, the older version of the software did indeed have a cronjob for this. In the new version this does not exist and upon install the new version, even older cronjobs are removed.
So the SBC upgrade needs to be done manually form the Management console.
 
NickD_3CX said:
I would suggest the following, leave the PBX on v16.0.2.910 (Update 2), that is most likely not your problem.
A few minutes ago we released a minor update for the new SBC software which is v16.0.386. This should address most issue some of you reported. The issue from what we could determine was due to nameservers existing on the SBC machine that were not valid, causing the SBC software to eventually timeout and generally misbehave.
Upgrade the SBC to v16.0.386 and check if it is still happening.

IT make take a few hours for the update to become available to all, but it will show up in the Management Console eventually.
Also because there has been some talk about SBCs auto-updating, the older version of the software did indeed have a cronjob for this. In the new version this does not exist and upon install the new version, even older cronjobs are removed.
So the SBC upgrade needs to be done manually form the Management console.
Click to expand...

Thanks Nick , After reading the release notes it does explain why the SBC 16.384 continually needed to be restarted to bring the phones on line every hour and why the Calls made via the SBC failed to authenticate via the sip trunk provider. The SBC was just was not hitting the PBX by resolving DNS

SIP Server/Call Manager ID: 12294
Call or Registration to Sip Provider has failed. sip:03964#####@sip.sipprovidor.com.au:5060 replied: 403 Authentication Failure; from IP:202.1##.###.###:5060


Upgrade completed, rebooted everything , seems stable. But this puts me back to a Beta testing situation.

I understand that errors are needed to correct issues and progresses the product forward. But live customer systems are not 3cx's testing play ground. These customers are real time. The circle of life is , Customers pay them , they pay us , we pay 3cx. No customers at the start why should the rest of us get paid? In this instance I asked for a roll back, because i had 3 days of instability. If i lose the customer its because testing was too loose and support has not supported us. Then refunds are asked from us and warranted by 3CX according to Local Australian consumer law. I suggest 3cx Quality Assurance look deeper into patch releases with checks into prerequisites
I will post back here in a couple days if all is stable to assist others
Ticket 457519

Australian support needs further retraining. No help was offered here just the finger pointed elsewhere

Thankyou for your help Nick you've probably saved my bacon

J
 
  • Like
Reactions: zeroplex
what's the update that got pushed today or yesterday? I see a new update available already for the SBC.
 
  • Like
Reactions: accentlogic
@pmterp - thanks.

@NickD_3CX - how do we get the RSS feed active for the release notes? If I try and add it to our stuff - I get invalid credentials.. we don't check the release notes unless we get a notification - but it seems like we're not posting blog/newsletter info out, but still doing updates. It would be so much easier for a lot of folks to know proactively when those are updated.
 
  • Like
Reactions: accentlogic
I read that the 3CX SBC performance is improved. Does this also mean that it can support more than 100 phones? We normally have the 3CX running in the cloud and a debian SBC on premise (CPU i5). Soon we will need to install a 3CX for an hotel with 150 phones. Can we use the new SBC for this, or is the only solution that we run the 3CX not in the cloud but inside the hotel?
 
We did the v16 2 update then updated the sbc to v16.0.384. All looked fine sbc connects to server but all our phones have dropped out and will not connect even with a factory restore. Can't get them to show in the 3cx portal at all. I did all updates from the portal and all seemed to work ok. We have had no phones now since yesterday. I cant work out what's wrong. I have restored our server to previous version. 16.0.2.910 and it still doesn't work. I have tried to re-install sbc ver15.5.9414 and still will not work. The big difference for us is that we do not use any standard ports on both server and sbc and believe this may be the issue. We have been throw out of the partner program (again) because we don't earn 3cx enough money, so feel we have no where to turn for support!! Anybody any suggestions? most things people have suggested already on here do not work for us.
 
@InfotechUK
If you use non-standard SIP port for SBC, you have to locate 3cxsbc.conf.local, find #LocalSipPort there, uncomment it (remove #) and put the needed port. Save and restart the SBC.
Feel free to send me a message if you need more info.
 
vkd said:
I read that the 3CX SBC performance is improved. Does this also mean that it can support more than 100 phones? We normally have the 3CX running in the cloud and a debian SBC on premise (CPU i5). Soon we will need to install a 3CX for an hotel with 150 phones. Can we use the new SBC for this, or is the only solution that we run the 3CX not in the cloud but inside the hotel?
Click to expand...
150 phones for this specific case should not be an issue at all as not many hotel guests talk on the phone at any given moment.
 
You must log in or register to reply here.

Latest Posts

Forum statistics

Threads
111,991
Messages
590,166
Members
164,929
Latest member
Cloudstar
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom