Skip to main content

Voice Device

This role is assigned to voice and telephony devices associated with Ohio State’s campus voice services. These devices are well-managed by OTDI or Wexner Medical center IT staff. Devices include wired and Wi-Fi phones and voice handsets.

Network role at a glance:

  • Wi-Fi (eduroam) and wired connectivity options available
  • Private IP addressing with network address translation (NAT) for traffic destined off-campus
  • DHCP reservations are not supported. Dynamic DNS used instead
  • All outbound traffic permitted
  • Inbound traffic limited to management tools and voice protocols from authorized voice servers only

Network Role Characteristics

Aliases for this role include

  • Voice
  • Phone
  • osu-voice

Network Traffic Permissions

No outbound traffic limitations are applied to this network role.

Inbound traffic is limited to:

  • IT management tools (e.g., Active Directory, Config Manager, Jump hosts, etc.)
  • Remote access tools (e.g., Guacamole, RDP gateway, etc.)
  • Voice protocols from authorized voice services

How to connect

Automated network assignment has been deployed for this role. On the wired network, devices are automatically assigned based on endpoint attributes presented to the network. On the Wi-Fi network, devices are automatically assigned based on a factory-installed certificate on authorized phones.

Staff simply connect the device to a wired port on OTDI’s Managed Network Service or have the device configured to connect to eduroam.

IP (Internet Protocol) Addressing

Devices placed in the Voice role are assigned private IPv4 address space dynamically assigned through DHCP. IP address reservations are not supported. Traffic destined off-campus to non-Ohio State address space will have the source IP translated to routable IPv4 public address space. However, traffic destined to Ohio State address space will retain the original private source address and not be translated. IPv6 addresses are not currently supported for this network role.

After receiving an IP address, the campus DHCP service will dynamically create a DNS A record for the endpoint in the DNS zone device.role.it.osu.edu. For example, an endpoint with hostname “Polycom_001122aabbcc” would have a DNS record of Polycom_001122aabbcc.voice.role.it.osu.edu. In the event the endpoint has no configured hostname, the mac address of the device will be used instead.

Additional Information for IT Teams

This network role is not assignable by IT administrators with access to My Devices. OTDI Networking has configured the network to automatically assign the voice network role to authorized devices, generally restricted to these manufacturers: 

  • Polycom
  • Cisco
  • Mediatrix

If a phone or handset from one of the above manufacturers is not automatically assigned the voice network role, it is possible that the device has a newer MAC address OUI that has not yet been recognized on the network. For this situation, open a ticket with the IT Service Desk to be escalated to the OTDI Networking team.