> Being that Jabber tethers to your own controlled device without a specific > CSF specified, what use case would extension mobility fulfill that jabber > itself wouldn?t?
To me that use case would be a multi-use workstation. Jabber stores all the prefs and history locally, so to switch users results in having to reset all of that. That's pretty annoying. Adam -----Original Message----- From: cisco-voip <[email protected]> On Behalf Of [email protected] Sent: Tuesday, April 3, 2018 12:00 PM To: [email protected] Subject: cisco-voip Digest, Vol 174, Issue 3 Send cisco-voip mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://puck.nether.net/mailman/listinfo/cisco-voip or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of cisco-voip digest..." Today's Topics: 1. Re: Log Parser for RTMT (Kent Roberts) 2. Re: Log Parser for RTMT (Stephen Welsh) 3. Re: Log Parser for RTMT (Kent Roberts) 4. Re: Jabber Multiline is Here (Lelio Fulgenzi) 5. Re: Jabber Multiline is Here (Brian Meade) 6. Re: Jabber Multiline is Here (Lelio Fulgenzi) 7. Re: Jabber Multiline is Here (Ben Amick) 8. Re: Log Parser for RTMT (Ben Amick) 9. Re: Jabber Multiline is Here (Matthew Loraditch) 10. Re: Jabber Multiline is Here (Ben Amick) 11. Re: Jabber Multiline is Here (Brian Meade) 12. Re: CUCM Pre-Upgrade Checklist (Winstrand, Kenneth) 13. Re: Jabber Multiline is Here (Pawlowski, Adam) 14. Re: CUCM Pre-Upgrade Checklist (Ryan Huff) 15. Re: Jabber Multiline is Here (Sebastian Hagedorn) 16. Re: Jabber Multiline is Here (Matthew Loraditch) ---------------------------------------------------------------------- Message: 1 Date: Mon, 2 Apr 2018 10:20:23 -0600 From: Kent Roberts <[email protected]> To: Kent Roberts <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Re: [cisco-voip] Log Parser for RTMT Message-ID: <cantqhpacs73p-ga12ccduvzjh5yrfkdqpti0wrahb3t-6ij...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Sorry All, It appears the linux server and windows and upper/lower case link bit me. http://www.projecttesn.org/CKRParse4rtmt.exe <http://www.projecttesn.org/ckrparse4rtmt.exe> I seem to be running into the same problem as the person with the AXL app was doing and antivirus. Is there a way to let the program run without being signed? Thanks On Fri, Mar 30, 2018 at 9:26 PM, Kent Roberts <[email protected]> wrote: > Hi all. > > So I am one of the few people that have worked with CUCM since Cisco > started with CallManager, back in 2000?s. As such, there is one thing that > I have always hated, and that was reading the logs cause there is just > soooooo much stuff there. > > I wrote a set of scrips a couple years ago, that is designed to parse the > RTMT logs from CUCM and return only data based on the call. > > After a few people begging for a copy of it, I decided to make it a real > program. > > If you find it useful, please contribute to my tax deductible non-profit. > (Facebook has an easy donation program. Https://www.facebook.com/ > projecttesn) > > > If you have Ideas for other stuff you would like to see let me know, I > will see what I can do. > > > So the program works or should work like the following. (It is beta > right now, as I am trying to make it self contained instead of scrips) > > Put in the ANI or DNIS. (Right now I know the extension on cucm works, > not sure about the other side yet). Or the SIP ID. (This might be hit > or miss at the moment) > > Push the button to start. Select the location of the RTMT files. (Gz?s > are ok, it will unpack them) > > It will create a -output on the end of the path you provide with the data. > > It will collect the calllog files, and put the revenant data into a > file. Once it finds matches it will start to assemble the data into a > file, and copy the SDL files that are tied to it. > > The goal is to get only the data related to the call provided, so tracking > down what went on is much easier. > > Once complete, you can or should be able to load the file with translatorx > and have a smaller file to work with. > > Find it here. Please note, I have restricted the running time, as it > will need some updates. Please feel free to help me make it better. If > its negative feedback, please don?t bother. > > http://www.projecttesn.org/ckrparse4rtmt.exe > > FYI. This is running with a test CERT, and right now not signed, so > windows defender may pop up and Symantec will have a cow?. Put should not > be any worries. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/30534e93/attachment-0001.html> ------------------------------ Message: 2 Date: Mon, 2 Apr 2018 16:27:22 +0000 From: Stephen Welsh <[email protected]> To: Kent Roberts <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Re: [cisco-voip] Log Parser for RTMT Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" If you publish an EXE for direct download it pretty much has to be signed, even in our case we publish an MSI and it?s signed too. If you zip the exe it might make the download easier as I belie the zip file will be blocked which is easier to ?unblock? than the hassle/cost of getting a signing certificate. Thanks to the constant threat of viruses its hassle to publish software for download ;) Thanks Stephen Welsh CTO UnifiedFX On 2 Apr 2018, at 17:20, Kent Roberts <[email protected]<mailto:[email protected]>> wrote: Sorry All, It appears the linux server and windows and upper/lower case link bit me. http://www.projecttesn.org/CKRParse4rtmt.exe<http://www.projecttesn.org/ckrparse4rtmt.exe> I seem to be running into the same problem as the person with the AXL app was doing and antivirus. Is there a way to let the program run without being signed? Thanks On Fri, Mar 30, 2018 at 9:26 PM, Kent Roberts <[email protected]<mailto:[email protected]>> wrote: Hi all. So I am one of the few people that have worked with CUCM since Cisco started with CallManager, back in 2000?s. As such, there is one thing that I have always hated, and that was reading the logs cause there is just soooooo much stuff there. I wrote a set of scrips a couple years ago, that is designed to parse the RTMT logs from CUCM and return only data based on the call. After a few people begging for a copy of it, I decided to make it a real program. If you find it useful, please contribute to my tax deductible non-profit. (Facebook has an easy donation program. Https://www.facebook.com/projecttesn<https://www.facebook.com/projecttesn>) If you have Ideas for other stuff you would like to see let me know, I will see what I can do. So the program works or should work like the following. (It is beta right now, as I am trying to make it self contained instead of scrips) Put in the ANI or DNIS. (Right now I know the extension on cucm works, not sure about the other side yet). Or the SIP ID. (This might be hit or miss at the moment) Push the button to start. Select the location of the RTMT files. (Gz?s are ok, it will unpack them) It will create a -output on the end of the path you provide with the data. It will collect the calllog files, and put the revenant data into a file. Once it finds matches it will start to assemble the data into a file, and copy the SDL files that are tied to it. The goal is to get only the data related to the call provided, so tracking down what went on is much easier. Once complete, you can or should be able to load the file with translatorx and have a smaller file to work with. Find it here. Please note, I have restricted the running time, as it will need some updates. Please feel free to help me make it better. If its negative feedback, please don?t bother. http://www.projecttesn.org/ckrparse4rtmt.exe FYI. This is running with a test CERT, and right now not signed, so windows defender may pop up and Symantec will have a cow?. Put should not be any worries. _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/3aafdb23/attachment-0001.html> ------------------------------ Message: 3 Date: Mon, 2 Apr 2018 10:40:20 -0600 From: Kent Roberts <[email protected]> To: Stephen Welsh <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Re: [cisco-voip] Log Parser for RTMT Message-ID: <CANtqHPbBksM=jktmc9-6uwqo9va5yvygjsza9-1tzl-a-_j...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Thank you, that seems to work www.projecttesn.org/CKRParse4rtmt.zip for now :)! On Mon, Apr 2, 2018 at 10:27 AM, Stephen Welsh <[email protected]> wrote: > If you publish an EXE for direct download it pretty much has to be signed, > even in our case we publish an MSI and it?s signed too. > > If you zip the exe it might make the download easier as I belie the zip > file will be blocked which is easier to ?unblock? than the hassle/cost of > getting a signing certificate. > > Thanks to the constant threat of viruses its hassle to publish software > for download ;) > > Thanks > > Stephen Welsh > CTO > UnifiedFX > > On 2 Apr 2018, at 17:20, Kent Roberts <[email protected]> wrote: > > Sorry All, It appears the linux server and windows and upper/lower case > link bit me. > > http://www.projecttesn.org/CKRParse4rtmt.exe > <http://www.projecttesn.org/ckrparse4rtmt.exe> > > I seem to be running into the same problem as the person with the AXL app > was doing and antivirus. Is there a way to let the program run without > being signed? > > Thanks > > > On Fri, Mar 30, 2018 at 9:26 PM, Kent Roberts <[email protected]> wrote: > >> Hi all. >> >> So I am one of the few people that have worked with CUCM since Cisco >> started with CallManager, back in 2000?s. As such, there is one thing that >> I have always hated, and that was reading the logs cause there is just >> soooooo much stuff there. >> >> I wrote a set of scrips a couple years ago, that is designed to parse the >> RTMT logs from CUCM and return only data based on the call. >> >> After a few people begging for a copy of it, I decided to make it a real >> program. >> >> If you find it useful, please contribute to my tax deductible non-profit. >> (Facebook has an easy donation program. Https://www.facebook.com/proj >> ecttesn <https://www.facebook.com/projecttesn>) >> >> >> If you have Ideas for other stuff you would like to see let me know, I >> will see what I can do. >> >> >> So the program works or should work like the following. (It is beta >> right now, as I am trying to make it self contained instead of scrips) >> >> Put in the ANI or DNIS. (Right now I know the extension on cucm works, >> not sure about the other side yet). Or the SIP ID. (This might be hit >> or miss at the moment) >> >> Push the button to start. Select the location of the RTMT files. (Gz?s >> are ok, it will unpack them) >> >> It will create a -output on the end of the path you provide with the data. >> >> It will collect the calllog files, and put the revenant data into a >> file. Once it finds matches it will start to assemble the data into a >> file, and copy the SDL files that are tied to it. >> >> The goal is to get only the data related to the call provided, so >> tracking down what went on is much easier. >> >> Once complete, you can or should be able to load the file with >> translatorx and have a smaller file to work with. >> >> Find it here. Please note, I have restricted the running time, as it >> will need some updates. Please feel free to help me make it better. If >> its negative feedback, please don?t bother. >> >> http://www.projecttesn.org/ckrparse4rtmt.exe >> >> FYI. This is running with a test CERT, and right now not signed, so >> windows defender may pop up and Symantec will have a cow?. Put should not >> be any worries. >> > > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/34746cdc/attachment-0001.html> ------------------------------ Message: 4 Date: Mon, 2 Apr 2018 17:43:03 +0000 From: Lelio Fulgenzi <[email protected]> To: Anthony Holloway <[email protected]>, Cisco VoIP Group <[email protected]> Subject: Re: [cisco-voip] Jabber Multiline is Here Message-ID: <ytxpr01mb06408b98f382e0a74791200bac...@ytxpr01mb0640.canprd01.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Let?s hope voicemail works with multi lines. ? --- Lelio Fulgenzi, B.A. | Senior Analyst Computing and Communications Services | University of Guelph Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1 519-824-4120 Ext. 56354 | [email protected]<mailto:[email protected]> www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook [University of Guelph Cornerstone with Improve Life tagline] From: cisco-voip [mailto:[email protected]] On Behalf Of Anthony Holloway Sent: Monday, April 2, 2018 10:44 AM To: Cisco VoIP Group <[email protected]> Subject: [cisco-voip] Jabber Multiline is Here Just in case you missed it, Jabber multiline made it into 12.0. You'll need to be on CUCM 11.5(1)SU4 and install a COP file to support it. Release Notes https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/12_0/RN/jabw_b_release-notes-for-cisco-jabber_12.html#reference_6CABFFC6E6E2B025EA1C691A8744962A Configuration Guide https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_0/cjab_b_feature-configuration-for-cisco-jabber-120/cjab_b_feature-configuration-for-cisco-jabber-120_chapter_011.html#reference_08DB2E9280C0A8ABF98E1B329604E883 Video Demo https://youtu.be/Cosfzf7XoBo -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/1a8aa840/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1297 bytes Desc: image001.png URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/1a8aa840/attachment-0001.png> ------------------------------ Message: 5 Date: Mon, 2 Apr 2018 14:04:52 -0400 From: Brian Meade <[email protected]> To: Lelio Fulgenzi <[email protected]> Cc: Anthony Holloway <[email protected]>, Cisco VoIP Group <[email protected]> Subject: Re: [cisco-voip] Jabber Multiline is Here Message-ID: <cagcuyh3tecfeg_9cp9x5orjqdjcls+soronxsqg_-hlxcfe...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Big holdup looks to be no multiline with MRA, still only single line there. The other big issue is no extension mobility support and UCCX is still enforcing their single device policy. I've been having some discussions with the Jabber/UCCX teams around this. Right now CIPC is EOL but I'm still having to do active deployments of it due to this issue as I'm sure many others are hitting. On Mon, Apr 2, 2018 at 1:43 PM, Lelio Fulgenzi <[email protected]> wrote: > Let?s hope voicemail works with multi lines. ? > > > > --- > > *Lelio Fulgenzi, B.A.* | Senior Analyst > > Computing and Communications Services | University of Guelph > > Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | > N1G 2W1 > > 519-824-4120 Ext. 56354 <(519)%20824-4120> | [email protected] > > > > www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook > > > > [image: University of Guelph Cornerstone with Improve Life tagline] > > > > *From:* cisco-voip [mailto:[email protected]] *On Behalf > Of *Anthony Holloway > *Sent:* Monday, April 2, 2018 10:44 AM > *To:* Cisco VoIP Group <[email protected]> > *Subject:* [cisco-voip] Jabber Multiline is Here > > > > Just in case you missed it, Jabber multiline made it into 12.0. You'll > need to be on CUCM 11.5(1)SU4 and install a COP file to support it. > > > > Release Notes > > https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/ > Windows/12_0/RN/jabw_b_release-notes-for-cisco-jabber_12.html#reference_ > 6CABFFC6E6E2B025EA1C691A8744962A > > > > Configuration Guide > > https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/ > 12_0/cjab_b_feature-configuration-for-cisco-jabber-120/cjab_b_feature- > configuration-for-cisco-jabber-120_chapter_011.html#reference_ > 08DB2E9280C0A8ABF98E1B329604E883 > > > > Video Demo > > https://youtu.be/Cosfzf7XoBo > > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/a207cbbd/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1297 bytes Desc: not available URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/a207cbbd/attachment-0001.png> ------------------------------ Message: 6 Date: Mon, 2 Apr 2018 18:17:40 +0000 From: Lelio Fulgenzi <[email protected]> To: Brian Meade <[email protected]> Cc: Anthony Holloway <[email protected]>, Cisco VoIP Group <[email protected]> Subject: Re: [cisco-voip] Jabber Multiline is Here Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" Aw. Snap. I read that part too quickly. Thought it _was_ supported via MRA. :( Sent from my iPhone On Apr 2, 2018, at 2:04 PM, Brian Meade <[email protected]<mailto:[email protected]>> wrote: Big holdup looks to be no multiline with MRA, still only single line there. The other big issue is no extension mobility support and UCCX is still enforcing their single device policy. I've been having some discussions with the Jabber/UCCX teams around this. Right now CIPC is EOL but I'm still having to do active deployments of it due to this issue as I'm sure many others are hitting. On Mon, Apr 2, 2018 at 1:43 PM, Lelio Fulgenzi <[email protected]<mailto:[email protected]>> wrote: Let?s hope voicemail works with multi lines. ? --- Lelio Fulgenzi, B.A. | Senior Analyst Computing and Communications Services | University of Guelph Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1 519-824-4120 Ext. 56354<tel:(519)%20824-4120> | [email protected]<mailto:[email protected]> www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook <image001.png> From: cisco-voip [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Anthony Holloway Sent: Monday, April 2, 2018 10:44 AM To: Cisco VoIP Group <[email protected]<mailto:[email protected]>> Subject: [cisco-voip] Jabber Multiline is Here Just in case you missed it, Jabber multiline made it into 12.0. You'll need to be on CUCM 11.5(1)SU4 and install a COP file to support it. Release Notes https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/12_0/RN/jabw_b_release-notes-for-cisco-jabber_12.html#reference_6CABFFC6E6E2B025EA1C691A8744962A Configuration Guide https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_0/cjab_b_feature-configuration-for-cisco-jabber-120/cjab_b_feature-configuration-for-cisco-jabber-120_chapter_011.html#reference_08DB2E9280C0A8ABF98E1B329604E883 Video Demo https://youtu.be/Cosfzf7XoBo _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/6d0784ac/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1297 bytes Desc: image001.png URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/6d0784ac/attachment-0001.png> ------------------------------ Message: 7 Date: Mon, 2 Apr 2018 18:41:03 +0000 From: Ben Amick <[email protected]> To: Brian Meade <[email protected]>, Lelio Fulgenzi <[email protected]> Cc: Cisco VoIP Group <[email protected]> Subject: Re: [cisco-voip] Jabber Multiline is Here Message-ID: <dm6pr19mb2316367162500be8e493666ab5...@dm6pr19mb2316.namprd19.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Brian, If you move to multiline on Jabber and decommission softphones/deskphones as a byproduct, what issue does that generate with UCCX? Being that Jabber tethers to your own controlled device without a specific CSF specified, what use case would extension mobility fulfill that jabber itself wouldn?t? Ben Amick Unified Communications Analyst From: cisco-voip <[email protected]> On Behalf Of Brian Meade Sent: Monday, April 2, 2018 2:05 PM To: Lelio Fulgenzi <[email protected]> Cc: Cisco VoIP Group <[email protected]> Subject: Re: [cisco-voip] Jabber Multiline is Here Security Notice: This is an EXTERNAL email. Please exercise caution and DO NOT open attachments or click links from unknown or unexpected senders. Big holdup looks to be no multiline with MRA, still only single line there. The other big issue is no extension mobility support and UCCX is still enforcing their single device policy. I've been having some discussions with the Jabber/UCCX teams around this. Right now CIPC is EOL but I'm still having to do active deployments of it due to this issue as I'm sure many others are hitting. On Mon, Apr 2, 2018 at 1:43 PM, Lelio Fulgenzi <[email protected]<mailto:[email protected]>> wrote: Let?s hope voicemail works with multi lines. ? --- Lelio Fulgenzi, B.A. | Senior Analyst Computing and Communications Services | University of Guelph Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1 519-824-4120 Ext. 56354<tel:(519)%20824-4120> | [email protected]<mailto:[email protected]> www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook [University of Guelph Cornerstone with Improve Life tagline] From: cisco-voip [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Anthony Holloway Sent: Monday, April 2, 2018 10:44 AM To: Cisco VoIP Group <[email protected]<mailto:[email protected]>> Subject: [cisco-voip] Jabber Multiline is Here Just in case you missed it, Jabber multiline made it into 12.0. You'll need to be on CUCM 11.5(1)SU4 and install a COP file to support it. Release Notes https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/12_0/RN/jabw_b_release-notes-for-cisco-jabber_12.html#reference_6CABFFC6E6E2B025EA1C691A8744962A Configuration Guide https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_0/cjab_b_feature-configuration-for-cisco-jabber-120/cjab_b_feature-configuration-for-cisco-jabber-120_chapter_011.html#reference_08DB2E9280C0A8ABF98E1B329604E883 Video Demo https://youtu.be/Cosfzf7XoBo _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip Disclaimer: The information contained in this transmission and any attachments may contain privileged and confidential information including patient information protected by federal and state privacy laws. This transmission is sent for the sole use of the intended recipient. If you are not the intended recipient, please immediately (1) notify the sender via reply email; (2) do not open or read the message or any attachments; and (3) delete this message and any attachments. The review, dissemination, distribution, or duplication of this transmission by anyone other than the intended recipient is strictly prohibited. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/4b7f1a40/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1297 bytes Desc: image001.png URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/4b7f1a40/attachment-0001.png> ------------------------------ Message: 8 Date: Mon, 2 Apr 2018 18:46:18 +0000 From: Ben Amick <[email protected]> To: Kent Roberts <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Re: [cisco-voip] Log Parser for RTMT Message-ID: <dm6pr19mb23160837da250b673c77a28eb5...@dm6pr19mb2316.namprd19.prod.outlook.com> Content-Type: text/plain; charset="utf-8" When the alert pops up, there?s a ?more options? link in the popup that when clicked will give you a ?Run Anyway? button. Ben Amick Unified Communications Analyst From: cisco-voip <[email protected]> On Behalf Of Kent Roberts Sent: Monday, April 2, 2018 12:20 PM To: Kent Roberts <[email protected]> Cc: [email protected] Subject: Re: [cisco-voip] Log Parser for RTMT Security Notice: This is an EXTERNAL email. Please exercise caution and DO NOT open attachments or click links from unknown or unexpected senders. Sorry All, It appears the linux server and windows and upper/lower case link bit me. http://www.projecttesn.org/CKRParse4rtmt.exe<http://www.projecttesn.org/ckrparse4rtmt.exe> I seem to be running into the same problem as the person with the AXL app was doing and antivirus. Is there a way to let the program run without being signed? Thanks On Fri, Mar 30, 2018 at 9:26 PM, Kent Roberts <[email protected]<mailto:[email protected]>> wrote: Hi all. So I am one of the few people that have worked with CUCM since Cisco started with CallManager, back in 2000?s. As such, there is one thing that I have always hated, and that was reading the logs cause there is just soooooo much stuff there. I wrote a set of scrips a couple years ago, that is designed to parse the RTMT logs from CUCM and return only data based on the call. After a few people begging for a copy of it, I decided to make it a real program. If you find it useful, please contribute to my tax deductible non-profit. (Facebook has an easy donation program. Https://www.facebook.com/projecttesn) If you have Ideas for other stuff you would like to see let me know, I will see what I can do. So the program works or should work like the following. (It is beta right now, as I am trying to make it self contained instead of scrips) Put in the ANI or DNIS. (Right now I know the extension on cucm works, not sure about the other side yet). Or the SIP ID. (This might be hit or miss at the moment) Push the button to start. Select the location of the RTMT files. (Gz?s are ok, it will unpack them) It will create a -output on the end of the path you provide with the data. It will collect the calllog files, and put the revenant data into a file. Once it finds matches it will start to assemble the data into a file, and copy the SDL files that are tied to it. The goal is to get only the data related to the call provided, so tracking down what went on is much easier. Once complete, you can or should be able to load the file with translatorx and have a smaller file to work with. Find it here. Please note, I have restricted the running time, as it will need some updates. Please feel free to help me make it better. If its negative feedback, please don?t bother. http://www.projecttesn.org/ckrparse4rtmt.exe FYI. This is running with a test CERT, and right now not signed, so windows defender may pop up and Symantec will have a cow?. Put should not be any worries. Disclaimer: The information contained in this transmission and any attachments may contain privileged and confidential information including patient information protected by federal and state privacy laws. This transmission is sent for the sole use of the intended recipient. If you are not the intended recipient, please immediately (1) notify the sender via reply email; (2) do not open or read the message or any attachments; and (3) delete this message and any attachments. The review, dissemination, distribution, or duplication of this transmission by anyone other than the intended recipient is strictly prohibited. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/d05d57a7/attachment-0001.html> ------------------------------ Message: 9 Date: Mon, 2 Apr 2018 18:47:46 +0000 From: Matthew Loraditch <[email protected]> To: Ben Amick <[email protected]>, Brian Meade <[email protected]>, "Lelio Fulgenzi" <[email protected]> Cc: Cisco VoIP Group <[email protected]> Subject: Re: [cisco-voip] Jabber Multiline is Here Message-ID: <dm2pr08mb461fed73a71b586d53931dab3...@dm2pr08mb461.namprd08.prod.outlook.com> Content-Type: text/plain; charset="utf-8" I?m going to presume my answer is the same as Brian?s but our Call Center staff all have hard phones at the office, but when they work from home they need to use a softphone. Since UCCX requires agent extensions only exist on one device, they have to use EM and Jabber doesn?t support EM so we have to provision them with CIPC for at home usage. Matthew Loraditch Sr. Network Engineer p: 443.541.1518 w: www.heliontechnologies.com | e: [email protected] From: cisco-voip <[email protected]> On Behalf Of Ben Amick Sent: Monday, April 2, 2018 2:41 PM To: Brian Meade <[email protected]>; Lelio Fulgenzi <[email protected]> Cc: Cisco VoIP Group <[email protected]> Subject: Re: [cisco-voip] Jabber Multiline is Here Brian, If you move to multiline on Jabber and decommission softphones/deskphones as a byproduct, what issue does that generate with UCCX? Being that Jabber tethers to your own controlled device without a specific CSF specified, what use case would extension mobility fulfill that jabber itself wouldn?t? Ben Amick Unified Communications Analyst From: cisco-voip <[email protected]<mailto:[email protected]>> On Behalf Of Brian Meade Sent: Monday, April 2, 2018 2:05 PM To: Lelio Fulgenzi <[email protected]<mailto:[email protected]>> Cc: Cisco VoIP Group <[email protected]<mailto:[email protected]>> Subject: Re: [cisco-voip] Jabber Multiline is Here Security Notice: This is an EXTERNAL email. Please exercise caution and DO NOT open attachments or click links from unknown or unexpected senders. Big holdup looks to be no multiline with MRA, still only single line there. The other big issue is no extension mobility support and UCCX is still enforcing their single device policy. I've been having some discussions with the Jabber/UCCX teams around this. Right now CIPC is EOL but I'm still having to do active deployments of it due to this issue as I'm sure many others are hitting. On Mon, Apr 2, 2018 at 1:43 PM, Lelio Fulgenzi <[email protected]<mailto:[email protected]>> wrote: Let?s hope voicemail works with multi lines. ? --- Lelio Fulgenzi, B.A. | Senior Analyst Computing and Communications Services | University of Guelph Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1 519-824-4120 Ext. 56354<tel:(519)%20824-4120> | [email protected]<mailto:[email protected]> www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook [University of Guelph Cornerstone with Improve Life tagline] From: cisco-voip [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Anthony Holloway Sent: Monday, April 2, 2018 10:44 AM To: Cisco VoIP Group <[email protected]<mailto:[email protected]>> Subject: [cisco-voip] Jabber Multiline is Here Just in case you missed it, Jabber multiline made it into 12.0. You'll need to be on CUCM 11.5(1)SU4 and install a COP file to support it. Release Notes https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/12_0/RN/jabw_b_release-notes-for-cisco-jabber_12.html#reference_6CABFFC6E6E2B025EA1C691A8744962A Configuration Guide https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_0/cjab_b_feature-configuration-for-cisco-jabber-120/cjab_b_feature-configuration-for-cisco-jabber-120_chapter_011.html#reference_08DB2E9280C0A8ABF98E1B329604E883 Video Demo https://youtu.be/Cosfzf7XoBo _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip Disclaimer: The information contained in this transmission and any attachments may contain privileged and confidential information including patient information protected by federal and state privacy laws. This transmission is sent for the sole use of the intended recipient. If you are not the intended recipient, please immediately (1) notify the sender via reply email; (2) do not open or read the message or any attachments; and (3) delete this message and any attachments. The review, dissemination, distribution, or duplication of this transmission by anyone other than the intended recipient is strictly prohibited. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/79b36f06/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1297 bytes Desc: image001.png URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/79b36f06/attachment-0005.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image948843.png Type: image/png Size: 8404 bytes Desc: image948843.png URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/79b36f06/attachment-0006.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image418627.png Type: image/png Size: 431 bytes Desc: image418627.png URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/79b36f06/attachment-0007.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image867261.png Type: image/png Size: 561 bytes Desc: image867261.png URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/79b36f06/attachment-0008.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image930159.png Type: image/png Size: 444 bytes Desc: image930159.png URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/79b36f06/attachment-0009.png> ------------------------------ Message: 10 Date: Mon, 2 Apr 2018 18:51:02 +0000 From: Ben Amick <[email protected]> To: Matthew Loraditch <[email protected]>, Brian Meade <[email protected]>, Lelio Fulgenzi <[email protected]> Cc: Cisco VoIP Group <[email protected]> Subject: Re: [cisco-voip] Jabber Multiline is Here Message-ID: <dm6pr19mb2316ede99efa83ffbd921ba0b5...@dm6pr19mb2316.namprd19.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Gotcha, so the issue only exists because of partial teleworking. Outside of supervisors in my environment everyone is either 100% telework or 100% in office so it?s never been a problem for us, and everyone just uses CIPC anyways outside of a few legacy desk phone deploys. Ben Amick Unified Communications Analyst From: Matthew Loraditch <[email protected]> Sent: Monday, April 2, 2018 2:48 PM To: Ben Amick <[email protected]>; Brian Meade <[email protected]>; Lelio Fulgenzi <[email protected]> Cc: Cisco VoIP Group <[email protected]> Subject: RE: [cisco-voip] Jabber Multiline is Here Security Notice: This is an EXTERNAL email. Please exercise caution and DO NOT open attachments or click links from unknown or unexpected senders. I?m going to presume my answer is the same as Brian?s but our Call Center staff all have hard phones at the office, but when they work from home they need to use a softphone. Since UCCX requires agent extensions only exist on one device, they have to use EM and Jabber doesn?t support EM so we have to provision them with CIPC for at home usage. Matthew Loraditch? Sr. Network Engineer p: 443.541.1518<tel:443.541.1518> w: www.heliontechnologies.com<http://www.heliontechnologies.com/> | e: [email protected]<mailto:[email protected]> [cid:[email protected]] [Facebook]<https://facebook.com/heliontech> [Twitter]<https://twitter.com/heliontech> [LinkedIn]<https://www.linkedin.com/company/helion-technologies> From: cisco-voip <[email protected]<mailto:[email protected]>> On Behalf Of Ben Amick Sent: Monday, April 2, 2018 2:41 PM To: Brian Meade <[email protected]<mailto:[email protected]>>; Lelio Fulgenzi <[email protected]<mailto:[email protected]>> Cc: Cisco VoIP Group <[email protected]<mailto:[email protected]>> Subject: Re: [cisco-voip] Jabber Multiline is Here Brian, If you move to multiline on Jabber and decommission softphones/deskphones as a byproduct, what issue does that generate with UCCX? Being that Jabber tethers to your own controlled device without a specific CSF specified, what use case would extension mobility fulfill that jabber itself wouldn?t? Ben Amick Unified Communications Analyst From: cisco-voip <[email protected]<mailto:[email protected]>> On Behalf Of Brian Meade Sent: Monday, April 2, 2018 2:05 PM To: Lelio Fulgenzi <[email protected]<mailto:[email protected]>> Cc: Cisco VoIP Group <[email protected]<mailto:[email protected]>> Subject: Re: [cisco-voip] Jabber Multiline is Here Security Notice: This is an EXTERNAL email. Please exercise caution and DO NOT open attachments or click links from unknown or unexpected senders. Big holdup looks to be no multiline with MRA, still only single line there. The other big issue is no extension mobility support and UCCX is still enforcing their single device policy. I've been having some discussions with the Jabber/UCCX teams around this. Right now CIPC is EOL but I'm still having to do active deployments of it due to this issue as I'm sure many others are hitting. On Mon, Apr 2, 2018 at 1:43 PM, Lelio Fulgenzi <[email protected]<mailto:[email protected]>> wrote: Let?s hope voicemail works with multi lines. ? --- Lelio Fulgenzi, B.A. | Senior Analyst Computing and Communications Services | University of Guelph Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1 519-824-4120 Ext. 56354<tel:(519)%20824-4120> | [email protected]<mailto:[email protected]> www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook [University of Guelph Cornerstone with Improve Life tagline] From: cisco-voip [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Anthony Holloway Sent: Monday, April 2, 2018 10:44 AM To: Cisco VoIP Group <[email protected]<mailto:[email protected]>> Subject: [cisco-voip] Jabber Multiline is Here Just in case you missed it, Jabber multiline made it into 12.0. You'll need to be on CUCM 11.5(1)SU4 and install a COP file to support it. Release Notes https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/12_0/RN/jabw_b_release-notes-for-cisco-jabber_12.html#reference_6CABFFC6E6E2B025EA1C691A8744962A Configuration Guide https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_0/cjab_b_feature-configuration-for-cisco-jabber-120/cjab_b_feature-configuration-for-cisco-jabber-120_chapter_011.html#reference_08DB2E9280C0A8ABF98E1B329604E883 Video Demo https://youtu.be/Cosfzf7XoBo _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip Disclaimer: The information contained in this transmission and any attachments may contain privileged and confidential information including patient information protected by federal and state privacy laws. This transmission is sent for the sole use of the intended recipient. If you are not the intended recipient, please immediately (1) notify the sender via reply email; (2) do not open or read the message or any attachments; and (3) delete this message and any attachments. The review, dissemination, distribution, or duplication of this transmission by anyone other than the intended recipient is strictly prohibited. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/31c39260/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 8404 bytes Desc: image002.png URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/31c39260/attachment-0005.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 431 bytes Desc: image003.png URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/31c39260/attachment-0006.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 561 bytes Desc: image004.png URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/31c39260/attachment-0007.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 444 bytes Desc: image005.png URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/31c39260/attachment-0008.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 1297 bytes Desc: image006.png URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/31c39260/attachment-0009.png> ------------------------------ Message: 11 Date: Mon, 2 Apr 2018 14:55:28 -0400 From: Brian Meade <[email protected]> To: Ben Amick <[email protected]> Cc: Matthew Loraditch <[email protected]>, Lelio Fulgenzi <[email protected]>, Cisco VoIP Group <[email protected]> Subject: Re: [cisco-voip] Jabber Multiline is Here Message-ID: <cagcuyh0+qsxlzjdxmomnsrxjibzfbxhqydzjsgdo0i4ysod...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Yea, this is the issue. Almost all of my customers want agents to be able to work from home if possible so forces us to go full Jabber for agents or split desk phone and CIPC with extension mobility. Desk phone and CIPC seems to be the popular choice. On Mon, Apr 2, 2018 at 2:51 PM, Ben Amick <[email protected]> wrote: > Gotcha, so the issue only exists because of partial teleworking. Outside > of supervisors in my environment everyone is either 100% telework or 100% > in office so it?s never been a problem for us, and everyone just uses CIPC > anyways outside of a few legacy desk phone deploys. > > > > Ben Amick > > Unified Communications Analyst > > > > *From:* Matthew Loraditch <[email protected]> > *Sent:* Monday, April 2, 2018 2:48 PM > *To:* Ben Amick <[email protected]>; Brian Meade <[email protected]>; > Lelio Fulgenzi <[email protected]> > *Cc:* Cisco VoIP Group <[email protected]> > *Subject:* RE: [cisco-voip] Jabber Multiline is Here > > > > *Security Notice:* This is an EXTERNAL email. Please exercise caution and > DO NOT open attachments or click links from unknown or unexpected senders. > > I?m going to presume my answer is the same as Brian?s but our Call Center > staff all have hard phones at the office, but when they work from home they > need to use a softphone. Since UCCX requires agent extensions only exist on > one device, they have to use EM and Jabber doesn?t support EM so we have to > provision them with CIPC for at home usage. > > > > > > > > > > *Matthew Loraditch**?* > > *Sr. Network Engineer* > > p: *443.541.1518* <443.541.1518> > > w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/> > > | > > e: *[email protected]* <[email protected]> > > [image: Facebook] <https://facebook.com/heliontech> > > [image: Twitter] <https://twitter.com/heliontech> > > [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies> > > *From:* cisco-voip <[email protected]> *On Behalf Of *Ben > Amick > *Sent:* Monday, April 2, 2018 2:41 PM > *To:* Brian Meade <[email protected]>; Lelio Fulgenzi <[email protected]> > *Cc:* Cisco VoIP Group <[email protected]> > *Subject:* Re: [cisco-voip] Jabber Multiline is Here > > > > Brian, > > If you move to multiline on Jabber and decommission softphones/deskphones > as a byproduct, what issue does that generate with UCCX? > > > > Being that Jabber tethers to your own controlled device without a specific > CSF specified, what use case would extension mobility fulfill that jabber > itself wouldn?t? > > > > Ben Amick > > Unified Communications Analyst > > > > *From:* cisco-voip <[email protected]> *On Behalf Of *Brian > Meade > *Sent:* Monday, April 2, 2018 2:05 PM > *To:* Lelio Fulgenzi <[email protected]> > *Cc:* Cisco VoIP Group <[email protected]> > *Subject:* Re: [cisco-voip] Jabber Multiline is Here > > > > *Security Notice:* This is an EXTERNAL email. Please exercise caution and > DO NOT open attachments or click links from unknown or unexpected senders. > > Big holdup looks to be no multiline with MRA, still only single line > there. > > > > The other big issue is no extension mobility support and UCCX is still > enforcing their single device policy. I've been having some discussions > with the Jabber/UCCX teams around this. Right now CIPC is EOL but I'm > still having to do active deployments of it due to this issue as I'm sure > many others are hitting. > > > > On Mon, Apr 2, 2018 at 1:43 PM, Lelio Fulgenzi <[email protected]> wrote: > > Let?s hope voicemail works with multi lines. ? > > > > --- > > *Lelio Fulgenzi, B.A.* | Senior Analyst > > Computing and Communications Services | University of Guelph > > Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | > N1G 2W1 > <https://maps.google.com/?q=50+Stone+Rd+E+%7C+Guelph,+ON+%7C+N1G+2W1&entry=gmail&source=g> > > 519-824-4120 Ext. 56354 <(519)%20824-4120> | [email protected] > > > > www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook > > > > [image: University of Guelph Cornerstone with Improve Life tagline] > > > > *From:* cisco-voip [mailto:[email protected]] *On Behalf > Of *Anthony Holloway > *Sent:* Monday, April 2, 2018 10:44 AM > *To:* Cisco VoIP Group <[email protected]> > *Subject:* [cisco-voip] Jabber Multiline is Here > > > > Just in case you missed it, Jabber multiline made it into 12.0. You'll > need to be on CUCM 11.5(1)SU4 and install a COP file to support it. > > > > Release Notes > > https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/ > Windows/12_0/RN/jabw_b_release-notes-for-cisco-jabber_12.html#reference_ > 6CABFFC6E6E2B025EA1C691A8744962A > > > > Configuration Guide > > https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/ > 12_0/cjab_b_feature-configuration-for-cisco-jabber-120/cjab_b_feature- > configuration-for-cisco-jabber-120_chapter_011.html#reference_ > 08DB2E9280C0A8ABF98E1B329604E883 > > > > Video Demo > > https://youtu.be/Cosfzf7XoBo > > > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip > > > > *Disclaimer:* The information contained in this transmission and any > attachments may contain privileged and confidential information including > patient information protected by federal and state privacy laws. This > transmission is sent for the sole use of the intended recipient. If you are > not the intended recipient, please immediately (1) notify the sender via > reply email; (2) do not open or read the message or any attachments; and > (3) delete this message and any attachments. The review, dissemination, > distribution, or duplication of this transmission by anyone other than the > intended recipient is strictly prohibited. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/efebb5d5/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 431 bytes Desc: not available URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/efebb5d5/attachment-0005.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 561 bytes Desc: not available URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/efebb5d5/attachment-0006.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 1297 bytes Desc: not available URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/efebb5d5/attachment-0007.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 8404 bytes Desc: not available URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/efebb5d5/attachment-0008.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 444 bytes Desc: not available URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/efebb5d5/attachment-0009.png> ------------------------------ Message: 12 Date: Mon, 2 Apr 2018 18:55:49 +0000 From: "Winstrand, Kenneth" <[email protected]> To: Anthony Holloway <[email protected]>, Cisco VoIP Group <[email protected]> Subject: Re: [cisco-voip] CUCM Pre-Upgrade Checklist Message-ID: <bn6pr1601mb1219c53596f94ab1e7fc629f8e...@bn6pr1601mb1219.namprd16.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Some of these are probably CYA?s? but you might as well do them in case you?re the one guy in 10,000 affected by a bug. From: cisco-voip <[email protected]> On Behalf Of Anthony Holloway Sent: Saturday, March 31, 2018 11:39 PM To: Cisco VoIP Group <[email protected]> Subject: [cisco-voip] CUCM Pre-Upgrade Checklist Has anyone seen this lately? This thing is nuts. I've been doing upgrades for like 10 years now, and this seems a little over the top. https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/11_5_1/cucm_b_upgrade-guide-cucm-115/cucm_b_upgrade-guide-cucm-115_chapter_010001.html<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cisco.com%2Fc%2Fen%2Fus%2Ftd%2Fdocs%2Fvoice_ip_comm%2Fcucm%2Fupgrade%2F11_5_1%2Fcucm_b_upgrade-guide-cucm-115%2Fcucm_b_upgrade-guide-cucm-115_chapter_010001.html&data=02%7C01%7Ckwinstrand%40hcr-manorcare.com%7C1b4f30f2556f45c4b44b08d597825f20%7C053af594947149639f1553432d540084%7C0%7C0%7C636581508558768969&sdata=aN9ySOTKYfdk0ni6KmqO8yh7P7uXfVr29imCVX9YOHE%3D&reserved=0> Some Highlights: "If you have custom ringtones or background images in the TFTP directory, you need to create a separate backup for these files. They are not included in the Disaster Recovery System (DRS) backup file." Good to know. I must admit that I didn't know that. "Record the following login and password information: all application users credentials, such as DRS, AXL, and accounts for other third-party integration" What? Why? What do you plan on doing with my configuration? "Record the settings for Enterprise Parameters on both [CM] nodes and [IM&P] nodes. [T]he settings that are configured on Unified Communications Manager nodes overwrite the settings configured on IM and Presence Service nodes during the upgrade process." Well that's some lazy software engineering right there folks. "Export user records using the Bulk Administration Tool (BAT)." That's a nice list of users you got there. It would be a shame if this upgrade deleted all of them. And the list just goes on, and on, and on. The pre-upgrade is as long as the upgrade. Who legitimately is already doing 100% of these things? -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/c6d7eeac/attachment-0001.html> ------------------------------ Message: 13 Date: Mon, 2 Apr 2018 19:03:53 +0000 From: "Pawlowski, Adam" <[email protected]> To: "[email protected]" <[email protected]> Subject: Re: [cisco-voip] Jabber Multiline is Here Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" The notes still call out 11.5 SU 3 as a minimum as it'd been throughout the trial, but, yeah 9.x is way back there. We're trying to adopt a more agile patching schedule , wherein in the past we would often not bother with any SU and simply wait for a .5 to move up to . To be honest I think the .5 is almost a .0 as far as that's concerned, the SUs are where the bugs are going to get fleshed out. SU3/SU4 is going to be important for iOS mobile, though multiline doesn't help them. Adam ------------------------------ Message: 14 Date: Mon, 2 Apr 2018 19:05:27 +0000 From: Ryan Huff <[email protected]> To: "Winstrand, Kenneth" <[email protected]> Cc: Anthony Holloway <[email protected]>, Cisco VoIP Group <[email protected]> Subject: Re: [cisco-voip] CUCM Pre-Upgrade Checklist Message-ID: <cy4pr1801mb181611cef6d14b2aed089590c5...@cy4pr1801mb1816.namprd18.prod.outlook.com> Content-Type: text/plain; charset="utf-8" These pre upgrade tasks have been the same for awhile I think. Here is the 10.5 guide that shows these. https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/10_5_1/cucm_b_upgrade-and-migration-guide-105/cucm_b_upgrade-and-migration-guide-105_chapter_01010.html Sent from my iPhone On Apr 2, 2018, at 14:56, Winstrand, Kenneth <[email protected]<mailto:[email protected]>> wrote: Some of these are probably CYA?s? but you might as well do them in case you?re the one guy in 10,000 affected by a bug. From: cisco-voip <[email protected]<mailto:[email protected]>> On Behalf Of Anthony Holloway Sent: Saturday, March 31, 2018 11:39 PM To: Cisco VoIP Group <[email protected]<mailto:[email protected]>> Subject: [cisco-voip] CUCM Pre-Upgrade Checklist Has anyone seen this lately? This thing is nuts. I've been doing upgrades for like 10 years now, and this seems a little over the top. https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/11_5_1/cucm_b_upgrade-guide-cucm-115/cucm_b_upgrade-guide-cucm-115_chapter_010001.html<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cisco.com%2Fc%2Fen%2Fus%2Ftd%2Fdocs%2Fvoice_ip_comm%2Fcucm%2Fupgrade%2F11_5_1%2Fcucm_b_upgrade-guide-cucm-115%2Fcucm_b_upgrade-guide-cucm-115_chapter_010001.html&data=02%7C01%7Ckwinstrand%40hcr-manorcare.com%7C1b4f30f2556f45c4b44b08d597825f20%7C053af594947149639f1553432d540084%7C0%7C0%7C636581508558768969&sdata=aN9ySOTKYfdk0ni6KmqO8yh7P7uXfVr29imCVX9YOHE%3D&reserved=0> Some Highlights: "If you have custom ringtones or background images in the TFTP directory, you need to create a separate backup for these files. They are not included in the Disaster Recovery System (DRS) backup file." Good to know. I must admit that I didn't know that. "Record the following login and password information: all application users credentials, such as DRS, AXL, and accounts for other third-party integration" What? Why? What do you plan on doing with my configuration? "Record the settings for Enterprise Parameters on both [CM] nodes and [IM&P] nodes. [T]he settings that are configured on Unified Communications Manager nodes overwrite the settings configured on IM and Presence Service nodes during the upgrade process." Well that's some lazy software engineering right there folks. "Export user records using the Bulk Administration Tool (BAT)." That's a nice list of users you got there. It would be a shame if this upgrade deleted all of them. And the list just goes on, and on, and on. The pre-upgrade is as long as the upgrade. Who legitimately is already doing 100% of these things? _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/ccf44946/attachment-0001.html> ------------------------------ Message: 15 Date: Tue, 03 Apr 2018 13:52:26 +0200 From: Sebastian Hagedorn <[email protected]> To: Brian Meade <[email protected]> Cc: Cisco VoIP Group <[email protected]> Subject: Re: [cisco-voip] Jabber Multiline is Here Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8"; Format="flowed" Where does it say that? I did not find anything in either the release notes or the configuration guide. --On 2. April 2018 um 14:04:52 -0400 Brian Meade <[email protected]> wrote: > The other big issue is no extension mobility support -- .:.Sebastian Hagedorn - Weyertal 121 (Geb?ude 133), Zimmer 2.02.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universit?t zu K?ln / Cologne University - ? +49-221-470-89578.:. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 191 bytes Desc: not available URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180403/aa04579b/attachment-0001.sig> ------------------------------ Message: 16 Date: Tue, 3 Apr 2018 12:34:13 +0000 From: Matthew Loraditch <[email protected]> To: Sebastian Hagedorn <[email protected]>, Brian Meade <[email protected]> Cc: Cisco VoIP Group <[email protected]> Subject: Re: [cisco-voip] Jabber Multiline is Here Message-ID: <dm2pr08mb461d4484d68cb0180b623c3b3...@dm2pr08mb461.namprd08.prod.outlook.com> Content-Type: text/plain; charset="utf-8" To be clear Jabber supports CTI control of a phone logged in with EM. It doesn't support jabber as a device where you can sign into an EM extension like CIPC does. Matthew Loraditch Sr. Network Engineer p: 443.541.1518 w: www.heliontechnologies.com | e: [email protected] -----Original Message----- From: cisco-voip <[email protected]> On Behalf Of Sebastian Hagedorn Sent: Tuesday, April 3, 2018 7:52 AM To: Brian Meade <[email protected]> Cc: Cisco VoIP Group <[email protected]> Subject: Re: [cisco-voip] Jabber Multiline is Here Where does it say that? I did not find anything in either the release notes or the configuration guide. --On 2. April 2018 um 14:04:52 -0400 Brian Meade <[email protected]> wrote: > The other big issue is no extension mobility support -- .:.Sebastian Hagedorn - Weyertal 121 (Geb?ude 133), Zimmer 2.02.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universit?t zu K?ln / Cologne University - ? +49-221-470-89578.:. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180403/398fb654/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image359586.png Type: image/png Size: 8404 bytes Desc: image359586.png URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180403/398fb654/attachment-0004.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image519930.png Type: image/png Size: 431 bytes Desc: image519930.png URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180403/398fb654/attachment-0005.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image402235.png Type: image/png Size: 561 bytes Desc: image402235.png URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180403/398fb654/attachment-0006.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image013307.png Type: image/png Size: 444 bytes Desc: image013307.png URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180403/398fb654/attachment-0007.png> ------------------------------ Subject: Digest Footer _______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip ------------------------------ End of cisco-voip Digest, Vol 174, Issue 3 ****************************************** _______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
