Configurare e comprendere IPv6 per la prima volta

hitech95 · 2021-05-13T20:10:59+00:00

Buonasera, Ora che ho Sky Wifi Attivo e funzionante vorrei finalmente capire come configurare la rete in dual stack. Allora, Comincio a dire che ovviamente c...

gandalf2016

hitech95 Mi sa che sei fuori strada per il voip.
voip.sky.it è solamente il dominio di rete. come Telecomitalia.it per TIM.
la query prova a farla su:
nslookup -query=AAAA voip.it.isp.sky 2a0e:404:0:a::1

Questa dovrebbe funzionare:
nslookup -query=srv _sip._udp.voip.it.isp.sky 2a0e:404:0:a::1

hitech95

fracarza nslookup -query=any voip.sky.it 2a0e:404:0:a::1 cosa dice?

gandalf2016 nslookup -query=AAAA voip.it.isp.sky 2a0e:404:0:a::1
nslookup -query=srv sip.udp.voip.it.isp.sky 2a0e:404:0:a::1

C:\Users\Hitech95>nslookup -query=AAAA voip.it.isp.sky 2a0e:404:0:a::1
Server:  UnKnown
Address:  2a0e:404:0:a::1

*** UnKnown non è in grado di trovare voip.it.isp.sky: No response from server

C:\Users\Hitech95>nslookup -query=srv _sip._udp.voip.it.isp.sky 2a0e:404:0:a::1
Server:  UnKnown
Address:  2a0e:404:0:a::1

*** UnKnown non è in grado di trovare _sip._udp.voip.it.isp.sky: No response from server

C:\Users\Hitech95>nslookup -query=any voip.sky.it 2a0e:404:0:a::1
Server:  UnKnown
Address:  2a0e:404:0:a::1

*** UnKnown non è in grado di trovare voip.sky.it: No response from server

C:\Users\Hitech95>

gandalf2016 voip.sky.it mi sa che è solamente il dominio di rete

Si si infatti, ma io ci avevo provato lo stesso!

[cancellato]

x_term Il discorso invece del test su ipv6-test, intanto considera che ICMP appare filtered giustamente, tu non vuoi che il tuo PC risponda ai ping da tutto internet, no?

In realtà in IPv6 ICMP gioca un ruolo più importante che in IPv4: https://datatracker.ietf.org/doc/html/rfc4890

hitech95 Comunque non ho ancora ben capito la differenza tra DHCPv6, SLAAC e RA.
Sembrano fare tutti la stessa cosa.

Sì, ma la fanno in modo diverso. Poi IPv6 complica le cose con DHCPv6 stateful e stateless, più SLAAC e RA.

DHCPv6 stateful funziona come in IPv4 - il server DHCP genera l'indirizzo, ne tiene traccia (ecco perché stateful) e lo invia a chi ne fa richiesta più le altre informazioni. Io uso questo perché 1) il server DHCP registra gli indirizzi nel DNS e solo lui può farlo 2) ho il log dei client che hanno richiesto un IP. L'unico problema è Android perché in Google c'è un deficiente che non vuole che i suoi "tessssori" abbiano l'accesso controllato dal proprietario della rete.

Con DHCPv6 stateless il client ottiente il prefisso via RA e poi usa SLAAC per generare l'indirizzo. Poi usa DHCP per ottenere le altre informazioni (es. server DNS). Il server DHCP non tiene traccia dei client. Se vuoi la registrazione nel DNS deve registrarsi il client per conto suo. A me non piace per questo motivo.

Oppure puoi usare solo SLAAC e RA - ti perdi il controllo centralizzato di DHCP.

fracarza

hitech95 Ora però ti sta dando un altro problema, che il server non risponde. Se fai
nslookup -query=any sky.it 2a0e:404:0:a::1, nslookup -query=any voip.it.isp.sky 2a0e:404:0:a::1, e nslookup -query=any voip.sky.it 2a0e:404:0:a::1 almeno il primo dovrebbe risolverlo.

hitech95

fracarza Ora però ti sta dando un altro problema, che il server non risponde. Se fai

Si per qualche ragione radvd era andato giù e non avevo più un indirizzo IPv6

C:\Users\Hitech95>nslookup -query=any sky.it 2a0e:404:0:a::1
Server:  UnKnown
Address:  2a0e:404:0:a::1

Risposta da un server non autorevole:
sky.it  internet address = 185.26.143.165
sky.it  internet address = 185.26.140.70
sky.it  text =

        "MS=ms90374774"
sky.it  text =

        "MS=ms97918068"
sky.it  text =

        "v=spf1 ip4:185.26.140.52/32 include:spf.protection.outlook.com -all"
sky.it  text =

        "google-site-verification=FcJkvvSDYWAZixO3SPwluEgx9Slo8-9Vwsdy2kEhdr4"
sky.it  text =

        "MS=ms45245552"
sky.it
        primary name server = ns1.sky.it
        responsible mail addr = hostmaster.sky.it
        serial  = 2021053005
        refresh = 86400 (1 day)
        retry   = 3600 (1 hour)
        expire  = 3600000 (41 days 16 hours)
        default TTL = 3600 (1 hour)
sky.it  nameserver = ns1.sky.it
sky.it  nameserver = ns2.sky.it
sky.it  MX preference = 10, mail exchanger = sky-it.mail.protection.outlook.com

ns1.sky.it      internet address = 185.26.140.129
ns2.sky.it      internet address = 185.26.142.129

C:\Users\Hitech95>nslookup -query=any voip.it.isp.sky 2a0e:404:0:a::1
Server:  UnKnown
Address:  2a0e:404:0:a::1

Risposta da un server non autorevole:
voip.it.isp.sky ??? unknown type 35 ???

