Similar documents
Call Detail Record Access Service Part No R01

CONTRACT MODEL IPONZ DESIGN SERVICE VERSION 2. Author: Foster Moore Date: 20 September 2011 Document Version: 1.7

Qualys API Limits. July 10, Overview. API Control Settings. Implementation

File Transfer Service (Batch SOAP) User Guide. A Guide to Submitting batches through emedny FTS

Lecture Notes course Software Development of Web Services

quick documentation Die Parameter der Installation sind in diesem Artikel zu finden:

Jetzt können Sie den Befehl 'nsradmin' auch für diverse Check-Operationen verwenden!

Software / FileMaker / Plug-Ins Mailit 6 for FileMaker 10-13

Table of Contents. Open-Xchange Authentication & Session Handling. 1.Introduction...3

Web-Programmierung (WPR)

JASPERREPORTS SERVER WEB SERVICES GUIDE

Windows Phone 8 Enterprise Device Management Protocol

Freight Tracking Web Service Implementation Guide

GET /FB/index.html HTTP/1.1 Host: lmi32.cnam.fr

HTTP Protocol. Bartosz Walter

Windows Phone 8.1 Enterprise Device Management Protocol

reference: HTTP: The Definitive Guide by David Gourley and Brian Totty (O Reilly, 2002)

Usage of Evaluate Client Certificate with SSL support in Mediator and CentraSite

AIRTEL INDIA OPEN API. Application Developer Guide for OAuth2 Authentication and Authorization. Document Version 1.1

HTTP - METHODS. Same as GET, but transfers the status line and header section only.

"Understanding Devices Profile for Web Services, Web Services Discovery, and SOAPover-UDP"

