FreeSWITCH package for pfSense 1.2.1 and 2.0 released. PBX or Proxy

adrianhensler

Nice mention of the freeswitch pfSense package in the freeswitch 1.02 announcement:

There are two specific projects that are a part of the ecosystem to keep an eye on. The first is TCAPI - an ambitious project that aims to provide a comprehensive Web-based front-end to FreeSWITCH. The second is pfSense. The pfSense project has incorporated FreeSWITCH as an optional package. This allows pfSense users to set up an appliance that can be a PBX or soft-switch. pfSense and FreeSWITCH user Mark Crane has also added a simple GUI to the pfSense/FreeSWITCH package. Look for more interesting things to come from both of these projects.

adrianhensler

I still can't get the ivr to work. I can send an incoming call to the pre-existing ivr at extension 5000 so I can validate the process works at least that much. I can also dial the 5000 IVR from my internal voip phone.

It doesn't seem to like the IVR I make at ext 1999 (for example). I tried deleting all three of my (not working) test IVR's and then adding a new one, just condition=true, using one of the existing recordings for testing; context=default. The action is 1 / extension / 2000 (if 1 is pressed go to extension 2000)

I have no anti-action.

I'm sure it is something I'm not understanding. It keeps returning javascript errors in the log:

2009-01-06 00:16:39 [ERR] ivr_D8DE6EA5-D512-39E8-C88A-52CF71C7245E.js:128 mod_spidermonkey() near  SyntaxError: syntax error             else {

cybrsrfr

I did some more testing on the IVR (auto attendant) and found a bug. When no anti-actions where defined the result would be a javascript error as you reported. I have fixed this problem in the FreeSWITCH package version 0.5.8.5.

Please backup your files using the 'backup' button on the 'Status' tab. Then remove the FreeSWITCH package and then reinstall it.

I have also fixed a minor bug for the anti-actions correctly on and edit for the dialplan and public tabs.

In addition to fixing what was mentioned above I have also added a new feature to the IVR (auto attendant). One of the special option numbers that could be done was 't' for timeout which was the length of time to wait for dtmf until proceeding with the timeout option. There is now a new special option 'n' which routes the call now and doesn't wait for dtmf. This new option is useful for office hours IVRs where during the day the call goes to a live person directly and at night the call is directed to an after hours IVR.

adrianhensler

I can confirm that the changes to the IVR are now allowing me to create an IVR as expected!

Great work.

I did try to help by poking around the code, but I didn't find anything. Hopefully reporting the errors I was seeing helped.

adrianhensler

Am I dense or is the wiki locked from creating accounts?

I just wanted to add that if you are enabling intercom and you've changed your extensions you want to edit the line in default.xml that reads:

<condition field="destination_number" expression="^8(10[01][0-9])$">^M</condition>
```  … to match what is required.

thekod

It's locked because of spammers…email the coreteam for an account, or have someone who has an account make the change.

mwalsh

This may be a dumb question but I have an existing Asterisk box behind the firewall with all the required port forwarding and static NAT mapping. To use Freeswitch do I need to turn all of these off?

Thanks,

Mike

thekod

You will almost certainly need to either turn them off or use non-standard ports and NAT with Freeswitch.

cybrsrfr

Your choice is to run it on a different Internet IP address, or have fun trying to switch things to non standard ports on one of the other systems.

New IRC channel #pfsense-freeswitch

adrianhensler

You could possibly make a sip trunk from freeswitch to the LAN pbx depending on what your needs are; if you are looking to run both at the same time.

I just shut my asterisk box off in my case; but my needs were pretty simple. That's not to say that the freeswitch package won't suit your needs; it's just taking me a bit of time to get where I want it to be - but it's working great so far.

adrianhensler

If I am troubleshooting outbound calling; how can I tell what gateway is in use when I make the call?

The log doesn't seem to show that information, I just see that it is using " New Channel sofia/external/19024466245 [8be3f58d-d7de-dd11-998b-00508df13a9d]" for example.

I had a heck of a time getting dialing to go out over one of my gateways - I was testing by calling my cell phone - but it kept using the wrong gateway every time no matter how I dialed. Eventually I tried another number and it worked correctly. I'm still not sure what is going on there. I'm thinking I need to set up a freeswitch server outside of pfsense just so I can understand the flow better….

cybrsrfr

@adrianhensler:

If I am troubleshooting outbound calling; how can I tell what gateway is in use when I make the call?

On the 'Status' tab during a phone call you can see call information in the 'show channels' scroll through the info and you will see the gateway that is being used.

@adrianhensler:

I had a heck of a time getting dialing to go out over one of my gateways - I was testing by calling my cell phone - but it kept using the wrong gateway every time no matter how I dialed. Eventually I tried another number and it worked correctly. I'm still not sure what is going on there.

Directing outbound calls to the appropriate gateway can be quite easy. I will add additional information on this topic here and on the wiki to help you and other understand how calls are directed to Gateways.

The 'Dialplan' is used to direct calls out the Gateways (aka SIP trunks, Providers.) You can make the required entries to directly to the dialplan from the 'Dialplan' tab. However there is an easier way using the 'Dialplan Expression' tool that is available on the 'Gateways' tab. It can make the dialplan entries for you. After using the 'Dialplan Expression' tool you can see what it added to the dialplan by viewing them from the 'Dialplan' tab. If you plan on calling with 7 digit dialing you need to provide the 'Default Area Code' on the 'Settings' tab. FreeSWITCH determines the outbound route based on conditions. The conditions are written with 'regular expressions'. FreeSWITCH uses regular expressions throughout its config. The 'Dialplan Expression' tool is a text area box where the regular expressions are placed one per line. To simplify this there is a select box which allows you to choose what type of outbound calls are routed to this gateway. There are several choices my favorites are 7, 10, and 11 digit dialing. For those that prefer dialing a 9 first there are choices for dialing a 9 with 7, 10, or 11 digits. I will be adding additional choices in the very near future such as dialing 8, and international.

In most cases the provider expects calls to be sent to them with 11 digits. If your provider is one of the exceptions then you will need to edit the dialplan entries that were made by the 'Dialplan Expression' tool so that it sends 10 digits rather than the default 11.

@adrianhensler:

I'm thinking I need to set up a freeswitch server outside of pfsense just so I can understand the flow better….

The pfSense FreeSWITCH package has been designed to closely follow the FreeSWITCH config. The names of most things came from the xml config that FreeSWITCH uses. The paths are given in most cases. In short the design plan of the pfSense FreeSWITCH package has been to follow the default config so that knowledge gained from the pfSense FreeSWITCH interface or from the FreeSWITCH xml config can be interchangeable and mutually beneficial.

adrianhensler

Thanks as always mcrane.

My issue was that I had created the two gateways but was having difficulty getting calls to go over the one I wanted. I had one set for 11 digit dialing and one set for 7 digit dialing; but every time I tried to call it would go over the 11 digit dialing one even if I had only entered 7 digits. I think my problem was that it was adding the area code automatically and then going over the gateway I had set as a default?

In any case, I just gave up on my configs after a bit and erased them and started over and everything seems to be working as expected - most of my problems exist between keyboard and chair. I realize now that the configs match very closely, I didn't realize they were that close when I wrote the email last night. Very nicely done.

I wanted some way to be able to look at the logs and see what had happened rather than just looking at the 'live' channels - is there no way to do that? There must be a way to view that information?

cybrsrfr

@adrianhensler:

My issue was that I had created the two gateways but was having difficulty getting calls to go over the one I wanted. I had one set for 11 digit dialing and one set for 7 digit dialing; but every time I tried to call it would go over the 11 digit dialing one even if I had only entered 7 digits. I think my problem was that it was adding the area code automatically and then going over the gateway I had set as a default?

Sound like 'Dialplan Expression' tool was used and created a dialplan entry for 7 digits for both Gateways. If you have multiple gateways it is a good idea to see what you have already defined in the 'Dialplan' tab. If there are duplicates 7, 10, or 11 digit dialing it will choose the one that is assigned the lowest order. If there are ever duplicates there in the tab then I suggest removing them or editing them. You can add additional conditions such as an extension which would direct calls based on extension and on how many digits. If you have multiple gateways another approach is to make one gateway for 7 10 and 11 digit dialing and the other one requiring dialing a prefix number such as 8 or 9 and then the number.

@adrianhensler:

I wanted some way to be able to look at the logs and see what had happened rather than just looking at the 'live' channels - is there no way to do that? There must be a way to view that information?

You can enabled SSH under PFSense -> Advanced and run FreeSWITCH from the console. If you are at the pfSense menu on the console or from SSH then choose option 8.
cd /usr/local/freeswitch/bin
./freeswitch -stop
./freesiwth start

pressing F8 enables debug or F7 disables debug.

Or if you you can connect to it remotely from the LAN using the new fs_cli tool that the FreeSWITCH team has developed. I have attached the windows version to this post. You just need to remove the .txt extension from the file.

Run it from the command prompt with:

fs_cli.exe -H 192.168.1.1 -P 8021 -p ClueCon

Replace 192.168.1.1 with the LAN IP of your FreeSWITCH install. The port 8021 and the password: ClueCon are set from the 'Settings' tab.

fs_cli.exe.txt

adrianhensler

Thanks mcrane. I think I have the outbound straightened out. I did have two gateways and both as 7 digit and I wanted that so that the second one would work if the first one failed.

I think it kept dialing my test number (my cell phone) using the wrong gateway because I have an extension set up for it? Not sure; I'll look at this a bit more.

Quick question about mod_dingaling for gtalk integration.

I get this error in the logs when I try to sing in:

"2009-01-10 22:31:17 [DEBUG] libdingaling.c:1175 on_stream() TLS NOT SUPPORTED IN THIS BUILD!"

My understanding is that gtalk requires tls? Is this correct or am I missing something. I enabled the module and stopped FS.

Edited client.xml to be this:

 <profile type="client"><param name="name" value="gmail.com">
   <param name="login" value="adrianhensler@myemail.ca/gtalk">
   <param name="password" value="bigfatsecret">
   <param name="server" value="talk.google.com">
   <param name="dialplan" value="XML">
   <param name="message" value="FreeSwitch (The Future of Telephony)">
   <param name="rtp-ip" value="auto">

   <param name="ext-rtp-ip" value="stun:stunserver.org">
   <param name="auto-login" value="true">
   <param name="auto-reply" value="Press *Call* to join my conference">
   <param name="sasl" value="plain">
   <param name="tls" value="true">
   <param name="exten" value="2000"></profile>

But then I got the error as above.

cybrsrfr

@adrianhensler:

"2009-01-10 22:31:17 [DEBUG] libdingaling.c:1175 on_stream() TLS NOT SUPPORTED IN THIS BUILD!"

I will work on enabling this on the next FreeSWITCH compile.

chpalmer

mcrane- First thing, You Rock! As do all the PFSense authors and support staff! Thanks to all of you!

Now to anyone else that knows… I thought I was able to dial from extension to extension when I first installed this package. I believe the reason I cant now is that both extensions exist on the same ATA as ports one and two. Its a Zoom in case it matters. I need to verify when I get a free moment but any comments...

I need to reread the thread here again in case its covered and I missed it but- my IVR message answers when I have the inbound pointed that way however when I press a number it hangs up. Im lost on this at this point.

Otherwise its working great! :) ;D

chpalmer

IVR seems to be working now… ;D :)

adrianhensler

@chpalmer:

mcrane- First thing, You Rock! As do all the PFSense authors and support staff! Thanks to all of you!

Now to anyone else that knows… I thought I was able to dial from extension to extension when I first installed this package. I believe the reason I cant now is that both extensions exist on the same ATA as ports one and two. Its a Zoom in case it matters. I need to verify when I get a free moment but any comments...

pfSense ftw for sure.

I'll take a stab at your question - I think you'll have to use different ports for the extensions as they will be on the same IP? Does that help? Or is that what you meant by 'ports one and two' now that I reread your message. Never heard of Zoom so I won't be any help there. Maybe I'll set up my linksys pap2 later tonight and see if I can get both channels on that to work.

chpalmer

Thanks: I think thats my problem. It appears the adapter may not be specifying the ports to the pbx correctly.

http://zoom.com/ These guys have been around for years. I used to have a 33k modem made by them. (Now Im not sure I actually have a modem in my house anywhere, but thats for another post…)

Im setting up another ata right now as I post this to seperate them out for more controlled conditions...

:) ;D