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. Ot: cisco live? (Scott Voll)
   2. Cannot Change Fixed Feature Button (Jonathan Charles)
   3. Re: SX20 quickset reg to CM (Ed Leatherman)
   4. Re: Cannot Change Fixed Feature Button (Wes Sisk)
   5. Re: snmp traps on voice gateways (Erick Wellnitz)


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

Message: 1
Date: Sun, 9 Jun 2013 13:33:17 -0700
From: Scott Voll <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] Ot: cisco live?
Message-ID:
        <cahgd+3-aa6srqt3av8os1gs4ufk9fsbcrtu7jyaf6y21z4e...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Has any one found the cisco live app yet?   I'm I just missing it?

Tia

Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130609/6a086dcc/attachment-0001.html>

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

Message: 2
Date: Sun, 9 Jun 2013 17:28:00 -0500
From: Jonathan Charles <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] Cannot Change Fixed Feature Button
Message-ID:
        <caplpvzgltbv0shzr+hv-rzol1g2u9j5gzs6fmg2t-pvfuwl...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

So, a new error message

[image: Inline image 2]

"Fixed feature button(s) 1 cannot be changed.  Please make sure the button
number matches the relative positions in the button list."

When I try to swap lines 2 and 1...


[image: Inline image 1]

When I try to reorder the lines on a Cisco IP Communicator...

Any ideas why?


Jonathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130609/77bc1b87/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 40653 bytes
Desc: not available
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130609/77bc1b87/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 4890 bytes
Desc: not available
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130609/77bc1b87/attachment-0003.png>

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

Message: 3
Date: Mon, 10 Jun 2013 07:10:27 -0400
From: Ed Leatherman <[email protected]>
To: Cisco VOIP <[email protected]>
Subject: Re: [cisco-voip] SX20 quickset reg to CM
Message-ID:
        <cafc4dsrh0koiyofctehe4kfbchupufpmvp521lxbv5yis+7...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Just to circle around on this one for posterity, a Device Pack was
necessary to fix this to work in mixed mode on 8.6(2). Device Pack
8.6.2(23047) or later - I installed 23079 and it worked fine.


On Tue, Jun 4, 2013 at 1:40 PM, Ed Leatherman <[email protected]>wrote:

> Hello everyone,
>
> I'm trying to get a SX20 registered to CUCM 8.6.2.22900, seem to be
> running into a issue getting the configuration file from call manager.
>
> From the logs I'm guessing that the endpoint is trying to download a
> signed xml file, however call manager is not publishing that file for it to
> get:
>
> Jun  4 11:37:39 a8 appl: 13342.74 TRUSTLIST I: Download of trustlist 
> 'http://x.x.x.x:6970/CTLSEPd867d9733a6a.tlv' complete
> Jun  4 11:37:39 a8 appl: 13342.74 PROV I: void 
> CUCMProvision::CUCMProvisionUser::configItem() 
> 'http://x.x.x.x:6970/SEPd867d9733a6a.cnf.xml.sgn'
> Jun  4 11:37:39 a8 appl: 13342.75 PROV !ER HTTP req failed!
>
> It appears to get the trust list file OK.
>
> I can manually download an unsigned file from callmanager from that
> location, but the signed version is not there - I thought all configs were
> signed now? Can't find anything in the SX20 security profile to enable
> signing these and likewise can't find anywhere in the SX20 config to make
> it ask for an unsigned. Anyone have an idea what I've got wrong?
>
> Firmware on the endpoint is TC6.0.0.876266
>
> Cluster is in mixed mode.
>
> Tried resetting TFTP service, didn't help.
>
> Thanks!
> Ed
>
> --
> Ed Leatherman
>



-- 
Ed Leatherman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130610/c58404b5/attachment-0001.html>

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

Message: 4
Date: Mon, 10 Jun 2013 11:07:16 -0400
From: Wes Sisk <[email protected]>
To: Jonathan Charles <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Cannot Change Fixed Feature Button
Message-ID: <[email protected]>
Content-Type: text/plain; charset=iso-8859-1

interesting.  others have found

"you cannot remove the line without adding a new feature back before saving the 
change."

so maybe one part that slot must be filled and another part that the order of 
operations is critical?

-Wes

On Jun 9, 2013, at 6:28 PM, Jonathan Charles <[email protected]> wrote:

So, a new error message

<image.png>

"Fixed feature button(s) 1 cannot be changed.  Please make sure the button 
number matches the relative positions in the button list."

When I try to swap lines 2 and 1...


<image.png>

When I try to reorder the lines on a Cisco IP Communicator...

Any ideas why?


Jonathan

_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip




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

Message: 5
Date: Mon, 10 Jun 2013 09:24:34 -0500
From: Erick Wellnitz <[email protected]>
To: "Jason Aarons (AM)" <[email protected]>
Cc: cisco-voip <[email protected]>
Subject: Re: [cisco-voip] snmp traps on voice gateways
Message-ID:
        <CAK0wOsC92d+KONZ4xrpe7V6Xi_jinryM=j2y2b1x9vtnt-o...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

I have a mix of MGCP and H323.

I know I can't get any layer 3 info from the MGCP PRIs.

The real issue is our SNMP monitoring system.  It is less than
sophisticated and we must push traps to it.  It cannot poll the router like
most good monitoring systems can.


On Fri, Jun 7, 2013 at 4:15 PM, Jason Aarons (AM) <
[email protected]> wrote:

> How is the PRI gateway configured?  H323/SIP/MGCP, etc.  Google should
> come back with this topic, if not Cisco Support Community has several
> threads.****
>
> ** **
>
> With H323 you get a trap every time a channel goes down (eg every call).
> I recall using Syslog and parsing the PRi  for channel 23  (d-channel)
> versus the channels or pulling another MIB verus the interface status.
> RTMT also has some alerting options versus SNMP.****
>
> ** **
>
> *From:* cisco-voip [mailto:[email protected]] *On Behalf
> Of *Erick Wellnitz
> *Sent:* Friday, June 07, 2013 4:54 PM
> *To:* cisco-voip
> *Subject:* [cisco-voip] snmp traps on voice gateways****
>
> ** **
>
> ** **
>
> I admit, I am not the best with SNMP. I have been going through the
> different SNMP settings for 28xx/29xx gateways.    I didn't see any SNMP
> traps for PRI/T1 interfaces, which until we start migrating to a SIP
> solution is important for us to monitor and alert if a PRI goes down.****
>
>  ****
>
> Has anyone configured their gateways to send traps for PRI interaces
> before?  ****
>
>
>
> itevomcid ****
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130610/752ab6f5/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 116, Issue 9
******************************************

Reply via email to