I have, on occasion built a Windows AD server on my offline network to
impersonate one of the production servers for LDAP authentication, DNS,
DHCP, etc. You don't really need all of the user objects, you really just
need user objects you need to test with, so I normally create a few user
objects
From: Charles Goldsmith
[mailto:wo...@justfamily.org<mailto:wo...@justfamily.org>]
Sent: Wednesday, July 19, 2017 3:20 PM
To: Lelio Fulgenzi
Cc: voyp list, cisco-voip
(cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>)
Subject: Re: [cisco-voip] offline network - using NAT/PAT t
e...@uoguelph.ca
>
> www.uoguelph.ca/ccs
>
> Room 037, Animal Science and Nutrition Building
>
> Guelph, Ontario, N1G 2W1
>
>
>
> *From:* Charles Goldsmith [mailto:wo...@justfamily.org]
> *Sent:* Wednesday, July 19, 2017 3:20 PM
> *To:* Lelio Fulgenzi
> *Cc:* voyp lis
Fulgenzi
Cc: voyp list, cisco-voip (cisco-voip@puck.nether.net)
Subject: Re: [cisco-voip] offline network - using NAT/PAT to connect to the
outside world
Be careful of SIP connections from your offline network getting to production
devices. You don't want your Unity Connection to start repo
Be careful of SIP connections from your offline network getting to
production devices. You don't want your Unity Connection to start
reporting MWI status back to your production network or if using Single
Inbox, to sync with your Exchange.
My advice is to not let your offline network connect to a
A while back we had a good discussion about offline network upgrade
preparation. A few people mentioned using NAT/PAT in order to connect to
servers that would be too difficult to replicate in the off-line network.
I'm trying to get my head around this and thought I'd share this simplified
pla
