Hi David,
The implementation of stir-shaken in France is different from in the US. The text which requires French operators to implement stir-shaken aims to stop the usurpation of caller-id. So, what is asked of the operator is to check their customer's caller-id and sign outgoing calls, in the event of fraud, it will then be easy to trace the malicious operator. For operators receiving unsigned or incorrectly signed traffic, the call must be disconnected. for the case of call forwarding (A -> B then B-> C), there will therefore be two signatures, a first issued by the operator of A and which will be controlled by the operator of B. Then operator B will add his own signature (in addition to that of A), both signatures will be controlled by C Regards De : Users <[email protected]> au nom de David Villasmil <[email protected]> Répondre à : OpenSIPS users mailling list <[email protected]> Date : vendredi 5 juillet 2024 à 11:39 À : OpenSIPS users mailling list <[email protected]> Objet : Re: [OpenSIPS-Users] Removing Identity hdr this is really getting ridiculous... and they think they can stop robocalls with this.. they never will. Regards, David Villasmil email: [email protected] On Tue, Jun 18, 2024 at 10:56 AM Alain Bieuzent <[email protected]> wrote: Hi, interesting question, because in future developments of stir/shaken in France, for forwarded calls, it is planned that the identity field received on the incoming call be forwarded to the outgoing leg but also to add a signature (with the local certificate) on the outgoing call (so two identity fields). Regards De : Users <[email protected]> au nom de Srigo Kanapathipillai <[email protected]> Répondre à : OpenSIPS users mailling list <[email protected]> Date : mardi 18 juin 2024 à 08:34 À : OpenSIPS users mailling list <[email protected]> Objet : [OpenSIPS-Users] Removing Identity hdr Hi, I'm encountering an issue with removing an Identity header in OpenSIPS 3.4. Here’s the situation: 1. An incoming call with an Identity header is received. 2. I perform a `stir_shaken_verify()` and remove the Identity header in a request route. 3. The call is forwarded to an upstream server, but it fails. 4. In the `failure_route`, I need to forward the call to a PSTN number. 5. Before sending the call to the PSTN (in compliance with French STIR/SHAKEN regulations), I need to sign it with my certificate. However, when I call `stir_shaken_auth()`, I receive an error -2 indicating that the Identity header already exists. Despite running `remove_hf(identity)` before calling this function, the header isn't removed, and `$hdr(identity)` still returns the initial value of the Identity header. What is the best way to remove the existing Identity header and re-sign the call? Thank you, Srigo _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
