다음을 통해 공유

Controlling VOIP interfaces on Windows Mobile devices

  • 아티클

RTC 1.5 can be restricted to use only certain types of interfaces (Wifi, Ethernet, etc.) on Windows Mobile devices. Same restriction cannot be applied on Windows CE, as RTC uses connection manager functionality to do that, which is not available on Windows CE.

 

RTC can be restricted using the following reg keys. These reg keys need to be set before RTC gets initialized.

 

HKLM\Comm\RTC\AdapterTypes

 

One can list all the allowed interfaces as numerical keys:

 

e.g. 1

              2

              3

              ETC.

 

The value of each key should be an ORed value of the connection manager interface type and sub-type

 

e.g. If one wants to allow Ethernet interface only.

The connection manager interface type to use will be CM_CONNTYPE_NIC (0x2)

The connection manager sub-interface type to use will be CM_CONNSUBTYPE_NIC_ETHERNET (0x1)

 

The Ored value = (0x2 << 16) | 0x1 = 0x20001

 

So the reg key will look like:

              

HKLM\Comm\RTC\AdapterTypes\1 (DWORD with value 0x2001)

 

Similarly, if Wifi is also desired,

The connection manager interface type to use will be CM_CONNTYPE_NIC (0x2)

The connection manager sub-interface type to use will be CM_CONNSUBTYPE_NIC_WIFI (0x2)

 

The ored value = 0x2 << 16 | 0x2 = 0x20002

 

So the reg keys will look like:

              

HKLM\Comm\RTC\AdapterTypes\1 (DWORD with value 0x2001) ß for Ethernet

                                                                 2(DWORD with value 0x2002) ß For Wifi

Comments

  • Anonymous
    January 16, 2008
    PingBack from http://voip.2go5.net/2008/01/16/controlling-voip-interfaces-on-windows-mobile-devices/

  • Anonymous
    January 28, 2008
    What would be the CM interface + sub-interface types for a device that only has a 3G (HSDPA) connection to the network? Getting RTC to work correctly on a device that only has 3G access does not seem to work when using the above registry settings.. No valid codecs are listed in the SIP invite transaction, as if no "bandwidth" was available for the RTC codec.

  • Anonymous
    February 02, 2008
    http://msdn2.microsoft.com/en-us/library/aa455858.aspxCM_CONNTYPE_UNKNOWN 0CM_CONNTYPE_CELLULAR 1CM_CONNTYPE_NIC 2CM_CONNTYPE_BLUETOOTH 3CM_CONNTYPE_UNIMODEM 4CM_CONNTYPE_VPN 5CM_CONNTYPE_PROXY 6CM_CONNTYPE_PC 7http://msdn2.microsoft.com/en-us/library/bb416501.aspx

  • Anonymous
    February 02, 2008
    I'm attempting to configure RTC to use PC passthrough, and even restricted it to just that; with no luck. Anyone have any ideas?   <<Rajesh>> Desktop pass through does not support UDP protocol. Since RTC always uses UDP for media, you will not succeed in establishing audio/video calls.   Thanks!