[cisco-voip] CallManager 7x to 8.5(1) and Attendant Console

Rhodes, Geoff GRhodes at rbh.com
Wed Feb 23 17:19:46 EST 2011 

And the ARC SC replacement simply stinks!  Our receptionists say we have
taken 3 steps backwards in functionality.  Painful doesn't begin to
describe it..

 

 

Geoffrey S. Rhodes

Director of Information Technology

Robinson, Bradshaw & Hinson, P.A.

101 N. Tryon St., Suite 1900

Charlotte, NC  28246-1900

704.377.2536

704.339.3488 (fax)

grhodes at rbh.com

 

 

 

 

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Buchanan, James
Sent: Sunday, February 20, 2011 2:32 PM
To: David Lee; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CallManager 7x to 8.5(1) and Attendant Console

 

The old version is totally gone with 8. The service doesn't exist-it has
been totally removed. 

 

You will definitely want to get the 60 day trial of the new ARC AC. This
is not a one-to-one replacement of the old Attendant Console, so you'll
want to see for yourself what you're getting into. 

 

Thanks,

 

James Buchanan | Technology Manager, UC | South Region | Presidio
Networked Solutions 
12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | jbuchanan at presidio.com
<mailto:jbuchanan at ctiusa.com> 
D: 615-866-5729 | F: 615-866-5781 | www.presidio.com
<http://www.presidio.com/>  

CCIE #25863, Voice

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of David Lee
Sent: Sunday, February 20, 2011 1:24 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] CallManager 7x to 8.5(1) and Attendant Console

 

The old AC is supported until v7.x IF you are doing an upgrade from
previous versions.  It is not supported if it's a fresh install, but if
you have the installation file, it will probably work.  Once you hit v8,
the support is completely withheld.  You will have to buy one of the
re-branded ARC attendant consoles.  Please see this link for more
details. 

http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps7046/ps7282/
end_of_life_notice_c51-499091.html

Just an FYI - the ARC ACs come with a 60 day trial, so the customer have
some time to buy the license if they "forgot" to buy it.  (Personally, I
wouldn't try to get the old AC to work with v8 simply because Cisco
specifically say it's not supported, and I don't want to install
anything that is not officially supported.)

On Sun, Feb 20, 2011 at 12:00 PM, <cisco-voip-request at puck.nether.net>
wrote:

Send cisco-voip mailing list submissions to
       cisco-voip at puck.nether.net

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
       cisco-voip-request at puck.nether.net

You can reach the person managing the list at
       cisco-voip-owner at puck.nether.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."


Today's Topics:

  1. Re: CUCM Upgrade (Buchanan, James)
  2. Re: CUCM Upgrade (Lelio Fulgenzi)
  3. Re: CUCM Upgrade (Buchanan, James)
  4. Re: CUCM Upgrade (Lelio Fulgenzi)
  5. Re: CUCM Upgrade (Buchanan, James)
  6. Re: CCM7 day to day admin tips ? (Tony Edwards)
  7. Re: R: R: Phones randomply reset (Karen Cheng)
  8. CallManager 7x  to 8.5(1) and Attendant Console
     (Jason Aarons (US))


----------------------------------------------------------------------

Message: 1
Date: Sat, 19 Feb 2011 13:07:15 -0500
From: "Buchanan, James" <jbuchanan at presidio.com>
To: "H, Tim" <TimH at trstone.com>, "cisco-voip at puck.nether.net"
       <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] CUCM Upgrade
Message-ID:
       <853687641CF93E40B362F112A3D8F3CE1724B85B at SOEXCH01.Presidio.Corp>
Content-Type: text/plain; charset="us-ascii"

I had a customer do this last Sunday. The only change was the firmware.
Attendant Console was unaffected. If you don't want to deal with the
firmware, you could hard code the firmware on the phones until you are
ready for the jump because the old firmware will stay on the server.

James Buchanan | Technology Manager, UC | South Region | Presidio
Networked Solutions
12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | 
jbuchanan at presidio.com<mailto:jbuchanan at ctiusa.com>
D: 615-866-5729 | F: 615-866-5781 | www.presidio.com<
http://www.presidio.com/>
CCIE #25863, Voice


From: cisco-voip-bounces at puck.nether.net [mailto:
cisco-voip-bounces at puck.nether.net] On Behalf Of H, Tim
Sent: Saturday, February 19, 2011 8:13 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] CUCM Upgrade

