Some of you may have seen the press release from Microsoft announcing the release of the Response Point PBX and the role of Junction Networks as a preferred service provider. Our favorite write-up of the partnership was over at Asterisk VOIP News, though that may be because they included a glowing note from the editor about the reliability of our service. We tested the Response Point in our labs, of course, and found the setup to be almost ridiculously easy. The test network was set up and ready to go within 30 minutes of unpacking the box the system came in. Most of the Response Point customers that we've spoken to report a similar experience.
Tech Talk- IT & Code
Posted by Charlotte Oliver at 04:37 PM EDT
Posted by Erick J Johnson at 05:28 PM EDT
Did you know that Junction Networks has a public web service API available to any of our customers that exposes all of the pieces necessary to manage your own hosted PBX and PSTN gateway services? In fact our admin.onsip.com web administration portal has been built entirely on top of the very same API that is open and available to the public - this means any feature you see in our administration portal is potentially available for you to implement in your very own VoIP product.
Posted by Charlotte Oliver at 08:50 PM EDT
We've had a really busy week in the Junction Networks lab. We've started a testing program for some of the routers out on the market so that we can come up with some solid recommendations for routers that are known to work well with our network. (Alas, not all routers are created equally.) The main rule is that the router needs to not interfere with SIP. Specifically, we need routers that don't rewrite SIP packets, because we do a fair amount of work in learning about the network that a packet comes from in order to route and transfer calls properly.
Posted by Charlotte Oliver at 10:47 AM EDT
We've been testing the Polycom IP 560 and the IP 320. These are really great phones - they came through all of our testing with flying colors, which didn't surprise us very much, since Polycom makes some of the most reliable SIP phones on the market. The IP 320 is a great convenience phone and could certainly also work for most users, although the small screen makes it less ideal for heavy phone users. The functionality is all there, despite the smaller screen size. For a full feature set, see Polycom's spec sheet. While the IP 320 is a nice phone, the IP 560 is the phone that really stole our hearts. It's an attractive phone, with a backlit screen that makes a nice impression. It is also, interestingly, capable of high definition voice. We were skeptical at first, but when we tried the feature out, we were all very impressed with the sound quality.
Posted by Erick J Johnson at 06:56 PM EDT
Posted by OnSIP Employee at 04:58 PM EDT
Let's walk through my daily workflow, up to the point where I'm ready to commit back to my upstream SVN repository. Since I work on a fair number of branches and I don't always know what I worked on last, I run
git-status to see which branch I'm in, and any uncommitted work. This command shows my current branch, uncommitted files, and files in the index cache1. I like to keep my tree as fresh as possible, so I'll next run
git-svn rebase to update my tree with the latest from SVN. You can't run a rebase, however, if your working tree is dirty, so I'll clean up what I can using
git-add --patch2. Any code I can't fold into a commit, I put aside for a moment with
git-stash. When the rebase is completed, I'll put any stashed code back with
Posted by OnSIP Employee at 01:13 PM EDT
The other day, I made a mistake while committing some work I'd done via Git to our SVN repository. Since this series of articles is about working with Git and SVN, I wanted to take a short time to look over what happened as well as a small change in my workflow that will prevent it from happening in the future. The mistake was that I accidentally pushed a file I was working on to our main repository. There was no damage caused, as the file wasn't in use by anything in production yet, but I'd rather not have pushed it at all. The solution is to diff my work against the current repository and make sure only the changes I want or going to be pushed. But since Git doesn't work in a centralized fashion, you can't run a straight diff: you first have to know which revision to use as the left hand side. In Subversion, this is straight forward as it's centralized; the left hand side is the SVN repository HEAD, and the right hand side are your uncommitted changes.
Posted by OnSIP Employee at 01:59 PM EDT
Posted by Charlotte Oliver at 02:59 PM EDT
The potential of IP telephony is, of course, very cool. But one concern that the industry buzzes about is SPIT - SPam over Internet Telephony. As with every IP service, spam is a real concern, although SPIT hasn't taken over to the same level that e-mail and blog spam have. A SPIT spammer uses a VoIP system to make hundreds of unsolicited, pre-recorded phone calls. This seems like a telemarketer's dream, of course, but it has bigger concerns since it can easily be used for illegal activity, such as tricking the recipient into punching in a credit card number that can then be stored on the computer that placed the call. In my opinion, it is the use of VoIP for illegal activity that is the real concern. Although telemarketing is unpopular, it's a legal practice and VoIP doesn't give telemarketers the ability to do anything they aren't already doing - it just lowers the cost of doing business.
Posted by Charlotte Oliver at 02:28 PM EDT
To add to our growing list of phones that have gone through the Junction Networks lab, we've been testing the Grandstream GXP 2000 and the GXP 2020. These attractive phones offer a budget conscious buyer a solid entry point for VoIP hardware. Both phones have a nice corporate look to them. The user interface is simple and well-designed and the menu system on the phones is one of the better ones we've seen. One of the things we really liked about these phones is that the IP address is displayed on the LCD, so doing the initial configuration is even easier. These are good phones for someone whose primary job function is not the phone, but advanced users are likely to have some frustration with them. We ran into a few problems, which in the interest of full disclosure, we have to mention here. Initially our testing was stalled because calls did not seem to be hanging up properly. Test Phone A called Test Phone B.