Oh one more interesting thing The data import/export for switches, ports, etc are going to be the real lifesaver in maintaining your data. I’ve found that the import will sometimes allow different character lengths, or will provide more useful information about something (such as how it refers to an interface on a switch, which may not be how you’d expect for TE versus GE, FA, etc).
I think they posted a bug for it but at some point someone here imported a switch in this valid addressing format: 192.168.1 . See Wikipedia’s comment on that: When fewer than four numbers are specified in the address in dotted notation, the last value is treated as an integer of as many bytes as are required to fill out the address to four octets. Thus, the address 127.65530 is equivalent to 127.0.255.250. CER happily imports this and the tracking engine expands this forever cursing you with it appearing in the things-not-tracked email until you spot it later in tables. Maybe it at least shows up in the UI now. Adam From: cisco-voip <cisco-voip-boun...@puck.nether.net> On Behalf Of Johnson, Tim Sent: Wednesday, February 19, 2020 1:34 PM To: Matthew Loraditch <mloradi...@heliontechnologies.com>; Matt Taber (mtaber) <mta...@cisco.com> Cc: cisco-voip@puck.nether.net Subject: Re: [cisco-voip] CER Configuration - Guides? I just worked my way through the official configuration guide the other day. It was a challenge, but I got it pieced together. The call flow diagram on this TAC document would have been super helpful to have! From: cisco-voip <cisco-voip-boun...@puck.nether.net> On Behalf Of Matthew Loraditch Sent: Wednesday, February 19, 2020 1:07 PM To: Matt Taber (mtaber) <mta...@cisco.com> Cc: cisco-voip@puck.nether.net Subject: Re: [cisco-voip] CER Configuration - Guides? Thank you, that is super useful Matthew Loraditch Sr. Network Engineer p: 443.541.1518<tel:443.541.1518> w: www.heliontechnologies.com<http://www.heliontechnologies.com/> | e: mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com> [Helion Technologies]<http://www.heliontechnologies.com/> [Facebook]<https://facebook.com/heliontech> [Twitter]<https://twitter.com/heliontech> [LinkedIn]<https://www.linkedin.com/company/helion-technologies> From: Matt Taber (mtaber) <mta...@cisco.com<mailto:mta...@cisco.com>> Sent: Wednesday, February 19, 2020 1:01 PM To: Matthew Loraditch <mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>> Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] CER Configuration - Guides? [EXTERNAL] This guide is a bit more streamlined, with configuration screenshots taken from an example deployment: https://www.cisco.com/c/en/us/support/docs/unified-communications/emergency-responder/211453-Cisco-Emergency-Responder-Integration-wi.html -Matt On Feb 19, 2020, at 12:53 PM, Matthew Loraditch <mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>> wrote: Any good guides or blogs that go through this in a more real world way than the documentation? I haven’t found anything super helpful yet. Matthew Loraditch Sr. Network Engineer p: 443.541.1518<tel:443.541.1518> w: www.heliontechnologies.com<http://www.heliontechnologies.com/> | e: mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com> <image890010.png><http://www.heliontechnologies.com/> <image285343.png><https://facebook.com/heliontech> <image753523.png><https://twitter.com/heliontech> <image362000.png><https://www.linkedin.com/company/helion-technologies> _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
