Asterisk
Local company Far South launches revolutionary Asterisk product
Far South Networks, a local development house based in Cape Town, has launched an interesting interface product for Asterisk.

The rack-mount ‘gateway’ is a telco interface adapter for Asterisk based PBX solutions available in various configurations including analog, BRI and PRI. It is similar to the Xorcom range of channel banks with the main differece being that the Far South iTA connects to the LAN rather than via USB and it also includes hardware echo cancellation, a definate requirement for SA analog lines!
Will be interesting to see how the product does in the Asterisk space against other interface options such as Digium and Sangoma. Apparently some further products are due to be launched by Far South Networks in the coming months… stay tuned!
The official release below:
Local VoIP hardware distributor, Even Flow Distribution, has announced a distribution partnership agreement with Far South Networks, a South African telecommunications development company. Together, the companies will be releasing a range of homegrown telephony products which compete effectively against international offerings in this space.
Far South Networks is a South African electronics design and development house, which provides network access and telephony solutions within the telecommunications sector. These solutions range from voice telephony, data and Voice over IP (VoIP) networks to consumer electronics devices.
“With over 40 years experience in the industry, Far South, is bringing to market a product range that will be well supported due to the real value that the products offer, and the benefits of local support and regionalised product development,” says Adrian Bush, managing director of Even Flow.
The first product announced is the Far South Comma iTA, a line interface adapter targeted at open source Asterisk telephony market. The versatile product is available in various configurations including analogue and digital interfaces, incorporates hardware echo cancellation on all ports and is ICASA approved.
“As a telecommunications equipment vendor, it is crucial that Far South Networks take our product line to market through established distribution networks. It is for this reason that we have partnered with Even Flow, who has established itself as a reliable and consistent distributor of telephony products in South Africa, contributing a significant value-add through service and technical support,” says Grant Broomhall, co-founder of Far South Networks.
“Our existing product line contributes significant new technologies in the open telephony space, enabling telephony service providers to differentiate themselves in local and international markets” he adds.
A range of converged telecommunication products that are likely to shake up the local telecommunications industry will soon be available through Even Flow as part of the agreement.
“Far South Networks is at the forefront of telephony solutions in South Africa and, with products built to unique SA specifications, we anticipate that they will garner considerable interest from local businesses while still holding global appeal,” says Bush.
About Far South Networks
Founded in 2006 by electronic engineers, Grant Broomhall and Michael Walton, Far South boasts a total of 40 years of award winning experience in the industry. In March 2008, Far South Networks was awarded a technology grant from the Industrial Development Corporations’ Support Program for Industrial Innovation (SPII) for the development of their telephony product range.
Astricon 2009 Updates: AsteriskExchange, AsteriskForge, Asterisk.org
![]()
The Astericon conference took place last week in the US with some interesting announcements from Digium. Digium announced the AsteriskExchange application store, an overhauled Asterisk.org community site and AsteriskForge for software developers. The three new offerings help formalise and unify the Asterisk community and confirms Asterisk as a disruptive force in the IP PBX market.
Over the past year, Digium has gradually grown its channel partner program worldwide. But for some VARs and customers, it’s often difficult to find Asterisk-compatible applications, hardware and related services. Digium is aiming to address that challenge with three key moves:
1. AsteriskExchange: A forthcoming app store of sorts, which will apparently allow partners and customers to more easily find Asterisk-compatible applications and services.
2. AsteriskForge: A central location for developers to share and track new Asterisk-related software components and projects.
3. Asterisk.org: Digium overhauled the community site with new content and new points of access to help partners, customers and developers more easily find key information about Asterisk.
Below is a clip of Mark Spencer thoughts of each of these new offerings
Asterisk tip: P2P SIP URI Dialing