All,

I'm getting ready to upgrade our CUCM cluster from 7.02 to 7.15.  I'm
aware of the firmware jump as you have to upgrade to 8.52sr1 or
whatever, but is there anything else I need to be cautious about?  Looks
like the attendant console might change a bit in the version jump, but
should still function?

Any other caveats that anyone have ran into would be helpful.

Thanks,
Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
https://puck.nether.net/pipermail/cisco-voip/attachments/20110219/62f89f
e9/attachment-0001.html>

------------------------------

Message: 2
Date: Sat, 19 Feb 2011 13:09:30 -0500 (EST)
From: Lelio Fulgenzi <lelio at uoguelph.ca>
To: "Buchanan, James" <jbuchanan at presidio.com>
Cc: "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] CUCM Upgrade
Message-ID: <6328DC44-8AED-4C39-9EAF-F10F43FF6E88 at uoguelph.ca>
Content-Type: text/plain; charset="utf-8"

You could also change the device defaults firmware config parameters.

Sent from my iPhone

On Feb 19, 2011, at 1:07 PM, "Buchanan, James" <jbuchanan at presidio.com>
wrote:

> I had a customer do this last Sunday. The only change was the
firmware. Attendant Console was unaffected. If you don?t want to deal
with the firmware, you could hard code the firmware on the phones until
you are ready for the jump because the old firmware will stay on the
server.
>
>
>
> James Buchanan | Technology Manager, UC | South Region | Presidio
Networked Solutions
> 12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | 
jbuchanan at presidio.com
> D: 615-866-5729 | F: 615-866-5781 | www.presidio.com
>
> CCIE #25863, Voice
>
>
>
>
> From: cisco-voip-bounces at puck.nether.net [mailto:
cisco-voip-bounces at puck.nether.net] On Behalf Of H, Tim
> Sent: Saturday, February 19, 2011 8:13 AM
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] CUCM Upgrade
>
>
>
> All,
>
>
>
> I'm getting ready to upgrade our CUCM cluster from 7.02 to 7.15.  I'm
aware of the firmware jump as you have to upgrade to 8.52sr1 or
whatever, but is there anything else I need to be cautious about?  Looks
like the attendant console might change a bit in the version jump, but
should still function?
>
>
>
> Any other caveats that anyone have ran into would be helpful.
>
>
>
> Thanks,
>
> Tim
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
https://puck.nether.net/pipermail/cisco-voip/attachments/20110219/243b20
d4/attachment-0001.html>

------------------------------

Message: 3
Date: Sat, 19 Feb 2011 13:13:11 -0500
From: "Buchanan, James" <jbuchanan at presidio.com>
To: Lelio Fulgenzi <lelio at uoguelph.ca>
Cc: "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] CUCM Upgrade
Message-ID:
       <853687641CF93E40B362F112A3D8F3CE1724B85E at SOEXCH01.Presidio.Corp>
Content-Type: text/plain; charset="utf-8"

No, that won?t do it because the upgrade will change it to the latest
version. It would need to be changed on the phones.

James Buchanan | Technology Manager, UC | South Region | Presidio
Networked Solutions
12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | 
jbuchanan at presidio.com<mailto:jbuchanan at ctiusa.com>
D: 615-866-5729 | F: 615-866-5781 | www.presidio.com<
http://www.presidio.com/>
CCIE #25863, Voice


From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
Sent: Saturday, February 19, 2011 12:10 PM
To: Buchanan, James
Cc: H, Tim; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUCM Upgrade

You could also change the device defaults firmware config parameters.

Sent from my iPhone

On Feb 19, 2011, at 1:07 PM, "Buchanan, James" <
jbuchanan at presidio.com<mailto:jbuchanan at presidio.com>> wrote:
I had a customer do this last Sunday. The only change was the firmware.
Attendant Console was unaffected. If you don?t want to deal with the
firmware, you could hard code the firmware on the phones until you are
ready for the jump because the old firmware will stay on the server.

James Buchanan | Technology Manager, UC | South Region | Presidio
Networked Solutions
12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | 
jbuchanan at presidio.com<mailto:jbuchanan at presidio.com>
D: 615-866-5729 | F: 615-866-5781 | www.presidio.com<
http://www.presidio.com>
CCIE #25863, Voice



