Difference between revisions of "FireBrick VoIP"

From AAISP Support Site
Jump to: navigation, search
[unchecked revision][unchecked revision]
(Configuring Specific Carriers: rm redlink)
(Configuring Phones to Register Against your FireBrick: Remove disabled extension usage)
 
Line 36: Line 36:
 
*[[VoIP Phones - Generic Client|Generic Client Configuration]]
 
*[[VoIP Phones - Generic Client|Generic Client Configuration]]
 
*[[:Category:VoIP Phones|VoIP Phone category]]
 
*[[:Category:VoIP Phones|VoIP Phone category]]
 
Specific Phones:
 
 
<ncl style=bullet  maxdepth=5 headings=bullet headstart=2 showcats=1 showarts=1>Category:VoIP Phones</ncl>
 
 
 
 
  
 
[[Category:FireBrick VoIP]]
 
[[Category:FireBrick VoIP]]

Latest revision as of 19:19, 26 February 2017

2700-small.png

Other Pages

These pages are also related to this topic:

AAISP VoIP Service

These pages are useful to owners of FireBrick 2500 and 2700 models, but the FireBrick SIP platform is also used by the AAISP VoIP service, so these pages are also relevant to customers using the AAISP VoIP service.

Overview

The FireBrick has SIP capabilities and can be set up as a basic back-to-back SIP endpoint for a home office and provide a set of PBX features itself, or can be combined additional RADIUS and custom companion software to create a much more powerful SIP switch that can be used by larger VoIP providers. It is designed to scale well by simply adding more boxes. When used as back-to-back, you have individual 'User' Accounts on your FireBrick for each of your phones, and separately, you have Carrier accounts configured. These carrier accounts are the SIP accounts with your SIP provider, they is nothing special about these accounts, they are the same as if you are configuring your phone to register directly with the SIP provider, but instead the FireBrick registers. This back-to-back configuration is not a SIP ALG.

AAISP use FireBrick as their SIP Platform as a 'hosted' VoIP solution where by customers have phones which use the service and the features are provided by AAISP.

SIP is supported across the FireBrick range with the 2500 and 2700 models ideal for Office use and for small VoIP providers, and the 6000 models being used by larger VoIP Providers.

FBVoIPDia.png

Configuring the FireBrick for SIP

Pbvoipicon.png

Carrier and Users are separate - Your the phones uses the 'VoIP users' configuration section, and the Carrier configuration is in the 'VoIP carriers' section of the FireBrick config. -The FireBrick doesn't pass on authentication on your phone over to your carrier. You'll need a configuration entry for each of your carriers and each of your phones. At a basic level you can just have a 1-to-1 mapping of carrier to phone, or you can use the FireBrick PBX features for a more comprehensive setup where the FireBrick is able to offer features such as ring groups, call pickup etc.

Please also see:

This page describes how to configure the FireBrick to work with SIP phones and Carriers. See below on how to then configure phones to register against your FireBrick.

Configuring Specific Carriers

Configuring Phones to Register Against your FireBrick

As AAISP use FireBrick as it's SIP platform the pages on this wiki for configuring phones to register with your FireBrick are relevant. Please see: