mirror of
https://github.com/asterisk/asterisk.git
synced 2025-09-03 11:25:35 +00:00
res_pjsip_stir_shaken: Fix JSON field ordering and disallowed TN characters.
The current STIR/SHAKEN signing process is inconsistent with the RFCs in a couple ways that can cause interoperability issues. RFC8225 specifies that the keys must be ordered lexicographically, but currently the fields are simply ordered according to the order in which they were added to the JSON object, which is not compliant with the RFC and can cause issues with some carriers. To fix this, we now leverage libjansson's ability to dump a JSON object sorted by key value, yielding the correct field ordering. Additionally, telephone numbers must have any leading + prefix removed and must not contain characters outside of 0-9, *, and # in order to comply with the RFCs. Numbers are now properly formatted as such. ASTERISK-30407 #close Change-Id: Iab76d39447c4b8cf133de85657dba02fda07f9a2
This commit is contained in:
committed by
Friendly Automation
parent
ecf49ff746
commit
0119f3ad48
@@ -60,13 +60,10 @@ static char *ari_show(struct ast_cli_entry *e, int cmd, struct ast_cli_args *a)
|
||||
ast_cli(a->fd, "ARI Status:\n");
|
||||
ast_cli(a->fd, "Enabled: %s\n", AST_CLI_YESNO(conf->general->enabled));
|
||||
ast_cli(a->fd, "Output format: ");
|
||||
switch (conf->general->format) {
|
||||
case AST_JSON_COMPACT:
|
||||
ast_cli(a->fd, "compact");
|
||||
break;
|
||||
case AST_JSON_PRETTY:
|
||||
if (conf->general->format & AST_JSON_PRETTY) {
|
||||
ast_cli(a->fd, "pretty");
|
||||
break;
|
||||
} else {
|
||||
ast_cli(a->fd, "compact");
|
||||
}
|
||||
ast_cli(a->fd, "\n");
|
||||
ast_cli(a->fd, "Auth realm: %s\n", conf->general->auth_realm);
|
||||
|
Reference in New Issue
Block a user