A800P Echo Elastix 2.0.3

techchip

Joined
Aug 10, 2010
Messages
25
Likes
0
Points
0
#1
Hi:

We are having an Echo problem while calling from elastix 2.0.3 to PSTN using a A800P card.

The Echo is only heard from inside VOIP PBX phones. There is not Echo on PSTN side.

Calling from internal extension to other internal extension, there is no echo.

Regards,

Mauricio F.
 

tivo

Joined
Jul 21, 2010
Messages
18
Likes
0
Points
0
#2
I have the same problem too.
I tried fxotune but it doesn't go away.
Another problem I have is that the hardware detector keeps undetecting my 4 PSTN.
All the 8 ports are red. If I detect hardware again it shows up and can be used.
But after a few hours it drops all the line again.
I have to repeat the hardware detection and the lines are up again.
Not too sure what is wrong.

The worst of it (I am using 64bit), when I upgrade using "yum update -y" (I am using the latest iso download recently but did the update nonetheless) the whole dahdi broke. When restarting it will not be able to load the dahdi drivers. In the end no hardware gets detected on the web gui. I have to reinstalled again.

I feel something is really wrong with elastix at the moment. Something must be done to fix this. Thanks.
 

tivo

Joined
Jul 21, 2010
Messages
18
Likes
0
Points
0
#3
Another thing I wanted to add..
I have loads of printk: x messages suppressed
After a reboot from a fresh installation, the printk messages start popping up.
And it never stop...
 

lisa.gao

Joined
Jul 1, 2010
Messages
39
Likes
0
Points
0
#4
Hi techchip,
Do you open software echo canceler? You can configure your /etc/dahdi/system.conf like the following:
-------------------------------------
fxsks=1
fxsks=2
fxoks=3
fxoks=4
...
echocanceller=oslec,1-8
-------------------------------------

Next run dahdi_cfg -vvvv, and then restart asterisk.

If any problem, please contact me. My MSN:lingergao@hotmail.com or G talk:eek:pvgaoling@gmail.com
 

lisa.gao

Joined
Jul 1, 2010
Messages
39
Likes
0
Points
0
#5
Hi tivo,
For echo issue,please follow the configure in system.conf.
For the detection and system issue, please don't upgrade using "yum update", it will destroy the structure of your system.
If any problem, please contact us.
 

tivo

Joined
Jul 21, 2010
Messages
18
Likes
0
Points
0
#6
Here is my dahdi system.conf

# Autogenerated by /usr/sbin/dahdi_genconf on Thu Feb 17 09:46:20 2011
# If you edit this file and execute /usr/sbin/dahdi_genconf again,
# your manual changes will be LOST.
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: WCTDM/0 "Wildcard TDM800P Board 1" (MASTER)
fxsks=1
echocanceller=oslec,1
fxsks=2
echocanceller=oslec,2
fxsks=3
echocanceller=oslec,3
fxsks=4
echocanceller=oslec,4
fxsks=5
echocanceller=oslec,5
fxsks=6
echocanceller=oslec,6
fxsks=7
echocanceller=oslec,7
fxsks=8
"system.conf" 29L, 606C

Funny thing is there is no echo canceller for the last port.
 

tivo

Joined
Jul 21, 2010
Messages
18
Likes
0
Points
0
#7
Another thing is I don't have zapata.conf file only the template.
Should I create one?
Thanks.
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#8
Re: Re:A800P Echo Elastix 2.0.3

"please don't upgrade using "yum update", it will destroy the structure of your system.
If any problem, please contact us."

whats that???
if people dont know how to compile your own patches to digium dahdi official driver it must not use that cards. Simple.
 

tivo

Joined
Jul 21, 2010
Messages
18
Likes
0
Points
0
#9
Re: Re:A800P Echo Elastix 2.0.3

fmvillares wrote:
whats that???
if people dont know how to compile your own patches to digium dahdi official driver it must not use that cards. Simple.[/quote]

So based on your logic, people who can't cook the food they eat should just stop eating those food. People who can't fix their plumbing should just stop using the toilet and crap on the floor. Only a egoistic and myopic fool follow such simpleton logic.