it.isp.sky      nameserver = ns1.it.isp.sky
it.isp.sky      nameserver = ns0.it.isp.sky
it.isp.sky      nameserver = ns2.it.isp.sky
ns0.it.isp.sky  internet address = 101.62.253.25
ns1.it.isp.sky  internet address = 101.62.253.26
ns2.it.isp.sky  internet address = 101.62.253.27

C:\Users\Hitech95>nslookup -query=any voip.sky.it 2a0e:404:0:a::1
Server:  UnKnown
Address:  2a0e:404:0:a::1

*** UnKnown non è in grado di trovare voip.sky.it: Non-existent domain

C:\Users\Hitech95>

fracarza

hitech95 voip.it.isp.sky ??? unknown type 35 ???

Ok funziona vede un NAPTR.

hitech95 SkyWifi/sip:voip.sky.it:5060 SkyWifi Rejected

Com'è configurato Asterisk? Ricordati che devi mettere voip.it.isp.sky come outbound proxy.

hitech95

Comunque Asterisk non ne vuole sapere di registrare la trunk.

<Registration/ServerURI..............................>  <Auth..........>  <Status.......>
==========================================================================================

Clouditalia/sip:voip.eutelia.it                         Clouditalia       Registered
SkyWifi/sip:voip.sky.it:5060                            SkyWifi           Rejected

Objects found: 2

[2021-05-14 14:32:00] WARNING[10287] res_pjsip_outbound_registration.c: No response received from 'sip:voip.sky.it:5060' on registration attempt to 'sip:NNNNNNXXXXXXXXX@voip.sky.it', retrying in '60'

Più tardi vado di debug cattivo -vvvv e miguardo tutti i frame SIP...

Dalla macchina PBX:

[root@freepbx ~]# host -t NAPTR voip.it.isp.sky
voip.it.isp.sky has NAPTR record 10 100 "S" "SIP+D2U" "" _sip._udp.voip.glb.it.isp.sky.
[root@freepbx ~]#

Non conosco questa tipologia di DNS, ma immagino che venga correttamente interpretata.

eutampieri

hitech95 Più tardi vado di debug cattivo -vvvv e miguardo tutti i frame SIP...

O di sip set debug on

hitech95

fracarza

Mi sembra tutto regolare:

PJSIP Endpoint

[SkyWifi]
type=endpoint
transport=0.0.0.0-udp
context=from-pstn
disallow=all
allow=ulaw,alaw
aors=SkyWifi
language=it
outbound_proxy=sip:voip.it.isp.sky:5060
outbound_auth=SkyWifi
from_domain=sip:voip.sky.it:5060
from_user=sip:<username>@voip.sky.it:5060
user_eq_phone=no
t38_udptl=no
t38_udptl_ec=none
fax_detect=no
trust_id_inbound=no
t38_udptl_nat=no
direct_media=no
rtp_symmetric=yes
dtmf_mode=auto

PJSIP Auth

[SkyWifi]
type=auth
auth_type=userpass
password=<redacted>
username=<redacted>

fracarza

hitech95 Questa configurazione mi puzza un po', ci sono un paio di cose che non mi convincono. Puoi mandare anche aor e registration?

transport deve essere IPv6 quindi 0.0.0.0-udp non va bene, dovresti avere bind su :: non 0.0.0.0 (se il bind è corretto in 0.0.0.0-udp allora ok, ma dovresti cambiargli il nome per rendere più chiaro o meglio ancora creare due trasporti diversi). outbound_proxy non deve avere :5060. from_domain è solo voip.sky.it e from_user solo <username>, ma entrambi non sono particolarmente necessari.

hitech95

fracarza
Super pappardella per voi 🙂

AOR

[SkyWifi]
type=aor
qualify_frequency=61
contact=sip:XXXXXXXXXXXXXXXX@voip.sky.it
outbound_proxy=sip:voip.it.isp.sky:5060

Registration:

[SkyWifi]
type=registration
transport=0.0.0.0-udp
outbound_auth=SkyWifi
retry_interval=60
fatal_retry_interval=0
forbidden_retry_interval=10
max_retries=10
expiration=3600
line=yes
endpoint=SkyWifi
auth_rejection_permanent=yes
server_uri=sip:voip.sky.it:5060
client_uri=sip:XXXXXXXXXXXXXXXX@voip.sky.it
outbound_proxy=sip:voip.it.isp.sky:5060

Verbose log di asterisk: (occhio che ho un altra trunk con eutelia)

