Asterisk ON pfSense2.0.1

marcelloc

I can help you on first package relase.

It's basically a XML file That install php files, create menus and install the asterisk files.

Isn't better start a topic on packages section instead of nat?

robi

A moderator please move the topic in the right place.

robi

I can help you on first package relase.

It's basically a XML file That install php files, create menus and install the asterisk files.

How to do that?

marcelloc

take a look on pfsense-packages at github.com

https://github.com/bsdperimeter/pfsense-packages

I'll create the xml file to install your php files.

blietaer

Sweeeet!
I think you have achieved more stability that I coul din my original hack/post, cheers!
Maybe 2.0.1 helps, or you VoIP provider is better/closer and/or you directory redirections help….
I'll give a shot to these improvements.

But most important for me, using a very poor country side 3M/128k DSL line, I really have to enable QoS in order to shut down/lower any non-VoIP traffic while a call is taking place....any input? Wizards seemed of no use for me...

robi

@blietaer:

But most important for me, using a very poor country side 3M/128k DSL line, I really have to enable QoS in order to shut down/lower any non-VoIP traffic while a call is taking place….any input? Wizards seemed of no use for me...

In sip.conf, general section add this:

[general]
disallow=all
allow=g729

Make sure to keep the correct order, disallow first, allow the second.

And of course check your SIP phones and your VoIP provider, do they support g729 codec (Linksys/Cisco and most SIP phones support it).
g729 is actually mpeg-compressed audio in 8kpbs, while alaw and ulaw are uncompressed pcm at 64kbps - sound quality is the same. Don't use alaw and ulaw unless you have plenty of bandwidth.

robi

@marcelloc:

I'll create the xml file to install your php files.

Thanks! I'll post a small update.

blietaer

Concerning the /usr/local/etc/asterisk/modules.conf, you really mean this is the whole content, or do you suggest to add your snipset at the end of any existing modules.conf file ?
same for the others ? (thouI guess you Sip.conf _is_longer than that…)

robi

I posted only parts of the config files, which are affected by my modifications.

In modules.conf, yes: just add what I posted at the end of the file.
In sip.conf I posted my general section, which should be at the beginning of each file. The other sections are each dependent of the particular setup, because every section defines a separate SIP client account (for a SIP phone device, for example).

There's no point thus, to post my entire config files, they are mostly irrelevant for others. What I suggested, are changes which actually make the thing work at all on pfSense nanobsd.

But if one looks into asterisk's documentation, everything will become straight clear.

marcelloc

First package release is out. :)

http://forum.pfsense.org/index.php/topic,47210.msg248054.html#msg248054

I did some changes to improve stability and checks for nanobsd or normal install.