But my comment was completely accurate: if you post an issue here, you're not assured of a reply--either to confirm/deny or offer answers. Sometimes there is one, often enough not. On a new product, peer response is not sufficient.
Yes it is an open forum for a product with a generous free section in my opinion compared to other products. There are support agreements with SLA's and you can purchase them. You will get support staff to answer your questions within 24 hours.
Of course this is highly technical stuff; that's why responsive support is even more essential. There is
a huge chance for installer errors and confusion.
Read manual, documentation and forums help a lot. If the machine is healthy installer errors will not occur. Everything is inbuilt in 3CX. You dont need to install a database for example - we package with it. There is no need for a webserver. We package it too. We package the sip engine, we have good documentation, active forums, blogs, videos, i fields, - come one information is out there. this is not a closed box or you have to dig heavily or run telnet and command prompt scripts to run the application.
In this case, I believed 3CX explicitly provided a feature to simultaneously ring a local and either a mobile or any other non-local extension. That is what is provided elsewhere; not just for mobiles.
No the feature was to ring my mobile and my extension simultaneously. And this is exactly what we provided. If you want something else create a dummy ring group and add anything you want in there. If you want to work, this is non trivial for you. In the meantime open a feature request and work with this workaround until it is implemented. We are always looking for positive and negative feedback. We take serious action on many requests. And we have workarounds you can apply. Workarounds that you can implement until we nail the problem - if there is a problem.
I need help to get this working, and I provided some fairly complete setup information when I first posted.
I guided you in what you need to do. Enter mobile number with prefix, enable checkbox in rules and call the extension. it will work out of the box. if there are problems I would like to know what they are because keep in mind that the problem might not be in 3CX after all.
Sorry, but other SIP product support does not always and automatically request Wireshark captures. It is a tedious and time-consuming effort. In some cases, they are essential, others not. There are distinctions.
Wireshark capture takes 2 seconds. this is ridiculous. It took you more time to complain on this tread. You have time to moan here but you see a simple wireshark capture as time consuming? Again this is ridiculous. Other sip products drown in wireshark captures because it is the best way to troubleshoot network errors, sip errors and truckloads of other responses. We are not asking you to analyze them - we just want you to send it. Go and open a support request whereever you want - see with your own eyes what they tend to ask for. I open support requests as well on enterprise mainstream sip manufacturers - I know what I am talking about because I also ask for support like you. No one can work without a capture.
In this case, if 3CX were to check the scenario I used, I don't believe it will work. Either I misunderstood the feature, didn't setup properly, or the feature doesn't work. You don't need Wireshark to answer those issues-- you simply need to look at the scenario and correct it. (Or, if it was setup as required, test and fix it.)
This feature works 100%. If you are in doubt prove me otherwise. If there is a bug i will not think twice of saying so just like I do with thousands of my partners and beta testers on a daily basis. Our intentions are to fix the problems not hide them. yes you might have configured it incorrectly. You might need to tweak your gateway. You might be using unsupported stuff. You might have a network condition. You might have some port leak on the machine. who knows?
Finally, I don't see a place on this forum for bug reports.
The community can open bug reports yes - but they are selected. Others can open from the forums and title the subject BUG. There are people monitoring the forums every single day and on the lookout for bug reports. Others can open issues through a special portal. We have honeypots, and servers out on the internet for users to test and prove their results - they also agreed to pass through bug reporting training too. And most of all they are more than willing to make wireshark captures. How can you expect to post bugs without having actual proof of what you are experiencing?
I appreciate the product, and your work, Nicky. This is not a slam, but a plea for revised support strategies. Dave
I am taking time to answer you and see what the problem is and in return you stay writing compositions with notepad. Just tell me what the problem is and justify your findings with a backup and a capture. I'm not asking for much. You can send it to my email
[email protected] since there will be sensitive information there which is not to be put on the forums.