freepbx*CLI> pjsip set logger on
PJSIP Logging enabled
[2021-05-14 20:02:06] DEBUG[7901]: res_pjsip_registrar.c:1176 check_expiration_thread: Woke up at 1621015326  Interval: 30
[2021-05-14 20:02:06] DEBUG[7901]: res_pjsip_registrar.c:1183 check_expiration_thread: Expiring 0 contacts
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip/pjsip_options.c:926 sip_options_qualify_aor: Qualifying all contacts on AOR 'SkyWifi'
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip/pjsip_options.c:856 sip_options_qualify_contact: Qualifying contact 'SkyWifi@@81175c713807c4225acf899c8c745ae2' on AOR 'SkyWifi'
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip.c:3983 endpt_send_request: 0x7fb03000a278: Wrapper created
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip.c:3998 endpt_send_request: 0x7fb03000a278: Set timer to 3000 msec
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip/pjsip_resolver.c:477 sip_resolve: Performing SIP DNS resolution of target 'voip.it.isp.sky'
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip/pjsip_resolver.c:504 sip_resolve: Transport type for target 'voip.it.isp.sky' is 'UDP'
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip/pjsip_resolver.c:547 sip_resolve: [0x7fb03000b600] Created resolution tracking for target 'voip.it.isp.sky'
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7fb03000b600] Added target 'voip.it.isp.sky' with record type '35', transport 'UDP', and port '5060'
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7fb03000b600] Added target '_sip._udp.voip.it.isp.sky' with record type '33', transport 'UDP', and port '5060'
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7fb03000b600] Added target 'voip.it.isp.sky' with record type '1', transport 'UDP', and port '5060'
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip/pjsip_resolver.c:616 sip_resolve: [0x7fb03000b600] Starting initial resolution using parallel queries for target 'voip.it.isp.sky'
[2021-05-14 20:02:20] DEBUG[7899]: res_pjsip/pjsip_resolver.c:277 sip_resolve_callback: [0x7fb03000b600] All parallel queries completed
[2021-05-14 20:02:20] DEBUG[7899]: res_pjsip/pjsip_resolver.c:371 sip_resolve_callback: [0x7fb03000b600] NAPTR record received on target 'voip.it.isp.sky'
[2021-05-14 20:02:20] DEBUG[7899]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7fb03000b600] Added target '_sip._udp.voip.glb.it.isp.sky' with record type '33', transport 'UDP', and port '5060'
[2021-05-14 20:02:20] DEBUG[7899]: res_pjsip/pjsip_resolver.c:413 sip_resolve_callback: [0x7fb03000b600] New queries added, performing parallel resolution again
[2021-05-14 20:02:20] DEBUG[7899]: res_pjsip/pjsip_resolver.c:277 sip_resolve_callback: [0x7fb03000b600] All parallel queries completed
[2021-05-14 20:02:20] DEBUG[7899]: res_pjsip/pjsip_resolver.c:349 sip_resolve_callback: [0x7fb03000b600] SRV record received on target '_sip._udp.voip.glb.it.isp.sky'
[2021-05-14 20:02:20] DEBUG[7899]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7fb03000b600] Added target 'sbc.rmle1.voip.glb.it.isp.sky' with record type '1', transport 'UDP', and port '5060'
[2021-05-14 20:02:20] DEBUG[7899]: res_pjsip/pjsip_resolver.c:349 sip_resolve_callback: [0x7fb03000b600] SRV record received on target '_sip._udp.voip.glb.it.isp.sky'
[2021-05-14 20:02:20] DEBUG[7899]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7fb03000b600] Added target 'sbc.mid41.voip.glb.it.isp.sky' with record type '1', transport 'UDP', and port '5060'
[2021-05-14 20:02:20] DEBUG[7899]: res_pjsip/pjsip_resolver.c:349 sip_resolve_callback: [0x7fb03000b600] SRV record received on target '_sip._udp.voip.glb.it.isp.sky'
[2021-05-14 20:02:20] DEBUG[7899]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7fb03000b600] Added target 'sbc.rmtp1.voip.glb.it.isp.sky' with record type '1', transport 'UDP', and port '5060'
[2021-05-14 20:02:20] DEBUG[7899]: res_pjsip/pjsip_resolver.c:349 sip_resolve_callback: [0x7fb03000b600] SRV record received on target '_sip._udp.voip.glb.it.isp.sky'
[2021-05-14 20:02:20] DEBUG[7899]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7fb03000b600] Added target 'sbc.mica1.voip.glb.it.isp.sky' with record type '1', transport 'UDP', and port '5060'
[2021-05-14 20:02:20] DEBUG[7899]: res_pjsip/pjsip_resolver.c:413 sip_resolve_callback: [0x7fb03000b600] New queries added, performing parallel resolution again
[2021-05-14 20:02:20] DEBUG[7899]: res_pjsip/pjsip_resolver.c:277 sip_resolve_callback: [0x7fb03000b600] All parallel queries completed
[2021-05-14 20:02:20] DEBUG[7899]: res_pjsip/pjsip_resolver.c:419 sip_resolve_callback: [0x7fb03000b600] Resolution completed - 0 viable targets
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip/pjsip_resolver.c:207 sip_resolve_invoke_user_callback: [0x7fb03000b600] Invoking user callback with '0' addresses
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip.c:3861 endpt_send_request_cb: 0x7fb03000a278: PJSIP tsx response received
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip.c:3874 endpt_send_request_cb: 0x7fb03000a278: Cancelling timer
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip.c:3883 endpt_send_request_cb: 0x7fb03000a278: Timer cancelled
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip.c:3904 endpt_send_request_cb: 0x7fb03000a278: Callbacks executed
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip.c:3960 send_request_wrapper_destructor: 0x7fb03000a278: wrapper destroyed
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip/pjsip_options.c:758 sip_options_contact_status_notify_task: Contact SkyWifi/sip:XXXXXXXXXXXXXXXX@voip.sky.it status didn't change: Unreachable, RTT: 0.000 msec
[2021-05-14 20:02:20] DEBUG[10287]: res_pjsip/pjsip_options.c:776 sip_options_contact_status_notify_task: AOR 'SkyWifi' now has 0 available contacts
[2021-05-14 20:02:28] DEBUG[3950]: manager.c:6473 process_message: Running action 'Login'
[2021-05-14 20:02:29] DEBUG[3950]: manager.c:6473 process_message: Running action 'Command'
[2021-05-14 20:02:29] DEBUG[3950]: manager.c:6473 process_message: Running action 'Command'
[2021-05-14 20:02:29] DEBUG[3950]: manager.c:6473 process_message: Running action 'Command'
[2021-05-14 20:02:29] DEBUG[3950]: manager.c:6473 process_message: Running action 'Command'
[2021-05-14 20:02:29] DEBUG[3950]: manager.c:6473 process_message: Running action 'Command'
[2021-05-14 20:02:29] DEBUG[3950]: manager.c:6473 process_message: Running action 'Command'
[2021-05-14 20:02:29] DEBUG[3950]: devicestate.c:367 _ast_device_state: No provider found, checking channel drivers for PJSIP - SkyWifi
[2021-05-14 20:02:29] DEBUG[3950]: manager.c:6473 process_message: Running action 'Command'
[2021-05-14 20:02:31] DEBUG[10287]: res_pjsip_outbound_registration.c:575 handle_client_registration: Outbound REGISTER attempt 3 to 'sip:voip.sky.it:5060' with client 'sip:XXXXXXXXXXXXXXXX@voip.sky.it'
[2021-05-14 20:02:31] DEBUG[10287]: res_pjsip/pjsip_resolver.c:477 sip_resolve: Performing SIP DNS resolution of target 'voip.it.isp.sky'
[2021-05-14 20:02:31] DEBUG[10287]: res_pjsip/pjsip_resolver.c:504 sip_resolve: Transport type for target 'voip.it.isp.sky' is 'UDP'
[2021-05-14 20:02:31] DEBUG[10287]: res_pjsip/pjsip_resolver.c:547 sip_resolve: [0x7fb03000af40] Created resolution tracking for target 'voip.it.isp.sky'
[2021-05-14 20:02:31] DEBUG[10287]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7fb03000af40] Added target 'voip.it.isp.sky' with record type '1', transport 'UDP', and port '5060'
[2021-05-14 20:02:31] DEBUG[10287]: res_pjsip/pjsip_resolver.c:616 sip_resolve: [0x7fb03000af40] Starting initial resolution using parallel queries for target 'voip.it.isp.sky'
[2021-05-14 20:02:31] DEBUG[7899]: res_pjsip/pjsip_resolver.c:277 sip_resolve_callback: [0x7fb03000af40] All parallel queries completed
[2021-05-14 20:02:31] DEBUG[7899]: res_pjsip/pjsip_resolver.c:419 sip_resolve_callback: [0x7fb03000af40] Resolution completed - 0 viable targets
[2021-05-14 20:02:31] DEBUG[10287]: res_pjsip/pjsip_resolver.c:207 sip_resolve_invoke_user_callback: [0x7fb03000af40] Invoking user callback with '0' addresses
[2021-05-14 20:02:31] DEBUG[10287]: res_pjsip_outbound_registration.c:1056 sip_outbound_registration_response_cb: Received REGISTER response 503(No answer record in the DNS response (PJLIB_UTIL_EDNSNOANSWERREC))
[2021-05-14 20:02:31] DEBUG[10287]: res_pjsip_outbound_registration.c:906 handle_registration_response: Processing REGISTER response 503 from server 'sip:voip.sky.it:5060' for client 'sip:XXXXXXXXXXXXXXXX@voip.sky.it'
[2021-05-14 20:02:31] DEBUG[10287]: res_pjsip_outbound_registration.c:635 schedule_registration: Scheduling outbound registration to server 'sip:voip.sky.it:5060' from client 'sip:XXXXXXXXXXXXXXXX@voip.sky.it' in 60 seconds
[2021-05-14 20:02:31] WARNING[10287]: res_pjsip_outbound_registration.c:796 schedule_retry: No response received from 'sip:voip.sky.it:5060' on registration attempt to 'sip:XXXXXXXXXXXXXXXX@voip.sky.it', retrying in '60'
[2021-05-14 20:02:31] DEBUG[13044]: manager.c:6017 match_filter: Examining AMI event:
Event: Registry
Privilege: system,all
ChannelType: PJSIP
Username: sip:XXXXXXXXXXXXXXXX@voip.sky.it
Domain: sip:voip.sky.it:5060
Status: Rejected