How To Connect A Webadmin To A Powerpoint (Utm) From A Usb To A Usb (Net) Or Ipa (Netlan) Device (Netbook) From Your Computer Or Ipam (Netnet

Welcome to the online application portal of the University of Hamburg

Microsoft Certified IT Professional (MCITP) MCTS: Windows 7, Configuration ( )

Quick Start Guide UTM 110/120

Multipurpsoe Business Partner Certificates Guideline for the Business Partner

Tunneling QuickTime RTSP and RTP over HTTP. Relationship to RTSP/RTP

GlassFish OpenSSO CAC Authentication Deployment Configuration Guide

VoIP LAB. 陳 懷 恩 博 士 助 理 教 授 兼 所 長 國 立 宜 蘭 大 學 資 訊 工 程 研 究 所 TEL: # 255

Secure Password-Based Authenticated Key Exchange. for Web Services

Abusing the Internet of Things. BLACKOUTS. FREAKOUTS. AND

AJAX SSL- Wizard Reference

B2B Appointment Booking Specification

Cisco TelePresence Content Server

Installing BankID Security Application in corporate environments

Information Extraction Art of Testing Network Peripheral Devices

Installing BankID Security Application in corporate environments

Online Application Guide 2013

Windows 8.1 Enterprise Device Management Protocol

IAC-BOX Network Integration. IAC-BOX Network Integration IACBOX.COM. Version English

NetCom SMS Bedrift API Technical Documentation

Qualys API V1. User Guide. Version 8.6

TIBCO JASPERREPORTS SERVER WEB SERVICES GUIDE

Vodia PBX RESTful API (v2.0)

Web Browser Settings for MOGADOC Version

HOST EUROPE CLOUD STORAGE REST API DEVELOPER REFERENCE

THE PROXY SERVER 1 1 PURPOSE 3 2 USAGE EXAMPLES 4 3 STARTING THE PROXY SERVER 5 4 READING THE LOG 6

What is Distributed Annotation System?

Penetration Testing Corporate Collaboration Portals. Giorgio Fedon, Co-Founder at Minded Security

Web Services in Eclipse. Sistemi Informativi Aziendali A.A. 2012/2013

QUICK START BALANCE AUDIO INTERFACE QUICK START DÉMARRAGE RAPIDE KURZANLEITUNG

Playing with Web Application Firewalls

POSTGRESQL, A PLATFORM FOR MULTIPLE SOURCES DATA RETRIEVAL

Internet Technologies Internet Protocols and Services

MatrixSSL Getting Started

HTTP Caching & Cache-Busting for Content Publishers

Designing and Implementing a Server Infrastructure MOC 20413

vshield API Programming Guide vshield Manager 4.1 vshield App 1.0 vshield Edge 1.0 vshield Endpoint 1.0

ipay Checkout API (IPC API)

Upgrading Your Skills to MCSA Windows Server 2012 MOC 20417

Technische Alternative elektronische Steuerungsgerätegesellschaft mbh. A-3872 Amaliendorf, Langestr. 124 Tel +43 (0)

What is SOAP MTOM? How it works?

Hacking SAP BusinessObjects

Upgrade-Preisliste. Upgrade Price List

Basic Xten Pro Configuration

J2EE-Application Server

Web. Services. Web Technologies. Today. Web. Technologies. Internet WWW. Protocols TCP/IP HTTP. Apache. Next Time. Lecture # Apache.

Deployment Guide. Caching (Static & Dynamic) Deployment Guide. A Step-by-Step Technical Guide

Security-Assessment.com White Paper Leveraging XSRF with Apache Web Server Compatibility with older browser feature and Java Applet

Developer Guide: REST API Applications. SAP Mobile Platform 2.3

CloudOYE CDN USER MANUAL

Search Engines Chapter 2 Architecture Felix Naumann

DV4 - Citrix CloudGateway: Access and control Windows, SaaS and web applications. Systems Engineer, Citrix Systems GmbH

Erfolgreiche Zusammenarbeit:

The Hyper-Text Transfer Protocol (HTTP)

ASV Scan Report Vulnerability Details. UserVoice Inc.

Brauche neues Power Supply

DEERFIELD.COM. DNS2Go Update API. DNS2Go Update API

RPC over XML. Web services with Java. How to install it? Reference implementation. Setting the environment variables. Preparing the system

Testing Work Group. Document Status: Project: WS-I Monitor Tool Functional Specification [MonitorSpecification.doc]

Grandstream Networks, Inc. GXP2130/2140/2160 Auto-configuration Plug and Play

Dev Guide for Encrypted Swipe

Data Sheet. Ihr Spezialist für Mess- und Prüfgeräte

Real-Time Connectivity Specifications For. 270/271 and 276/277 Inquiry Transactions. United Concordia Dental (UCD)

O D B C / R O C K E T ( B S / O S D ) V 5. 0 F O R S E S A M / S Q L D A T E : F E B R U A R Y *2 R E L E A S E N O T I C E

Open Text Social Media. Actual Status, Strategy and Roadmap

Internet Technologies 4-http. F. Ricci 2010/2011

Symantec Backup Exec (TM) 13 Installation Log

SAP Sourcing/CLM Webcast Query & User/Contact Maintenance Web Service

Architecture Flaws Internet Security Systems. All rights reserved. Contents are property of Internet Security Systems.

Nuance Mobile Developer Program. HTTP Services for Nuance Mobile Developer Program Clients

Transcription:

Request of end customer against AP AP forwards request to OTACS Aborted with failure code Validate the request Is request syntactically correct? No Send failure code to AP Yes Validate authentication pin and check it s time slot Yes Is authentication request? Is valid request? No No No Is operator ID given? No Determine operator ID by phone number Yes Ja Yes Is the mobile supporting this configuration type? No Is the mobile supporting manual configuration? Yes Load configuration data Save configuration data Is request with authentication pin? Yes Send message with generated authentication pin to mobile Yes No Create and send configuration message to mobile Send status code and perhaps the configuration parameters and the manual text End customer has received the configuration AP has received the response

¹) POST /otacs/services/otacssoap HTTP/1.0 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.3 Host: localhost:5160 Cache-Control: no-cache Pragma: no-cache SOAPAction: "http://wotas.de.wm/webservice/configurewap" Content-Length: 582 Authorization: Basic dxnlcm5hbwu6cgfzc3dvcmq= <?xml version="1.0" encoding="utf-8"?> <configurewap xmlns="http://wotas.de.wm/webservice"> <request xmlns=""> <languageid>2</languageid> <mpnr>491722345678</mpnr> <mptype>4</mptype> <tac>351972</tac> <bearer>1</bearer> <operatorid>0</operatorid> <providerid>0</providerid> <startpage>wap://superwap.de/portal/</startpage> <startpagename>superwap</startpagename> <displayname>superwap wap</displayname> <authorise>false</authorise> <billingid>1</billingid> <countsms>true</countsms> </request> </configurewap>

