Frequently Asked Questions

Avalanche

How do I Upgrade My Licenses?
When upgrading any Wavelink software to the newer version, a newer version of the license is required.

This is a process we refer to as "license exchange/license upgrade" but can only be performed based on your licenses currently being under a maintenance contract.

A license exchange can be performed by contacting us at customerservice@wavelink.com or calling our support line: +1 888-699-WAVE(9283) ext 2.

Please have your Sales Order number for your licenses ready.

Additional Information:
If you have numerous licenses, please feel free to contact us at support and we can assist you in a software license consolidation.

Is There a Way to Manually Activate Licenses?
Yes. Follow these steps:

  1. Go to a computer that you can get an internet connection.
  2. Go to www.wavelink.com/activate
  3. To get the Hardware Node Lock go to AMC 5.x
  4. Go to Help
  5. Then to About Avalanche
  6. Type in the Node Lock in the activation box
  7. Type in the License Key number
  8. Save the file where ever you would like.
  9. In AMC go to Tools, Manage Licenses.
  10. Click on Add a License
  11. Click on Import a License
  12. Locate the license file where you saved it and import.

I registered for the wrong version of your product. How can I fix this?
We will exchange your order and you may then go in and register for the correct platform version.
If I upgrade may I use my current licenses?
No. If you have current maintenance, we can exchange your licenses for you. You may then register your licenses for the upgraded version.
Only One Device Showing on the Console at One Time
If the Avalanche enabler is sent down to the devices through an image or a copy format (when there are multiple devices) then there is known to be issues with the console only showing one device at one time. When a second device connects the first one is cleared and the second takes its place. The issue with this is most likely that the devices are showing the same GUID as the enabler was imaged to the guns and not individually installed. The GUID is an identification for the enabler and if the package is imaged to the devices they will copy the _local.prf file to the guns with the same GUID for each gun as the _local.prf is the file that contains this identification number.

To fix this you can manually Active sync the devices and delete the _local.prf file from the application/avalanche/config from the device and contact the console to create a new GUID. This should resolve this issue. If not please contact Wavelink support for further instruction.

MU Needs Packages
When deploying a package the error "Agent disconnect: MU needs packages" occurs.

This error occurs when two of the same package are being deployed to a device. Any kind of duplicate package can cause this, even ones with different settings. To resolve this either disable one of the packages, or use selection criteria so that both will not be going to the same devices.

Motorola MC 9090 Newer Enablers Showing Unlicensed
Problem: AMC 4.1.1 or 4.1.2 mobile devices running 4.02-00 and higher enablers showing unlicensed, even though there are remaining licenses.

Solution: To run 4.02 enablers on previous version of AMC you must have a base license for the device as well as a current maintenance license entered for your AMC console. If you are unsure what a maintenance license is please contact one of our support representatives at 1-888-697-WAVE.

How do I enable and use the integrated log on with in AMC?
To enable the integrated log on you must first establish a connection with your console. Once you logged in you will need to go to Tools\User Management. From here you will enable the integrated log on.

Once you have enabled this feature, select ok then log off of the console. You can now enter your log on information and domain to obtain access to the console. Upon your first successful log on to the console you will have minimal access to the console. Your AMC admin will now be able to give that user certain permissions when accessing the console.

Is there a software package so that I can configure my Enablers remotely via AMC?
Yes, the Enabler Configuration Utility. Avalanche MC product download
How do I configure the Enabler to lockdown the device?
  1. Launch the Avalanche Enabler configuration utility.
  2. Click the Enabler Settings icon button. The Avalanche Update Settings dialog box appears.
  3. In the Avalanche Update Settings dialog box, select the User Interaction tab.
  4. Enable the Secure Settings with Password checkbox.
  5. Configure the settings password.
  6. Enable the Prompt for Password When Exiting Monitor checkbox.
  7. Configure the exit password.
  8. Select the Startup/Shutdown tab.
  9. Select the Monitor and Launch Update Utility option.
  10. Enable the Hide Start Menu (System Taskbar) checkbox.
  11. Select the Stop Monitoring option.
  12. Select the Shortcuts tab.
  13. Use the Shortcuts tab to configure Avalanche Enabler shortcuts to any applications on the mobile device that users will need.
  14. Click OK. The Avalanche Update Settings dialog box closes and the new configuration is saved to the host system.
  15. Download the new Avalanche Enabler configuration to the mobile device.