There are thousands of people that operate their own Asterisk based PBX systems, yet they do not enable any method to allow for p2p sip URI dialing. These sip “targets” are very easy to enable and allow you to dial anyone that has also enabled the function. Dialing with SIP URI completely avoids toll calling and forces your Asterisk server to create P2P sip connections when you dial someone’s SIP URI. It makes a less complex phone call without a system administrator configuring a peer and best of all: It gets rid of phone numbers and your telco!
How does it work?
By creating a SRV record in DNS for your domain you can help remote PBX systems establish P2P calls for a specific extensions. For example, when someone calls me, my URI is resolved to my PBX (sip.blyon.com). When the call comes into my Asterisk box, blyon is setup as a extension, and that extension is connected to a phone or a context. As a result, if someone uses something like Xten to call blyon@blyon.com, I get a normal ring and phone call. When I use my Cisco 7960 phone and dial someone’s SIP URI it completes like a normal phone call.
Why is this cool?
This is great because it takes away any central control for locating people. The ENUM standard is nice, but gives someone else control over the mapping database and it keeps an ugly old phone numbers in place. I really don’t want to dial phone numbers 10 years from now, I much rather just give someone my email address and have that map to my phone. If I need to call a business, I much rather just call pbx@somecompany.com then find some obscure phone number.
If more people adopt this as a standard, it will be the method of choice for calling people and it puts power into the end user’s hands!
Configuring the DNS SRV Record
Much like an MX record that defines mail servers for a domain, you can use an SRV record to define your PBX server for a domain. My domain blyon.com has a PBX and I simply created the SRV record for it:
In bind it would look something like this:
_iax._udp SRV 10 10 4569 iax2.blyon.com.
_sip._udp SRV 10 10 5060 sip.blyon.com.
SIP and IAX2 are also host names that point to my PBX. When someone dials my URI extension@blyon.com, their client or PBX will do a DNS lookup and see that sip is available on port 5060 at sip.blyon.com.
IAX records are not needed to make SIP URI dialing work. It is listed here to show that you can use other protocols like IAX.
Create a whitepage TXT record
To make it easy on others to locate your public extensions you should also create a protocol whitepage listing. I suggesst you map your user’s email addresses to extensions. If you do enable extensions to email addresses, you will want to include “email_addr” in your TXT record. A sample in bind looks like this:
sip.whitepage TXT “email_addr, home, echo, pbx”
“sip.whitepage” is the SIP protocol whitepages txt record, the first “email_addr” tells people that email addresses are mapped to extensions, and other non-email address extensions are listed. You should list each extension seperated by a comma.
This TXT record is not a standard RFC, it’s something I thought would be helpful for people to establish SIP communications. This is not needed to make the system work.
Configuring Asterisk to accept inbound URI calls:
Under [general] in sip.conf make sure the following is allowed:
[general]
context=in ; Context for incoming calls
allowguest=yes ; Allow or reject guest calls (default is yes, this can also be set to ‘osp’
bindport=5060 ; UDP Port to bind to (SIP standard port is 5060)
srvlookup=yes ; Enable DNS SRV lookups on outbound calls
My specific context is “in” that’s where these calls go in the extensions.conf, this is the same place that I send inbound calls from a telco or another sip peer. Under your version of the “in” context just define your username mapping:
exten => blyon,1,Macro(doDialExten,${BARRETT-VM},${BARRETT-HOME})
I have BARRETT-VM and BARRETT-HOME setup so that it rings my home office and then sends the caller to voicemail if I don’t answer. So rather than putting my extension there, I just define my username that will be picked apart by Asterisk and matched.
Configuring Asterisk to accept outbound URI calls:
When you define a sip proxy for things like a Cisco 7960 or Xten, they forward all URI calls to the proxy. Asterisk does not have any idea what to do with them so they usually 404 error and as a result you can’t make your free calls to your buddy that also set this up and operates Asterisk. There is a simple fix however, in your dial plan after you have defined your local extensions and usernames, and after your _1XXX… toll definitions simply add this uri context or the exten directly into your dialplan:
[uri]
exten => _[a-z].,1,Macro(uridial,${EXTEN}@${SIPDOMAIN})
exten => _[A-Z].,1,Macro(uridial,${EXTEN}@${SIPDOMAIN})
exten => _X.,1,Macro(uridial,${EXTEN}@${SIPDOMAIN})
Next make sure you add the macro into the extensions.conf in the area where you have your other macros defined:
[macro-uridial]
exten => s,1,NoOp(Calling remote SIP peer ${ARG1})
exten => s,n,Dial(SIP/${ARG1},120,tr)
exten => s,n,Congestion()
After local extensions are not matched and toll extensions are not matched it will then take the call and make a SIP connection and away you go! Asterisk splits everything past the “@” in the call and makes an ${EXTEN} variable and a ${SIPDOMAIN} variable. If we match an lowercase alpha character in the ${EXTEN} then we simply just dial the EXTEN@SIPDOMAIN and away you go!
Dialing with a free “Soft Phone”
Any “soft phone” that can dial sip numbers including Micscrewsoft NetMeeting can now be used to make free inbound calls to your Asterisk box. If you setup an extension called pbx that goes to your main phone tree, and someone calls pbx@yourdomain.com, they would get your main tree just as if they called via a toll system. You can also do SIP calls without any fancy DNS by specifying the full hostname to the Asterisk/PBX:
sip:exten@hostname.of.asterisk.server.com
This requires you to know the exact IP or hostname of the Asterisk PBX, rather it would be more simple to have the one time DNS record and then you can give your extension@hostname.com.
Dialing the URI with DNS is simply:
pbx@blyon.com, blyon@blyon.com, or foo@bar given there are functioning SRV records.
Use Xten without any provider or special settings to call a SIP URI
If you would like to directly dial to another URI without setting up a SIP proxy, X-Lite allows for this option. To configure the direct dialing just go to System Settings -> SIP Proxy menu:
Enabled: Choose “Yes”
Display Name: Your calling name, maybe Joe Daly’s PC
Domain/Realm: Just put your ISP or local domain
Direct Dial IP: choose “Yes”
To make a call, simply specify the URI and away you go!
This works great for dialing out, I have not spent any time to figure out how to accept P2P URI calls just via a raw softphone client, but I am sure they support it. If you know how to do this email me and I will add it to this doc.
SIP URI and Vonage
When I was a vonage user people could dial me by calling: sip:{Vonage_Phone Number 10 digits}@sip.vonage.net. This is a SIP URI but it would be much more clean if they had created SRV records for vonage.com.
Dialing URI with an ATA
This is doable but a little more complex, but for a free call, who cares? The ‘@’ is dialed as “**”, and ‘.’ and ‘:’ are dialed as a ‘*’. If you were to dial 10000000000@sip.vonage.net, it would be dialed like this: 10000000000**12*144*47*38
To keep it easy we have replaced the hostname of sip.vonage.com with the IP address 12.144.47.38 (12*144*74*38). This really sucks having to dial using an IP address, so you may want to setup an exten for old phones that don’t support URI. Someone may also be kind and give us some clue on how to dial alpha with a standard phone, I am sure you can do it somehow.
To setup an exten for the URI to make it simple (if you are using Asterisk):
; Bob
exten => 1100,1,DIAL(SIP/bob@foo.com,120,tr);
Test it!!!
I have setup an echo test so you can just call into the system and see how it goes, just dial: echo@blyon.com
You can also test your SRV and TXT records by running the dig command:
# dig _sip._udp.blyon.com SRV
;; ANSWER SECTION:
_sip._udp.blyon.com. 1200 IN SRV 10 10 5060 sip.blyon.com.
# dig sip.whitepage.blyon.com TXT
;; ANSWER SECTION:
sip.whitepage.blyon.com. 408 IN TXT “email_addr, home, echo, pbx”
You can also use my test form to see if your domain or others are configured for SIP URI.
Source: blyon.com
Setting up FNB Connect with Asterisk
As strange as it may seem for a bank to be offering a VoIP service, it is all the more strange that they seem to be doing it well! FNB Connect seems to be getting fairly possitive reviews and feedback in the press regarding the quality of service. So, for those FNB customers that want to now take it to the next level and hook up their office Asterisk PBX to an FNB Connect account then you may find the below interesting. The good news is that the FNB client uses IAX (not SIP) with an endpoint of voice.fnbconnect.co.za, making it very easy to incorporate with Asterisk.
The below is a setup documented by Durban technology group Thusa
iax.conf
register => 087
[fnb]
type=peer
host=voice.fnbconnect.co.za
username=087
secret=
[087
type=user
host=dynamic
Now to route some calls out of there
extensions.conf
[local]
exten => 087
[default]
exten => s,1,DIAL(SIP/
[outbound]
exten => _X.,1,DIAL(IAX2/fnb/${EXTEN})
FNB’s calls come in as “s@default” so you need a ‘default’ context to route incoming calls to your local call group or extension.
After publishing this information someone at FNB also pointed out that their cluster supports G729 and trunking. Switching to G729 where available should greatly improve voice quality.
Skype for Asterisk

Asterisk recently launched the add-on Skype channel driver for Asterisk based PBX systems, allowing complete access to the Skype network, including low cost PSTN access and free calling to over 440+ million Skype users. The Skype for Asterisk single channel sells for $66 (approx R560) on the Digium website.
Key features include:
• Make Skype to Skype calls
• Calls to landlines and mobile phones
• Receive calls with SkypeIn
• Make world-wide PSTN calls with SkypeOut
• Make and receive multiple concurrent Skype calls from the same Skype account
• DTMF support for incoming and outgoing calls
• Read Skype profile fields from incoming calls
• Set and retrieve online status
• Set privacy settings
• Handle incoming Skype calls using all Asterisk applications (voicemail, ACD, MeetMe conferencing, etc.)
• Simultaneous access from both Asterisk and the Skype desktop client
• Use Asterisk phone for voice and Skype desktop client for IM, video
• Trunk calls between Asterisk servers over Skype
• Supports G.711 and G.729 (included) codecs
Recent Posts
Categories
Email Updates
Archives
Recent Comments
- The new snom M9 review, some nice new upgrades and feature additions http://www.voipblog.co.za/2009/11/the-new-snom-m9-cordless-ip-phone/
- Cheeky move by SA's biggest operators... the interconnect rate debate continues http://tinyurl.com/yjtxfem
- Astricon 2009 announcements and interview with Mark Spencer, CTO Digium http://tinyurl.com/yfqmj5w
- snom now supports TR-069 standard for remote VoIP device management http://tinyurl.com/ygu2g7x
- ICASA: Empty promises or a step in the right direction? http://tinyurl.com/nqnja2