HTTP/1.1 200 OK Date: Mon, 07 May 2007 14:58:22 GMT Server: Jetty/4.2.17 (Linux/2.4.20-4GB i386 java/1.5.0_09) <configurewapresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <id>871</id> <text>sie erhalten eine Konfigurationsnachricht für Ihr Handy. Wählen Sie die neue Nachricht "Automatische Konfiguration". Bitte hinzufügen des Kontos bestätigen. Bitte prüfen Sie, ob die neue Einstellung als Standard festgelegt ist: Falls nicht, scrollen Sie zur Einstellung und legen Sie diese als Standard fest. Falls angefordert, können Sie einen neuen Favoriten hinzufügen. Wählen Sie "Yes". </text> <parameterlist/> <amountsms>2</amountsms> </response> </configurewapresponse>

¹)

POST /otacs/services/otacssoap HTTP/1.0 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.3 Host: localhost:5160 Cache-Control: no-cache Pragma: no-cache SOAPAction: "http://wotas.de.wm/webservice/configuremms" Content-Length: 511 Authorization: Basic dxnlcm5hbwu6cgfzc3dvcmq= <?xml version="1.0" encoding="utf-8"?> <configuremms xmlns="http://wotas.de.wm/webservice"> <request xmlns=""> <languageid>2</languageid> <mpnr>491722345678</mpnr> <mptype>31</mptype> <tac>35292800</tac> <operatorid>0</operatorid> <providerid>0</providerid> <displayname>mms</displayname> <authorise>false</authorise> <billingid>2</billingid> <countsms>true</countsms> </request> </configuremms> HTTP/1.1 200 OK Date: Mon, 07 May 2007 15:16:26 GMT Server: Jetty/4.2.17 (Linux/2.4.20-4GB i386 java/1.5.0_09) <configuremmsresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <id>872</id> <text>sie erhalten eine Konfigurationsnachricht für Ihr Handy. Speichern Sie Ihre Auswahl. Falls erforderlich, ersetzen Sie die vorhandenen Einstellungen. Falls erforderlich, aktivieren Sie die Einstellung. </text> <parameterlist/> <amountsms>2</amountsms> </response> </configuremmsresponse>

¹)

POST /otacs/services/otacssoap HTTP/1.0 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.3 Host: localhost:5160 Cache-Control: no-cache Pragma: no-cache SOAPAction: "http://wotas.de.wm/webservice/configureinternet" Content-Length: 544 Authorization: Basic dxnlcm5hbwu6cgfzc3dvcmq= <?xml version="1.0" encoding="utf-8"?> <configureinternet xmlns="http://wotas.de.wm/webservice"> <request xmlns=""> <languageid>2</languageid> <mpnr>491722345678</mpnr> <mptype>31</mptype> <tac>35292800</tac> <bearer>1</bearer> <operatorid>0</operatorid> <providerid>0</providerid> <startpage>http://superwap.de/portal</startpage> <startpagename>superwap</startpagename> <displayname>superwap inet</displayname> <authorise>false</authorise> <billingid>3</billingid> <countsms>true</countsms> </request> </configureinternet>

