Configuring an Application to Use a Specific Network
In specific cases, an application may need to bypass Connection Planner and explicitly connect with a specific network GUID. For example, a Multimedia Messaging Service (MMS) application may need to connect to a specific MMS APN. In another example, a traffic application may need to connect to a specific GPRS APN, even if a cheaper connection, such as Wi-Fi, is present.
To support scenarios in which an application needs to bypass Connection Planner and connect with a specific network GUID, Connection Manager exposes the ConnMgrMapConRef function. This function allows applications to pass a specific GUID as a parameter to connect to a specific network. An application can choose to specify a connection object, either a Network Access Point (NAP) or a proxy object, to connect to, and Connection Manager will return a destination network GUID that uniquely identifies the given connection. When the application subsequently calls ConnMgrEstablishConnection with this GUID, Connection Manager ensures that the right connection path is chosen as specified by the application originally.
If access to an application (such as MMS) requires a WAP gateway and the WAP gateway is configured using the PXLOGICAL configuration service provider, then the first parameter of the ConnMgrMapConRef call must contain the PHYSICAL-PROXY-ID, PROXY-ID and TO-NAPID as specified by the PXLOGICAL configuration. Use the format PHYSICAL-PROXY-ID@PROXY-ID@TO-NAPID to specify the required information in the first parameter of the ConnMgrMapConRef call.
See Also
Send Feedback on this topic to the authors