FAD Fedora Talk 2009 game plan

From FedoraProject

Revision as of 15:50, 24 October 2009 by Pfrields (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Note.png
Page description
This page is to lay out and plan the specifics the work we will complete at the FAD. The FAD Fedora Talk 2009 page explains the original goals and planning done for this event.

Contents

Participants

Note.png
Travel days
Travel days are Thursday and Sunday. On-site participants are leaving early and no on-site hacking will take place on Sunday.
Name Remote? Fri Sat Sun Core Tasks
John X X Travel Project Management + Documentation + Requirements
Paul X X Hosting, chauffeuring, hacking when no one's looking
Ian X X Travel Web page/app creation and hacking, design and misc. hackery
Jon X X Travel Testing, puppetizing, general hacking, learn Asterisk, moral support, etc :D
Jared X X Be the Asterisk guru + Bring lots of VoIP equipment + Documentation
Jeff X X Travel Asterisk hacking
Mike X puppetizing and testing
Clint X X X X puppetizing and testing (shadowing Mike)
Darren X .5 X testing
Bruno X X X AM testing, possibly some asterisk config hacking

Schedule

Thursday, 2009-10-22
Time (EDT) Details
1500 Paul picks up Jon Stanley from bus station
1515 Paul and Jon trip to store to pick up a couple small hardware bits
1700 Paul and Jon to either hotel or Paul's house
2000 Paul (maybe Jon) to RIC airport to pick up arriving travelers
2300 (approximate) Travelers to hotel, Ian to Paul's house
Friday, 2009-10-23
0800 Paul picks up travelers at hotel for breakfast (Waffle House Cracker Barrel [loc. #1])
0930 Arrive at work site, greet owner, set up
1000 Sessions start
1800 Wrap up/depart for dinner (possible late-night hacking?)
Saturday, 2009-10-24
0930 Paul picks up travelers at hotel
1000 Sessions start
1800 Wrap up/depart for dinner
Sunday, 2009-10-25
0830 Paul picks up travelers at hotel
0900 Drop off Jon Stanley at bus terminal, depart for RIC airport
1015 Drop off travelers for flights (Ian ~1130, Jeff ~1210), then to Richmond/SM bus terminal (Poelstra)

Use Cases

Explanations and proposed usage of different FedoraTalk functionality

Asterisk Packages & Installation Instructions

I think this is ready for review by the gurus as I have gone about as far as I can. I am able to complete twinkle to twinkle calls through the server.

  • Base system should be F12
  • wget http://kojipkgs.fedoraproject.org/packages/asterisk/1.6.2.0/0.6.rc3.fc13/i686/asterisk-1.6.2.0-0.6.rc3.fc13.i686.rpm for i686 systems.
  • yum install --nogpgcheck asterisk-1.6.2.0-0.6.rc3.fc13.i686.rpm asterisk-sounds-core-en-wav
    • This will pull in some other packages, including tex stuff (presumably for documentation).
    • I think we can use the F12 asterisk-sounds-core until there is an F13 version available, but I haven't got that far in my testing.
    • I am not sure which codecs we need and what issues installing multiple languages causes.
  • git clone git://fedorapeople.org/~jcollie/ftalk-asterisk-configs.git ftalk-asterisk-configs
  • cp -f ftalk-asterisk-configs/* /etc/asterisk
  • chown asterisk.asterisk /etc/asterisk/*
    • There are a couple of config files in Jeff's set that are new and get owned by root instead of asterisk. Depending on your umask setting this might be a problem.
  • A line "type = peer" should get added into the [general] section of /etc/asterisk/users.conf . Without this registration as one of the users won't work.
  • If you want to test connecting with a sip client you can edit /etc/asterisk/users.conf to replace the modified md5secret with a correct md5secret or just secret.
  • /etc/asterisk/sip.conf has a fixed ip address in several commands. If you comment them out (with ;) asterisk will listen on all interfaces (0.0.0.0).
  • /etc/asterisk/asterisk.conf has a [directories] section that causes problems for sip. Probably something needed by sip is in a missing directory. Since we are keeping stuff in the standard places, this can just be commented out by adding (!) to the end of the line. So it should look like: [directories](!)
  • Open ports 5060/udp 5060/tcp for inbound SIP. Allowing related connections should take care of RTP.
    • The way things are configured, only udp is being used for 5060. Unless that changes 5060/tcp doesn't need to be opened up.
    • For example if you aren't using a firewall tool you can add the following to /etc/sysconfig/iptables and service iptables restart:
      • -A INPUT -m state --state NEW -m tcp -p tcp --dport 5060 -j ACCEPT
      • -A INPUT -m state --state NEW -m udp -p udp --dport 5060 -j ACCEPT
  • Open port 4569/udp for iax2, if we play with that.
  • chkconfig asterisk on
  • service asterisk restart
  • asterisk -r
    • If you want to do some debugging you can run asterisk -r as root or asterisk.
    • "core show help" will show you what commands are available.
    • "sip set debug on" is one that might be particularly useful.
  • Note with this setup authentication (domain and realm in twinkle) uses fedoraproject.org but for the server setup and host being called you want to use the real domain name of the server.
  • If you edit system settings -> Network you can change the sip port and run an instance of twinkle on the same box as the server.

Targeted Trac Tickets

  • Primary targets:
    • #309 -- Asterisk recording
    • #395 -- Audio streaming of Fedora Board conf-calls
    • #453 -- Asterisk/gstreamer solution for town hall meetings
    • #1160 -- streaming and recording moderated conf-calls
  • Secondary targets (as time allows):