tag:blogger.com,1999:blog-6740945304355297925Thu, 22 Mar 2012 09:17:14 +0000asteriskaastracentoscloudphonesQOSxorcomVLANcustomer servicevendorsnetworksiprhinohardwarehttp://blog.jkl5group.com/noreply@blogger.com (MichelV69)Blogger4125tag:blogger.com,1999:blog-6740945304355297925.post-4104852111936092512Thu, 16 Sep 2010 12:39:00 +00002010-09-16T08:44:11.739-04:00sipaastraasteriskAn amusing gotcha that's taken me two days to pin down... If you have an Aastra 53i up to firmware version 2.6.0.1008 connecting to an Asterisk 1.4.x box do _not_ use the "fromuser=" directive in the SIP.CONF file associated with that phone.  The phone won't accept calls from Asterisk any more, returning error code 400 "Bad Request". <--- SIP read from 192.168.2.192:5060 ---> SIP/2.0 400 Bad http://blog.jkl5group.com/2010/09/aastra-53i-showing-sip-400-bad-request.htmlnoreply@blogger.com (MichelV69)0tag:blogger.com,1999:blog-6740945304355297925.post-2098333873737666758Thu, 12 Aug 2010 15:51:00 +00002010-08-12T11:51:32.023-04:00xorcomnetworkcentoscustomer servicehardwarerhinovendorsIf the vendor doesn't fit, change him Fodder for another post is a nightmare I've had with Xorcom USA with one of my newest accounts.  If there was a way to blow the order and the VAR-partner relationship, including lying to the VAR, they've done it with this account.  No fun. Eventually, we were obligated to drop Xorcom for this project and get a different appliance vendor.  We opted for Rhino http://blog.jkl5group.com/2010/08/if-vendor-doesnt-fit-change-him-centos.htmlnoreply@blogger.com (MichelV69)2tag:blogger.com,1999:blog-6740945304355297925.post-5453498283708163513Thu, 05 Aug 2010 13:14:00 +00002010-08-05T09:23:17.959-04:00networkVLANcloudphonesQOShardwareasteriskA question I've seen a lot lately is about how much hardware at the network and in the rack you need to run an Asterisk VOIP environment for the enterprise.  The real answer is "not much". The Network Matters On the network side, you're looking for Quality of Service (QOS) and the ability to put your voice traffic on a Virtual LAN (VLAN) so that it is "invisible" to data traffic.  Of the two, http://blog.jkl5group.com/2010/08/how-much-hardware-do-you-need.htmlnoreply@blogger.com (MichelV69)0tag:blogger.com,1999:blog-6740945304355297925.post-3894090347725056201Wed, 28 Jul 2010 12:28:00 +00002010-07-28T08:36:02.547-04:00The whole "hedgehog concept" has pushed me to setting up the JKL5 Blog over here at Blogger.com. We'd had one that we were running on our own servers using Typo but maintaining and managing it is just another "thing to do" that isn't our core business.Thanks for following us and we're looking forward to sharing some of ideas and thoughts about the Free Open Source Software (FOSS) Voice Over IP (http://blog.jkl5group.com/2010/07/getting-started.htmlnoreply@blogger.com (MichelV69)0