Great news! Thanks for sharing.
Sent from my iPhone
On May 28, 2020, at 5:27 PM, Mark H. Turpin wrote:
CAUTION: This email originated from outside of the University of Guelph. Do not
click links or open attachments unless you recognize the sender and know the
content is safe. If in doubt,
Quick update from the 911 geek on the list ICYMI -
https://help.webex.com/en-us/av6oo3/RedSky-Emergency-911-Service-for-Webex-Calling
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
I like that use case. It makes sense to me if you were doing exports often
enough. I don't think most customers are however, exporting their own
configurations. But I still like the use case nonetheless.
On Thu, May 28, 2020 at 3:02 PM Matthew Loraditch <
mloradi...@heliontechnologies.com>
Fun fact, you can name a sip trunk and an mgcp gateway the same name and it
will break mgcp configuration, as the internal lookup for the device config
file looks for a config file for the trunk first, will not find it, and
then return an error.
On Thu, May 28, 2020 at 2:50 PM Johnson, Tim
We name most things by the site name or similar. If you were looking a device
export or something it can get mighty confusing IMO if you just saw several
columns all saying SITENAME as the values. Easier to mix up data when you have
non unique values.
Matthew Loraditch
Sr. Network Engineer
That bothers me too. I think the only option where that makes sense is for RGs
and RLs because they cannot share the same name.
From: cisco-voip On Behalf Of Anthony
Holloway
Sent: Thursday, May 28, 2020 3:42 PM
To: Matthew Loraditch
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip]
Can anyone give a use case where appending or prepending the object type
identifier on the name is helpful? E.g., why put -css on a css at all?
On Thu, May 28, 2020 at 2:19 PM Matthew Loraditch <
mloradi...@heliontechnologies.com> wrote:
>
>1. PT-, CSS-, etc
>2. FQDN
>3. My setups
1. PT-, CSS-, etc
2. FQDN
3. My setups are always distributed. Certainly could have central if it’s
one site.
4. Usually always
5. SIP, SIP, SIP
6. Unfortunately no, drives my OCD crazy. I hate lower/mixed case naming of
devices with a passion. I’m also born of a Windows world
I see it, and I see that it's not 100% clear. However, if you listen to the
presentation recording for this section, Brandon does mention the lengthy
process for multi-step upgrades, and how PCD solves that, though, either
are valid.
On Thu, May 28, 2020 at 2:07 PM Matthew Loraditch <
Slide 92
Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: mloradi...@heliontechnologies.com
From: Anthony Holloway
Sent: Thursday, May 28, 2020 2:51 PM
To: Matthew Loraditch
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Migration from
Sure I can fire this up
1. part_ , like part_local, part_ld, part_ld_privacy , etc.
2. FQDN, but, make sure your DNS/NTP/etc works with resiliency.
3. Depends on if you’re distributed, using hardware conf, transcoder cause
you have some people on some sort of twizzler based connection
Jabber used to have a feature on iPhone where it would auto-dial a number when
Jabber was brought to foreground and phone placed against ear.
We sent it to our voice activated dialer. Worked like a charm. Miss that
feature.
Sent from my iPhone
On May 28, 2020, at 2:40 PM, James B wrote:
Correct. Today, it's basically the standard to involve DNS in your
deployment. However, there's always exceptions to the rule.
On Thu, May 28, 2020 at 1:35 PM Hunter Fuller wrote:
> I swear, really, that I'm not trying to stir anything up here.
>
> But is there any reason to turn up a new
Interesting thing is this preso (which is not official for TAC Purposes) says I
can go from 8.6 to 12.5 directly in OS admin, but docs say use PCD. Not going
to try it, but nevertheless curious.
Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e:
The argument used to be that using an FQDN made you dependent on DNS. Then, someone realized that all the other stuff customers care about relies on DNS, so maybe that was OK. And certificates of course. FQDN all the way! From: Hunter FullerSent: 28 May 2020 19:35To: James BCc: Anthony
lol, not exactly off list there buddy. ;)
On Thu, May 28, 2020 at 1:32 PM Lelio Fulgenzi wrote:
> *Replying off-list…*
>
>
>
> Yes, I took down our telephone system once by inserting a blank
> translation in the none partition.
>
>
>
> What did I know? I was young and naïve.
>
>
>
> Of
Replying off-list…
Yes, I took down our telephone system once by inserting a blank translation in
the none partition.
What did I know? I was young and naïve.
Of course, with CCM v2 or v3, anything was possible.
From: cisco-voip On Behalf Of Lelio
Fulgenzi
Sent: Thursday, May 28, 2020
Don’t forget:
7: @ with route filters or not.
From: cisco-voip On Behalf Of James B
Sent: Thursday, May 28, 2020 2:28 PM
To: Anthony Holloway ; Matthew Loraditch
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Migration from CUCM/UCXN/UCCX 8.5 to 12.5
CAUTION: This email
I call blank translation patterns.
From: cisco-voip On Behalf Of Anthony
Holloway
Sent: Thursday, May 28, 2020 2:02 PM
To: Kent Roberts
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Migration from CUCM/UCXN/UCCX 8.5 to 12.5
CAUTION: This email originated from outside of the
Another thing, CUCM 12.5 specific, Cisco wants all of us to run through the
Collaboration Sizing Tool every time we upgrade to 12.5 now.
See slide 13
https://www.ciscolive.com/c/dam/r/ciscolive/us/docs/2019/pdf/BRKUCC-2011.pdf
On Thu, May 28, 2020 at 1:08 PM Anthony Holloway <
I was thinking of the community configuration approach Anthony suggested and was thinking of the debates we’d have if we did that: Do you use “_PT”, “PT_”, or just the site name? Same for “CSS”, “LOC”, and the ever-debated “RGN” or “REG”?.FQDN or IP addresses?Do all the media resources go into a
Keep in mind that PCD network migrations, while awesome for CUCM, do not
work for other products.
Typically with a project like this, you'll likely have a different approach
for each app, and not a one size fits all solution.
With the app upgrades, you will also have to change OVA sizes (or want
Free Beer to all participants at the next in person Cisco Live!
Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: mloradi...@heliontechnologies.com
From: Anthony Holloway
Sent: Thursday, May 28, 2020 2:02 PM
To: Kent Roberts
Cc: Matthew Loraditch ;
Ha, maybe for a larger amount of servers, but the amount of time to read,
interpret/document, have meetings with the customer to go over, and finally
program it all again, would be astronomically longer. There are I think 8
different sites/flows in the system. That’s all active work. Most of
Or turn it into the first cisco-voip community project, and we all jump in
and help? I call translation patterns!
On Thu, May 28, 2020 at 12:57 PM Kent Roberts wrote:
>
> Might be less work to just start over…..
>
>
> On May 28, 2020, at 10:25 AM, Matthew Loraditch <
>
Might be less work to just start over…..
> On May 28, 2020, at 10:25 AM, Matthew Loraditch
> wrote:
>
> Here’s a fun one. We have taken over support of these ancient servers hosted
> on Esxi 4.1 on UCS-C200-M2s!
>
> Exact Versions are:
> 8.5 SU2 for CUCM/UCXN
> 8.5 FCS for UCCX
>
> Each
Here's a fun one. We have taken over support of these ancient servers hosted on
Esxi 4.1 on UCS-C200-M2s!
Exact Versions are:
8.5 SU2 for CUCM/UCXN
8.5 FCS for UCCX
Each is a pair of servers.
Have new M5s and flex licensing... need to get to 12.5.. 8.5 docs are dead for
CUCM/UCXN and 8 and
27 matches
Mail list logo
