Re: [asterisk-dev] stirshaken caller_id_number matching wrong field
On Tue, May 10, 2022 at 6:54 PM Luke Escudé wrote: > 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. > As implemented currently, no. -- Joshua C. Colp Asterisk Technical Lead Sangoma Technologies Check us out at www.sangoma.com and www.asterisk.org -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] stirshaken caller_id_number matching wrong field
On Tue, May 10, 2022 at 4:51 PM Luke Escudé 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 '' > > 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 and www.asterisk.org -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
