peterfillmore / iso8583py Goto Github PK

There are acquirers out there who have modified the ISO8583 from the spec. 
(redefineBit works great), however, some acquirers also insert a header of 
their own design between the initial length indicator and the MTI.

For example, the original....

    [LL] [MTI] [bitmap1]...

where the vendor wants to see:

    [LL] [HEADER] [MTI] [bitmap1]...

Since I'm already overriding __init__() in order to redefine some of the BITs, 
I could also override this function... Wouldn't it be better to provide the 
header in a param as part of the init? or maybe as part of the getter/setter?

Hello,as I promised yesterday, here is a module which contains the MUX class.

Basically is a Thread with the method MUX.request(isoMsg,timeout=None) 

The usage is the following:

mux = MUX(server_address,server_port,default_timeout)
mux.start()
isoMsg = createMsg()
isoResp = mux.request(isoMsg) #This method queue the message and waits for 
                              #the response for default_timeout seconds,
                              #if no response is received, it returns None

Hi:

ASCII to process 
<0110F23A40010A80800000000000060000011688888888888888884010000000000001000702014
92700000601492707020702601106179200059490124182007217211115616888888888888888819
1111111111111111111AE3D1B33>

becase bit128=1,so there is error in ISO8583.py
I have changed something in py file, please diff it with vim.

Hello, I'm very interested in this project but: is still alive?
greetings

Q1:ISO8583 structure problem
  ISO8583 is the structure : msg-len+TPDU+MSG
  I test your module. I do not find it(TPDU).  

Q2: ISO8583 sending message:
1.msg_len  is nible  type
2.MTI is nible type also. e.g MTI='0200'
3.F41/F42 is char type.e.g F41='12345678'
So,After  the step ,message = iso.getNetworkISO().
If I use binascii.b2a_hex(message),
 MTI is 0200, F41 should be 31323435363738.

What steps will reproduce the problem?
1. p = ISO8583()
2. p.setBit(18, 6011)
3. v1 = p.getBitsAndValues()

What is the expected output? What do you see instead?
6011 , 0046011


What version of the product are you using? On what operating system?
Module1.0

Please provide any additional information below.

What steps will reproduce the problem?
1.When install your library, none of the examples are functional. All exhibits 
the same error:
Traceback (most recent call last):
  File "/home/pablo/temp/Iso 8583/teste.py", line 20, in <module>
    from ISO8583.ISO8583 import ISO8583
  File "/usr/local/lib/python3.3/dist-packages/ISO8583/ISO8583.py", line 26, in <module>
    from ISOErrors import *
ImportError: No module named 'ISOErrors'

In my case, works if i change from ISOErrors import * to from ISO8583.ISOErrors 
import *

What version of the product are you using? On what operating system?
version 1.3 linux (ubuntu 13.10). Ii installed via pip

Please provide any additional information below.

how to get field 64(Message Authentication Code)? thank!

Is there any reason why you are including the string size in the LL and LLL 
data fields ?

For example: DE2 is supposed to have 16 bytes, but it is returning 18 - it 
includes the field size.
Ex: 165544334455667766

The same applies to DE 61, 63, and others.

Tks.

Robson

Here is the 0820 message that I generated. Notice that I omitted the length and 
that the first 4 bytes are the MTI. (this string wear produced with pprint().

'0820\x82 
\x00\x00\x00\x00\x00\x00\x04\x00\x00\x00\x10\x00\x00\x00021717045803156330108250
00344'

It's not interesting to note that the 6th-byte of the message or the 2nd-byte 
of the bitmap field resolved to a \x20 or a space.

when __getBitmapFromStr() attempted to parse the first byte in this code:

if (int(bitmap[0:2],16) & self._BIT_POSITION_1)  .....

I receive a value error because int() does not like the space in the string. 
For example try these:

int("\x82\x20")
int("\x82 ")

They are the same value and they both generate the error. I think you should 
consider using the struct.unpack() instead of int().

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?
n/a

Please provide any additional information below.
_BITS_VALUE_TYPE[40] = ['40','Service code','N3',3,'an']
N3 is correct ? 

Looking at the spec for ISO8583, field 41 is incorrect in the ISO8583.py file 
where it is limited to 8 ANS chars when the semi official spec on Wikipedia 
says it is 16 ANS chars.

Hello, this is not an actual issue, I'm sorry, but didn't find another
place to ask:

I'm planning to use iso8583py in a django project as a middleware between
the mobile clients(who send http requests) and a JPOS who make the actual
connections with the Switch.

For that I need to send to the JPOS server a message with a binary field
52, where the 6 digits NIP goes, for that I do something like: 
msg.setBit(52,123456)
msg.redefineBit(52, '52', msg.getLargeBitName(52), 'B', 6,"n" )

So far so good, in the JPOS server I got:

<field id="52" value="0000000000123456" type="binary"/>

The problem is: that value is not the binary representation of the NIP, in
java I would do:

msg.set(52, "123456".getBytes());

I have searched the web but I haven't found anything like that for python,
what do you use?

Ah, BTW, I wrote something like the ISOMUX of JPOS, I made it based on
Queue.Queue() and it have a really nice performance, when I test it a  bit
more I will send it to you, in case it helps.

good luck

According to the ISO spec, DE 18 should be N -> 4, but your class is setting 
LLL and cause an exception. Fixed it subclassing ISO8583, but would be nice to 
get it patched:

self._BITS_VALUE_TYPE[18] = ['18','Message error indicator','N',4,'n']

Regards,

What steps will reproduce the problem?
1. p.setBit(52,"00000105")

What is the expected output? What do you see instead?

Want that the bit is set!

The bit wasn't set. But if you started debug you can see the bit inside the
bitmap is set, but the value not.

What version of the product are you using? On what operating system?
Last version, Any.


In log we can see the execution of example1.py with p.setBit(52,"00000105")
in debug mode.