| Syntax | void TSPI_phoneSetDeviceIDBase(dwTSPIVersion, dwDeviceID) This function tells the Service Provider what its lowest numbered phone device ID should be. |
| Parameters | DWORD dwTSPIVersion Specifies the interface version under which the Service Provider and TAPI DLL operation for this function. This version number has already been negotiated using TSPI_phoneNegotiateTSPIVersion. |
| DWORD dwDeviceID Specifies the new base phone device ID from which the Service Provider should number its phone devices. | |
| Return Value | none |
| Call States | Not applicable |
| Comments | Under directed park, the application determines the address at which it wants to park the call. Under non directed park, the switch determines the address and provides this to the application. In either case, a parked call can be unparked by specifying this address. |
| The Service Provider numbers its available phone devices contiguously starting at the number set by this function. For example, if the Service Provider supports 4 phones and this procedure is called with a base dwDeviceID of 5, the phones have device IDs 5 through 8 both when device IDs are used as "input" parameters (as in TSPI_phoneGetDevCaps) and when device IDs are used as "output" parameters (as in a returned PHONEADDRESSCAPS data structure). This procedure may be called again, in which case device ID numbering changes for all subsequent requests. The operation returns synchronously. The device IDs before this procedure is called start at 0. Since this procedure is called without an active device to identify the interface version, it includes an already-negotiated TSPI version number defining the interface version at which the Service Provider is expected to operate for this function. | |
| Comparison | This function has no correspondence at the TAPI level, where device IDs are a zero-based range spanning all Service Providers. This function is used to "divide up" the range of device IDs between different Service Providers. |
| The responsibility for "offsetting" device IDs resides with the Service Providers rather than with the TAPI DLL to allow Service Provider designers maximum flexibility in defining extensions. Since the Service Provider uses the same device IDs as the application level, device-specific extensions can pass device IDs back and forth to applications using consistent device ID numbering. | |
| See Also | none |