Difference between revisions of "Telephone System"

From Hackerspace ACKspace
Jump to: navigation, search
m (future)
(archived CCC, put in open day info)
Line 15: Line 15:
  
 
== implementation ==
 
== implementation ==
First, I'm trying to revive my current FS box for usage on the CCC camp, make sure the set up has the following:
+
For the open day, I'm setting up a stand-alone test system with two Cisco 7940s, a FxS/FxO and dual FxS ATA, and any softclient that is willing to participate.
* At least three extensions: editor, fieldreporter hd audio and studio
+
The Cisco phones will have a menu where you can view a 2 bit grayscale snapshot of the two space cams, and you'll be able to switch some outlets.
* one or more sip trunks to [http://eventphone.de/ EventPhone]
+
People are allowed to navigate the configs and exploit functionality. [[User:LuckY|LuckY]] already mentioned he wants to sniff and replay audio, so I'll try and set up a working access point for it.
* visual ring/in-use indicator
 
* calling queue, optionally w/ IVR and direct forward (field reporter)
 
  
 
=== todo ===
 
=== todo ===
Line 39: Line 37:
 
* 94214: xopr cell
 
* 94214: xopr cell
 
* 4891: [[User:Vicarious|Vicarious]]
 
* 4891: [[User:Vicarious|Vicarious]]
 +
 +
== history ==
 +
The CCC Binary Voice Radio telephony server was a mixed success.
 +
Actually, it was a disaster:
 +
-The visual ring indicator circuit didn't trigger the optocouplers so that was the first thing to fail.
 +
-a lot of power failures which caused a lot of downtime and eventually database corruption
 +
-the DECT system was getting too complex for the simple phones we've modded for field reporting (Technical clarification came from one of the Eventphone key people who explained that the antenna register on cheap phones was too small to identify them all).  Besides that, it looked like the cabling had short-circuited because the 9v battery didn't have any oomph left to generate amplified audio.
 +
-wifi had a hard time maintaining the links and coverage wasn't 100% so the wifi field reporter wasn't a good alternative
 +
-last but not least: the public ip addressing threw a spanner in the works and the server went limbo.
 +
The server's database went corrupt, and after a restore, it didn't match the regular config files. I got it semi-working after it was far too late to make it useful to the studio.
 +
Also, after I got it to work, it wouldn't register correctly to the Eventphone trunk and we only got to call the editorial room (2781|BVR1) via DECT twice or so.
 +
Despite all that stress, it was promising, so better luck next time.
  
 
== future ==
 
== future ==

Revision as of 17:53, 17 November 2011

Project: Telephone System
Featured:
State Active
Members xopr
GitHub No GitHub project defined. Add your project here.
Description Telephone Communication System
Picture
No project picture! Fill in form Picture or Upload a jpeg here

synopsis

Create and/or implement a telephone communication system for companies to communicate with the front desk or vice versa, for notifications, emergency and-or quick automation.

This idea was mentioned before: not only can we be informed there is a pizza delivery boy at the desk, but also other companies can benefit from a telephone/intercom system.

The cheapest setup would be SIP/RTP (VoIP); make use of the current network infrastructure. I happen to have a system with FreeSWITCH running, but it's currently in experimental mode.

Be aware that FS has a very steep learning curve, but once you get the point, you'll never want to go back (hint: regular expressions ftw)

implementation

For the open day, I'm setting up a stand-alone test system with two Cisco 7940s, a FxS/FxO and dual FxS ATA, and any softclient that is willing to participate. The Cisco phones will have a menu where you can view a 2 bit grayscale snapshot of the two space cams, and you'll be able to switch some outlets. People are allowed to navigate the configs and exploit functionality. LuckY already mentioned he wants to sniff and replay audio, so I'll try and set up a working access point for it.

todo

  • register extensions at eventphone (done)
    • reserved numbers 2871 (BVR1), 2872 (BVR2) (spelled: Binary Voice Radio)
  • (backup and) install a fresh freeswitch/FusionPBX
  • create extensions
  • backup again, for

notes

Noticeable telephone numbers:

  • 4865: SvenR
  • 2779: PsychiC (2PSY)
  • 4214: xopr
  • 5225: socialhack/Binary Voice
  • 5636: gmc
  • 6510: Ranzbak/deFEEST
  • 6581: JinX/deFEEST
  • 94214: xopr cell
  • 4891: Vicarious

history

The CCC Binary Voice Radio telephony server was a mixed success. Actually, it was a disaster: -The visual ring indicator circuit didn't trigger the optocouplers so that was the first thing to fail. -a lot of power failures which caused a lot of downtime and eventually database corruption -the DECT system was getting too complex for the simple phones we've modded for field reporting (Technical clarification came from one of the Eventphone key people who explained that the antenna register on cheap phones was too small to identify them all). Besides that, it looked like the cabling had short-circuited because the 9v battery didn't have any oomph left to generate amplified audio. -wifi had a hard time maintaining the links and coverage wasn't 100% so the wifi field reporter wasn't a good alternative -last but not least: the public ip addressing threw a spanner in the works and the server went limbo. The server's database went corrupt, and after a restore, it didn't match the regular config files. I got it semi-working after it was far too late to make it useful to the studio. Also, after I got it to work, it wouldn't register correctly to the Eventphone trunk and we only got to call the editorial room (2781|BVR1) via DECT twice or so. Despite all that stress, it was promising, so better luck next time.

future

Set up a FS/FusionPBX virtual machine for ACKspacers to play with.


Once it works, I would like to have the internal phone number 1984..

or 0118 999 881 999 119 7253

-- Vicarious