[asterisk-dev] stirshaken caller_id_number matching wrong field

[Luke Escudé]

Gotcha, thanks - One last question, does caller_id_number accept more than 1 number for matching? If a customer has 100 DIDs, I'd hate to repeat the certificate profile 100 times.
________________________________
From: asterisk-dev <asterisk-dev-bounces at lists.digium.com> on behalf of Joshua C. Colp <jcolp at sangoma.com>
Sent: Tuesday, May 10, 2022 3:03 PM
To: Asterisk Developers Mailing List <asterisk-dev at lists.digium.com>
Subject: Re: [asterisk-dev] stirshaken caller_id_number matching wrong field

On Tue, May 10, 2022 at 4:51 PM Luke Escudé <luke at primevox.net<mailto:luke at primevox.net>> wrote:
Getting STIR/SHAKEN stuff going, and I'm encountering something odd.

All outbound calls are not being signed, and Asterisk gives the following error:

Failed to retrieve certificate for caller ID '<DIALED NUMBER>'

So, it's trying to match on the number I dialed, instead of the actual outgoing CallerID set in the CALLERID(num) of the outgoing call.

There's already an open issue[1] for this. The STIR/SHAKEN functionality needs further work aside from this to work with current standards.

[1] https://issues.asterisk.org/jira/browse/ASTERISK-29169

--
Joshua C. Colp
Asterisk Technical Lead
Sangoma Technologies
Check us out at www.sangoma.com<http://www.sangoma.com> and www.asterisk.org<http://www.asterisk.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20220510/d3965479/attachment-0001.html>