Author Topic: tassazione https  (Read 10761 times)

0 Members and 1 Guest are viewing this topic.

Offline Lucky

  • Hero Member
  • *****
  • Posts: 741
  • Karma: +14/-0
    • View Profile
tassazione https
« on: November 16, 2012, 08:18:13 pm »
Sto combattendo con la tassazione di un lx v3 r3.2.0, nella documentazione scrivono che il formato esteso funziona solo in https mentre in tcp il formato é solo compresso.
L' account manager funziona solo in compresso con protocollo https.
Allora
non capisco come leggere i dati di tassazione in formato non compresso.
Qualcuno sa darmi qualche dritta?
« Last Edit: November 16, 2012, 08:30:01 pm by Lucky »

Offline Kimera

  • Global Moderator
  • Hero Member
  • ****
  • Posts: 1.196
  • Karma: +42/-3
  • Kimera (Ars Gratia Artis)
    • View Profile
    • SIEMENS Enterprise Wiki
Re: tassazione https
« Reply #1 on: November 16, 2012, 09:29:49 pm »
Ciao Lucky,

da quel che so il CDR viene esportato solo in formato compresso (a differenza di quel che avviene in HiPath 3000) che, tra l'altro, viene utilizzato dall'Accounting Manager.

CDR Output Format

An OpenScape Office CDR contains several fields for specific data of the call. Fields are delimited by the " | " sign. The field content is filled with the appropriate information of the call. If information for a field is missing, a “blank” sign is inserted instead.

Più precisamente:

Compressed and Uncompessed Output Format

OpenScape Office supports only the “Compressed” output format. Coding is done in ASCII 8-Bit in general

Compressed Format

The fields are delimited by a | sign.
The end of a CDR is indicated by CR LF (carriage return, line feed)

Examples (Compressed Format):

- Example n°1 “Output LCR number ... is set
20.06.12|13:11:35|201|33388|00:02|00:00:07|0123456789||1||||||

- Example n°2 “Output LCR number ... is not set
20.06.12|13:21:14|202|33388|00:05|00:00:12|0123456789||1|||||

Uncompressed Format

The uncompressed format as known from HiPath 3000, where unavailable information and missing characters are replaced by blanks, is not supported by OpenScape Office.
If the “Uncompressed” format is chosen within the administration the CDR output is done in compressed format nevertheless, but with following differences to “Compressed” format:

1. The first line of the Output file contains the field meaning in plain ASCII.
2. Only fields 1 to 13 (not US) are available within the CDR.
3. The uncompressed format cannot be processed by the Accounting Manager of OpenScape Office

Examples (Uncompressed Format):

- Example n°1 “Output LCR number ... is set
Datum|Uhrzeit|Lt|Tln|Ruf|Dauer|Rufnummer|Betrag|I|
20.06.12|12:53:45|201|33388|00:04|00:00:04|01706340803||1|

- Example n°2 “Output LCR number ... is not set
Datum|Uhrzeit|Lt|Tln|Ruf|Dauer|Rufnummer|Betrag|I|
20.06.12|13:38:27|202|33388|00:02|00:00:05|01706340803||1|


Il Download avviene sicuramente attraverso una richiesta GET ben formata attraverso il protocollo HTTPS (Quindi porta 443) contro l'IP Address dell'OSO LX.

Saluti, Kimera.
« Last Edit: November 16, 2012, 09:32:17 pm by Kimera »
(Ethical) Hackers are not just skilled, they are lucky people and they are persistent people. It's a combination of all three.
"Die Lösung ist immer einfach, man muss sie nur finden" Alexander Solschenizyn

I'm all for being a Partner, and a Professional. But if you want me to sell your products...you need to scratch my back a little too.

Offline Lucky

  • Hero Member
  • *****
  • Posts: 741
  • Karma: +14/-0
    • View Profile
Re: tassazione https
« Reply #2 on: November 16, 2012, 10:50:32 pm »
Quindi il flag serve a poco o niente.
Mi trovo davanti a un bel problema, il cliente usa già un software (che gestisce altre macchine) che non supporta il formato compresso.
Devo trovare un modo per esportare in automatico e riformattare le stringhe, ahi ahi ahi.