Re: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?

[Ryan Huff]

I use an excel spread sheet with a hyperlink to the base doc in one sheet with 
notes and details gathered in the sheet.Then I create additional worksheets of 
subordinate documentation and notes and then make references from the base 
sheet to the subordinate sheets. I also have a sheet for customer discovery 
(current dns, ip, device loads  etc). It ends up looking a lot like a Gantt 
chart.

If you'd like, I can sanitize and send one to you, to compare notes and see if 
there is anything of use to you.

Also, If time permits, and it's feasible,  I like to stage a mock upgrade in my 
lab with customer data (drs ... etc) and do a dry run.

 Original message 
From: Anthony Holloway  
Date:10/16/2015  2:38 PM  (GMT-05:00) 
To: Cisco VoIP Group  
Subject: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade? 

Does anyone else do this?  Gather all of the documentation ahead of time, 
because inevitably you're going to revisit a document more than once?  There 
are a lot of documents to gather!  Anything I could be doing better?  Tips?  
Tricks?

I create a spreadsheet of all of the pertinent documents I need to review or 
reference, like in this screenshot.  There's over 90 documents in this list.  
Granted, I don't read them all front to back, but some I do, and  for others I 
need to reference information within them nonetheless.  You never know when you 
might find a small font hidden note in there.

E.g., From the 8945 Release Notes

"Release 9.4(2)SR1 can only be upgraded from 9.3(4) and later. Releases prior 
to 9.3(4) have to be upgraded to 9.3(4) first."

Source: 8945 9.4(2)SR1 Release Notes

I actually missed this one recently, and unlike 7900 series phones, they phone 
will just brick itself and never register.  Causing you to walk to every phone 
and reset power to it, or walk the mac address tables of your layer 2 network 
and shut/no shut the ports.


___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?

[Ryan Huff]

Yeah, I am mobile at the moment,  Once I get home I'll clean one up and send it 
out to the list.

Thanks,

Ryan


Sent from my T-Mobile 4G LTE Device

 Original message 
From: Terry Oakley  
Date:10/16/2015  3:05 PM  (GMT-05:00) 
To: 'Ryan Huff' ,Anthony Holloway 
,Cisco VoIP Group  
Subject: RE: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade? 

I would certainly be interested in a sanitized look.   Upgrades are fun (yeah 
right) but having some sort of tool to assist would at least make the light 
appear a little clearer.
 
 
 
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan 
Huff
Sent: October 16, 2015 12:57 PM
To: Anthony Holloway ; Cisco VoIP Group 

Subject: Re: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?
 
I use an excel spread sheet with a hyperlink to the base doc in one sheet with 
notes and details gathered in the sheet.Then I create additional worksheets of 
subordinate documentation and notes and then make references from the base 
sheet to the subordinate sheets. I also have a sheet for customer discovery 
(current dns, ip, device loads  etc). It ends up looking a lot like a Gantt 
chart.
 
If you'd like, I can sanitize and send one to you, to compare notes and see if 
there is anything of use to you.
 
Also, If time permits, and it's feasible,  I like to stage a mock upgrade in my 
lab with customer data (drs ... etc) and do a dry run.


 Original message 
From: Anthony Holloway 
Date:10/16/2015 2:38 PM (GMT-05:00) 
To: Cisco VoIP Group 
Subject: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?

Does anyone else do this?  Gather all of the documentation ahead of time, 
because inevitably you're going to revisit a document more than once?  There 
are a lot of documents to gather!  Anything I could be doing better?  Tips?  
Tricks?
 
I create a spreadsheet of all of the pertinent documents I need to review or 
reference, like in this screenshot.  There's over 90 documents in this list.  
Granted, I don't read them all front to back, but some I do, and  for others I 
need to reference information within them nonetheless.  You never know when you 
might find a small font hidden note in there.
 
E.g., From the 8945 Release Notes
 
"Release 9.4(2)SR1 can only be upgraded from 9.3(4) and later. Releases prior 
to 9.3(4) have to be upgraded to 9.3(4) first."
 
Source: 8945 9.4(2)SR1 Release Notes
 
I actually missed this one recently, and unlike 7900 series phones, they phone 
will just brick itself and never register.  Causing you to walk to every phone 
and reset power to it, or walk the mac address tables of your layer 2 network 
and shut/no shut the ports.
 
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] AQM 10.5 Recordings Playback

[Mathew Miller]

Hello All,

Fresh install of AQM 10.5 SR6 integrated with UCCX 10.6

Recording seem to be working ok, and I can see them being written for both
audio and screen scrapes to the directories i specified during install but
in the admin interface I don't see the recordings displaying in the Web
Interface.

My user is an admin and I have given it access to each of the teams as a QM
manager to the group. I have set recording visibility to as unlimited for
all users.

I can see users under the QM monitor section and can even remote monitor
their screens, but not seeing recordings.

Has anyone seen this before?

Any suggestions?

Thanks
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?

[Lelio Fulgenzi]

I've never made a spreadsheet like yours, but I've done something similar. 
Typically with compatibility checking. You do have to visit a number of 
documents and/or links. It's quite frustrating to say the least. 

The process of upgrading is a difficult one to say the least, especially with 
things like you mention, where gotchas are hidden deep in documents that you 
may not read front to back. 

