Re: [MISC] [TECH] Problème VoLTE / IMS et tickets opérateur sur OnePlus

Le ven. 24 juil. 2026 =C3=A0 12:02, St=C3=A9phane Rivi=C3=A8re via frnog <f=
[email protected]>
a =C3=A9crit :

>
> Un "canal voix" devrait =C3=AAtre associable =C3=A0 n'importe quel email =
et basta.
>
>
RFC2543, mars 1999, Session Initiation Protocol

Petite extrait :

   For example, consider a client that wishes to send a SIP request. The
   Request-URI for the destination is sip:[email protected].  The client
   only supports UDP. It would follow these steps:

        1.   The host portion is not an IP address, so the client goes
             to step 2 above.

        2.   The client does a DNS query of QNAME=3D"sip.udp.company.com",
             QCLASS=3DIN, QTYPE=3DSRV. Since it doesn't support TCP, it
             omits the TCP query. There were no addresses in the DNS
             response, so the client goes to the next step.

        3.   The client does a DNS query for A records for
             "company.com". An address is found, so that client attempts
             to contact a server at that address at port 5060.


Tout n'=C3=A9tait pas parfait dans le SIP, mais l'essentiel y =C3=A9tait. L=
'Internet
(IETF) a gagn=C3=A9 sur les t=C3=A9l=C3=A9coms (ITU). Le SIP est devenu le =
protocole
dominant (H323 anyone ?). Malheureusement, contrairement =C3=A0 ce qu'il s'=
est
pass=C3=A9 pour les r=C3=A9seaux de donn=C3=A9es "op=C3=A9rateurs" (X25 any=
one ?) qui ont
essentiellement disparu au profit de l'Internet, l'architecture de routage
du RTC n'a pas =C3=A9volu=C3=A9, et est rest=C3=A9e bas=C3=A9e sur la num=
=C3=A9rotation ITU.

--=20
Nicolas Bougues

---------------------------
Liste de diffusion du FRnOG
http://www.frnog.org/