Примеры использования Media proxy на Английском языке и их переводы на Русский язык
{-}
-
Official
-
Colloquial
Media Proxy is not built for these endpoints.
The FTP Module uses the TCP Media Proxy ports for Passive Mode transfers.
Media Proxy is always built for these endpoints.
If this parameter exists, a Media Proxy is always created for an outgoing call.
A Media Proxy is created to relay traffic between an IPv4 and IPv6 entries.
Bug Fix: DIALOG: 6.1c:in some call scenarios media proxy might be not properly initialized.
The Media Proxy component records in the System Log are marked with the MEDIAPROXY tag.
When this option is selected,TCP ports are explicitly allocated for TCP media proxy and FTP data channels only.
Bug Fix: SIGNAL:6.2c2: media proxy might be incorrectly collapsed in some call scenarios.
The Media Server supports clients connecting from remote NATed networks,using the same algorithms as those employed with the Media Proxy component.
A Media Proxy is created to serve entries(users) located behind remote NAT devices.
Use this setting to specify what kind of information the Media Proxy component should put in the Server Log.
Media Proxy is built for these endpoints if their visible Network IP Address is included into the NAT Server IP Addresses list.
It forces the client to connect to that Media Proxy instead of the remote system media port.
The Media Proxy relays media data between the"LAN leg" and the"WAN leg" of the media connection.
When a client on the LAN tries to communicate with a remote system on the Internet(WAN),CommuniGate Pro creates a Media Proxy- a communication port on its own system.
The CommuniGate Pro Media Proxy communicates with the remote system itself, relaying the data received from the LAN client to the remote system and vice versa.
The CommuniGate Pro Server solves this problem by automatically creating Media Proxies and instructing endpoints to send media data to that Media Proxy for relaying.
Note: If you need the Media Proxy functionality, make sure that the LAN and NAT data is specified correctly on the LAN IPs and NAT WebAdmin settings pages.
When two endpoints are located behind the same far-end NAT(i.e. when their visible,external Network IP Addresses are the same), this option specifies if a Media Proxy should be built to relay media between these endpoints.
Disable the Use for Media Proxy only option to make the CommuniGate Pro Server software use the selected port range for all outgoing TCP connections with a predefined source address.
Each Media stream terminated in CommuniGate Pro(a stream relayed with a media proxy or a stream processed with a media server channel) is bound to a particular Cluster Member.
A Media Proxy can create zero, one or several stream proxies for each media stream(for example, one stream proxy for the audio stream, and one- for the video stream).
Each frontend hasits own IP address, and when a Media Channel or a Media Proxy is created on that frontend Server, this unique IP address is used for direct communication between the Server and the client device or remote server.
If there is no signal sent within a Call for the specified period of time, and, if a Media Proxy is associated with that Call, there no media data to relay for the specified period of time, a call termination(BYE) request is sent to both sides of the call, and the Call object is removed.
The time-out mechanism is used to remove"abandoned" Media Proxies.
The ports used for Media Proxies and active FTP data connections are always allocated by the CommuniGate Pro Server itself.
Media Proxies are created with the SIP and XIMSS components when a call is being sent to a remote entity.
In this case,the CommuniGate Pro SIP module builds and manages media proxies, relaying not only the SIP protocol requests and responses, but the media data, too.
The SIP module can detect much more complex loop cases, either avoiding Media Proxies altogether, or minimizing the number of Media Proxies used.