HTTP/1.1 200 OK Date: Mon, 07 May 2007 15:20:20 GMT Server: Jetty/4.2.17 (Linux/2.4.20-4GB i386 java/1.5.0_09) <configureinternetresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <id>878</id> <text>sie erhalten eine Konfigurationsnachricht für Ihr Handy. Speichern Sie Ihre Auswahl. Falls erforderlich, aktivieren Sie die Einstellung. Falls erforderlich, ersetzen Sie die vorhandenen Einstellungen. Drücken Sie "Nein", um die Einstellung zu aktivieren. </text> <parameterlist/> <amountsms>2</amountsms> </response> </configureinternetresponse>

¹) Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.3 Host: localhost:5160 Cache-Control: no-cache Pragma: no-cache SOAPAction: "http://wotas.de.wm/webservice/configureemail" Content-Length: 667 Authorization: Basic dxnlcm5hbwu6cgfzc3dvcmq= <?xml version="1.0" encoding="utf-8"?> <configureemail xmlns="http://wotas.de.wm/webservice"> <request xmlns=""> <languageid>2</languageid> <mpnr>491722345678</mpnr> <mptype>1525</mptype> <tac>35316902</tac> <email>test@email.com</email> <username>username</username> <userpwd>password</userpwd> <incomingmailserver>pop3.mail.com</incomingmailserver> <incomingmailserverport>110</incomingmailserverport> <outgoingmailserver>smtp.mail.com</outgoingmailserver> <outgoingmailserverport>25</outgoingmailserverport> <operatorid>0</operatorid> <providerid>0</providerid> <displayname>email account</displayname> <authorise>false</authorise> <billingid>4</billingid> <inprotocolauth>true</inprotocolauth> <outprotocolauth>false</outprotocolauth> <inprotocoltls>false</inprotocoltls> <outprotocoltls>false</outprotocoltls> <countsms>true</countsms> </request> </configureemail>

HTTP/1.1 200 OK Date: Mon, 07 May 2007 15:24:47 GMT Server: Jetty/4.2.17 (Linux/2.4.20-4GB i386 java/1.5.0_09) <configureemailresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <id>883</id> <text>sie erhalten eine Konfigurationsnachricht für Ihr Handy. Bestätigen Sie den nächsten Schritt, falls angefordert. Geben Sie den PIN Code 1234 ein und bestätigen Sie die Eingabe. Bestätigen Sie den nächsten Schritt, falls angefordert. </text> <pin>1234</pin> <parameterlist/> </response> </configureemailresponse>

¹)

POST /otacs/services/otacssoap HTTP/1.0 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.3 Host: localhost:5160 Cache-Control: no-cache Pragma: no-cache SOAPAction: "http://wotas.de.wm/webservice/configurebookmark" Content-Length: 557 Authorization: Basic dxnlcm5hbwu6cgfzc3dvcmq= <?xml version="1.0" encoding="utf-8"?> <configurebookmark xmlns="http://wotas.de.wm/webservice"> <request xmlns=""> <languageid>2</languageid> <mpnr>491722345678</mpnr> <mptype>716</mptype> <tac>35170701</tac> <linkname>whatever MOBILE</linkName> <linkaddress>http://www.whatevermobile.com</linkaddress> <authorise>false</authorise> <billingid>5</billingid> <countsms>true</countsms> </request> </configurebookmark>

HTTP/1.1 200 OK Date: Mon, 07 May 2007 15:29:29 GMT Server: Jetty/4.2.17 (Linux/2.4.20-4GB i386 java/1.5.0_09) <?xml version="1.0" encoding="utf-8"?> <configurebookmarkresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <id>1062</id> <text> In Kürze erhalten Sie die gewünschten Zugangsinformationen direkt auf Ihr Mobiltelefon. Zum Einstellen folgen Sie bitte den Anweisungen auf dem Bildschirm Ihres Mobiltelefons. </text> <parameterlist /> <amountsms>3</amountsms> </response> </configurebookmarkresponse>

