Skip to main content

conference call manager blank

Posted by cirrustelecom on Mon, 06/23/2008

has anyone had the problem with the conference call manager in 6.0.1.59 showing no users in the conference (even thou there are) ?


Submitted by cirrustelecom on Mon, 06/23/2008 Permalink

in the asterisk log:

[Jun 23 15:36:55] NOTICE[355]: manager.c:929 authenticate: 12.19.49.94 failed to pass IP ACL as 'manager'

== Connect attempt from '12.19.49.94' unable to authenticate

That IP address is not mine and it only shows up when I click on the "Manage Conference" button.

Submitted by cbbs70a on Mon, 06/30/2008 Permalink

I had the same error and Alex worked with me a long time to figure out what it was. My guess is that you will not be able to see anything in the manager interface either. Essentially it has to do with the version of the flash player in your web browser. Adobe changed the flash player security rules and the change is not backwards compatible. The solution requires that the server have a security policy file. Check it out here.

http://www.adobe.com/devnet/flashplayer/articles/socket_policy_files.ht…

The fix is to do the following: (1) have a policy file on your Thirdlane box and (2) run a little PERL daemon out of xinetd to serve up the policy file. I can also post the files if you need me to. It shouldn't take more than 5 minutes to install.

Later;

FSD

Submitted by duc on Tue, 10/07/2008 Permalink

Hi cbbs70a,

I successfully install the xientd and the policy, my var/log/syslog tell me :

Oct 7 10:05:13 xyzPbx xinetd[20529]: xinetd Version 2.3.14 started with libwrap loadavg options compiled in.

Oct 7 10:05:13 xyzPbx xinetd[20529]: Started working: 1 available service

I use the following flashpolicy.xml :

<?xml version="1.0"?>

I use the following service in /etc/xinetd.d/flashpolicyd :

service flashpolicy

{

disable = no

wait = no

socket_type = stream

flags = IPv4

port = 843

user = nobody

group = nogroup

server = /usr/local/sbin/in.flashpolicyd.pl

server_args = --file=/usr/local/etc/flashpolicy.xml

}

But unfortunaltely,when I launche the conference manger I have the famous error message :

== Connect attempt from '172.ZZ.YY.XX' unable to authenticate

To be sure I've added the following line in manager.conf and reloaded.

permit=172.ZZ.YY.0/255.255.255.0

Any idea ? I'm on Debian...

Submitted by duc on Tue, 10/07/2008 Permalink

In my last post, I forget to mention this :

I use the PBX Manager 6.0.1.63.

Cheers, Duc

Submitted by cbbs70a on Tue, 10/07/2008 Permalink

Its a pain to get the XML to format properly so you can see it here. Shoot me an e-mail to frank (at) digennaro (dot) com and I will e-mail you the files. It's pretty trivial. Don't forget to add an entry in /etc/services.

FSD

Submitted by Had on Sun, 05/24/2009 Permalink

Is there some step by step how to install this policy? tried to follow couple of articles but still doesn't work :(

Peter

Submitted by eeman on Mon, 05/25/2009 Permalink

I have a ruby one that works, you just have to make sure you have ruby installed, its easy to use. just run this script:

tar -zxvf flashpolicyd-2.0.tgz

cd flashpolicyd-2.0/

install -c -m 755 flashpolicyd /usr/sbin

install -c -m 755 flashpolicyd.init /etc/init.d/flashpolicyd

install -c -m 644 flashpolicy.xml /etc/

cat > /etc/sysconfig/flashpolicyd <<-EOF

        TIMEOUT=10

        XML=/etc/flashpolicy.xml

        LOGFREQ=1800

        LOGFILE=/var/log/flashpolicyd.log

EOF

chkconfig --add flashpolicyd

chkconfig flashpolicyd on