Source: Avalanche MC User Guide, Appendix A: Common Configuration Tasks

Within package builder can I make a call to use the WCELoad utility with in the OS?
You can use the WCEload utility and its switches. As an example, you can create a silent install of a cab file that is to be deployed to your device. Enter you command arguments with in the start up command. For further information regarding the WCELoad utility and its features, please refer to microsoft.com

\windows\wceload.exe /noui "\Your\Path"

Does Package Builder ship with any examples of how to build and deploy my own applications using AMC?
Answer: Yes. see the " Examples" directory of Package Builder
How do I deploy and install a custom CAB file using Package Builder and AMC?
  1. Create your package in Package Builder, and include the CAB file(s) as the files to install on the device.
  2. In Package Builder, make your Package Type a "Support" package.
  3. Select the option to "Include Post Install Script" as part of the package.
  4. In the Post Install Script, include an [Execute] heading with the property "CabFiles = Yes"
How do I deploy files to non-default, (i.e. APPS) directories?
  1. Create your package in Package Builder, and include the files to install on the device.
  2. On the file entry line in the Package Files tab, click on the "Install Drive" column, and change it to "C"
  3. Click on the Install Path column and insert the complete path from root to install the file. (For example, "\Windows\Program Files\MyApplication").
Can I use Package Builder to create custom properties for my device / enabler (using a post-install script)?
Yes
Avalanche 3.x and Prior – End Of Life Notice - DEADLINE EXTENDED
We are extending the End of Life Notice for Avalanche 3.x and Prior until March 31, 2010. At that time, no licenses or maintenance sales will be accepted. Please review the information below and if you have further questions, please contact your Wavelink Rep. Please carefully review the information below and ensure that your customers are aware of these changes as well as your organization.

  • Effective immediately, Wavelink will no longer release enhancements for those Avalanche versions.
  • Effective March 31, 2010, Wavelink will no longer sell or renew standard annual maintenance for those Avalanche versions. For customers needing extra time to make the transition, premium maintenance may be available at an additional cost. Contact Wavelink Sales for availability and pricing.
  • Effective November 1, 2010, Wavelink will end all standard support for those Avalanche versions.

We encourage your affected customers to make plans to upgrade to Avalanche SE or Avalanche MC as soon as possible to avoid any problems with this end-of-life schedule.

For those customers needing assistance upgrading or with training for the newest Avalanche platform, Wavelink offers Certified Professional Services. Wavelink has multiple solutions to assist customers migrating from older versions of Avalanche to the latest version. Services include onsite or remote upgrade and migration assistance, and onsite or remote product training.

For more information on the Avalanche end-of-life schedule, or to request Wavelink’s Certified Professional Services, please contact your Wavelink sales representative or e-mail sales@wavelink.com.

Listing of Wavelink Product Ports including Avalanche, SecurePlus (formerly CE Secure),
Remote Control, ConnectPro (formerly TermProxy) and Studio Enterprise Server Ports
The following table provides a list of the ports that the Mobile Device dServer uses.
5432 Avalanche MC JDBC (Internal Use, facilitates communication between the Enterprise Server and PostgreSQL database.)
TCP
7221 Avalanche MC License Server TCP
7226 InfoRail Service IR to IR router port TCP
7225 InfoRail Service TCP
5002 AMC Wavelink Authentication Service TCP
1899 Remote Control Communication TCP
5001 SecurePlus (formerly CE Secure) Authentication Service TCP
1777 Mobile Device dServer MU Protocol Service TCP/UDP
358 Wavelink Avalanche Mobility Center

Infrastructure dServer Ports
7200 Infrastructure dServer RPC TCP
7208 Infrastructure RMI TCP
7210 Infrastructure dServer Alert Service RPC TCP
7211 Infrastructure dServer Service Manager TCP
7212 Infrastructure dServer SNMP Server UDP
7213 Infrastructure dServer SNMP Alert Service UDP
7214 Infrastructure dServer SNMP Statistics Service UDP
7215 Infrastructure dServer SNMP Server Security UDP
7216 Infrastructure dServer System Interface TCP
7217 Infrastructure dServer Web Server (Tomcat) TCP
7218 Infrastructure dServer Web Server (Apache) TCP
7219 Infrastructure dServer UDP Proxy (Internal use) UDP
161 SNMP TCP/UDP
80 HTTP TCP
69 Trivial File Transfer Protocol UDP
23 Telnet TCP/UDP
The following is a list of TCP/UDP socket ports used by the Wavelink Avalanche software:
TNClient License Server
Broadcast UDP 1820
Receive License on UDP port 2001

