This describe the settings to be given to the STUN transport during its creation. Application should initialize this structure by calling pj_stun_sock_cfg_default().
Specify the number of simultaneous asynchronous read operations to be invoked to the ioqueue. Having more than one read operations will increase performance on multiprocessor systems since the application will be able to process more than one incoming packets simultaneously. Default value is 1.
Specify the interface where the socket should be bound to. If the address is zero, socket will be bound to INADDR_ANY. If the address is non-zero, socket will be bound to this address only, and the transport will have only one address alias (the alias_cnt field in pj_stun_sock_info structure. If the port is set to zero, the socket will bind at any port (chosen by the OS).
The group lock to be used by the STUN socket. If NULL, the STUN socket will create one internally.
Specify the STUN keep-alive duration, in seconds. The STUN transport does keep-alive by sending STUN Binding request to the STUN server. If this value is zero, the PJ_STUN_KEEP_ALIVE_SEC value will be used. If the value is negative, it will disable STUN keep-alive.
Packet buffer size.
Default value is PJ_STUN_SOCK_PKT_LEN.
Specify the port range for STUN socket binding, relative to the start port number specified in bound_addr. Note that this setting is only applicable when the start port number is non zero.
Default value is zero.
Specify if STUN socket should ignore any errors when setting the QoS traffic type/parameters.
Set the low level QoS parameters to the transport. This is a lower level operation than setting the qos_type field and may not be supported on all platforms.
By default all settings in this structure are disabled.
QoS traffic type to be set on this transport. When application wants to apply QoS tagging to the transport, it's preferable to set this field rather than qos_param fields since this is more portable.
Default value is PJ_QOS_TYPE_BEST_EFFORT.
The documentation for this struct was generated from the following file: