-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
- HP Community
- Poly Video Conferencing
- Collaboration & Conferencing Platforms
- Re: DNS hostnaming for UC infrastructure question?
Create an account on the HP Community to personalize your profile and ask a question
03-04-2012 03:35 PM
I am new to the Polycom world with some new infrastructure equipment consisting of a RMX, CMA, RSS, VMC, VBP-E, and VBP-ST appliances. My question is in regards to defining hostnames in DNS for some of these appliances. If I'm understanding the technology correctly, I would give my VBP-E appliance the name of video.domain.com for the outside world to use to communicate to me, while making my inside network (internal DNS) resolve video.domain.com directly to my CMA. Does anyone see any issue with that scenario?
Also, what would be a good name for my VBP-ST appliance on the outside for my external hosts to use since I'm already using video.domain.com for the E- series?
Thanks in advance.
Solved! Go to Solution.
Accepted Solutions
03-05-2012 06:38 AM
Cajun,
Generally, people will use an FQDN that resolves to their CMA and VBP ST. The ST is the registration proxy, so when you are outside the network, it serves as a gatekeeper for you.
The idea is that you set up all of your employees' CMA Desktop clients to use that FQDN, and they will be able to register to your CMA server directly when inside the network, and through your VBP ST when outside the network.
The VBP E doesn't have a counterpart inside the network, so there isn't much need to have a dual-mapped FQDN for it. It is simply used for internet calls to and from unregistered devices. So a user on the internet with no gatekeeper would call in through your VBP E, and calls out to that user would be routed automatically through your VBP E.
03-05-2012 06:38 AM
Cajun,
Generally, people will use an FQDN that resolves to their CMA and VBP ST. The ST is the registration proxy, so when you are outside the network, it serves as a gatekeeper for you.
The idea is that you set up all of your employees' CMA Desktop clients to use that FQDN, and they will be able to register to your CMA server directly when inside the network, and through your VBP ST when outside the network.
The VBP E doesn't have a counterpart inside the network, so there isn't much need to have a dual-mapped FQDN for it. It is simply used for internet calls to and from unregistered devices. So a user on the internet with no gatekeeper would call in through your VBP E, and calls out to that user would be routed automatically through your VBP E.
Didn't find what you were looking for? Ask the community