Final answer (in french): *Par ailleurs, il semble que ce point n’est pas clair pour tout le monde, APNF a soulevé ce point ce matin en atelier MAN. Il y aura une mise à jour du document « Règles techniques MAN » pour bien clarifier afin d’éviter des mauvaises interprétations. Je t’enverrai le texte clarifié discuté ce matin dès que je le reçois de la part de APNF.*
So we have to accept more than 15 digits in dest... Le mer. 6 sept. 2023 à 16:07, Mickael Hubert <[email protected]> a écrit : > Answer of this french provider (in french sorry) > > *Pour le 1er point, la clause 2.5.3 des règles techniques MAN est pour le > cas où l’opérateur de transit ajoute un préfixe de portabilité, afin de > préservé l’Identity initial, il est impérative de ne pas modifier le header > To.* > > *Par contre, dans le cas où c’est l’opérateur origine d’initie un appel > avec préfixe de portabilité, il n’est pas interdit de valoriser le header > To avec le préfixe de portabilité, à condition que le Token contient le > claim « dest » égale la valeur du header To. Le résultat de vérification > devra être OK.* > > > What do you think ? > > Le mer. 6 sept. 2023 à 15:35, Mickael Hubert <[email protected]> a écrit : > >> Thanks a lot Daren, >> I have to contact this big french provider to explain its issue ;) >> >> Le mer. 6 sept. 2023 à 15:24, Daren FERREIRA <[email protected]> a >> écrit : >> >>> We don’t have the same understanding of MAN and FFT rules as, for >>> portability, only R-URI is changed, not the To, that should point to the >>> called number. >>> And, as To is the source of the TN, the TN shouldn’t contain the >>> portability prefix, and, then, we don’t exceed the 15 numbers limit and >>> E164. >>> >>> Then, MAN documentation always mention E164 conformity. One of the main >>> rules of E164 is the maximum of 15 digits, so... >>> >>> So, it’s up to you to make things works as you intend to do. Good luck ;) >>> >>> >>> >>> Some extracts from MAN documentation as proofs : >>> >>> >>> Règles techniques: >>> >>> Remarque sur la portabilité : l’ajout d’un préfixe de portabilité >>> doit être fait uniquement au niveau de l’en-tête SIP Request-URI. >>> >>> Cahier de tests: >>> >>> Appel (fixe ou mobile) depuis un ORT1 vers un ORT2 en transit SIP qui >>> retransmet vers ORT3 avec présence de header Identity valide. ORT2 >>> ajoute un préfixe de portabilité pour ORT3 dans R-URI mais pas dans TO (TO >>> n'est pas modifié) >>> >>> >>> >>> Le 6 sept. 2023 à 15:09, Mickael Hubert <[email protected]> a écrit : >>> >>> Nop Daren, in France it's possible to sign with a portability prefix :( >>> >>> Le mer. 6 sept. 2023 à 14:53, David Villasmil < >>> [email protected]> a écrit : >>> >>>> damn... it seems there's a new law in France to do stir/shaken... >>>> Regards, >>>> >>>> David Villasmil >>>> email: [email protected] >>>> phone: +34669448337 >>>> >>>> >>>> On Wed, Sep 6, 2023 at 2:38 PM Mickael Hubert <[email protected]> >>>> wrote: >>>> >>>>> We are deploying it in France. >>>>> In France on providers interconnections, we can see a format (made in >>>>> France maybe ;) ) >>>>> prefix: +33 >>>>> portability prefix: 10200 >>>>> phonenumber national format without 0: 123456789 >>>>> >>>>> ++ >>>>> >>>>> >>>>> Le mer. 6 sept. 2023 à 14:30, David Villasmil < >>>>> [email protected]> a écrit : >>>>> >>>>>> Is ST/SH being used other than the US? AFAIK it only applies to US >>>>>> numbers, thus 10 digits, no? >>>>>> >>>>>> On Wed, 6 Sep 2023 at 14:27, Mickael Hubert <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> yep I found... >>>>>>> >>>>>>> if (end - start < 2 || end - start > 15) >>>>>>> return -1; >>>>>>> >>>>>>> I have to modify this code. >>>>>>> I will propose a PR. >>>>>>> >>>>>>> Thanks a lot >>>>>>> ++ >>>>>>> >>>>>>> Le mer. 6 sept. 2023 à 14:25, Marcin Groszek <[email protected]> >>>>>>> a écrit : >>>>>>> >>>>>>>> Correction : maximum of 15 digits . >>>>>>>> On 9/6/2023 7:21 AM, Marcin Groszek wrote: >>>>>>>> >>>>>>>> Your number is to long >>>>>>>> >>>>>>>> E.164 is + [1-9] and {1-14} digits for total of 15 digits NOT >>>>>>>> starting with 0 >>>>>>>> On 9/6/2023 7:16 AM, Mickael Hubert wrote: >>>>>>>> >>>>>>>> Hi all, >>>>>>>> I have an issue, when I verify a call with no E164 format (dest: >>>>>>>> +3310200123456789) >>>>>>>> >>>>>>>> *logs:* >>>>>>>> Sep 6 13:39:48 am-scr-001 /usr/local/sbin/opensips[622409]: >>>>>>>> ERROR:stir_shaken:check_passport_phonenum: number is not in E.164 >>>>>>>> format: >>>>>>>> 3310200123456789 >>>>>>>> Sep 6 13:39:48 am-scr-001 /usr/local/sbin/opensips[622409]: >>>>>>>> ERROR:stir_shaken:w_stir_verify: failed to validate Destination number >>>>>>>> (3310200123456789) >>>>>>>> >>>>>>>> *My configuration:* >>>>>>>> # ----------------- module stir_shaken --------------- >>>>>>>> loadmodule "stir_shaken.so" >>>>>>>> #----------- stir_shaken params ----------------- >>>>>>>> modparam("stir_shaken", "ca_list", >>>>>>>> "/usr/local/etc/opensips/man_ca.pem") >>>>>>>> modparam("stir_shaken", "require_date_hdr", 0) >>>>>>>> modparam("stir_shaken", "verify_date_freshness", 60) >>>>>>>> >>>>>>>> According to the doc e164_strict_mode is disabled by default, so I >>>>>>>> don't know why it doesn't work. >>>>>>>> >>>>>>>> *source of code: * >>>>>>>> if (_is_e164(num, e164_strict_mode) == -1) { >>>>>>>> LM_GEN(log_lev, "number is not in E.164 format: >>>>>>>> %.*s\n", num->len, num->s); >>>>>>>> return -1; >>>>>>>> } >>>>>>>> >>>>>>>> >>>>>>>> Do you have any help for me please ? I have to validate this format >>>>>>>> of dest number. >>>>>>>> >>>>>>>> Thanks in advance >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Users mailing >>>>>>>> [email protected]http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>>>>>> >>>>>>>> -- >>>>>>>> Best Regards: >>>>>>>> Marcin Groszek >>>>>>>> Business Phone Servicehttps://www.voipplus.net >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Users mailing >>>>>>>> [email protected]http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>>>>>> >>>>>>>> -- >>>>>>>> Best Regards: >>>>>>>> Marcin Groszek >>>>>>>> Business Phone Servicehttps://www.voipplus.net >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>> >>>> _______________________________________________ >>>> 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
