Cardserver(127.0.0.1) is not responding to Amethyst server

[Belinda Frick]

Overview

It has happened that the cardserver service has started up
before the network has been succesfully established. The
service then starts up with IP address 127.0.0.1.

The recordings where sent to AMETHYST from cardserver
127.0.0.1 and were rejected.

Solution

As a workaround the "cardserver" 127.0.0.1 was added
to AMETHYST. under:

"Configure cardserver IP"

This resolved that calls were being rejected coming from the
cardserver before the network connection was established.

AMETHYST tries to ping the 127.0.0.1 cardserver service but
it fails to respond. It is then that a critical email gets
sent.

To ensure that the cardserver critical error is not sent
anymore:
In the "Inclusive Rules", please edit the extension
rules (click on "edit" next to the extension range
rule).
This will allow you to untick both cardservers.
The "inclusive rules" will now display "All Servers".
Please click on "Save Changes".
Once all the rules has been changed, please click on
"Apply Changes".


***Under investigation***