My biggest issue is when you skip versions, it's not really clear which 
documents to read with respect to changes. For example, when I upgraded from 
7.1 to 9.1, I found myself printing (k!) a number of documents which had 
duplicate information, but I wasn't sure on where to look. 

And then there's the issue that each application will have different rules, so 
CUCM might say only print the latest minor version notes, any SU or a/b/c 
release will have everything you need. Where Connection or Unity Express might 
do something different. 

It's not fun to say the least. 

But isn't Prime supposed to make it easy to upgrade now? 


--- 
Lelio Fulgenzi, B.A. 
Senior Analyst, Network Infrastructure 
Computing and Communications Services (CCS) 
University of Guelph 

519‐824‐4120 Ext 56354 
le...@uoguelph.ca 
www.uoguelph.ca/ccs 
Room 037, Animal Science and Nutrition Building 
Guelph, Ontario, N1G 2W1 

- Original Message -

From: "Anthony Holloway"  
To: "Cisco VoIP Group"  
Sent: Friday, October 16, 2015 2:38:40 PM 
Subject: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade? 

Does anyone else do this? Gather all of the documentation ahead of time, 
because inevitably you're going to revisit a document more than once? There are 
a lot of documents to gather! Anything I could be doing better? Tips? Tricks? 

I create a spreadsheet of all of the pertinent documents I need to review or 
reference, like in this screenshot. There's over 90 documents in this list. 
Granted, I don't read them all front to back, but some I do, and for others I 
need to reference information within them nonetheless. You never know when you 
might find a small font hidden note in there. 

E.g., From the 8945 Release Notes 

"Release 9.4(2)SR1 can only be upgraded from 9.3(4) and later. Releases prior 
to 9.3(4) have to be upgraded to 9.3(4) first." 

Source: 8945 9.4(2)SR1 Release Notes 

I actually missed this one recently, and unlike 7900 series phones, they phone 
will just brick itself and never register. Causing you to walk to every phone 
and reset power to it, or walk the mac address tables of your layer 2 network 
and shut/no shut the ports. 



___ 
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

Re: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?

[Ed Leatherman]

I do this but not nearly as organized :) I have an evernote notebook with a
page where I lay out upgrade procedures and notes, and then as I find docs
relevant to the upgrade I clip them into the notebook so they are there and
synced if I need them

On Fri, Oct 16, 2015 at 2:38 PM, Anthony Holloway <
avholloway+cisco-v...@gmail.com> wrote:

> Does anyone else do this?  Gather all of the documentation ahead of time,
> because inevitably you're going to revisit a document more than once?
> There are a lot of documents to gather!  Anything I could be doing better?
> Tips?  Tricks?
>
> I create a spreadsheet of all of the pertinent documents I need to review
> or reference, like in this screenshot.  There's over 90 documents in this
> list.  Granted, I don't read them all front to back, but some I do, and
>  for others I need to reference information within them nonetheless.  You
> never know when you might find a small font hidden note in there.
>
> E.g., From the 8945 Release Notes
>
> *"Release 9.4(2)SR1 can only be upgraded from 9.3(4) and later. Releases
> prior to 9.3(4) have to be upgraded to 9.3(4) first."*
>
> *Source: 8945 9.4(2)SR1 Release Notes
> *
>
> I actually missed this one recently, and unlike 7900 series phones, they
> phone will just brick itself and never register.  Causing you to walk to
> every phone and reset power to it, or walk the mac address tables of your
> layer 2 network and shut/no shut the ports.
>
> [image: Inline image 1]
>
> ___
> 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] How Many Docs Does it Take to Prep for an Upgrade?

[Terry Oakley]

I would certainly be interested in a sanitized look.   Upgrades are fun (yeah 
right) but having some sort of tool to assist would at least make the light 
appear a little clearer.



From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan 
Huff
Sent: October 16, 2015 12:57 PM
To: Anthony Holloway ; Cisco VoIP Group 

Subject: Re: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?

I use an excel spread sheet with a hyperlink to the base doc in one sheet with 
notes and details gathered in the sheet.Then I create additional worksheets of 
subordinate documentation and notes and then make references from the base 
sheet to the subordinate sheets. I also have a sheet for customer discovery 
(current dns, ip, device loads  etc). It ends up looking a lot like a Gantt 
chart.

If you'd like, I can sanitize and send one to you, to compare notes and see if 
there is anything of use to you.

Also, If time permits, and it's feasible,  I like to stage a mock upgrade in my 
lab with customer data (drs ... etc) and do a dry run.


 Original message 
From: Anthony Holloway
Date:10/16/2015 2:38 PM (GMT-05:00)
To: Cisco VoIP Group
Subject: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?
Does anyone else do this?  Gather all of the documentation ahead of time, 
because inevitably you're going to revisit a document more than once?  There 
are a lot of documents to gather!  Anything I could be doing better?  Tips?  
Tricks?

I create a spreadsheet of all of the pertinent documents I need to review or 
reference, like in this screenshot.  There's over 90 documents in this list.  
Granted, I don't read them all front to back, but some I do, and  for others I 
need to reference information within them nonetheless.  You never know when you 
might find a small font hidden note in there.

E.g., From the 8945 Release Notes

"Release 9.4(2)SR1 can only be upgraded from 9.3(4) and later. Releases prior 
to 9.3(4) have to be upgraded to 9.3(4) first."

