Jump to content

This is the support site for Andrews & Arnold Ltd, a UK Internet provider. Information on these pages is generally for our customers but may be useful to others, enjoy!

FireBrick SIP Configuration: Difference between revisions

← Older edit
Content deleted Content added
Reedy (talk | contribs)
editor
706 edits
Reedy (talk | contribs)
editor
706 edits
Update deprecated tags
 
(3 intermediate revisions by 2 users not shown)
Line 2: Line 2:


=Overview=
=Overview=
[[File:Pbvoipicon.png]]
⚫
[[File:Pbvoipicon.png]]Also see: [http://www.firebrick.co.uk/fb2700/voip.php FireBrick VoIP Page] which has more details about the feature, as well as the [http://www.firebrick.co.uk/manuals.php?PRODUCT=2700 FireBrick Manuals] which contain a VoIP section.

⚫
Also see: [https://www.firebrick.co.uk/support/knowledge-base/voip/ FireBrick VoIP Page] which has more details about the feature, as well as the [https://www.firebrick.co.uk/support/manuals/0 FireBrick Manuals] which contain a VoIP section.


The FireBrick can be used for VoIP by being a VoIP gateway (FBSIP). Your local (or remote) SIP devices register against the FireBrick, and the FireBrick registers to your SIP provider, in a sense the Firebrick acts as a back-to-back SIP gateway.
The FireBrick can be used for VoIP by being a VoIP gateway (FBSIP). Your local (or remote) SIP devices register against the FireBrick, and the FireBrick registers to your SIP provider, in a sense the Firebrick acts as a back-to-back SIP gateway.
Line 14: Line 16:
==SIP and NAT==
==SIP and NAT==
First, a few comments about SIP, NAT and the FireBrick...
First, a few comments about SIP, NAT and the FireBrick...

The FireBrick maps ports and IPs for NAT but provides no ALG for SIP or any other protocol. SIP is notoriously difficult with any sort of NAT, with or without ALGs. AAISP will be happy to route a block of IP addresses for use with VoIP phones, and the FireBrick can be configured to use these, and even allocate phones from the same manufacturer the correct IP by DHCP.
The FireBrick maps ports and IPs for NAT but provides no ALG for SIP or any other protocol. SIP is notoriously difficult with any sort of NAT, with or without ALGs. AAISP will be happy to route a block of IP addresses for use with VoIP phones, and the FireBrick can be configured to use these, and even allocate phones from the same manufacturer the correct IP by DHCP.


Line 69: Line 72:
| extn
| extn
| 100
| 100
| Internal extension number where incoming calls are routed to (e.g. a user or a group)
| Internal extension number '''where incoming calls are routed to (e.g. a user or a group)'''
|-
|-
| allow
| allow
Line 82: Line 85:


xml:
xml:
<source lang=xml>
<syntaxhighlight lang=xml>
<carrier name="AAISP" display-name="Main" allow="81.187.30.110-119" registrar="voiceless.aa.net.uk"username="01234567890" password="secret" extn="100" comment="Main Office Number"/>
<carrier name="AAISP" display-name="Main" allow="81.187.30.110-119" registrar="voiceless.aa.net.uk"username="01234567890" password="secret" extn="100" comment="Main Office Number"/>
</syntaxhighlight>
</source>


If you go to Status - VoIP, you should see the Carrier listed with an expiry - this shows that the FireBrick is registered to the server.
If you go to Status - VoIP, you should see the Carrier listed with an expiry - this shows that the FireBrick is registered to the server.
Line 143: Line 146:


xml:
xml:
<source lang=xml>
<syntaxhighlight lang=xml>
<telephone name="John" display-name="John" username="john" password="secret" allow="192.168.1.0/24" ddi="+441234567890" extn="101" carrier="AAISP" max-calls="1"/>
<telephone name="John" display-name="John" username="john" password="secret" allow="192.168.1.0/24" ddi="+441234567890" extn="101" carrier="AAISP" max-calls="1"/>
</syntaxhighlight>
</source>


You can repeat this process for your other users, changing the extn each time, e.g. 102, 103 etc.
You can repeat this process for your other users, changing the extn each time, e.g. 102, 103 etc.
Line 188: Line 191:


xml:
xml:
<source lang=xml>
<syntaxhighlight lang=xml>
<group name="Main" display-name="Main" extn="100" ddi="+441234567890" ring="101 102 103" type="all"/>
<group name="Main" display-name="Main" extn="100" ddi="+441234567890" ring="101 102 103" type="all"/>
</syntaxhighlight>
</xml>


==Firewall==
==Firewall==
You will need to open the firewall if you are actually fire-walling traffic to the FireBrick - often people just firewall traffic to the LAN, and therefore all traffic to the FireBrick is allowed.
You will need to open the firewall if you are actually fire-walling traffic to the FireBrick - often people just firewall traffic to the LAN, and therefore all traffic to the FireBrick is allowed.


SIP and RTP traffic will need to be allowed in to the FireBrick. This will need to be from the carrier, but also from external SIP phones if you have any.
SIP and RTP traffic will need to be allowed into the FireBrick. This will need to be from the carrier, but also from external SIP phones if you have any.
Take a look at this wiki page for more info: [[FireBrick_2700#VoIP_Rules FireBrick_2700#VoIP Rules|FireBrick and VoIP Firewall]]
Take a look at this wiki page for more info: [[FireBrick_2700#VoIP_Rules FireBrick_2700#VoIP Rules|FireBrick and VoIP Firewall]]


Retrieved from "http://support.aa.net.uk/FireBrick_SIP_Configuration"