¹) POST /otacs/services/otacssoap HTTP/1.0 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.3 Host: localhost:5160 Cache-Control: no-cache Pragma: no-cache SOAPAction: "http://wotas.de.wm/webservice/configurepushtotalk" Content-Length: 590 Authorization: Basic dxnlcm5hbwu6cgfzc3dvcmq= <?xml version="1.0" encoding="utf-8"?> <configurepushtotalk xmlns="http://wotas.de.wm/webservice"> <request xmlns=""> <languageid>2</languageid> <mpnr>491722345678</mpnr> <mptype>716</mptype> <tac>35170701</tac> <username>username</username> <userpwd>password</userpwd> <operatorid>0</operatorid> <providerid>0</providerid> <displayname>push-to-talk</displayname> <authorise>false</authorise> <billingid>6</billingid> <countsms>true</countsms> </request> </configurepushtotalk>

HTTP/1.1 200 OK Date: Mon, 07 May 2007 15:32:50 GMT Server: Jetty/4.2.17 (Linux/2.4.20-4GB i386 java/1.5.0_09) <?xml version="1.0" encoding="utf-8"?> <configurepushtotalkresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <id>1063</id> <text> In Kürze erhalten Sie die gewünschten Zugangsinformationen direkt auf Ihr Mobiltelefon. Zum Einstellen folgen Sie bitte den Anweisungen auf dem Bildschirm Ihres Mobiltelefons. </text> <parameterlist /> <amountsms>3</amountsms> </response> </configurepushtotalkresponse>

¹) POST /otacs/services/otacssoap HTTP/1.0 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.3 Host: localhost:5160 Cache-Control: no-cache Pragma: no-cache SOAPAction: "http://wotas.de.wm/webservice/configurestreaming" Content-Length: 529 Authorization: Basic dxnlcm5hbwu6cgfzc3dvcmq= <?xml version="1.0" encoding="utf-8"?> <configurestreaming xmlns="http://wotas.de.wm/webservice"> <request xmlns=""> <languageid>2</languageid> <mpnr>491722345678</mpnr> <mptype>716</mptype> <tac>35170701</tac> <operatorid>0</operatorid> <providerid>0</providerid> <displayname>streaming</displayname> <authorise>false</authorise> <billingid>7</billingid> <countsms>true</countsms> </request> </configurestreaming>

HTTP/1.1 200 OK Date: Mon, 07 May 2007 15:36:56 GMT Server: Jetty/4.2.17 (Linux/2.4.20-4GB i386 java/1.5.0_09) <?xml version="1.0" encoding="utf-8"?> <configurestreamingresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <id>1064</id> <text></text> <parameterlist /> <amountsms>3</amountsms> </response> </configurestreamingresponse>

¹) POST /otacs/services/otacssoap HTTP/1.0 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.3 Host: localhost:5160 Cache-Control: no-cache Pragma: no-cache SOAPAction: "http://wotas.de.wm/webservice/configuresyncml" Content-Length: 666 Authorization: Basic dxnlcm5hbwu6cgfzc3dvcmq= <?xml version="1.0" encoding="utf-8"?> <configuresyncml xmlns="http://wotas.de.wm/webservice"> <request xmlns=""> <languageid>2</languageid> <mpnr>491722345678</mpnr> <mptype>716</mptype> <tac>35170701</tac> <SyncMLAddress>http://sync.xyz.com</SyncMLAddress> <username>username</username> <userpwd>password</userpwd> <displayname>syncml</displayname> <authorise>false</authorise> <billingid>8</billingid> <countsms>true</countsms> </request> </configuresyncml>

HTTP/1.1 200 OK Date: Tue, 08 May 2007 08:26:39 GMT Server: Jetty/4.2.17 (Linux/2.4.20-4GB i386 java/1.5.0_09) <?xml version="1.0" encoding="utf-8"?> <configuresyncmlresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <id>1065</id> <text></text> <pin>9728</pin> <parameterlist /> <amountsms>3</amountsms> </response> </configuresyncmlresponse> 1

