diff options
| author | Richard Mudgett <rmudgett@digium.com> | 2017-12-22 19:50:34 -0600 |
|---|---|---|
| committer | Richard Mudgett <rmudgett@digium.com> | 2018-01-16 12:50:34 -0600 |
| commit | 8494e78010d8917a4165d877045be34ddc2dda22 (patch) | |
| tree | b1ecd89e12d5925258d337e67e966164b044f99c /res/res_pjsip.c | |
| parent | 2f392bedb3987ee3c587bd8b046299320b84d5c5 (diff) | |
res_pjsip: Split type=identify to IP address and SIP header matching priorities
The type=identify endpoint identification method can match by IP address
and by SIP header. However, the SIP header matching has limited
usefulness because you cannot specify the SIP header matching priority
relative to the IP address matching. All the matching happens at the same
priority and the order of evaluating the identify sections is
indeterminate. e.g., If you had two type=identify sections where one
matches by IP address for endpoint alice and the other matches by SIP
header for endpoint bob then you couldn't predict which endpoint is
matched when a request comes in that matches both.
* Extract the SIP header matching criteria into its own "header" endpoint
identification method so the user can specify the relative priority of the
SIP header and the IP address matching criteria in the global
endpoint_identifier_order option. The "ip" endpoint identification method
now only matches by IP address.
ASTERISK-27491
Change-Id: I9df142a575b7e1e3471b7cda5d3ea156cef08095
Diffstat (limited to 'res/res_pjsip.c')
| -rw-r--r-- | res/res_pjsip.c | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/res/res_pjsip.c b/res/res_pjsip.c index 3f9574d2a..07fc980ef 100644 --- a/res/res_pjsip.c +++ b/res/res_pjsip.c @@ -323,6 +323,17 @@ endpoint identification. </para> </enum> + <enum name="header"> + <para>Matches the endpoint based on a configured SIP header + value. + </para> + <para>This method of identification is not configured here + but simply allowed by this configuration option. See the + documentation for the <literal>identify</literal> + configuration section for more details on this method of + endpoint identification. + </para> + </enum> </enumlist> </description> </configOption> |