Yealink is our go to vendor for telephony hardware, mainly due to its ease and variety of configurability. But recently have been tasked with adding a Polycom VVX250 to the system for a charity to use.
While the setup between different manufacturers normally follows the same general path. This is a journey of how Polycom interprets it…
I’ve been a NordVPN customer for about 6 months now, mainly due to its ongoing support of L2TP connections. However recent changes to its service put my use of this service with my Draytek 2862 in jeopardy. Luckily there is a fix, and it’s a story of updates…
2021 is here and so returns (In the UK at least) one of my favourite shows to Netflix, The Office (US). Since starting working in VoIP its hard not to notice what phones turn up in TV shows, here the Cisco 7960, was prolific for showing up in shows around this era.
So why not, nearly 16 years after the show started, try and get one of these working on an Asterisk PBX? At work we had a number of similar 7940 models that hadn’t be used for years, so why not give it a try…
Here’s a quick one, ever thought of taking some existing phone extension wiring and converting for use in ethernet networking?
Since moving in I’ve had an analogue phone extension socket in the bedroom. The cable runs outside and down the side of the house, before returning into the house close to the BT master socket. It was connected, but was immediately removed to get the best internet speed at the master.
Unexpectedly and to much excitement, my home internet is now provided via FTTP.
For background, I was previously in a FTTC environment getting average speeds due to my distance from the cab, however good enough to assumably be overlooked for the next phase of the Openreach Ultrafast rollout. Not that I’m complaining, 2020 is the year my speed gets a much-needed boost.
2020 also turns out to be the inaugural international work from home year, so had the opportunity to have a front seat view from my home office on the activity and timeline that brought FTTP home.
I’d like to share my observations and timeline as an example of what you can expect should you get the inkling of fibre coming to your street soon.
Before we get started, as my expectations rose, I found this post by Andy’s World invaluable for identifying activity and helping me confirm that FTTP was on its way.
In a series of events that I thought wouldn’t have happened for many years, FTTP (Fibre To The Premises) has just become available to my home. With available speeds of 1000/330Mbps available the temptation is to go for the maximum, but will my current infrastructure actually deliver what’s on offer?
My current router is a Draytek 2862ac, which has an advertised 400Mbps throughput at the WAN, but what can it actually achieve in the real world? This will be the basis on choosing a FTTP speed profile.
Speed testing a router can be setup with a couple of laptops…
Hopefully the mad dash for home working is over, and now
everyone who can has settled in to a comfortable home setup with new knowledge
of what a VPN and remote desktops are all about.
I thought my established home setup was great, however I
didn’t envisage words like Teams and Zoom to become the buzzwords of companies
the world over.
This posed an issue for myself. Even though my 2017 Dell XPS
has a webcam ready to go, it spends its home office days docked with the lid
closed. When opening the 4K screen combined with the Full HD monitors, Windows
implementation of scaling rears is appalling head and just looks terrible.
Combined with the Dell’s decision to locate the webcam below the screen to give
maximum nostril-cam angle, its not something I like to use.
Buying a USB webcam didn’t seem worth it for what is
(hopefully at time of writing) a temporary solution.
So in comes another Pi project, this time using a spare Raspberry Pi Camera module connected to an aptly placed Pi, that can be used on a Windows machine for the software likes of Zoom, Skype and Teams…
I’ve had the opportunity to deploy and test a call centre PBX product to gauge
if its viable to offer as a product and how it will sit within our
Installing and poking around the GUI is all well and good but to really find out how a PBX behaves it needs some traffic, to find outs its performance in regards to resources but also to find out what a vendor’s interpretation of an advertised feature actually is.
To generate sample calls, instead of registering handsets/softphones and dialling manually it would be better to automate this, and SIPp is the perfect tool for this.
I like this time of year, a chance to reflect on the last 12 months and take stock of accomplishments and realise the achievements. And something I like to gauge a success on is the longevity of a solution, and a time-lapse comparison 6 months apart is seemingly my go to example.
To elaborate on this achievement, earlier this year was the setup of a homebrew CCTV solution using an array of Raspberry Pi’s with cameras, and a VM Cent OS server acting as a PVR host. A surplus Pi W Zero was pointed at the hills and used as a time-lapse experiment.
The real achievement is that since its conception in early June,
it has been stable enough to run in the background, capturing footage for such an
So here I present my latest time-lapse, a split screen video on the difference between a June day and a December day:
It’s been a while since I had my last automated time-lapse solution, and since the change of location and change of servers the setup has been lost in the ether.
Back then, it was achieved with an off the shelf IP Camera, a Windows Server share and a batch script. Now that the Linux / Raspberry Pi CCTV solution is up and running, I hope to re-instate the automated time lapse in a simpler way using MotionEye and Cent OS.