mip.ini File
The mip.ini file specifies the order in which incoming Mobile IP requests are processed by the optional mobility modules. The following Mobile IP methods can be specified:
To enable deployment in mixed 3GPP2/WiMAX environments, these modules can operate at the same time. Incoming requests are processed by the modules in the order listed in the mip.ini file. If a module determines not to act on a request, it passes the request onto the next module specified in the list.
 |
NOTE: 3GPP and 3GPP2 can be enabled simultaneously. 3GPP is not a mobility module and is supported with the Steel-Belted Radius Carrier core license. To support 3GPP, you need to configure the 3gpp.ini file, see Chapter 9, 3GPP Configuration File. 3GPP is implicitly last in the mip.ini list, and is not specified in the list, since it is not a mobility module. Each mobility module (CDMA and WiMAX) listed in the mip.ini file gets a chance at servicing the incoming message. If the message is for that module, then the module services it. If a module decides that the message is not intended for itself, it hands the message to the next module listed in the mip.ini file. If none of the listed mobility modules service the message, and if 3GPP is enabled, then 3GPP gets a chance to service the message. Of course, each of the mobility modules needs to be enabled in order to examine and possibly service the request. |
|
NOTE: The mip.ini file is read whenever Steel-Belted Radius Carrier restarts or receives a HUP signal. |
[MobileIpMethods] Section
Specifies the order in which the Mobile IP wireless methods are checked. |
Example
[MobileIpMethods]
WiMAX
3GPP2
In this example, the WiMAX module attempts to process the incoming Mobile IP requests first. If it determines that the request is not a WiMAX request, then it passes the request on to the next module in the list, 3GPP2 (CDMA).
