Updates (Sticky)

December 27 2008

I tried upgrading to the latest GUI:

ipkg remove asterisk14-gui
ipkg install asterisk-gui

but had some problems with the CDR reader. While the
interface seems a little nicer, i would stay with
asterisk14-gui for now.

August 27 2008

I reinstalled asterisk on the slug today using
my instructions. It all seemed to work OK!

I did make a couple of minor changes: I added some
code under the Platform step to automatically start
asterisk on reboot; I also updated the version numbers
of the asterisk software for the ipkg install step.

FWD is no linger free. It can still be used
as an example of SIP trunking.

May 13 2008

I added a bit of an explanation to Step 3 on how
to allow all calls to go out. The original dialplan
blocks long distance calls by default (other than
to toll free numbers).

Friday, December 28, 2007

Sixth Step (Inbound SIP Trunks)

If we want to receive calls from FWD we have to make a few modifications to sip.conf. If you've already added your externhost and localnet information in sip.conf half the battle is won. If you have an opportunity to call a SIP phone outside your local network, you will see that Caller ID information was detected by the receiving station. That call can actually be returned by simply redialing the number that was detected i.e. 6003@your.local.net.

However, in order for a foreign station to call your local station without any knowledge of your network you must configure the SIP equivalent of a traditional PSTN trunk.

Step 1

Many instructions on the Internet have you adding a register entry in sip.conf to allow incoming calls. However, using the GUI in version 1.4 this is done in users.conf (registersip). We did this when we first set up our SIP trunk in Step 5 so there is no need to modify the
register =>
line in sip.conf.

Step 2

We must make a context to handle incoming calls. If you recall from step 5 in the previous post there was an entry added to extensions.conf
[DID_trunk_1]
Let's complete the entry by launching the GUI and navigating to Incoming Calls.

Click on Add an Incoming Rule and fill in the following fields:

Route: All unmathed incoming calls
from Provider: Custom FWD_SIP
to exentions: whatever_local_extension_you_want

Click Save and Activate Changes

extensions.conf will have the following entry added:


[DID_trunk_1]
include = default
exten = _X.,1,Goto(default|6003|1)
exten = s,1,Goto(default|6003|1)

I chose extension 6003 to receive my FWD calls.

Step 3

The final step is to edit sip.conf. Look for the
[sip_proxy]
entry and edit the following lines:


[sip_proxy]
; For incoming calls only. Example: FWD (Free World Dialup)
; We match on IP address of the proxy for incoming calls
; since we can not match on username (caller id)
type=peer
context=DID_trunk_1
host=fwd.pulver.com

If you use the Call Me feature of FWD you can check to see if the extension you assigned rings.

Note: I'm a little confused why I couldn't designate trunk_1 in users.conf to accept incoming calls. Perhaps a kind reader would leave a comment about that! It seems that if I can configure outgoing calls in users.conf, I should be able to receive these calls without having to edit sip_proxy.

1 comment:

Atlanta Contract Staffing said...

Highly еnergetic blog, I enjоyed that a lot.