Avalanche Agent/Enabler communication
UDP/TCP port 1777 - Avalanche console listening port.
UDP/TCP port 1778 - Clients (enabler) listening port.
UDP/TCP port 1779 - Console server port (Agent listening for communication from the Avalanche Manager console)

Host connections
Default port = 23
ConnectPro (Formerly TemProxy)
4428 - Default web server port
4430 - Default proxy service proxy1 for listening

StudioCOM
Default listening ports can be 2001 or 1000 (should be at least 1000 or higher to avoid system conflicts). The clients will create a random port on their side to communicate with. This is usually in the 1400-1500 range. Auto discovery is 900 and 901

Studio Java
UDP port 905 for Auto discover on the server
UDP port 903 for Auto discover on the client
port 1000 and up for application listening port
(should be open for editing as needed)

ConnectPro (formerly TermProxy)

If I upgrade may I use my current licenses?
No. If you have current maintenance, we can exchange your licenses for you. You may then register your licenses for the upgraded version.
I registered for the wrong version of your product. How can I fix this?
We will go ahead and exchange your order and you may then go in and register for the correct platform version.
Listing of Wavelink Product Ports including Avalanche, SecurePlus (formerly CE Secure),
Remote Control, ConnectPro (formerly TermProxy) and Studio Enterprise Server Ports
The following table provides a list of the ports that the Mobile Device dServer uses.
5432 Avalanche MC JDBC (Internal Use, facilitates communication between the Enterprise Server and PostgreSQL database.)
TCP
7221 Avalanche MC License Server TCP
7226 InfoRail Service IR to IR router port TCP
7225 InfoRail Service TCP
5002 AMC Wavelink Authentication Service TCP
1899 Remote Control Communication TCP
5001 SecurePlus (formerly CE Secure) Authentication Service TCP
1777 Mobile Device dServer MU Protocol Service TCP/UDP
358 Wavelink Avalanche Mobility Center

Infrastructure dServer Ports
7200 Infrastructure dServer RPC TCP
7208 Infrastructure RMI TCP
7210 Infrastructure dServer Alert Service RPC TCP
7211 Infrastructure dServer Service Manager TCP
7212 Infrastructure dServer SNMP Server UDP
7213 Infrastructure dServer SNMP Alert Service UDP
7214 Infrastructure dServer SNMP Statistics Service UDP
7215 Infrastructure dServer SNMP Server Security UDP
7216 Infrastructure dServer System Interface TCP
7217 Infrastructure dServer Web Server (Tomcat) TCP
7218 Infrastructure dServer Web Server (Apache) TCP
7219 Infrastructure dServer UDP Proxy (Internal use) UDP
161 SNMP TCP/UDP
80 HTTP TCP
69 Trivial File Transfer Protocol UDP
23 Telnet TCP/UDP
The following is a list of TCP/UDP socket ports used by the Wavelink Avalanche software:
TNClient License Server
Broadcast UDP 1820
Receive License on UDP port 2001

Avalanche Agent/Enabler communication
UDP/TCP port 1777 - Avalanche console listening port.
UDP/TCP port 1778 - Clients (enabler) listening port.
UDP/TCP port 1779 - Console server port (Agent listening for communication from the Avalanche Manager console)

Host connections
Default port = 23
ConnectPro (Formerly TemProxy)
4428 - Default web server port
4430 - Default proxy service proxy1 for listening

StudioCOM
Default listening ports can be 2001 or 1000 (should be at least 1000 or higher to avoid system conflicts). The clients will create a random port on their side to communicate with. This is usually in the 1400-1500 range. Auto discovery is 900 and 901