From: cisco-voip-bounces at puck.nether.net<mailto:
cisco-voip-bounces at puck.nether.net> [mailto:
cisco-voip-bounces at puck.nether.net] On Behalf Of H, Tim
Sent: Saturday, February 19, 2011 8:13 AM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] CUCM Upgrade

All,

I'm getting ready to upgrade our CUCM cluster from 7.02 to 7.15.  I'm
aware of the firmware jump as you have to upgrade to 8.52sr1 or
whatever, but is there anything else I need to be cautious about?  Looks
like the attendant console might change a bit in the version jump, but
should still function?

Any other caveats that anyone have ran into would be helpful.

Thanks,
Tim
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
https://puck.nether.net/pipermail/cisco-voip/attachments/20110219/6feda7
d3/attachment-0001.html>

------------------------------

Message: 4
Date: Sat, 19 Feb 2011 13:20:06 -0500 (EST)
From: Lelio Fulgenzi <lelio at uoguelph.ca>
To: "Buchanan, James" <jbuchanan at presidio.com>
Cc: "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] CUCM Upgrade
Message-ID: <7056B91F-D4C6-40CF-A38F-9B05AE87FEAB at uoguelph.ca>
Content-Type: text/plain; charset="utf-8"

If I'm not mistaken, you can upgrade the publisher first, change the
device defaults, then upgrade the subs. We've been doing something
similar on 4.1 for years.

Sent from my iPhone

On Feb 19, 2011, at 1:13 PM, "Buchanan, James" <jbuchanan at presidio.com>
wrote:

> No, that won?t do it because the upgrade will change it to the latest
version. It would need to be changed on the phones.
>
>
>
> James Buchanan | Technology Manager, UC | South Region | Presidio
Networked Solutions
> 12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | 
jbuchanan at presidio.com
> D: 615-866-5729 | F: 615-866-5781 | www.presidio.com
>
> CCIE #25863, Voice
>
>
>
>
> From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
> Sent: Saturday, February 19, 2011 12:10 PM
> To: Buchanan, James
> Cc: H, Tim; cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] CUCM Upgrade
>
>
>
> You could also change the device defaults firmware config parameters.
>
> Sent from my iPhone
>
>
> On Feb 19, 2011, at 1:07 PM, "Buchanan, James" <
jbuchanan at presidio.com> wrote:
>
> I had a customer do this last Sunday. The only change was the
firmware. Attendant Console was unaffected. If you don?t want to deal
with the firmware, you could hard code the firmware on the phones until
you are ready for the jump because the old firmware will stay on the
server.
>
>
>
> James Buchanan | Technology Manager, UC | South Region | Presidio
Networked Solutions
> 12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | 
jbuchanan at presidio.com
> D: 615-866-5729 | F: 615-866-5781 | www.presidio.com
>
> CCIE #25863, Voice
>
>
>
>
>
> From: cisco-voip-bounces at puck.nether.net [mailto:
cisco-voip-bounces at puck.nether.net] On Behalf Of H, Tim
> Sent: Saturday, February 19, 2011 8:13 AM
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] CUCM Upgrade
>
>
>
> All,
>
>
>
> I'm getting ready to upgrade our CUCM cluster from 7.02 to 7.15.  I'm
aware of the firmware jump as you have to upgrade to 8.52sr1 or
whatever, but is there anything else I need to be cautious about?  Looks
like the attendant console might change a bit in the version jump, but
should still function?
>
>
>
> Any other caveats that anyone have ran into would be helpful.
>
>
>
> Thanks,
>
> Tim
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
https://puck.nether.net/pipermail/cisco-voip/attachments/20110219/1058b4
88/attachment-0001.html>

------------------------------

Message: 5
Date: Sat, 19 Feb 2011 13:21:34 -0500
From: "Buchanan, James" <jbuchanan at presidio.com>
To: Lelio Fulgenzi <lelio at uoguelph.ca>
Cc: "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] CUCM Upgrade
Message-ID:
       <853687641CF93E40B362F112A3D8F3CE1724B85F at SOEXCH01.Presidio.Corp>
Content-Type: text/plain; charset="utf-8"

Yes, you could do that and that would definitely keep your phones from
getting the new firmware. Good idea!