This is a community help forum. This forum is not for your private narcissistic voyeurism. Please don't leave any useless sarcastic banter if you have nothing constructive to add. If you think you are too good for this forum, then I feel sorry for you. Just don't stop others from helping each other.
 

techchip

Joined
Aug 10, 2010
Messages
25
Likes
0
Points
0
#10
Hello Guys:

Take it easy. Please remember that asian people just
don't think like us, western people.

Even worse if they don't speak english fluently. I'm
sure that what Lisa wanted to said is that is better to
contact her before using yum where if you don't know
what you are doing you can damage your system.

You must take in care that she is directly from openvox
and she is trying to help everybody that is using her
product even with its personal email.

Regards,

Mauricio
 

techchip

Joined
Aug 10, 2010
Messages
25
Likes
0
Points
0
#11
hello everybody:

I have already solved my echo problem.

The hardware auto detection on distro 2.0.3 is not working, so that was the reason why dahdi-channels.conf file and system.conf were missing.

Of course without that files there was no echo software canceller active.

1. using putty ingrese to log as root in linux
2. execute script dahdi_genconf (missing files created).
3. execute script dahdi_cfg -vvv
4. restart dahdi using: /etc/init.d/dahdi restart
5. stop asterisk with: amportal stop.
6. fxotune -i 4 to calibrate fxo channels
7. make sure to write line: /usr/sbin/ fxotune-s , in path: /etc/rc.local (it was already there).
8. amportal start.
9. asterisk -rx dahdi show channels

that's all folks, no echo, no missing files.
 

lisa.gao

Joined
Jul 1, 2010
Messages
39
Likes
0
Points
0
#12
Dear tivo and techchip,
Thanks very much for your understanding. I'm so glad to hear that techchip's problem has been solved.

Dear tivo:
1) zaptel.conf is the configure file for driver zaptel. The driver Elastix 2.0.3 use is dahdi, which upgrade from zaptel. The configure file for dahdi is /etc/dahdi/system.conf and /etc/asterisk/dahdi-channels.conf, you can check that.

2) And you can add oslec on channel 8.
But after you run dahdi_genconf, it will autogenerate system.conf

3) And in another way you can edit /etc/dahdi/genconf_parameters like the following:
Default:
------------------------------------
#echo_can oslec
#echo_can none # to avoid echo canceler altogether
------------------------------------

Please remove #
------------------------------------
echo_can oslec
#echo_can none # to avoid echo canceler altogether
------------------------------------
This way will augoconfigure oslec when you run dahdi_genconf

My duty is to try my best to help you all.
 

tivo

Joined
Jul 21, 2010
Messages
18
Likes
0
Points
0
#13
I am listing my conf files that has been with me since installation.

Below is my chan_dahdi.conf

; Auto-generated by /usr/sbin/hardware_detector
[trunkgroups]

[channels]
context=from-zaptel
signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
faxdetect=incoming
;echotraining=800
rxgain=0.0
txgain=0.0
callgroup=1
pickupgroup=1

;Uncomment these lines if you have problems with the disconection of your analog lines
busydetect=yes
busycount=1


immediate=no

#include dahdi-channels.conf
#include chan_dahdi_additional.conf


Below is my dahdi-channels.conf

; Autogenerated by /usr/sbin/dahdi_genconf on Fri Feb 18 15:20:15 2011
; If you edit this file and execute /usr/sbin/dahdi_genconf again,
; your manual changes will be LOST.
; Dahdi Channels Configurations (chan_dahdi.conf)
;
; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended
; to be #include-d by /etc/chan_dahdi.conf that will include the global settings
;

; Span 1: WCTDM/0 "Wildcard TDM800P Board 1" (MASTER)
;;; line="1 WCTDM/0/0 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 1
callerid=
group=
context=default

;;; line="2 WCTDM/0/1 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 2
callerid=
group=
context=default

;;; line="3 WCTDM/0/2 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 3
callerid=
group=
context=default

;;; line="4 WCTDM/0/3 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 4
callerid=
group=
context=default

;;; line="5 WCTDM/0/4 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 5
callerid=
group=
context=default

;;; line="6 WCTDM/0/5 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 6
callerid=
group=
context=default

;;; line="7 WCTDM/0/6 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 7
callerid=
group=
context=default

