create connection profile

1. After starting "Mobile Partner" go to "Tools", "Options".
   
2. In the following window chose "Profile Management" on the left. Then click the "New" on the upper right.
   
3. Now enter the following details:
   • As "Profile Name" enter some title for your connection (e.g. "Vodafone").
   • Under APN chose "Static" and enter your operator's accesspoint in the "APN" field. (For example "pp.vodafone.co.uk" if you are using a British Vodafone PAYG SIM)
   • Don't change the remaining fields unless you know what you do.
4. Now click "Save" to save your new profile and close the windows by clicking "OK" (lower right).
   Confirm the following question "Do you want to save the changes" with "Yes".
   
5. Now chose "Connection" in Mobile Partner. There you should see your new profile. Now you can connect through the newly created profile by clicking "Connect". As soon as the connection has been established, the button is renamed in "Disconnect" and serves to disconnect your connection.

plugins
Mobile Partner has several plugins integrated, which are mostly not activated by default. Some can be enabled by editing the file C:\Program Files\Mobile Partner\config\PluginsConfig.xml.

PluginsConfig.xml
The file is build in the XML-format and consits generally of four sections:

1. <devices> ... </devices>
   In the devices section <item>-tages assigns a name to each device model according to it's product/hardware ID (productID can be found unter Tools / Diagnosis after starting Mobile Partner) and a description, which doesn't seem to be of relevance.
   e.g. a tag assigning the name "E180" to the device with the productID "E180" and some description looks like this:
   <item name="E180" productid="E180" describe="3G Data Card"/>
   
   The devices section usually contains dozens of devices, however only those applying for your device are necessary. The remaining code is useless unless and can be deleted.
   
   
2. <common><plugin> ... </plugin></common>
   Next there is the plugin section, which again contains <item>-tags, that define all the plugins. However it seems like you can activate plugins (e.g. CallPlugin and CallUIPlugin) even if they are not listed here. So the function of this section is unclear.
   
   
3. <device name="???"> ... </device>
   After the </common> tag the device section starts, which will define the available plugins for each model. To add the voice-call plugin (consiting of three plugins) for the E169, the following code is used:
   <device name="E169">
   <plugin>
   <add name="CallPlugin" clsid="8FC7A17B-EA76-4e6e-872D-9AAC222C8B03"/>
   <add name="CallUIPlugin" clsid="58A0343A-93DB-4ea2-92B4-C51589629381"/>
   <add name="CallLogUIPlugin" clsid="1FCAC0FF-9E87-450f-8258-1155D7696571"/>
   </plugin>
   </device>
   
   The device section usually contains dozens of devices, however only those applying for your device are necessary. The remaining code is useless unless and can be deleted.
   
   
4. <customize name ="???"> ... </customize>
   The customize section contains changes on the activation or deactivation of plugins, which will overwrite definitions in the device section (above) if your version of Mobile Partner is customized/branded.
   As KTF (presumably a Korean operator) doesn't want their subscribers to have SMS-functionality in Mobile Partner, they remove is by the following code:
   <customize name="KTF_C148">
   <plugin>
   <remove name="SMSPlugin" clsid="AB349C02-A88F-4ef5-A44A-F178B9FAAF35"/>
   <remove name="SMSUIPlugin" clsid="ED395DF6-E3BA-478e-8AE9-D8A1BF090214"/>
   </plugin>
   </customize>
   
   Of course one could also use an <add>-tag here and add plugins instead of removing them (as showed above).
   
   The customization is dependant on the operator ID (in the example above "KTF_C148"), which is defined in the C:\Program Files\Mobile Partner\SysConfig.dat file, which has a section like this:
   [customize]
   operator=O2_C40
   simtype=SIM/USIM
   uimtype=UIM
   
   This example shows the operator ID "O2_C40", which stands for O2 Germany's prepaid product "O2 Loop".
   On unbranded versions of Mobile Partner the operator ID is "common", so the section in SysConfig.dat would look like this:
   [customize]
   operator=common
   simtype=SIM/USIM
   uimtype=UIM
   
   If you edit SysConfig.dat and replace the operator ID by "common" (like above), you will immediately have an unbranded version of Mobile Partner.
   
   
   

voice-call plugin
Since only some Huawei devices support voice-calling, this plugin can only be used properly if supported by your hardware. Currently the following devices are confirmed to support voice calls:

• E169, E169G
• E173u-2
  
• K3715
• K3565
  

Other devices like the E160/G/E/X can establish calls, but there is no audio. Currently it's unclear if this is caused by hard- or software and so if this can be patched.



customization / operator branding
As mentioned above, the file C:\Program Files\Mobile Partner\SysConfig.dat sets an operator ID, which will determine if Mobile Partner is operator-branded or not.
An operator branding is defined by some ID, which is "O2_C40" in this case:

[customize]
operator=O2_C40
simtype=SIM/USIM
uimtype=UIM

While the unbranded version set the operator ID to "common":

[customize]
operator=common
simtype=SIM/USIM
uimtype=UIM
This operator ID is already important during installation of branded versions of Mobile Partner, since the data.bin file (can be opened with WinRAR), which is part of the setup files, contains a folder named by the operator ID. This folder (e.g. "O2_C40") contains dozens of files, which will be installed instead of the common files, which would be installed for an unbranded version. However branded setup files do also contain the common files, so one could modify the SysConfig.dat file inside the data.bin file in order to make setup install an unbranded verison.






How to Use an STK Function????

The Mobile Partner supports the SIM Application Toolkit (STK) functions.
I
The STK functions are supplied by the network service provider.
Procedure
Step 1 Choose Tools > Sim Toolkit.
Step 2 Select the required STK function


IF ANY IDEA ABOUT STK FUNCTION FEATURE PLEASE SHARE.
version numbering theme
Any idea on how the system of the version numbering theme? Please share your thoughts!