Panasonic TGP600 Developer's Manual

Brand: Panasonic

Model: TGP600

Type: Developer's Manual

Panasonic SIP Phone TGP600, HDV100/130/230/330/430

XML Application Developer’s Guide

Revision 2.52

Revision

No.

Date

Page

Comments of revision

1.00

16 July, 2015

First Release

2.00

14 Sep, 2015

Add HDV330/430 models

2.10

08 Dec, 2015

Modify some contents for Enhanced feature on December/2015

2.20

18 May, 2016

Modify some contents for Enhanced feature on May/2016

2.30

16 Sep 2016

Modify some contents for Enhanced feature on Aug/2016

2.40

2 Nov 2016

Modify some contents for Enhanced feature on Oct/2016

2.50

6 Dec 2016

Modify some contents for Enhanced feature on Dec/2016

2.52

17 May 2017

Delete error code of GetConfig.(Mistype)

[CONTENTS]

1. INTRODUCTION ............................................................................................................. 2

2. OVERVIEW...................................................................................................................... 3

2.1. A GENERAL SYSTEM DIAGRAM (NETWORK PHONEBOOK) ................................................. 3

2.1.1. Easy operation of SIP Server Call Control (e.g. DND/CFWD) ......................................... 3

2.1.2. Network Phonebook system example ............................................................................. 3

2.2. BASIC OPERATION ........................................................................................................ 4

2.2. XML DATA ACCESS FLOW ............................................................................................. 5

2.3. AVAILABLE MEDIA FORMAT ............................................................................................ 5

2.4. DISPLAYING PRIORITY ................................................................................................... 5

2.5. DISPLAY AREA .............................................................................................................. 6

3. HTTP SERVER INTERFACE ........................................................................................... 7

3.1. GET XML DATA ............................................................................................................ 7

3.1.1. Structure of HTTP Server ............................................................................................... 7

3.1.2. HTTP POST/GET Request/Response from the phone to HTTP Server. ......................... 8

3.2. PUSH XML DATA ........................................................................................................ 10

3.2.2. Push Event Process ..................................................................................................... 11

3.3. HTTP SEQUENCE EXAMPLE ........................................................................................ 12

3.3.1. GET XML method ......................................................................................................... 12

3.3.2. Push method ................................................................................................................ 12

3.3.3. GET PhoneBook method .............................................................................................. 13

4. PHONE CONFIGURATION AND OPERATION............................................................. 14

4.1. WEB USER INTERFACE SETTING LIST – CONFIGURATION PARAMETER ............................ 14

4.2. COMMON CONFIGURATION AND OPERATION ................................................................. 15

4.2.1. Configuration Parameter .............................................................................................. 15

4.2.2. Remarks of Softkey and FFkey Operation (*1) ........................................................... 15

4.3. INITIATION METHODS OF XML APPLICATION (*1) .......................................................... 16

4.3.1. Acquiring XML data corresponding to the Phone Status - Configuration ....................... 16

4.3.1.1. Configuration Parameter ........................................................................................... 16

4.3.2. Network Phone Book Configuration and operation ....................................................... 17

4.3.2.1. Configuration Parameter ........................................................................................... 17

4.3.2.2 Configuration Parameter (other than LDAP server) .................................................... 18

4.3.2.3. Network Phonebook operations ................................................................................. 19

4.3.3. Application Menu Configuration and operation.............................................................. 22

4.3.3.1. Configuration Parameter ........................................................................................... 22

4.3.3.2. Application Menu operations ...................................................................................... 22

4.3.4. Call Log Menu Configuration and operation .................................................................. 22

4.3.4.1. Configuration Parameter ........................................................................................... 22

4.3.4.2. Call Log key operations ............................................................................................. 22

4.3.5. Initiation Key Configuration and operation .................................................................... 24

4.3.5.1. Configuration Parameter ........................................................................................... 24

4.3.5.2. Initiation key operations ............................................................................................. 24

4.3.6. Redial key Configuration and operation ................................................................... 26

4.3.6.1. Configuration Parameter ......................................................................................... 26

4.3.6.2. Redial key operations ............................................................................................. 26

4.3.7. Cursor skip Configuration and operation ................................................................. 26

