CM.com requires all numbers for outbound calling to be formatted using E.164, where the initial + sign is optional.
To / Request URI - The To-header and the Request URI should contain a valid number in the user part of the SIP URI.
From - The From-header should contain a valid number in the user part of the SIP URI, unless the P-Asserted-Identity-header or Remote-Party-ID-header already contain a valid number.
P-Asserted-Identity - The P-Asserted-Identity-header, when present, should contain a valid number in the user part of the SIP URI.
Remote-Party-ID - The Remote-Party-ID-header, when present, should contain a valid number in the user part of the SIP URI.
When a P-Asserted-Identity-header is present in the SIP INVITE, CM.com will use this number as the presented CLI. When a Remote-Party-ID-header is present and no P-Asserted-Identity-header is present, CM.com will use the number in the Remote-Party-ID-header as the presented CLI. In all other cases, CM.com will use the number in the From-header. At least one of the headers (From, P-Asserted-Identity or Remote-Party-ID) should contain a valid number for CLI presentation.
For anonymous calling, a valid CLI should always be present. For more information please visit the Anonymous calls Knowledge Center page.
If your PBX does not have means to send a (valid) CLI in any of the mentioned headers, please refer to the configuration of your SIP account in the Voice Management App (link). Here you can configure one of the DID on your account as the Default CLI.
STIR/SHAKEN
For some countries, STIR/SHAKEN is required to provide attestation on the CLI used for calls. CM.com takes care of signing calls with a valid Identity for the countries that require this. Please visit the STIR/SHAKEN Knowledge Center Page.