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. UCCE CAD WrapUp CUIC Reports (Ryan Burtch)
2. Re: Jump upgrade/DRS licensing bug (Ryan Ratliff (rratliff))
3. Re: Jump upgrade/DRS licensing bug (Ed Leatherman)
4. ICM Ad-Hoc Closure w/o Administrator Intervention (Ryan Burtch)
5. Re: ICM Ad-Hoc Closure w/o Administrator Intervention
(Brian Meade (brmeade))
6. Re: ICM Ad-Hoc Closure w/o Administrator Intervention
(Brian Meade (brmeade))
7. Re: ICM Ad-Hoc Closure w/o Administrator Intervention
(Erik Goppel)
----------------------------------------------------------------------
Message: 1
Date: Tue, 3 Sep 2013 15:12:56 -0400
From: Ryan Burtch <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] UCCE CAD WrapUp CUIC Reports
Message-ID:
<cak+shf4hvhw9h6r_yivlg9ppe6n3vwh8fj_sxwbl1tw+bwx...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
I need a CUIC report that will allow me to pull wrap-up codes from the
Termination Call Detail records. Does anyone know how to do this?
Sincerely,
Ryan Burtch
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130903/e7bd3fe0/attachment-0001.html>
------------------------------
Message: 2
Date: Tue, 3 Sep 2013 20:20:58 +0000
From: "Ryan Ratliff (rratliff)" <[email protected]>
To: Ed Leatherman <[email protected]>
Cc: Cisco VOIP <[email protected]>
Subject: Re: [cisco-voip] Jump upgrade/DRS licensing bug
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="windows-1252"
The refresh COP file is the one you want as long as it's the latest and you did
them in the correct order. This is the second one I've heard of that the cop
file didn't work correctly for 7.1(5). One of my colleagues tested 6.1(5) last
week and confirmed the steps work but I think we'll need to try a 7.1 just to
be sure.
-Ryan
On Aug 30, 2013, at 12:27 PM, Ed Leatherman
<[email protected]<mailto:[email protected]>> wrote:
OK - perhaps I installed the wrong one then; I installed
ciscocm.refresh_upgrade_v1.2.cop.sgn... sounds like I grabbed the wrong one.
Here was what i did:
-Installed fresh 7.1.5 on all VM nodes, let DB sync
-Installed refresh cop per the upgrade doc (I thought this was an odd place for
it but that?s where it wanted it). Did NOT reboot per the documentation.
-Restored DRS file. Rebooted subs. Rebooted Pub. Let DB sync again.
-At this point, I changed some MAC addresses on some of the configured phones
so I could have a few running in the lab for the upgrade; hind sight I probably
don't need this until everything's on 9
-Tried to install the 9.1 firmware - failed with that error
-Tried to upgrade to 9.1 - also failed with that error
On Fri, Aug 30, 2013 at 12:16 PM, Justin Steinberg
<[email protected]<mailto:[email protected]>> wrote:
there is a COP file that you need to install on 7.1.5 that will disable the
licensing and allow you to goto 9.12
On Fri, Aug 30, 2013 at 10:22 AM, Ed Leatherman
<[email protected]<mailto:[email protected]>> wrote:
Good morning,
I'm running through the jump upgrade in my lab for a regional campus so that I
get all the steps correct. I have the UCS hardware they will upgrade to +
VMWare installed, and everything on isolated lab network.
So I took a known good backup of their production CUCM (3 nodes). Installed
7.1.5 into VMWare per the jump document, and restored the DRS backup onto it,
rebooted subs, rebooted pub; everything went smoothly and I can setup a few
phones on this isolated network and register/call, database happy etc.
However now when I go to load new firmware for 9.1 or upgrade the VM to 9.1.2,
I get the following from the command line:
Upgrades are prohibited during license grace period
which seems to be related to
CSCtb86875<https://www.cisco.com/cisco/psn/bssprt/bss?searchType=bstbugidsearch&page=bstBugDetail&BugID=CSCtb86875>
Licensing page on CUCM doesn't show any issues.
Are other people running into this? I thought I was following through the guide
closely, but it doesn't mention anything about needing to rehost the 7.1
license files or have TAC root in to delete a file during the upgrade.
Since we're likely to run through this exercise a few times (this issue is
exactly why I'm running through it in lab to begin with).. I don't know if its
kosher for me to keep asking licensing to rehome it, since this isn't the
production system. But I guess I will if i need to :)
Where am I going wrong here, or is this normal?
--
Ed Leatherman
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
--
Ed Leatherman
_______________________________________________
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/20130903/afe6ebbc/attachment-0001.html>
------------------------------
Message: 3
Date: Tue, 3 Sep 2013 16:29:22 -0400
From: Ed Leatherman <[email protected]>
To: "Ryan Ratliff (rratliff)" <[email protected]>
Cc: Cisco VOIP <[email protected]>
Subject: Re: [cisco-voip] Jump upgrade/DRS licensing bug
Message-ID:
<cafc4dspa15nij5at7aqrbge_snwpxv35lke__vugw1jpitf...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I'm going thru my steps again - the first time i tried it, I configured
some phones (just changed macs on 2 existing ones) mid-way through the
process to test the restore, and my SE thought that might have tripped a
licensing check. I also didn't have the DRS restart location "exactly" the
same as the production one, so fixing that also.
My next attempt should be by the book without any extra-curricular
activities ><.
On Tue, Sep 3, 2013 at 4:20 PM, Ryan Ratliff (rratliff)
<[email protected]>wrote:
> The refresh COP file is the one you want as long as it's the latest and
> you did them in the correct order. This is the second one I've heard of
> that the cop file didn't work correctly for 7.1(5). One of my colleagues
> tested 6.1(5) last week and confirmed the steps work but I think we'll need
> to try a 7.1 just to be sure.
>
>
> -Ryan
>
> On Aug 30, 2013, at 12:27 PM, Ed Leatherman <[email protected]>
> wrote:
>
> OK - perhaps I installed the wrong one then; I installed
> ciscocm.refresh_upgrade_v1.2.cop.sgn... sounds like I grabbed the wrong
> one.
>
> Here was what i did:
>
> -Installed fresh 7.1.5 on all VM nodes, let DB sync
>
> -Installed refresh cop per the upgrade doc (I thought this was an odd
> place for it but that?s where it wanted it). Did NOT reboot per the
> documentation.
>
> -Restored DRS file. Rebooted subs. Rebooted Pub. Let DB sync again.
>
> -At this point, I changed some MAC addresses on some of the configured
> phones so I could have a few running in the lab for the upgrade; hind sight
> I probably don't need this until everything's on 9
>
> -Tried to install the 9.1 firmware - failed with that error
>
> -Tried to upgrade to 9.1 - also failed with that error
>
>
> On Fri, Aug 30, 2013 at 12:16 PM, Justin Steinberg
> <[email protected]>wrote:
>
>> there is a COP file that you need to install on 7.1.5 that will disable
>> the licensing and allow you to goto 9.12
>>
>>
>> On Fri, Aug 30, 2013 at 10:22 AM, Ed Leatherman
>> <[email protected]>wrote:
>>
>>> Good morning,
>>>
>>> I'm running through the jump upgrade in my lab for a regional campus
>>> so that I get all the steps correct. I have the UCS hardware they will
>>> upgrade to + VMWare installed, and everything on isolated lab network.
>>>
>>> So I took a known good backup of their production CUCM (3 nodes).
>>> Installed 7.1.5 into VMWare per the jump document, and restored the DRS
>>> backup onto it, rebooted subs, rebooted pub; everything went smoothly and I
>>> can setup a few phones on this isolated network and register/call, database
>>> happy etc.
>>>
>>> However now when I go to load new firmware for 9.1 or upgrade the VM
>>> to 9.1.2, I get the following from the command line:
>>> Upgrades are prohibited during license grace period
>>>
>>> which seems to be related to
>>> CSCtb86875<https://www.cisco.com/cisco/psn/bssprt/bss?searchType=bstbugidsearch&page=bstBugDetail&BugID=CSCtb86875>
>>>
>>> Licensing page on CUCM doesn't show any issues.
>>>
>>> Are other people running into this? I thought I was following through
>>> the guide closely, but it doesn't mention anything about needing to rehost
>>> the 7.1 license files or have TAC root in to delete a file during the
>>> upgrade.
>>>
>>> Since we're likely to run through this exercise a few times (this
>>> issue is exactly why I'm running through it in lab to begin with).. I don't
>>> know if its kosher for me to keep asking licensing to rehome it, since this
>>> isn't the production system. But I guess I will if i need to :)
>>>
>>> Where am I going wrong here, or is this normal?
>>>
>>> --
>>> Ed Leatherman
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> [email protected]
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>
>
> --
> Ed Leatherman
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
--
Ed Leatherman
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130903/69d658fe/attachment-0001.html>
------------------------------
Message: 4
Date: Wed, 4 Sep 2013 00:31:51 -0400
From: Ryan Burtch <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] ICM Ad-Hoc Closure w/o Administrator
Intervention
Message-ID:
<CAK+Shf4moRSc_C=dfxeikCANMnhj=0yjelsfhvcjnvwomem...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
All:
I'm looking for a way to have a customer be able to call into an ICM
script>enter in an access code> and be able to 'Ad-Hoc Close' a contact
center.
Does anyone know how to do this?
Sincerely,
Ryan Burtch
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130904/cefacdba/attachment-0001.html>
------------------------------
Message: 5
Date: Wed, 4 Sep 2013 13:39:56 +0000
From: "Brian Meade (brmeade)" <[email protected]>
To: Ryan Burtch <[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [cisco-voip] ICM Ad-Hoc Closure w/o Administrator
Intervention
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
You could just have it update an XML file that your other scripts referenced to
check if the contact center is closed or not.
Brian Meade
From: cisco-voip [mailto:[email protected]] On Behalf Of Ryan
Burtch
Sent: Wednesday, September 04, 2013 12:32 AM
To: [email protected]
Subject: [cisco-voip] ICM Ad-Hoc Closure w/o Administrator Intervention
All:
I'm looking for a way to have a customer be able to call into an ICM
script>enter in an access code> and be able to 'Ad-Hoc Close' a contact center.
Does anyone know how to do this?
Sincerely,
Ryan Burtch
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130904/df3ff58b/attachment-0001.html>
------------------------------
Message: 6
Date: Wed, 4 Sep 2013 14:31:41 +0000
From: "Brian Meade (brmeade)" <[email protected]>
To: Erik Goppel <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] ICM Ad-Hoc Closure w/o Administrator
Intervention
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Erik,
Yea, I was thinking UCCX.
Brian
From: Erik Goppel [mailto:[email protected]]
Sent: Wednesday, September 04, 2013 10:28 AM
To: Brian Meade (brmeade)
Cc: [email protected]; Ryan Burtch
Subject: Re: [cisco-voip] ICM Ad-Hoc Closure w/o Administrator Intervention
Use a persistent user variable like cc_open and set it to true or false by
using a menu in your callin script. Then modify your cc routing script to check
this variable for true or false (if node, example if cc_open== "true", route
like normal under your success connector, under the x fail connector, route to
your closed message)
Good luck,
Using an xml file within icm is not possible afaik , maybe icw cvp, i think
brian is mistaken with uccx.
Brian, if you do know a method to use an xml file in icm for reference, without
having to use ipivr or cvp, please share.
Thanks,
Erik
Op 4 sep. 2013 15:42 schreef "Brian Meade (brmeade)"
<[email protected]<mailto:[email protected]>> het volgende:
You could just have it update an XML file that your other scripts referenced to
check if the contact center is closed or not.
Brian Meade
From: cisco-voip
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Ryan Burtch
Sent: Wednesday, September 04, 2013 12:32 AM
To: [email protected]<mailto:[email protected]>
Subject: [cisco-voip] ICM Ad-Hoc Closure w/o Administrator Intervention
All:
I'm looking for a way to have a customer be able to call into an ICM
script>enter in an access code> and be able to 'Ad-Hoc Close' a contact center.
Does anyone know how to do this?
Sincerely,
Ryan Burtch
_______________________________________________
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/20130904/fdd944cf/attachment-0001.html>
------------------------------
Message: 7
Date: Wed, 4 Sep 2013 16:27:51 +0200
From: Erik Goppel <[email protected]>
To: "Brian Meade (brmeade)" <[email protected]>
Cc: [email protected]
Subject: Re: [cisco-voip] ICM Ad-Hoc Closure w/o Administrator
Intervention
Message-ID:
<cahtx7xhppn91komvbzmssh56benkb2pt5r-1oskif2x570r...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Use a persistent user variable like cc_open and set it to true or false by
using a menu in your callin script. Then modify your cc routing script to
check this variable for true or false (if node, example if cc_open==
"true", route like normal under your success connector, under the x fail
connector, route to your closed message)
Good luck,
Using an xml file within icm is not possible afaik , maybe icw cvp, i think
brian is mistaken with uccx.
Brian, if you do know a method to use an xml file in icm for reference,
without having to use ipivr or cvp, please share.
Thanks,
Erik
Op 4 sep. 2013 15:42 schreef "Brian Meade (brmeade)" <[email protected]>
het volgende:
> You could just have it update an XML file that your other scripts
> referenced to check if the contact center is closed or not.****
>
> ** **
>
> Brian Meade****
>
> ** **
>
> *From:* cisco-voip [mailto:[email protected]] *On Behalf
> Of *Ryan Burtch
> *Sent:* Wednesday, September 04, 2013 12:32 AM
> *To:* [email protected]
> *Subject:* [cisco-voip] ICM Ad-Hoc Closure w/o Administrator Intervention*
> ***
>
> ** **
>
> All:****
>
> ** **
>
> I'm looking for a way to have a customer be able to call into an ICM
> script>enter in an access code> and be able to 'Ad-Hoc Close' a contact
> center.****
>
> ** **
>
> Does anyone know how to do this?
> ****
>
> ** **
>
> ** **
>
> ** **
>
> Sincerely,****
>
> ** **
>
> Ryan Burtch****
>
> _______________________________________________
> 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/20130904/ce370b17/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
------------------------------
End of cisco-voip Digest, Vol 119, Issue 4
******************************************