4.3.7.1. Configuration Parameter ......................................................................................... 26

4.3.7.2. Cursor skip operation ............................................................................................. 26

5. XML STRUCTURE ........................................................................................................ 27

5.1. XML DOCUMENT ........................................................................................................ 27

5.1.1. XML Schema of the phone ........................................................................................... 27

5.1.2. Name Space of XML Document .................................................................................... 28

5.1.3. Character reference ..................................................................................................... 28

5.1.3.1. Predefined Entities in XML ........................................................................................ 28

5.1.3.2. Numeric Character Reference ................................................................................... 28

5.1.4. XML Object Outline ...................................................................................................... 29

5.2. XML OBJECT DEFINITION ............................................................................................ 30

5.2.1. ppxml ........................................................................................................................... 31

5.2.2. Screen .......................................................................................................................... 32

5.2.3. Components ................................................................................................................. 33

5.2.4. Label ............................................................................................................................ 34

5.2.5. PictureBox .................................................................................................................... 36

5.2.6. TextBox ........................................................................................................................ 37

5.2.7. Menu ............................................................................................................................ 40

5.2.8. PhoneBook ................................................................................................................... 44

5.2.9. Events .......................................................................................................................... 45

5.2.10. SoftKeys ..................................................................................................................... 49

5.2.11. FFKeys ....................................................................................................................... 50

5.2.12. PageKeys(*1) ............................................................................................................. 51

5.2.13. SetVariables ............................................................................................................... 52

5.2.14. Timer .......................................................................................................................... 54

5.2.15. Execute ...................................................................................................................... 55

5.2.16. Trigger ........................................................................................................................ 56

5.2.17. Redialkey .................................................................................................................. 57

6. APPENDIX ..................................................................................................................... 59

6.1. ERROR CODE REFERENCE .......................................................................................... 59

6.2. EDITING XML CONTENTS ON THE PC ........................................................................... 63

ATTENTION

- This document is copyrighted by Panasonic Corporation or its licensor, and is protected by the

- All contents of this document are subject to change without notice.

- THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT ANY WARRANTY. Panasonic Corporation

AND ITS AFFILIATE COMPANIES (“PANASONIC”) DOES NOT MAKE OR PASS ON TO YOU

OR OTHER THIRD PARTY, ANY WARRANTY OR REPRESENTATION INCLUDING, BUT NOT

LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING,

PANASONIC DOES NOT WARRANT THAT THIS DOCUMENT WILL BE ERROR-FREE OR

THAT IT WILL MEET YOUR REQUIREMENTS. PANASONIC SHALL NOT BE LIABLE FOR

ANY DAMAGE SUFFERED BY YOU OR OTHER THIRD PARTY INCLUDING, BUT NOT

LIMITED TO, CONSEQUENTIAL, INCIDENTAL, SPECIAL OR PUNITIVE DAMAGES, EVEN IF

PANASONIC HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

1. Introduction

This document has described the technical information and specification for the XML application

development of the TGP600, HDV100/130/230/330/430 (Represents as TGP/HDV).

The corresponding Administrator Guide Document Version is from 2016 and depends on each model.

It is able to acquire the latest firmware and the related documents from the following URL.

https://panasonic.net/cns/pcc/support/sipphone/index.html

2. Overview

2.1. A general System Diagram (Network Phonebook)

Various types of applications such as following examples can be developed by using XML API.

2.1.1. Easy operation of SIP Server Call Control (e.g. DND/CFWD)

2.1.2. Network Phonebook system example

HDV

LDAP Server

For Company Directory

XML Server

XML contents on the HTTP Server

Display

Phonebook

LDAP Query

/Answer

Search name

TGP

HDV

SIP Server

XML Server

XML contents on the HTTP Server

Display Menu

Call Control

Operation

Call Control

TGP

2.2. Basic Operation

The phone translates XML data and generates GUI.

1) Parses XML data by using XML parser and analyze the meaning.

2) Creates Window for screen.

3) Prepare components.

Attach event handler and action function.

Create component image.

4) Place components on Window.

5) Show Window.

The PHONE (HDV)

HTTP Server

XML

Data

<ppxml>

………………….

</component>

………………..

</events>

</screen>

</ppxml>

