Project

General

Profile

Community TDMSS7 Network » History » Version 16

manawyrm, 02/19/2022 12:14 AM
typo fix

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 14 laforge
h2. Mailing List
10
11 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/
12 14 laforge
13 1 laforge
h2. Underlying Protocol / Hardware
14
15 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.
16 1 laforge
17
h2. TDM layer hub / cross-connect
18
19
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.
20
21 3 laforge
{{graphviz_link()
22
graph G {
23
  hub [shape=box, label="TDMoIP hub\ncross-connect\nin public internet"];
24
  subgraph cluster_1 {
25 5 tnt
    label="Hobbyist A";
26 3 laforge
    ad1 [label="Access Device\n"];
27
    pbx1 [label="PBX"];
28
    pbx1 -- ad1 [label="E1"];
29
  }
30
  subgraph cluster_2 {
31 5 tnt
    label="Hobbyist B";
32 3 laforge
    ad2 [label="Access Device\n"];
33
    frr [label="FrameRelay Device"];
34
    frr -- ad2 [label="E1"];
35
  }
36
  subgraph cluster_3 {
37 5 tnt
    label="Hobbyist C";
38 3 laforge
    ad3 [label="Access Device\n"];
39
    ras [label="RAS Server"];
40
    ras -- ad3 [label="E1"];
41
  }
42
  ad1 -- hub [label="TDMoIP\nInternet"];
43
  ad2 -- hub [label="TDMoIP\nInternet"];
44
  ad3 -- hub [label="TDMoIP\nInternet"];
45
}
46
}}
47 1 laforge
48
h2. Services
49
50
h3. Classic SS7
51
52
Classic SS7 (MTP2/MTP3 plus TUP/ISUP) would permit to connect STPs and SPCs, such as those of telephony exchanges / switches.
53
54
A user connecting to the SS7 service would need to be allocated point codes.
55
56
57
h3. ISDN PRI
58
59
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.
60
61 16 manawyrm
A user connecting to the ISDN PRI service would need to be allocated telephone numbers in the dialling plan.
62 1 laforge
63
On the hub side, the PRI lines and ISDN service could be terminated in a yate or Freeswitch instance.
64
65 4 laforge
{{graphviz_link()
66
graph G {
67
  hub [shape=box, label="TDMoIP hub\ncross-connect\nin public internet"];
68
  subgraph cluster_1 {
69 5 tnt
    label="Hobbyist A";
70 4 laforge
    ad1 [label="Access Device\n"];
71
    pbx1 [label="PBX"];
72
    phone1a [label="Phone"];
73
    modem1b [label="Modem"];
74
    ta1c [label="ISDN TA"];
75
    pbx1 -- ad1 [label="E1"];
76
    phone1a -- pbx1 [label="POTS"];
77
    modem1b -- pbx1 [label="POTS"];
78
    ta1c -- pbx1 [label="ISDN-BRI"];
79
  }
80
  subgraph cluster_2 {
81 5 tnt
    label="Hobbyist B";
82 4 laforge
    ad2 [label="Access Device\n"];
83
    pbx2 [label="PBX"];
84
    phone2a [label="Phone"];
85
    modem2b [label="Modem"];
86
    ta2c [label="ISDN TA"];
87
    pbx2 -- ad2 [label="E1"];
88
    phone2a -- pbx2 [label="POTS"];
89
    modem2b -- pbx2 [label="POTS"];
90
    ta2c -- pbx2 [label="ISDN-BRI"];
91
  }
92
  subgraph cluster_3 {
93 5 tnt
    label="Hobbyist C";
94 4 laforge
    ad3 [label="Access Device\n"];
95
    pbx3 [label="PBX"];
96
    phone3a [label="Phone"];
97
    modem3b [label="Modem"];
98
    ta3c [label="ISDN TA"];
99
    pbx3 -- ad3 [label="E1"];
100
    phone3a -- pbx3 [label="POTS"];
101
    modem3b -- pbx3 [label="POTS"];
102
    ta3c -- pbx3 [label="ISDN-BRI"];
103
  }
104
  ad1 -- hub [label="TDMoIP\nInternet"];
105
  ad2 -- hub [label="TDMoIP\nInternet"];
106
  ad3 -- hub [label="TDMoIP\nInternet"];
107
}
108
}}
109 1 laforge
110
h3. SCCP/MAP/TCAP
111
112
SCCP/MAP/TCAP on top of SS7 can be used to provide interworking between private cellular networks.
113
114
h3. ISDN BRI
115
116
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.
117
118 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 
119 2 laforge
120
h3. Frame Relay
121
122
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.
123 8 laforge
124
h3. POTS / analog telephony
125
126
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)