| Philipp Maier | 6e2795b | 2020-11-26 17:50:01 +0100 | [diff] [blame] | 1 | == MGCP Endpoints |
| 2 | |
| 3 | MGCP organizes the switching resources in so called endpoints. Each endpoint is |
| 4 | referenced by its unique identifier. While RFC 3435 specifies a naming scheme, the |
| 5 | actual identifier naming is subject to the implementation and configuration. |
| 6 | |
| 7 | === RTP proxy / RTP bridge endpoints |
| 8 | |
| 9 | OsmoMGW implements a freely configurable number of `rtpbridge` endpoints. Those |
| 10 | endpoints are able to host two connections at a time to model the functionality |
| 11 | of a tandem switch. |
| 12 | |
| 13 | RTP bridge endpoint identifiers are referenced by the string `rtpbridge/`, a |
| 14 | hexadecimal number without leading zeros and a domain name (configurable). |
| 15 | |
| 16 | ---- |
| 17 | rtpbridge/<number>@<domain> |
| 18 | ---- |
| 19 | |
| 20 | .Example: List of virtual endpoints |
| 21 | ---- |
| 22 | rtpbridge/1@mgw |
| 23 | rtpbridge/2@mgw |
| 24 | rtpbridge/3@mgw |
| 25 | rtpbridge/4@mgw |
| 26 | rtpbridge/5@mgw |
| 27 | rtpbridge/6@mgw |
| 28 | rtpbridge/7@mgw |
| 29 | rtpbridge/8@mgw |
| 30 | rtpbridge/9@mgw |
| 31 | rtpbridge/a@mgw |
| 32 | rtpbridge/b@mgw |
| 33 | rtpbridge/c@mgw |
| 34 | rtpbridge/d@mgw |
| 35 | rtpbridge/e@mgw |
| 36 | rtpbridge/f@mgw |
| 37 | rtpbridge/10@mgw |
| 38 | ---- |
| 39 | |
| 40 | === E1/T1 endpoints |
| 41 | |
| 42 | OsmoMGW supports E1 subslot multiplexing as specified by I.460. All possible |
| 43 | subslot combinations are mapped on individual endpoints. The endpoint names |
| 44 | are prefixed with `ds/e1-` followed by the trunk number and the E1 timeslot. |
| 45 | The subslot is defined by a bit rate and a bit offset. |
| 46 | |
| 47 | ---- |
| 48 | ds/e1-<trunk>/s-<timeslot>/su<bitrate>-<bitoffset>@<domain> |
| 49 | ---- |
| 50 | |
| 51 | .Example: List of endpoints on E1 trunk 0 at E1 timeslot 2 |
| 52 | ---- |
| 53 | ds/e1-0/s-2/su64-0@mgw |
| 54 | ds/e1-0/s-2/su32-0@mgw |
| 55 | ds/e1-0/s-2/su32-4@mgw |
| 56 | ds/e1-0/s-2/su16-0@mgw |
| 57 | ds/e1-0/s-2/su16-2@mgw |
| 58 | ds/e1-0/s-2/su16-4@mgw |
| 59 | ds/e1-0/s-2/su16-6@mgw |
| 60 | ds/e1-0/s-2/su8-0@mgw |
| 61 | ds/e1-0/s-2/su8-1@mgw |
| 62 | ds/e1-0/s-2/su8-2@mgw |
| 63 | ds/e1-0/s-2/su8-3@mgw |
| 64 | ds/e1-0/s-2/su8-4@mgw |
| 65 | ds/e1-0/s-2/su8-5@mgw |
| 66 | ds/e1-0/s-2/su8-6@mgw |
| 67 | ds/e1-0/s-2/su8-7@mgw |
| 68 | ---- |
| 69 | |
| 70 | When creating connections on endpoints that reside in one E1 timeslot the call |
| 71 | agent must make sure that no overlapping endpoints are used. It is for example |
| 72 | not possible to use `ds/e1-0/s-2/su16-2@mgw` and `ds/e1-0/s-2/su8-3@mgw` at the |
| 73 | same time because they overlap. |
| 74 | |
| 75 | .Subslot overlapping |
| 76 | [options="header"] |
| 77 | |=== |
| 78 | | Bit offset 4+| Subslots |
| 79 | | 0 | 8k .2+| 16k .4+| 32k .8+| 64k |
| 80 | | 1 | 8k |
| 81 | | 2 | 8k .2+| 16k |
| 82 | | 3 | 8k |
| 83 | | 4 | 8k .2+| 16k .4+| 32k |
| 84 | | 5 | 8k |
| 85 | | 6 | 8k .2+| 16k |
| 86 | | 7 | 8k |
| 87 | |=== |
| 88 | |
| 89 | NOTE: The current implementation (December 2020) only implements TRAU frame |
| 90 | encoding/decoding for 16K and 8K subslots. Endpoints with other bitrates are |
| 91 | not yet useable. |
| 92 | |
| 93 | NOTE: the VTY command "show mgcp" can be used to get a list of all available |
| 94 | endpoints (including identifiers) |