Analyze XML data.

Prepare components.

Show components

TGP/HDV

(TGP)

1. Menu A

2. Menu B

3. Menu C

Soft1

Soft2

Soft3

(HDV330/430)

2.2. XML Data Access Flow

There are two methods to access XML Data.

2.3. Available Media Format

The following are available media format which can be supported in the phone.

It is recommended to adjust the media quality/size suitably beforehand.

Media

Type

Format

Total Size Max.

Model

Remarks

Picture

BMP

4bit grayscale

(The color palette is

not supported.)

132 x 64pixels

HDV130/230

Picture is displayed with

BW. (Black&White)

Picture

BMP

8 / 16 / 24bit

480 x 245pixels

HDV330/430

Picture is displayed as a

256 Color/High Color/

True Color

Text

TXT

UTF-8 plain text

128bytes

(Depends on

Models)

Character references

are not supported

except specific cords.

2.4. Displaying priority

The displayed objects are always overwritten in postscript information.

XML

SERVER

HTTP GET/POST

200 OK + XML DATA

HTTP POST

200 OK

HTTP GET/POST

200 OK + XML DATA

B. SERVER PUSH

EVENTMETHOD

A. TGP/HDV GET/POST

TGP/HDV

Event Trigger

2.5. Display Area

HDV100/130/230 (4 line)

TGP600 (6 line)

HDV330/430 (6 line)

Key 1

Key 2

Key 3

155dot

155

1dot

272

(Key1)

(key2)

(Key3)

Phone

Information Area

480

Status bar

245

Soft 1

Soft 2

Soft 3

40dot

1dot

128

160

Soft 1

Soft 2

Soft 3

Phone

Information Area

Soft 1

Soft 2

Soft 3

43dot

1dot

Soft 1

Soft 2

Soft 3

132

Phone

Information Area

3. HTTP Server Interface

3.1. Get XML Data

3.1.1. Structure of HTTP Server

HTTP Server is installed in followings:

1) PC Server

2) Appliance Server

HTTP Server usually manages following directory.

CGI for the phone usually processes along following steps.

CGI for TGP/HDV

Decode CGI parameters.

Execute requested process.

Generate XML data.

CGI-bin

Html

initialURL.cgi

Phonebook.c

・・・

Start.xml

Menu.xml

・・・

Document Root

Static XML file.

*) "Template" xml files may be prepared.

"Template" means that almost definitions

are static and only the part is replaced

dynamically.

3.1.2. HTTP POST/GET Request/Response from the phone to HTTP Server.

[HTTP POST/GET Request]

The phone sends HTTP POST/GET request to HTTP Server as the result of “SendRequest" Action.

The format of HTTP POST/GET request is same as ordinary HTTP POST/GET request.

<Note1>

There are some values reserved values by the phone.

These values are automatically replaced by the phone and sent to HTTP Server.

Correct values of XML components on GUI. (Note1)

When definition of "Action" is "SendRequest".

Send all pairs of name and value to HTTP Server

specified with URL by using HTTP.

Format each name and value with URL encode.

[HTTP POST/GET Response]

TGP/HDV receives HTTP response including XML data from HTTP Server.

Receive HTTP response header.

Check the HTTP result code.

Receive HTTP response content.

200 OK

Other

Display GUI.

3.2. Push XML Data

3.2.1. Push Mechanism

Push may be kicked by PC Client which operator uses.

Push is achieved with 2 steps.

First step is to send trigger.

Second step is to get XML data. (This is same as the description of "Get XML data".)

HTTP Server sends a Link XML data as Trigger, which describes the behavior of TGP/HDV, to "Push Port"

by using HTTP POST.

When TGP/HDV catches the Link XML data, TGP/HDV executes Push Event process.

HTTP Server

PC Client (Operator)

1. Send Trigger

2. Get XML Data

HDV

TGP

3.2.2. Push Event Process

When considering from the phone side, this process is separated to 2 phases. (Processing Trigger and

Processing Service Content.)

This phase processes a trigger.

A TCP/IP connection is kept during following flow.

Listen on Push Port.

Receive Link XML data.

Check Link XML data.

Send error HTTP response

("400 Bad Request")

Send HTTP response header (200 OK).

Download main XML data.

