Asterisk pjsip configuration: Difference between revisions
(Created page with "== Overview == Asterisk pjsip configuration. == Configuration format == <pre> [ SectionName ] ConfigOption = Value ConfigOption = Value </pre> == Section names == 대부...") |
|||
Line 13: | Line 13: | ||
However, in some cases, (endpoint and aor types) the section name has a relationship to its function. In the case of endpoint and aor their names must match the user portion of the SIP URI in the "from" header for inbound SIP request. The exception to that rule is if you have an identify section configured for that endpoint. In that case the inbound request would be matched by IP instead of against the user in the "From" header. | However, in some cases, (endpoint and aor types) the section name has a relationship to its function. In the case of endpoint and aor their names must match the user portion of the SIP URI in the "from" header for inbound SIP request. The exception to that rule is if you have an identify section configured for that endpoint. In that case the inbound request would be matched by IP instead of against the user in the "From" header. | ||
== Section types == | |||
Below is brief description of each section type and an example showing configuration of that section only. The module providing the configuration object related to the section is listed in parentheses next to each section name. | |||
There are dozens of config options for some of the sections, but the examples below are very minimal for the sake of simplicity. | |||
=== ENDPOINT === | |||
provided by module: res_pjsip | |||
Endpoint configuration provides numerous options relating to core SIP functionality and ties to other sections such as auth, aor and transport. You can't contact an endpoint without associating one or more AoR sections. An endpoint is essentially a profile for the configuration of a SIP endpoint such as a phone or remote server. | |||
<pre> | |||
[6001] | |||
type=endpoint | |||
context=default | |||
disallow=all | |||
allow=ulaw | |||
transport=simpletrans | |||
auth=auth6001 | |||
aors=6001 | |||
</pre> | |||
If you want to define the Caller id this endpoint should use, then add something like the following. | |||
<pre> | |||
trust_id_outbound=yes | |||
callerid=Spaceman Spiff <6001> | |||
</pre> | |||
=== TRANSPORT === | |||
[[category:asterisk]] | [[category:asterisk]] |
Revision as of 23:32, 1 December 2018
Overview
Asterisk pjsip configuration.
Configuration format
[ SectionName ] ConfigOption = Value ConfigOption = Value
Section names
대부분의 경우, 섹션 이름은 아무렇게나 지정할 수 있다. 예를 들어 transport 이름을 [transport-udp-nat] 와 같이 기억하기 쉽게 지정할 수도 있다.
However, in some cases, (endpoint and aor types) the section name has a relationship to its function. In the case of endpoint and aor their names must match the user portion of the SIP URI in the "from" header for inbound SIP request. The exception to that rule is if you have an identify section configured for that endpoint. In that case the inbound request would be matched by IP instead of against the user in the "From" header.
Section types
Below is brief description of each section type and an example showing configuration of that section only. The module providing the configuration object related to the section is listed in parentheses next to each section name.
There are dozens of config options for some of the sections, but the examples below are very minimal for the sake of simplicity.
ENDPOINT
provided by module: res_pjsip
Endpoint configuration provides numerous options relating to core SIP functionality and ties to other sections such as auth, aor and transport. You can't contact an endpoint without associating one or more AoR sections. An endpoint is essentially a profile for the configuration of a SIP endpoint such as a phone or remote server.
[6001] type=endpoint context=default disallow=all allow=ulaw transport=simpletrans auth=auth6001 aors=6001
If you want to define the Caller id this endpoint should use, then add something like the following.
trust_id_outbound=yes callerid=Spaceman Spiff <6001>