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

mannix

Thank you, the workaround works for me

Bye

iced98lx

working like a charm on 1.2.2 now to get this thing configured.. ???

tester_02

mcrane, you mention 1.2.2 and 1.2.1. I seem to have this issue on my now 1.2.3 test machine also (others seem to also have this problem).
I also see an updated version available. Does that mean the updated version is for 1.2.3 / 2.0 and the workaround script is for the 1.2.1/1.2.2 versions?

Ditto with the others. Tonight it's back to where I left off, that damm internal setting so my extensions can talk to each other…...

bigboy

I am on 1.2.2, the script did not help. I am still facing with the same issue.

tester_02

Freeswitch Version 0.8.3.1

1 Test Machine 1.2.3 Yesterday's build. Now up and running
1 Production machine 1.2.2 - No go as advertised

On 1.2.2 used the supplied script…
Worked as advertised! Wohooo... back to playing!

Now that I've tested 1.2.3 I'm even tempted to switch the production machine.....

cybrsrfr

Need Help:
For those that still need help catch me on #pfsense-freeswitch irc channel. New to IRC I recommend using chatzilla which is a simple Firefox add on then just search for the #pfsense-freeswitch channel and join it.

Backup Package:
I am planning on building a pfSense backup package that will be designed to backup whatever package files are desired. It will be designed to create a single tgz backup file for any directories that are listed to backup. Such a backup package could be used to "roll back" a package.

It would also be useful to back pfSense, FreeSWITCH, TFTP files, RRD graph data, logs, and any other future packages.

Trouble Shooting Tip:
If you are having problems starting FreeSWITCH then the following will help you see what is wrong.
1. Enable SSH on pfSense
2. Connect to the console or through SSH
3. cd /usr/local/freeswitch/bin
4. check to see if freeswitch is running with the following:
ps -waux | grep freeswitch
5. start FreeSWITCH from the console
./freeswitch
Watch for immediate errors an execution ending or red errors that indicate something has gone wrong.

If you FreeSWITCH is running and you want to connect to monitor the console
1. cd /usr/local/freeswitch/bin
2. Replace the 192.168.1.1 with your LAN IP address.
./fs_cli -H 192.168.1.1

mrguitar

Man that's cool! Thanks Mcrane. Updating now.

…seriously "moderators", we need to change his status to Super Hero Member.

chpalmer

Trying to reinstall last night and this morning my box gets to "Loading package configuration… "

and never goes any farther... Ideas?

Running pfSense 2.0

"Fatal error: Cannot create references to/from string offsets nor overloaded objects in /etc/inc/xmlparse.inc on line 68 "

cybrsrfr

This error is a bug on pfSense 2.0. Try a different snapshot build of pfSense 2.0.

@chpalmer:

"Fatal error: Cannot create references to/from string offsets nor overloaded objects in /etc/inc/xmlparse.inc on line 68 "

chpalmer

Thanks!

;D

chpalmer

Any suggestions which snap to use for 2.0? The jan 15 version I was using worked for the longest time but now wont.?..

The latest version wont work with the same results…

tester_02

I'm having issues with inbound calling. Anyone have suggestions?

I've got 2 providers (2 DID), and unknowingly, I have both with the same username.
The problem is that during inbound calls, the destination_number is coming in as my username in freeswitch (both providers). So for my call routing in the public tab, I cannot use destination_number to tell which call is coming in (number is not being recognised). I thought I would use the Network_addr as a condition, but if I put the ip address, it does not find a match, even though it looks like it's right
Regex: [1001] network_addr(66.51.127.173) =~ /(66.51.127.173)/

The numbers are identical, so it has to be a formatting thing.

I also have an issue where if I call in and the calls goes to voicemail, I cannot leave a message. As I talk into the phone to leave the message, it stops and says it is below minimum record length, even thought I am still talking. This is not an issue if I am calling from extension to extension.

Love the software, lots of fun things to play with still….

cybrsrfr

chpalmer: The snapshots I tested where saved on a laptop that has a power issue and will no longer power up.

tester_02: on the public tab use an anti-action as a catch all then for the action set it to info and leave the data field empty. The go to the console and watch for info a call coming in from each gateway. 'info' will send information to the console which will show in green. You can then use any of that information with the condition and direct your calls accordingly. So all you will need to do is look for something unique among the info to determine how to route the call.

On your voicemail issue it sounds like you are having a one way sound audio problem. You should test by calling another extension inside the same network. It could be simply settings needing to be adjusted on the phone.

tester_02

@mcrane:

tester_02: on the public tab use an anti-action as a catch all then for the action set it to info and leave the data field empty. The go to the console and watch for info a call coming in from each gateway. 'info' will send information to the console which will show in green. You can then use any of that information with the condition and direct your calls accordingly. So all you will need to do is look for something unique among the info to determine how to route the call.

The only unique thing that I could get was the ip.
so I set the network_addr to be equal to the ip. That did not work, so I pit the ip to be ^(ip)$ but it does not work. I've looked at some freeswitch forums but it's not leading me to the right direction, I keep getting..
Regex: [1001] network_addr(66.51.127.173) =~ /(66.51.127.173)/

It has to just be a syntax thing. Any idea what the proper sytax could be?

As for the voicemail issue…'ll play with the phone and see what's going on. Strange thing is I can have a conversation on the phone (so I know audio works), it's just the voicemail recorder that does not hear it.

One last question, what do you have for dialplan settings on your phone? Do you blank them out and let freeswitch do the plan?

Thanks again!

chpalmer

Thanks mcrane… I dropped back to 1.2.3 for now. Its working for me.

chpalmer

Just a report:

My provider is getting this line from me now (instead of the standard sip:1234567890@myipaddy:5080;transport=udp)

sip:gw+Voip Line 1@myipaddy:5080;transport=udp

pfsense 1.2.3 package 0.8.3.1

cybrsrfr

pfSense FreeSWITCH package 0.8.3.3

Trimmed whitespaces from freeswith.xml file and other xml files so that FreeSWITCH will now install on pfSense 2.0.

Note:
The latest pfSense 2.0 snapshot now use PHP 5.2.9. This new version of PHP uses an updated libxml which should fix the XML problems that have been experienced in pfSense 2.0.

chpalmer

@chpalmer:

Just a report:

My provider is getting this line from me now (instead of the standard sip:1234567890@myipaddy:5080;transport=udp)

sip:gw+Voip Line 1@myipaddy:5080;transport=udp

pfsense 1.2.3 package 0.8.3.1

Was playing some more last night. "The Voip Line 1" comes from my gateway name. Dont know where the gw+ comes from. Is there a way to fix this?

cybrsrfr

In order for me or anyone else to help you please provide more information on your configuration.

Or try IRC freenode at: #pfsense-freeswitch

chpalmer

Sorry…

1.2.3-PRERELEASE-TESTING-VERSION
built on Tue Mar 3 22:30:29 EST 2009

package now... 0.8.3.3

This is a fresh install of both the firewall and Freeswitch just to make sure...

The config I was using worked up till the last two packages. Ptretty much default otherwise.

Reinstall- Ive tried starting over without any backups from configs.

Provider is pointed back to my gateway name "Voip Line 1" and not my user id. "1231231234"

Anything else I can tell you?

Im lost...