<Note1>

These sequences are same

as the sequences

"Get XML data".

HTTP GET /request.cgi

access from server with Link

XML data.

Specified by XML_HTTPD_PORT.

Default: 6666

3.3. HTTP Sequence Example

The followings are some HTTP sequence example for reference. *For example: KX-HDV330

3.3.1. GET XML method

GET /hdv330/pana.xml?tb=ABC4567890ABC4567890ABCD HTTP/1.0

User-Agent: Panasonic_KX-HDV330/01.066 (0080f0xxxxxx)

Host: 192.168.0.100:80

HTTP/1.1 200 OK

Server: Microsoft-IIS/5.1

X-Powered-By: ASP.NET

Date: Fri, 16 Dec 2011 01:46:29 GMT

Content-Type: text/xml

Accept-Ranges: bytes

Last-Modified: Thu, 01 Dec 2011 07:21:33 GMT

ETag: "902242daf9afcc1:1023"

Content-Length: 433

<?xml version="1.0" encoding="utf-8"?>

<ppxml xmlns="http://panasonic/sip_screen"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://panasonic/sip_screen sip_screen.xsd">

<PictureBox name="PictureBox1" left="0" top="27" width="120" height="55"

source="http://192.168.0.100/hdv330/pana4.bmp" />

</Components>

</Screen>

</ppxml>

Note. <Except for HDV330/430>

<PictureBox name="PictureBox1" left="0" top="0" width="120" height="55"

source="http://192.168.0.100/hdv330/pana4.bmp" />

3.3.2. Push method

GET /Request.cgi HTTP/1.1

HOST: 192.168.0.115

Content-Type: text/xml

Content-Length: 305

<?xml version="1.0" encoding="utf-8"?>

<ppxml xmlns="http://panasonic/sip_menu"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://panasonic/sip_menu sip_menu.xsd">

</Trigger>

</ppxml>

HTTP/1.1 200 OK

Connection: Keep-Alive

Content-type:text/html; charset=UTF-8

Status:200

Content-length: 0

GET /HDV330/Page1.xml HTTP/1.0

User-Agent: Panasonic_KX-HDV330/01.023 (0080f0xxxxxx)

Host: 192.168.0.111:80

HTTP/1.1 200 OK

Fixed file name for push request.

Access to the port 6666

of the phone from server.

Link XML data

200 OK if accepted.

Get main XML data from

the phone to the server.

Get XML data from the

phone to the server.

Acquired XML data

200 OK if accepted.

Server: Microsoft-IIS/5.1

X-Powered-By: ASP.NET

Date: Thu, 13 Oct 2011 01:31:59 GMT

Content-Type: text/xml

Accept-Ranges: bytes

Last-Modified: Thu, 13 Oct 2011 01:23:31 GMT

ETag: "50c144b84689cc1:fc1"

Content-Length: 359

<?xml version="1.0" encoding="utf-8"?>

<ppxml xmlns="http://panasonic/sip_screen"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://panasonic/sip_screen sip_screen.xsd">

</Components>

</Screen>

</ppxml>

3.3.3. GET PhoneBook method

GET

/DirectoryAccessForLDAP/get_directory.aspx?max_rec=20&base=dc%3Dmy-domain%2Cdc%3

Dcom&name=T&userid=cn%3Dmanager%2Cdc%3Dmy-domain%2Cdc%3Dcm&userpass=secret

HTTP/1.0

User-Agent: Panasonic_KX-HDV330/01.070 (0080f0xxxxxx)

Host: 192.168.70.36:80

HTTP/1.1 200 OK

Server: Microsoft-IIS/5.1

Date: Wed, 21 Dec 2011 07:52:46 GMT

X-Powered-By: ASP.NET

X-AspNet-Version: 2.0.50727

Cache-Control: private

Content-Type: text/xml; charset=utf-8

Content-Length: 1742

<?xml version="1.0" encoding="utf-8"?><ppxml xmlns="http://panasonic/sip_phone"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://panasonic/sip_phone_directory

sip_phone_phonebook.xsd"><Screen version="2.0”><PhoneBook version="2.0”><Personnel

id="1"><Name>Test User01</Name><Ruby>Test01</Ruby><PhoneNums><PhoneNum