Non manda nessun pacchetto SIP fuori o perlomeno non mi mostra nulla riguardo la trunk di sky!

fracarza

hitech95 Ok quindi i problemi che vedo così di primo acchito sono il trasporto sbagliato e :5060 attaccato all'outbound proxy.

Aggiungi alla conf:

[transport-udp6]
type=transport
protocol=udp
bind=::

e sostituisci 0.0.0.0-udp con transport-udp6 negli snippet [SkyWifi].

P.S. ocio che mi sa che hai lasciato dei dati sensibili nel log

gandalf2016

hitech95 mm vedo dei Datacenter familiari da cui rispondo i server.

mica1 Milano Caldera
Mid41 Milano Data4
RmtpRoma TecnoPolo (tiburtino) cloudeurope
Rmle?? Boh non mi viene in mente al momento 😅

hitech95

fracarza P.S. ocio che mi sa che hai lasciato dei dati sensibili nel log

Sicuro mi sembra di aver tolto tutto ora controllo di nuovo!

fracarza Aggiungi alla conf:
[transport-udp6]
type=transport
protocol=udp
bind=::
e sostituisci 0.0.0.0-udp con transport-udp6 negli snippet [SkyWifi].

Con freePBX è più incasinato del previsto, ma ho fatto.
Ora ottengo un altro errore maledetto!

ERROR[11694]: res_pjsip.c:4049 endpt_send_request: Error 320047 'No answer record in the DNS response (PJLIB_UTIL_EDNSNOANSWERREC)' sending OPTIONS request to endpoint SkyWifi

freepbx*CLI> pjsip show transport transport-udp6

Transport:  <TransportId........>  <Type>  <cos>  <tos>  <BindAddress....................>
==========================================================================================

Transport:  transport-udp6            udp      3     96  [::]:5060

 ParameterName              : ParameterValue
 ===========================================
 allow_reload               : false
 async_operations           : 1
 bind                       : [::]:5060
 ca_list_file               :
 ca_list_path               :
 cert_file                  :
 cipher                     :
 cos                        : 3
 domain                     :
 external_media_address     :
 external_signaling_address :
 external_signaling_port    : 0
 local_net                  :
 method                     : unspecified
 password                   :
 priv_key_file              :
 protocol                   : udp
 require_client_cert        : No
 symmetric_transport        : false
 tos                        : 96
 verify_client              : No
 verify_server              : No
 websocket_write_timeout    : 100

