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 server administrator track requests, which is useful if you have a billing arrangement with the UP.Link server 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."
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 the AppUtils::OutputDigest() call. For example:
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 the DigestSerialize() call. For example:
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 before the FaxResponseSerialize() call. For example:
The sample application (test1.c) in sdk_installdir/examples/source/digests provides examples of how to use the C library functions to set the x-up-service header.