HTTP/1.1 200 OK Date: Mon, 07 May 2007 15:43:50 GMT Server: Jetty/4.2.17 (Linux/2.4.20-4GB i386 java/1.5.0_09) <?xml version="1.0" encoding="utf-8"?> <configurewapresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <id>1055</id> <parameterlist> <parameter> <name>profilename</name> <value>t-d1 WAP</value> </parameter> <parameter> <name>apn</name> <value>wap.t-d1.de</value> </parameter> <parameter> <name>password</name> <value>wap</value> </parameter> <parameter> <name>proxyip</name> <value>193.254.160.002</value> </parameter> <parameter> <name>proxyport</name> <value>9201</value> </parameter> <parameter> <name>username</name> <value>t-d1</value> </parameter> </parameterlist> </response> </configurewapresponse>

HTTP/1.1 200 OK Date: Mon, 07 May 2007 15:47:05 GMT Server: Jetty/4.2.17 (Linux/2.4.20-4GB i386 java/1.5.0_09) <?xml version="1.0" encoding="utf-8"?> <configurewapresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <id>1056</id> <text> In Kürze erhalten Sie die gewünschten Zugangsinformationen direkt auf Ihr Mobiltelefon. Zum Einstellen folgen Sie bitte den Anweisungen auf dem Bildschirm Ihres Mobiltelefons. </text> <pin>7171</pin> <parameterlist /> </response> </configurewapresponse> HTTP/1.1 200 OK Date: Mon, 07 May 2007 15:51:15 GMT Server: Jetty/4.2.17 (Linux/2.4.20-4GB i386 java/1.5.0_09) <?xml version="1.0" encoding="utf-8"?> <configurewapresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <id>1057</id> <parameterlist /> </response> </configurewapresponse>

POST /otacs/services/otacssoap HTTP/1.0 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.3 Host: localhost:5160 Cache-Control: no-cache Pragma: no-cache SOAPAction: "http://wotas.de.wm/webservice/getauthorisation" Content-Length: 383 Authorization: Basic dxnlcm5hbwu6cgfzc3dvcmq= <?xml version="1.0" encoding="utf-8"?> <getauthorisation xmlns="http://wotas.de.wm/webservice"> <request xmlns=""> <id>2395</id> <authenticationpin>8713</authenticationpin> </request> </getauthorisation>

HTTP/1.1 200 OK Date: Mon, 07 May 2007 15:57:39 GMT Server: Jetty/4.2.17 (Linux/2.4.20-4GB i386 java/1.5.0_09) <?xml version="1.0" encoding="utf-8"?> <getauthorisationresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <id>1066</id> </response> </getauthorisationresponse>

false false POST /otacs/services/otacssoap HTTP/1.0 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.3 Host: localhost:5160 Cache-Control: no-cache Pragma: no-cache SOAPAction: "http://wotas.de.wm/webservice/getmobilephonelist" Content-Length: 320 Authorization: Basic dxnlcm5hbwu6cgfzc3dvcmq= <?xml version=1.0" encoding="utf-8"?> <web:getmobilephonelist> <request> <!--Optional:--> <showtacs>true</showtacs> </request> </web:getmobilephonelist>

2 2 Newer mobiles can provide the input of a pin by the user to accept the incoming configuration, but some of them don t support this completely. Mobile phones which support incoming configuration only partially are listed in table 16.

HTTP/1.1 200 OK Date: Mon, 07 May 2007 15:57:39 GMT Server: Jetty/4.2.17 (Linux/2.4.20-4GB i386 java/1.5.0_09) <?xml version="1.0" encoding="utf-8"?> <getmobilephonelistresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <mobilephonelist> <mobilephone> <id>716</id> <name>k800i</name> <taclist> <tac> <value>35170701</value> </tac> <tac> <value>35170801</value> </tac> <tac> <value>35342701</value> </tac> <tac> <value>35399601</value> </tac> <tac> <value>35427102</value> </tac>... </taclist> <producer>sony Ericsson</producer> <wapgprs>true</wapgprs> <wapgsmcsd>true</wapgsmcsd> <mms>true</mms> <email>true</email> <internetgprs>true</internetgprs> <internetgsmcsd>true</internetgsmcsd> <bookmark>true</bookmark> <streaming>true</streaming> <securitypin>true</securitypin> <pushtotalk>true</pushtotalk> <syncml>true</syncml> </mobilephone> </mobilephonelist> </response> </getmobilephonelistresponse>