freepbx*CLI> pjsip show endpoint SkyWifi

 Endpoint:  <Endpoint/CID.....................................>  <State.....>  <Channels.>
    I/OAuth:  <AuthId/UserName...........................................................>
        Aor:  <Aor............................................>  <MaxContact>
      Contact:  <Aor/ContactUri..........................> <Hash....> <Status> <RTT(ms)..>
  Transport:  <TransportId........>  <Type>  <cos>  <tos>  <BindAddress..................>
   Identify:  <Identify/Endpoint.........................................................>
        Match:  <criteria.........................>
    Channel:  <ChannelId......................................>  <State.....>  <Time.....>
        Exten: <DialedExten...........>  CLCID: <ConnectedLineCID.......>
==========================================================================================

 Endpoint:  SkyWifi                                              Unavailable   0 of inf
    OutAuth:  SkyWifi/XXXXXXXXXXXXXXXX
        Aor:  SkyWifi                                            0
      Contact:  SkyWifi/sip:XXXXXXXXXXXXXXXX@voip.sky.it    81175c7138 Unavail       0.000
  Transport:  transport-udp6            udp      3     96  [::]:5060


 ParameterName                      : ParameterValue
 =============================================================
 100rel                             : yes
 accept_multiple_sdp_answers        : false
 accountcode                        :
 acl                                :
 aggregate_mwi                      : true
 allow                              : (ulaw|alaw)
 allow_overlap                      : true
 allow_subscribe                    : true
 allow_transfer                     : true
 aors                               : SkyWifi
 asymmetric_rtp_codec               : false
 auth                               :
 bind_rtp_to_media_address          : false
 bundle                             : false
 call_group                         :
 callerid                           : <unknown>
 callerid_privacy                   : allowed_not_screened
 callerid_tag                       :
 connected_line_method              : invite
 contact_acl                        :
 context                            : from-pstn
 cos_audio                          : 0
 cos_video                          : 0
 device_state_busy_at               : 0
 direct_media                       : false
 direct_media_glare_mitigation      : none
 direct_media_method                : invite
 disable_direct_media_on_nat        : false
 dtls_auto_generate_cert            : No
 dtls_ca_file                       :
 dtls_ca_path                       :
 dtls_cert_file                     :
 dtls_cipher                        :
 dtls_fingerprint                   : SHA-256
 dtls_private_key                   :
 dtls_rekey                         : 0
 dtls_setup                         : active
 dtls_verify                        : No
 dtmf_mode                          : auto
 fax_detect                         : false
 fax_detect_timeout                 : 0
 follow_early_media_fork            : true
 force_avp                          : false
 force_rport                        : true
 from_domain                        : voip.sky.it
 from_user                          :
 g726_non_standard                  : false
 ice_support                        : false
 identify_by                        : username,ip
 inband_progress                    : false
 incoming_mwi_mailbox               :
 language                           : it
 mailboxes                          :
 max_audio_streams                  : 1
 max_video_streams                  : 1
 media_address                      :
 media_encryption                   : no
 media_encryption_optimistic        : false
 media_use_received_transport       : false
 message_context                    :
 moh_passthrough                    : false
 moh_suggest                        : default
 mwi_from_user                      :
 mwi_subscribe_replaces_unsolicited : no
 named_call_group                   :
 named_pickup_group                 :
 notify_early_inuse_ringing         : false
 one_touch_recording                : false
 outbound_auth                      : SkyWifi
 outbound_proxy                     : sip:voip.it.isp.sky:5060
 pickup_group                       :
 preferred_codec_only               : false
 record_off_feature                 : automixmon
 record_on_feature                  : automixmon
 refer_blind_progress               : true
 rewrite_contact                    : false
 rpid_immediate                     : false
 rtcp_mux                           : false
 rtp_engine                         : asterisk
 rtp_ipv6                           : false
 rtp_keepalive                      : 0
 rtp_symmetric                      : true
 rtp_timeout                        : 0
 rtp_timeout_hold                   : 0
 sdp_owner                          : -
 sdp_session                        : Asterisk
 send_diversion                     : true
 send_pai                           : false
 send_rpid                          : false
 set_var                            :
 srtp_tag_32                        : false
 sub_min_expiry                     : 0
 subscribe_context                  :
 suppress_q850_reason_headers       : false
 t38_udptl                          : false
 t38_udptl_ec                       : none
 t38_udptl_ipv6                     : false
 t38_udptl_maxdatagram              : 0
 t38_udptl_nat                      : false
 timers                             : yes
 timers_min_se                      : 90
 timers_sess_expires                : 1800
 tone_zone                          :
 tos_audio                          : 0
 tos_video                          : 0
 transport                          : transport-udp6
 trust_id_inbound                   : false
 trust_id_outbound                  : false
 use_avpf                           : false
 use_ptime                          : false
 user_eq_phone                      : false
 voicemail_extension                :
 webrtc                             : no

freepbx*CLI>

sul trasport come puoi notare ho provato anche con [::]:5060

hitech95

gandalf2016
Si su DDday parlavano di 4 "super-nodi" 2 a milano e 2 a roma interconnessi con tre connessioni rindondate
ciascuno... bah. Io immagino sia una rete tier 3 con il core router al centro....

fracarza

hitech95 Togli la porta dall'outbound proxy e dal bind.

hitech95 Sembra che da quando il trasport è impostato su IPv6 sia addirittura peggiorato.

Prima cercava un record di tipo 35 ma ora non lo fa più.

É tutto corretto trova un record AAAA per voip.it.isp.sky.

hitech95 EDIT #1: intanto la porta non ci va altrimenti non risolve:
https://github.com/asterisk/asterisk/blob/master/res/res_pjsip/pjsip_resolver.c#L551

Solo se il transport non è specificato.

hitech95

fracarza Si guarda qui: hitech95
Ho provato con il +39 0039 e il numero diretto. Non cambia nulla.

gandalf2016

hitech95 No, puoi verificare che è veramente come descritto. Es. Telia lo agganciano a Milano Data4 e Milano Caldera. Configurato in ECMP.

