| Subject: | ESDC signing invoice fails using inspur ESDC firmware 1.0.4.4 |
| Summary: | Hi Asheel,
Avneel downgraded Inspur from V1.0.4.4 to 1.0.4.3 and I am now able to sign the invoices.
Here is a brief on what was happening on V1.0.4.4: - Attention command is returning successfully
- GetStatus command is returning successfully
- IsPinRequired and Pin insertion is working correctly
- Audit Status command is returning successfully
- Invoice Sign is returning a empty object. (This issue is not happening on 1.0.4.3)
Here is the JSON file I am signing.
Let me know if you would like me to do a conference session with Inspur developers to look into the issue.
JSON file for signing {
"DateAndTimeOfIssue": "2019-07-30T09:51:40.8470000",
"Cashier": "admin [223344]",
"BD": "",
"BuyerCostCenterId": "",
"IT": 0,
"TT": 0,
"PaymentType": 0,
"InvoiceNumber": "TX000022",
"ReferentDocumentNumber": null,
"Options": {
"OmitTextualRepresentation": "0",
"OmitQRCodeGen": "0"
},
"Items": [
{
"GTIN": null,
"Name": "Anchor Lite Milk 1L",
"Quantity": 1.00,
"UnitPrice": 10.00,
"Discount": 0.00,
"Labels": [
"A"
],
"TotalAmount": 10.00
}
]
}
Regards Sanjay Singh Managing Director & Founder B Sc, PGDTE, MCSD, MIT
Mobile:+ 61(0) XXX-XXX-XXX |
| Audit Notes: | Edited by sanjay on 13/05/20 09:38. |
| 25 Mar 2020 | 09:29AM Comment 1 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 25-03-2020 03:28 PM Time Taken: 16.00 |
| *** Email from Tax Core ***
Date: 30/07/19 17:51 (GMT+12:00) Subject: Fwd: ESDC signing invoice url using inspur ESDC provided by Datec Fiji Hi Guys, see email from Taxcore. Can we try downgrading the firmware tomorrow morning as suggested by Asheel?. I'll be available from 8 am aest, skype me when ready.
Mobile:+ 61(0) XXX-XXX-XXX
## -- PLEASE REPLY ABOVE THIS LINE -- ## Dear Sanjay Singh,Dear Sanjay,
There were no changes regarding signing url, your request is in order also.
it is most likely due to device you are using, please contact inspur to resolve this issue. Your TaxCore Support Team,
Best Regards,
Nenad Nikic.
.Net Developer |
|
| 25 Mar 2020 | 09:34AM Comment 2 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 25-03-2020 03:29 PM Time Taken: 12.00 |
| Skype message from Asheel on 25/03/2020 - Inspur support has asked us to place the Payment type as a String. LinkPOS is placing this as an INT
- Zyenal to send Sanjay Inspur Firmware 1.0.4.4 to make the change and verify
The following changes have been completed and tested in InSpur 1.0.4.3 - Changed PaymentType, InvoiceType and TransactionType from Int to String
- Added "Training" mode
- Changed Payment Type to pick LinkSOFT Payment Type when a single Payment Type is used, otherwise, we use "Other"
Nest Step: - Waiting for Zyenal to send Inspur Firmware 1.0.4.4
- Sanjay to run tests to ensure this works on the new Firmware
- Sanjay to Test VSDC and SOFTSDC as this is a common function for all TMS
|
|
| 25 Mar 2020 | 10:41AM Comment 3 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 25-03-2020 04:40 PM Time Taken: 6.00 |
| Hi all, Inspur firmware 1.0.4.4 issue resolved, thanks Asheel and Zyenal for following up with Inspur Support. The issue was to do with the Payment Type - required: String, we were sending it as an Int
We will have this change in LinkSOFT 11.5 - ETA this week as soon as Prasant confirms Certification with FRCS |
|
| 25 Mar 2020 | 11:49AM Comment 4 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 25-03-2020 05:47 PM Time Taken: 4.00 |
| Hi Guys, false alarm. When I restarted the Inspur Device, invoice signing failed with the exact same symptoms as before. I have downgraded the firmware to 1.0.4.3 and the invoices are signing correctly. Please check with Inspur Support on what we need to do next. thx |
|
| 25 Mar 2020 | 11:50AM Comment 5 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 25-03-2020 05:50 PM |
| Seems like the Firmware upgrade does not take effect unless the device is restarted |
|
| 25 Mar 2020 | 03:52PM Comment 6 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 25-03-2020 09:50 PM Time Taken: 3.00 |
| Corrected the issue by implementing the following changes:- ESDC device date and time needs to align with POS data and time
- Changed IT, TT and Payment type to String
Performed the following tests: - Inspur Firmware 1.0.4.3
- Inspur Firmware 1.0.4.4
- Samoa V-ESDV
|
|