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

tester_02

@mcrane:

@tester_02:

So I decided to modify the internal setting and specify the rtp-ip and the sip-ip.

The default doesn't need to be changed in most circumstances.

@tester_02:

"Can't find user [1003@192.168.0.3]

Look on the status tab and see what IP the internal profile uses. That is the IP that your phone should use to register.
On the 'Internal' tab there is a variable called: force-register-domain if you uncomment that so that it is applied then all registrations that FreeSWITCH receives will be forced seen as that domain that is specified. This means the phone could register with the domain or the IP that the Internal profile is listening on.

I agree that it should not need to be changed, as my other test system had no issues with getting the correct interface, and working by default. This current(final) setup still reads in the sofia status
68.151.XXX.XXX alias internal ALIASED
While my other setup reads in that line, the IP of my internal network.

The change you suggested works! I can now connect to freeswitch from the phones.
So the only conclusion I see here is that if you are unable to connect to freeswitch, watch the "sofia status profile internal" in the status tab. If it's the wrong one, you have to modify 3 items in the internal settings. The rtp-ip, the sip-ip and uncomment force-register-domain.

Could there be an issue with it showing the WAN ip in the internal setting above that someone outside could connect to freeswitch as it's now listening on the wan? (I guess they would still need to know the extension and password)
Then again I understand that the terminology in freeswitch different from what I might perceive it to be…

ANYWAYS!! Thanks! I'm on my final setup now, connecting, dialing out, and am down to getting inbound calls (plus playing with other items). I know the rest I can play/read.

bigboy

I note that mod_openzap.so is missing in latest installation.

Fitopy

HI mcrane,
I'm running pfsense 1.2.2 and i can't install freswitch correctly. I't installs all the gui components but fails to install binaries. I manually deleted the pckg according to this thread , then reinstalling , removing and reinstalling again but keeps failling with this errors :

Warning: fopen(/usr/local/freeswitch/scripts/recordings.js): failed to open stream: No such file or directory in /usr/local/pkg/freeswitch.inc on line 197 Warning: fwrite()

tons off those errors at the end of the installation process. I have tried to create manually "/usr/local/freeswitch" just to test what happends with no luck. The directory is still empty .

Has this been reported? or has not been tested on 1.2.2

Tks a lot and keep up the good work .

p.s.: Sorry I'm not very fluent in english

tester_02

@Fitopy:

Has this been reported? or has not been tested on 1.2.2

I can't help you much, but I do know it works on 1.2.2. Freeswitch runs ok on my current 1.2.1 system, and it ran even better on my 1.2.2 system.
Both systems I've installed and even reinstalled, and never had your errors.
Sorry can't be of more help than that.

cybrsrfr

@bigboy:

I note that mod_openzap.so is missing in latest installation.

Next version will have mod_openzap.so file but in order for it to work zaptel has to be compiled into the FreeBSD kernel which it isn't at this time. I've worked on doing that but so far have not succeeded.

cybrsrfr

@Fitopy:

Warning: fopen(/usr/local/freeswitch/scripts/recordings.js): failed to open stream: No such file or directory in /usr/local/pkg/freeswitch.inc on line 197 Warning: fwrite()

I'm not exactly sure why your package is failing to install correctly. Is your firewall behind a proxy? or a Firewall that is removing some of the data stream?

bigboy

@mcrane:

@bigboy:

I note that mod_openzap.so is missing in latest installation.

Next version will have mod_openzap.so file but in order for it to work zaptel has to be compiled into the FreeBSD kernel which it isn't at this time. I've worked on doing that but so far have not succeeded.

Shouldn't we just install from port version? I managed to install Zaptel from freebsd port on pfsense 1.2.2 Dev ISO and have it started and detect by adding script file in rc.d, similar to freeswitch.sh but start zaptel instead.

cybrsrfr

The dev iso has the tools necessary to compile a port. Standard pfsense install does not have those tools. If I or someone else can come up with a process that adds the compiling tools back into pfsense then I will add it to the FreeSWITCH package or create a package specifically for compiling ports.

Mark

tester_02

mcrane. How do we uninstall freeswitch so that it does not save any settings?

I'm having issues with my setup. With changing the internal Ip settings, the phones can register to freeswitch, but I can't get it to talk to each other (dial another extension and I get a couple of tones and goodbye). I still thing it's that it shows my wan ip as internal…

Anyways, I wanted to uninstall freeswitch, and then reinstall from scratch. The problem is that when I reinstall, it puts back all my settings.
I even uninstalled, rebooted, and ssh into the box to see that the backup file in /tmp does not exist. It still gets the settings!

