I kinda feel like a jerk for hi-jacking this call but it really was a lot of fun and I think (hope) everyone enjoyed it.  I’d like to thank Randy (Zeeek) for letting me share my experience setting up our new Asterisk box at work.

Download the call here, check out the post here.

Listen to the VUC every Friday at noon here and be sure to take part in IRC on FreeNode at #vuc.

I have received 6 calls over the past month from readers who are having difficulty provisioning their VoIP hardware (specifically Cisco endpoints) and in most cases was able to help get the devices registered – mind you it was quite a hassle over the phone.  The biggest problem is that for the non-geeks this can be a daunting task and many don’t care to spend the time.

The good news is that we have gathered a team of developers to write a totally web based app for provisioning your endpoints with ease.  To start we will support the devices that we actually have and can test.  Within the week we plan to support the following models :

• Grandstream GXP XXXX & Budgetone Models
• Cisco 79XX series
• Several Aastra models (53i, 9143i, 480i)
• Linksys SPA94X
• Sipura SPA2102 (AKA Linksys PAP2)
• Whatever else can be found or generously donated.

We began development on the frontend which has two modes – wizard (basic) and advanced.  We have also constructed working templates for many models listed above which is probably the most tedious task.  We will offer HTTP and TFTP provisioning totally free! as well as the option to download your entire endpoint configuration to place on your own network (if you so choose).

A word on security :

Any and all data you submit to this application will be passed through an extensive encryption / decryption process and stored in the database – thus no one but you will have access to the private information.  You will actually have the ability to set your own security salt and change it if you suspect foul play (which is very unlikely).  We may also buy a CA for that extra peace of mind.

We will be adding this functionality as a module at ENUMPlus so sign up to catch first glimpse.

Anyone looking to help either with a donation of hardware or Paypal is of course much appreciated.  The more devices we can get our hot little hands on – the more we will be able to support.

I have been busy integrating Asterisk into NimbleBilling – take a look see and let me know what you think!

I stumbled upon this module last night when trying to delimit access to an outbound route per extension. I added a colleague to my PBX who had purchased an account at voip.ms; problem was when he would dial out it would always display my Caller ID and use my trunk (which is bad if he dials international). I guess this is a frequently asked question so I created a video demonstrating the great power of this module – you will be surprised how easy creating permissive contexts can be This video will show you how to install the module and limit access to outbound routes / trunks per extension. The goal is to partition an Asterisk IP PBX in order to host multiple tenants on one system.

The following information is from this site.  Please check it out for download link and changelog / usage.

Possible Uses

• Restrict access to certain outbound routes or feature codes by a particular extension or group of extensions.
• Give particular extension(s) priority access to certain outbound routes, such as a particular emergency route associated with their geographic location.
• Give certain outbound routes top priority for use during “free” or low cost calling periods, while making those same routes lower priority (or disallowing access entirely) during higher cost time periods.
• Disallow access to outbound routes (with possible exception of Emergency access) to certain (or all) extensions during particular time periods (don’t let night cleaning crew make long distance calls, or disallow outgoing night calls from telephones in children’s rooms, while still allowing emergency number calls).
• Allow two or more families/companies/organizations to use the same FreePBX box, while still allowing each to have access only to “their” outgoing routes and trunks.
• If you have a SIP provider that does not send DID (normally a pain to handle because you can’t create a normal Inbound Route), set up a new custom context (call it idiot-provider), give them no access to anything (deny all), and then specify where you want their calls to go in the Failover Destination. Then put context=idiot-provider in that provider’s trunk user details.

Module Description

One feature which was a bit lacking in Asterisk/FreePBX was the ability to easily create multiple tenants.

This module creates custom contexts which can be used to allow limited access to dialplan applications.

Now allows for time restrictions on any dialplan access!

This can be very useful for multi-tenant systems.

Inbound routing can be done using DID or zap channel routing, this module allows for selective outbound routing.

House/public phones can be placed in a restricted context allowing them only internal calls.

Custom contexts can now be used as destinations. An IVR menu, Time Condition, etc. can now send a caller into a custom context. This feature requires FreePBX 2.2.0rc2 (or the latest SVN version if prior to the release of rc2)

(The following are the module author’s comments, “I” refers to the module author, not the original creator of this wiki page).

A number of improvements have been made to freePbx to handle multiple tenants.

1) inbound routing based on zap channel – i used to have to hack it by putting each zap channel in its own context.

2) authtype = database allows for dividing extension ranges

the main problem for me was outbound routing…

I wanted some extensions to dial out one route, and others out another route.

I had to create a custom context for each, then place each in their own custom context, then include all of the contexts which they should have access to. This became a nuisance as each module added its own context to from-internal-additional which could not be included as it also contains outbound-allroutes.

The purpose of this module is to dynamically list all contexts included in any contexts you choose, and allow you to create custom contexts which can include any of these all without config editing.

Being woken up several times throughout the night from anonymous calls is not fun.  Here is a screencast (shot with my shiny new MacBook) that explains how to delimit these annoying calls while still being able to route incoming SIP calls from Gizmo and IPKall to their appropriate destinations.

Here is the code I used to allow IPKall incoming SIP connections :


[ipkall]
disallow=all
host=66.54.140.46
context=from-trunk
insecure=port,invite
qualify=yes
type=peer
dtmfmode=rfc2833
allow=ulaw
nat=no

[ipkall2]
disallow=all
host=66.54.140.47
context=from-trunk
insecure=port,invite
qualify=yes
type=peer
dtmfmode=rfc2833
allow=ulaw
nat=no