View in ref guide.
Edit this option Publish this option Clear draft content
Published Option
Default Value: 1024
Valid Values: Possible values are integers from 1 to 4096 inclusive.
Changes Take Effect: At start/restart
Specifies the number of sockets to be managed per RTP thread. The usage of this parameter is different depending on whether mpc.rtp.fixedsocketthreads is set to 0 or not.
If mpc.rtp.fixedsocketthreds is set to 0:
1 RTP thread is created and initialized at the start. During the run-time, mpc.rtp.socketsperthread denotes the maximum number of sockets that can be handled by 1 thread. When new RTP socket is created and all existing RTP threads have reached the maximum number of sockets, new RTP thread is created to handle the new socket. This entails that specifying a higher number will result in less number of RTP threads being created, and a lower number in more RTP threads.
Otherwise:
For Windows, mpc.rtp.socketsperthread has no effect. For Linux, mpc.rtp.socketsperthread parameter will be used as maxevents argument to the epoll_wait() system call. maxevents affects how many concurrent socket events can be retrieved at the same time. It is recommended that mpc.rtp.socketsperthread be set to the maximum possible number of sockets that will be handled per fixed RTP thread. For example, if MCP will handle maximum of 1000 concurrent calls, there will be a maximum of 4000 RTP sockets open concurrently if both audio and video are used (audio alone will open 2 RTP sockets including RTCP). Assuming mpc.rtp.fixedsocketthreads is set to 8, each RTP thread will handle 500 sockets (4000 / 8). Hence for this example, 500 will be the recommended value for the mpc.rtp.socketsperthread parameter.
Draft Option
No draft option