Search results

Jump to: navigation, search
  • * ip_transport: Optional SIP transport to use (udp, tcp, tls). : TCP/TLS: Optional local ip to use when connecting
    8 KB (1,225 words) - 10:07, 6 July 2018
  • TLS and SRTP in Yate
    8 KB (1,083 words) - 11:49, 27 October 2017
  • * ip_transport: Optional SIP transport to use (UDP, TCP, TLS). ::- TCP/TLS: Optional local ip/port to bind on when connecting
    3 KB (422 words) - 08:08, 23 November 2017
  • SSL/TLS sockets provider using the [http://www.openssl.org/ OpenSSL] library
    12 KB (1,662 words) - 13:25, 1 October 2019
  • param['ip_transport'] = 'TLS' param['ip_transport'] = 'TLS'
    16 KB (1,017 words) - 16:12, 15 December 2017
  • ...ich network interfaces to listen. Yate supports 3 types of listeners: TCP, TLS, UDP. ; tls: Build a TLS listener (encrypted TCP)
    25 KB (3,811 words) - 10:09, 6 July 2018
  • ... for incoming connections.<br>This parameter is used when inband security (TLS) is negociated on an incoming connection.<br>If not set the connection will ... If a transport is set port will default to 3868 for sctp/tcp and 5658 for tls.
    43 KB (6,355 words) - 13:27, 1 October 2019
  • * When a SIPS URI is used to send a request transport defaults to TLS unless explicitly set to another value (UDP/TCP). A line can be configured to register using a SIPS URI on non TLS transport.<br>
    1 KB (245 words) - 10:35, 6 July 2018

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Personal tools
Namespaces

Variants
Views
Actions
Preface
Configuration
Administrators
Developers