Source: 8945 9.4(2)SR1 Release 
Notes

I actually missed this one recently, and unlike 7900 series phones, they phone 
will just brick itself and never register.  Causing you to walk to every phone 
and reset power to it, or walk the mac address tables of your layer 2 network 
and shut/no shut the ports.

[content://com.android.email.attachmentprovider/2/1388/RAW]
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?

[Ryan Huff]

Typically, the only time that I'll stage an upgrade in a lab environment for a 
dry run is if I am doing something that I haven't done in a while or I have 
reason to think it might fail (you can screw up as much as you want in the lab 
;). I used to do it for almost every major upgrade.

I am a fan of doing the upgrade locally, grabbing the DRS from the local 
(upgraded) environment then restoring to a newly built environment in the 
customer network. This is a habit that extends from the pizza box days. 
However, with everything being virtualized now, I have become a fan of doing it 
all in the customer network.

I think each method has its pros and cons and the context of the customer 
engagement will generally point you to which method is better or more efficient 
for you. 

Thanks,

Ryan

Sent from my T-Mobile 4G LTE Device

 Original message 
From: Anthony Holloway  
Date:10/16/2015  3:41 PM  (GMT-05:00) 
To: Ryan Huff  
Cc: Cisco VoIP Group  
Subject: Re: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade? 

You sound more organized than I am.  I would like to see what you have, sure.  
Thanks for the offer.

I've never staged an upgrade in my lab, though I have heard of plenty of people 
doing this.  Is it really something to consider or is that a thing of the past? 
 Like pulling a drive from the array?  Not too mention, I rarely have time to 
perform two upgrades on a project like this.  I barely get enough time to 
upgrade the system once.

On Fri, Oct 16, 2015 at 1:56 PM, Ryan Huff  wrote:
I use an excel spread sheet with a hyperlink to the base doc in one sheet with 
notes and details gathered in the sheet.Then I create additional worksheets of 
subordinate documentation and notes and then make references from the base 
sheet to the subordinate sheets. I also have a sheet for customer discovery 
(current dns, ip, device loads  etc). It ends up looking a lot like a Gantt 
chart.

If you'd like, I can sanitize and send one to you, to compare notes and see if 
there is anything of use to you.

Also, If time permits, and it's feasible,  I like to stage a mock upgrade in my 
lab with customer data (drs ... etc) and do a dry run.


 Original message 
From: Anthony Holloway 
Date:10/16/2015 2:38 PM (GMT-05:00) 
To: Cisco VoIP Group 
Subject: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade? 

Does anyone else do this?  Gather all of the documentation ahead of time, 
because inevitably you're going to revisit a document more than once?  There 
are a lot of documents to gather!  Anything I could be doing better?  Tips?  
Tricks?

I create a spreadsheet of all of the pertinent documents I need to review or 
reference, like in this screenshot.  There's over 90 documents in this list.  
Granted, I don't read them all front to back, but some I do, and  for others I 
need to reference information within them nonetheless.  You never know when you 
might find a small font hidden note in there.

E.g., From the 8945 Release Notes

"Release 9.4(2)SR1 can only be upgraded from 9.3(4) and later. Releases prior 
to 9.3(4) have to be upgraded to 9.3(4) first."

Source: 8945 9.4(2)SR1 Release Notes

I actually missed this one recently, and unlike 7900 series phones, they phone 
will just brick itself and never register.  Causing you to walk to every phone 
and reset power to it, or walk the mac address tables of your layer 2 network 
and shut/no shut the ports.



___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] AQM 10.5 Recordings Playback

[Mathew Miller]

It's been about 18 hours so far. I can see the files are not in the
encoding folders, but the final folder for where they should live.

I setup the workflow to do immediate upload of both screen and audio files.

I've setup for network recording for audio and have the client installed
for the screen capture on a citrix server.

On Fri, Oct 16, 2015 at 12:15 PM, Brian Meade  wrote:

> I think some of them take some time to encrypt the files and put them up
> on the webpage.  Have you given it a day?  Do you see the files getting
> encrypted?
>
> On Fri, Oct 16, 2015 at 2:25 PM, Mathew Miller 
> wrote:
>
>> Hello All,
>>
>> Fresh install of AQM 10.5 SR6 integrated with UCCX 10.6
>>
>> Recording seem to be working ok, and I can see them being written for
>> both audio and screen scrapes to the directories i specified during install
>> but in the admin interface I don't see the recordings displaying in the Web
>> Interface.
>>
>> My user is an admin and I have given it access to each of the teams as a
>> QM manager to the group. I have set recording visibility to as unlimited
>> for all users.
>>
>> I can see users under the QM monitor section and can even remote monitor
>> their screens, but not seeing recordings.
>>
>> Has anyone seen this before?
>>
>> Any suggestions?
>>
>> Thanks
>>
>>
>> ___
>> 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

Re: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?

[Kevin Przybylowski]

It is very time consuming to stage in the lab… Installs, DRS’s, Upgrades, etc…  
I’ve only done them in the past if there was a large gap in versions.  It looks 
like PCD PCD is getting better so it looks like a valid option nowadays for 
bare metal to esx migration/upgrades.

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of 
Anthony Holloway
Sent: Friday, October 16, 2015 3:42 PM
To: Ryan Huff 
Cc: Cisco VoIP Group 
Subject: Re: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?

