[cisco-voip] as built doc generation

Wed Mar 2 23:12:55 EST 2016

I don't think it would be that big of a deal for a customer to open up a few tcp ports for a temporary tls connection .... but maybe not for every customer/situation. Could piggy back on 8443 cause a lot of Cisco UC customers might already have that open.

IMO, I think there are plenty of scenarios is where it would work. Pie in the sky for now though :)

Thanks,

Ryan

On Mar 2, 2016, at 11:06 PM, Horton, Jamin <jamin.horton at oneneck.com<mailto:jamin.horton at oneneck.com>> wrote:

Don't ever see that happening. Can you imagine the firewall issues you would have in trying to get a web based tool initiating a connection to what are usually internal only accessible applications! Good wish list though.

Jamin Horton - Collaboration Practice Manager
CCIE Collaboration #39988
Direct:  303-734-4048
Cell:  720-401-8340
Email:  Jamin.Horton at OneNeck.com<mailto:Jamin.Horton at OneNeck.com>

<image001.png>   <image002.jpg>
<image004.png><xmpp:jamin.horton at uc.oneneck.com><image006.png><tel:3037344048><image008.png><tel:jamin.horton at uc.oneneck.com><image010.png><https://jabber-guest.uc.oneneck.com/call/jamin.horton@uc.oneneck.com><image012.png><https://oneneck.webex.com/join/jamin.horton><image014.png><tel:3033873980>

<image015.png> - This email may contain confidential and privileged material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Huff
Sent: Wednesday, March 02, 2016 9:03 PM
To: Thomas LeMay
Cc: cisco voip
Subject: Re: [cisco-voip] as built doc generation

- should be a web app, no desktop gui
- if I have to use a desktop GUI, please let me maximize the window
- I need an API, everything is better with an API (even toasters)
- I want a cloud based export; an arguable point I know, because I could manually move the local export to a cloud
- I want a regex engine that allows me to tone down the captured data based on pattern matching

Thanks,

Ryan

On Mar 2, 2016, at 10:53 PM, Thomas LeMay <thomaslemay at comcast.net<mailto:thomaslemay at comcast.net>> wrote:
Hi, Ryan,

I like Uplinx. What are some of the shortfalls?

Tom

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Huff
Sent: Wednesday, March 02, 2016 9:52 PM
To: cisco voip
Subject: [cisco-voip] as built doc generation

What is everyone using to build as built docs nowadays?

Variphy doesn't quite get everything I want to see and Uplinx is nice but has some shortfalls IMO that never seem to get addressed. Anyone have other suggestions besides Variphy and Uplinx? I'd love to whitebox something but do not have the time.

Thanks,

= Ryan =

Email: ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>

Spark: ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>

Twitter: @ryanthomashuff<http://twitter.com/ryanthomashuff>

LinkedIn: ryanthomashuff<http://linkedin.com/in/ryanthomashuff>

Web ryanthomashuff.com<http://ryanthomashuff.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160303/8221beea/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 2090 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160303/8221beea/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 894 bytes
Desc: image002.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160303/8221beea/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1973 bytes
Desc: image004.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160303/8221beea/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 2309 bytes
Desc: image006.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160303/8221beea/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 2191 bytes
Desc: image008.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160303/8221beea/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 1678 bytes
Desc: image010.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160303/8221beea/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.png
Type: image/png
Size: 1836 bytes
Desc: image012.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160303/8221beea/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image014.png
Type: image/png
Size: 1498 bytes
Desc: image014.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160303/8221beea/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image015.png
Type: image/png
Size: 1636 bytes
Desc: image015.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160303/8221beea/attachment-0007.png>