SIP URI Dialling – Setting up Inbound SIP calling to a Domain Name or IP Address


In layman’s terms, “SIP URI Dialling” is the ability to dial a SIP address without having to call a telephone number; instead you’d call a resource that has the same format as an email address. It is possible to assign both SIP and Email resources to the same email address for further simplicity for your callers.

This post explains how to implement SIP URI dialling on your own domain name. A domain name is not strictly required, an IP address is sufficient.

What this post doesn’t cover:

  • PBX/IPBX implementation.
  • Outbound calling.
  • Anything that’s vendor-specific.


This post is based on the understanding that you already have a Session Border Controller or other Edge Device in place, together with an external (public) IP address which is both static and not shared with any other resource.

What’s required?

In addition to the above, you should have:

  • A domain name.
  • Access to and/or the ability to add information to the same domain’s  Domain Name System (DNS) Zone record.

Used in this example:

The following examples are used to explain how to implement SIP URI:

  • ‘’, as a domain name.
  • ‘sip’ as a sub-domain.
  • ‘’, as an external (public) IP address.

You can setup SIP URI on your main domain name. In this example, I’ve used the sub-domain ‘’.

 DNS Record Setup:

 In the following:

  • ‘A’ Record means an “Address Record”.
  • ‘SRV’ means a “Service Record”.

 Add the following to domains DNS:

  • An ‘A’ Record which points to the external (public) IP address of the Session Border .Controller or other Edge Device:
    • A’  of ‘sip’ in ‘’. This states that ‘’ resolves to
  • An ‘SRV’ record which states the service, protocol, priority and weight. If you are using SIP. URI to a single SBC/ED, the following will suffice:
    • SRV’ syntax: ‘_sip._udp 0 5 5060’ – “The Service SIP uses UDP with a priority of 0 and a weight of 5 to port 5060 at
    • ‘SRV’ syntax: ‘_sip._tcp 0 5 5060’ – “The Service SIP uses TCP with a priority of and a weight of 5 to port 5060 at
DNS Zone Config – Example:
SIP URI Dialling – Example:
To dial a SIP URI fom a SIP client such as Bria, use “sip:” followed by the SIP URI:

Related RFC’s:

WordPress: Enabling Two Factor Authentication Login (2FA)

Enabling Two Factor Authentication on your WordPress site gives an extra layer of security to a simple password-only login.

The items used for this are:

Installation Process:

Login to your WordPress site

Go to Plugins | Add New

Search for and install Two Factor Authentication

Activate Plugin

Setup Process:

  • Click User Settings
  • Activate Two Factor Authentication, by selecting Enabled, then hit Save Changes
  • Scan the QR Code
  • Under Advanced Settings, select TOTP (time based) algorithm
  • Hit Save Changes

Checking That This Works:

Once you log out of WordPress, 2FA will become active. You should make sure that the time on your Google Authenticator app is the same as this plugin.

To do this, press update next to Current one-time password and make sure that both numbers match. Note: The first time you do this, both numbers may not match – you may have to wait up to one minute for both to synchronize.


How to disable this feature if Two Factor Authentication fails

If your pass-code used to work, but no longer does, then check that the time on your device that generates them is accurate.

If you cannot get in and need to disable two-factor authentication, then add this to your wp-config.php file, using FTP or the file manager in your hosting control panel:

define(‘TWO_FACTOR_DISABLE’, true);

Add it next to where any other line beginning with “define” is.

Cisco: Config Registry Settings

0x102 – Ignores break – 9600 console baud rate

0x1202 – 1200 baud rate

0x2101 – Boots into bootstrap. Ignores break. Boots into ROM if initial boot fails – 9600 console baud rate

0x2102 – Ignores break – Boots into ROM if initial boot fails – 9600 console baud rate. Default value for most plaforms

0x2120 – Boots into ROMmon – 19200 console speed

0x2122 – Ignores break – Boots into ROM if initial boot fails – 19200 console baud rate

0x2124 – NetBoot. Ingores break. Boots into ROM if initial boot fails – 19200 console speed

0x2142 – Ignores break. Boots into ROM if initial boot fails – 9600 baud rate. Ignores configuration (NVRAM)

0x2902 – Ignores break. Boots into ROM if inital boot fails – 4800 console baud rate

0x2922 – Ignores break. Boots into ROM if initial boot fails – 38400 console baud rate

0x3122 – Ignores break. Boots into ROM if initial boot fails – 57600 console baud rate

0x3902 – Ignores break. Boots into ROM if initial boot fails – 2400 console baud rate

0x3922 – Ignores break. Boots into ROM if initial boot fails – 115200 console baud rate

Polycom SoundStation IP 5000: Setting to UK Dialplan

The default dialplan on a Plycom SoundStation IP 5000 is set for the USA:

If used in the UK, a unit may act as if it’s broken. Dialplan should be changed as follows to work in the UK:

Web interface username/password:
Username: Polycom
Password: 456

Wonga: Unfair and Misleading Debt Collection Practices

From this FCA Press Release

Wonga, the UK’s biggest payday lender, has entered an agreement with the Financial Conduct Authority (FCA) which will see it pay compensation of over £2.6m to around 45,000 customers for unfair and misleading debt collection practices.

In an investigation begun by the Office of Fair Trading (OFT) and taken forward by the FCA, Wonga was found to have sent letters to customers in arrears from non-existent law firms, threatening legal action.


During this time, Wonga sent communications to customers in arrears under the names “Chainey, D’Amato & Shannon” and “Barker and Lowe Legal Recoveries”, leading customers to believe that their outstanding debt had been passed to a law firm, or other third party. Further legal action was threatened if the debt was not repaid.