Category filter
How to configure Ascom devices with OEMConfig
OEMConfig is an application that utilizes managed configurations to configure OEM-specific policies on a device. These applications are built by their corresponding vendors and uploaded to the Google Play Store. The Ascom OEMConfig application enables enterprise configurations of Ascom Myco 3 devices to be configured from the Hexnode portal.
To configure these settings, an enterprise must integrate with a UEM solution that supports the OEMConfig feature. Hexnode UEM lets you easily add, configure and distribute Ascom OEMConfig apps to your devices.
Pre-requisites:
- Enroll the device in Android Enterprise (Device Owner or Profile Owner).
- Ascom Myco 3 devices running on Android 9.0 and above.
Approve and add OEMConfig app to app inventory:
You will have to approve and add the Ascom OEMConfig App to the app inventory by following the below-mentioned steps:
- Navigate to the Apps tab.
- Click on +Add Apps button and select Managed Google Apps from the dropdown list.
- Search for “Ascom OEMConfig” in the search bar and select the app.
- Click on Add.
- A popup shows up on the screen, which displays the permissions required by the app. Click on Approve.
- Next, the Approval Settings page shows up, where you will have to choose the method by which the new app permissions are to be handled in its upcoming updates.
- Keep Approved when app requests new permissions – Select this option to ensure that the app is automatically approved even when new permissions are requested by the app.
- Revoke app approval when this app requests new permissions – Select this option for the app to be removed from the inventory when it requests new permissions. The app remains revoked till you re-approve the app again.
- Right beside the Approval Settings tab, click on the Notifications tab where you can add email addresses to subscribe for email notifications when the approved app request for new permissions. Enter the email address and click on Add. Any number of email addresses can be added.
- Click Save.
Once the Ascom OEMConfig app has been added to the app inventory, you can install the app to the target devices from the Hexnode UEM portal.
Setup App Configurations
- Go to the Policies tab.
- Create a New Policy or select an Existing Policy.
- Select Android > App Management > App Configurations.
- Click on Configure and select +Add New Configuration button.
- Select Ascom OEMConfig from the list of approved apps.
- The list of all available configurations for the OEMConfig app is displayed. Configure the required settings from the list and click on Done.
List of all available configurations for the Ascom OEMConfig app
| Category | Sub-category | Configuration | Description |
|---|---|---|---|
| Wi-Fi – Contains restrictions which affect settings associated with the wifiextensions app. | Define option for regulatory domain | Select the regulatory domain from the options given below:
| |
| Select channels | Select the allowed channels. | ||
| Reconnect if invalid FT association | Turn on to make the device disconnect and reconnect if the cached 802.11r Fast Transition (FT) credentials are invalid for the current access point. | ||
| IP connectivity check | If enabled, the device will verify that there is IP connectivity after each roam by transmitting directed ARP requests to the default gateway as well as the primary DNS. If no ARP response is received within reasonable time, the device will disconnect from the Wi-Fi and perform a reconnect. | ||
| MAC randomization | When MAC randomization is enabled both in Ascom settings and for an individual network (under “Privacy”), the handset will use a random MAC address when connecting to this network. In all other cases, the handset’s real MAC address will be used when connecting to a Wi-Fi network. | ||
| Ascom VoIP – Contains restrictions which affect settings associated with the phonesip app | SIP Transport | Define the protocol to carry the SIP signalling traffic. Change will take effect once the device is restarted. The available options are:
|
|
| Primary SIP proxy | Define the SIP PBX by an IP address, a domain name, or an IP address with a port number. If left blank, SIP telephony will be disabled. Examples of valid formats are: pbx1.mydomain.com or 192.168.1.1:5060 | ||
| Secondary SIP proxy | Define the optional SIP PBX, if the handset fails to register with the primary SIP PBX. Specify an IP address, a domain name, or an IP address with a port number. Examples of valid formats are: pbx1.mydomain.com or 192.168.1.1:5060 | ||
| Listening port | Specify the port that the handset listens to for incoming SIP traffic. If not specified, 5070 port will be set by default. | ||
| SIP proxy ID | Define the ID to be used as the Primary/Secondary SIP message headers (optional). | ||
| SIP Register expiration | The number of seconds for register expiration. If not specified, 120 seconds will be set by default. | ||
| Endpoint ID | Set the identity to register with at the SIP PBX (use the phone number or name). | ||
| Authentication identity | Set the authentication identity to register with at the SIP PBX (authentication only). | ||
| Password | Set the password to register with at the SIP PBX. | ||
| Allow SIP over cellular | Turn on to allow SIP calls over cellular when Wi-Fi network is not available. | ||
| Prioritize cellular over Wi-Fi | Turn on to choose cellular over the Wi-Fi connection if both of them exist. | ||
| Prefer to call with | Choose the preferred call carrier for outgoing calls. If the preferred call method is unavailable at the time of the outgoing call, the other call carrier will be used. Choose “Ask for every call” if you want to receive confirmation dialog each time an outgoing call is made.
The available options are:
|
||
| Preferred codec | Defines which codec to use for speech.
Available options are:
|
||
| Disabled codecs | Select the voice codecs you want to omit as fallbacks in the codec negotiation. The available options are:
|
||
| DTMF type | Defines the signalling path to use for sending DTMF. Either in the RTP stream, as specified in RFC 2833, or with SIP signalling, using the SIP INFO method. The available options are:
|
||
| Hold type | Define the type of hold to send when the handset puts a call on hold. The selection depends on what type of hold the PBX supports. Available options are:
|
||
| Call waiting behaviour | Select the behaviour when receiving a second call during an ongoing call.
Available options are:
|
||
| Replace Call Rejected with User Busy | Turn on to send “User busy” instead of “Call rejected” cause code if an incoming call is rejected. | ||
| Dialling tone patterns | Defines which tone pattern to use when dialling. When there is a SIM card, the phone will revert to the SIM card’s country and dialling tone. Available countries are:
|
||
| Voicemail Message Server number | Specify the number to the Message Server. If specified, the handset will interrogate with the Message Server for voicemail message waiting indications (MWI) after registering with the SIP-Proxy. | ||
| Voicemail number | Specify the user’s voicemail number in the Voicemail Message Server. | ||
| Reset voicemail MWI | Turn on to reset message waiting indications (MWI) in the Message Server once the user has listened to all new messages. | ||
| Secure audio negotiation | Choose how the handset should behave when setting up an encrypted voice call. Available options are:
|
||
| Secure RTP mode | This setting controls which crypto will be offered by the handset when negotiating the setup of a secure RTP call. | ||
| Emergency call location method | Select the method to locate the handset when an emergency call is established. The available options are:
|
||
| DECT – Contains restrictions which affect settings associated with the dect app | DECT enabled | You can enable this option and configure all the configurations that are provided under this setting. | |
| Button configuration – Contains restrictions which affect settings associated with the extensions app | Top multifunction button [Long press] | Function | Defines what function is triggered by long press of this button. Available options include:
|
| Duration for long press | Defines how long the button shall be pressed until it is recognized as a long press. Available options include 0.5 sec, 1 sec, 2 sec, 3 sec. 4 sec and 5 sec. | ||
| Action of the intent | Specify an action to be performed. | ||
| Component of the intent | Specify the component name if the explicit intent should be sent. The component can be any of the following formats: package, package/component or package/.component. | ||
| Data of the intent | Specifies the data to be acted on. The data must be in a Uri format. | ||
| Top multifunction button [Single & Multi-press] | Function | Defines what function is triggered by single and multi press of this button. Available options include:
|
|
| Number of button presses | Defines how many times in one sequence the user must press the button to get a multiple press. | ||
| Action of the intent | Specify an action to be performed. | ||
| Component of the intent | Specify the component name if the explicit intent should be sent. The component can be any of the following formats: package, package/component or package/.component. | ||
| Data of the intent | Specifies the data to be acted on. The data must be in a Uri format. | ||
| Top multifunction button [Press and release] | Function | Defines what function is triggered when button is pressed and released. Available options include:
|
|
| Action of the intent on press | Specify an action to be performed when the button is pressed. | ||
| Action of the intent on release | Specify an action to be performed when the button is released. If left empty, the action of the intent on press will be used instead. | ||
| Component of the intent | Specify the component name if the explicit intent should be sent. The component can be any of the following formats: package, package/component or package/.component. | ||
| Data of the intent on press | Specify the data to be performed upon action on press. The data must be in a URI format. | ||
| Data of the intent on release | Specify the data to be performed upon action on release. The data must be in a URI format. If left empty, data of the intent on press will be used instead. | ||
| Multifunction button II [Long press] | Function | Defines what function is triggered by long press of this button. Available options include:
|
|
| Duration for long press | Defines how long the button shall be pressed until it is recognized as a long press. Available options include 0.5 sec, 1 sec, 2 sec, 3 sec. 4 sec and 5 sec. | ||
| Action of the intent | Specify an action to be performed. | ||
| Component of the intent | Specify the component name if the explicit intent should be sent. The component can be any of the following formats: package, package/component or package/.component. | ||
| Data of the intent | Specifies the data to be acted on. The data must be in a Uri format. | ||
| Multifunction button II [Single & Multi-press] | Function | Defines what function is triggered by single and multi press of this button. Available options include:
|
|
| Number of button presses | Defines how many times in one sequence the user must press the button to get a multiple press. | ||
| Action of the intent | Specify an action to be performed. | ||
| Component of the intent | Specify the component name if the explicit intent should be sent. The component can be any of the following formats: package, package/component or package/.component. | ||
| Data of the intent | Specifies the data to be acted on. The data must be in a Uri format. | ||
| Multifunction button II [Press and release] | Function | Defines what function is triggered when button is pressed and released. Available options include:
|
|
| Action of the intent on press | Specify an action to be performed when the button is pressed. | ||
| Action of the intent on release | Specify an action to be performed when the button is released. If left empty, the action of the intent on press will be used instead. | ||
| Component of the intent | Specify the component name if the explicit intent should be sent. The component can be any of the following formats: package, package/component or package/.component. | ||
| Data of the intent on press | Specify the data to be performed upon action on press. The data must be in a URI format. | ||
| Data of the intent on release | Specify the data to be performed upon action on release. The data must be in a URI format. If left empty, data of the intent on press will be used instead. | ||
| Multifunction button III [Long press] | Function | Defines what function is triggered by long press of this button. Available options include:
|
|
| Duration for long press | Defines how long the button shall be pressed until it is recognized as a long press. Available options include 0.5 sec, 1 sec, 2 sec, 3 sec. 4 sec and 5 sec. | ||
| Action of the intent | Specify an action to be performed. | ||
| Component of the intent | Specify the component name if the explicit intent should be sent. The component can be any of the following formats: package, package/component or package/.component. | ||
| Data of the intent | Specifies the data to be acted on. The data must be in a Uri format. | ||
| Multifunction button III [Single & Multi-press] | Function | Defines what function is triggered by single and multi press of this button. Available options include:
|
|
| Number of button presses | Defines how many times in one sequence the user must press the button to get a multiple press. | ||
| Action of the intent | Specify an action to be performed. | ||
| Component of the intent | Specify the component name if the explicit intent should be sent. The component can be any of the following formats: package, package/component or package/.component. | ||
| Data of the intent | Specifies the data to be acted on. The data must be in a Uri format. | ||
| Multifunction button III [Press and release] | Function | Defines what function is triggered when button is pressed and released. Available options include:
|
|
| Action of the intent on press | Specify an action to be performed when the button is pressed. | ||
| Action of the intent on release | Specify an action to be performed when the button is released. If left empty, the action of the intent on press will be used instead. | ||
| Component of the intent | Specify the component name if the explicit intent should be sent. The component can be any of the following formats: package, package/component or package/.component. | ||
| Data of the intent on press | Specify the data to be performed upon action on press. The data must be in a URI format. | ||
| Data of the intent on release | Specify the data to be performed upon action on release. The data must be in a URI format. If left empty, data of the intent on press will be used instead. | ||
| Blue parrot headset button [Long press] | Function | Defines what function is triggered by long press of this button. Available options include:
|
|
| Duration for long press | Defines how long the button shall be pressed until it is recognized as a long press. Available options include 0.5 sec, 1 sec, 2 sec, 3 sec. 4 sec and 5 sec. | ||
| Action of the intent | Specify an action to be performed. | ||
| Component of the intent | Specify the component name if the explicit intent should be sent. The component can be any of the following formats: package, package/component or package/.component. | ||
| Data of the intent | Specifies the data to be acted on. The data must be in a Uri format. | ||
| Blue parrot headset button [Single & Multi-press] | Function | Defines what function is triggered by single and multi press of this button. Available options include:
|
|
| Number of button presses | Defines how many times in one sequence the user must press the button to get a multiple press. | ||
| Action of the intent | Specify an action to be performed. | ||
| Component of the intent | Specify the component name if the explicit intent should be sent. The component can be any of the following formats: package, package/component or package/.component. | ||
| Data of the intent | Specifies the data to be acted on. The data must be in a Uri format. | ||
| Blue parrot headset button [Press and release] | Function | Defines what function is triggered when button is pressed and released. Available options include:
|
|
| Action of the intent on press | Specify an action to be performed when the button is pressed. | ||
| Action of the intent on release | Specify an action to be performed when the button is released. If left empty, the action of the intent on press will be used instead. | ||
| Component of the intent | Specify the component name if the explicit intent should be sent. The component can be any of the following formats: package, package/component or package/.component. | ||
| Data of the intent on press | Specify the data to be performed upon action on press. The data must be in a URI format. | ||
| Data of the intent on release | Specify the data to be performed upon action on release. The data must be in a URI format. If left empty, data of the intent on press will be used instead. | ||
| Man-down | Detection time | ||
| Detection angle | Select the angle of the device for man-down detection. Man-down is detected when the angle of the device is tilted below that value (default 45 degrees) within the specified time. | ||
| Package name | Specify the package name of the app that will be allowed to receive and enable/disable Man-down detection. | ||
| No-movement | Package name | Specify the package name of the app that will be allowed to receive and enable/disable No-movement detection. | |
| Detection time | Set a delay in seconds (5 – 120 sec) between the detection of no-movement and the warning phase. If left blank, 30 sec will be set by default. | ||
| Barcode Scanning – Contains restrictions which affect settings associated with the barcodescanner app | Profiles – Create profiles with the list of supported symbologies. Profile 1 is the default profile. | Profile name | Enter a name for your profile |
| Linear barcodes | Enable the available barcode symbologies in this profile. | ||
| Postal barcodes | Enable the available barcode symbologies in this profile. | ||
| Matrix (2D) barcodes | Enable the available barcode symbologies in this profile. | ||
| Advanced settings | Option to specify parameter settings following the format P[parameter number]=[desired value], e.g. P7=1. Entries are separated with a “,”. When conflicting, advanced settings will override other settings. | ||
| App configurations – Configure the scanner for specific apps. | Package or Activity name | Entitle the app that will use this configuration. Use the package name, optionally joined by a ‘/’ and the activity class name. Use a wildcard ‘*’ in the end to match multiple packages or classes. | |
| Profile | Assign the scanning profile to this app (name or number). If empty, Profile 1 is used. | ||
| LED | Set the default setting for the LED light beam. LED can also be temporarily turned on/off directly on the viewfinder screen. | ||
| Continous scanning | Choose a timeout interval between scans. This setting controls the time the scanner waits before it decodes another barcode. | ||
| Viewfinder | When turned on, the scanning area is shown on the handset screen. | ||
| Start scanning in viewfinder automatically | When turned on, scanning starts immediately in the opened viewfinder. If disabled, scanning is triggered manually by pressing the scan button. | ||
| Picklist mode | Choose the aiming pattern to be shown on the viewfinder screen. Only those barcodes that are placed in the center of the selected pattern will be scanned.
You can choose the Picklist mode from the options given below:
|
||
| Keystroke output | Enable output of data in the form of simulated key presses. | ||
| Send Enter key | Enable to automatically send Enter key when a barcode has been successfully scanned. | ||
| Action key character | Set a special character to trigger action key if found embedded in barcode.
The available options are:
|
||
| Intent output | Enable intent output for this app. | ||
| Intent target | The target component type of an intent sent for this app. You can choose the intent target from the options given below:
|
||
| Intent identification prefix | Prepend an optional package name to intent identification strings which start with a dot. Applies to action, category and extras identifiers. | ||
| Intent action | The intent action to use for the output data. | ||
| Intent category | The optional intent category to use for the output data. | ||
| Scanned string intent extra | The intent extra key that identifies the scanned data when sent as a string. | ||
| Scanned data intent extra | The intent extra key that identifies the scanned data when sent as a list of byte arrays. | ||
| Source intent extra | The intent extra key that identifies the data source for the barcode data. This key will always have the value of ‘scanner’. If left empty, the intent extra will not be included in the intent. | ||
| Type intent extra | The intent extra key that identifies the type of the scanned barcode. If left empty, the intent extra will not be included in the intent. The value for the type intent extra shall be LABEL-TYPE-, e.g. LABEL-TYPE-EAN13. | ||
| Data formatting | Specify a rule according to which the scanned data will be formatted before it is sent to the app (applies to intent data and keystroke output). Use the Sed language to define the rule. Leave empty for no formatting. | ||
| Location services – Contains restrictions which affect settings associated with the locationmanager app | Base station positioning | When turned on, the handset will always roam to the DECT base station with the best signal strength. Knowing the nearest base station allows for a rough positioning of the handset. Note that standby time will be shorter when setting is enabled. | |
| Beacon positioning | If enabled, third-party applications will be allowed to access DECT location of the handset received from 9dLD location devices (DECT beacons). The four latest detected DECT location can be provided to the application. Please note that the standby time will be shorter when this setting is enabled. | ||
| DECT RSSI threshold | Specify the lowest allowed RSSI threshold value sent by the location beacon for which a DECT location position will be accepted by the handset. | ||
| Wi-Fi scanning interval – | Set the number of seconds (minimum 5 and maximum 300) to wait between each scan. If left blank, the scanning interval will be set to 10 seconds by default. | ||
| Wi-Fi location scanning | Turn on to perform Wi-Fi location scans within a specified scanning interval. The scan result will be available to all installed third-party applications. | ||
| Wi-Fi location services | When turned on, third-party applications will be allowed to access Wi-Fi access point info via the proprietary location API. This setting also controls if Wi-Fi events are written to the event log or not. | ||
| Zone filter mask | Zone filter mask [0000-FFFF (hexadecimal), default: 0000] | ||
| Zone filter | Zone filter [0000-FFFF (hexadecimal), default: 0000] | ||
| Zone range | If this parameter is Off, all detected IR beacons are considered as zones. If this parameter is On, the administrator may determine which IR beacons that are to be considered as zones. | ||
| Zone update time (minutes) | A parameter to configure the regular current zone transmission interval. Value in minutes. | ||
| Out of zone time (seconds) | A parameter to configure the timeout before considering the Zone to be left. Value in seconds. | ||
| Enable zone locations | Enabling zone locations feature. | ||
| IR short range | Short range mode reduces the impact that sunshine or incandescent light has on the IR coverage area, and is typically used when large glass areas are present at a site. If short range mode is not used at these sites, the coverage area will differ between day and night. | ||
| IR location services | If enabled, third-party applications will be allowed to access the IR location of the handset. The four latest detected IR Locators can be provided to the application. | ||
| Display setup– Contains restrictions which affect settings associated with the launcher2 app | Quick Settings tiles | Select the tiles that will appear in the Quick Settings menu of the notification drawer. Note that you need to enable the “Lock Quick Settings menu” parameter to see changes. You can choose from the following ones:
|
|
| Lock Quick Settings menu | When turned off, you are allowed to change the tiles of the Quick Settings menu. When turned on, the selected tiles become accessible but you cannot rearrange them in the Quick Settings menu. | ||
| Custom display text | Enter a custom lock and charging screen text or number. | ||
| Display text | Turn on to enter a custom text or number you want to be displayed when the handset is locked or placed in charger. | ||
| Telephony identifiers | Turn on to display telephony identifiers when the handset is locked or placed in charger. | ||
| Show Google Search Bar | When turned on, Google Search Bar is shown on the Home screen. Turn off to remove this widget from the Home screen. | ||
| Lock Home screen layout | Enable to prevent the widgets and shortcuts from being removed or repositioned. You will no longer be able to add any apps to the home screen | ||
| Advanced settings – Contains restrictions which affect settings associated with the settings app | Ascom settings password | Set the password required to access Ascom settings (4–32 characters). | |
| Screen timeout | Select how long the screen should stay on when you do not interact with the handset. Note that increasing the screen timeout duration will lead to more battery usage and quick battery drain. | ||
| Password protect Ascom settings | Turn on to ask for a password to access Ascom settings. | ||
| Adjust volume on lock screen | When turned on, you can adjust volume when the screen is locked. Turn off if you want to allow volume change only in unlocked state. | ||
| Minimum volume | Specifies the minimum volume level for ringtones and notifications. If a user tries to decrease volume below the specified level, the device will reset the volume to what is specified here. |
||
| NTP server addresses | Specify the NTP time server address(es) separated by comma (192.168.1.1, 192.168.1.2, backup.company.com) to allow the handset’s date and time to be automatically synchronized with them. Note that “Use network-provided time” must be first enabled in Android settings. | ||
| Troubleshooting – Contains restrictions which affect settings associated with the devicelogger app | Severity levels | Select the severity level(s) for the logs you wish to be included in the Syslog messages to the server. The settings include:
|
|
| Transport protocol | Select which transport-layer protocol (TLS or UDP) to use for sending Syslog messages. | ||
| Syslog server | Specify the network socket to connect to the remote syslog server in a host[:port] format (Example: 192.168.100.2:4321). Host can be either IP address or a domain name. TCP or UDP port is optional | ||
| Syslog | Turn on to allow devices to send messages about their state to a server. | ||
| Network logging hostname | Specify the IP address or hostname that is allowed to connect to the device and receive network traffic. | ||
| Network packet logging | Choose the network packet logging mode: Off – to disable the network traffic logging. Local – to start tcpdump logging traffic on a network. If disabled later, the stored files should be removed manually. Remote – to enable remote logging. Switch to this mode to allow Wireshark sniffer to connect to the device to get network traffic from it. | ||
| Additional Wi-Fi trace | When turned on, additional debug logs will be produced by the Wi-Fi stack. | ||
| Additional SIP trace | If enabled, additional debug logs are produced by the SIP stack. | ||
| Save logs | Set the time-interval to save logs from the following options:
|
||
| System update – Contains restrictions which affect settings associated with the softwareupdate app | Scheduled software update | Turn on to schedule when the handset will install new software. If there are new updates available at this time, the handset will try to download and install them right away. The handset will also try to update software right away if neither date nor time is specified. Note that the battery level shall be at least 20% of charge. | |
| Require the use of charger | Turn on to require the handset to be placed in charger in order to perform a scheduled update. | ||
| Set date | Specify the date when the software shall be installed. Use one of the following formats: YYYY-MM-DD or YYYY/MM/DD. Note that if both time and date left empty, then software update will start immediately. | ||
| Set time | Specify the time when the software shall be installed. Use one of the following formats: hh:mm AM/PM or HH:mm. Note that if both time and date left empty, then software update will start immediately. | ||
| Software update interval | Select how often the handset should retry update the software if it, for some reason, cannot be updated right away. | ||
| Software policy URL | Enter the URL to the policy where available software updates will be downloaded from. Valid URL protocols are http and https. If no protocol is specified, https will be set by default. | ||
| Update software over cellular | Turn on to allow software update over cellular when Wi-Fi network is not available | ||
| Supervisor – Contains restrictions which affect settings associated with the supervisor app | Battery optimization whitelist | Specify package name(s) of the app(s) that will be exempt from battery optimization restrictions. By default, all apps use battery optimization feature. If you have several packages, they shall be separated by commas. Note that you must specify the exact package name(s) of the app(s) when using this setting. | |
| Battery | Standby intelligent power saving | Enable to turn on standby intelligent power saving. Note that this function is not present on devices running Android 10 or later. | |
| Mobile network APN | APN configuration | Default | Enable/Disable APN configuration in the device. |
| Name | A name for the APN settings to identify among other saved APN settings. | ||
| APN | The access point name for the network connection. | ||
| Proxy | Specify the IP or domain address of the HTTP proxy server to mask web traffic over this connection. | ||
| Port | Specify the port number of the APN server to be configured. | ||
| Username | The username used for authenticating the connection. | ||
| Password | The password associated with the username. | ||
| Server | The Multimedia Messaging Service Center (MMSC) address that looks like a web URL. It is used for sending and receiving MMS messages. | ||
| MMS proxy | The HTTP proxy address for connecting to the MMSC server. | ||
| MMS port | The port number for the MMS proxy endpoint connecting to the MMSC server. | ||
| MCC | MCC is a three-digit code that is used to identify a country or a group of networks that share the same MCC. MCC is used with MNC (Mobile Network Code) to uniquely identify a network. This field is mandatory. | ||
| MNC | Mobile Network Code (MNC) is a two or three-digit code that is assigned to a network. Use it with MCC to uniquely identify the home network. This field is mandatory. | ||
| Authentication type | Select an authentication protocol for your connection. The available options are:
|
||
| APN type | Define the APN type to be configured. | ||
| APN protocol | |||
| Select the protocol to be used: IPV4, IPV6 or IPV4V6. | |||
| APN roaming protocol | From IPV4, IPV6 and IPV4/V6, select an internet protocol to use while the user is outside their home network. | ||
| Carrier enabled | Enable/Disable carrier. | ||
| Bearer | MVNO type | Mobile Virtual Network Operator – a reseller carrier that uses one of the larger (AT&T, Sprint, T-Mobile) carriers. Available options are:
|
|
| MVNO match data | Used to enter provider-specific data based on the selected mobile virtual network operator. |
Note:
The OEM specific settings explained in this document are based on the configurations set by the respective OEM vendors, which may vary frequently. Since Hexnode is not solely responsible for setting up these configurations, you may find slight variations in the settings displayed on the portal from this document.
Associating policy
- Associate the policy with the target devices by navigating to the Policy Targets tab.
- Select the required Devices/Device Groups/Users/User Groups/Domains with which the policy is to be associated.
- Click on Save.
The applied configurations will be associated with the selected devices.
Need more help?