James Buchanan | Technology Manager, UC | South Region | Presidio
Networked Solutions
12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | 
jbuchanan at presidio.com<mailto:jbuchanan at ctiusa.com>
D: 615-866-5729 | F: 615-866-5781 | www.presidio.com<
http://www.presidio.com/>
CCIE #25863, Voice


From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
Sent: Saturday, February 19, 2011 12:20 PM
To: Buchanan, James
Cc: H, Tim; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUCM Upgrade

If I'm not mistaken, you can upgrade the publisher first, change the
device defaults, then upgrade the subs. We've been doing something
similar on 4.1 for years.

Sent from my iPhone

On Feb 19, 2011, at 1:13 PM, "Buchanan, James" <
jbuchanan at presidio.com<mailto:jbuchanan at presidio.com>> wrote:
No, that won?t do it because the upgrade will change it to the latest
version. It would need to be changed on the phones.

James Buchanan | Technology Manager, UC | South Region | Presidio
Networked Solutions
12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | 
jbuchanan at presidio.com<mailto:jbuchanan at presidio.com>
D: 615-866-5729 | F: 615-866-5781 | www.presidio.com<
http://www.presidio.com>
CCIE #25863, Voice



From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
Sent: Saturday, February 19, 2011 12:10 PM
To: Buchanan, James
Cc: H, Tim; cisco-voip at puck.nether.net<mailto:
cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] CUCM Upgrade

You could also change the device defaults firmware config parameters.

Sent from my iPhone

On Feb 19, 2011, at 1:07 PM, "Buchanan, James" <
jbuchanan at presidio.com<mailto:jbuchanan at presidio.com>> wrote:
I had a customer do this last Sunday. The only change was the firmware.
Attendant Console was unaffected. If you don?t want to deal with the
firmware, you could hard code the firmware on the phones until you are
ready for the jump because the old firmware will stay on the server.

James Buchanan | Technology Manager, UC | South Region | Presidio
Networked Solutions
12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | 
jbuchanan at presidio.com<mailto:jbuchanan at presidio.com>
D: 615-866-5729 | F: 615-866-5781 | www.presidio.com<
http://www.presidio.com>
CCIE #25863, Voice




From: cisco-voip-bounces at puck.nether.net<mailto:
cisco-voip-bounces at puck.nether.net> [mailto:
cisco-voip-bounces at puck.nether.net] On Behalf Of H, Tim
Sent: Saturday, February 19, 2011 8:13 AM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] CUCM Upgrade

All,

I'm getting ready to upgrade our CUCM cluster from 7.02 to 7.15.  I'm
aware of the firmware jump as you have to upgrade to 8.52sr1 or
whatever, but is there anything else I need to be cautious about?  Looks
like the attendant console might change a bit in the version jump, but
should still function?

Any other caveats that anyone have ran into would be helpful.

Thanks,
Tim
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
https://puck.nether.net/pipermail/cisco-voip/attachments/20110219/6cc5ec
9f/attachment-0001.html>

------------------------------

Message: 6
Date: Sun, 20 Feb 2011 10:38:38 +1100
From: Tony Edwards <tonyedwards.rs at gmail.com>
To: Anthony Holloway <avholloway+cisco-voip at gmail.com
<mailto:avholloway%2Bcisco-voip at gmail.com> >
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CCM7 day to day admin tips ?
Message-ID:
       <AANLkTimMn_4xmUBtu-5oUvth8aUODXUC02jpGYjx=DVB at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

your modified url works , Anthony :-) thanks for that.

tony



On Fri, Feb 18, 2011 at 2:09 AM, Anthony Holloway <
avholloway+cisco-voip at gmail.com
<mailto:avholloway%2Bcisco-voip at gmail.com> > wrote:

> Close, but it should look like this:
>
>
> 
http://192.168.10.100:8080/emapp/EMAppServlet?device=SEP1234567&userid=t
estuser&seq=99999
>
> Anthony
>
>   On Thu, Feb 17, 2011 at 5:03 AM, Tony Edwards <tonyedwards.rs@
gmail.com>wrote:
>
>>   hi Stephen,
>>
>> thanks for your unifiedfx advise.i will check them out shortly.
>>
>>
>>
>> hi Bernard,
>>
>> thanks a lot for your detailed explanations. great work indeed.now ,
can i
>> please ask you couple of questions on what you said below.
>>
>> With EM Login URL syntax, is the following correct ?
>>
>> 
http://<192.168.10.100>:8080/emapp/EMAppServlet?SEP1234567=<leSEP1234567
>&userid=<le
<http://%3c192.168.10.100%3e:8080/emapp/EMAppServlet?SEP1234567=%3cleSEP
1234567%3e&userid=%3cle>  testuser>&seq=<le 99999>
>>
>> where my pub ip is 192.168.10.100 and user pin is 99999 and the
device
>> name SEP1234567.
>>
>> Also , let us say , if I have 100 users whom I wants to remote login
to
>> their EM profiles , let us say after some maintenance works on the
cluster,
>> shall I have to run this URL on my http gui single time every user ?
or can
>> I bulk them up all in one go ?
>>
>> secondly, with my vg224 display , yes , i did try with show endpoints
to
>> yes , but when you click on end points , she will show me ip adds and
>> descriptions ...etc. but if i click on vg device itself , then it
show me
>> all ports in a serial fashion like , 0/1 , 0/2 , 0/3..etc
>>
>> but still , it will not show me what i used to have with in ccm4 like
>> following with both port vs dn mappings such as,
>> 0/1 - 1011
>> 0/2 - 1012
>> 0/3 - blank
>> 0/4 - 1014
>> .
>> .
>> .
>> 0/24 -1024
>>
>> ...etc
>>
>>
>> thanks
>>
>> tony
>>
>>   On Wed, Feb 16, 2011 at 10:03 PM, Bernhard Albler <
>> bernhard.albler at gmail.com> wrote:
>>
>>> Hi Tony,
>>>
>>>
>>> >
>>> > 1) my ccm 7x admin gui keeps on logging me out , so how i can make
my
>>> login a permanent for few hours at least , let us say 8am to 5pm ,
if not
>>> for any longer ?
>>> >
>>> Known issue, i believe this is not fixable right now. See CSCsj45520
for
>>> details
>>>
>>> >
>>> > 2) how can remote login my users across wan ? cause , i heard that
>>> there is a url with which you can remotely login any extension
mobility user
>>> , even though you can logout the same user via device gui section ?
>>> >
>>> Two options
>>> 1.)Use AXL (quite easy to do). There is even an example script to do
>>> this in the pyaxl distribution from TU Chemnitz
>>> (http://www.kra-se.de/pyAXL/)
>>> 2.)You can always use the normal EM Login URL in the following form:
>>> http://<ucm>:8080/emapp/EMAppServlet?device=<le
<http://%3cucm%3e:8080/emapp/EMAppServlet?device=%3cle>
device>&userid=<le
>>> username>&seq=<le highly secret pin code of the user>
>>> Devicename includes SEP + the mac.
>>> For this to work you need to know the pin of the user
>>>
>>> > 3) with in my previous ccm4 platform , i use to have a vg224 gui
>>> display under device menu i.e and in this display , there used to be
very
>>> useful info or "ports vs associated dn Numbers" mapping and you used
to see
>>> which ports are vacant ..etc after the ccm7x migration , i could not
display
>>> similar useful info unfortunately. so , is there any way i can
extract this
>>> vg224 ports vs dn numbers view ?
>>> >
>>> Hmm, not sure which view you mean. did you check the GW view with
>>> "show endpoints" set to yes?
>>>
>>>
>>> > 4) speaking of display , another display i found very useful in my
>>> previous ccm4x platform was that , you can actually navigate between
>>> "device/mac + loged out dn ( i.e base dn with out any extension
mobility or
>>> device profile dn) + loged in dn ( i.e with device profile dn). Is
there any
>>> way , i can view similar 3 way mappings with in ccm7 admin gui ?
>>> >
>>> So the DB model for a EM login has changed quite a bit. Logins are
now
>>> done just via a relational association.
>>> You have two options:
>>> 1.)go via Device->Actively logged in Devices. Just be aware that
>>> whenever you click on the device you will get the logged out dn
there
>>> 2.)Dependency records. Newer CCM versions will show a Dependency
>>> record for the extensionmobilitydynamic table (unfortunately labeled
>>> as "null"). So this gives you some info as well
>>> 3.)run the following query on the cli
>>> run sql select d.name,d.description,np.dnorpattern as
>>> loggedoutdn,emdn.dnorpattern emdn from device d,device
>>> profile,extensionmobilitydynamic em,devicenumplanmap
>>> dnmp,devicenumplanmap dnmp2,numplan np,numplan emdn where
>>> d.pkid=dnmp.fkdevice and dnmp.fknumplan=np.pkid and
d.pkid=em.fkdevice
>>> and em.fkdevice_currentloginprofile=profile.pkid and
>>> profile.pkid=dnmp2.fkdevice and dnmp2.fknumplan=emdn.pkid
>>> this should at least give you a bit a easy view who is logged in
where
>>> (no navigating from there though :-( )
>>>
>>> cheerio
>>> bernhard
>>>
>>
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
https://puck.nether.net/pipermail/cisco-voip/attachments/20110220/910c0f
a5/attachment-0001.html>

------------------------------

Message: 7
Date: Sun, 20 Feb 2011 22:40:02 +1000
From: Karen Cheng <kaz.cheng at gmail.com>
To: Mauro Celli <mauro.celli at 2000net.it>
Cc: "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] R: R: Phones randomply reset
Message-ID:
       <AANLkTi=nfxnai1kujrNFO==d_TqZ5GFcUeSbFanOWtKM at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Heya,

Judging from your logs it seems more to do with path changes/vlan
changes.
What type of switches and phone firmware are you running?

Are they attached to a stack of switches? If so are there multiple paths
in/out or spanning-tree loop that could be directly associated to your
voice
vlan?

Regards

Karen

On Fri, Feb 18, 2011 at 10:34 PM, Mauro Celli <
mauro.celli at 2000net.it>wrote:

> The phones reset only when i press some key.
> If i leave in stand-by, no reset occured.
>
> Another log. in this PAE: SIGIPCFG received... is missing
>
> NOT 11:45:09.533159 CDP-D: catchipcfg:getdhcpinfo IP:1001497 domain:
> fiphre1.2000net.it chngVal:1
> NOT 11:45:09.576221 CDP-D: catchipcfg:getdhcpinfo IP:1001497 domain:
> fiphre1.2000net.it chngVal:1
> NOT 11:45:09.581101 tftpClient: request server 0 ---> 1.1.254.3
> ERR 11:45:09.583327 RTSOLD: opvvlan:4095->4095 advvlan:4096->4096
> ERR 11:45:09.587012 RTSOLD: LINK -> LINK
> ERR 11:45:09.587784 RTSOLD:address mode changed..
>
>
>
>
>
> Da: Daniel [mailto:dan.voip at danofive.id.au]
> Inviato: venerd? 18 febbraio 2011 02:52
> A: Mauro Celli
> Cc: Stephen Welsh; cisco-voip at puck.nether.net
> Oggetto: Re: [cisco-voip] R: Phones randomply reset
>
> I agree with Stephen,
>
> We see alot of restarts from DHCP issues, we run DHCP from the router
and
> IP conflict logging is a pain as you start to run out of IPs real
quick so
> we turn logging off.
>
> The other issue could be the "Maximum Number of Registered Devices"
call
> manager service parameter. When we got to over 5000 phones weird
things
> started with phone reboots and registration. Changed the value to fit
our
> cluster and all is ok.
>
>
> On Fri, Feb 18, 2011 at 8:32 AM, Mauro Celli <mauro.celli at 2000net.it>
> wrote:
> This is observed in multiple installation,
> 7945 7970 7975 are those  who restarted more...
> Poe is ok...
>
> -----Messaggio originale-----
> Da: Stephen Welsh [mailto:stephen.welsh at unifiedfx.com]
> Inviato: gioved? 17 febbraio 2011 22:51
> A: Mauro Celli
> Cc: cisco-voip at puck.nether.net
> Oggetto: Re: [cisco-voip] Phones randomply reset
>
> Nothing I can tell from the logs, but I've seen this when there is
more
> phones in a subnet/VLAN than there is IP Addresses, as some phones
fight for
> an IP address lease.
>
> Stephen
>
> On 17 Feb 2011, at 21:03, Mauro Celli wrote:
>
> >
> > We have an issue in some IP phones,it keep resetting randomly.
> > Below is an extract from one of the console logs from the phone.
> >
> > Can anyone interpret what exactly is causing the restart?
> >
> > Note,i have disabled cdp and lldp in cucm phone properties  with no
> success...
> > Thanks
> >
> > NOT 16:08:49.258777 PAE: SIGIPCFG received...
> > NOT 16:08:49.262716 CDP-D: catchipcfg:getdhcpinfo IP:10014aa
> domain:xxx.xxx.xx chngVal:1
> > NOT 16:08:49.307331 CDP-D: catchipcfg:getdhcpinfo IP:10014aa
> domain:xxx.xxx.xx chngVal:1
> > NOT 16:08:49.322263 tftpClient: request server 0 ---> 10.1.254.3
> > ERR 16:08:49.324461 RTSOLD: opvvlan:4095->4095 advvlan:4096->4096
> > ERR 16:08:49.327917 RTSOLD: LINK -> LINK
> > ERR 16:08:49.328677 RTSOLD:address mode changed..
> > NOT 16:08:49.345190 tftpClient: request server 1 --->
> > ERR 16:08:49.355400 RTSOLD: opvvlan:4095->4095 advvlan:4096->4096
> > ERR 16:08:49.361458 RTSOLD: LINK -> LINK
> > NOT 16:08:49.365233 tftpClient: request server 0 ---> 10.1.254.3
> > NOT 16:08:49.372982 ESP: server 0 = 1.1.254.3
> > NOT 16:08:49.382033 tftpClient: request server 1 --->
> > NOT 16:08:49.384385 ESP: server 1 =
> > NOT 16:08:49.395732 tftpClient: request server6 0 ---> ::
> > NOT 16:08:49.396802 ESP: server 2 = ::
> > NOT 16:08:49.417733 tftpClient: request server6 1 ---> ::
> > NOT 16:08:49.420555 ESP: server 3 = ::
> > NOT 16:08:49.423144 ESP: send ADMIN, logging = 1, shell = 0,
ipconfig = 1
> > NOT 16:08:49.443032 tftpClient: request server6 0 ---> ::
> > NOT 16:08:49.449721 tftpClient: request server6 1 ---> ::
> > NOT 16:08:49.465934 JVM: Startup Module
Loader|cip.cfg.ConfigManager:? -
> ConfigManager PropertyChanged: device.settings.network.ipstacksstate
> > NOT 16:08:49.467530 JVM: Startup Module
Loader|cip.cfg.ConfigManager:? -
> ConfigManager IP_STACKS_STATE changed
> > NOT 16:08:49.469131 JVM: Startup Module
Loader|cip.cfg.ConfigManager:? -
>   IPv4 state=DHCP BOUND
> > NOT 16:08:49.470741 JVM: Startup Module
Loader|cip.cfg.ConfigManager:? -
>   IPv6 state=STACK TURNED OFF
> > WRN 16:08:49.478478 SECD: WARN:getCTLInfo: ** phone has no CTL
> > WRN 16:08:49.483464 SECD: WARN:getCTLInfo: ** phone has no CTL
> > NOT 16:08:49.493588 tftpClient: request server 0 ---> 10.1.254.3
> >
> >
> > Cordiali saluti
> > Mauro Celli (work in progress...)
> >
> >
> >
> >
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
https://puck.nether.net/pipermail/cisco-voip/attachments/20110220/32e4a7
f7/attachment-0001.html>

------------------------------

Message: 8
Date: Sun, 20 Feb 2011 09:15:12 -0500
From: "Jason Aarons (US)" <jason.aarons at us.didata.com>
To: "cisco-voip (cisco-voip at puck.nether.net)"
       <cisco-voip at puck.nether.net>
Subject: [cisco-voip] CallManager 7x  to 8.5(1) and Attendant Console
Message-ID:
       <
4E38DB0A1959B04C8C83EDCF069B53ED0C9D80A82D at USISPCLEXDB01.na.didata.local
>

Content-Type: text/plain; charset="us-ascii"

I understood the Attendant Console Service/TCD is no longer present in
CallManager 8.x, is it 8.0 or 8.5(1).

So if they had 7x with the migrated Attendant Console and go to 8.5(1)
the old AC application should stop working.   I just haven't tested it.
Are the services gone completely under Serviceability ? AC used TCD
right?


-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
https://puck.nether.net/pipermail/cisco-voip/attachments/20110220/f5698b
40/attachment-0001.html>

------------------------------

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


End of cisco-voip Digest, Vol 88, Issue 19
******************************************

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110223/77f86cdb/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2790 bytes
Desc: image001.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110223/77f86cdb/attachment.jpg>

More information about the cisco-voip mailing list