FreeSWITCH package for pfSense 1.2.1 and 2.0 released. PBX or Proxy
-
Sounds good. I confirmed that the reloadxml command is working, although it didn't work for me when adding extensions immediately after install, but that might just be FreeSwitch trying to be efficient and not having Sofia loaded (since I didn't have any sip devices listed prior to that), or who knows. It's working now, so whatever.
Another question…you'll be getting several package bug reports from me (if there are any bugs and I'm not just being retarded. :) ), do you prefer I PM them to you?
#1: When changing the area code in the settings tab, 7 digit calls still get prepended with 918, due to the <x-pre-process cmd="set" data="default_areacode=918">line in the VAR tab. Should this be changed to the value from the Settings tab? EDIT: I actually put ${default_areacode} in the area code field on the settings page...I figure that should pull it from the vars.xml file, where I have it set correctly. Is this correct? Also, what xml setting does the "area code" on the settings page change?
#2: In /usr/local/freeswitch/conf/dialplan/default/01_provider.com.xml, 10 digit calls just drop. Adding the following section will fix that by prepending a 1, and sending the call out.
<extension name="domestic.provider.com"><condition field="${toll_allow}" expression="domestic"><condition field="destination_number" expression="^(\d{10})$"><action application="set" data="effective_caller_id_number=${outbound_caller_id_number}"><action application="set" data="effective_caller_id_name=${outbound_caller_id_name}"><action application="bridge" data="sofia/gateway/${default_gateway}/1$1"></action></action></action></condition></condition></extension>#3: I can't get the "say:" command in the IVR xml file to work. I get the following error in the console:```
2008-10-28 22:43:15 [ERR] mod_native_file.c:68 native_file_file_open() Error opening /usr/local/freeswitch/sounds/en/us/callie/say:Press 1 to join the conference, Press 2 to join the other conference.PCMU#4: In /usr/local/freeswitch/conf/dialplan/default/01_provider.com.xml all the caller id setup is done with single dollar signs…IE, ${outbound_caller_id_number}. I'm no FreeSwitch guru, so I can't explain why, but I can't pass callerid through Voicepulse to the PSTN until I change them all to double dollar signs, as I saw in the vars.xml file...note that I didn't add a dollar sign to ${default_gateway}, only the caller_id settings, and that's apparently working...I'm not sure what the difference is. #5: In /usr/local/freeswitch/conf/dialplan/default/01_provider.com.xml all the caller id variables reference ${outbound_caller_id_number} or =${outbound_caller_id_name}. In the vars.xml file, the only caller id variables are outbound_caller_id and outbound_caller_name. Until I assign my caller id data to the first variables, outbound_caller_id_number and outbound_caller_id_name, I can't pass callerid through Voicepulse to the PSTN.</x-pre-process> -
I have completed a few more changes to the package.
1. When adding a Gateway the following command is now called automatically through a socket connection.
sofia profile external rescan reloadxml
This will pick up new gateways that have been added or deleted and handle them appropriately without restarting FreeSWITCH. There still may be times a few times that require a restart for a gateway. I could have been more aggressive and had it run: sofia profile external restart reloadxml but that would interrupt current incoming/outgoing calls so I chose not to go that way.2. Added a few more input fields for Gateways such as 'Realm' and 2 others fields in many cases this is not needed but I wanted to make sure that there is flexibility in GUI for special situations. If a field is left blank then the corresponding xml parameter tag will not be used in the config. The fields under the 'Gateways' tab match up exactly with the SIP provider examples at:
http://wiki.freeswitch.org/wiki/SIP_Provider_Examples3. The 'Modules' tab has been changed from the original text area to a list in the GUI that allows you to enable or disable different modules. Note: not all modules are available in this build… an example would be Cepstral text to speech which doesn't have a native FreeBSD build. Flite text to speech is available if its modules is enabled.
Now to answer your questions...
Sounds good. I confirmed that the reloadxml command is working, although it didn't work for me when adding extensions immediately after install, but that might just be FreeSwitch trying to be efficient and not having Sofia loaded (since I didn't have any sip devices listed prior to that), or who knows. It's working now, so whatever.
Sofia (SIP) is loaded by default. If you restart FreeSWITCH under Services then you should check the Status tab to make sure that the sofia internal profile is loaded if it does not load it will say 'Invalid Profile!' This is caused from a port not closing by the time you restart FreeSWITCH. It can be solved by shutting down the service longer sometimes up to 2-5 minutes then starting it again. Rebooting will also work to clear that up.
Another question…you'll be getting several package bug reports from me (if there are any bugs and I'm not just being retarded. :) ), do you prefer I PM them to you?
If the information can be valuable to others then the forum. Items that are not likely to be useful to others you can pm me.
#1: When changing the area code in the settings tab, 7 digit calls still get prepended with 918, due to the <x-pre-process cmd="set" data="default_areacode=918">line in the VAR tab. Should this be changed to the value from the Settings tab? EDIT: I actually put ${default_areacode} in the area code field on the settings page…I figure that should pull it from the vars.xml file, where I have it set correctly. Is this correct? Also, what xml setting does the "area code" on the settings page change?</x-pre-process>
$${default_areacode} in the area code field on the settings page should work fine.
The settings page populates the area code in the following xml file /usr/local/freeswitch/conf/directory/default/default.xml#2: In /usr/local/freeswitch/conf/dialplan/default/01_provider.com.xml, 10 digit calls just drop. Adding the following section will fix that by prepending a 1, and sending the call out.
<extension name="domestic.provider.com"><condition field="${toll_allow}" expression="domestic"><condition field="destination_number" expression="^(\d{10})$"><action application="set" data="effective_caller_id_number=${outbound_caller_id_number}"><action application="set" data="effective_caller_id_name=${outbound_caller_id_name}"><action application="bridge" data="sofia/gateway/${default_gateway}/1$1"></action></action></action></condition></condition></extension>This can also be done from the dialplan tab as noted in the this first message in this thread. As you have shown the caller id can also be done for all calls going outbound to the gateway with the 10 digits shown above. The other method for caller id is per extension which can be done by setting the effective caller id on the 'Extension' tab.
#3: I can't get the "say:" command in the IVR xml file to work. I get the following error in the console:```
2008-10-28 22:43:15 [ERR] mod_native_file.c:68 native_file_file_open() Error opening /usr/local/freeswitch/sounds/en/us/callie/say:Press 1 to join the conference, Press 2 to join the other conference.PCMUI have not worked with the XML IVR because I prefer doing the IVR in javascript. For help with the XML IVR see the wiki at http://wiki.freeswitch.org/
To see an example IVR in javascript.
http://wiki.freeswitch.org/wiki/Javascript_Examples look for the example ivrmenuofficehours.js link.The sounds under /usr/local/freeswitch/sounds/en/us/callie/ are pre-recorded messages using Cepstral's text to speech engine.
At this time Cepstral does not have a native FreeBSD build. Alternatives are to pre-record messages on a different computer, use Flight text to speech engine, or make your own voice recordings.#4: In /usr/local/freeswitch/conf/dialplan/default/01_provider.com.xml all the caller id setup is done with single dollar signs…IE, ${outbound_caller_id_number}. I'm no FreeSwitch guru, so I can't explain why, but I can't pass callerid through Voicepulse to the PSTN until I change them all to double dollar signs, as I saw in the vars.xml file...note that I didn't add a dollar sign to ${default_gateway}, only the caller_id settings, and that's apparently working...I'm not sure what the difference is.
Looks like you found a missing $ in the default config. Next time I compile I will check to see if that has been corrected if not I will report it if you don't beat me to it.
#5: In /usr/local/freeswitch/conf/dialplan/default/01_provider.com.xml all the caller id variables reference $${outbound_caller_id_number} or =$${outbound_caller_id_name}. In the vars.xml file, the only caller id variables are outbound_caller_id and outbound_caller_name. Until I assign my caller id data to the first variables, outbound_caller_id_number and outbound_caller_id_name, I can't pass callerid through Voicepulse to the PSTN.
Vars.xml maps to the 'Vars' tab in the GUI. It sets up variables that can be used anywhere in the config. There may be some cases where the vairables are not being used anywhere in the config. FreeSWITCH is a young open source project and the configs are evolving and being improved over time.
-
Added an option to the package to disable gateways without deleting them.
-
A tip for those using this package. You can pickup your voicemail by dialing the extension number you are calling from. So for example if your extension is 1001 and you want to get your voicemail then from extension 1001 call 1001 and it will send you to your voicemail.
Alternative method to access voicemail is to dial extension 4000 followed by your extension number and the password.
GUI enhancements that are coming soon …
1. Management tool for adding and removing recordings
2. Management tool to setup and configure an IVR (Auto Attendant) -
Minor version update. Added commands to the 'Status' tab to start, stop, restart, rescan, reloaxml and flush inbound registrations. Also found and corrected 2 minor issues with syntax.
-
Thanks mcrane…this package rocks.
-
Thanks for the encouragement.
New version is almost ready. I will try my best to get it out by sometime tomorrow (Saturday 29 Nov 2008).
-
was this updated over the weekend? it looks like it wasnt based on my packages list.
is there another way to check other than the packages list page within my pfsense?
-
Sorry I missed my goal for weekend release still working on it. Should be soon.
-
Any idea when this will be coming along Mcrane? My Linksy 941 clips the packet size of RTP and apparently there is a fix for this in the latest version of freeswitch. My phone in usable until this gets updated.
Thanks, and sorry if im sounding pushy!
-
I will be releasing this today Friday 5th December 2008. When its ready I will announce it here.
-
Announcing the release of the new pfSense FreeSWITCH package version 0.3.2.
The new package includes
1. Recordings
2. IVR (Auto Attendant)
3. 'Public' Tab
4. 'Dialplan' Tab
5. 'Gateways' Tab now has an advanced tab that hides options that are not used often simplifying the interface. Also has a tool that will make it easy to quickly add outbound dialplan rules for 7,10, and 11 digit dialing.
6. Improved 'status' Tab
Added a download button for 'call detail records' in csv format and for logs.
Added better formatting for active calls and channels.
7. New build of FreeSWITCH revision 10638 from 5 December 2008.In the previous versions after adding a new gateway, extension or some other change the configuration was automatically reloaded. However this took a little more extra time after each change. 0.3.2 no longer reloads the configuration automatically. To reload the configuration go to the 'Status' tab and click on 'reloadxml' if you adding a gateway then press rescan. Update a gateway then press 'restart' on the external profile.
Added some documentation and links to the interface hopefully making things a bit easier.
The 'Public' tab in the previous version was a text area that allowed you to modify the XML manually. This is still available under 'deprecated xml'. Please move your config to the new public GUI interface as the 'deprecated xml' will be available for a short period of time allowing anyone who has an older install a chance to move the config.
Public tab routes inbound calls to the desired location.
Example 'Public' config in the new interface:
Extension Name: inbound_did
Enabled: true
Order: 001
Description: Inbound DIDDirects specific calls that are calling into the following DID.
Tag: Condition
Type: destination_number
Data: ^(12081231234)$Call is transferred to extension 1001. Can also use this to direct calls to the IVR.
Tag: Action
Type: transfer
Data: 1001 XML default–-- Upgrade Warning ------------
If you are upgrading then backup your recordings and voicemail before starting. To be absolutely you have everything backup the /usr/local/freeswitch directory. You can do this by using the 'Command' tool under 'Diagnostics' to tar gzip the directory and then use copy the file to the /tmp directory or use the 'Download' to save a copy of the file.
---- Upgrade Warning ------------If you have any questions or problems please post a message here.
Best Regards,
Mark J Crane -
Last night (8 December 2008) fixed a bug or two that prevented hearing the prompts for recording on the 'Rec' tab.
Today (9 December 2008) fixed an issue with the auto attendant (IVR) saving correctly and the audio from playing.If you have installed the package make sure to back up /usr/local/freeswitch and then reinstall to the latest version.
-
I reinstalled the package to upgrade to the latest version and ended up with some missing files…the IVR tab and Gateway tab both gave 404s. Uninstalled and reinstalled the package, and it works now. So, if you run into problems, just try uninstalling and reinstalling.
-
mcrane, very nice job. I'm struggling a bit figuring out how everything interacts in the GUI, but this is awesome. Great job.
One feature request when you have time would be to add controls to change the order of IVR\inbound conditions and actions, like there are for firewall rules…add below this, and insert here.
-
mcrane, very nice job. I'm struggling a bit figuring out how everything interacts in the GUI, but this is awesome. Great job.
As you figure out how it interacts post some tips here on the forum so that it can benefit others. If you have questions post them here and I will help.
One feature request when you have time would be to add controls to change the order of IVR\inbound conditions and actions, like there are for firewall rules…add below this, and insert here.
I agree ability to change the order would be useful. I will work on it when I get some time.
-
Does anybody have a pointer ?
We already are running a PFSense Box as the main Firewall in our test environment. We now what to add a separate PFSense box with the Freeswitch package, and running just for that purpose.Do I need to setup
a "Transparent Firewall"
b "Bridge w/th Outbound NAT'
c "Router [Disable Firewall] + Bridge]" ?Sorry if these options don't make sense, but hopelly they will make you smile :). Point being is that I should be able to work all on the WAN as a single network device and not need all the extra NATing,
Unfortunately my alternative if I cant get moving forward is to use askozia. I only have 5 days applied to this test. 3 to go.
-
Does anybody have a pointer ?
We already are running a PFSense Box as the main Firewall in our test environment. We now what to add a separate PFSense box with the Freeswitch package, and running just for that purpose.Sounds good.
a "Transparent Firewall"
b "Bridge w/th Outbound NAT'
c "Router [Disable Firewall] + Bridge]" ?What you do for choice a, b, or c is dependent on you are trying to accomplish. For example if your phones are always going to be in the same network, and or you are using a point to point vpn between locations then setting the FreeSWITCH machine inside NAT should work fine.
However if you want to have FreeSWITCH work inside your office and phones work outside the office without a VPN then the easiest way would be to give the FreeSWITCH machine a real world IP on the WAN. If it is static you can use the IP address or a domain. If the IP is dynamic then use a dynamic dns provider to provide a domain name. If you choose to use a domain name then you will need to set the domain= from the 'var' tab to the domain you are wanting to use.
You can disable the firewall if you have a firewall in front of the FreeSWITCH machine. However my preference still leans toward a higher level of security by leaving the firewall on so that it firewalls itself. Really this depends on if its has a public IP then yes I would leave the firewall in tact. If FreeSWITCH machine is on the LAN IP and there are only a few people connected to the LAN then you might be okay with the firewall disabled.
Sorry if these options don't make sense, but hopelly they will make you smile :). Point being is that I should be able to work all on the WAN as a single network device and not need all the extra NATing,
At this moment you still need the LAN port. I have PHP communicating with the FreeSWITCH package over the LAN interface. However I be changing this soon so that it will work with one or more interfaces.
Unfortunately my alternative if I cant get moving forward is to use askozia. I only have 5 days applied to this test. 3 to go.
I will attempt to help you get this working before your deadline.
-
Announcing a few more features that I stayed up all night to add.
1. Auto Attendant timeout. The recording plays one time and then the timeout is used to allow more time for dtmf to be detected. If no dtmf is detected during that time the system will direct the call to the timeout out option 't'.
2. Backup and Restore feature I felt was an important feature.
I have added a backup and restore buttons to the 'Status' tab. When you click on the backup button a /usr/local/freeswitch directory is tar gzipped and saved into /tmp/ directory as freeswitch.bak.tgz. When the file exists then the 'restore' button will be visible.The restore currently leaves the config directory alone allowing pfSense configuration to store all the configuration.
However the restore does extract the backup files to the following folders.Internal Database files keep track of registrations, voicemail details, and more.
/usr/local/freeswitch/db/Logs
/usr/local/freeswitch/log/Recordings from the 'Rec' tab are saved here.
/usr/local/freeswitch/recordings/Saves the javascript files most usefull if you have any custom scripts in this directory.
/usr/local/freeswitch/scripts/Voicemail audio files are stored in this location
/usr/local/freeswitch/storage/–-----------------------------------------------------
If you are using a version less than 0.4.1 then you should
manually create the backup before upgrading using the
following command.Diagnostics->Command->PHP Execute->Command
system('cd /usr/local/;tar cvzf /tmp/freeswitch.bak.tgz freeswitch');After you have upgraded to 0.4.1 or higher then you will have the
backup button that you can use at any time.If /tmp/freeswitch.bak.tgz file exists during the install then the
restore will automatically run directory content to /usr/local/freeswitch.
Upgrading the FreeSWITCH pfSense package:
System-> Package Manager-> Installed Packages
Updateat this time the any of the 'Reinstall' buttons will not likely work.Its working nowAt this time the upgrade procedure is to make the backup and then remove the FreeSWITCH package.
Then install the package again. During the installation it will detect the backup and restore the additional directories. -
Thanks for the advise, so let me understand
For now I will setup the FreeSwitch box behind the NAT [ Other pfsense box ] inside the LAN network.
- I can have Firewall on … got that ...
- I can connect just the LAN of FreeSwitch Box and give it a static private IP part of our existing network and move on, no need for bridging or anything else
- I suppose when you update the package we can choose which network port to use. In either case with just the LAN network port and an ethernet cable I should be fine, ... but what about NATing on that box ? will that interfere ?
Thanks in advance