Derek Murawsky derekmurawsky

How to setup Grandstream DP750 for Unifi Talk

I've seen several posts on Reddit and other forums that say "oh you can use a grandstream phone with UniFi Talk and it's flawless". Unfortunately, I am not a VoIP engineer so it was not intuitive to me, but I got it to work. Here's how.

For this writeup, I'm using a Grandstream DP750 DECT base with a DP720 DECT wireless handset. I really wanted a wireless phone for general use in my house, but Ubiquiti doesn't make one, so I wanted to find a way. My goal is to setup UniFi Talk for my home phone solution and share a single phone number with a UniFi wired phone that sits on my office desk. As far as I know, you have to get a UniFi phone to do the initial Talk setup (though, in my tinkering, I noticed it's using a PostgreSQL database, you could probably bypass the initial setup if you knew what you were doing). I'm also using a UDM-Pro for my gateway.

Assuming your UDM-Pro management interface is on 192.168.1.1, your base station should be assigned an IP on a VL

Create service and add dependencies

serverless create --template hello-world
npm init
npm install dd-trace@dev
npm install serverless-plugin-datadog

Install Lambda Forwarder

.gitkeep

A .gitkeep file tells github to do the opposite of its default behaviour, which is to ignore empty folders.

If you want to track an empty folder, or a folder with untracked files, create a 0kb file with the .gitkeep file extension in that folder.

touch FOLDER_NAME/.gitkeep

From time to time, Musk will send out an e-mail to the entire company to enforce a new policy or let them know about something that's bothering him. One of the more famous e-mails arrived in May 2010 with the subject line: Acronyms Seriously Suck:

There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don't want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees.

That needs to stop immediately or I will take drastic action - I have given enough warning over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary.

An Ansible summary

Jon Warbrick, July 2014, V3.2 (for Ansible 1.7)

Configuration file

intro_configuration.html

First one found from of

README

This is an example of a socket-activated per-connection service (which is usually referred to as inetd-like service). A thorough explanation can be found at http://0pointer.de/blog/projects/inetd.html.

Define a socket unit

The key point here is to specify Accept=yes, which will make the socket accept connections (behaving like inetd) and pass only the resulting connection socket to the service handler.

	dockerfile:
	policies:
	- name: warn_latest_tag
	enabled: true

	function _cdk_completer {
	STACK_CMDS="list synthesize bootstrap deploy destroy diff metadata init context docs doctor"

	if [ "$3" == "cdk" ]; then
	COMPREPLY=($(compgen -W "$STACK_CMDS" $2))
	elif [[ -d "cdk.out" ]] && ! [[ "$2" == "-"* ]]; then
	TEMPLATES=$(ls -1 cdk.out/*.template.json \| awk '{split($0,t,/\/\|\./); print t[3]}')
	COMPREPLY=($(compgen -W "$TEMPLATES" $2))
	else
	COMPREPLY=()

	#!/usr/bin/env ruby

	require 'snmp'
	#include SNMP
	require 'logger'
	require 'sensu-plugin/check/cli'

	# Usage: Import specific MIB modules into the snmp gem mib folder
	# - : Import specific MIB modules into the snmp gem mib folder
	# - : Performs some SNMP Checks

	=========================
	# /etc/nginx/nginx.conf
	=========================

	user www-data;
	worker_processes 4;
	pid /var/run/nginx.pid;

	events {
	worker_connections 768;