Topic: conference call manager blank [Comments: 11]
cirrustelecom

Mon, 06/23/2008 - 15:33 | conference call manager blank

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) ?

cirrustelecom

Mon, 06/23/2008 - 22:38 | in the asterisk log: [Jun 23

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.

eeman

Tue, 06/24/2008 - 00:24 | what is your ip when you

what is your ip when you surf to http://whatismyip.com ?

Erik Smith
CTO
BluegrassNet Voice
dCAP
Thirdlane Support by BluegrassNet Voice
eeman at bluegrassnetvoice dot com

cbbs70a

Mon, 06/30/2008 - 22:11 | I had the same error and

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.html

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

eeman

Tue, 07/01/2008 - 14:44 | how specific were you in

how specific were you in your flashpolicy.xml

Erik Smith
CTO
BluegrassNet Voice
dCAP
Thirdlane Support by BluegrassNet Voice
eeman at bluegrassnetvoice dot com

cbbs70a

Tue, 07/01/2008 - 18:00 | All I did was add:

All I did was add: allow-access-from domain="*" to-ports="*"

FSD

duc

Tue, 10/07/2008 - 08:19 | Hi cbbs70a, I successfully

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"?>

<!DOCTYPE cross-domain-policy SYSTEM "/xml/dtds/cross-domain-policy.dtd">

<!-- Policy file for xmlsocket://socks.example.com -->

<cross-domain-policy>

   <!-- This is a master socket policy file -->

   <!-- No other socket policies on the host will be permitted -->

   <site-control permitted-cross-domain-policies="master-only"/>

   <!-- Instead of setting to-ports="*", administrator's can use ranges and commas -->

   <!-- This will allow access to ports 123, 456, 457 and 458 -->

   <allow-access-from domain="*" to-ports="*"/>

</cross-domain-policy>

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...

duc

Tue, 10/07/2008 - 08:21 | Addendum

In my last post, I forget to mention this :

I use the PBX Manager 6.0.1.63.

Cheers, Duc

cbbs70a

Tue, 10/07/2008 - 21:11 | Its a pain to get the XML to

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

Had

Sun, 05/24/2009 - 22:48 | Is there some step by step

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

Peter

Had

Sun, 05/24/2009 - 23:09 | just found

just found this:

http://www.lightsphere.com/dev/articles/flash_socket_policy.html

works ok

eeman

Mon, 05/25/2009 - 14:01 | I have a ruby one that

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

Erik Smith
CTO
BluegrassNet Voice
dCAP
Thirdlane Support by BluegrassNet Voice
eeman at bluegrassnetvoice dot com