Re: [cisco-voip] Old phone models dropped from CUCM 11.5
Interesting. I just started getting a bunch of 7912's boxed up for surplus. I hope we get some more warning when they axe the 7960 model. On Thu, Jun 9, 2016 at 6:55 PM, Stephen Welsh wrote: > Wow, formally dropping phone support from CUCM in 11.5, I assume this > means the models listed will not register... > > > http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/11_5_1/cucm_b_release-notes-cucm-imp-1151/cucm_b_release-notes-cucm-imp-1151_chapter_01.html > > Also, > Very grateful for the MigrationFX ‘plug’ in the CUCM release notes ;) > > FYI: MigrationFX now includes the ability to provision new phones too > (similar to TAPS but no IVR/UCCX, a simple XML service instead), BAT import > the phone details with dummy MAC addresses, use the Migration XML phone > service on the newly plugged in handset (i.e. auto registered with Idle URL > via Universal Device Template). Using the XML service search for the users > extension then MigrationFX will rename the matching BAT device to the MAC > address of the new phone. It will even migrate if the model of the new > phone does not match the BAT import, so more flexibility on deploy handsets > than TAPS. > > We also have some new MigrationFX functionality due for release at Cisco > Live, we shall publish the details in due course, but if you are curious > drop me a line or come and say hello. > > Kind Regards > > Stephen Welsh > CTO > UnifiedFX > > Come along and meet the UnifiedFX team > World of Solutions stand T2 > > > > ___ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip > > -- Ed Leatherman ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] Old phone models dropped from CUCM 11.5
SynApps has a supported device pack you can use that doesn’t count for licensing Matthew G. Loraditch – CCNP-Voice, CCNA-R&S, CCDA Network Engineer Direct Voice: 443.541.1518 Facebook<https://www.facebook.com/heliontech?ref=hl> | Twitter<https://twitter.com/HelionTech> | LinkedIn<https://www.linkedin.com/company/helion-technologies?trk=top_nav_home> | G+<https://plus.google.com/+Heliontechnologies/posts> From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of NateCCIE Sent: Thursday, June 9, 2016 10:15 PM To: 'Lelio Fulgenzi' ; 'Cisco VoIP Group' Subject: Re: [cisco-voip] Old phone models dropped from CUCM 11.5 Yeah, you wonder why it took so long. I will stop doing Cisco Communications Manager when they stop supporting my favorite phone, the 7911. I do wonder what happens to Syn-Apps’ SA-Announce software. They use VIP30 virtual phones, which I don’t like anyways because it takes a UCL ENH license for each of them. Thanks, -Nate VanMaren, CCIE #7911 From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Lelio Fulgenzi Sent: Thursday, June 09, 2016 6:08 PM To: Cisco VoIP Group mailto:cisco-voip@puck.nether.net>> Subject: Re: [cisco-voip] Old phone models dropped from CUCM 11.5 Whoa. I think this is the first time they've actually said they'll stop working. Sent from my iPhone On Jun 9, 2016, at 6:55 PM, Stephen Welsh mailto:stephen.we...@unifiedfx.com>> wrote: Wow, formally dropping phone support from CUCM in 11.5, I assume this means the models listed will not register... http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/11_5_1/cucm_b_release-notes-cucm-imp-1151/cucm_b_release-notes-cucm-imp-1151_chapter_01.html Also, Very grateful for the MigrationFX ‘plug’ in the CUCM release notes ;) FYI: MigrationFX now includes the ability to provision new phones too (similar to TAPS but no IVR/UCCX, a simple XML service instead), BAT import the phone details with dummy MAC addresses, use the Migration XML phone service on the newly plugged in handset (i.e. auto registered with Idle URL via Universal Device Template). Using the XML service search for the users extension then MigrationFX will rename the matching BAT device to the MAC address of the new phone. It will even migrate if the model of the new phone does not match the BAT import, so more flexibility on deploy handsets than TAPS. We also have some new MigrationFX functionality due for release at Cisco Live, we shall publish the details in due course, but if you are curious drop me a line or come and say hello. Kind Regards Stephen Welsh CTO UnifiedFX Come along and meet the UnifiedFX team World of Solutions stand T2 ___ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] Old phone models dropped from CUCM 11.5
Yeah, you wonder why it took so long. I will stop doing Cisco Communications Manager when they stop supporting my favorite phone, the 7911. I do wonder what happens to Syn-Apps’ SA-Announce software. They use VIP30 virtual phones, which I don’t like anyways because it takes a UCL ENH license for each of them. Thanks, -Nate VanMaren, CCIE #7911 From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Lelio Fulgenzi Sent: Thursday, June 09, 2016 6:08 PM To: Cisco VoIP Group Subject: Re: [cisco-voip] Old phone models dropped from CUCM 11.5 Whoa. I think this is the first time they've actually said they'll stop working. Sent from my iPhone On Jun 9, 2016, at 6:55 PM, Stephen Welsh mailto:stephen.we...@unifiedfx.com> > wrote: Wow, formally dropping phone support from CUCM in 11.5, I assume this means the models listed will not register... http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/11_5_1/cucm_b_release-notes-cucm-imp-1151/cucm_b_release-notes-cucm-imp-1151_chapter_01.html Also, Very grateful for the MigrationFX ‘plug’ in the CUCM release notes ;) FYI: MigrationFX now includes the ability to provision new phones too (similar to TAPS but no IVR/UCCX, a simple XML service instead), BAT import the phone details with dummy MAC addresses, use the Migration XML phone service on the newly plugged in handset (i.e. auto registered with Idle URL via Universal Device Template). Using the XML service search for the users extension then MigrationFX will rename the matching BAT device to the MAC address of the new phone. It will even migrate if the model of the new phone does not match the BAT import, so more flexibility on deploy handsets than TAPS. We also have some new MigrationFX functionality due for release at Cisco Live, we shall publish the details in due course, but if you are curious drop me a line or come and say hello. Kind Regards Stephen Welsh CTO UnifiedFX Come along and meet the UnifiedFX team World of Solutions stand T2 ___ cisco-voip mailing list cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] Old phone models dropped from CUCM 11.5
Whoa. I think this is the first time they've actually said they'll stop working. Sent from my iPhone > On Jun 9, 2016, at 6:55 PM, Stephen Welsh wrote: > > Wow, formally dropping phone support from CUCM in 11.5, I assume this means > the models listed will not register... > > http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/11_5_1/cucm_b_release-notes-cucm-imp-1151/cucm_b_release-notes-cucm-imp-1151_chapter_01.html > > Also, > Very grateful for the MigrationFX ‘plug’ in the CUCM release notes ;) > > FYI: MigrationFX now includes the ability to provision new phones too > (similar to TAPS but no IVR/UCCX, a simple XML service instead), BAT import > the phone details with dummy MAC addresses, use the Migration XML phone > service on the newly plugged in handset (i.e. auto registered with Idle URL > via Universal Device Template). Using the XML service search for the users > extension then MigrationFX will rename the matching BAT device to the MAC > address of the new phone. It will even migrate if the model of the new phone > does not match the BAT import, so more flexibility on deploy handsets than > TAPS. > > We also have some new MigrationFX functionality due for release at Cisco > Live, we shall publish the details in due course, but if you are curious drop > me a line or come and say hello. > > Kind Regards > > Stephen Welsh > CTO > UnifiedFX > > Come along and meet the UnifiedFX team > World of Solutions stand T2 > > > ___ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
[cisco-voip] Old phone models dropped from CUCM 11.5
Wow, formally dropping phone support from CUCM in 11.5, I assume this means the models listed will not register... http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/11_5_1/cucm_b_release-notes-cucm-imp-1151/cucm_b_release-notes-cucm-imp-1151_chapter_01.html Also, Very grateful for the MigrationFX ‘plug’ in the CUCM release notes ;) FYI: MigrationFX now includes the ability to provision new phones too (similar to TAPS but no IVR/UCCX, a simple XML service instead), BAT import the phone details with dummy MAC addresses, use the Migration XML phone service on the newly plugged in handset (i.e. auto registered with Idle URL via Universal Device Template). Using the XML service search for the users extension then MigrationFX will rename the matching BAT device to the MAC address of the new phone. It will even migrate if the model of the new phone does not match the BAT import, so more flexibility on deploy handsets than TAPS. We also have some new MigrationFX functionality due for release at Cisco Live, we shall publish the details in due course, but if you are curious drop me a line or come and say hello. Kind Regards Stephen Welsh CTO UnifiedFX Come along and meet the UnifiedFX team World of Solutions stand T2 ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
