SIPSorcery Blog
Posted: Wed Jul 15, 2009 12:25 pm
Hi All,
I have started a new blog where I plan to publish posts about various bits and pieces related to the new sipsorcery set up along with anything else noteworthy. The blog is at:
http://sipsorcery.wordpress.com/.
I've decided to focus on using the blog to provide assistance as it was becoming overwhelming responding to posts on the forums due to both the increasing volume and demanding tone of the support requests (and I thought providing paid support was tough).
I still plan to read the forums as much as I can and will be looking to distill and group common problems into a post on the blog. The first one dealing with incoming call processing, which I've already noted has been confusing some people, is already there.
In regards to the current state of the sipsorcery service there are no known bugs except for the continuing issues with the Ruby engine - there will be a blog post on the near future - but suffice to say there have been some big improvements and the problem is NOT sporadic errors processing a dial plan it is the "Long Running Dialplan" message appearing due to the memory leak. If you think there is a bug in your dialplan processing then I'd recommend you troubleshoot your script as it's pretty much guaranteed the bug is there and not in the sipsorcery code.
I've been reading the bug reports and the above applies to things like TheFug's regular expression probelms and jvwelzen's use of == where it should have been =. Triple check your script and if you're really stuck you could try asking a question on stackoverflow.com but be warned it's a programmers hang out and you'll need to keep your question Ruby related and concise. Here's an example of how to ask a question http://stackoverflow.com/questions/1130 ... on-request.
The other ever present issues are the problems with getting such and such working with Provider X. There have always been quirks with certain providers and that hasn't changed from mysipswitch to sipsorcery. I've checked a few of the ones that have been mentioned in the forum posts, namely sipgate and pennytel, and did not identify any issues on the sipsorcery end. Doubtless there are other cases where something needs to be fixed or tweaked at the sipsorcery end and we need to come up with a way to efficiently troubleshoot provider integration issues. A two sentence post stating "Provider X doesn't work with sipsorcery. It works fine with my phone" is of no use.
It's been a very busy few months attempting to get the sipsorcery service running and I'm glad to see there are already 1260 user accounts (although that includes a few Chinese users setting up 20 accounts at a time to pump the calls through Betamax) and 894 provider registrations. I hope the majority of people continue to get something out of the service. If you find it doesn't work for you or get frustrated then please remember we don't get paid for this and in my case I spend a vast amount of my free time on the project (easily over 40 or 50 hours a week). A few words of encouragement of thanks make it a lot easier to get motivated to fix something than complaints. And if you're still not satisifed then there are other options that may better suit you such as voxalot or pbxes.org.
Best Regards,
Aaron
I have started a new blog where I plan to publish posts about various bits and pieces related to the new sipsorcery set up along with anything else noteworthy. The blog is at:
http://sipsorcery.wordpress.com/.
I've decided to focus on using the blog to provide assistance as it was becoming overwhelming responding to posts on the forums due to both the increasing volume and demanding tone of the support requests (and I thought providing paid support was tough).
I still plan to read the forums as much as I can and will be looking to distill and group common problems into a post on the blog. The first one dealing with incoming call processing, which I've already noted has been confusing some people, is already there.
In regards to the current state of the sipsorcery service there are no known bugs except for the continuing issues with the Ruby engine - there will be a blog post on the near future - but suffice to say there have been some big improvements and the problem is NOT sporadic errors processing a dial plan it is the "Long Running Dialplan" message appearing due to the memory leak. If you think there is a bug in your dialplan processing then I'd recommend you troubleshoot your script as it's pretty much guaranteed the bug is there and not in the sipsorcery code.
I've been reading the bug reports and the above applies to things like TheFug's regular expression probelms and jvwelzen's use of == where it should have been =. Triple check your script and if you're really stuck you could try asking a question on stackoverflow.com but be warned it's a programmers hang out and you'll need to keep your question Ruby related and concise. Here's an example of how to ask a question http://stackoverflow.com/questions/1130 ... on-request.
The other ever present issues are the problems with getting such and such working with Provider X. There have always been quirks with certain providers and that hasn't changed from mysipswitch to sipsorcery. I've checked a few of the ones that have been mentioned in the forum posts, namely sipgate and pennytel, and did not identify any issues on the sipsorcery end. Doubtless there are other cases where something needs to be fixed or tweaked at the sipsorcery end and we need to come up with a way to efficiently troubleshoot provider integration issues. A two sentence post stating "Provider X doesn't work with sipsorcery. It works fine with my phone" is of no use.
It's been a very busy few months attempting to get the sipsorcery service running and I'm glad to see there are already 1260 user accounts (although that includes a few Chinese users setting up 20 accounts at a time to pump the calls through Betamax) and 894 provider registrations. I hope the majority of people continue to get something out of the service. If you find it doesn't work for you or get frustrated then please remember we don't get paid for this and in my case I spend a vast amount of my free time on the project (easily over 40 or 50 hours a week). A few words of encouragement of thanks make it a lot easier to get motivated to fix something than complaints. And if you're still not satisifed then there are other options that may better suit you such as voxalot or pbxes.org.
Best Regards,
Aaron