res_stir_shaken: Add stir_shaken option and general improvements.

Added a new configuration option for PJSIP endpoints - stir_shaken. If
set to yes, then STIR/SHAKEN support will be added to inbound and
outbound INVITEs. The default is no. Alembic has been updated to include
this option.

Previously the dialplan function was not trimming the whitespace from
the parameters it recieved. Now it does.

Also added a conditional that, when TEST_FRAMEWORK is enabled, the
timestamp in the identity header will be overlooked. This is just for
testing, since the testsuite will rely on a SIPp scenario with a preset
identity header to trigger the MISMATCH result.

Change-Id: I43d67f1489b8c1c5729ed3ca8d71e35ddf438df1
This commit is contained in:
Ben Ford
2020-06-24 11:49:11 -05:00
committed by George Joseph
parent d979bdf87a
commit 21ab0a450b
9 changed files with 127 additions and 14 deletions

View File

@@ -0,0 +1,20 @@
Subject: STIR/SHAKEN
STIR/SHAKEN support has been added to Asterisk. Configuration is done in
stir_shaken.conf. There is a sample configuration file to help you get
started (asterisk/configs/samples/stir_shaken.conf.sample). Once that's
set up, you can enable STIR/SHAKEN on any endpoint by setting stir_shaken
to yes on the endpoint configuration object. This will add an Identity
header on outgoing INVITEs, and check for an Identity header on incoming
INVITEs. This option has been added to Alembic as well.
The information received on an incoming INVITE can be checked using the
STIR_SHAKEN dialplan function. There are two variations:
STIR_SHAKEN(count)
STIR_SHAKEN(0, verify_result)
The first variation will tell you how many STIR/SHAKEN results are on the
channel. The second fetches information for a specific result. The first
parameter is the index, followed by what information you want to retrieve.
The available options are 'verify_result', 'identity', and 'attestation'.