Troubleshooting guide

TD 92735EN
15 May 2012 / Ver. G
Installation and Operation Manual
Unite Connectivity Manager
153
Message ID
The Message ID is used to refer to previously sent messages, for example, to make the
handset beep at each transmission of the message or to erase a previously sent message.
The same Message ID as when the message originally was sent has to be used.
The Message ID can be set manually by the user or automatically by NetPage. NetPage sets
the Message ID automatically if the parameter “id” is set to 0 or not specified. If the number
is generated manually, it should be kept in the range 1 to 2147483647.
NOTE: NetPage does not check for conflicting manually set message IDs, therefore manually
set message IDs must be kept unique. Conflicting message IDs will result in erroneous
status reports among other problems.
Erase message
A previously sent message can be erased with a new URL call. Call ID, Message ID and the
parameter “del” should be included in the URL call. This brings that the Message ID has to be
set manually if a message should be able to erase later on. The parameter “del” has to be
given a value but the value has no meaning, that is, it can have any value. The URL will look
as follows, “http://xxx.xxx.xxx.xxx/cgi-bin/npcgi?no=1234&id=23&del=1”.
UTF8 encoded
When NetPage is accessed from a cordless unit that uses WAP version earlier than 2.0, the
message that is sent will be UTF8 encoded. The parameter “utf8” then has to be included to
indicate this for the CGI script in NetPage. The parameter “utf8” has to be given a value but
the value has no meaning, i.e. it can be any value.
NOTE: This parameter should not be used for HTML based NetPage applications.
22.2.6 Translation of the User Interfaces
The texts presented in the user interfaces can be translated. The translation is entered
differently depending on the example user interface that is used. The HTML files
index_template and index1, index2 and index3 are translated in the HTML code. The default
Netpage user interface (index4) on the other hand is translated in the “language.js” and
“receive.html” file, where receive.html includes the NetPage message history applet. See
figure 66 on page 154 for an overview of where the different files are used.
Start Page
1 Download/copy the file and included image from the FTP area, see 22.2.2 Files for
Translation/Editing on page 148.
2 Open the file in a text or HTML editor and translate all words.
3 Save the file.
4 Upload/paste the file to the FTP area, see 22.2.7 Upload the Files to the FTP Area on
Unite CM on page 155.
5 Check that the user interface looks all right.
Example User Interfaces index_example1.html, index_example2.html and
index_example3.html.
1 Download/copy the file and included images from the FTP area, see 22.2.2 Files for
Translation/Editing on page 148.