STIR/SHAKEN#

DIDWW supports STIR/SHAKEN for outbound call termination via Outbound SIP Trunks. This includes default DIDWW attestation and an optional mode to relay a customer-generated SIP Identity header.


Default DIDWW Attestation#

By default, DIDWW applies STIR/SHAKEN attestation to outbound calls.

When a call is sent through a DIDWW outbound trunk:

  • DIDWW applies STIR/SHAKEN attestation to the call. Any SIP Identity header received from the customer is not preserved.

  • The attestation level is assigned according to DIDWW policies and regulatory requirements.

No additional configuration or action is required from the customer.


Relay Customer Identity Header#

If the customer applies their own STIR/SHAKEN attestation, DIDWW can relay the SIP Identity header unchanged.

When a call is sent through a DIDWW outbound trunk:

  • The customer is responsible for generating and providing a valid SIP Identity header.

  • DIDWW does not generate or modify the SIP Identity header.

  • The original SIP Identity header provided by the customer is relayed unchanged.

To enable Identity header relay for your outbound trunks, contact sales@didww.com or customer.care@didww.com with a request to relay your identity header for outbound calls.

Note

  • This configuration is applied per trunk. It is recommended to use a separate trunk for STIR/SHAKEN traffic.

  • Activation is subject to technical and compliance review.


Additional Information#

For more information about STIR/SHAKEN standards, see the following references:

RFC 8224

Defines how SIP Identity tokens are used to authenticate and verify calling numbers.

https://datatracker.ietf.org/doc/html/rfc8224
RFC 8225

Explains how to create and validate cryptographic tokens for Caller ID verification.

https://datatracker.ietf.org/doc/html/rfc8225
RFC 8226

Covers the use of certificates to establish authority over telephone numbers.

https://datatracker.ietf.org/doc/html/rfc8226
RFC 7340

Outlines challenges leading to unauthorized robocalling and Caller ID spoofing.

https://datatracker.ietf.org/doc/html/rfc7340