[cisco-voip] CER Configuration - Guides?

[Lelio Fulgenzi]

This reminds me of the time when my obsessiveness of things lining up got the better of me.

Editing the netware ip config file, I added zero’s to some of the octets.

Gotta admit. The config file looked pretty.

Didn’t work though.

Leading zeros were interpreted as a HEX indicator. Which, is apparently something that still happens.


Sent from my iPhone

On Feb 19, 2020, at 1:54 PM, Pawlowski, Adam <ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>> wrote:

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-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Johnson, Tim
Sent: Wednesday, February 19, 2020 1:34 PM
To: Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>>; Matt Taber (mtaber) <mtaber at cisco.com<mailto:mtaber at cisco.com>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at 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-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Matthew Loraditch
Sent: Wednesday, February 19, 2020 1:07 PM
To: Matt Taber (mtaber) <mtaber at cisco.com<mailto:mtaber at cisco.com>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at 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: MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>
<image001.png><http://www.heliontechnologies.com/>
<image002.png><https://facebook.com/heliontech>
<image003.png><https://twitter.com/heliontech>
<image004.png><https://www.linkedin.com/company/helion-technologies>
From: Matt Taber (mtaber) <mtaber at cisco.com<mailto:mtaber at cisco.com>>
Sent: Wednesday, February 19, 2020 1:01 PM
To: Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at 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 <MLoraditch at heliontechnologies.com<mailto:MLoraditch at 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: MLoraditch at heliontechnologies.com<mailto:MLoraditch at 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 at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
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/20200220/95bef5d2/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6884 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200220/95bef5d2/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 431 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200220/95bef5d2/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 561 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200220/95bef5d2/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 444 bytes
Desc: image004.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200220/95bef5d2/attachment-0003.png>