hitech95

Continuo ad avere quel problema che non risolve il dominio... non capisco come fare...
Sembra che da quando il trasport è impostato su IPv6 sia addirittura peggiorato.

Prima cercava un record di tipo 35 ma ora non lo fa più. Inoltre la dicitura dei 4 nodi (milano e roma) non ci sono.

[2021-05-14 22:56:01] DEBUG[17860]: res_pjsip/pjsip_resolver.c:479 sip_resolve: Performing SIP DNS resolution of target 'voip.it.isp.sky'
[2021-05-14 22:56:01] DEBUG[17860]: res_pjsip/pjsip_resolver.c:506 sip_resolve: Transport type for target 'voip.it.isp.sky' is 'UDP transport'
[2021-05-14 22:56:01] DEBUG[17860]: res_pjsip/pjsip_resolver.c:549 sip_resolve: [0x7fd7c0318d28] Created resolution tracking for target 'voip.it.isp.sky'
[2021-05-14 22:56:01] DEBUG[17860]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7fd7c0318d28] Added target 'voip.it.isp.sky' with record type '28', transport 'UDP IPv6 transport', and port '5060'
[2021-05-14 22:56:01] DEBUG[17860]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7fd7c0318d28] Added target 'voip.it.isp.sky' with record type '1', transport 'UDP transport', and port '5060'
[2021-05-14 22:56:01] DEBUG[17860]: res_pjsip/pjsip_resolver.c:620 sip_resolve: [0x7fd7c0318d28] Starting initial resolution using parallel queries for target 'voip.it.isp.sky'
[2021-05-14 22:56:01] DEBUG[17870]: res_pjsip/pjsip_resolver.c:277 sip_resolve_callback: [0x7fd7c0318d28] All parallel queries completed
[2021-05-14 22:56:01] DEBUG[17870]: res_pjsip/pjsip_resolver.c:421 sip_resolve_callback: [0x7fd7c0318d28] Resolution completed - 0 viable targets
[2021-05-14 22:56:01] DEBUG[17860]: res_pjsip/pjsip_resolver.c:207 sip_resolve_invoke_user_callback: [0x7fd7c0318d28] Invoking user callback with '0' addresses
[2021-05-14 22:56:01] DEBUG[17860]: res_pjsip_outbound_registration.c:1235 sip_outbound_registration_response_cb: Received REGISTER response 503(No answer record in the DNS response (PJLIB_UTIL_EDNSNOANSWERREC))
[2021-05-14 22:56:01] DEBUG[17860]: res_pjsip_outbound_registration.c:1073 handle_registration_response: Processing REGISTER response 503 from server 'sip:voip.sky.it' for client 'sip:0600001PPsmqAAD@voip.sky.it'
[2021-05-14 22:56:01] WARNING[17860]: res_pjsip_outbound_registration.c:1156 handle_registration_response: Maximum retries reached when attempting outbound registration to 'sip:voip.sky.it' with client 'sip:XXXXXXXXXXXXXXXX@voip.sky.it', stopping registration attempt
[2021-05-14 22:56:01] DEBUG[17977]: manager.c:6200 match_filter: Examining AMI event:
Event: Registry
Privilege: system,all
ChannelType: PJSIP
Username: sip:XXXXXXXXXXXXXXXX@voip.sky.it
Domain: sip:voip.sky.it
Status: Rejected

Il resolver funziona da CLI:

[root@freepbx ~]# host -t NAPTR voip.it.isp.sky
voip.it.isp.sky has NAPTR record 10 100 "S" "SIP+D2U" "" _sip._udp.voip.glb.it.isp.sky.
[root@freepbx ~]# host -t SRV _sip._udp.voip.glb.it.isp.sky
_sip._udp.voip.glb.it.isp.sky has SRV record 10 10 5060 sbc.rmle1.voip.glb.it.isp.sky.
_sip._udp.voip.glb.it.isp.sky has SRV record 20 10 5060 sbc.mid41.voip.glb.it.isp.sky.
_sip._udp.voip.glb.it.isp.sky has SRV record 30 10 5060 sbc.rmtp1.voip.glb.it.isp.sky.
_sip._udp.voip.glb.it.isp.sky has SRV record 40 10 5060 sbc.mica1.voip.glb.it.isp.sky.
[root@freepbx ~]# host -t SRV sbc.mica1.voip.glb.it.isp.sky
sbc.mica1.voip.glb.it.isp.sky has no SRV record
[root@freepbx ~]# host -t all sbc.mica1.voip.glb.it.isp.sky
host: invalid type: all

[root@freepbx ~]# nslookup sbc.mica1.voip.glb.it.isp.sky
Server:         127.0.0.1
Address:        127.0.0.1#53

Non-authoritative answer:
Name:   sbc.mica1.voip.glb.it.isp.sky
Address: 2a0e:402:100:200::7

[root@freepbx ~]#

EDIT #1: intanto la porta non ci va altrimenti non risolve:
https://github.com/asterisk/asterisk/blob/master/res/res_pjsip/pjsip_resolver.c#L551

hitech95