Studio Java
UDP port 905 for Auto discover on the server
UDP port 903 for Auto discover on the client
port 1000 and up for application listening port
(should be open for editing as needed)
With in Term Proxy, what is a re-connect string and how can I tell which one to use?
When a client re-connects after having been idle or having otherwise terminated the session, the proxy server sends the client session information and the client continues the session as if it had never been terminated. Block-mode emulations such as 5250 and 3270, require a reconnect string. Character-mode emulation such as VT100 and VT220, do not require a reconnect string.

To best determine which re-connect string you should use, you should pick a function that is present on each screen of your host application.. To acquire the Hex values you can take a simple packet trace to obtain your hex values for the desire values.

When you enter a [string] value, you must place a % character before each hex code value. Each hex code character is represented by a two-digit number.

Example:
To send an F24 upon re-connect (EBCDIC BC before FFEF):
%00%0D%12%A0%00%00%04%00%00%03%01%01%BC%FF%EF

Terminal Emulation

How do I Upgrade My Licenses?
When upgrading any Wavelink software to the newer version, a newer version of the license is required.

This is a process we refer to as "license exchange/license upgrade" but can only be performed based on your licenses currently being under a maintenance contract.

A license exchange can be performed by contacting us at customerservice@wavelink.com or calling our support line: +1 888-699-WAVE(9283) ext 2.

Please have your Sales Order number for your licenses ready.

Additional Information:
If you have numerous licenses, please feel free to contact us at support and we can assist you in a software license consolidation.

If I upgrade may I use my current licenses?
No. If you have current maintenance, we can exchange your licenses for you. You may then register your licenses for the upgraded version.
Authorization Code Check Failed Message
When the Authorization Code Check Failed message appears it is because something has been entered in differently. Here are a few things to try that commonly fix this problem.

Check to make sure the case is correct. For example, if the Licensee Name was "WaveLink" and had been entered in as "Wavelink"

Leaving a space on the end of the field can cause this as well. IE: "WaveLink "

Another common error is selecting an incorrect platform version. This needs to be the version you have the license for, but should also match the version of Telnet on the device.

I registered for the wrong version of your product. How can I fix this?
We will go ahead and exchange your order and you may then go in and register for the correct platform version.
Is there a way to have TelnetCE pop up on startup instead of the Intermec Simulation
No. We do not support this.
Unable to License "Attempting to contact a license server on the local segment: Timed out"
  1. The error "Attempting to contact license server on a local segment: Timed out" is often caused by a mismatch in licenses. This could be caused by purchasing one version of telnet with a different version installed onto the device. Verify the version on the device by going to Options and About.

    Also pay attention to the Emulation type used for registration.

  2. Make sure that the license server address is entered in the emulation parameters.

    Emulation > Common > License Server Address

My screen size is wrong and I can only see some of the text, how do I make the screen larger?
To adjust the screen size with in TelnetCE you will need to adjust the font size which will in turn adjust the screen size and real-estate on the devices screen.
Can I use GPRS with Wavelink’s telnet client?
Yes you can use GPRS with Wavelink’s emulation clients. The Clients connect over IP making it possible to use GPRS.
How do I set up concurrent sessions on my client?
  1. Access the Configuration Manager.
  2. Locate the Emulation > Common > Number of Sessions parameter.
  3. Use the Number of Sessions dialog box to specify the maximum number of sessions.
  4. Click OK.
  5. Save the new configuration.
  6. Close the Configuration Manager and download the new configuration to the mobile device.

Source: Emulators User Guide, Appendix B: Common Configuration Tasks

How do I configure a Scan Handler to modify scans on input?
  1. Access the Configuration Manager.
  2. In Configuration Manager, locate and right-click the Scanner > Common > Scan Handler parameter. A menu list appears.
  3. Click Add. The Scan Handler dialog box appears.
  4. Use the Scan Handler dialog box to configure a new scan handler.
  5. Click OK.
  6. The new scan handler now appears beneath the Scan Handler parameter in the Configuration Manager

Source: Emulators User Guide, Appendix B: Common Configuration Tasks

How do I map a key, or keys, to different key input? (For example, the "g" key to F10)?
Create a Key Macro

  1. Access the Configuration Manager.
  2. In the Configuration Manager, locate and right-click the Emulation > Common > Key Macro parameter. A menu list appears.
  3. From the menu list, select Add. The Key Macros dialog box appears.
  4. Use the Key Macros dialog box to configure the new key macro.
  5. After you have configured the key macro, click OK. The new key macro now appears beneath the Key Macros parameters in the Configuration Manager.
  6. Save the new configuration.
  7. Close the Configuration Manager.
  8. Download the new configuration to the mobile device