You sound more organized than I am.  I would like to see what you have, sure.  
Thanks for the offer.

I've never staged an upgrade in my lab, though I have heard of plenty of people 
doing this.  Is it really something to consider or is that a thing of the past? 
 Like pulling a drive from the array?  Not too mention, I rarely have time to 
perform two upgrades on a project like this.  I barely get enough time to 
upgrade the system once.

On Fri, Oct 16, 2015 at 1:56 PM, Ryan Huff 
> wrote:
I use an excel spread sheet with a hyperlink to the base doc in one sheet with 
notes and details gathered in the sheet.Then I create additional worksheets of 
subordinate documentation and notes and then make references from the base 
sheet to the subordinate sheets. I also have a sheet for customer discovery 
(current dns, ip, device loads  etc). It ends up looking a lot like a Gantt 
chart.

If you'd like, I can sanitize and send one to you, to compare notes and see if 
there is anything of use to you.

Also, If time permits, and it's feasible,  I like to stage a mock upgrade in my 
lab with customer data (drs ... etc) and do a dry run.


 Original message 
From: Anthony Holloway
Date:10/16/2015 2:38 PM (GMT-05:00)
To: Cisco VoIP Group
Subject: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?
Does anyone else do this?  Gather all of the documentation ahead of time, 
because inevitably you're going to revisit a document more than once?  There 
are a lot of documents to gather!  Anything I could be doing better?  Tips?  
Tricks?

I create a spreadsheet of all of the pertinent documents I need to review or 
reference, like in this screenshot.  There's over 90 documents in this list.  
Granted, I don't read them all front to back, but some I do, and  for others I 
need to reference information within them nonetheless.  You never know when you 
might find a small font hidden note in there.

E.g., From the 8945 Release Notes

"Release 9.4(2)SR1 can only be upgraded from 9.3(4) and later. Releases prior 
to 9.3(4) have to be upgraded to 9.3(4) first."

Source: 8945 9.4(2)SR1 Release 
Notes

I actually missed this one recently, and unlike 7900 series phones, they phone 
will just brick itself and never register.  Causing you to walk to every phone 
and reset power to it, or walk the mac address tables of your layer 2 network 
and shut/no shut the ports.


___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?

[Anthony Holloway]

You sound more organized than I am.  I would like to see what you have,
sure.  Thanks for the offer.

I've never staged an upgrade in my lab, though I have heard of plenty of
people doing this.  Is it really something to consider or is that a thing
of the past?  Like pulling a drive from the array?  Not too mention, I
rarely have time to perform two upgrades on a project like this.  I barely
get enough time to upgrade the system once.

On Fri, Oct 16, 2015 at 1:56 PM, Ryan Huff  wrote:

> I use an excel spread sheet with a hyperlink to the base doc in one sheet
> with notes and details gathered in the sheet.Then I create additional
> worksheets of subordinate documentation and notes and then make references
> from the base sheet to the subordinate sheets. I also have a sheet for
> customer discovery (current dns, ip, device loads  etc). It ends up
> looking a lot like a Gantt chart.
>
> If you'd like, I can sanitize and send one to you, to compare notes and
> see if there is anything of use to you.
>
> Also, If time permits, and it's feasible,  I like to stage a mock upgrade
> in my lab with customer data (drs ... etc) and do a dry run.
>
>
>  Original message 
> From: Anthony Holloway
> Date:10/16/2015 2:38 PM (GMT-05:00)
> To: Cisco VoIP Group
> Subject: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?
>
> Does anyone else do this?  Gather all of the documentation ahead of time,
> because inevitably you're going to revisit a document more than once?
> There are a lot of documents to gather!  Anything I could be doing better?
> Tips?  Tricks?
>
> I create a spreadsheet of all of the pertinent documents I need to review
> or reference, like in this screenshot.  There's over 90 documents in this
> list.  Granted, I don't read them all front to back, but some I do, and
>  for others I need to reference information within them nonetheless.  You
> never know when you might find a small font hidden note in there.
>
> E.g., From the 8945 Release Notes
>
> *"Release 9.4(2)SR1 can only be upgraded from 9.3(4) and later. Releases
> prior to 9.3(4) have to be upgraded to 9.3(4) first."*
>
> *Source: 8945 9.4(2)SR1 Release Notes
> *
>
> I actually missed this one recently, and unlike 7900 series phones, they
> phone will just brick itself and never register.  Causing you to walk to
> every phone and reset power to it, or walk the mac address tables of your
> layer 2 network and shut/no shut the ports.
>
> [image: Inline image 1]
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?

[Anthony Holloway]

When you say Prime, I will assume you mean Prime Collaboration Deployment
(PCD).

I have used PCD a few times now, but it's far from being the savior one
might think it is.

First, PCD really only shines when migrating to v10 on new hardware.  Or,
the same hardware, but you have twice the space.  You can jump straight
from CUCM 6.1(4) to 10.5(2) without COP files, or intermediate versions.
That's because PCD is actually installing v10 fresh, and just moving the
data for you.  At least it tries to.  There are a few things it doesn't
move yet.  E.g., DHCP Server TFTP Option 150.  Yes, I saw someone using
that in CUCM!

