This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
dexter gerrit-no-reply at lists.osmocom.orgdexter has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-mgw/+/21365 ) Change subject: configuration: add section about E1 trunks ...................................................................... configuration: add section about E1 trunks The cunfiguration chapter does not say anything about E1 trunk configurations, lets add a subsection that explains how an E1 trunk is added. Change-Id: I4059771df0f115242398d1af499c837005a7dabc --- M doc/manuals/chapters/configuration.adoc 1 file changed, 61 insertions(+), 0 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-mgw refs/changes/65/21365/1 diff --git a/doc/manuals/chapters/configuration.adoc b/doc/manuals/chapters/configuration.adoc index 1d273b6..60c3d35 100644 --- a/doc/manuals/chapters/configuration.adoc +++ b/doc/manuals/chapters/configuration.adoc @@ -57,3 +57,64 @@ trunks or a change of the number of available endpoints, require a full restart of osmo-mgw! +=== E1 trunk considerations + +While the RTP bridge trunks are natively based on IP no special considerations +are required during setup. E1 trunks are mapped on a physical E1 line, while +each endpoint is mapped on a physical E1 subslot. + +.Example: E1 line setup +---- +OsmoMGW(config-e1_input)# e1_line 0 driver dahdi <1> +OsmoMGW(config-e1_input)# e1_line 0 port 2 <2> +---- +<1> Name of the libosmo-abis driver implementation ("dahdi") +<2> Port number of the physical E1 port to use (2) + +In osmo-mgw the e1_input node is used to configure the physical E1 line. The +line number will be used internally to identify the configured E1 line. The +port number is the physical E1 connector at the E1 hardware. Per trunk an +individual E1 line will be needed. Beware that the E1 driver may also need +configuration settings that is not discussed here. + +.Example: E1 trunk setup +---- +OsmoMGW(config-mgcp)# trunk 0 <1> +OsmoMGW(config-mgcp-trunk)# line 0 <2> +---- +<1> Creation of a ("dahdi") +<2> Reference to the E1 line to use (0) + +The E1 trunk is created along with a number, typically starting at 0, but if +required any number from 0-64 is allowed. The E1 trunk configuration concerning +the IP related aspects is nearly identical to the configuration of the virtual +trunk. However, it is important that the user assigns one of the E1 line numbers +that were configured under the e1_input node. + +.Example: A typical configuration with one E1 trunk +---- +e1_input + e1_line 0 driver dahdi + e1_line 0 port 2 +mgcp + bind ip 127.0.0.1 + rtp net-range 6000 6011 + rtp net-bind-ip 192.168.100.130 + rtp ip-probing + rtp ip-tos 184 + no rtp keep-alive + bind port 2428 + number endpoints 30 + loop 0 + force-realloc 1 + osmux off + rtp-patch rfc5993hr + trunk 0 + rtp keep-alive once + no rtp keep-alive + line 0 +---- + +NOTE: One E1 trunk always covers a whole E1 line. All subslots will be mapped +to individual MGCP endpoints. As long as the endpoints remain unused the +underlying E1 timeslot is not used. \ No newline at end of file -- To view, visit https://gerrit.osmocom.org/c/osmo-mgw/+/21365 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-mgw Gerrit-Branch: master Gerrit-Change-Id: I4059771df0f115242398d1af499c837005a7dabc Gerrit-Change-Number: 21365 Gerrit-PatchSet: 1 Gerrit-Owner: dexter <pmaier at sysmocom.de> Gerrit-MessageType: newchange -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20201125/6d6e858e/attachment.htm>