type="ext">6789</PhoneNum><PhoneNum type="company">382719</PhoneNum><PhoneNum

type="mobile">928378</PhoneNum><PhoneNum type="home">6789</PhoneNum><PhoneNum

type="etc">382719</PhoneNum></PhoneNums></Personnel><Personnel id="2"><Name>Test

User02</Name><Ruby>Test02</Ruby><PhoneNums><PhoneNum

type="ext">6058</PhoneNum><PhoneNum type="company">777058</PhoneNum><PhoneNum

type="mobile">888012</PhoneNum><PhoneNum type="home">6058</PhoneNum><PhoneNum

type="etc">777058</PhoneNum></PhoneNums></Personnel><Personnel id="3"><Name>Test

User03</Name><Ruby>Test03</Ruby><PhoneNums><PhoneNum

type="ext">6001</PhoneNum><PhoneNum type="company">777001</PhoneNum><PhoneNum

type="mobile">888001</PhoneNum><PhoneNum type="home">6001</PhoneNum><PhoneNum

type="etc">777001</PhoneNum></PhoneNums></Personnel><Personnel id="4"><Name>Test

user04</Name><Ruby>Test04</Ruby><PhoneNums><PhoneNum

type="ext">6053</PhoneNum><PhoneNum type="company">777053</PhoneNum><PhoneNum

type="mobile">888053</PhoneNum><PhoneNum type="home">6053</PhoneNum><PhoneNum

type="etc">777053</PhoneNum></PhoneNums></Personnel><Personnel id="5"><Name>Test

user05</Name><Ruby>Test05</Ruby><PhoneNums><PhoneNum

type="ext">6002</PhoneNum><PhoneNum type="company">777002</PhoneNum><PhoneNum

type="mobile">888002</PhoneNum><PhoneNum type="home">6002</PhoneNum><PhoneNum

type="etc">777002</PhoneNum></PhoneNums></Personnel></PhoneBook></Screen></ppxml

Acquired XML data

Get XML data from the

phone to the phonebook

server.

e.g. ) searching “T”

Acquired XML data

200 OK if accepted.

4. Phone Configuration and Operation

4.1. Web User Interface Setting List – Configuration Parameter

Network * For example: KX-HDV230

Menu Item

Section Title

Setting

Configuration Parameter

XML Application

Settings

XML Application

Enable XMLAPP

XMLAPP_ENABLE

User ID

XMLAPP_USERID

Password

XMLAPP_USERPASS

Local XML Port

XML_HTTPD_PORT

Bootup URL

(*2)

XMLAPP_START_URL

Initial URL

(*2)

XMLAPP_INITIAL_URL

Incoming Call URL

(*2)

XMLAPP_INCOMING_URL

Talking URL

(*2)

XMLAPP_TALKING_URL

Making Call URL

(*2)

XMLAPP_MAKECALL_URL

Call Log URL

(*2)

XMLAPP_CALLLOG_URL

Idling URL

(*2)

XMLAPP_IDLING_URL

Enable FF Key

(*2)

XMLAPP_FFKEY_ENABLE

Shortcut Key Settings

(*1)

Soft Key A(Left)

XML_INITIATE_KEY_SOFT1

Soft Key B(Center)

XML_INITIATE_KEY_SOFT2

Soft Key C(Right)

XML_INITIATE_KEY_SOFT3

XML Phonebook

LDAP URL

XMLAPP_LDAP_URL

User ID

XMLAPP_LDAP_USERID

Password

XMLAPP_LDAP_USERPASS

Max Hits

XMLAPP_LDAP_MAXRECORD

Note. (*1) HDV330/430 doesn’t support Shortcut Key Settings, since there are no Initiation Key.

(*2) Supported only HDV130/230/330/430.

4.2. Common Configuration and Operation

It is necessary to set this configuration parameter for activating XML application feature.

4.2.1. Configuration Parameter

Configuration parameters are as follows.

Configuration Parameter

Description

Format

Value

Range

Default

Value

XMLAPP_ENABLE

Set “Y” for activating XML application

feature.

Boolean

Y/N

XMLAPP_USERID

Specify user ID for XML server

authentication

String

Max. 128

characters

Empty

String

