To access the Mobile Access Gateway Provisioning System, click on the login
button (below) and enter your developer account name and password.
Privacy Policy:
At Openwave, we are committed to protecting your privacy. We use the
information we collect about you so that we can contact you if necessary, and
so that we may better understand what types of developers are using our
products and services. Your account information is used only by Openwave or on
Openwave's behalf. It will only be disclosed to other individuals, companies or
organizations who are obligated to keep your account information confidential
and only when disclosure is consistent with our commitment to your privacy.
What is Mobile Access Gateway Provisioning?
You may provision (i.e. create and administrate) up to five subscriber accounts
on our Developer Mobile Access Gateway Server ("Devgate2"). A subscriber
account allows the Simulator to access applications and services through a
production Mobile Access Gateway Server environment. In addition to providing a
fully compliant WAP 1.1 Gateway, the Mobile Access Gateway Server also provides
basic subscriber services (Bookmarks, Subscriber ID, Alert Inbox, Fax)
and allows you to test notifications (both UP.Notify and WAP Push).
How to View Your Subscribers
When you signed-up for your developer account, a Mobile Access Gateway
subscriber was automatically created for you. To view your subscriber
(and any additional subscribers that you may have manually created), follow
these steps:
Login
to the Mobile Access Gateway Provisioning System
Click on the Find Subscriber button. This will display the Find
Subscriber Form.
Click on the Submit
button to view all of your subscriber records.
Click on the Client ID field to view the details for any given
subscriber account.
How to Create a New Subscriber
Follow these steps to create a new subscriber account:
Login
to the Mobile Access Gateway Provisioning System.
Click on the Add Subscriber button. This will display the Subscriber
Registration Form.
Click on the radio button for the appropriate Client ID Format.
Choose WAP if you are using the Openwave® Simulator v4.1, 5.1, 6.1, or
6.2.2. Otherwise, choose HDTP
for Openwave Simulator v3.2 and earlier. If you plan to use multiple
versions of the Simulator, you should create multiple subscriber accounts --
one for each SDK version.
Enter the IP address of your PC in the Client ID field. This
should be the same PC on which you installed the Openwave® SDK. You must
create a unique Client ID
for each SDK version you plan to use. You can do this by appending a
4-digit string to your IP address. For example, for SDK 6.1 you can
append .9999 to the IP address of your PC (i.e. if your IP is 222.222.222.222,
provision 222.222.222.222.9999).
Enter your first and last name in the Name
field.
Click on the Submit button to create the subscriber account.
How to Connect the Simulator Simulator 6.2.2
Make sure that you've downloaded the WAP Plugin for the SDK 6.2.2
Select Tools -> Options from the Simulator Menu after launching the Openwave SDK 6.2.2 WAP
Select the Sever Tab and click on the Add button
Enter devgate2.openwave.com as the server address and click the Next button
Leave the default settings on the next screens and just click Next
Enter the IP address that you've provisioned above
Leave the default settings on the next screen and just click Next
Enter a name for your new configuration and click Finish
Click on your new profile and select the Activate button
How to connect the Phone Simulator v7
Select Settings -> Server Profiles from the Simulator Menu after launching Openwave Phone Simulator v7
Click on the New button to create a new profile
Enter a name for the profile
Select the WAP radio button
Enter devgate2.openwave.com as the proxy address
Select IP Address from the Client ID Format drop down
the client ID will automatically become the IP address of your PC. If you wish to
use an alternate IP address as the client id, click the Edit IP button and
input the IP address you wish to use for your client ID in the dialog that comes up
Check Activate this profile
Click the OK button
The Phone window will exit and restart, and will re-activate using your new profile. You may now close the
Server Configuration Profiles dialog window
Follow these steps to connect the Simulator 4.1 or earlier
Select UP.SDK -> UP.Simulator
from the Programs menu on your PC to launch the Simulator.
Select Settings -> UP.Link Settings from the Simulator menu. In the
dialog, set the UP.Link address to devgate2.uplanet.com and then press OK.
Make sure the home deck is displayed on the phone. If you are not able to
connect to the Mobile Access Gateway, please refer to the
SDK Tools & APIs Reference (.pdf) for information on Simulator system
requirements.
Follow these steps to connect the Simulator 5.1
Select Openwave SDK 5.1 -> Openwave SDK 5.1
from the Programs menu on your PC to launch the Simulator.
Select Device Settings from the Simulator menu. In the dialog, select
the radio button next to Proxy 1: Auto provisioned gateway and then
press OK.
Make sure the home deck is displayed on the phone.
Follow these steps to connect the Simulator 6.1:
Make sure you downloaded and installed the
WAP simulator plug-in for SDK 6.1.
You need this add-on to the SDK 6.1 main package in order to connect to a WAP
gateway.
The "Openwave SDK 6.1 WAP" shortcut and menu item point
to a .cmd batch file, which by default, is located at C:\Program
Files\Openwave\SDK 6.1\program\wap\OSDK61wap.cmd.
Open up this file in your favorite editor and set the
command string to:
start /b osdk61wap.exe -g devgate2.openwave.com -clearcache
-secure -pho slimjim-mini-lime.pho -sethome
http://developer.openwave.com/dhome5.cgi
If you want to be able to test WAP Push, and/or server
side cookies, or you've used the Openwave SDK 4.1 in conjunction with
devgate2.openwave.com in a secure mode, you will also need to set the -clientid
flag. The -clientid value should be set to the
hexadecimal version (minus the first 4 digits) of the clientid you created for
SDK6.1. In the example below, which shows a sample subscriber profile on
devgate2, the clientid should be set to 0401020304270F. Ensure
that you use the correct client ID for your sdk.
start /b osdk61wap.exe -g devgate2.openwave.com-clientid
0401020304270F -clearcache -secure -pho slimjim-mini-lime.pho
-sethome
http://developer.openwave.com/dhome5.cgi
Name
Value
Client ID
1.2.3.4.9999
Full Client ID (Hexadecimal)
0A000401020304270F
Client ID Format
WAP, IP Address(IPv4 Packet/Circuit)
Subscriber ID
1039131842-40089_devgate2.uplanet.com
Home Page
UP.Dev Home Page
Status
active
Client Type
Client Version
Created By
test@openwave.com
Create Date
05-Dec-2002
Session State
force
Signature
Messenger Push Stack Service
UnsecureWAP1.1_IPv4
Messenger Push Client Port
4445
Messenger Push Client Address
001.002.003.004
Name
Cross Reference
Email Alias
test
Save this file and start SDK 6.1 WAP from the menu or shortcut.
For all simulators, to verify that you are connected to the correct gateway with
the correct client ID, you can point the simulator to:
http://developer.openwave.com/dev/sdk.41/scripts/whoami.cgi#u
How to Synchronize a Dynamic IP Address
If your PC's IP address is dynamically assigned by your Internet service
provider, for the Openwave SDK 3.x/4.x you will need to synchronize your
subscriber's Client ID each time you connect to the service provider by
following these steps:
Login to the Mobile Access Gateway Provisioning System.
Click on the Developer Utilities button.
Click on the Sync Phone link.
If you are using the Openwave SDK 5.1 you can fix the client ID that your
simulator uses by entering your current IP address (with the unique
4-digit string appended to it) in the Proxy 2 input field
under the Simulator -> Device Settings dialog. This step need only be taken
once, and the Client ID that you specify will be used regardless of your
current IP Address. *NOTE: Be sure to set the Client ID Format to IP Address: (IPV4 Packet/Circuit)
If you are using Openwave SDK 6.1, you can fix
the client ID that your simulator uses by adding the -clientid argument to
the command string in the .cmd file. As mentioned above, the value should
be set to the hexadecimal version (minus the first 4 digits) of the Client
ID you created for that SDK.
