Project

General

Profile

Community TDMSS7 Network » History » Version 17

laforge, 03/07/2022 12:07 PM

1 6 laforge
{{>toc}}
2
3 1 laforge
h1. Community TDM/ISDN/SS7 Network
4
5 13 laforge
This wiki page describes some ideas about a _work in progress_ creating a community TDM/ISDN/SS7 network, enabling retronetworking enthusiasts around the world to interconnect their TDM equipment, such as PBXs, telephony switches, RAS servers, access multiplers, etc.
6 1 laforge
7 2 laforge
For classic analog telephones, there is the C*NET (https://www.ckts.info/).  This is basically the same idea but for one later generation of technology: Digital TDM/PDH/ISDN/SS7 networks.  And of course one can connect analog telephone/modem equipment via ISDN/SS7, if that is desired.
8 1 laforge
9 17 laforge
h2. Currnet Network
10
11
{{graphviz_link()
12
graph G {
13
  newrank=true;
14
  divo [shape=house,label="Central Office\nyate + TE820"];
15
  subgraph cluster_1 {
16
    label="@laforge / Berlin";
17
    uei1a [label="ISDN Phone"];
18
    uea1a [label="Analog Phone"];
19
    ues1a [label="SIP Phone"];
20
    pbx1a [label="Auerswald COMmander\nBasic 2 PBX"];
21
    pm3a [label="Livingston\nPortmaster 3\nRAS Server"];
22
    ice1a [shape=box3d,label="icE1usb\nGPS-DO\nosmo-e1d"];
23
    uei1a -- pbx1a [label="ISDN\nBRI"];
24
    uea1a -- pbx1a [label="POTS"];
25
    pbx1a -- divo [label="ISDN\nPRI"];
26
    pm3a -- divo [label="ISDN\nPRI"];
27
    ice1a -- divo [label="ISDN\nPRI"];
28
    ues1a -- divo [label="SIP"];
29
  }
30
31
  subgraph cluster_2 {
32
    label="@manawyrm / Kiel";
33
    ue2a [label="ISDN Phone\n"];
34
    pbx2 [label="Auerswald COMmander\nBasic 2 PBX"];
35
    ice2 [shape=box3d,label="icE1usb\nGPS-DO\nosmo-e1d\n"];
36
    ue2a -- pbx2 [label="ISDN\nBRI"];
37
    pbx2 -- ice2 [label="ISDN\nPRI"];
38
  }
39
  internet [shape=hexagon,label="Public Internet"];
40
  cnet [shape=hexagon,label="C*NET"];
41
  ice1a -- internet [label="OCTOI\nTDMoIP"];
42
  ice2 -- internet [label="OCTOI\nTDMoIP"];
43
  divo -- cnet [label="IAX2"];
44
}
45
}}
46
47 14 laforge
h2. Mailing List
48
49 15 laforge
We now have a public "mailing list":https://lists.retronetworking.org/postorius/lists/octoi.lists.retronetworking.org/ for discussion among interested parties. The list has a public "archive":https://lists.retronetworking.org/hyperkitty/list/octoi@lists.retronetworking.org/
50 14 laforge
51 1 laforge
h2. Underlying Protocol / Hardware
52
53 12 laforge
The underlying transport protocol is being designed around the wiki page [[e1-t1-adapter:Proposed_efficient_TDMoIP]].  The initial hardware implementation is going to be an [[e1-t1-adapter:icE1usb]] attached to some kind of [embedded] Linux sytem like a Raspberry Pi.  The unique property about the icE1usb is that it contains a GPS-DO to ensure the same clock reference is used in all locations.
54 1 laforge
55
h2. TDM layer hub / cross-connect
56
57
The TDM layer would allow to interconnect any E1 line (or even only some timeslots of a line) with any other E1 line.  It doesn't interpret the payload but just passes it around.
58
59 3 laforge
{{graphviz_link()
60
graph G {
61
  hub [shape=box, label="TDMoIP hub\ncross-connect\nin public internet"];
62
  subgraph cluster_1 {
63 5 tnt
    label="Hobbyist A";
64 3 laforge
    ad1 [label="Access Device\n"];
65
    pbx1 [label="PBX"];
66
    pbx1 -- ad1 [label="E1"];
67
  }
68
  subgraph cluster_2 {
69 5 tnt
    label="Hobbyist B";
70 3 laforge
    ad2 [label="Access Device\n"];
71
    frr [label="FrameRelay Device"];
72
    frr -- ad2 [label="E1"];
73
  }
74
  subgraph cluster_3 {
75 5 tnt
    label="Hobbyist C";
76 3 laforge
    ad3 [label="Access Device\n"];
77
    ras [label="RAS Server"];
78
    ras -- ad3 [label="E1"];
79
  }
80
  ad1 -- hub [label="TDMoIP\nInternet"];
81
  ad2 -- hub [label="TDMoIP\nInternet"];
82
  ad3 -- hub [label="TDMoIP\nInternet"];
83
}
84
}}
85 1 laforge
86
h2. Services
87
88
h3. Classic SS7
89
90
Classic SS7 (MTP2/MTP3 plus TUP/ISUP) would permit to connect STPs and SPCs, such as those of telephony exchanges / switches.
91
92
A user connecting to the SS7 service would need to be allocated point codes.
93
94
95
h3. ISDN PRI
96
97
ISDN (Q.921/Q.931) would permit to connect equipment like PBXs.   The hub offers the NT / central office function, while the client side implements the TE function.
98
99 16 manawyrm
A user connecting to the ISDN PRI service would need to be allocated telephone numbers in the dialling plan.
100 1 laforge
101
On the hub side, the PRI lines and ISDN service could be terminated in a yate or Freeswitch instance.
102
103 4 laforge
{{graphviz_link()
104
graph G {
105
  hub [shape=box, label="TDMoIP hub\ncross-connect\nin public internet"];
106
  subgraph cluster_1 {
107 5 tnt
    label="Hobbyist A";
108 4 laforge
    ad1 [label="Access Device\n"];
109
    pbx1 [label="PBX"];
110
    phone1a [label="Phone"];
111
    modem1b [label="Modem"];
112
    ta1c [label="ISDN TA"];
113
    pbx1 -- ad1 [label="E1"];
114
    phone1a -- pbx1 [label="POTS"];
115
    modem1b -- pbx1 [label="POTS"];
116
    ta1c -- pbx1 [label="ISDN-BRI"];
117
  }
118
  subgraph cluster_2 {
119 5 tnt
    label="Hobbyist B";
120 4 laforge
    ad2 [label="Access Device\n"];
121
    pbx2 [label="PBX"];
122
    phone2a [label="Phone"];
123
    modem2b [label="Modem"];
124
    ta2c [label="ISDN TA"];
125
    pbx2 -- ad2 [label="E1"];
126
    phone2a -- pbx2 [label="POTS"];
127
    modem2b -- pbx2 [label="POTS"];
128
    ta2c -- pbx2 [label="ISDN-BRI"];
129
  }
130
  subgraph cluster_3 {
131 5 tnt
    label="Hobbyist C";
132 4 laforge
    ad3 [label="Access Device\n"];
133
    pbx3 [label="PBX"];
134
    phone3a [label="Phone"];
135
    modem3b [label="Modem"];
136
    ta3c [label="ISDN TA"];
137
    pbx3 -- ad3 [label="E1"];
138
    phone3a -- pbx3 [label="POTS"];
139
    modem3b -- pbx3 [label="POTS"];
140
    ta3c -- pbx3 [label="ISDN-BRI"];
141
  }
142
  ad1 -- hub [label="TDMoIP\nInternet"];
143
  ad2 -- hub [label="TDMoIP\nInternet"];
144
  ad3 -- hub [label="TDMoIP\nInternet"];
145
}
146
}}
147 1 laforge
148
h3. SCCP/MAP/TCAP
149
150
SCCP/MAP/TCAP on top of SS7 can be used to provide interworking between private cellular networks.
151
152
h3. ISDN BRI
153
154
ISDN BRI service is expected to initially only be obtained indirectly: By connecting a ISDN PRI capable PBX to the hub, and then locally connecting to ISDN BRI ports of the PBX.
155
156 11 laforge
At a later point, one could consider implementing a ISDN BRI version of the TDMoIP protocol and some software implementation for ISDN BRI cards that support NT mode.  One notable topic is clocking:  The hardware would either need a GPS-DO (like [[e1-t1-adapter:icE1usb]] has for E1) or at the very least a VCTCXO that can be disciplined by software to match the timing recovered from the IP packet side.  See #5436 and #5417 
157 2 laforge
158
h3. Frame Relay
159
160
A Frame Relay network could be implemented on top of the TDM hub.  In this case, framed E1 would be used with groups of 64k timeslots (typically all 31) building the underlying FR transport medium.
161 8 laforge
162
h3. POTS / analog telephony
163
164
There is no plan to directly support analog telephony.  Rather, analog ports for phones, modems, etc. can be provided by means of ISDN PBXs connecting via ISDN PRI  (and possibly later ISDN BRI)
Add picture from clipboard (Maximum size: 48.8 MB)