XMLAPP_USERPASS

Specify the Password for XML server

authentication

String

Max. 128

characters

Empty

String

XML_HTTPD_PORT

Specify listen port number for receiving

XML push event from XML server.

Integer

1 to 65535

6666

XML_ERROR_INFORMATION

Set “N” in order to inhibit displaying error

information on the phone’s LCD.

Boolean

Y/N

If it is necessary to access secure to the network phonebook server, it is able to use HTTPS protocol instead

of HTTP.

For that, it is necessary to compose the following parameters in the addition. (C.f. Admin Guide)

Configuration Parameter

Description

Format

Value

Range

Default

Value

HTTP_SSL_VERIFY

Specifies whether to enable the

verification of the root certificate.

- 0 (No verification)

- 1 (Simple verification)

- 2 (Precise verification

Integer

0~2

CFG_ROOT_CERTIFICATE_PATH

Specifies the URI of the root certificate.

String

Max.384

characters

Empty

String

4.2.2. Remarks of Softkey and FFkey Operation (*1)

When XML contents are displayed, Softkeys and FFkeys are controlled according to its XML definition.

It means default Softkey and FFkey for phone use cannot be used in the XML contents.

It is able to exit from XML contents by using following methods.

- Press [Cancel] button.

- Off hook the handset

- [SP-PHONE] On.

Note. (*1) HDV330/430 are supported only FFKey Operation.TGP600 and HDV100 are not supported.

Configuration Parameter

Description

Format

Value

Range

Default

Value

XML_SOFT_KEY_NAMEx

x=1-3

Specifies the name of Soft Key A/B/C

assigned XML application.

String

Max.16

characters

Empty

String

4.3. Initiation methods of XML application (*1)

The phone has six types of methods to access XML contents as follows.

- Phone Status (4.3.1)

- Phonebook menu (4.3.2)

- Application menu (4.3.3)

- Call log key (4.3.4)

- Initiation key (4.3.5)

- Redial key(4.3.6)

Please refer to each section for more detail.

Note. (*1) Supported only HDV130/230/330/430.

4.3.1. Acquiring XML data corresponding to the Phone Status - Configuration

It is able to acquire specified XML data linked to the status of the phone.

For example, company logo bitmap is display when the phone goes idle status.

Operations depend on the each XML data.

4.3.1.1. Configuration Parameter

Configuration parameters are as follows.

Configuration Parameter

Description

Format

Value

Range

Default

Value

XMLAPP_START_URL

Specify the XML URL to acquire when the

phone starts up.

It is useful for displaying startup logo.

This is only once when the phone starts.

String

Max. 256

characters

Empty

String

XMLAPP_INITIAL_URL

Specifies the URL that is accessed when

the application is started from the unit's

menu, to check for XML data.

XMLAPP_INCOMING_URL

Specify the XML URL to acquire when the

phone receives a call.

XMLAPP_TALKING_URL

Specify the XML URL to acquire when the

phone goes talking.

XMLAPP_MAKECALL_URL

Specify the XML URL to acquire when the

phone goes off-hook.

XMLAPP_CALLLOG_URL

Specifies the URL that is accessed when

the call log is accessed, to check for XML

data.

XMLAPP_IDLING_URL

Specify the XML URL to acquire when the

phone is idle state.

It is useful for displaying company logo in

the idle state.

XMLAPP_FFKEY_ENABLE

Specifies whether to use the XML

application or operate normal telephone

when the corresponding button is

pressed. (FF Key and Page Key)

Y: XML Mode

N: Normal Telephone Mode

Boolean

Y/N

XMLAPP_STATUSBAR_ENABLE

(*1)

Selects whether to enable or disable

“Icon, Text, Clock on the Status Bar XML

application feature.

Y: Enable Display “Icon, Text, Clock”

on Status Bar

N: Disable

Boolean

Y/N

(*)It is not possible to notify internal variables, such as originating call number, to XML server dynamically.

Note. (*1) Only HDV330/430 supports the “XMLAPP_STATUSBAR_ENABLE”

Page is loading ...

Panasonic TGP600 Developer's Manual

Panasonic TGP600 Developer's Manual

Panasonic TGP600 Developer's Manual

Related papers

Other documents