SunOS 5.9

login: root 
Password: 
Last login: Mon Oct  1 11:44:44 from 172.1.31.27
Sun Microsystems Inc.   SunOS 5.9       Generic May 2002
You have new mail.
Sourcing //.profile-EIS.....
root@MAQUETALV # /opt/cp/syncml1/syncml/bin/syncmlrc isotrace -d syncml:6 \ -f/opt/cp/syncml1/syncml/bin/c.1
starting /opt/cp/syncml1/syncml/bin/isotrace -d syncml:6  -f/opt/cp/syncml1/syncml/bin/c.1
12:02:12.460: [17171.25] PAB-STORAGE: txn-chk: processing environment checkpoint operation
12:02:12.480: [17171.25] PAB-STORAGE: txn-chk: environment checkpoint operation completed
12:02:17.104: [5292.12] SYNCML: connection established from 195.55.47.52
12:02:17.122: [5292.12] SYNCML: request rcvd 'POST /syncml HTTP/1.1'
12:02:17.122: [5292.12] SYNCML: header rcvd 'TM_user_msisdn: 34629175429'
12:02:17.122: [5292.12] SYNCML: header rcvd 'TM_user_GW: Gateway WAP 2.0'
12:02:17.122: [5292.12] SYNCML: header rcvd 'x-up-calling-line-id: 34629175429'
12:02:17.122: [5292.12] SYNCML: header rcvd 'Host: 195.235.160.141'
12:02:17.122: [5292.12] SYNCML: header rcvd 'Accept: application/vnd.syncml+xml,*/*'
12:02:17.122: [5292.12] SYNCML: header rcvd 'Accept-charset: utf-8,*'
12:02:17.122: [5292.12] SYNCML: header rcvd 'content-length: 777'
12:02:17.122: [5292.12] SYNCML: header rcvd 'content-type: application/vnd.syncml+wbxml; charset=utf-8'
12:02:17.122: [5292.12] SYNCML: header rcvd 'user-agent: Alcatel-OT-S920/1.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 ObigoInternetBrowser/Q04A UP.Link/6.3.1.15.0'
12:02:17.122: [5292.12] SYNCML: header rcvd 'x-up-forwarded-for: 10.146.245.252'
12:02:17.122: [5292.12] SYNCML: header rcvd 'x-up-subscriber-coi: coiwap'
12:02:17.122: [5292.12] SYNCML: header rcvd 'Via: 1.1 mbe-lwp01_coi1.openwave.com:8080'
12:02:17.172: [5292.12] SYNCML: body received length = 777
12:02:17.172: [5292.12] SYNCML: incoming wbxml request:
12:02:17.172: [5292.12] SYNCML: <SyncML xmlns='SYNCML:SYNCML1.1'><SyncHdr><VerDTD>1.1</VerDTD><VerProto>SyncML/1.1</VerProto><SessionID>1</SessionID><MsgID>1</MsgID><Target><LocURI>http://195.235.160.141/syncml</LocURI></Target><Source><LocURI>IMEI:357593010003476</LocURI></Source><Cred><Meta><Format xmlns='syncml:metinf'>b64</Format><Type xmlns='syncml:metinf'>syncml:auth-basic</Type></Meta><Data>bW92aXN0YXI6bW92aXN0YXI=</Data></Cred><Meta><MaxMsgSize xmlns='syncml:metinf'>8192</MaxMsgSize></Meta></SyncHdr><SyncBody><Alert><CmdID>1</Cmd
12:02:17.172: [5292.12] SYNCML: ID><Data>201</Data><Item><Target><LocURI>./pab</LocURI></Target><Source><LocURI>./contacts</LocURI></Source><Meta><Anchor xmlns='syncml:metinf'><Next xmlns='syncml:metinf'>1</Next></Anchor></Meta></Item></Alert><Put><CmdID>2</CmdID><Meta><Type xmlns='syncml:metinf'>application/vnd.syncml-devinf+wbxml</Type></Meta><Item><Source><LocURI>./devinf11</LocURI></Source><Data><DevInf xmlns="syncml:devinf"><VerDTD>1.1</VerDTD><Man>Vodafone</Man><Mod>V 710</Mod><OEM>Huawei Technology Co., Ltd.</OEM><FwV>1.0</FwV><Sw
12:02:17.172: [5292.12] SYNCML: V> 36</SwV><HwV>1.0</HwV><DevID>357593010003476</DevID><DevTyp>phone</DevTyp><SupportNumberOfChanges/><DataStore><SourceRef>./contacts</SourceRef><MaxGUIDSize>4</MaxGUIDSize><Rx-Pref><CTType>text/x-vcard</CTType><VerCT>2.1</VerCT></Rx-Pref><Rx><CTType>text/x-vcard</CTType><VerCT>2.1</VerCT></Rx><Tx-Pref><CTType>text/x-vcard</CTType><VerCT>2.1</VerCT></Tx-Pref><Tx><CTType>text/x-vcard</CTType><VerCT>2.1</VerCT></Tx><SyncCap><SyncType>1</SyncType><SyncType>2</SyncType></SyncCap></DataStore><CTCap><CTType>tex
12:02:17.173: [5292.12] SYNCML: t/x-vcard</CTType><PropName>BEGIN</PropName><ValEnum>VCARD</ValEnum><PropName>END</PropName><ValEnum>VCARD</ValEnum><PropName>VERSION</PropName><ValEnum>2.1</ValEnum><PropName>N</PropName><PropName>TEL</PropName><ParamName>HOME</ParamName><ParamName>WORK</ParamName><ParamName>CELL</ParamName><ParamName>FAX</ParamName><PropName>EMAIL</PropName><ParamName>INTERNET</ParamName><PropName>ADR</PropName><ParamName>WORK</ParamName><ParamName>HOME</ParamName></CTCap></DevInf></Data></Item></Put><Final/></SyncBody><
12:02:17.173: [5292.12] SYNCML: /SyncML>
12:02:17.173: [5292.12] SYNCML: adding command for synchdr with type [6C]
12:02:17.173: [5292.12] SYNCML: received message id '1'
12:02:17.173: [5292.12] SYNCML: captured target uri [http://195.235.160.141/syncml]
12:02:17.173: [5292.12] SYNCML: captured source uri [IMEI:357593010003476]
12:02:17.173: [5292.12] SYNCML: session successfully found in cache
12:02:17.173: [5292.12] SYNCML: invalid message id received
12:02:17.173: [5292.12] SYNCML: unable to process sync data item '23' error '1005'
12:02:17.173: [5292.12] SYNCML: response status '400 - Bad Request'
12:02:17.173: [5292.12] SYNCML: response transfer completed
12:02:17.173: [5292.12] SYNCML: closing session - no user information
12:02:22.550: [17171.25] PAB-STORAGE: txn-chk: processing environment checkpoint operation
12:02:22.608: [17171.25] PAB-STORAGE: txn-chk: environment checkpoint operation completed
12:02:29.923: [23110.19] SYNCML: server configuration has changed - reconfiguring myself
12:02:29.924: [23110.19] SYNCML: Server name = 12.12.12.2
12:02:29.924: [23110.19] SYNCML: Data HTTP port = 80, ssl port = 0 data threads = 256
12:02:29.924: [23110.19] SYNCML: Notification port = 9081, notification threads = 64
12:02:29.924: [23110.19] SYNCML: Manager port = 4221, manager threads = 64
12:02:29.924: [23110.19] SYNCML: User Manager port = 4222, user manager threads = 16
12:02:29.924: [23110.19] SYNCML: Log file directory = '/opt/cp/syncml1/syncml/log'
12:02:32.680: [17171.25] PAB-STORAGE: txn-chk: processing environment checkpoint operation
12:02:32.708: [17171.25] PAB-STORAGE: txn-chk: environment checkpoint operation completed
12:02:41.490: [5292.3] LOCATOR: LDAP Read(cn=domains,cn=cproot,dc=movistar1,c=es) DSA='loc1'
12:02:41.492: [5292.3] LOCATOR: LDAP Read successful
12:02:42.790: [17171.25] PAB-STORAGE: txn-chk: processing environment checkpoint operation
12:02:42.808: [17171.25] PAB-STORAGE: txn-chk: environment checkpoint operation completed
12:02:42.810: [17171.20] LOCATOR: LDAP Read(cn=domains,cn=cproot,dc=movistar1,c=es) DSA='loc1'
12:02:42.811: [17171.20] LOCATOR: LDAP Read successful
12:02:52.880: [17171.25] PAB-STORAGE: txn-chk: processing environment checkpoint operation
12:02:52.923: [17171.25] PAB-STORAGE: txn-chk: environment checkpoint operation completed
12:02:53.842: [5292.11] SYNCML: connection established from 195.55.47.52
12:02:53.844: [5292.11] SYNCML: request rcvd 'POST /syncml HTTP/1.1'
12:02:53.844: [5292.11] SYNCML: header rcvd 'TM_user_msisdn: 34629175429'
12:02:53.844: [5292.11] SYNCML: header rcvd 'TM_user_GW: Gateway WAP 2.0'
12:02:53.844: [5292.11] SYNCML: header rcvd 'x-up-calling-line-id: 34629175429'
12:02:53.844: [5292.11] SYNCML: header rcvd 'Host: 195.235.160.141'
12:02:53.844: [5292.11] SYNCML: header rcvd 'Accept: application/vnd.syncml+xml,*/*'
12:02:53.844: [5292.11] SYNCML: header rcvd 'Accept-charset: utf-8,*'
12:02:53.844: [5292.11] SYNCML: header rcvd 'content-length: 777'
12:02:53.844: [5292.11] SYNCML: header rcvd 'content-type: application/vnd.syncml+wbxml; charset=utf-8'
12:02:53.844: [5292.11] SYNCML: header rcvd 'user-agent: Alcatel-OT-S920/1.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 ObigoInternetBrowser/Q04A UP.Link/6.3.1.15.0'
12:02:53.844: [5292.11] SYNCML: header rcvd 'x-up-forwarded-for: 10.146.222.80'
12:02:53.844: [5292.11] SYNCML: header rcvd 'x-up-subscriber-coi: coiwap'
12:02:53.844: [5292.11] SYNCML: header rcvd 'Via: 1.1 mbe-lwp01_coi1.openwave.com:8080'
12:02:53.858: [5292.11] SYNCML: body received length = 777
12:02:53.858: [5292.11] SYNCML: incoming wbxml request:
12:02:53.858: [5292.11] SYNCML: <SyncML xmlns='SYNCML:SYNCML1.1'><SyncHdr><VerDTD>1.1</VerDTD><VerProto>SyncML/1.1</VerProto><SessionID>1</SessionID><MsgID>1</MsgID><Target><LocURI>http://195.235.160.141/syncml</LocURI></Target><Source><LocURI>IMEI:357593010003476</LocURI></Source><Cred><Meta><Format xmlns='syncml:metinf'>b64</Format><Type xmlns='syncml:metinf'>syncml:auth-basic</Type></Meta><Data>bW92aXN0YXI6bW92aXN0YXI=</Data></Cred><Meta><MaxMsgSize xmlns='syncml:metinf'>8192</MaxMsgSize></Meta></SyncHdr><SyncBody><Alert><CmdID>1</Cmd
12:02:53.858: [5292.11] SYNCML: ID><Data>201</Data><Item><Target><LocURI>./pab</LocURI></Target><Source><LocURI>./contacts</LocURI></Source><Meta><Anchor xmlns='syncml:metinf'><Next xmlns='syncml:metinf'>1</Next></Anchor></Meta></Item></Alert><Put><CmdID>2</CmdID><Meta><Type xmlns='syncml:metinf'>application/vnd.syncml-devinf+wbxml</Type></Meta><Item><Source><LocURI>./devinf11</LocURI></Source><Data><DevInf xmlns="syncml:devinf"><VerDTD>1.1</VerDTD><Man>Vodafone</Man><Mod>V 710</Mod><OEM>Huawei Technology Co., Ltd.</OEM><FwV>1.0</FwV><Sw
12:02:53.858: [5292.11] SYNCML: V> 36</SwV><HwV>1.0</HwV><DevID>357593010003476</DevID><DevTyp>phone</DevTyp><SupportNumberOfChanges/><DataStore><SourceRef>./contacts</SourceRef><MaxGUIDSize>4</MaxGUIDSize><Rx-Pref><CTType>text/x-vcard</CTType><VerCT>2.1</VerCT></Rx-Pref><Rx><CTType>text/x-vcard</CTType><VerCT>2.1</VerCT></Rx><Tx-Pref><CTType>text/x-vcard</CTType><VerCT>2.1</VerCT></Tx-Pref><Tx><CTType>text/x-vcard</CTType><VerCT>2.1</VerCT></Tx><SyncCap><SyncType>1</SyncType><SyncType>2</SyncType></SyncCap></DataStore><CTCap><CTType>tex
12:02:53.869: [5292.11] SYNCML: t/x-vcard</CTType><PropName>BEGIN</PropName><ValEnum>VCARD</ValEnum><PropName>END</PropName><ValEnum>VCARD</ValEnum><PropName>VERSION</PropName><ValEnum>2.1</ValEnum><PropName>N</PropName><PropName>TEL</PropName><ParamName>HOME</ParamName><ParamName>WORK</ParamName><ParamName>CELL</ParamName><ParamName>FAX</ParamName><PropName>EMAIL</PropName><ParamName>INTERNET</ParamName><PropName>ADR</PropName><ParamName>WORK</ParamName><ParamName>HOME</ParamName></CTCap></DevInf></Data></Item></Put><Final/></SyncBody><
12:02:53.869: [5292.11] SYNCML: /SyncML>
12:02:53.869: [5292.11] SYNCML: adding command for synchdr with type [6C]
12:02:53.869: [5292.11] SYNCML: received message id '1'
12:02:53.869: [5292.11] SYNCML: captured target uri [http://195.235.160.141/syncml]
12:02:53.869: [5292.11] SYNCML: captured source uri [IMEI:357593010003476]
12:02:53.869: [5292.11] SYNCML: no session found in cache. a new session will be created
12:02:53.870: [5292.11] LOCATOR: LDAP Read(uid=629175429,cn=users,cn=movistar.es,cn=domains,cn=cproot,dc=movistar1,c=es) DSA='loc1'
12:02:53.871: [5292.11] LOCATOR: LDAP Read error 32 'No such object'
12:03:03.000: [17171.25] PAB-STORAGE: txn-chk: processing environment checkpoint operation
12:03:03.028: [17171.25] PAB-STORAGE: txn-chk: environment checkpoint operation completed
12:03:13.070: [17171.25] PAB-STORAGE: txn-chk: processing environment checkpoint operation
12:03:13.098: [17171.25] PAB-STORAGE: txn-chk: environment checkpoint operation completed
12:03:14.020: [5292.11] LOCATOR: LDAP Read(uid=629175429,cn=users,cn=movistar.es,cn=domains,cn=cproot,dc=movistar1,c=es) DSA='loc1'
12:03:14.021: [5292.11] LOCATOR: LDAP Read error 32 'No such object'
12:03:14.021: [5292.11] SYNCML: unable to resolve msisdn '629175429' - error 20002
12:03:14.022: [5292.11] SYNCML: set max msg size to [8192]
12:03:14.022: [5292.11] SYNCML: set status to '401' based on auth
12:03:14.022: [5292.11] SYNCML: captured next anchor [1]
12:03:14.022: [5292.11] SYNCML: parse device info
12:03:14.022: [5292.11] SYNCML: processing devinf
12:03:14.022: [5292.11] SYNCML: searching for datastore with source_ref './contacts'
12:03:14.022: [5292.11] SYNCML: datastore not found
12:03:14.022: [5292.11] SYNCML: creating and storing datastore for './contacts' from DevInf
12:03:14.022: [5292.11] SYNCML: setting current datastore for client db './contacts'
12:03:14.022: [5292.11] SYNCML: captured CTType 'text/x-vcard'
12:03:14.022: [5292.11] SYNCML: found datastore, saving CTType
12:03:14.022: [5292.11] SYNCML: captured CTType 'text/x-vcard'
12:03:14.022: [5292.11] SYNCML: found datastore, saving CTType
12:03:14.022: [5292.11] SYNCML: captured CTType 'text/x-vcard'
12:03:14.022: [5292.11] SYNCML: found datastore, saving CTType
12:03:14.022: [5292.11] SYNCML: captured CTType 'text/x-vcard'
12:03:14.022: [5292.11] SYNCML: found datastore, saving CTType
12:03:14.022: [5292.11] SYNCML: captured CTType 'text/x-vcard'
12:03:14.023: [5292.11] SYNCML: found devinf with values:
12:03:14.023: [5292.11] SYNCML:         dtd major[1] - dtd minor[1]
12:03:14.023: [5292.11] SYNCML:         man[Vodafone]
12:03:14.023: [5292.11] SYNCML:         mod[V 710]
12:03:14.023: [5292.11] SYNCML:         oem[Huawei Technology Co., Ltd.]
12:03:14.023: [5292.11] SYNCML:         sw_version[ 36]
12:03:14.023: [5292.11] SYNCML:         hw_version[1.0]
12:03:14.023: [5292.11] SYNCML:         fw_version[1.0]
12:03:14.023: [5292.11] SYNCML:         dev_id[357593010003476]
12:03:14.023: [5292.11] SYNCML:         dev_type[phone]
12:03:14.023: [5292.11] SYNCML: saving device info
12:03:14.023: [5292.11] SYNCML: generating status for command of type [SyncHdr]
12:03:14.023: [5292.11] SYNCML: requesting auth challenge response
12:03:14.023: [5292.11] SYNCML: agent mfg - 0
12:03:14.023: [5292.11] SYNCML: agent model - V 710
12:03:14.023: [5292.11] SYNCML: Command with 0 items
12:03:14.023: [5292.11] SYNCML: generating status for command of type [Alert]
12:03:14.023: [5292.11] SYNCML: Command with 1 item
12:03:14.024: [5292.11] SYNCML: generating status for command of type [Put]
12:03:14.024: [5292.11] SYNCML: Command with 1 item
12:03:14.024: [5292.11] SYNCML: syncml message response:
12:03:14.024: [5292.11] SYNCML: <SyncML xmlns='SYNCML:SYNCML1.1'><SyncHdr><VerDTD>1.1</VerDTD><VerProto>SyncML/1.1</VerProto><SessionID>1</SessionID><MsgID>1</MsgID><Target><LocURI>IMEI:357593010003476</LocURI></Target><Source><LocURI>http://195.235.160.141/syncml</LocURI></Source><Meta><MaxMsgSize xmlns='syncml:metinf'>10240</MaxMsgSize></Meta></SyncHdr><SyncBody><Status><CmdID>1</CmdID><MsgRef>1</MsgRef><CmdRef>0</CmdRef><Cmd>SyncHdr</Cmd><TargetRef>http://195.235.160.141/syncml</TargetRef><SourceRef>IMEI:357593010003476</SourceRef><Ch
12:03:14.024: [5292.11] SYNCML: al><Meta><Type xmlns='syncml:metinf'>syncml:auth-md5</Type><Format xmlns='syncml:metinf'>b64</Format><NextNonce xmlns='syncml:metinf'>OUIwNjFD</NextNonce></Meta></Chal><Data>401</Data></Status><Status><CmdID>2</CmdID><MsgRef>1</MsgRef><CmdRef>1</CmdRef><Cmd>Alert</Cmd><TargetRef>./pab</TargetRef><SourceRef>./contacts</SourceRef><Data>401</Data></Status><Status><CmdID>3</CmdID><MsgRef>1</MsgRef><CmdRef>2</CmdRef><Cmd>Put</Cmd><SourceRef>./devinf11</SourceRef><Data>401</Data></Status><Final/></SyncBody></Syn
12:03:14.024: [5292.11] SYNCML: cML>
12:03:14.024: [5292.11] SYNCML: response status '200 - OK'
12:03:14.024: [5292.11] SYNCML: header sent 'Content-Type: application/vnd.syncml+wbxml'
12:03:14.024: [5292.11] SYNCML: header sent 'Date: Mon, 1 Oct 2007 10:03:14 GMT'
12:03:14.024: [5292.11] SYNCML: header sent 'Server: Critical Path SyncML Server version 7.3.113.DEV'
12:03:14.024: [5292.11] SYNCML: header sent 'Content-Length: 395'
12:03:14.024: [5292.11] SYNCML: transmit response body length=395
12:03:14.025: [5292.11] SYNCML: response transfer completed
12:03:16.468: [5292.10] SYNCML: connection established from 195.55.47.52
12:03:16.469: [5292.10] SYNCML: request rcvd 'POST /syncml HTTP/1.1'
12:03:16.470: [5292.10] SYNCML: header rcvd 'TM_user_msisdn: 34629175429'
12:03:16.470: [5292.10] SYNCML: header rcvd 'TM_user_GW: Gateway WAP 2.0'
12:03:16.470: [5292.10] SYNCML: header rcvd 'x-up-calling-line-id: 34629175429'
12:03:16.470: [5292.10] SYNCML: header rcvd 'Host: 195.235.160.141'
12:03:16.470: [5292.10] SYNCML: header rcvd 'Accept: application/vnd.syncml+xml,*/*'
12:03:16.470: [5292.10] SYNCML: header rcvd 'Accept-charset: utf-8,*'
12:03:16.470: [5292.10] SYNCML: header rcvd 'content-length: 867'
12:03:16.470: [5292.10] SYNCML: header rcvd 'content-type: application/vnd.syncml+wbxml; charset=utf-8'
12:03:16.470: [5292.10] SYNCML: header rcvd 'user-agent: Alcatel-OT-S920/1.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 ObigoInternetBrowser/Q04A UP.Link/6.3.1.15.0'
12:03:16.470: [5292.10] SYNCML: header rcvd 'x-up-forwarded-for: 10.146.222.80'
12:03:16.470: [5292.10] SYNCML: header rcvd 'x-up-subscriber-coi: coiwap'
12:03:16.470: [5292.10] SYNCML: header rcvd 'Via: 1.1 mbe-lwp01_coi1.openwave.com:8080'
12:03:16.484: [5292.10] SYNCML: body received length = 867
12:03:16.484: [5292.10] SYNCML: incoming wbxml request:
12:03:16.484: [5292.10] SYNCML: <SyncML xmlns='SYNCML:SYNCML1.1'><SyncHdr><VerDTD>1.1</VerDTD><VerProto>SyncML/1.1</VerProto><SessionID>1</SessionID><MsgID>2</MsgID><Target><LocURI>http://195.235.160.141/syncml</LocURI></Target><Source><LocURI>IMEI:357593010003476</LocURI></Source><Cred><Meta><Format xmlns='syncml:metinf'>b64</Format><Type xmlns='syncml:metinf'>syncml:auth-md5</Type></Meta><Data>UZECt3tPb6mTN8E109saQg==</Data></Cred><Meta><MaxMsgSize xmlns='syncml:metinf'>8192</MaxMsgSize></Meta></SyncHdr><SyncBody><Status><CmdID>1</CmdI
12:03:16.484: [5292.10] SYNCML: D><MsgRef>1</MsgRef><CmdRef>0</CmdRef><Cmd>SyncHdr</Cmd><TargetRef>IMEI:357593010003476</TargetRef><SourceRef>http://195.235.160.141/syncml</SourceRef><Data>200</Data></Status><Alert><CmdID>2</CmdID><Data>201</Data><Item><Target><LocURI>./pab</LocURI></Target><Source><LocURI>./contacts</LocURI></Source><Meta><Anchor xmlns='syncml:metinf'><Next xmlns='syncml:metinf'>1</Next></Anchor></Meta></Item></Alert><Put><CmdID>3</CmdID><Meta><Type xmlns='syncml:metinf'>application/vnd.syncml-devinf+wbxml</Type></Meta>
12:03:16.486: [5292.10] SYNCML: <Item><Source><LocURI>./devinf11</LocURI></Source><Data><DevInf xmlns="syncml:devinf"><VerDTD>1.1</VerDTD><Man>Vodafone</Man><Mod>V 710</Mod><OEM>Huawei Technology Co., Ltd.</OEM><FwV>1.0</FwV><SwV> 36</SwV><HwV>1.0</HwV><DevID>357593010003476</DevID><DevTyp>phone</DevTyp><SupportNumberOfChanges/><DataStore><SourceRef>./contacts</SourceRef><MaxGUIDSize>4</MaxGUIDSize><Rx-Pref><CTType>text/x-vcard</CTType><VerCT>2.1</VerCT></Rx-Pref><Rx><CTType>text/x-vcard</CTType><VerCT>2.1</VerCT></Rx><Tx-Pref><CTType>te
12:03:16.487: [5292.10] SYNCML: xt/x-vcard</CTType><VerCT>2.1</VerCT></Tx-Pref><Tx><CTType>text/x-vcard</CTType><VerCT>2.1</VerCT></Tx><SyncCap><SyncType>1</SyncType><SyncType>2</SyncType></SyncCap></DataStore><CTCap><CTType>text/x-vcard</CTType><PropName>BEGIN</PropName><ValEnum>VCARD</ValEnum><PropName>END</PropName><ValEnum>VCARD</ValEnum><PropName>VERSION</PropName><ValEnum>2.1</ValEnum><PropName>N</PropName><PropName>TEL</PropName><ParamName>HOME</ParamName><ParamName>WORK</ParamName><ParamName>CELL</ParamName><ParamName>FAX</ParamN
12:03:16.487: [5292.10] SYNCML: ame><PropName>EMAIL</PropName><ParamName>INTERNET</ParamName><PropName>ADR</PropName><ParamName>WORK</ParamName><ParamName>HOME</ParamName></CTCap></DevInf></Data></Item></Put><Final/></SyncBody></SyncML>
12:03:16.487: [5292.10] SYNCML: adding command for synchdr with type [6C]
12:03:16.487: [5292.10] SYNCML: received message id '2'
12:03:16.487: [5292.10] SYNCML: captured target uri [http://195.235.160.141/syncml]
12:03:16.487: [5292.10] SYNCML: captured source uri [IMEI:357593010003476]
12:03:16.487: [5292.10] SYNCML: session successfully found in cache
12:03:16.487: [5292.10] SYNCML: set max msg size to [8192]
12:03:16.487: [5292.10] SYNCML: set status to '401' based on auth
12:03:16.487: [5292.10] SYNCML: processing status for command of type '2C'
12:03:16.488: [5292.10] SYNCML: captured next anchor [1]
12:03:16.488: [5292.10] SYNCML: parse device info
12:03:16.488: [5292.10] SYNCML: processing devinf
12:03:16.488: [5292.10] SYNCML: searching for datastore with source_ref './contacts'
12:03:16.488: [5292.10] SYNCML: comparing to uri './contacts'
12:03:16.488: [5292.10] SYNCML: setting current datastore for client db './contacts'
12:03:16.488: [5292.10] SYNCML: captured CTType 'text/x-vcard'
12:03:16.488: [5292.10] SYNCML: found datastore, saving CTType
12:03:16.488: [5292.10] SYNCML: captured CTType 'text/x-vcard'
12:03:16.488: [5292.10] SYNCML: found datastore, saving CTType
12:03:16.488: [5292.10] SYNCML: captured CTType 'text/x-vcard'
12:03:16.488: [5292.10] SYNCML: found datastore, saving CTType
12:03:16.488: [5292.10] SYNCML: captured CTType 'text/x-vcard'
12:03:16.488: [5292.10] SYNCML: found datastore, saving CTType
12:03:16.488: [5292.10] SYNCML: captured CTType 'text/x-vcard'
12:03:16.488: [5292.10] SYNCML: found devinf with values:
12:03:16.488: [5292.10] SYNCML:         dtd major[1] - dtd minor[1]
12:03:16.488: [5292.10] SYNCML:         man[Vodafone]
12:03:16.488: [5292.10] SYNCML:         mod[V 710]
12:03:16.488: [5292.10] SYNCML:         oem[Huawei Technology Co., Ltd.]
12:03:16.488: [5292.10] SYNCML:         sw_version[ 36]
12:03:16.488: [5292.10] SYNCML:         hw_version[1.0]
12:03:16.489: [5292.10] SYNCML:         fw_version[1.0]
12:03:16.489: [5292.10] SYNCML:         dev_id[357593010003476]
12:03:16.489: [5292.10] SYNCML:         dev_type[phone]
12:03:16.489: [5292.10] SYNCML: saving device info
12:03:16.489: [5292.10] SYNCML: generating status for command of type [SyncHdr]
12:03:16.489: [5292.10] SYNCML: requesting auth challenge response
12:03:16.489: [5292.10] SYNCML: agent mfg - 0
12:03:16.489: [5292.10] SYNCML: agent model - V 710
12:03:16.489: [5292.10] SYNCML: Command with 0 items
12:03:16.489: [5292.10] SYNCML: generating status for command of type [Alert]
12:03:16.489: [5292.10] SYNCML: Command with 1 item
12:03:16.489: [5292.10] SYNCML: generating status for command of type [Put]
12:03:16.489: [5292.10] SYNCML: Command with 1 item
12:03:16.489: [5292.10] SYNCML: syncml message response:
12:03:16.489: [5292.10] SYNCML: <SyncML xmlns='SYNCML:SYNCML1.1'><SyncHdr><VerDTD>1.1</VerDTD><VerProto>SyncML/1.1</VerProto><SessionID>1</SessionID><MsgID>2</MsgID><Target><LocURI>IMEI:357593010003476</LocURI></Target><Source><LocURI>http://195.235.160.141/syncml</LocURI></Source><Meta><MaxMsgSize xmlns='syncml:metinf'>10240</MaxMsgSize></Meta></SyncHdr><SyncBody><Status><CmdID>4</CmdID><MsgRef>2</MsgRef><CmdRef>0</CmdRef><Cmd>SyncHdr</Cmd><TargetRef>http://195.235.160.141/syncml</TargetRef><SourceRef>IMEI:357593010003476</SourceRef><Ch
12:03:16.489: [5292.10] SYNCML: al><Meta><Type xmlns='syncml:metinf'>syncml:auth-md5</Type><Format xmlns='syncml:metinf'>b64</Format><NextNonce xmlns='syncml:metinf'>OThGNjkx</NextNonce></Meta></Chal><Data>401</Data></Status><Status><CmdID>5</CmdID><MsgRef>2</MsgRef><CmdRef>2</CmdRef><Cmd>Alert</Cmd><TargetRef>./pab</TargetRef><SourceRef>./contacts</SourceRef><Data>401</Data></Status><Status><CmdID>6</CmdID><MsgRef>2</MsgRef><CmdRef>3</CmdRef><Cmd>Put</Cmd><SourceRef>./devinf11</SourceRef><Data>401</Data></Status><Final/></SyncBody></Syn
12:03:16.490: [5292.10] SYNCML: cML>
12:03:16.490: [5292.10] SYNCML: response status '200 - OK'
12:03:16.490: [5292.10] SYNCML: header sent 'Content-Type: application/vnd.syncml+wbxml'
12:03:16.490: [5292.10] SYNCML: header sent 'Date: Mon, 1 Oct 2007 10:03:16 GMT'
12:03:16.490: [5292.10] SYNCML: header sent 'Server: Critical Path SyncML Server version 7.3.113.DEV'
12:03:16.490: [5292.10] SYNCML: header sent 'Content-Length: 395'
12:03:16.490: [5292.10] SYNCML: transmit response body length=395
12:03:16.490: [5292.10] SYNCML: response transfer completed
12:03:23.170: [17171.25] PAB-STORAGE: txn-chk: processing environment checkpoint operation
12:03:23.215: [17171.25] PAB-STORAGE: txn-chk: environment checkpoint operation completed
^Croot@MAQUETALV # grep 629175429 /opt/cp/syncml1/syncml/bin/c.1
12:02:17.122: [5292.12] SYNCML: header rcvd 'TM_user_msisdn: 34629175429'
12:02:17.122: [5292.12] SYNCML: header rcvd 'x-up-calling-line-id: 34629175429'
12:02:53.844: [5292.11] SYNCML: header rcvd 'TM_user_msisdn: 34629175429'
12:02:53.844: [5292.11] SYNCML: header rcvd 'x-up-calling-line-id: 34629175429'
12:02:53.870: [5292.11] LOCATOR: LDAP Read(uid=629175429,cn=users,cn=movistar.es,cn=domains,cn=cproot,dc=movistar1,c=es) DSA='loc1'
12:03:14.020: [5292.11] LOCATOR: LDAP Read(uid=629175429,cn=users,cn=movistar.es,cn=domains,cn=cproot,dc=movistar1,c=es) DSA='loc1'
12:03:14.021: [5292.11] SYNCML: unable to resolve msisdn '629175429' - error 20002
12:03:16.470: [5292.10] SYNCML: header rcvd 'TM_user_msisdn: 34629175429'
12:03:16.470: [5292.10] SYNCML: header rcvd 'x-up-calling-line-id: 34629175429'
root@MAQUETALV # 



HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
HTC P5500/arcsoft-mmsua-4.0.0.xx
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml
http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml









GET /browser/index.wml HTTP/1.1
Accept: application/xhtml+xml, text/html, text/plain, text/css, application/vnd.wap.xhtml+xml, application/vnd.wap.wmlc, application/vnd.wap.wmlscriptc, text/vnd.wap.wml, text/vnd.wap.connectivity, image/vnd.wap.wbmp, image/jpeg, image/gif, audio/x-midi, audio/sp-midi, audio/midi, audio/mid, text/vnd.sun.j2me.app-descriptor, */*
Accept-Language: es
UA-OS: Windows CE (Pocket PC) - Version 5.2
UA-color: color16
x-wap-profile: "http://www.htcmms.com.tw/tme/nike-1.0.xml"
UA-pixels: 240x320
UA-Voice: TRUE
UA-CPU: ARM
Accept-Encoding: gzip,deflate
User-Agent: HTC P5500/1.09.621.05 Mozilla/4.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 (compatible; MSIE 6.0; Windows CE; IEMobile 7.6)
Host: 195.235.160.80
Connection: Keep-Alive

HTTP/1.1 200 OK
Date: Fri, 28 Sep 2007 12:02:25 GMT
Server: Apache/1.3.36 (Win32) mod_ssl/2.8.27 OpenSSL/0.9.8b
Last-Modified: Thu, 22 Sep 2005 10:44:28 GMT
ETag: "0-480-43328b0c"
Accept-Ranges: bytes
Content-Length: 1152
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/vnd.wap.wml

<?xml version="1.0"?> 
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml"> 
<wml> 
	<card id="card1"> 
		<p align="center"> 	<b>
<u>BROWSER Test</u></b><br/> </p>
<p>


  <a href="./wap12/index.wml">WAP 1.2</a><br/>
  <a href="./Pruebas_XHTMLMP/IndiceDePruebas.xhtml">WAP 2.0 [xHTML-MP]</a><br/>

  <!-- 
  <a href="./Pruebas_XHTMLMP_SIN_INFORME/IndiceDePruebas.xhtml">WAP 2.0 [xHTML-MP] (sin informe)</a><br/> 
  <a href="http://195.235.160.162/r.wml">i-MODE [i-HTML] DOCOMO STEP 3</a><br/>  
  <a href="http://terminales.movistar.com/browser/imode/index.html">i-MODE [i-HTML] TELEFONICA</a><br/><br/> 
  -->

<br/>
<a href="../index.wml">Back</a><br/>

 <!-- 
<a href="./chtml/access.html">i-MODE [c-HTML] TELEFONICA test</a><br/>
  <a href="wap20.wml">WAP 2.0</a><br/>
   <a href="./imodedocomo/global/tech/s2index.htm">I-MODE docomo antiguo</a><br/>
  <a href="http://terminales.movistar.com/Step2Contents/global/tech/s2index.htm">i-html DOCOMO    test</a><br/>
  <a href="./wap20/IndiceDePruebas.xhtml">WAP...20</a><br/>
 -->

</p> 
	</card>  
</wml> 










GET /browser/Pruebas_XHTMLMP/IndiceDePruebas.xhtml HTTP/1.1
Accept: application/xhtml+xml, text/html, text/plain, text/css, application/vnd.wap.xhtml+xml, application/vnd.wap.wmlc, application/vnd.wap.wmlscriptc, text/vnd.wap.wml, text/vnd.wap.connectivity, image/vnd.wap.wbmp, image/jpeg, image/gif, audio/x-midi, audio/sp-midi, audio/midi, audio/mid, text/vnd.sun.j2me.app-descriptor, */*
Accept-Language: es
UA-OS: Windows CE (Pocket PC) - Version 5.2
UA-color: color16
x-wap-profile: "http://www.htcmms.com.tw/tme/nike-1.0.xml"
UA-pixels: 240x320
UA-Voice: TRUE
UA-CPU: ARM
Accept-Encoding: gzip,deflate
User-Agent: HTC P5500/1.09.621.05 Mozilla/4.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 (compatible; MSIE 6.0; Windows CE; IEMobile 7.6)
Host: 195.235.160.80
Connection: Keep-Alive

HTTP/1.1 200 OK
Date: Fri, 28 Sep 2007 12:02:27 GMT
Server: Apache/1.3.36 (Win32) mod_ssl/2.8.27 OpenSSL/0.9.8b
Last-Modified: Tue, 04 Apr 2006 10:00:03 GMT
ETag: "0-3a1-443243a3"
Accept-Ranges: bytes
Content-Length: 929
Keep-Alive: timeout=15, max=99
Connection: Keep-Alive
Content-Type: application/xhtml+xml

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.0//EN" 
"http://www.wapforum.org/DTD/xhtml-mobile10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<!--
	Etiqueta      : Ninguna
	Contenido   : Fichero de seleccion del tipo de pruebas que se desean realizar.
		      Las dos posibilidades son:
		      		Pruebas de etiquetas lenguaje WML 2.0
		      		Pruebas de hojas de estilo.
-->

	<head>
		<title>
			Tests Index
		</title>
	</head>
	<body>
		<p>
			Select type of tests: <br/>
<a title="XHTML-MP Tags" href="./PRUEBAS_XHTMLMP/IndiceGeneral.xhtml"> XHTML-MP tags tests</a><br/>
<a title="XHTML-MP CSS" href="./PRUEBAS_CSS/IndiceWCSS.xhtml"> XHTML-MP CSS tests</a><br/>
<a title="XHTML-MP size" href="./PRUEBAS_SIZE/size.xhtml"> XHTML-MP size</a><br/>
<a title="SmartMenu" href="../color/color.wml"> Smart Menu</a><br/>

		</p>
	</body>
</html>
GET /browser/Pruebas_XHTMLMP/PRUEBAS_SIZE/size.xhtml HTTP/1.1
Accept: application/xhtml+xml, text/html, text/plain, text/css, application/vnd.wap.xhtml+xml, application/vnd.wap.wmlc, application/vnd.wap.wmlscriptc, text/vnd.wap.wml, text/vnd.wap.connectivity, image/vnd.wap.wbmp, image/jpeg, image/gif, audio/x-midi, audio/sp-midi, audio/midi, audio/mid, text/vnd.sun.j2me.app-descriptor, */*
Accept-Language: es
UA-OS: Windows CE (Pocket PC) - Version 5.2
UA-color: color16
x-wap-profile: "http://www.htcmms.com.tw/tme/nike-1.0.xml"
UA-Voice: TRUE
Referer: http://195.235.160.80/browser/Pruebas_XHTMLMP/IndiceDePruebas.xhtml
UA-pixels: 240x320
UA-CPU: ARM
Accept-Encoding: gzip,deflate
User-Agent: HTC P5500/1.09.621.05 Mozilla/4.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 (compatible; MSIE 6.0; Windows CE; IEMobile 7.6)
Host: 195.235.160.80
Connection: Keep-Alive

HTTP/1.1 200 OK
Date: Fri, 28 Sep 2007 12:02:29 GMT
Server: Apache/1.3.36 (Win32) mod_ssl/2.8.27 OpenSSL/0.9.8b
Last-Modified: Fri, 04 Mar 2005 08:35:12 GMT
ETag: "0-58f-42281dc0"
Accept-Ranges: bytes
Content-Length: 1423
Keep-Alive: timeout=15, max=98
Connection: Keep-Alive
Content-Type: application/xhtml+xml

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.0//EN" 
"http://www.wapforum.org/DTD/xhtml-mobile10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<!--
	Etiqueta      : Ninguna
	Contenido   : Fichero de seleccion del tipo de pruebas que se desean realizar.
		      Las dos posibilidades son:
		      		Pruebas de etiquetas lenguaje WML 2.0
		      		Pruebas de hojas de estilo.
-->

	<head>
		<title>
			Size Tests
		</title>
	</head>
	<body>
		<p>
			Select type of tests xhtml-mp: <br/>

-Page  of 30 KB total size (xhtml+css+image) :-<br/>
<a title="XHTML-MP size" href="./total30kb.xhtml">30KB total</a><br/>

-Pages of different sizes :-<br/>
<a title="XHTML-MP Tags" href="./size10kb.xhtml"> 10KB</a><br/>
<a title="XHTML-MP Tags" href="./size20kb.xhtml"> 20KB</a><br/>
<a title="XHTML-MP Tags" href="./size30kb.xhtml"> 30KB</a><br/>
<a title="XHTML-MP Tags" href="./size40kb.xhtml"> 40KB</a><br/>
<a title="XHTML-MP Tags" href="./size50kb.xhtml"> 50KB</a><br/>
<a title="XHTML-MP Tags" href="./size60kb.xhtml"> 60KB</a><br/>
<a title="XHTML-MP Tags" href="./size70kb.xhtml"> 70KB</a><br/>
<a title="XHTML-MP Tags" href="./size80kb.xhtml"> 80KB</a><br/>
<a title="XHTML-MP Tags" href="./size90kb.xhtml"> 90KB</a><br/>
<a title="XHTML-MP Tags" href="./size100kb.xhtml">100KB</a><br/>








		</p>
	</body>
</html>

GET /browser/Pruebas_XHTMLMP/PRUEBAS_SIZE/size30kb.xhtml HTTP/1.1
Accept: application/xhtml+xml, text/html, text/plain, text/css, application/vnd.wap.xhtml+xml, application/vnd.wap.wmlc, application/vnd.wap.wmlscriptc, text/vnd.wap.wml, text/vnd.wap.connectivity, image/vnd.wap.wbmp, image/jpeg, image/gif, audio/x-midi, audio/sp-midi, audio/midi, audio/mid, text/vnd.sun.j2me.app-descriptor, */*
Accept-Language: es
UA-OS: Windows CE (Pocket PC) - Version 5.2
UA-color: color16
x-wap-profile: "http://www.htcmms.com.tw/tme/nike-1.0.xml"
UA-Voice: TRUE
Referer: http://195.235.160.80/browser/Pruebas_XHTMLMP/PRUEBAS_SIZE/size.xhtml
UA-pixels: 240x320
UA-CPU: ARM
Accept-Encoding: gzip,deflate
User-Agent: HTC P5500/1.09.621.05 Mozilla/4.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 (compatible; MSIE 6.0; Windows CE; IEMobile 7.6)
Host: 195.235.160.80
Connection: Keep-Alive

HTTP/1.1 200 OK
Date: Fri, 28 Sep 2007 12:02:32 GMT
Server: Apache/1.3.36 (Win32) mod_ssl/2.8.27 OpenSSL/0.9.8b
Last-Modified: Thu, 17 Mar 2005 09:40:02 GMT
ETag: "0-74f9-42395072"
Accept-Ranges: bytes
Content-Length: 29945
Keep-Alive: timeout=15, max=97
Connection: Keep-Alive
Content-Type: application/xhtml+xml

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.0//EN" 
"http://www.wapforum.org/DTD/xhtml-mobile10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<!--
	Referencia : 6.8
	Etiqueta   : img
	Contenido  : muestra la imagen "perros.jpg"
-->


	<head>
		<title>30 KBytes page</title>
	</head>
	<body>
		<p>
THIS PAGE HAS A SIZE OF 30 KB. WAP2.0.<br/>
--<br/>

The present documents intends to be of WAP 2.0 browsers, including both the XHTML-MP tags and the design of style sheets with CSS. 
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.
Moreover, it is in the aim of this document to analyze the browser compatibility with the different contents and WAP applications contained in e-mocion, the WAP site of Telefonica Moviles Espaņa.<br/>

			<a title="Index" href="./size40kb.xhtml">40KB page</a><br/>

			<a title="Index" href="./size.xhtml"> Index</a><br/>

These tests are based on document 6-ERD030000-WAPv2.doc, which describes the necessary WAP requirements. In each of the rows of the following tables, the first box contains a requirement code which corresponds to the appropriate requirement contained in the specification 6-ERD030000-WAPv2 Requirements Specification. In some cases this box is blank, meaning that the corresponding test has not a specific requirement associated with it.

The following tests shall be done in the lab network of Telefonica Moviles Espaņa. The web server for tests is:

http://terminales.movistar.com/test.wml

and it is accessible with the e-mocion profile out of the labs.

In the following, we describe the trials protocol to be followed to check the compatibility of the browser with the different XHTML-MP tags and the style sheet elements (CSS). The trials should be performed using the connection with the WSP stack protocol for wap (port 9201) or with the HTTP stack protocol for wap 2.0 (port 8080), or with both, depending on the handset capabilities, which are the mandatory modes for Telefonica Moviles.
The trials shall be done using GPRS access. 

This section describes the exact configuration parameters to be introduced to the terminal in order to access the e-mocion site of Telefonica Moviles Espaņa. Such configuration shall be similar to that specified in document " anexo-1.1-ERD030000-parameters_TME_v3".

These trials intend to characterize the browser's behavior regarding the tags or elements defined in XHTML-MP. 
The tree structure formed by all XHTML-MP test pages shall be browsed through, analyzing the result and visualization shown by the browser, as indicated in section 7.1.
The test pages are grouped, depending on the type of elements to test, in the blocks listed in the following table:

These trials intend to characterize the browser's behavior regarding the style sheets defined in XHTML-MP (WCSS). 
The tree structure formed by all style sheet trial pages shall be browsed through, analyzing the result and visualization shown by the browser, as indicated in section 7.2.
All the elements in these trials will be correctly shown by the browser with the defined style sheet properties.
The test pages are grouped, depending on the type of elements to test, in the blocks listed in the following table:

These trials are intended to check the compatibility of the browser with contents tree of e-mocion. Specially, with several special services that can be found in e-mocion.
It should be taken into account that these special services are modified and enriched regularly, hence the tested services may change.
It's also tested the e-mocion color menu.

The test user shall browse through the contents tree of e-mocion, the WAP site of Telefonica Moviles Espaņa (it should be taken into account that the e-mocion contents are modified and enriched regularly), checking that all contents can be accessed correctly.

In this tests are included static pages with diferent templates of the e-mocion menu with color. It'll be tested which of the existent templates are the most suitable for the browser. It'll will also tested the most appropriate size of the icons to adjust to the screen size. There is  a template in e-mocion: one shows in the screen two icons in every row and another shows only one in every line.
---<br/>
The present document intends to be used as a base for the verification of the correct operation of WAP 2.0 browsers, including both the XHTML-MP tags and the design of style sheets with CSS. 
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.
Moreover, it is in the aim of this document to analyze the browser compatibility with the different contents and WAP applications contained in e-mocion, the WAP site of Telefonica Moviles Espaņa.
These tests are based on document 6-ERD030000-WAPv2.doc, which describes the necessary WAP requirements. In each of the rows of the following tables, the first box contains a requirement code which corresponds to the appropriate requirement contained in the specification 6-ERD030000-WAPv2 Requirements Specification. In some cases this box is blank, meaning that the corresponding test has not a specific requirement associated with it.

The following tests shall be done in the lab network of Telefonica Moviles Espaņa. The web server for tests is:

http://terminales.movistar.com/test.wml

and it is accessible with the e-mocion profile out of the labs.

In the following, we describe the trials protocol to be followed to check the compatibility of the browser with the different XHTML-MP tags and the style sheet elements (CSS). The trials should be performed using the connection with the WSP stack protocol for wap (port 9201) or with the HTTP stack protocol for wap 2.0 (port 8080), or with both, depending on the handset capabilities, which are the mandatory modes for Telefonica Moviles.
The trials shall be done using GPRS access. 

This section describes the exact configuration parameters to be introduced to the terminal in order to access the e-mocion site of Telefonica Moviles Espaņa. Such configuration shall be similar to that specified in document " anexo-1.1-ERD030000-parameters_TME_v3".

These trials intend to characterize the browser's behavior regarding the tags or elements defined in XHTML-MP. 
The tree structure formed by all XHTML-MP test pages shall be browsed through, analyzing the result and visualization shown by the browser, as indicated in section 7.1.
The test pages are grouped, depending on the type of elements to test, in the blocks listed in the following table:

These trials intend to characterize the browser's behavior regarding the style sheets defined in XHTML-MP (WCSS). 
The tree structure formed by all style sheet trial pages shall be browsed through, analyzing the result and visualization shown by the browser, as indicated in section 7.2.
All the elements in these trials will be correctly shown by the browser with the defined style sheet properties.
The test pages are grouped, depending on the type of elements to test, in the blocks listed in the following table:

These trials are intended to check the compatibility of the browser with contents tree of e-mocion. Specially, with several special services that can be found in e-mocion.
It should be taken into account that these special services are modified and enriched regularly, hence the tested services may change.
It's also tested the e-mocion color menu.

This section describes the exact configuration parameters to be introduced to the terminal in order to access the e-mocion site of Telefonica Moviles Espaņa. Such configuration shall be similar to that specified in document " anexo-1.1-ERD030000-parameters_TME_v3".

The present document intends to be used as a base for the verification of the correct operation of WAP 2.0 browsers, including both the XHTML-MP tags and the design of style sheets with CSS. 
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.
Moreover, it is in the aim of this document to analyze the browser compatibility with the different contents and WAP applications contained in e-mocion, the WAP site of Telefonica Moviles Espaņa.
These tests are based on document 6-ERD030000-WAPv2.doc, which describes the necessary WAP requirements. In each of the rows of the following tables, the first box contains a requirement code which corresponds to the appropriate requirement contained in the specification 6-ERD030000-WAPv2 Requirements Specification. In some cases this box is blank, meaning that the corresponding test has not a specific requirement associated with it.

The present documents intends to be used as a base for the verification of the correct operation of WAP 2.0 browsers, including both the XHTML-MP tags and the design of style sheets with CSS. 
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.

The present documents intends to be used as a base for the verification of the correct operation of WAP 2.0 browsers, including both the XHTML-MP tags and the design of style sheets with CSS. 
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.

The present documents intends to be used as a base for the verification of. 

<br/>---END

--<br/>

The present documents intends to be used as a base for the verification of the correct operation of WAP 2.0 browsers, including both the XHTML-MP tags and the design of style sheets with CSS. 
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.
Moreover, it is in the aim of this document to analyze the browser compatibility with the different contents and WAP applications contained in e-mocion, the WAP site of Telefonica Moviles Espaņa.<br/>

Moreover, it is in the aim of this document to analyze the browser compatibility with the different contents and WAP applications contained in e-mocion, the WAP site of Telefonica Moviles Espaņa.<br/>
These tests are based on document 6-ERD030000-WAPv2.doc, which describes the necessary WAP requirements. In each of the rows of the following tables, the first box contains a requirement code which corresponds to the appropriate requirement contained in the specification 6-ERD030000-WAPv2 Requirements Specification. In some cases this box is blank, meaning that the corresponding test has not a specific requirement associated with it.

The following tests shall be done in the lab network of Telefonica Moviles Espaņa. The web server for tests is:

http://terminales.movistar.com/test.wml

and it is accessible with the e-mocion profile out of the labs.

In the following, we describe the trials protocol to be followed to check the compatibility of the browser with the different XHTML-MP tags and the style sheet elements (CSS). The trials should be performed using the connection with the WSP stack protocol for wap (port 9201) or with the HTTP stack protocol for wap 2.0 (port 8080), or with both, depending on the handset capabilities, which are the mandatory modes for Telefonica Moviles.
The trials shall be done using GPRS access. 

This section describes the exact configuration parameters to be introduced to the terminal in order to access the e-mocion site of Telefonica Moviles Espaņa. Such configuration shall be similar to that specified in document " anexo-1.1-ERD030000-parameters_TME_v3".

These trials intend to characterize the browser's behavior regarding the tags or elements defined in XHTML-MP. 
The tree structure formed by all XHTML-MP test pages shall be browsed through, analyzing the result and visualization shown by the browser, as indicated in section 7.1.
The test pages are grouped, depending on the type of elements to test, in the blocks listed in the following table:

These trials intend to characterize the browser's behavior regarding the style sheets defined in XHTML-MP (WCSS). 
The tree structure formed by all style sheet trial pages shall be browsed through, analyzing the result and visualization shown by the browser, as indicated in section 7.2.
All the elements in these trials will be correctly shown by the browser with the defined style sheet properties.
The test pages are grouped, depending on the type of elements to test, in the blocks listed in the following table:

These trials are intended to check the compatibility of the browser with contents tree of e-mocion. Specially, with several special services that can be found in e-mocion.
It should be taken into account that these special services are modified and enriched regularly, hence the tested services may change.
It's also tested the e-mocion color menu.

The test user shall browse through the contents tree of e-mocion, the WAP site of Telefonica Moviles Espaņa (it should be taken into account that the e-mocion contents are modified and enriched regularly), checking that all contents can be accessed correctly.

In this tests are included static pages with diferent templates of the e-mocion menu with color. It'll be tested which of the existent templates are the most suitable for the browser. It'll will also tested the most appropriate size of the icons to adjust to the screen size. There is  a template in e-mocion: one shows in the screen two icons in every row and another shows only one in every line.
---<br/>
The present document intends to be used as a base for the verification of the correct operation of WAP 2.0 browsers, including both the XHTML-MP tags and the design of style sheets with CSS. 
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.
Moreover, it is in the aim of this document to analyze the browser compatibility with the different contents and WAP applications contained in e-mocion, the WAP site of Telefonica Moviles Espaņa.
These tests are based on document 6-ERD030000-WAPv2.doc, which describes the necessary WAP requirements. In each of the rows of the following tables, the first box contains a requirement code which corresponds to the appropriate requirement contained in the specification 6-ERD030000-WAPv2 Requirements Specification. In some cases this box is blank, meaning that the corresponding test has not a specific requirement associated with it.

The following tests shall be done in the lab network of Telefonica Moviles Espaņa. The web server for tests is:

http://terminales.movistar.com/test.wml

and it is accessible with the e-mocion profile out of the labs.

In the following, we describe the trials protocol to be followed to check the compatibility of the browser with the different XHTML-MP tags and the style sheet elements (CSS). The trials should be performed using the connection with the WSP stack protocol for wap (port 9201) or with the HTTP stack protocol for wap 2.0 (port 8080), or with both, depending on the handset capabilities, which are the mandatory modes for Telefonica Moviles.
The trials shall be done using GPRS access. 

This section describes the exact configuration parameters to be introduced to the terminal in order to access the e-mocion site of Telefonica Moviles Espaņa. Such configuration shall be similar to that specified in document " anexo-1.1-ERD030000-parameters_TME_v3".

These trials intend to characterize the browser's behavior regarding the tags or elements defined in XHTML-MP. 
The tree structure formed by all XHTML-MP test pages shall be browsed through, analyzing the result and visualization shown by the browser, as indicated in section 7.1.
The test pages are grouped, depending on the type of elements to test, in the blocks listed in the following table:

These trials intend to characterize the browser's behavior regarding the style sheets defined in XHTML-MP (WCSS). 
The tree structure formed by all style sheet trial pages shall be browsed through, analyzing the result and visualization shown by the browser, as indicated in section 7.2.
All the elements in these trials will be correctly shown by the browser with the defined style sheet properties.
The test pages are grouped, depending on the type of elements to test, in the blocks listed in the following table:

These trials are intended to check the compatibility of the browser with contents tree of e-mocion. Specially, with several special services that can be found in e-mocion.
It should be taken into account that these special services are modified and enriched regularly, hence the tested services may change.
It's also tested the e-mocion color menu.

This section describes the exact configuration parameters to be introduced to the terminal in order to access the e-mocion site of Telefonica Moviles Espaņa. Such configuration shall be similar to that specified in document " anexo-1.1-ERD030000-parameters_TME_v3".

The present document intends to be used as a base for the verification of the correct operation of WAP 2.0 browsers, including both the XHTML-MP tags and the design of style sheets with CSS. 
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.
Moreover, it is in the aim of this document to analyze the browser compatibility with the different contents and WAP applications contained in e-mocion, the WAP site of Telefonica Moviles Espaņa.
These tests are based on document 6-ERD030000-WAPv2.doc, which describes the necessary WAP requirements. In each of the rows of the following tables, the first box contains a requirement code which corresponds to the appropriate requirement contained in the specification 6-ERD030000-WAPv2 Requirements Specification. In some cases this box is blank, meaning that the corresponding test has not a specific requirement associated with it.

The present documents intends to be used as a base for the verification of the correct operation of WAP 2.0 browsers, including both the XHTML-MP tags and the design of style sheets with CSS. 
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.

The present documents intends to be used as a base for the verification of the correct operation of WAP 2.0 browsers, including both the XHTML-MP tags and the design of style sheets with CSS. 
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.

The present documents intends to be used as a base for the verification of. 
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the .
<br/>---END<br/>


--<br/>

The present documents intends to be used as a base for the verification of the correct operation of WAP 2.0 browsers, including both the XHTML-MP tags and the design of style sheets with CSS. 
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.
Moreover, it is in the aim of this document to analyze the browser compatibility with the different contents and WAP applications contained in e-mocion, the WAP site of Telefonica Moviles Espaņa.<br/>

Moreover, it is in the aim of this document to analyze the browser compatibility with the different contents and WAP applications contained in e-mocion, the WAP site of Telefonica Moviles Espaņa.<br/>
These tests are based on document 6-ERD030000-WAPv2.doc, which describes the necessary WAP requirements. In each of the rows of the following tables, the first box contains a requirement code which corresponds to the appropriate requirement contained in the specification 6-ERD030000-WAPv2 Requirements Specification. In some cases this box is blank, meaning that the corresponding test has not a specific requirement associated with it.

The following tests shall be done in the lab network of Telefonica Moviles Espaņa. The web server for tests is:

http://terminales.movistar.com/test.wml

and it is accessible with the e-mocion profile out of the labs.

In the following, we describe the trials protocol to be followed to check the compatibility of the browser with the different XHTML-MP tags and the style sheet elements (CSS). The trials should be performed using the connection with the WSP stack protocol for wap (port 9201) or with the HTTP stack protocol for wap 2.0 (port 8080), or with both, depending on the handset capabilities, which are the mandatory modes for Telefonica Moviles.
The trials shall be done using GPRS access. 

This section describes the exact configuration parameters to be introduced to the terminal in order to access the e-mocion site of Telefonica Moviles Espaņa. Such configuration shall be similar to that specified in document " anexo-1.1-ERD030000-parameters_TME_v3".

These trials intend to characterize the browser's behavior regarding the tags or elements defined in XHTML-MP. 
The tree structure formed by all XHTML-MP test pages shall be browsed through, analyzing the result and visualization shown by the browser, as indicated in section 7.1.
The test pages are grouped, depending on the type of elements to test, in the blocks listed in the following table:

These trials intend to characterize the browser's behavior regarding the style sheets defined in XHTML-MP (WCSS). 
The tree structure formed by all style sheet trial pages shall be browsed through, analyzing the result and visualization shown by the browser, as indicated in section 7.2.
All the elements in these trials will be correctly shown by the browser with the defined style sheet properties.
The test pages are grouped, depending on the type of elements to test, in the blocks listed in the following table:

These trials are intended to check the compatibility of the browser with contents tree of e-mocion. Specially, with several special services that can be found in e-mocion.
It should be taken into account that these special services are modified and enriched regularly, hence the tested services may change.
It's also tested the e-mocion color menu.

The test user shall browse through the contents tree of e-mocion, the WAP site of Telefonica Moviles Espaņa (it should be taken into account that the e-mocion contents are modified and enriched regularly), checking that all contents can be accessed correctly.

In this tests are included static pages with diferent templates of the e-mocion menu with color. It'll be tested which of the existent templates are the most suitable for the browser. It'll will also tested the most appropriate size of the icons to adjust to the screen size. There is  a template in e-mocion: one shows in the screen two icons in every row and another shows only one in every line.
---<br/>
The present document intends to be used as a base for the verification of the correct operation of WAP 2.0 browsers, including both the XHTML-MP tags and the design of style sheets with CSS. 
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.
Moreover, it is in the aim of this document to analyze the browser compatibility with the different contents and WAP applications contained in e-mocion, the WAP site of Telefonica Moviles Espaņa.
These tests are based on document 6-ERD030000-WAPv2.doc, which describes the necessary WAP requirements. In each of the rows of the following tables, the first box contains a requirement code which corresponds to the appropriate requirement contained in the specification 6-ERD030000-WAPv2 Requirements Specification. In some cases this box is blank, meaning that the corresponding test has not a specific requirement associated with it.

The following tests shall be done in the lab network of Telefonica Moviles Espaņa. The web server for tests is:

http://terminales.movistar.com/test.wml

and it is accessible with the e-mocion profile out of the labs.

In the following, we describe the trials protocol to be followed to check the compatibility of the browser with the different XHTML-MP tags and the style sheet elements (CSS). The trials should be performed using the connection with the WSP stack protocol for wap (port 9201) or with the HTTP stack protocol for wap 2.0 (port 8080), or with both, depending on the handset capabilities, which are the mandatory modes for Telefonica Moviles.
The trials shall be done using GPRS access. 

This section describes the exact configuration parameters to be introduced to the terminal in order to access the e-mocion site of Telefonica Moviles Espaņa. Such configuration shall be similar to that specified in document " anexo-1.1-ERD030000-parameters_TME_v3".

These trials intend to characterize the browser's behavior regarding the tags or elements defined in XHTML-MP. 
The tree structure formed by all XHTML-MP test pages shall be browsed through, analyzing the result and visualization shown by the browser, as indicated in section 7.1.
The test pages are grouped, depending on the type of elements to test, in the blocks listed in the following table:

These trials intend to characterize the browser's behavior regarding the style sheets defined in XHTML-MP (WCSS). 
The tree structure formed by all style sheet trial pages shall be browsed through, analyzing the result and visualization shown by the browser, as indicated in section 7.2.
All the elements in these trials will be correctly shown by the browser with the defined style sheet properties.
The test pages are grouped, depending on the type of elements to test, in the blocks listed in the following table:

These trials are intended to check the compatibility of the browser with contents tree of e-mocion. Specially, with several special services that can be found in e-mocion.
It should be taken into account that these special services are modified and enriched regularly, hence the tested services may change.
It's also tested the e-mocion color menu.

This section describes the exact configuration parameters to be introduced to the terminal in order to access the e-mocion site of Telefonica Moviles Espaņa. Such configuration shall be similar to that specified in document " anexo-1.1-ERD030000-parameters_TME_v3".

The present document intends to be used as a base for the verification of the correct operation of WAP 2.0 browsers, including both the XHTML-MP tags and the design of style sheets with CSS. 
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.
Moreover, it is in the aim of this document to analyze the browser compatibility with the different contents and WAP applications contained in e-mocion, the WAP site of Telefonica Moviles Espaņa.
These tests are based on document 6-ERD030000-WAPv2.doc, which describes the necessary WAP requirements. In each of the rows of the following tables, the first box contains a requirement code which corresponds to the appropriate requirement contained in the specification 6-ERD030000-WAPv2 Requirements Specification. In some cases this box is blank, meaning that the corresponding test has not a specific requirement associated with it.

The present documents intends to be used as a base for the verification of the correct operation of WAP 2.0 browsers, including both the XHTML-MP tags and the design of style sheets with CSS. 
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.

The present documents intends to be used as a base for the verification of the correct operation of WAP 2.0 browsers, including both the XHTML-MP tags and the design of style sheets with CSS. 
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.

The present documents intends to be used as a base for the verification of. 
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the behavior, visualization and interface shown to the user by them.
The goal is not only to check the compatibility with the different tags and libraries, but also characterize the .
<br/>---END

	</p>


</body>
</html>