Project

General

Profile

Colocated Hub » History » Version 4

laforge, 08/29/2022 04:17 PM

1 2 laforge
{{>toc}}
2
3 1 laforge
h1. Colocated Hub
4
5 4 laforge
This page exists to collect planning about the future colocated OCTOI hub, see #5542
6 2 laforge
7 4 laforge
h2. Rackmount units
8 1 laforge
9 4 laforge
h3. Central Office server (2U / 67cm)
10 1 laforge
11 4 laforge
This is a 2U rack-mount server running all the relevant software.
12 1 laforge
13 4 laforge
See [[AVSt_Server]] for more details of the server
14 1 laforge
15 4 laforge
h4. Connections
16 1 laforge
17 4 laforge
This is a 2U rack-mount server with the following connections:
18
* Power
19
** 2x AC power connections (Redundand PSU)
20
* Ethernet
21
** 1x RJ45 100-Base-TX BMC
22
** 2x RJ45 1000-Base-TX
23
* E1
24
** 8x E1 to a co-located Cisco AS5400 (see below)
25
** 1x E1 to a co-located Livingston PM3 (see below)
26
** 1x E1 to icE1usb/clock-source
27 1 laforge
28
29 4 laforge
h3. icE1usb / E1 clock source (1U / 31cm)
30 1 laforge
31 4 laforge
This is a 1U rack mount system containing:
32
* a PC-Engines APU3 embedded x86_64
33
* an [[e1-t1-adapter:ICE40_E1_USB_interface|icE1usb]] with a custom RS422 interface board
34
* a custom rs422 over voltage protection + 12V injection board
35 1 laforge
36 4 laforge
This icE1usb acts as a GPS-disciplined clock master.  However, as no acutal RF GPS signal is available in the data centre, we are using an Ericsson [[ericsson-rbs-6xxx:GPS_02]] attached via ~100m of RS-422.
37 1 laforge
38 4 laforge
h4. Connections
39 1 laforge
40 4 laforge
* Power
41
** 2x AC power connections (1x APU, 1x RS422/GPS)
42
* Ethernet
43
* RS422
44
** 1x RJ45 towards GPS02 on the roof
45 1 laforge
46
47 4 laforge
h3. Cisco AS5400 RAS Server (2U / 49cm)
48 1 laforge
49 4 laforge
h4. Connections
50 1 laforge
51 4 laforge
* Power
52
** 2x AC power connection (redundant PSU)
53
* Ethernet
54
** 1x RJ45 Ethernet (100-Base-TX) to internal VLAN
55
* E1
56
** 8x E1 (via break-out cable) to AVSt-Server
57
58
59
h3. Livingstion Portmaster 3 (2U / 31cm)
60
61
h4. Connections
62
63
* Power
64
** 1x AC power connection
65
* Ethernet
66
** 1x RJ45 Ethernet (10-Base-TX) [yes, 10MBps]
67
* E1
68
** 1x E1 to AVSt-Server
69
70
71
h2. Roof installation
72
73
74
On the roof of the data centre, the CAT5 cable with RS422 for the GPS03 arrives.
75
76
It will be passed through several DIN rail mounted OVP (Over Voltage Protection) circuits before  connecting to the actual DIN-rail mounted Ericsson GPS03
77
78
The Ericsson GPS03 has a SMA connector, to which a SMA-male to N-Male coaxial cable is attached.
79
80
A Times Microwave LP-GTR-NFF lightning protector (N-female to N-femaile) is used to pass the coaxial cable through the enclosure
81
82
An external GPS antenna with N connector is plugged into the LP-GTR-NFF
83
84
85 2 laforge
86
87 1 laforge
h2. Software
88
89 3 laforge
* Like in the current hub at @laforge's basement, we should run the entire yate / osmo-e1d / dahdi-trunkdev inside a KVM with SRV-IO mapping the PCI devices
90
91
92
h2. Misc / TODO
93
94
h3. local verification with modem/ISDN-TA
95
96
It would be great if we could somehow verify local calls via the yate / hub excluding the complexity of the TDMoIP to compare calls without TDMoIP to calls with TDMoIP.
97
98
Unfortuantely I'm not aware of any really small PBX that would terminate the E1/S2M and offer S0/POTS ports.  Adding antoher 3U for a PBX seems excessive.
99
100 1 laforge
Doing calls between PM3 and ASR5400 is of course an option, but ideally we'd have a real physical modem attached via a serial port, and a real HFC-S-USB for test purpose.
Add picture from clipboard (Maximum size: 48.8 MB)