Identifying your service to the UP.Link Server

The UP.Link Server maintains a transaction log of UP.Phone requests; each log entry specifies information such as the transaction date and time, the subscriber ID, and the domain of the requested URL. It can also include a service identifier, if you provide it. The service identifier is not required. However, it helps the UP.Link administrator track requests, which is useful if you have a billing arrangement with the UP.Link provider.

To provide a service identifier, set the x-up-service HTTP header to a string that identifies your service. For example, the following HTTP response identifies the service that originated it as "myservice."

x-up-service: myservice

Content-type: text/vnd.wap.wml
<wml>
<card>
<p>
You just used myservice!
</p>
</card>
</wml>

If you are using the UP.SDK Perl library to generate a digest, you can add the x-up-service header by including a line similar to the following before calling AppUtils::OutputDigest():

...

$digest->addHeader("x-up-service", "UP.SDK Sample App");
...

If you are using the UP.SDK C library to generate a digest, you can add the x-up-service header by including a DigestAddHeader() call similar to the following before calling DigestSerialize():

...

Digest digest;
...
DigestAddHeader(digest,"x-up-service","UP.SDK Sample App");
...

If you are using the UP.SDK C library to send a fax, you can add the x-up-service header by including a FaxResponseAddHeader() call similar to the following before calling FaxResponseSerialize():

...

FaxResponse fr;
...
FaxResponseAddHeader(fr,"x-up-service","UP.SDK Sample App");
...

The following sample application provides examples of how to use the C library functions to set the x-up-service header:

sdk_installdir/examples/source/digests/test1.c