fracarza
Allora se ci metto la porta fallisce male perchè non si mette a cercare via NAPTR. (non cerca un record di tipo 25.

Ora invece mi fallisce il pjsip con un bel PJSIP_ETPNOTSUITABLE.

[2021-05-14 23:30:48] DEBUG[1737]: res_pjsip_outbound_registration.c:686 handle_client_registration: Outbound REGISTER attempt 4 to 'sip:voip.sky.it' with client 'sip:XXXXXXXXXXXXXXXX@voip.sky.it'
[2021-05-14 23:30:48] DEBUG[1737]: res_pjsip/pjsip_resolver.c:479 sip_resolve: Performing SIP DNS resolution of target 'voip.it.isp.sky'
[2021-05-14 23:30:48] DEBUG[1737]: res_pjsip/pjsip_resolver.c:506 sip_resolve: Transport type for target 'voip.it.isp.sky' is 'UDP transport'
[2021-05-14 23:30:48] DEBUG[1737]: res_pjsip/pjsip_resolver.c:549 sip_resolve: [0x7f38643076b8] Created resolution tracking for target 'voip.it.isp.sky'
[2021-05-14 23:30:48] DEBUG[1737]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7f38643076b8] Added target 'voip.it.isp.sky' with record type '35', transport 'UDP transport', and port '5060'
[2021-05-14 23:30:48] DEBUG[1737]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7f38643076b8] Added target '_sip._udp.voip.it.isp.sky' with record type '33', transport 'UDP transport', and port '5060'
[2021-05-14 23:30:48] DEBUG[1737]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7f38643076b8] Added target 'voip.it.isp.sky' with record type '28', transport 'UDP IPv6 transport', and port '5060'
[2021-05-14 23:30:48] DEBUG[1737]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7f38643076b8] Added target 'voip.it.isp.sky' with record type '1', transport 'UDP transport', and port '5060'
[2021-05-14 23:30:48] DEBUG[1737]: res_pjsip/pjsip_resolver.c:620 sip_resolve: [0x7f38643076b8] Starting initial resolution using parallel queries for target 'voip.it.isp.sky'
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:277 sip_resolve_callback: [0x7f38643076b8] All parallel queries completed
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:373 sip_resolve_callback: [0x7f38643076b8] NAPTR record received on target 'voip.it.isp.sky'
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7f38643076b8] Added target '_sip._udp.voip.glb.it.isp.sky' with record type '33', transport 'UDP transport', and port '5060'
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:415 sip_resolve_callback: [0x7f38643076b8] New queries added, performing parallel resolution again
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:277 sip_resolve_callback: [0x7f38643076b8] All parallel queries completed
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:349 sip_resolve_callback: [0x7f38643076b8] SRV record received on target '_sip._udp.voip.glb.it.isp.sky'
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7f38643076b8] Added target 'sbc.rmle1.voip.glb.it.isp.sky' with record type '28', transport 'UDP IPv6 transport', and port '5060'
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7f38643076b8] Added target 'sbc.rmle1.voip.glb.it.isp.sky' with record type '1', transport 'UDP transport', and port '5060'
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:349 sip_resolve_callback: [0x7f38643076b8] SRV record received on target '_sip._udp.voip.glb.it.isp.sky'
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7f38643076b8] Added target 'sbc.mid41.voip.glb.it.isp.sky' with record type '28', transport 'UDP IPv6 transport', and port '5060'
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7f38643076b8] Added target 'sbc.mid41.voip.glb.it.isp.sky' with record type '1', transport 'UDP transport', and port '5060'
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:349 sip_resolve_callback: [0x7f38643076b8] SRV record received on target '_sip._udp.voip.glb.it.isp.sky'
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7f38643076b8] Added target 'sbc.rmtp1.voip.glb.it.isp.sky' with record type '28', transport 'UDP IPv6 transport', and port '5060'
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7f38643076b8] Added target 'sbc.rmtp1.voip.glb.it.isp.sky' with record type '1', transport 'UDP transport', and port '5060'
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:349 sip_resolve_callback: [0x7f38643076b8] SRV record received on target '_sip._udp.voip.glb.it.isp.sky'
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7f38643076b8] Added target 'sbc.mica1.voip.glb.it.isp.sky' with record type '28', transport 'UDP IPv6 transport', and port '5060'
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7f38643076b8] Added target 'sbc.mica1.voip.glb.it.isp.sky' with record type '1', transport 'UDP transport', and port '5060'
[2021-05-14 23:30:48] DEBUG[1747]: res_pjsip/pjsip_resolver.c:415 sip_resolve_callback: [0x7f38643076b8] New queries added, performing parallel resolution again
[2021-05-14 23:30:49] DEBUG[1747]: res_pjsip/pjsip_resolver.c:277 sip_resolve_callback: [0x7f38643076b8] All parallel queries completed
[2021-05-14 23:30:49] DEBUG[1747]: res_pjsip/pjsip_resolver.c:332 sip_resolve_callback: [0x7f38643076b8] AAAA record received on target 'sbc.rmle1.voip.glb.it.isp.sky'
[2021-05-14 23:30:49] DEBUG[1747]: res_pjsip/pjsip_resolver.c:332 sip_resolve_callback: [0x7f38643076b8] AAAA record received on target 'sbc.mid41.voip.glb.it.isp.sky'
[2021-05-14 23:30:49] DEBUG[1747]: res_pjsip/pjsip_resolver.c:332 sip_resolve_callback: [0x7f38643076b8] AAAA record received on target 'sbc.rmtp1.voip.glb.it.isp.sky'
[2021-05-14 23:30:49] DEBUG[1747]: res_pjsip/pjsip_resolver.c:332 sip_resolve_callback: [0x7f38643076b8] AAAA record received on target 'sbc.mica1.voip.glb.it.isp.sky'
[2021-05-14 23:30:49] DEBUG[1747]: res_pjsip/pjsip_resolver.c:421 sip_resolve_callback: [0x7f38643076b8] Resolution completed - 4 viable targets
[2021-05-14 23:30:49] DEBUG[1737]: res_pjsip/pjsip_resolver.c:201 sip_resolve_invoke_user_callback: [0x7f38643076b8] Address '0' is [2a0e:402:100::7]:5060 with transport 'UDP IPv6 transport'
[2021-05-14 23:30:49] DEBUG[1737]: res_pjsip/pjsip_resolver.c:201 sip_resolve_invoke_user_callback: [0x7f38643076b8] Address '1' is [2a0e:402:100:300::7]:5060 with transport 'UDP IPv6 transport'
[2021-05-14 23:30:49] DEBUG[1737]: res_pjsip/pjsip_resolver.c:201 sip_resolve_invoke_user_callback: [0x7f38643076b8] Address '2' is [2a0e:402:100:100::7]:5060 with transport 'UDP IPv6 transport'
[2021-05-14 23:30:49] DEBUG[1737]: res_pjsip/pjsip_resolver.c:201 sip_resolve_invoke_user_callback: [0x7f38643076b8] Address '3' is [2a0e:402:100:200::7]:5060 with transport 'UDP IPv6 transport'
[2021-05-14 23:30:49] DEBUG[1737]: res_pjsip/pjsip_resolver.c:207 sip_resolve_invoke_user_callback: [0x7f38643076b8] Invoking user callback with '4' addresses
[2021-05-14 23:30:49] DEBUG[1737]: res_pjsip_outbound_registration.c:1235 sip_outbound_registration_response_cb: Received REGISTER response 503(Unsuitable transport selected (PJSIP_ETPNOTSUITABLE))
[2021-05-14 23:30:49] DEBUG[1737]: res_pjsip_outbound_registration.c:1073 handle_registration_response: Processing REGISTER response 503 from server 'sip:voip.sky.it' for client 'sip:XXXXXXXXXXXXXXXX@voip.sky.it'
[2021-05-14 23:30:49] DEBUG[1737]: res_pjsip_outbound_registration.c:732 schedule_registration: Scheduling outbound registration to server 'sip:voip.sky.it' from client 'sip:XXXXXXXXXXXXXXXX@voip.sky.it' in 60 seconds
[2021-05-14 23:30:49] WARNING[1737]: res_pjsip_outbound_registration.c:894 schedule_retry: No response received from 'sip:voip.sky.it' on registration attempt to 'sip:XXXXXXXXXXXXXXXX@voip.sky.it', retrying in '60'
[2021-05-14 23:30:49] DEBUG[1879]: manager.c:6200 match_filter: Examining AMI event:
Event: Registry
Privilege: system,all
ChannelType: PJSIP
Username: sip:XXXXXXXXXXXXXXXX@voip.sky.it
Domain: sip:voip.sky.it
Status: Rejected