POST /otacs/services/otacssoap HTTP/1.0 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.3 Host: localhost:5160 Cache-Control: no-cache Pragma: no-cache SOAPAction: "http://wotas.de.wm/webservice/getoperatorlist" Content-Length: 317 Authorization: Basic dxnlcm5hbwu6cgfzc3dvcmq= <?xml version="1.0" encoding="utf-8"?> <getoperatorlist xmlns="http://wotas.de.wm/webservice" />

HTTP/1.1 200 OK Date: Mon, 07 May 2007 15:57:39 GMT Server: Jetty/4.2.17 (Linux/2.4.20-4GB i386 java/1.5.0_09) <?xml version="1.0" encoding="utf-8"?> <getoperatorlistresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <operatorlist> <operator> <id>2</id> <name>vodafone D2</name> <country>germany - MNP</country> </operator> <operator> <id>3</id> <name>t-mobile Deutschland</name> <country>germany - MNP</country> </operator> <operator> <id>4</id> <name>e-plus</name> <country>germany - MNP</country> </operator> <operator> <id>8</id> <name>o2 (Germany)</name> <country>germany - MNP</country> </operator> </operatorlist> </response> </getoperatorlistresponse>

false false ¹) POST /otacs/services/otacssoap HTTP/1.1 Content-Type: text/xml;charset=utf-8 SOAPAction: "http://wotas.de.wm/webservice/getmobilephonepicture" Authorization: Basic dxnlcm5hbwu6cgfzc3dvcmq= User-Agent: Jakarta Commons-HttpClient/3.0.1 Host: localhost:5160 Content-Length: 335 <getmobilephonepicture> <request> <mptype>8</mptype> <tac>35666500</tac> <showtacs>true</showtacs> </request> </getmobilephonepicture>

HTTP/1.1 200 OK Date: Fri, 08 Aug 2008 09:23:57 GMT Server: Jetty/4.2.17 (Linux/2.6.18-4-xen-amd64 i386 java/1.5.0_09) Content-Type: multipart/related; type="text/xml"; start="<d3f87717b1c26807cd9a5ba5b4023ce8>"; boundary="---- =_Part_2_21722279.1218187438266" Transfer-Encoding: chunked 29b ------=_Part_2_21722279.1218187438266 Content-Type: text/xml; charset=utf-8 Content-Transfer-Encoding: binary Content-Id: <D3F87717B1C26807CD9A5BA5B4023CE8> <?xml version="1.0" encoding="utf-8"?> <getmobilephonepictureresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <mobilephonepicture> <id>8</id> <taclist> <tac> <value>35152500</value> </tac> <tac> <value>35154600</value> </tac> <tac> <value>35227201</value> </tac> <tac> <value>35227301</value> </tac>... </taclist> <name>6600</name> <producer>nokia</producer> </mobilephonepicture> </response> </getmobilephonepictureresponse> c16 ------=_Part_2_21722279.1218187438266 Content-Type: image/gif Content-Transfer-Encoding: binary Content-Id: <8.gif> GIF89a...other binary encoded data of the image... 2b

false false POST /otacs/services/otacssoap HTTP/1.1 Content-Type: text/xml;charset=utf-8 SOAPAction: "http://wotas.de.wm/webservice/getmobilephonepictures" Authorization: Basic dxnlcm5hbwu6cgfzc3dvcmq= User-Agent: Jakarta Commons-HttpClient/3.0.1 Host: localhost:5160 Content-Length: 232 <web:getmobilephonepictures> <request> <!--Optional:--> <showtacs>true</showtacs> </request> </web:getmobilephonepictures>