;;; line="8 WCTDM/0/7 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 8
callerid=
group=
context=default

So far my echo has dissapeared. But the line keep being drop.
 

tivo

Joined
Jul 21, 2010
Messages
18
Likes
0
Points
0
#14
This is currently keep happening, every few hours (1-2 hours) my 4 pstn line will get dropped. I cannot call out or get calls in. To get the line back, I have to click on "detect new hardware". Only then the line will come back on and I get to see four green fxo ports. Why is this happening?

As for my echo problem, it fixed itself after running fxotune yesterday.
Thanks.
 

lisa.gao

Joined
Jul 1, 2010
Messages
39
Likes
0
Points
0
#15
Hi,
Would you please set busycount to 3 or 5 to have a try.
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#16
Re: Re:A800P Echo Elastix 2.0.3

jeje typical noob talk...if you dont know how to cook you buy a book or seek in google or ask a relative how to do it in a respectful manner and learn how to cook food..about crap well in some countries is normal so...its cultural to crap on the floor

the idea is simple...f you dont know the basics...you cant use it until you learn first...and before you can learn about compiling a patch for a card there is much more learning to do

for example...dahdi driver involves several items...
it depends on the kernel so changing or upgrading kernels must lead to a new dahdi compile...
some openvox cards are not dahdi native card and needs patchs to apply to dahdi to recompile over...do you see the logic....
if i dont know anything about a cheese how do i know if it is rotten or simply a smelly and delicious camembert...
 

techchip

Joined
Aug 10, 2010
Messages
25
Likes
0
Points
0
#17
Hi Tivo:

Did you solve your call drop problem?

Please replace the following line on chan_dahdi.conf file

context=from-zaptel ---> context=from-pstn

also replace busycount=1 ---> busycount=3 if it doesn't work ---> busycount=5

Then restart the machine

Regards,

Mauricio
 

lisa.gao

Joined
Jul 1, 2010
Messages
39
Likes
0
Points
0
#18
Hi tivo,
Please try these:
Set busycount to 3 or 5 to have a try.
Run dahdi_test, and check the result.
Run cat /proc/interrupt to ensure opvxa1200 to have independent IRQ.
 

Gelevera

Joined
Aug 22, 2010
Messages
143
Likes
0
Points
0
#19
tivo said:
Here is my dahdi system.conf

# Autogenerated by /usr/sbin/dahdi_genconf on Thu Feb 17 09:46:20 2011
# If you edit this file and execute /usr/sbin/dahdi_genconf again,
# your manual changes will be LOST.
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: WCTDM/0 "Wildcard TDM800P Board 1" (MASTER)
fxsks=1
echocanceller=oslec,1
fxsks=2
echocanceller=oslec,2
fxsks=3
echocanceller=oslec,3
fxsks=4
echocanceller=oslec,4
fxsks=5
echocanceller=oslec,5
fxsks=6
echocanceller=oslec,6
fxsks=7
echocanceller=oslec,7
fxsks=8
"system.conf" 29L, 606C

Funny thing is there is no echo canceller for the last port.
Hi tivo. I had the same problems with zycoo ZA16P 16ch card.
i change my "oslec" echo canceller to "mg2" and works great.
Or installing the dahdi driver 2.3.x.x. and dahdi tools.
The 2.4.x.x.x version have echo problems..


Hola Tivo. Tube el mismo problema con la tarjeta de Zycoo ZA16P de 16 canales
Cambié mi cancelador de eco "oslec" por el "mg2" y funciona muy bien..
o tambien instalando los drivers de dahdi 2.3.x.x. y dahdi tools.
La version 2.4.x.x. tiene problemas con el eco.
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#20
Re: Re:A800P Echo Elastix 2.0.3

estuve trabajando con gente de sangoma y el asunto esta en que cambio el api de cancelacion de eco entre la version 2.3.0.1 de dahdi y la 2.4.0, solo afecta a tarjetas que requieren drivers extras al dahdi original
lease sangoma, y todos los clones chinos y de otros paises que requieren drivers compilados extras como zycoo, openvox, yeastar, etc
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,902
Messages
130,886
Members
17,563
Latest member
dineshr
Top