Done
Details
Priority
MediumAssignee
Julien AlieJulien AlieReporter
François BlackburnFrançois BlackburnApprovers
Pascal CadottePair
Sylvain BoilyFix versions
Sprint
NoneStory Points
8
Details
Details
Priority
Assignee
Julien Alie
Julien AlieReporter
François Blackburn
François BlackburnApprovers
Pascal Cadotte
Pair
Sylvain Boily
Fix versions
Sprint
None
Story Points
8
Zendesk Support
Zendesk Support
Zendesk Support
Created January 16, 2024 at 12:57 PM
Updated April 25, 2024 at 1:18 PM
Resolved April 19, 2024 at 6:44 PM
Given I have a trunk and a user configured
Given I set the outgoing caller ID of my user to Anonymous
When I make a call
Then the operator doesn’t use the anonymous and fallback on a DID configured
Expected: Anonymous caller ID is used
Technical:
Our Anonymous system doesn’t follow the recommandation by RFC to work by default on most VOIP providers.
When using anonymous, we should send the following headers:
Note:
Latest asterisk version should have new method to update headers
We don’t want to add
send_pai: yes
in theregistration_trunk
template, because we don’t necessarily trust the environmentWe may want to make difference between trunk using authentication by IP and those using authentication by user/password
A more extended investigation about different VOIP provider should be done
Asterisk already implement all this behavior with different options:
trust_id_outbound
will sendPrivate: id
withP-Asserted-Identity
headercallerid_privacy
:prohib
will changeFrom
to"Anonymous” <sip:anonymous@anonymous.invalid>
Acceptance Test:
Make it work with VOIP operator support anonymous call.
ref:
RFC 3323
RFC 3325