(brmeade); 'cisco-voip@puck.nether.net'
Subject: RE: 7945 VPN option
Afternoon Brian,
I have checked this and Auto Network Detect is off.
Do you have any other suggestions?
The firmware level is: SCCP45.9-3-1SR1-1S
From: Brian Meade (brmeade) [mailto:brme...@cisco.com]
Sent: 24 January 2014 20:28
http://x.x.x.x:6970/SEPMAC.cnf.xmlhttp://x.x.x.x:6970/SEP%3cMAC%3e.cnf.xml
Replace x.x.x.x with a node on your cluster running TFTP service.
From: James Dust [mailto:james.d...@charles-stanley.co.uk]
Sent: Monday, January 27, 2014 10:01 AM
To: Brian Meade (brmeade); 'cisco-voip@puck.nether.net
replication state and
utils dbreplication status to check for any mismatched tables.
Brian
From: James Dust [mailto:james.d...@charles-stanley.co.uk]
Sent: Monday, January 27, 2014 10:23 AM
To: Brian Meade (brmeade); 'cisco-voip@puck.nether.net'
Subject: RE: 7945 VPN option
Thanks Brian,
It looks
Erick,
I'd suggest doing sip bind's based on dial-peer on your CUBE.
https://supportforums.cisco.com/community/netpro/collaboration-voice-video/ip-telephony/blog/2013/04/04/cube-sip-media-and-signalling-binding-to-an-interface
Brian
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net]
All X.0 software has to be ordered through PUT which is why you don't see it.
PUT will give you a bootable you could use for upgrade or direct install.
-Original Message-
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of
Robert Kulagowski
Sent: Monday, January
Message-
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Brian
Meade (brmeade)
Sent: Monday, January 27, 2014 1:52 PM
To: Robert Kulagowski; Cisco VOIP
Subject: Re: [cisco-voip] Unity Connection 10.0 / SAML
All X.0 software has to be ordered through PUT which is why you
Erick,
You can add a 2nd cert to the VPN Gateway configuration after you add it as a
VPN-Trust.
So what you want to do is create a new trustpoint on the ASA with the new
certificate, upload that to CUCM as a phone-vpn-trust, and then add it as a 2nd
cert to the VPN Gateway.
You'll then want
Viki,
What do you see getting negotiated for DTMF on the CUCM side? You might want
to try forcing out-of-band on the CUCM side. Try changing the DTMF Signaling
Method to OOB and RFC 2833.
Brian
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of
vignesh sethuraman
.pem.
Thanks,
Brian
From: Erick Wellnitz [mailto:ewellnitzv...@gmail.com]
Sent: Thursday, January 30, 2014 3:24 PM
To: Brian Meade (brmeade)
Cc: cisco-voip
Subject: Re: [cisco-voip] cisco phone-vpn cert expiration
This dd not work as described.
The new cert took the place of the old one
. But it may be a little
risky opening up the TFTP service on one node to the outside world temporarily.
From: Erick Wellnitz [mailto:ewellnitzv...@gmail.com]
Sent: Thursday, January 30, 2014 3:51 PM
To: Brian Meade (brmeade)
Cc: cisco-voip
Subject: Re: [cisco-voip] cisco phone-vpn cert expiration
Joe,
The best resource for stuff like this is to log into the Unified Reporting page
in CUCM and select Unified CM Phone Feature List then generate a new report
with the Feature selected as Security By Default. That list should always be
correct.
Thanks,
Brian Meade
From: cisco-voip
Jason,
Do you have an SR number I can take a look at to do some investigating on this?
Thanks,
Brian
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Jason
Aarons (AM)
Sent: Monday, February 03, 2014 9:16 AM
To: Henry Gicheru (KE); Henry Gicheru (KE); Lelio Fulgenzi;
Angel,
You can just go under Bulk Administration-Phones-Add/Update Lines-Update
Lines. Just click Find to select all the DNs on the system, then click Next.
From there, place a check box next to Voice Mail Profile and select your new
Voice Mail Profile. Then you just need to check Run
in the connections on
the gateway not being torn down 100%.
Brian
From: Eric Pedersen [mailto:peders...@bennettjones.com]
Sent: Monday, February 03, 2014 3:02 PM
To: Brian Meade (brmeade); cisco-voip@puck.nether.net
Subject: RE: Stuck conferences on 2911
Thanks Brian. I'll keep an eye on it. I
, 2014 2:57 PM
To: Brian Meade (brmeade)
Cc: cisco-voip (cisco-voip@puck.nether.net)
Subject: Re: [cisco-voip] unpublished bug listed on 9.1(2)SU1 release notes:
CSCui43689
Hi again Brian.
I also noticed that in the release notes, the phone firmware listing is
incorrect. It shows *.9-3-1SR2-1
James,
The audit logs are going to be your best bet. They don't give a ton of info on
what specifically was changed though.
Brian
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of James
Dust
Sent: Wednesday, February 05, 2014 6:59 AM
To: cisco-voip@puck.nether.net
Lelio,
That warning message on the DRS webpage was added back in 6.x. as part of
CSCsu59755. It looks like there were a lot of replication problems when
restoring all the nodes at once so their fix was just to add that message of
restoring the publisher first. It looks like the bug mentions
all” from the publisher.
Since it’s only a 2-node cluster, it should be pretty quick to get it back to a
2.
Thanks,
Brian
From: Lelio Fulgenzi [mailto:le...@uoguelph.ca]
Sent: Tuesday, February 11, 2014 11:50 AM
To: Brian Meade (brmeade)
Cc: cisco-voip
Subject: Re: [cisco-voip] conflicting
Jason,
You set a route string on the URI Catalog such as vcs.coke.com and then just
create a SIP Route Pattern to match and point it towards the VCS SIP Trunk.
Brian
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Jason
Aarons (AM)
Sent: Thursday, February 13, 2014
---|
|
|
Thanks,
Brian Meade
From: Daniel Pagan [mailto:dpa...@fidelus.com]
Sent: Thursday, February 13, 2014 6:16 PM
To: Brian Meade (brmeade); cisco-voip@puck.nether.net
Subject: RE: SIP Stack Trace Question
Brian:
Thanks for the response.
I'd have to review traces for a non-transfer scenario but it's my
Lelio,
So the phones will still get an ITL file in a “Prepare Cluster for Rollback”
scenario but it should be a blank ITL allowing the phones to trust everything.
If you open the trust list on the phone, you should see there are no TFTP
servers defined in that scenario.
That explains the
Eric,
The SU version numbers don't exactly line up with the ES version numbers.
9.1.2.11900-12 (9.1.2 SU1) was actually built off of the 9.1.2.11006-1
Engineering Special so the 9.1.2.11021.1 ES he told you to go to will indeed be
a newer release.
Thanks,
Brian
From: cisco-voip
Lelio,
I’d suggest taking a look at
https://supportforums.cisco.com/docs/DOC-14548#Troubleshoot_CDR_Files_not_being_transfered_to_billing_server
You’ll want to make sure the files are showing up under the preserve folder.
I’d also suggest collecting CDR Repository Manager traces.
Thanks,
David,
You just need to set the No Answer Ring Duration (seconds) setting on the
individual extension to however many seconds you'd like.
Thanks,
Brian
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of David
Zhars
Sent: Monday, February 24, 2014 9:17 AM
To:
Shaihan,
Your first requirement will work with UCCX and making custom not-ready codes.
You can use Client Matter Codes in CUCM for your 2nd requirement.
Thanks,
Brian
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of
Shaihan Jaffrey
Sent: Monday, February 24, 2014 1:32
/products/3841
Thanks,
Brian
From: Shaihan Jaffrey [mailto:schae...@gmail.com]
Sent: Tuesday, February 25, 2014 9:50 AM
To: Brian Meade (brmeade)
Cc: Cisco VOIP
Subject: Re: [cisco-voip] reporting in CUCM
HI Brian,
Will CMC work for inbound calls.
Regards.
On Mon, Feb 24, 2014 at 11:44 PM, Brian Meade
AM
To: Brian Meade (brmeade)
Cc: Cisco VOIP; Shaihan Jaffrey
Subject: Re: [cisco-voip] reporting in CUCM
Brian,
Do you know if an off-net incoming call will be prompted for an FAC/CMC when
dialing a route pattern that is configured as so?
Lelio
---
Lelio Fulgenzi, B.A.
Senior Analyst, Network
Hey all,
Just wanted to send a heads up that my contact info will be changing on Friday.
You should be able to contact me at
bmead...@gmail.commailto:bmead...@gmail.com.
I have some cases with some of you that will be handed off as needed.
I will try to stay active on this mailer if possible.
28 matches
Mail list logo