Share via

WAP Physical Proxy: PXPHYSICAL

  • Article

4/8/2010

The following table lists the parms in PXPHYSICAL element processed by the device. For more information see PXLOGICAL Configuration Service Provider.

WAP characteristic WAP parm Comments

PXPHYSICAL

 

For an acceptable proxy, a globally unique identifier (GUID) will be created. It is set as DestID in the Connection Manager proxy definition. A network entry of CM_Networks will also be defined. The network name uses the following format:

NAME + "@" + PHYSICAL-PROXY-ID + "@" + "PROXY-ID" + "@PXLOGICAL"

NAME is the NAME parm in the PXLOGICAL element.

 

PHYSICAL-PROXY-ID

For each WAP proxy in Connection Manager, the WAP proxy name is the combination of PHYSICAL-PROXY-ID and its corresponding logical proxies PROXY-ID and TO-NAPID.

PHYSICAL-PROXY-ID + " 
@" + PROXY-ID + " 
@" + TO-NAPID

 

DOMAIN

If no DOMAIN parm is supplied, the corresponding parm value from the logical proxy definition is used. The DOMAIN parm and the GUID of this proxy will be set as entries of the Connection Manager mapping table. The value of DOMAIN will be modified to match the mapping table's request for the device.

 

PXADDR

For Push Proxy, PXADDR represents the Short Message Service (SMS) address that push proxy uses to send the message to the SMSC center.

 

PXADDRTYPE

On Smartphone 2002 and Pocket PC 2002 devices, only the IPv4 address type is accepted by Internet Explorer Mobile. E164 addresses will also be saved; however, they will be used by the Push Router only as a push proxy address if the PUSHENABLED parm is set.

 

PUSHENABLED

Indicates whether or not push operations are enabled.

 

TO-NAPID

The PXLOGICAL Configuration Service Provider creates one proxy for only the last TO-NAPID that it finds in a PXPHYSICAL that matches the NAPID of a NAPDEF. The corresponding GUID of the NAPID is set as SrcID in the Connection Manager WAP proxy.

Currently, Connection Manager does not support an automatic switch among multiple Point-to-Point Protocol (PPP) settings for one WAP gateway. Only the last TO-NAPID will be accepted.

The push proxy NAPDEF settings that use the Global System for Mobile Communications (GSM)-Short Message Service (SMS) bearer are ignored. However, for the purpose of validating the xml, the TO-NAPID should still be provided in PXPHYSICAL.

Push Proxy Gateway (PPG) should use the Short Message Service Center (SMSC) that is saved on the Subscriber Identity Module (SIM) card. The SMSC number can be changed by using the Telephony API (TAPI) Configuration Service Provider or by using the GSM network directly.

PXPHYSICAL/PORT

PORTNBR

At most, two pairs of PORT sets can be accepted whose SERVICE value could be CO-WSP and CO-SEC-WSP.

PXPHYSICAL/PORT

SERVICE

 

See Also

Reference

PXLOGICAL Configuration Service Provider

Concepts

Standard OMA Client Provisioning Parameters Processed by the Device