One last question. Can you see any issues with this package and a provider that uses a non-standard port? vbuzzer uses port 80.

thanks!

cybrsrfr

@tester_02:

mcrane. How do we uninstall freeswitch so that it does not save any settings?

Diagnostics -> Backup Restore
Download the configuration then edit it and remove references to any tag that says <freeswitch*<br>Then restore the configuration.

@tester_02:

One last question. Can you see any issues with this package and a provider that uses a non-standard port? vbuzzer uses port 80.

Try putting the domain:port when you are setting up the gateway's proxy.</freeswitch*<br>

cybrsrfr

pfSense FreeSWITCH package version 0.8.1 is now available.

1. It includes FreeSWITCH version 1.0.3 revision 12228.
2. Fixed a minor install error.
3. Added new dependency files that were required for 1.0.3.
4. Created a backup directory to store a copy of the original config. /usr/local/freeswitch/conf.rev.orig

tester_02

@mcrane:

pfSense FreeSWITCH package version 0.8.1 is now available.

yayyyy!
0.8.0 went BOOM!!!

Update:
Actually both my systems went boom on even the 0.8.1 update.. Won't start up due to line errors on freeswitch.inc

Here is some more info from the status page….
unable to connect to 68.XXX.XXX.XXX:8021 in /usr/local/pkg/freeswitch.inc on line 97 Warning: socket_set_blocking(): supplied argument is not a valid stream resource in /usr/local/pkg/freeswitch.inc on line 98 Warning: fsockopen(): unable to connect to 192.168.0.3:8021 in /usr/local/pkg/freeswitch.inc on line 97 Warning: socket_set_blocking(): supplied argument is not a valid stream resource in /usr/local/pkg/freeswitch.inc on line 98 no handle

Update 2:
ok, I crashed my test machine by editing the backup and restoring (that's why it's a test machine).
Anyways, fresh install of pfsense 1.2.2
Freeswitch installs with the above errors.

So I'd say it's temporarily broken.. Do not update!!

oln

After update to FreeSWITCH 0.8.1:

Service Freeswitch does not start and nothing is written to the log.

bigboy

@oln:

After update to FreeSWITCH 0.8.1:

Service Freeswitch does not start and nothing is written to the log.

I am having the same issues.

billm

No issues here on 2.0 (other than the unrelated php xml bugs we're fighting in 2.0).

–Bill

iced98lx

@bigboy:

@oln:

After update to FreeSWITCH 0.8.1:

Service Freeswitch does not start and nothing is written to the log.

I am having the same issues.

Also having this issue on 1.2.2

ldavismead

I can confirm this behavior. When attempting to start FreeSWITCH as root from the console (module version 0.8.1 on pfSense 1.2.2), it fails to start saying that it can't lock the pid file (/usr/local/freeswitch/log/freeswitch.pid, IIRC). Removing this file or creating it ahead of time with world-writable permissions had no effect.

I upgraded pfSense to the latest 1.2.3 nightly, and this cleared up the FreeSWITCH issue; I can now start it from the console as well as manage it from the webConfig services interface. So I'd hazard a guess that its some sort of dependency issue with 1.2.2 that goes away in 1.2.3 (and presumably also 2.0).

iced98lx

@ldavismead:

I can confirm this behavior. When attempting to start FreeSWITCH as root from the console (module version 0.8.1 on pfSense 1.2.2), it fails to start saying that it can't lock the pid file (/usr/local/freeswitch/log/freeswitch.pid, IIRC). Removing this file or creating it ahead of time with world-writable permissions had no effect.

I upgraded pfSense to the latest 1.2.3 nightly, and this cleared up the FreeSWITCH issue; I can now start it from the console as well as manage it from the webConfig services interface. So I'd hazard a guess that its some sort of dependency issue with 1.2.2 that goes away in 1.2.3 (and presumably also 2.0).

Interesting just upgraded to latest nightly snapshot and still no freeswitch for me..

tester_02

So I guess the common theme is
1. If you are running 1.2.1 or 1.2.2. DO NOT UPGRADE TO THE LATEST VERSION. Until we hear back from mcrane
2. If you are running 1.2.3 or 2.0 take your own risk if you want. It may/may not work.
3. If you upgraded already and it's crashed your freeswitch, then we are out of luck until mcrane comes up with something..

wait…

cybrsrfr

The system I'm running is working fine on pfSense 1.2.3.

I'm currently on IRC at #pfsense-freeswitch. Those with problems please contact me there and I will help you get your systems working. As the problem is identified I will get it fixed in the package.

Mark