NumberMatching bug in AMTCards 1.6.3.1 and 1.6.3.2

[Belinda Frick]

Problem description

There's a bug in the 1.6.3.1 and 1.6.3.2 Cardserver software where
it enables number matching for all cards, regardless of the previous
setting.

Result: Calls can be dropped due to number matching.

Cause

When it converts the PCI slot information in the INI file to a
PCI Bus / PCI slot combination, it looks for a PCI slot and channel
instead of a PCI slot alone. Since it doesn't find the entry, it
uses the default value, which is to enable number matching for that
card.

More details on Number matching please check here.

An example might explain it better. It converts this:


Code: Select all

[NUMBERMATCHING]
3=0
1=0
2=3



to this:



Code: Select all

[NUMBERMATCHING]
1003=3
1001=3
1002=3



because it looked for something like 2_11=3 in the number matching
section, and can't find it.

It will be fixed in 1.6.3.3.