Do you have the port configured explicitly in the Epiphan config gui? Try removing it. Matterhorn is very sensitive to tenancy issues :S
G Kirk Alexander <[email protected]> wrote: >Still having trouble getting our Matterhorn server to recognize the >epiphan box. Maybe >its an apache configuration issue or a matterhorn configuration issue. >Here are some >lines from the vhosts log file that seem to indicate trouble. Thoughts?: > >lgibson.ucdavis.edu:80 169.237.97.209 - - [02/Nov/2011:18:13:55 -0700] "POST >/capture-admin/rest/agents HTTP/1.1" 401 1923 "-" "curl/7.11.0 >(arm-unknown-linux-gnu) libcurl/7.11.0 OpenSSL/0.9.8g zlib/1.2.3" >lgibson.ucdavis.edu:80 169.237.97.209 - - [02/Nov/2011:18:13:55 -0700] "POST >/capture-admin/rest/agents HTTP/1.1" 404 303 "-" "curl/7.11.0 >(arm-unknown-linux-gnu) libcurl/7.11.0 OpenSSL/0.9.8g zlib/1.2.3" > >lgibson.ucdavis.edu:80 169.237.97.209 - - [02/Nov/2011:18:10:39 -0700] "POST >/admin/capture-admin/rest/agents HTTP/1.1" 401 1929 "-" "curl/7.11.0 >(arm-unknown-linux-gnu) libcurl/7.11.0 OpenSSL/0.9.8g zlib/1.2.3" >lgibson.ucdavis.edu:80 169.237.97.209 - - [02/Nov/2011:18:10:39 -0700] "POST >/admin/capture-admin/rest/agents HTTP/1.1" 405 1803 "-" "curl/7.11.0 >(arm-unknown-linux-gnu) libcurl/7.11.0 OpenSSL/0.9.8g zlib/1.2.3" > > >lgibson is the matterhorn host and 169.237.97.209 is the ip of the >epiphan box > > >On 11/2/2011 12:37 PM, Kirk Alexander wrote: >> Does the matterhorn admin server require a port number (8080?) Does >> it need the admin path or just >> http://materhornserver.myschool.edu? >> >> On 11/2/2011 11:15 AM, Jonathan Felder wrote: >>> On the epiphan device click on "Matterhorn". Make sure it is enabled >>> and that the core version matches the version of matterhorn you are >>> using. >>> >>> Under Core URL enter the URL to your matterhorn admin server. >>> >>> The username and password should be what you defined on the server >>> that contains the admin app in >>> /locatation/of/your/matterhorn/install/felix/conf/config.properties >>> under: >>> >>> org.opencastproject.security.digest.user >>> org.opencastproject.security.digest.pass >>> >>> Set the polling interval to whatever works for you keeping in mind >>> that it limits how soon you can schedule recordings. For example a >>> polling interval of 5 means that you shouldn't schedule a recording >>> within 5 minutes of its start time so as to give the agent time to >>> update its schedule. I set it to 1. >>> >>> I set the push interval to 5, I'm not sure the ideal number for this >>> is yet. I left the defaults for the other settings. >>> >>> On 11/2/11 11:07 AM, Kirk Alexander wrote: >>>> I got the device working and doing captures via the web interface but I >>>> don't know how to make it >>>> talk to our Matterhorn server. All we have configured on our server is >>>> the dummy demo_capture_agent >>>> that has mock parameters. Can you tell me how to change the capture >>>> device settings to get the >>>> server to recognize the epiphan over the net? >>>> >>>> On 11/2/2011 10:50 AM, Adam Hochman wrote: >>>>> We're in the same boat Kirk. I've cc'd Greg Logan who had been a >>>>> consultant with Epiphan to get Matterhorn working with their device. >>>>> He will release the latest firmware likely by eod today which should >>>>> fix the device as it currently does not capture. It will work with >>>>> Matterhorn 1.2+. He hasn't really tested the limits of the device yet, >>>>> but has found the following configuration to work: >>>>> 2Mbit for 1024x768 on the VGA, 600kbit for 720x480 on the S-video cam >>>>> (H264), 30 fps video (at 10 Mbit it starts dropping frames. he has >>>>> tested with 15 fps more extensively. vga likely only needs 5fps for >>>>> slides) , and PCM for the audio (mp3 too intensive). >>>>> >>>>> The device has generally 32 GB of storage and it has no storage >>>>> management, so it is possible that the device will fail to record if >>>>> it backlogs too many recordings. Once a recording is successfully >>>>> ingested it is deleted from the CA. Epiphan provides a live stream for >>>>> confidence monitoring so you can theoretically capture it as a backup >>>>> measure, but this hasn't been implemented. They should re-enable file >>>>> download via the epiphan UI shortly so folks can download orphan >>>>> recordings. >>>>> >>>>> The documentation is non-existent but Epiphan will hire Greg to >>>>> provide docs, etc. to move the product out of beta. If you have any >>>>> additional questions, it would be great if you can cc list so everyone >>>>> can benefit from Greg's answers :) Jonathan Felder, our local sys >>>>> guru, is also cc'd on this email. He has had some experience with the >>>>> epiphan and may be able to help. Locally we ran into the bug where it >>>>> communicated that is was capturing but it really wasn't. This will be >>>>> addressed in Greg's fix. >>>>> >>>>> On 11/1/11 9:24 PM, Kirk Alexander wrote: >>>>>> Hi, >>>>>> We just got one of the Epiphan Opencast boxes. I ran it through some >>>>>> basic testes >>>>>> and it seems to be functioning ok. But it came with NO documentation >>>>>> and I am having >>>>>> a hard time finding the explicit configurations for >>>>>> Matterhorn/OpenCast for this box. >>>>>> Does one use the same settings as VGA2USB or is there one explicitly >>>>>> for the >>>>>> Opencast box? Any help/pointers you can provide would be welcome! The >>>>>> lists >>>>>> didn't give me all that seems to be needed when I went a-googling. >>>>>> Kirk >>>>>> -- >>>>>> >>>>>> Kirk Alexander >>>>>> SmartSite Program Manager, >>>>>> IET-Academic Technology Services; >>>>>> Technology Lead, >>>>>> UC Online Education Initiative >>>>>> Tel: 530-752-2133 >>>>>> Fax: 530-752-4655 >>>>>> [email protected] <mailto:[email protected]> >>>>>> >>>> >> > > _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
