SIP Trunk Settings for Trixbox (FreePBX / Asterisk) for iEtherSpeak

Mindwatering Incorporated

Author: Tripp W Black

Created: 06/30/2010 at 11:08 PM

 

Category:
VOIP
Asterisk

Sample Settings for Asterisk with iEtherSpeak (ZIPTrunk) that worked for us:
Note: Mindwatering does not endorse EtherSpeak. This information is provided for sample configuration only.

To get our trunk open, we:
1. Made a "hole" in the firewall to their IP address and opened up ports UDP 2050 & 2051 as a forward to our Trixbox/Asterisk server's internal IP. You also need a whole bunch out (which were open anyway from internal).
2. Created a SIP Trunk and Route Out and a Route In.
3. Updated the sip_nat.conf which seemed to be necessary to get the outgoing half of the trunk working.

sip_nat.config File Additions:
PBX --> Config File Editor --> sip_nat.conf
nat=yes
externip=192.168.2.195
localnet=192.168.2.0/255.255.255.0


SIP Trunk Settings:
PBX --> PGX Settings --> Trunks --> Add Trunk --> select SIP

General Settings:
Caller ID: "Mindwatering" 9195563691

Maximum Channels: 5

Outgoing Dial Rules
1919+NXXXXXX
1+NXXXXXXXXX
(iEtherSpeak requires full number including 1, but doesn't seem to require the + in front of it.)

Outgoing Settings:
Trunk Name: MWES1Out
(This just needs to be unique. This is our example.)

Peer Details:
type=peer
host=74.84.203.90
context=from-trunk
reinvite=yes
qualify=no
insecure=very
nat=yes

Incoming Settings:
USER Context: 24.25.26.27 (Our External IP)

USER Details:
type=peer&user
host=74.84.203.90
qualify=no
insecure=very
context=from-sipexternal
nat=yes
reinvite=yes

__________________________

Notes:
What got us were messages. We kept getting "circuits not available" and "invalid number" messages. We ended up doing a console into the server and looking at the SIP log messages while in debug and placing calls from both directions. How to get started. (Hint: type help sip in the CLI for a list of commands.)
# asterisk -r
CLI> sip set debug on
...
CLI> sip set debug off
CLI> exit
# exit

Also, the bulk of our issue was actually a dialing pattern out. So start with a good dial out rules to add the 1 necessary in this case. That way you are only testing the trunk and not going down a very lengthy hole troubleshooting trunk settings needlessly.

previous page

×