Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-2215

FIWARE.Request.Lab.FI-Lab Assistance - Are we community? Datenfreunde UG.

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-LAB-HELP
    • Labels:
      None

      Description

      Hello Fiware Help!

      We've won SpeedUpEurope! Grants with Datefreunde UG, which I think makes us
      elegible for community membership status in the FiWare Cloud. Still, I
      found no way of confirming what my / our status is in the lab cloud. We
      want to make sure our work in the lab cloud is not lost.

      This is our organization:

      https://account.lab.fiware.org/organizations/datenfreunde-ug-1

      ​Basically, our preference would be that anybody who is member of that
      organization will be community member of the lab cloud. Is that possible?

      Cheers,

      MV

      PS SpeedupEurope-Projects run by Datenfreunde UG include:

      Roboreport http://apps.opendatacity.de/speedupeurope/0.3/#roboreport
      Sensorhome http://apps.opendatacity.de/speedupeurope/0.3/#sensorhome
      Dataflow http://apps.opendatacity.de/speedupeurope/0.3/#dataflow
      Carnanny http://apps.opendatacity.de/speedupeurope/0.3/#carnanny


      Martin Virtel <martin.virtel@gmail.com> / @mvtango / +49/172/992 13 96
      Current Projects: http://soglaubtberlin.de · http://lobbycloud.eu/
      Liveblogging für dpa <http://www.dpa.de/Anmeldung-Whitepaper-01.1110.0.html>
      · http://ediciones.la22.org/laeconomista/ · http://twitter.com/roboreport

      _______________________________________________
      Fiware-lab-help mailing list
      Fiware-lab-help@lists.fi-ware.org
      https://lists.fi-ware.org/listinfo/fiware-lab-help

      [Created via e-mail received from: Martin Virtel <martin.virtel@gmail.com>]

        Activity

        Hide
        marcocipriani Marco Cipriani added a comment -

        Dear Martin,
        the process will be applied in different steps, starting from 24/02/2015.
        Instructions, procedures and application forms for “community” account will be soon available and communicated to the users.
        No work will be lost.

        Best regards
        Marco

        ----------------------------------------------------------------
        Telecom Italia
        Marco Cipriani
        O.ET.NSM.SSD
        Via V. Zambra, 1 - 38121 Trento
        +39 0461 316 365
        +39 331 6001044
        marco2.cipriani@telecomitalia.it<marco2.cipriani@telecomitalia.it>

        Da: fiware-lab-help-bounces@lists.fi-ware.org fiware-lab-help-bounces@lists.fi-ware.org Per conto di Martin Virtel
        Inviato: giovedì 26 febbraio 2015 10:54
        A: fiware-lab-help@lists.fi-ware.org
        Cc: umut; Malte Burkhardt; Carl Ziegner; kd@datenfreunde.com; Maas Marco
        Oggetto: [Fiware-lab-help] FI-Lab Assistance - Are we community? Datenfreunde UG

        Hello Fiware Help!

        We've won SpeedUpEurope! Grants with Datefreunde UG, which I think makes us elegible for community membership status in the FiWare Cloud. Still, I found no way of confirming what my / our status is in the lab cloud. We want to make sure our work in the lab cloud is not lost.

        This is our organization:

        https://account.lab.fiware.org/organizations/datenfreunde-ug-1

        ​Basically, our preference would be that anybody who is member of that organization will be community member of the lab cloud. Is that possible?

        Cheers,

        MV

        PS SpeedupEurope-Projects run by Datenfreunde UG include:

        Roboreport http://apps.opendatacity.de/speedupeurope/0.3/#roboreport
        Sensorhome http://apps.opendatacity.de/speedupeurope/0.3/#sensorhome
        Dataflow http://apps.opendatacity.de/speedupeurope/0.3/#dataflow
        Carnanny http://apps.opendatacity.de/speedupeurope/0.3/#carnanny


        Martin Virtel <martin.virtel@gmail.com<martin.virtel@gmail.com>> / @mvtango / +49/172/992 13 96
        Current Projects: http://soglaubtberlin.de · http://lobbycloud.eu/
        Liveblogging für dpa<http://www.dpa.de/Anmeldung-Whitepaper-01.1110.0.html> · http://ediciones.la22.org/laeconomista/ · http://twitter.com/roboreport
        Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

        This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

        [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario.

        Show
        marcocipriani Marco Cipriani added a comment - Dear Martin, the process will be applied in different steps, starting from 24/02/2015. Instructions, procedures and application forms for “community” account will be soon available and communicated to the users. No work will be lost. Best regards Marco ---------------------------------------------------------------- Telecom Italia Marco Cipriani O.ET.NSM.SSD Via V. Zambra, 1 - 38121 Trento +39 0461 316 365 +39 331 6001044 marco2.cipriani@telecomitalia.it< marco2.cipriani@telecomitalia.it > Da: fiware-lab-help-bounces@lists.fi-ware.org fiware-lab-help-bounces@lists.fi-ware.org Per conto di Martin Virtel Inviato: giovedì 26 febbraio 2015 10:54 A: fiware-lab-help@lists.fi-ware.org Cc: umut; Malte Burkhardt; Carl Ziegner; kd@datenfreunde.com; Maas Marco Oggetto: [Fiware-lab-help] FI-Lab Assistance - Are we community? Datenfreunde UG Hello Fiware Help! We've won SpeedUpEurope! Grants with Datefreunde UG, which I think makes us elegible for community membership status in the FiWare Cloud. Still, I found no way of confirming what my / our status is in the lab cloud. We want to make sure our work in the lab cloud is not lost. This is our organization: https://account.lab.fiware.org/organizations/datenfreunde-ug-1 ​Basically, our preference would be that anybody who is member of that organization will be community member of the lab cloud. Is that possible? Cheers, MV PS SpeedupEurope-Projects run by Datenfreunde UG include: Roboreport http://apps.opendatacity.de/speedupeurope/0.3/#roboreport Sensorhome http://apps.opendatacity.de/speedupeurope/0.3/#sensorhome Dataflow http://apps.opendatacity.de/speedupeurope/0.3/#dataflow Carnanny http://apps.opendatacity.de/speedupeurope/0.3/#carnanny ​ – Martin Virtel <martin.virtel@gmail.com< martin.virtel@gmail.com >> / @mvtango / +49/172/992 13 96 Current Projects: http://soglaubtberlin.de · http://lobbycloud.eu/ Liveblogging für dpa< http://www.dpa.de/Anmeldung-Whitepaper-01.1110.0.html > · http://ediciones.la22.org/laeconomista/ · http://twitter.com/roboreport Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente] Rispetta l'ambiente. Non stampare questa mail se non è necessario.
        Hide
        fw.ext.user FW External User added a comment -

        Hello FiWare Lab Help,

        I've not been successful in reaching my public IP. Please see diagnostics
        below - traceroute finds it, but ping and ssh do not.

        What am I missing?

        Cheers,

        MV

        mvirtel@nyx:~$ traceroute 130.206.126.244
        traceroute to 130.206.126.244 (130.206.126.244), 30 hops max, 60 byte
        packets
        1 1.64.238.89.in-addr.arpa.manitu.net (89.238.64.1) 0.203 ms 0.181 ms
        0.170 ms
        2 inexio1.gw.network.manitu.net (89.238.127.46) 4.577 ms 4.584 ms
        4.550 ms
        3 ae61.edge4.Frankfurt1.Level3.net (212.162.5.201) 11.137 ms 4.502 ms
        4.630 ms
        4 ae-14-14.bar1.Madrid2.Level3.net (4.69.158.169) 34.545 ms
        ae-13-13.bar1.Madrid2.Level3.net (4.69.158.165) 34.525 ms
        ae-12-12.bar1.Madrid2.Level3.net (4.69.158.161) 34.534 ms
        5 213.242.113.78 (213.242.113.78) 34.534 ms 34.570 ms 34.504 ms
        6 TELMADI.AE1.ciemat.rt1.mad.red.rediris.es (130.206.245.1) 33.737 ms
        33.784 ms 33.797 ms
        7 CIEMAT.XE4-1-0.telmad.rt6.mad.red.rediris.es (130.206.245.46) 34.384
        ms 34.245 ms 34.284 ms
        8 130.206.192.158 (130.206.192.158) 34.790 ms 34.771 ms 34.764 ms
        9 130.206.126.244 (130.206.126.244) 3050.760 ms !H 3049.191 ms !H
        3049.199 ms !H
        mvirtel@nyx:~$ ssh 130.206.126.244
        ssh: connect to host 130.206.126.244 port 22: No route to host
        mvirtel@nyx:~$ ssh -v 130.206.126.244
        OpenSSH_6.0p1 Debian-4+deb7u1, OpenSSL 1.0.1e 11 Feb 2013
        debug1: Reading configuration data /etc/ssh/ssh_config
        debug1: /etc/ssh/ssh_config line 19: Applying options for *
        debug1: Connecting to 130.206.126.244 [130.206.126.244] port 22.
        debug1: connect to address 130.206.126.244 port 22: No route to host
        ssh: connect to host 130.206.126.244 port 22: No route to host
        mvirtel@nyx:~$ ping 130.206.126.244
        PING 130.206.126.244 (130.206.126.244) 56(84) bytes of data.
        From 130.206.126.244 icmp_seq=1 Destination Host Unreachable
        From 130.206.126.244 icmp_seq=2 Destination Host Unreachable
        From 130.206.126.244 icmp_seq=3 Destination Host Unreachable
        From 130.206.126.244 icmp_seq=4 Destination Host Unreachable
        From 130.206.126.244 icmp_seq=5 Destination Host Unreachable
        From 130.206.126.244 icmp_seq=6 Destination Host Unreachable


        Martin Virtel <martin.virtel@gmail.com> / @mvtango / +49/172/992 13 96
        Current Projects: http://soglaubtberlin.de · http://lobbycloud.eu/
        Liveblogging für dpa <http://www.dpa.de/Anmeldung-Whitepaper-01.1110.0.html>
        · http://ediciones.la22.org/laeconomista/ · http://twitter.com/roboreport

        Show
        fw.ext.user FW External User added a comment - Hello FiWare Lab Help, I've not been successful in reaching my public IP. Please see diagnostics below - traceroute finds it, but ping and ssh do not. What am I missing? Cheers, MV mvirtel@nyx:~$ traceroute 130.206.126.244 traceroute to 130.206.126.244 (130.206.126.244), 30 hops max, 60 byte packets 1 1.64.238.89.in-addr.arpa.manitu.net (89.238.64.1) 0.203 ms 0.181 ms 0.170 ms 2 inexio1.gw.network.manitu.net (89.238.127.46) 4.577 ms 4.584 ms 4.550 ms 3 ae61.edge4.Frankfurt1.Level3.net (212.162.5.201) 11.137 ms 4.502 ms 4.630 ms 4 ae-14-14.bar1.Madrid2.Level3.net (4.69.158.169) 34.545 ms ae-13-13.bar1.Madrid2.Level3.net (4.69.158.165) 34.525 ms ae-12-12.bar1.Madrid2.Level3.net (4.69.158.161) 34.534 ms 5 213.242.113.78 (213.242.113.78) 34.534 ms 34.570 ms 34.504 ms 6 TELMADI.AE1.ciemat.rt1.mad.red.rediris.es (130.206.245.1) 33.737 ms 33.784 ms 33.797 ms 7 CIEMAT.XE4-1-0.telmad.rt6.mad.red.rediris.es (130.206.245.46) 34.384 ms 34.245 ms 34.284 ms 8 130.206.192.158 (130.206.192.158) 34.790 ms 34.771 ms 34.764 ms 9 130.206.126.244 (130.206.126.244) 3050.760 ms !H 3049.191 ms !H 3049.199 ms !H mvirtel@nyx:~$ ssh 130.206.126.244 ssh: connect to host 130.206.126.244 port 22: No route to host mvirtel@nyx:~$ ssh -v 130.206.126.244 OpenSSH_6.0p1 Debian-4+deb7u1, OpenSSL 1.0.1e 11 Feb 2013 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to 130.206.126.244 [130.206.126.244] port 22. debug1: connect to address 130.206.126.244 port 22: No route to host ssh: connect to host 130.206.126.244 port 22: No route to host mvirtel@nyx:~$ ping 130.206.126.244 PING 130.206.126.244 (130.206.126.244) 56(84) bytes of data. From 130.206.126.244 icmp_seq=1 Destination Host Unreachable From 130.206.126.244 icmp_seq=2 Destination Host Unreachable From 130.206.126.244 icmp_seq=3 Destination Host Unreachable From 130.206.126.244 icmp_seq=4 Destination Host Unreachable From 130.206.126.244 icmp_seq=5 Destination Host Unreachable From 130.206.126.244 icmp_seq=6 Destination Host Unreachable – Martin Virtel <martin.virtel@gmail.com> / @mvtango / +49/172/992 13 96 Current Projects: http://soglaubtberlin.de · http://lobbycloud.eu/ Liveblogging für dpa < http://www.dpa.de/Anmeldung-Whitepaper-01.1110.0.html > · http://ediciones.la22.org/laeconomista/ · http://twitter.com/roboreport
        Hide
        marcocipriani Marco Cipriani added a comment -

        Dear Martin,
        you should check:

        • if you have associated a security group to the instance
        • the rules applied in the security group. You have to create a protocol/port rules for each service you want to reach.

        You can get information/help about the FIWARE platform on:

        Best regards
        Marco

        Da: fiware-lab-help-bounces@lists.fi-ware.org fiware-lab-help-bounces@lists.fi-ware.org Per conto di Martin Virtel
        Inviato: giovedì 26 febbraio 2015 20:53
        A: fiware-lab-help@lists.fi-ware.org
        Cc: umut; Malte Burkhardt; Carl Ziegner; kd@datenfreunde.com; Maas Marco
        Oggetto: Re: [Fiware-lab-help] FI-Lab Assistance - Are we community? Datenfreunde UG

        Hello FiWare Lab Help,

        I've not been successful in reaching my public IP. Please see diagnostics below - traceroute finds it, but ping and ssh do not.

        What am I missing?

        Cheers,

        MV

        mvirtel@nyx:~$ traceroute 130.206.126.244
        traceroute to 130.206.126.244 (130.206.126.244), 30 hops max, 60 byte packets
        1 1.64.238.89.in-addr.arpa.manitu.net<http://1.64.238.89.in-addr.arpa.manitu.net> (89.238.64.1) 0.203 ms 0.181 ms 0.170 ms
        2 inexio1.gw.network.manitu.net<http://inexio1.gw.network.manitu.net> (89.238.127.46) 4.577 ms 4.584 ms 4.550 ms
        3 ae61.edge4.Frankfurt1.Level3.net<http://ae61.edge4.Frankfurt1.Level3.net> (212.162.5.201) 11.137 ms 4.502 ms 4.630 ms
        4 ae-14-14.bar1.Madrid2.Level3.net<http://ae-14-14.bar1.Madrid2.Level3.net> (4.69.158.169) 34.545 ms ae-13-13.bar1.Madrid2.Level3.net<http://ae-13-13.bar1.Madrid2.Level3.net> (4.69.158.165) 34.525 ms ae-12-12.bar1.Madrid2.Level3.net<http://ae-12-12.bar1.Madrid2.Level3.net> (4.69.158.161) 34.534 ms
        5 213.242.113.78 (213.242.113.78) 34.534 ms 34.570 ms 34.504 ms
        6 TELMADI.AE1.ciemat.rt1.mad.red.rediris.es<http://TELMADI.AE1.ciemat.rt1.mad.red.rediris.es> (130.206.245.1) 33.737 ms 33.784 ms 33.797 ms
        7 CIEMAT.XE4-1-0.telmad.rt6.mad.red.rediris.es<http://CIEMAT.XE4-1-0.telmad.rt6.mad.red.rediris.es> (130.206.245.46) 34.384 ms 34.245 ms 34.284 ms
        8 130.206.192.158 (130.206.192.158) 34.790 ms 34.771 ms 34.764 ms
        9 130.206.126.244 (130.206.126.244) 3050.760 ms !H 3049.191 ms !H 3049.199 ms !H
        mvirtel@nyx:~$ ssh 130.206.126.244
        ssh: connect to host 130.206.126.244 port 22: No route to host
        mvirtel@nyx:~$ ssh -v 130.206.126.244
        OpenSSH_6.0p1 Debian-4+deb7u1, OpenSSL 1.0.1e 11 Feb 2013
        debug1: Reading configuration data /etc/ssh/ssh_config
        debug1: /etc/ssh/ssh_config line 19: Applying options for *
        debug1: Connecting to 130.206.126.244 [130.206.126.244] port 22.
        debug1: connect to address 130.206.126.244 port 22: No route to host
        ssh: connect to host 130.206.126.244 port 22: No route to host
        mvirtel@nyx:~$ ping 130.206.126.244
        PING 130.206.126.244 (130.206.126.244) 56(84) bytes of data.
        From 130.206.126.244 icmp_seq=1 Destination Host Unreachable
        From 130.206.126.244 icmp_seq=2 Destination Host Unreachable
        From 130.206.126.244 icmp_seq=3 Destination Host Unreachable
        From 130.206.126.244 icmp_seq=4 Destination Host Unreachable
        From 130.206.126.244 icmp_seq=5 Destination Host Unreachable
        From 130.206.126.244 icmp_seq=6 Destination Host Unreachable


        Martin Virtel <martin.virtel@gmail.com<martin.virtel@gmail.com>> / @mvtango / +49/172/992 13 96
        Current Projects: http://soglaubtberlin.de · http://lobbycloud.eu/
        Liveblogging für dpa<http://www.dpa.de/Anmeldung-Whitepaper-01.1110.0.html> · http://ediciones.la22.org/laeconomista/ · http://twitter.com/roboreport
        Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

        This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

        [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario.

        Show
        marcocipriani Marco Cipriani added a comment - Dear Martin, you should check: if you have associated a security group to the instance the rules applied in the security group. You have to create a protocol/port rules for each service you want to reach. You can get information/help about the FIWARE platform on: The FIWARE Academy e-learning portal: http://edu.fiware.org Video tutorials: http://help.lab.fi-ware.org Questions/Answers http://stackoverflow.com/questions/tagged/fiware Best regards Marco Da: fiware-lab-help-bounces@lists.fi-ware.org fiware-lab-help-bounces@lists.fi-ware.org Per conto di Martin Virtel Inviato: giovedì 26 febbraio 2015 20:53 A: fiware-lab-help@lists.fi-ware.org Cc: umut; Malte Burkhardt; Carl Ziegner; kd@datenfreunde.com; Maas Marco Oggetto: Re: [Fiware-lab-help] FI-Lab Assistance - Are we community? Datenfreunde UG Hello FiWare Lab Help, I've not been successful in reaching my public IP. Please see diagnostics below - traceroute finds it, but ping and ssh do not. What am I missing? Cheers, MV mvirtel@nyx:~$ traceroute 130.206.126.244 traceroute to 130.206.126.244 (130.206.126.244), 30 hops max, 60 byte packets 1 1.64.238.89.in-addr.arpa.manitu.net< http://1.64.238.89.in-addr.arpa.manitu.net > (89.238.64.1) 0.203 ms 0.181 ms 0.170 ms 2 inexio1.gw.network.manitu.net< http://inexio1.gw.network.manitu.net > (89.238.127.46) 4.577 ms 4.584 ms 4.550 ms 3 ae61.edge4.Frankfurt1.Level3.net< http://ae61.edge4.Frankfurt1.Level3.net > (212.162.5.201) 11.137 ms 4.502 ms 4.630 ms 4 ae-14-14.bar1.Madrid2.Level3.net< http://ae-14-14.bar1.Madrid2.Level3.net > (4.69.158.169) 34.545 ms ae-13-13.bar1.Madrid2.Level3.net< http://ae-13-13.bar1.Madrid2.Level3.net > (4.69.158.165) 34.525 ms ae-12-12.bar1.Madrid2.Level3.net< http://ae-12-12.bar1.Madrid2.Level3.net > (4.69.158.161) 34.534 ms 5 213.242.113.78 (213.242.113.78) 34.534 ms 34.570 ms 34.504 ms 6 TELMADI.AE1.ciemat.rt1.mad.red.rediris.es< http://TELMADI.AE1.ciemat.rt1.mad.red.rediris.es > (130.206.245.1) 33.737 ms 33.784 ms 33.797 ms 7 CIEMAT.XE4-1-0.telmad.rt6.mad.red.rediris.es< http://CIEMAT.XE4-1-0.telmad.rt6.mad.red.rediris.es > (130.206.245.46) 34.384 ms 34.245 ms 34.284 ms 8 130.206.192.158 (130.206.192.158) 34.790 ms 34.771 ms 34.764 ms 9 130.206.126.244 (130.206.126.244) 3050.760 ms !H 3049.191 ms !H 3049.199 ms !H mvirtel@nyx:~$ ssh 130.206.126.244 ssh: connect to host 130.206.126.244 port 22: No route to host mvirtel@nyx:~$ ssh -v 130.206.126.244 OpenSSH_6.0p1 Debian-4+deb7u1, OpenSSL 1.0.1e 11 Feb 2013 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to 130.206.126.244 [130.206.126.244] port 22. debug1: connect to address 130.206.126.244 port 22: No route to host ssh: connect to host 130.206.126.244 port 22: No route to host mvirtel@nyx:~$ ping 130.206.126.244 PING 130.206.126.244 (130.206.126.244) 56(84) bytes of data. From 130.206.126.244 icmp_seq=1 Destination Host Unreachable From 130.206.126.244 icmp_seq=2 Destination Host Unreachable From 130.206.126.244 icmp_seq=3 Destination Host Unreachable From 130.206.126.244 icmp_seq=4 Destination Host Unreachable From 130.206.126.244 icmp_seq=5 Destination Host Unreachable From 130.206.126.244 icmp_seq=6 Destination Host Unreachable – Martin Virtel <martin.virtel@gmail.com< martin.virtel@gmail.com >> / @mvtango / +49/172/992 13 96 Current Projects: http://soglaubtberlin.de · http://lobbycloud.eu/ Liveblogging für dpa< http://www.dpa.de/Anmeldung-Whitepaper-01.1110.0.html > · http://ediciones.la22.org/laeconomista/ · http://twitter.com/roboreport Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente] Rispetta l'ambiente. Non stampare questa mail se non è necessario.

          People

          • Assignee:
            marcocipriani Marco Cipriani
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: