-
...n accfile so Yate will register to it. Then set Yate Server with Jingle in client mode.
==Load Jabber client module ==
2 KB (343 words) - 09:20, 4 November 2013
-
This module allows controlling Yate using a simple telnet client.
For Windows clients no simple free connection solution exists. The commercial (with 30 days tr
7 KB (1,041 words) - 13:24, 4 June 2014
-
* from telnet client ([[Rmanager]] module is required).
...e that can be accessed with a [http://en.wikipedia.org/wiki/Telnet telnet] client program (needs the [[rmanager]] module)
6 KB (819 words) - 14:08, 16 August 2023
-
:*accounts: bool: Activate client registrations on "user.notify" and "engine.timer". Defaults to no
* control which Caller ID uses SIP client and change it to allowed from predefined range;
14 KB (2,155 words) - 10:47, 11 January 2014
-
==Yate configuration as Server and / or Client==
Various configuration for Yate to act as a Server and as a Client using different protocols.
9 KB (1,376 words) - 10:01, 27 October 2017
-
...h authentication between Yate and a server(gateway). Yate Server will be a client for that server(gateway). The connection information will be configured in
8 KB (1,225 words) - 10:07, 6 July 2018
-
To use it in client mode disable parameter '''servermode''' from [general] section.
...e clients can be SIP, IAX, Jabber or H323 for one side and Jingle or other clients for the other side. In those cases the mapping of the called number must b
9 KB (1,391 words) - 09:14, 4 November 2013
-
* [[SIP_Client|SIP Client]].
...u can see in the image below and also you can configure Yate to be a [[SIP Client]].
8 KB (1,261 words) - 08:43, 4 November 2013
-
* [[SIP Client]]
Implementation and SIP Client features in Yate
8 KB (1,083 words) - 11:49, 27 October 2017
-
; Perform direct RTP forwarding between client endpoints.
; is also supported and enabled on all clients.
13 KB (1,916 words) - 09:08, 4 November 2013
-
* '''response'''=''Digest (MD5) response computed by client''
2 KB (250 words) - 21:15, 13 March 2014
-
The '''user.notify''' message is emitted by channels that support client registration to other servers. It is generated asynchronously every time th
888 B (114 words) - 11:00, 21 January 2013
-
It can be used for any kind of SIP application: client server or proxy.
263 B (48 words) - 11:05, 13 December 2012
-
... is emitted by an authentication token - providing module (e.g. accfile or client). The message is targeted towards channel-providing modules (e.g. h323chan
1,015 B (144 words) - 10:59, 21 January 2013
-
The textual return value is displayed either to the requesting remote client or to the logging output (for commands placed on the command line). The lin
1 KB (183 words) - 15:56, 18 January 2013
-
: drillhole=disable in server mode, enable in client mode
: maxjitter=120 in client mode, 0 in server mode
6 KB (870 words) - 14:12, 10 January 2014
-
* use YateClient as an H.323 client;
== Testing YateClient as H.323 client==
12 KB (2,088 words) - 15:15, 31 October 2013
-
Configuring Yate to act as a SIP Server and YateClient to act as a SIP Client.
* use Yate Client as an SIP client;
2 KB (381 words) - 15:16, 31 October 2013
-
Yate can be used as IAX Server and YateClient as IAX Client. This configuration will be done on platforms that have Mandriva 2010 sprin
* to be able to configure YateClient as an IAX client.
12 KB (1,986 words) - 15:13, 31 October 2013
-
... line with all his available options when starting Yate as server and Yate Client.
==Starting Yate as Client on Windows==
5 KB (770 words) - 08:44, 7 August 2013
