Thanks Vladimir for the response and apologies for my extremely late
one! This week was quite crazy!!
I have just upgraded my server to FreePBX to take advantage of an
up-to-date system.
I migrated the original config over with a few set changes.
On 05/14/2012 04:42 AM, Vladimir Mikhelson
Hi,
I'm using Trixbox 2.8 edition and having issues with my PSTN line and
the OpenVox A400P card.
During purchase I decided to go for the 1xFXS and 1xFXO option.
I hooked the PSTN and my POTs DECT phone up correctly and configured the
appropriate trunks, routes, and extensions.
The
On 13 May 2012 17:05, Kaya Saman kayasa...@gmail.com wrote:
[May 13 13:15:49] DEBUG[3056] pbx.c: FONALITY: This thread has already
held the conlock, skip locking
You should really be posting on the trixbox forums.
--
_
--
You should really be posting on the trixbox forums.
I did and no one there could help as it turns out Trixbox is EOL.
Since Trixbox is indeed Asterisk I thought that I should post here as
there might be more people who know about dahdi and my issue.
However, if this isn't the right
As a first step, I would verify the problem is not in the phone itself. Can
you duplicate the behavior with a different telephone? Does the handset act
properly when connected directly to your PSTN line?
If these tests still indicate the problem is on the trixbox, can you verify
you changed
Thanks for the response!
On 05/13/2012 09:41 PM, Stephen J Alexander wrote:
As a first step, I would verify the problem is not in the phone
itself. Can you duplicate the behavior with a different telephone?
Does the handset act properly when connected directly to your PSTN line?
Kaya,
I do not have a definitive answer for you, but here are several things I
noticed.
1. fxo*ls*=1 -- I would definitely try /fxoks/ instead
fxs*ls*=2 -- I am not sure about your provider but I would try
/fxsks/ instead
2. [May 13 13:15:31] WARNING[3624]
