On Tue, May 26, 2009 at 10:47:52AM +0200, Stefan Sayer wrote: > uh. what does it say? any python exception in the terminal?
It say that the remote methods are not found. >> What are the correct steps needed to use webconference.py app with the >> webconference sems app ? > > in xmlrpc2di.conf you need to set direct_export=webconference so that > the XMLRPC server has the methods from webconference (dialout, roomList > etc) exported directly. Ah! .. ok .. that was the problem, on xmlrpc2di.conf I have direct_export=di ... so thats why it doesn't run, I will change that and retest That let me wonder ... how should I setup xmlrpc2di.conf if I want to control more than one sems app ?, I don't mean more than one webconference instance, I mean click2call + webconference + <whatever> ... could I export more than one DI interface ? and how ? > If you don't change the server name then it uses iptel.org webconference > server by default, so you can try it out. as you have noticed you can > use your own server by setting e.g. CONTROL_URI="http://localhost:8090"; > (note http not https if you haven't set up apache/ssl as proxy) in > webconference.py. I changed the CONTROL_URI to point to my server and without ssl, just for testing. > yes. the credentials together with caller user/callee user/domain are > sent to sems with the dialout() function, and sems uses those to > authenticate with uac_auth. Ok, that's perfect. Best Regards P.D.: I'm on the list, so no need to CC me -- Raul Alexis Betancor Santana Dimension Virtual S.L. _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