fracarza

hitech95 C'è qualcosa che non va nel trasporto allora, te lo legge ancora come UDP transport invece che UDP IPv6 transport. Toglilo da endpoint e registration che dovrebbe fare autodiscovery.

E ricordati anche rtp_ipv6=yes in endpoint, anche se non dovrebbe essere questa la causa del problema ora.

Hai riavviato Asterisk dopo aver cambiato i trasporti?

hitech95

fracarza
Si si riavvio asterisk ogni volta. Qualcosa si è mosso. Ma il fatto che non trova il trasport è davvero strano.

[May 15 00:53:16] <--- Transmitting SIP request (650 bytes) to UDP:[2a0e:402:100::7]:5060 --->
[May 15 00:53:16] REGISTER sip:voip.it.isp.sky SIP/2.0
[May 15 00:53:16] Via: SIP/2.0/UDP [2a0e:xxxx:xxxx:0:xxxx:xxff:fexx:xxxx]:5060;rport;branch=z9hG4bKPj06e553c1-0038-4cf0-a72d-07688b415560
[May 15 00:53:16] From: <sip:XXXXXXXXXXXXXXXX@voip.sky.it>;tag=b459a34a-f89f-43f1-8cc4-6b1a781714e6
[May 15 00:53:16] To: <sip:XXXXXXXXXXXXXXXX@voip.sky.it>
[May 15 00:53:16] Call-ID: 4688519d-8402-4f53-8740-ab3cb614d91a
[May 15 00:53:16] CSeq: 26672 REGISTER
[May 15 00:53:16] Contact: <sip:s@[2a0e:xxxx:xxxx:0:xxxx:xxff:fexx:xxxx]:5060;line=xhxioyt>
[May 15 00:53:16] Expires: 3600
[May 15 00:53:16] Allow: OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, MESSAGE, REFER
[May 15 00:53:16] Route: <sip:voip.sky.it>
[May 15 00:53:16] Max-Forwards: 70
[May 15 00:53:16] User-Agent: FPBX-14.0.16.4(18.3.0)
[May 15 00:53:16] Content-Length:  0
[May 15 00:53:16]
[May 15 00:53:16]
[May 15 00:53:16] <--- Received SIP response (471 bytes) from UDP:[2a0e:402:100::7]:5060 --->
[May 15 00:53:16] SIP/2.0 403 Forbidden
[May 15 00:53:16] Call-ID: 4688519d-8402-4f53-8740-ab3cb614d91a
[May 15 00:53:16] Via: SIP/2.0/UDP [2a0e:xxxx:xxxx:0:xxxx:xxff:fexx:xxxx]:5060;received=2a0e:xxxx:xxxx:0:xxxx:xxff:fexx:xxxx;branch=z9hG4bKPj06e553c1-0038-4cf0-a72d-07688b415560;rport=5060
[May 15 00:53:16] To: <sip:XXXXXXXXXXXXXXXX@voip.sky.it>;tag=6099bed2-609eff5c28ee4db3
[May 15 00:53:16] From: <sip:XXXXXXXXXXXXXXXX@voip.sky.it>;tag=b459a34a-f89f-43f1-8cc4-6b1a781714e6
[May 15 00:53:16] CSeq: 26672 REGISTER
[May 15 00:53:16] Date: Fri, 14 May 2021 22:53:16 GMT
[May 15 00:53:16] Content-Length: 0

Che poi la sequenza non dovrebbe essere register > 403 > auth > register con token?
Perchè si ferma?

« Pagina precedente Pagina successiva »

Informativa privacy - Informativa cookie - Termini e condizioni - Regolamento - Disclaimer - 🏳️‍🌈 🇵🇸
P.I. IT16712091004 - info@fibraclick.it

♻️ Il server di questo sito è alimentato al 100% con energia rinnovabile