...
If you already have a Vendor (TILTX or 46 Labs for example) that supports 302 redirect which can return the digital token for insertion into the SIP Header using a 302 redirect response, iterate through the configuration sections below to configure.
302 Redirect Originating IP Information:
Dallas Originating IPs: 108.166.187.49 and 108.166.187.50
Ashburn Originating IPs: 23.167.192.0
If necessary, the platform can be reconfigured to use a signaling IP.
A local 302 Redirect Endpoint server can be spun using your own certificate up by the 46 Labs team if you do not have a vendor that can perform this function.
Please reach out to support@46labs.com for additional information, to change originating IP or in case you have your own endpoint integration.
...
The following fields will be parsed from the token and saved in the CDR Warehouse. The warehouse is also used to generate Reports.
stir_attest | Character. (Max 1) | (STIR Signing Request Component) This value indicates the attestation level. Must be either A, B, or C. (Full, Partial, or Gateway) |
stir_orig_id | Character. (Max. 50) | (STIR Signing Request Component)This value indicates the origination identifier which is a GUID that represents the originating point of a call. For example the switch where the call started or a trunk group. This information is used to help traceback the origin of a call on a trusted network. |
stir_orig_tn | Character. (Max. 50) | (STIR Signing Request Component)
Indicates the calling number or calling Uniform Resource Identifier. |
stir_dest_tn | Character. (Max. 50) | (STIR Signing Request Component)
Indicates the called number(s) or called Uniform Resource Identifier(s). |
stir_iat | Character. (Max. 50) | (STIR Signing Request Component)
Initiated at time (IAT). The time the request is initiated. |
stir_x5u | Character. (Max. 200) | (STIR Signing Request Component)
Indicates the location of the certificate used to sign the token. |