HTTP/1.1 200 OK Date: Fri, 08 Aug 2008 09:54:49 GMT Server:Jetty/4.2.17 (Linux/2.6.18-4-xen-amd64 i386 java/1.5.0_09) Content-Type: multipart/related; type="text/xml"; start="<bfb69e2f5a1e988853cf7bc41a58923e>";boundary="---- =_Part_4_30352443.1218189304137" Transfer-Encoding: chunked a5 ------=_Part_4_30352443.1218189304137 Content-Type: text/xml; charset=utf-8 Content-Transfer-Encoding: binary Content-Id: <BFB69E2F5A1E988853CF7BC41A58923E> 1df8 <?xml version="1.0" encoding="utf-8"?> <getmobilephonepicturesresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <mobilephonepictureslist> <mobilephonepicture> <id>1</id> <taclist> <tac> <value>350839</value> </tac> <tac> <value>350889</value> </tac> <tac> <value>350890</value> </tac>... </taclist> <name>3410</name> <producer>nokia</producer> </mobilephonepicture> </mobilephonepictureslist> </response> </getmobilephonepicturesresponse> e39 ------=_Part_4_30352443.1218189304137 Content-Type: image/gif Content-Transfer-Encoding: binary Content-Id: <1.gif> GIF89a... other data of the binary encoded image... 1b7a

POST /otacs/services/otacssoap HTTP/1.0 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.3 Host: localhost:5160 Cache-Control: no-cache Pragma: no-cache SOAPAction: "http://wotas.de.wm/webservice/getoperatorproviderlist" Content-Length: 317 Authorization: Basic dxnlcm5hbwu6cgfzc3dvcmq= <?xml version="1.0" encoding="utf-8"?> < getoperatorproviderlist xmlns="http://wotas.de.wm/webservice" />

HTTP/1.1 200 OK Date: Mon, 07 May 2007 15:57:39 GMT Server: Jetty/4.2.17 (Linux/2.4.20-4GB i386 java/1.5.0_09) <?xml version="1.0" encoding="utf-8"?> <getoperatorproviderlistresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <operatorproviderlist> <operatorprovider> <operatorid>4</operatorid> <operatorname>e-plus</operatorname> <providerid>0</providerid> <providername>no provider</providername> <country>germany - MNP</country> <wapgprs>true</wapgprs> <wapgsmcsd>true</wapgsmcsd> <mms>true</mms> <email>true</email> <internetgprs>true</internetgprs> <internetgsmcsd>true</internetgsmcsd> <pushtotalk>false</pushtotalk> <streaming>false</streaming> </operatorprovider> <operatorprovider> <operatorid>3</operatorid> <operatorname>t-mobile Deutschland</operatorName> <providerid>2</providerid> <providername>medion Mobile</providerName> <country>germany - MNP</country> <wapgprs>true</wapgprs> <wapgsmcsd>false</wapgsmcsd> <mms>false</mms> <email>false</email> <internetgprs>false</internetgprs> <internetgsmcsd>false</internetgsmcsd> <pushtotalk>false</pushtotalk> <streaming>false</streaming> </operatorprovider> </operatorproviderlist> </response> </getoperatorproviderlistresponse>

POST /otacs/services/otacssoap HTTP/1.1 Content-Type: text/xml;charset=utf-8 SOAPAction: "http://wotas.de.wm/webservice/getmanufacturerandmodelname" Authorization: Basic dxnlcm5hbwu6cgfzc3dvcmq= User-Agent: Apache-HttpClient/4.1.1 (java 1.5) Content-Length: 348 xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ xmlns:web="http://wotas.de.wm/webservice"> <soapenv:header/> <web:getmanufacturerandmodelname> <request> <tac> 35762400</tac> </request> </web:getmanufacturerandmodelname> state manufacturer state 0 modelname

HTTP/1.1 200 OK Transfer-Encoding: chunked xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ xmlns:xsd=http://www.w3.org/2001/xmlschema <getmanufacturerandmodelnameresponse xmlns="http://wotas.de.wm/webservice"> <response xmlns=""> <state>0</state> <manufacturer> Nokia Corporation</manufacturer> <modelname> Nokia 3100</modelName> </response> </getmanufacturerandmodelnameresponse>

Authorization: Basic dxnlcm5hbwu6cgfzc3dvcmq=

showtacs