Asterisk taskprocessor: Difference between revisions

From 탱이의 잡동사니
Jump to navigation Jump to search
Line 25: Line 25:
=== pjsip/session/<endpoint> ===
=== pjsip/session/<endpoint> ===
Task processor created by res_pjsip_session.so to handle incoming and outgoing sessions and their associated dialog messages. Asterisk v13.10.0 renamed the task processors for outgoing sessions to pjsip/outsess/<endpoint>. The task processors for incoming sessions were eliminated to continue using the pjsip/distributor task processor the initial INVITE came in on.
Task processor created by res_pjsip_session.so to handle incoming and outgoing sessions and their associated dialog messages. Asterisk v13.10.0 renamed the task processors for outgoing sessions to pjsip/outsess/<endpoint>. The task processors for incoming sessions were eliminated to continue using the pjsip/distributor task processor the initial INVITE came in on.
=== pjsip/outsess/<endpoint ===
Task processor created by res_pjsip_session.so to handle messages


== Reference ==
== Reference ==

Revision as of 12:32, 2 July 2019

Overview

Asterisk taskprocessor 내용 정리.

Basic

Asterisk 에서는 여러 처리작업을 수행하기 위해 task processor 라는 내부 thread 를 이용하는데, 각각의 이름마다 하는 역할이 정해져 있다.

Task processors

pjsip/aor/<aor-name>

Task processor created by res_pjsip_registrar.so for incoming endpoint registrations. Asterisk v13.10.0 eliminated these task processors to continue using the pjsip/distributor task processor the REGISTER request came in on.

pjsip/default

Task processor created by res_pjsip.so. Miscellaneous PJSIP tasks that don't have any other association. Theses task processors are assigned tasks in a round robin sequence.

Before Asterisk v13.10.0 these task processors also handled the initial PJSIP message distribution if the message was not associated with any other task processor.

pjsip/distributor

Task processor created by res_pjsip.so. PJSIP distributor incoming messages to these task processors if the message is not associated with any other task processor. The task processor assignment is determined by hashing the SIP rquest's Call-ID and from tag. These task processors are new since Asterisk v13.10.0.

pjsip/messaging

Task processor created by res_pjsip_messaging.so to send all out-of-dialog MESSAGE requests for PJSIP.

pjsip/outreg/<endpoint>

Task processor created by res_pjsip_outbound_registration.so to handle the endpoint's outbound registration message.

pjsip/session/<endpoint>

Task processor created by res_pjsip_session.so to handle incoming and outgoing sessions and their associated dialog messages. Asterisk v13.10.0 renamed the task processors for outgoing sessions to pjsip/outsess/<endpoint>. The task processors for incoming sessions were eliminated to continue using the pjsip/distributor task processor the initial INVITE came in on.

pjsip/outsess/<endpoint

Task processor created by res_pjsip_session.so to handle messages

Reference