home.social

#cucm — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #cucm, aggregated by home.social.

fetched live
  1. Eben hat Netbox per Device Importer den Cisco ISR4451-X importiert.

    Erinnerungen werden wach...

    Hach!

    #cisco #cucm #UC #voip

  2. Eben hat Netbox per Device Importer den Cisco ISR4451-X importiert.

    Erinnerungen werden wach...

    Hach!

    #cisco #cucm #UC #voip

  3. Eben hat Netbox per Device Importer den Cisco ISR4451-X importiert.

    Erinnerungen werden wach...

    Hach!

    #cisco #cucm #UC #voip

  4. Eben hat Netbox per Device Importer den Cisco ISR4451-X importiert.

    Erinnerungen werden wach...

    Hach!

    #cisco #cucm #UC #voip

  5. Eben hat Netbox per Device Importer den Cisco ISR4451-X importiert.

    Erinnerungen werden wach...

    Hach!

    #cisco #cucm #UC #voip

  6. En 2026, Mines de Rayons, les Ateliers Nomades et la Maison des Familles de Torcy vous invite à profiter du programme #Vélo-égaux sur les territoires de la Communauté Urbaine Creusot Montceau et du Grand Autunois Morvan.
    Le programme offre un parcours complet vers la mobilité à vélo, sous réserve d’éligibilité :
    - Un diagnostic mobilité.
    - Des cours de vélo
    - Une initiation à la mécanique vélo
    - Un vélo issu d’une recyclerie.
    Le tout 100% pris en charge par le programme.

    Résidents ou acteurs du domaine social, suivez-nous pour rester informer.
    Première séances dès début avril !

    #CUCM #CCGAM #autun #LeCreusot #montceaulesmines

    youtube.com/watch?v=N6n3UKat-_g

  7. En 2026, Mines de Rayons, les Ateliers Nomades et la Maison des Familles de Torcy vous invite à profiter du programme #Vélo-égaux sur les territoires de la Communauté Urbaine Creusot Montceau et du Grand Autunois Morvan.
    Le programme offre un parcours complet vers la mobilité à vélo, sous réserve d’éligibilité :
    - Un diagnostic mobilité.
    - Des cours de vélo
    - Une initiation à la mécanique vélo
    - Un vélo issu d’une recyclerie.
    Le tout 100% pris en charge par le programme.

    Résidents ou acteurs du domaine social, suivez-nous pour rester informer.
    Première séances dès début avril !

    #CUCM #CCGAM #autun #LeCreusot #montceaulesmines

    youtube.com/watch?v=N6n3UKat-_g

  8. Achso… gestern auf ner #Cisco Veranstalting gewesen, wo es auch um Collab und Virtualisierung ging.

    #CUCM wird weiterhin nicht #KVM supporten. Unter anderem eine Uni hatte nach Proxmoxsupport gefragt.

    Ich würde annehmen, dass Cisco hier mittelfristig On-Prem Kunden verlieren wird. Nicht jeder Kunde ist bereitet parallel Nutanix für zu betreiben oder extra Hardware in Form von BE6k Servern dafür anzuschaffen noch stattdessen in die Cloud zu migrieren.

  9. Achso… gestern auf ner #Cisco Veranstalting gewesen, wo es auch um Collab und Virtualisierung ging.

    #CUCM wird weiterhin nicht #KVM supporten. Unter anderem eine Uni hatte nach Proxmoxsupport gefragt.

    Ich würde annehmen, dass Cisco hier mittelfristig On-Prem Kunden verlieren wird. Nicht jeder Kunde ist bereitet parallel Nutanix für zu betreiben oder extra Hardware in Form von BE6k Servern dafür anzuschaffen noch stattdessen in die Cloud zu migrieren.

  10. Achso… gestern auf ner #Cisco Veranstalting gewesen, wo es auch um Collab und Virtualisierung ging.

    #CUCM wird weiterhin nicht #KVM supporten. Unter anderem eine Uni hatte nach Proxmoxsupport gefragt.

    Ich würde annehmen, dass Cisco hier mittelfristig On-Prem Kunden verlieren wird. Nicht jeder Kunde ist bereitet parallel Nutanix für zu betreiben oder extra Hardware in Form von BE6k Servern dafür anzuschaffen noch stattdessen in die Cloud zu migrieren.

  11. Achso… gestern auf ner #Cisco Veranstalting gewesen, wo es auch um Collab und Virtualisierung ging.

    #CUCM wird weiterhin nicht #KVM supporten. Unter anderem eine Uni hatte nach Proxmoxsupport gefragt.

    Ich würde annehmen, dass Cisco hier mittelfristig On-Prem Kunden verlieren wird. Nicht jeder Kunde ist bereitet parallel Nutanix für zu betreiben oder extra Hardware in Form von BE6k Servern dafür anzuschaffen noch stattdessen in die Cloud zu migrieren.

  12. Achso… gestern auf ner #Cisco Veranstalting gewesen, wo es auch um Collab und Virtualisierung ging.

    #CUCM wird weiterhin nicht #KVM supporten. Unter anderem eine Uni hatte nach Proxmoxsupport gefragt.

    Ich würde annehmen, dass Cisco hier mittelfristig On-Prem Kunden verlieren wird. Nicht jeder Kunde ist bereitet parallel Nutanix für zu betreiben oder extra Hardware in Form von BE6k Servern dafür anzuschaffen noch stattdessen in die Cloud zu migrieren.

  13. Aktywnie wykorzystywana, krytyczna luka w Cisco Unified Communications

    Cisco załatało aktywnie wykorzystywaną, krytyczną podatność w produktach Unified Communications oraz Webex Calling Dedicated Instance. Problem dotyczy zarówno instalacji on-prem (CUCM), jak również chmurowego rozwiązania Webex Calling Dedicated Instance. Luka została oznaczona identyfikatorem CVE-2026-20045. W ramach oceny NIST NVD otrzymała wynik 9.8 w CVSS 3.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Sytuacja jest bardzo poważna....

    #WBiegu #Cisco #Critical #Cucm #Rce

    sekurak.pl/aktywnie-wykorzysty

  14. Aktywnie wykorzystywana, krytyczna luka w Cisco Unified Communications

    Cisco załatało aktywnie wykorzystywaną, krytyczną podatność w produktach Unified Communications oraz Webex Calling Dedicated Instance. Problem dotyczy zarówno instalacji on-prem (CUCM), jak również chmurowego rozwiązania Webex Calling Dedicated Instance. Luka została oznaczona identyfikatorem CVE-2026-20045. W ramach oceny NIST NVD otrzymała wynik 9.8 w CVSS 3.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Sytuacja jest bardzo poważna....

    #WBiegu #Cisco #Critical #Cucm #Rce

    sekurak.pl/aktywnie-wykorzysty

  15. Aktywnie wykorzystywana, krytyczna luka w Cisco Unified Communications

    Cisco załatało aktywnie wykorzystywaną, krytyczną podatność w produktach Unified Communications oraz Webex Calling Dedicated Instance. Problem dotyczy zarówno instalacji on-prem (CUCM), jak również chmurowego rozwiązania Webex Calling Dedicated Instance. Luka została oznaczona identyfikatorem CVE-2026-20045. W ramach oceny NIST NVD otrzymała wynik 9.8 w CVSS 3.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Sytuacja jest bardzo poważna....

    #WBiegu #Cisco #Critical #Cucm #Rce

    sekurak.pl/aktywnie-wykorzysty

  16. Aktywnie wykorzystywana, krytyczna luka w Cisco Unified Communications

    Cisco załatało aktywnie wykorzystywaną, krytyczną podatność w produktach Unified Communications oraz Webex Calling Dedicated Instance. Problem dotyczy zarówno instalacji on-prem (CUCM), jak również chmurowego rozwiązania Webex Calling Dedicated Instance. Luka została oznaczona identyfikatorem CVE-2026-20045. W ramach oceny NIST NVD otrzymała wynik 9.8 w CVSS 3.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Sytuacja jest bardzo poważna....

    #WBiegu #Cisco #Critical #Cucm #Rce

    sekurak.pl/aktywnie-wykorzysty

  17. Aktywnie wykorzystywana, krytyczna luka w Cisco Unified Communications

    Cisco załatało aktywnie wykorzystywaną, krytyczną podatność w produktach Unified Communications oraz Webex Calling Dedicated Instance. Problem dotyczy zarówno instalacji on-prem (CUCM), jak również chmurowego rozwiązania Webex Calling Dedicated Instance. Luka została oznaczona identyfikatorem CVE-2026-20045. W ramach oceny NIST NVD otrzymała wynik 9.8 w CVSS 3.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Sytuacja jest bardzo poważna....

    #WBiegu #Cisco #Critical #Cucm #Rce

    sekurak.pl/aktywnie-wykorzysty

  18. This weekend I am upgrading a Cisco #CUCM cluster from 12.5 to 15 using the "fresh install and data import" method. The biggest stumbling block so far has been that I made a typo in the IP address of the gateway for one of the nodes.

  19. This weekend I am upgrading a Cisco #CUCM cluster from 12.5 to 15 using the "fresh install and data import" method. The biggest stumbling block so far has been that I made a typo in the IP address of the gateway for one of the nodes.

  20. Phomes

    mastodon app wont let me add alt text so in order:

    Cisco 8841
    Avaya K175 running home assistant
    NEC DT800
    wide shot with avaya j169, Avaya k175, poly vvx410, Cisco 7962, Nortel 1140e, Avaya 9641GS

    running #cisco #cucm - #avaya aura and IP office - #nec sv9100 and #microsoft #lync (for the vvx410 on Skype for business firmware)

  21. Phomes

    mastodon app wont let me add alt text so in order:

    Cisco 8841
    Avaya K175 running home assistant
    NEC DT800
    wide shot with avaya j169, Avaya k175, poly vvx410, Cisco 7962, Nortel 1140e, Avaya 9641GS

    running #cisco #cucm - #avaya aura and IP office - #nec sv9100 and #microsoft #lync (for the vvx410 on Skype for business firmware)

  22. Phomes

    mastodon app wont let me add alt text so in order:

    Cisco 8841
    Avaya K175 running home assistant
    NEC DT800
    wide shot with avaya j169, Avaya k175, poly vvx410, Cisco 7962, Nortel 1140e, Avaya 9641GS

    running #cisco #cucm - #avaya aura and IP office - #nec sv9100 and #microsoft #lync (for the vvx410 on Skype for business firmware)

  23. Phomes

    mastodon app wont let me add alt text so in order:

    Cisco 8841
    Avaya K175 running home assistant
    NEC DT800
    wide shot with avaya j169, Avaya k175, poly vvx410, Cisco 7962, Nortel 1140e, Avaya 9641GS

    running #cisco #cucm - #avaya aura and IP office - #nec sv9100 and #microsoft #lync (for the vvx410 on Skype for business firmware)

  24. Phomes

    mastodon app wont let me add alt text so in order:

    Cisco 8841
    Avaya K175 running home assistant
    NEC DT800
    wide shot with avaya j169, Avaya k175, poly vvx410, Cisco 7962, Nortel 1140e, Avaya 9641GS

    running #cisco #cucm - #avaya aura and IP office - #nec sv9100 and #microsoft #lync (for the vvx410 on Skype for business firmware)

  25. #BSI WID-SEC-2024-3356: [NEU] [mittel] #Cisco ##Unified ##Communications ##Manager #IM & #Presence #Service #und Unified Communications Manager (#CUCM): Mehrere Schwachstellen

    Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Cisco Unified Communications Manager IM & Presence Service und Cisco Unified Communications Manager (CUCM) ausnutzen, um Informationen offenzulegen oder einen Cross-Site-Scripting-Angriff durchzuführen.

    wid.cert-bund.de/portal/wid/se

  26. #BSI WID-SEC-2024-3356: [NEU] [mittel] #Cisco ##Unified ##Communications ##Manager #IM & #Presence #Service #und Unified Communications Manager (#CUCM): Mehrere Schwachstellen

    Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Cisco Unified Communications Manager IM & Presence Service und Cisco Unified Communications Manager (CUCM) ausnutzen, um Informationen offenzulegen oder einen Cross-Site-Scripting-Angriff durchzuführen.

    wid.cert-bund.de/portal/wid/se

  27. Is there a special config option in ntpsec or similar to make it work with #Cisco #CUCM #NTP requirements?

    I tried ntpsec, chrony, ntp on pfsence, a FritzBox 7490, UI DreamMachine Pro and ntp on a Cisco 2970C switch. No luck so far yet.

  28. Is there a special config option in ntpsec or similar to make it work with #Cisco #CUCM #NTP requirements?

    I tried ntpsec, chrony, ntp on pfsence, a FritzBox 7490, UI DreamMachine Pro and ntp on a Cisco 2970C switch. No luck so far yet.

  29. Is there a special config option in ntpsec or similar to make it work with #Cisco #CUCM #NTP requirements?

    I tried ntpsec, chrony, ntp on pfsence, a FritzBox 7490, UI DreamMachine Pro and ntp on a Cisco 2970C switch. No luck so far yet.

  30. Is there a special config option in ntpsec or similar to make it work with #Cisco #CUCM #NTP requirements?

    I tried ntpsec, chrony, ntp on pfsence, a FritzBox 7490, UI DreamMachine Pro and ntp on a Cisco 2970C switch. No luck so far yet.

  31. Is there a special config option in ntpsec or similar to make it work with #Cisco #CUCM #NTP requirements?

    I tried ntpsec, chrony, ntp on pfsence, a FritzBox 7490, UI DreamMachine Pro and ntp on a Cisco 2970C switch. No luck so far yet.

  32. Dear #followerpower,

    especially those with experience in Cisco Unified Communication:

    When installing #Cisco #CUCM #Callmanager, the installer requests a #NTP server. But neither ntpsec on Debian 12 nor openntp nor the ntp service on pfSense seems suitable for the CUCM installer as it reports "inaccessible".
    Sometimes (on first try) it reports "accesible", though. I suspect the kod setting, maybe.

    Any advice is welcome! 🙂

    :boost_ok:

  33. Dear #followerpower,

    especially those with experience in Cisco Unified Communication:

    When installing #Cisco #CUCM #Callmanager, the installer requests a #NTP server. But neither ntpsec on Debian 12 nor openntp nor the ntp service on pfSense seems suitable for the CUCM installer as it reports "inaccessible".
    Sometimes (on first try) it reports "accesible", though. I suspect the kod setting, maybe.

    Any advice is welcome! 🙂

    :boost_ok:

  34. Dear #followerpower,

    especially those with experience in Cisco Unified Communication:

    When installing #Cisco #CUCM #Callmanager, the installer requests a #NTP server. But neither ntpsec on Debian 12 nor openntp nor the ntp service on pfSense seems suitable for the CUCM installer as it reports "inaccessible".
    Sometimes (on first try) it reports "accesible", though. I suspect the kod setting, maybe.

    Any advice is welcome! 🙂

    :boost_ok:

  35. Dear #followerpower,

    especially those with experience in Cisco Unified Communication:

    When installing #Cisco #CUCM #Callmanager, the installer requests a #NTP server. But neither ntpsec on Debian 12 nor openntp nor the ntp service on pfSense seems suitable for the CUCM installer as it reports "inaccessible".
    Sometimes (on first try) it reports "accesible", though. I suspect the kod setting, maybe.

    Any advice is welcome! 🙂

    :boost_ok:

  36. Dear #followerpower,

    especially those with experience in Cisco Unified Communication:

    When installing #Cisco #CUCM #Callmanager, the installer requests a #NTP server. But neither ntpsec on Debian 12 nor openntp nor the ntp service on pfSense seems suitable for the CUCM installer as it reports "inaccessible".
    Sometimes (on first try) it reports "accesible", though. I suspect the kod setting, maybe.

    Any advice is welcome! 🙂

    :boost_ok:

  37. For those of you following #CVE CVE-2024-20253, note that #cisco have released a small patch for affected #callmanager systems overnight. As such you shouldn't need to do full updates to fixed versions to remediate so long as you're running 12.5(1) or higher.

    sec.cloudapps.cisco.com/securi has been updated to reflect the new patches for #cucm #imp#cuc #ucce #uccx and #vvb

  38. For those of you following #CVE CVE-2024-20253, note that #cisco have released a small patch for affected #callmanager systems overnight. As such you shouldn't need to do full updates to fixed versions to remediate so long as you're running 12.5(1) or higher.

    sec.cloudapps.cisco.com/securi has been updated to reflect the new patches for #cucm #imp#cuc #ucce #uccx and #vvb

  39. For those of you following #CVE CVE-2024-20253, note that #cisco have released a small patch for affected #callmanager systems overnight. As such you shouldn't need to do full updates to fixed versions to remediate so long as you're running 12.5(1) or higher.

    sec.cloudapps.cisco.com/securi has been updated to reflect the new patches for #cucm #imp#cuc #ucce #uccx and #vvb

  40. For those of you following #CVE CVE-2024-20253, note that #cisco have released a small patch for affected #callmanager systems overnight. As such you shouldn't need to do full updates to fixed versions to remediate so long as you're running 12.5(1) or higher.

    sec.cloudapps.cisco.com/securi has been updated to reflect the new patches for #cucm #imp#cuc #ucce #uccx and #vvb

  41. Today is going to be a looooong day spent looking at progress bars #cisco #callmanager #cucm

  42. Today is going to be a looooong day spent looking at progress bars #cisco #callmanager #cucm

  43. Today is going to be a looooong day spent looking at progress bars #cisco #callmanager #cucm

  44. Today is going to be a looooong day spent looking at progress bars #cisco #callmanager #cucm

  45. Unbelievably, building IVRs in #msTeams is even more of a PITA than it was on #CUCM. Every layer needs it’s own Auto Attendant voice app, which requires a licensed resource account. It's just such a faff to do manually. Really need to get this scripted and automated…

  46. Unbelievably, building IVRs in #msTeams is even more of a PITA than it was on #CUCM. Every layer needs it’s own Auto Attendant voice app, which requires a licensed resource account. It's just such a faff to do manually. Really need to get this scripted and automated…

  47. Unbelievably, building IVRs in #msTeams is even more of a PITA than it was on #CUCM. Every layer needs it’s own Auto Attendant voice app, which requires a licensed resource account. It's just such a faff to do manually. Really need to get this scripted and automated…

  48. Unbelievably, building IVRs in #msTeams is even more of a PITA than it was on #CUCM. Every layer needs it’s own Auto Attendant voice app, which requires a licensed resource account. It's just such a faff to do manually. Really need to get this scripted and automated…

  49. #SAML is nice in theory, but in practice it's pretty painful to work around the various different implementations. Currently we're troubleshooting a #Shibboleth IDP metadata file that #Webex was perfectly happy with, but which #Cisco #CUCM and #CUC don't seem to like.

  50. #SAML is nice in theory, but in practice it's pretty painful to work around the various different implementations. Currently we're troubleshooting a #Shibboleth IDP metadata file that #Webex was perfectly happy with, but which #Cisco #CUCM and #CUC don't seem to like.

  51. I've run one-off SQL commands against our #CUCM in the past, almost always reads. Today was the first time I did a batch update of data on a live system. Something of a rite-of-passage, but sad that it's as part of migrating our users to #msTeams 😕

  52. I've run one-off SQL commands against our #CUCM in the past, almost always reads. Today was the first time I did a batch update of data on a live system. Something of a rite-of-passage, but sad that it's as part of migrating our users to #msTeams 😕