- Sentinel 100
- Sentinel 400
- Mediatrix S7 and S7 LP Series
- Mediatrix G7 Series
- Mediatrix C7 Series
- Mediatrix 4100 Series
- Mediatrix 3000 Series
- Mediatrix 4400 Series
- Mediatrix LP Series
In the scope of this document and Mediatrix products in general, a "SIP gateway" is a software entity of the DGW application that ties the SIP communications to different network interfaces and listening ports. Not to be confused with a "VoIP gateway" which usually represents the whole gateway device.
A SIP gateway can be used to:
There are two types of SIP gateways: trunk gateway and endpoint gateway. For more details on their difference, refer to Trunk Gateway vs Endpoint Gateway
|Trunk Gateways||Endpoint Gateways|
|Operates like a traditional SIP gateway||Operation is inspired from the IMS (IP Multimedia Subsystem) model.|
|No concept of being connected to a SIP server at the SIP level.||
|Supports all types of telephony lines: FXO, FXS, ISDN, PRI, E1, ...||Supports only FXS.|
|Accepts incoming SIP requests from peers on a listening port.||The gateway has no listening port. It accepts incoming SIP requests only from the server on which it is registered.|
|When the destination is an FQDN, each SIP transaction is possibly sent to a different IP address, depending on the DNS query result. The gateway assumes that all SIP servers identified by a single FQDN have a synchronised state.||The Endpoint Gateway is designed to operate with a destination specified by an
The addresses obtained from the DNS resolution of this FQDN are used as potential “SIP connection” addresses, in ordered priorities. The endpoint gateway first attempts to register to the highest priority server. If the SIP connection (registration) fails, the next priority server is tried, and so on. A failback scheme periodically attempts to switch to the server with the highest priority available.
Failover/fallback to another server requires the SIP user to register on that server prior to establishing SIP communication.
|Supports UDP, TCP, and TLS transport:
||Supports UDP transport only.
Separate persistent connections are established for each user. Persistent connections are emulated over the UDP transport.
|SIP dialogs are established independently of each other (in some conditions, the selection of the destination server may depend on the keep alive parameters configured under SIP/Servers).||SIP dialogs for a given SIP user can only be established once the user is registered to the server.|
|The call router shows a single SIP source/destination for the gateway.||The call router and gateway status tables show an instance of the gateway for each user of the gateway.|
|Supports endpoint, gateway, user, and unit registrations.||Supports endpoint registrations only.|
The total number of registrations is the sum of all the endpoint and gateway pairs.
For most Mediatrix devices, the total number of registrations is limited to 64. However, for the Mediatrix G7 Series, the Mediatrix S7 Series, the Mediatrix 3000 Series, the Sentinel 400, and the Sentinel 100, the limit is 500. If a custom DGW profile is used, the limit can be different depending on what value was defined in the profile. For example, when using a Sentinel 400, up to 500 registrations are possible, but if the profile specifies 200, then the unit will only be able to manage up to 200 registrations.
The Mediatrix unit supports a maximum of 5 gateways. An endpoint configured with All gateways generates as many registrations as the number of gateways. In a setup with 3 gateways, one endpoint configured with All as the gateway name counts for 3 in the total number of registrations. The registrations are enabled gateway by gateway until the limit is reached. Endpoint registrations are used first, then unit registrations. The remaining registrations are not registered and do not appear in the Status table. If the number of registrations exceeds the defined limit, a warning is displayed on the Web interface (as well as in the CLI and SNMP interfaces) and a syslog notify (Level Error) is sent. Adding a gateway or an endpoint triggers a warning message if the total number of registrations configured reached the defined limit
The LAN interface may be used by a SIP gateway to be bound on the LAN. However, there is no routing between the LAN and the Uplink interface.
You can choose to enable realm validation, but this is not mandatory.
All SIP gateway parameters are configurable via the DGW Web Interface.
Mediatrix units are supplied with an exhaustive set of documentation.
Mediatrix user documentation is available on the Documentation Portal .
Several types of documents were created to clearly present the information you are looking for. Our documentation includes:
Copyright © 2018 Media5 Corporation.
This document contains information that is proprietary to Media5 Corporation.
Media5 Corporation reserves all rights to this document as well as to the Intellectual Property of the document and the technology and know-how that it includes and represents.
This publication cannot be reproduced, neither in whole nor in part, in any form whatsoever, without written prior approval by Media5 Corporation.
Media5 Corporation reserves the right to revise this publication and make changes at any time and without the obligation to notify any person and/or entity of such revisions and/or changes.