Second, if your doing any other kind of upgrade in PCD, you're not really
saving yourself from having to read all the documentation.  As your still
bound to all the same restrictions and COP files, and whatever else.  You
can look at PCD in this scenario as an intern who you've given instructions
to and he/she just executes them while you go play GTA V on your Xbox you
won in an Engineering Deathmatch
.  The intern really isn't
doing anything special for you, other than allowing you to look away while
the upgrades happen.  And even then, I've seen them fail more times than
they have succeeded.  YMMV.

Lastly, on the topic of PCD migrations, which are it's bread and butter, it
only does this for CUCM and IM  Not CUC, nor CER, not UCCX, or anything
else.  So, if you go migrate with PCD, then your stuck with COBRAS for CUC,
BAT for CER, and who knows what else for the rest.  I'll leave that as an
exercise to the reader.

At the end of the day, their maybe some environments where you can just
pull the trigger and upgrade the system without reading any documentation,
and just gamble, but for a professional of their craft, that's just not
acceptable.

On Fri, Oct 16, 2015 at 2:02 PM, Lelio Fulgenzi  wrote:

> I've never made a spreadsheet like yours, but I've done something similar.
> Typically with compatibility checking. You do have to visit a number of
> documents and/or links. It's quite frustrating to say the least.
>
> The process of upgrading is a difficult one to say the least, especially
> with things like you mention, where gotchas are hidden deep in documents
> that you may not read front to back.
>
> My biggest issue is when you skip versions, it's not really clear which
> documents to read with respect to changes. For example, when I upgraded
> from 7.1 to 9.1, I found myself printing (k!) a number of documents
> which had duplicate information, but I wasn't sure on where to look.
>
> And then there's the issue that each application will have different
> rules, so CUCM might say only print the latest minor version notes, any SU
> or a/b/c release will have everything you need. Where Connection or Unity
> Express might do something different.
>
> It's not fun to say the least.
>
> But isn't Prime supposed to make it easy to upgrade now?
>
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst, Network Infrastructure
> Computing and Communications Services (CCS)
> University of Guelph
>
> 519‐824‐4120 Ext 56354
> le...@uoguelph.ca
> www.uoguelph.ca/ccs
> Room 037, Animal Science and Nutrition Building
> Guelph, Ontario, N1G 2W1
>
> --
> *From: *"Anthony Holloway" 
> *To: *"Cisco VoIP Group" 
> *Sent: *Friday, October 16, 2015 2:38:40 PM
> *Subject: *[cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?
>
> Does anyone else do this?  Gather all of the documentation ahead of time,
> because inevitably you're going to revisit a document more than once?
> There are a lot of documents to gather!  Anything I could be doing better?
> Tips?  Tricks?
>
> I create a spreadsheet of all of the pertinent documents I need to review
> or reference, like in this screenshot.  There's over 90 documents in this
> list.  Granted, I don't read them all front to back, but some I do, and
>  for others I need to reference information within them nonetheless.  You
> never know when you might find a small font hidden note in there.
>
> E.g., From the 8945 Release Notes
>
> *"Release 9.4(2)SR1 can only be upgraded from 9.3(4) and later. Releases
> prior to 9.3(4) have to be upgraded to 9.3(4) first."*
>
> *Source: 8945 9.4(2)SR1 Release Notes
> *
>
> I actually missed this one recently, and unlike 7900 series phones, they
> phone will just brick itself and never register.  Causing you to walk to
> every phone and reset power to it, or walk the mac address tables of your
> layer 2 network and shut/no shut the ports.
>
> [image: Inline image 1]
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> 

Re: [cisco-voip] AQM 10.5 Recordings Playback

[Ashwani R]

Matthew,

What is the type of recording? Network, Desktop, Server?  What are you not
seeing on admin page?  Audio/Screen or both?  As Brian said you have to
wait 24 hrs for screen recording but you can setup workflow to see screen
recording before 24 hrs.

Thanks,
AR

On Fri, Oct 16, 2015 at 3:15 PM, Brian Meade  wrote:

> I think some of them take some time to encrypt the files and put them up
> on the webpage.  Have you given it a day?  Do you see the files getting
> encrypted?
>
> On Fri, Oct 16, 2015 at 2:25 PM, Mathew Miller 
> wrote:
>
>> Hello All,
>>
>> Fresh install of AQM 10.5 SR6 integrated with UCCX 10.6
>>
>> Recording seem to be working ok, and I can see them being written for
>> both audio and screen scrapes to the directories i specified during install
>> but in the admin interface I don't see the recordings displaying in the Web
>> Interface.
>>
>> My user is an admin and I have given it access to each of the teams as a
>> QM manager to the group. I have set recording visibility to as unlimited
>> for all users.
>>
>> I can see users under the QM monitor section and can even remote monitor
>> their screens, but not seeing recordings.
>>
>> Has anyone seen this before?
>>
>> Any suggestions?
>>
>> Thanks
>>
>>
>> ___
>> 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 mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Outbound IVR-UCCX and CUBE

[Anthony Holloway]

Nice work Nick, and thanks for such great detail on your efforts.  I agree
that switching your transcoder to universal didn't help you, considering
you are not using the transcoder any longer.  You did confirm that correct?

I am also curious to see how having no dtmf-relay impacts your users.  You
must only ever do g711 out to the PSTN then?  And your ITSP was onboard
with no relay?

Was the TCP vs UDP requirement documented somewhere and you just missed it
originally, or was that a shot in the dark to try TCP?

Thanks again for sharing your journey.

On Thu, Oct 15, 2015 at 6:00 PM, Nick Britt 
wrote:

> Didn't try VAD maybe should have though! Resolution below, in short we
> changed the trans-coder to universal (not sure this helped the issue)
> forced TCP in both the SIP gateway within UCCX and on the incoming
> dial-peers then also removed RTP-NTE DTMF on the dial-peers.
>
> Here is a summary:
>
>
>
> *Problem description: *
>
> · CPA calls from UCCX oubound dialer not working over SIP trunk
> to CUBE.
>
> *Case closure Summary:*
>
> · We started with debugging the CUBE.
>
> · According to the flow between CCX and GW:
>
> INVITE from CCX to GW -->
>
> 100 Trying <--
>
> 180 Ring<--
>
> 200 OK<--
>
> ·  We are not receiving ACK from CCX to proceed with the call
> further, after which we should establish media CPA and send an update to
> CCX.
>
> · Collected MIVR logs and found that UCCX is not accepting the
> incoming SIP signaling from VGW on its Sip stack.
>
> · Confirmed SIP packet relay using packet captures.
>
> · UCCX server was rebooted more than one time but issue remained
> the same.
>
> · We finally changed the protocol from UDP to TCP between the
> UCCX and cube. This helped in the SIP signaling to complete.
>
> · We also upgraded the IOS to 15.5 proactively.
>
> · Did some research and found an enhancement Caveat
> https://tools.cisco.com/bugsearch/bug/CSCui62525/?
>
> · As per the Caveat *Call Progress Analysis (CPA) will fail to
> run and detect live voice or SIT tones during a Unified Contact Center
> Express (UCCX) IVR-based Outbound Dialer Call.*
>
> · Now since we were doing DTMF internetworking (RTP-NTE to raw
> inband) the DSPs were ingoring the CPA config and not detecting the audio.
>
> · We removed the DTMF internetworking and allowed raw inband DTMF
> type on the Service provider leg. To do this we removed the “dtmf-relay
> rtp-nte” under the dial peer 60 which was the dial peer to provider.
>
> · We also rolled back the IOS version to 15.4.3 as it was and
> confirmed calls success.
>
> · For your reference I have posted the useful CPA links below.
>
>
>
> *CPA config :*
>
> https://tools.cisco.com/squish/6fFE9
>
>
>
> *CPA call flow overview:*
>
> https://tools.cisco.com/squish/3CEe0
>
>
>
>
> On Fri, Oct 16, 2015 at 1:52 AM, Ryan Huff  wrote:
>
>> Long shot here but have you double checked that voice activity detection
>> (VAD) is off?
>>
>> Thanks,
>>
>> Ryan
>>
>> --
>> From: nickolasjbr...@gmail.com
>> Date: Thu, 15 Oct 2015 14:14:59 +1100
>> To: rlafo...@cisco.com
>> Subject: Re: [cisco-voip] Outbound IVR-UCCX and CUBE
>> CC: cisco-voip@puck.nether.net
>>
>>
>> Sorry to Grave dig here, trying to configure CPA on UCCX on
>> 10.6(1.1.1) with a CISCO2921/K9 on  Version 15.4(3)M4, RELEASE SOFTWARE
>> (fc1).
>>
>> It appears CSCui62525 was resolved on our version of UCCX but we tried
>> removing RTP-NTE from all dialpeers with no luck (no update messages being
>> sent from the GW to UCCX to advise that a live human is speaking connected)
>>
>> Anything else we should check? TAC is next :(
>>
>>
>> On Fri, Apr 11, 2014 at 4:12 AM, Ryan LaFountain (rlafount) <
>> rlafo...@cisco.com> wrote:
>>
>> Hi Michele,
>>
>> As Bill said, only TDM is supported at this time. Although CUBE recently
>> released support for CPA in DSPs that is not involved in call termination,
>> there are still some things we have to work out.
>>
>> You can track CSCui62525. When this gets integrated I hope we’ll support
>> CUBE for IVR-based Outbound Dialer with UCCX.
>>
>> You can also see this article which talks a little bit more about it.
>>
>>
>> http://www.cisco.com/c/en/us/support/docs/customer-collaboration/unified-contact-center-express/116084-trouble-ivr-dialer-00.html
>>
>> Thank you,
>>
>> Ryan LaFountain
>> Unified Contact Center
>> Cisco Services
>> Direct: +1 919 392 9898
>> Hours: M - F 9:00am - 5:00pm Eastern Time
>>
>> On Apr 10, 2014, at 12:41 PM, Bill Talley  wrote:
>>
>> PSTN access has to be TDM.  SIP trunking to telco is not supported in CCX
>> 9.0(2) for outbound dialer functionality.
>>
>> 
>>
>>
>> On Thu, Apr 10, 2014 at 12:11 PM, Michele Russo (AM) <
>> michele.ru...@dimensiondata.com> wrote:
>>
>> I am configuring an Outbound IVR Progressive Campaign using UCCX 

Re: [cisco-voip] Outbound IVR-UCCX and CUBE

[Nick Britt]

No tcp not documented anywhere. No chance to change the transcoder. But we
turned rtp-ntp off and that buggered everything. The bug is not resolved in
10.6

On Saturday, 17 October 2015, Anthony Holloway <
avholloway+cisco-v...@gmail.com> wrote:

> Nice work Nick, and thanks for such great detail on your efforts.  I agree
> that switching your transcoder to universal didn't help you, considering
> you are not using the transcoder any longer.  You did confirm that correct?
>
> I am also curious to see how having no dtmf-relay impacts your users.  You
> must only ever do g711 out to the PSTN then?  And your ITSP was onboard
> with no relay?
>
> Was the TCP vs UDP requirement documented somewhere and you just missed it
> originally, or was that a shot in the dark to try TCP?
>
> Thanks again for sharing your journey.
>
> On Thu, Oct 15, 2015 at 6:00 PM, Nick Britt  > wrote:
>
>> Didn't try VAD maybe should have though! Resolution below, in short we
>> changed the trans-coder to universal (not sure this helped the issue)
>> forced TCP in both the SIP gateway within UCCX and on the incoming
>> dial-peers then also removed RTP-NTE DTMF on the dial-peers.
>>
>> Here is a summary:
>>
>>
>>
>> *Problem description: *
>>
>> · CPA calls from UCCX oubound dialer not working over SIP trunk
>> to CUBE.
>>
>> *Case closure Summary:*
>>
>> · We started with debugging the CUBE.
>>
>> · According to the flow between CCX and GW:
>>
>> INVITE from CCX to GW -->
>>
>> 100 Trying <--
>>
>> 180 Ring<--
>>
>> 200 OK<--
>>
>> ·  We are not receiving ACK from CCX to proceed with the call
>> further, after which we should establish media CPA and send an update to
>> CCX.
>>
>> · Collected MIVR logs and found that UCCX is not accepting the
>> incoming SIP signaling from VGW on its Sip stack.
>>
>> · Confirmed SIP packet relay using packet captures.
>>
>> · UCCX server was rebooted more than one time but issue remained
>> the same.
>>
>> · We finally changed the protocol from UDP to TCP between the
>> UCCX and cube. This helped in the SIP signaling to complete.
>>
>> · We also upgraded the IOS to 15.5 proactively.
>>
>> · Did some research and found an enhancement Caveat
>> https://tools.cisco.com/bugsearch/bug/CSCui62525/?
>>
>> · As per the Caveat *Call Progress Analysis (CPA) will fail to
>> run and detect live voice or SIT tones during a Unified Contact Center
>> Express (UCCX) IVR-based Outbound Dialer Call.*
>>
>> · Now since we were doing DTMF internetworking (RTP-NTE to raw
>> inband) the DSPs were ingoring the CPA config and not detecting the audio.
>>
>> · We removed the DTMF internetworking and allowed raw inband
>> DTMF type on the Service provider leg. To do this we removed the
>> “dtmf-relay rtp-nte” under the dial peer 60 which was the dial peer to
>> provider.
>>
>> · We also rolled back the IOS version to 15.4.3 as it was and
>> confirmed calls success.
>>
>> · For your reference I have posted the useful CPA links below.
>>
>>
>>
>> *CPA config :*
>>
>> https://tools.cisco.com/squish/6fFE9
>>
>>
>>
>> *CPA call flow overview:*
>>
>> https://tools.cisco.com/squish/3CEe0
>>
>>
>>
>>
>> On Fri, Oct 16, 2015 at 1:52 AM, Ryan Huff > > wrote:
>>
>>> Long shot here but have you double checked that voice activity detection
>>> (VAD) is off?
>>>
>>> Thanks,
>>>
>>> Ryan
>>>
>>> --
>>> From: nickolasjbr...@gmail.com
>>> 
>>> Date: Thu, 15 Oct 2015 14:14:59 +1100
>>> To: rlafo...@cisco.com
>>> 
>>> Subject: Re: [cisco-voip] Outbound IVR-UCCX and CUBE
>>> CC: cisco-voip@puck.nether.net
>>> 
>>>
>>>
>>> Sorry to Grave dig here, trying to configure CPA on UCCX on
>>> 10.6(1.1.1) with a CISCO2921/K9 on  Version 15.4(3)M4, RELEASE SOFTWARE
>>> (fc1).
>>>
>>> It appears CSCui62525 was resolved on our version of UCCX but we tried
>>> removing RTP-NTE from all dialpeers with no luck (no update messages being
>>> sent from the GW to UCCX to advise that a live human is speaking connected)
>>>
>>> Anything else we should check? TAC is next :(
>>>
>>>
>>> On Fri, Apr 11, 2014 at 4:12 AM, Ryan LaFountain (rlafount) <
>>> rlafo...@cisco.com >
>>> wrote:
>>>
>>> Hi Michele,
>>>
>>> As Bill said, only TDM is supported at this time. Although CUBE recently
>>> released support for CPA in DSPs that is not involved in call termination,
>>> there are still some things we have to work out.
>>>
>>> You can track CSCui62525. When this gets integrated I hope we’ll support
>>> CUBE for IVR-based Outbound Dialer with UCCX.
>>>

Re: [cisco-voip] CUCM 10.5 and Exchange 2013 voicemail setup. RESOLVED

[Terry Oakley]

Well did some call traces and I get this on the try to the hunt pilot

Line 1
11:14:05.430|CC|OFFERED|66715124|66715125|3521|1803|1803|SEPA45630BA4343|Exchange2013CASTrunk
Line 2
11:14:05.517|SIPT|66715125|TCP|OUT|xxx.16.xxx.12|5060|Exchange2013CASTrunk|xxx.28.x.xxx|5060|3
100

13

2806.1^*^*|11508701|f79c7200-61e18d5d-35cac-cc91...@172.16.xxx.12|INVITE

Line 3   
11:14:05.518|SIPT|66715125|TCP|IN|xxx.16.xxx.12|5060|Exchange2013CASTrunk|xxx.28.x.222|5060|3
100

14

1874917.2^xxx.28.x.222^*|11508702|f79c7200-61e18d5d-35cac-cc91...@xxx.16.xxx.12|100

Trying

Line 4
11:14:05.545|SIPT|66715125|TCP|IN|xxx.16.xxx.12|5060|Exchange2013CASTrunk|xxx.28.x.222|5060|3
100

14

1874917.3^xxx.28.x.222^*|11508703|f79c7200-61e18d5d-35cac-cc91...@xxx.16.xxx.12|403

Forbidden







IP addressed masked to protect the less than innocent.

Then on looking at the Exchange side and the event viewer there was a telltale 
event there, that I should have asked the admin earlier.   “The Unified 
Messages server cannot find a valid UM hunt group associate with the UM IP 
gateway.   Pilot 1803”

So after attempts to modify the UM dial plan to add the hunt group we removed 
it and started again.   This time making the URI type Telephone extension 
instead of SIP URI.   We were able to add the hunt group and voila an answered 
call from CUCM 10.5 to Exchange 2013.

BTW there is a problem with Play on Phone in Office 2013 that requires a KB to 
be added for the Play on Phone to work.   The KB is 2880477.   
https://support.microsoft.com/en-us/kb/2880477


Thanks for all of the support and a special thanks to Ryan and Aaron

Terry



From: Ryan Huff [mailto:ryanh...@outlook.com]
Sent: October 13, 2015 5:29 PM
To: Terry Oakley ; cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] CUCM 10.5 and Exchange 2013 voicemail setup.

Terry,

Sounds like you have a lot going on there!

How did you move into the 10.5 environment?  Did you do a bridge migration or a 
'stare and compare'?

A fast busy could be a few different things (css, partition ... etc) or dns 
based since you mentioned fqdn or resource based.

What codec are you trying using?

Have you pulled traces?

What is the disconnect cause code for one of the failed calls into the hunt 
pilot?

If you can reproduce a failed call and then send me the traces or the sip 
messages I can give you a much better answer.

Thanks,

Ryan


Sent from my T-Mobile 4G LTE Device


 Original message 
From: Terry Oakley
Date:10/13/2015 6:24 PM (GMT-05:00)
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] CUCM 10.5 and Exchange 2013 voicemail setup.
We currently are moving from Exchange 2007 to Exchange 2013.   We have three 
CAS servers and 3 Mailbox servers, all virtualized.   In our test environment, 
before we moved from CUCM 6.1 to 10.5 we are able to at least get Exchange 2013 
to answer a SIP trunk request from CUCM 6.1.   Now in CUCM 10.5 we just get a 
fast busy when we dial the VM pilot number.   Does anyone have experience with 
this and have a guide that we could follow?We have followed a number of 
guides from Microsoft and they have not proven to be the magic answer.

We have a SIP trunk set to the CAS servers with all three individual servers 
listed in the Destination section (all FQDN) port 5060
We have three separate SIP trunks to the three mailbox servers with all three 
having the ports 5062 through 5068 listed and again FQDN for the destination 
address.
The VM pilot (route pattern) is associated with the CAS trunk.
Do we need a route list and hence a route group?

Thank you for your knowledge and wiliness to share.  And especially thanks to 
this forum for providing us the access.

Cheers

Terry

Terry Oakley
Telecommunications Coordinator | Information Technology Services
Red Deer College |100 College Blvd. | Box 5005 | Red Deer | Alberta | T4N 5H5
work (403) 342-3521   |  FAX (403) 343-4034

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?

[Anthony Holloway]

Does anyone else do this?  Gather all of the documentation ahead of time,
because inevitably you're going to revisit a document more than once?
There are a lot of documents to gather!  Anything I could be doing better?
Tips?  Tricks?

I create a spreadsheet of all of the pertinent documents I need to review
or reference, like in this screenshot.  There's over 90 documents in this
list.  Granted, I don't read them all front to back, but some I do, and
 for others I need to reference information within them nonetheless.  You
never know when you might find a small font hidden note in there.

E.g., From the 8945 Release Notes

*"Release 9.4(2)SR1 can only be upgraded from 9.3(4) and later. Releases
prior to 9.3(4) have to be upgraded to 9.3(4) first."*

*Source: 8945 9.4(2)SR1 Release Notes
*

I actually missed this one recently, and unlike 7900 series phones, they
phone will just brick itself and never register.  Causing you to walk to
every phone and reset power to it, or walk the mac address tables of your
layer 2 network and shut/no shut the ports.

[image: Inline image 1]
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip