Vendor access
This part is for Aigna staff
Vendors see their own installation and the device reference they need to build it: device types, setup guides and models. Everything else stays with Aigna.
Go to your installationModule
Projects is switched off
Projects, the schedule, planning, the work plan and the Lab. This demo has the Projects module switched off in Organisation settings.
Batch 3 of 16 · Project PRJ-22Simulated live
1 Poly Studio G62 video codec
0 of 1 unit set up · nothing to reviewchecked just now
Setup is done by Aigna's engineers. Your installs are on the Deploy page.
Once for all 1
Through Fleet Lens, the Dublin office policyNot applied yet. One setup guide sets the shared settings on all 1; 0 can take it now, the rest when they can be reached.
14 settings to set and 0 to check; 0 left at the manufacturer's default.See every settingThe setup guide
The same on every unit
- Provider
- Poly Video Mode
- Enable SIP
- On
- SIP Server Configuration
- Specify
- Transport Protocol
- TLS
- Registrar Server
- sip.aigna.example
- Proxy Server
- sip.aigna.example
and 3 more, all in the setup guide
The units
Only what differs per unit. Each unit's build sheet has every setting worked out.Nothing is ready for you here. Keia Atlas keeps checking these units.
| Unit | Hostname | Pairs with | Provision | Install | Configure | |
|---|---|---|---|---|---|---|
| Build sheet | dub-303-vc0110.20.3.53 | dub-303-tc01 | ||||
Setup order
Optional: tick as you go, or let the checks do it1Patch into the space's AV port and power on; the device takes its reserved address.0/1
2Leave Provider at Poly Video Mode.0/1
3Set identity, time, network and SIP below.0/1
4Pair the touch controller.0/1
5Check the firmware is the standard and automatic updates are off.0/1
6Run the space's verification, including a test SIP call.0/1
Every setting
14 in the setup guide, as patternsValues marked Per unit are patterns here. Each unit's build sheet has them worked out: dub-303-vc01.
Identity4
- ProviderGeneral Settings > ProviderSet to Poly Video Mode
Why
The G62 doesn't support Google Meet.
- Device NamePer unitGeneral Settings > System Settings > Device NameSet to The hostnameWorked out on the build sheet
Why
Matches DNS, device management and monitoring.
- Room NamePer unitGeneral Settings > System Settings > Room NameSet to Room number and nameWorked out on the build sheet
Why
Shown to people at the far end.
- Admin passwordPer unitSecurity > Local AccountsSet to From the password vault, per siteWorked out on the build sheet
Why
The default is printed on the device.
SIP7
- Enable SIPSet to On
Why
How the space joins meetings while it can't use Google Meet.
- SIP Server ConfigurationSet to Specify
Why
Point at Aigna's SIP service rather than discovering one.
- Transport ProtocolSet to TLS
Why
Encrypts call signalling.
- Sign-in AddressPer unitSet to hostname@sip.aigna.exampleWorked out on the build sheet
Why
One address per space, built from the hostname.
- Registrar ServerSet to sip.aigna.example
Why
Aigna's SIP service.
- Proxy ServerSet to sip.aigna.example
Why
The same service handles calls.
- User Name and PasswordPer unitSet to From the password vault, per spaceWorked out on the build sheet
Why
Each space registers with its own account.
H.3231
- Enable IP H.323Set to Off
Why
SIP only; one call path to support.
Updates2
- Enable Automatic UpdatesGeneral Settings > Device ManagementSet to Off
Why
Version 5 drops Poly Video Mode too.
- Maintenance Hours Begin and EndGeneral Settings > Device ManagementSet to 01:00 to 04:00, local time
Why
Any restart happens when no one is in the space.