Source: Emulators User Guide, Appendix B: Common Configuration Tasks

Studio

How do I Upgrade My Licenses?
When upgrading any Wavelink software to the newer version, a newer version of the license is required.

This is a process we refer to as "license exchange/license upgrade" but can only be performed based on your licenses currently being under a maintenance contract.

A license exchange can be performed by contacting us at customerservice@wavelink.com or calling our support line: +1 888-699-WAVE(9283) ext 2.

Please have your Sales Order number for your licenses ready.

Additional Information:
If you have numerous licenses, please feel free to contact us at support and we can assist you in a software license consolidation.

If I upgrade may I use my current licenses?
No. If you have current maintenance, we can exchange your licenses for you. You may then register your licenses for the upgraded version.
I registered for the wrong version of your product. How can I fix this?
We will go ahead and exchange your order and you may then go in and register for the correct platform version.
User Limit Reached
Most likely the user was turning off devices without logging out of the Studio session. So the error they receive is in response to maxing out the allowed amount of sessions. The user just needs to go into their Studio administrator and close sessions.
Listing of Wavelink Product Ports including Avalanche, SecurePlus (formerly CE Secure),
Remote Control, ConnectPro (formerly TermProxy) and Studio Enterprise Server Ports
The following table provides a list of the ports that the Mobile Device dServer uses.
5432 Avalanche MC JDBC (Internal Use, facilitates communication between the Enterprise Server and PostgreSQL database.)
TCP
7221 Avalanche MC License Server TCP
7226 InfoRail Service IR to IR router port TCP
7225 InfoRail Service TCP
5002 AMC Wavelink Authentication Service TCP
1899 Remote Control Communication TCP
5001 SecurePlus (formerly CE Secure) Authentication Service TCP
1777 Mobile Device dServer MU Protocol Service TCP/UDP
358 Wavelink Avalanche Mobility Center

Infrastructure dServer Ports
7200 Infrastructure dServer RPC TCP
7208 Infrastructure RMI TCP
7210 Infrastructure dServer Alert Service RPC TCP
7211 Infrastructure dServer Service Manager TCP
7212 Infrastructure dServer SNMP Server UDP
7213 Infrastructure dServer SNMP Alert Service UDP
7214 Infrastructure dServer SNMP Statistics Service UDP
7215 Infrastructure dServer SNMP Server Security UDP
7216 Infrastructure dServer System Interface TCP
7217 Infrastructure dServer Web Server (Tomcat) TCP
7218 Infrastructure dServer Web Server (Apache) TCP
7219 Infrastructure dServer UDP Proxy (Internal use) UDP
161 SNMP TCP/UDP
80 HTTP TCP
69 Trivial File Transfer Protocol UDP
23 Telnet TCP/UDP
The following is a list of TCP/UDP socket ports used by the Wavelink Avalanche software:
TNClient License Server
Broadcast UDP 1820
Receive License on UDP port 2001

Avalanche Agent/Enabler communication
UDP/TCP port 1777 - Avalanche console listening port.
UDP/TCP port 1778 - Clients (enabler) listening port.
UDP/TCP port 1779 - Console server port (Agent listening for communication from the Avalanche Manager console)

Host connections
Default port = 23
ConnectPro (Formerly TemProxy)
4428 - Default web server port
4430 - Default proxy service proxy1 for listening

StudioCOM
Default listening ports can be 2001 or 1000 (should be at least 1000 or higher to avoid system conflicts). The clients will create a random port on their side to communicate with. This is usually in the 1400-1500 range. Auto discovery is 900 and 901

Studio Java
UDP port 905 for Auto discover on the server
UDP port 903 for Auto discover on the client
port 1000 and up for application listening port
(should be open for editing as needed)
Wavelink.com Homepage Stay Connected: Wavelink on Twitter Wavenlink on YouTube   |   Downloads   |   News   |   Blog   |   Contact Us   |   Shopping Cart   |   My Account Live Chat Icon

© 2011 Wavelink Corporation. All Rights Reserved.
Privacy Statement