Try to reboot/restart/disconnect-reconnect your client registered with Voxalot.
Yesterday after I had a couple of hours when Voxalot was only replying “busy”, my ATA went crazy – its other line registered with another provider replied busy as well.
Well, disconnecting it from power helped.
I’m not sure, but there might be something about hung socket connection, or some state variable that made parties to think they’re busy…
|