NO JOY Sangoma A200 dialing trouble

CoinTos

Member
Joined
Jan 5, 2012
Messages
34
Reaction score
7
So I manged to get one of those Sangoma A200 from that 75% promotion and it's been nothing but trouble. After fighting with irq and such to get the dahdi_test to be decent I now have issue with configs, one minute it's working the next is the problem below.

The problem I am currently having is when I dial from my cordless attached to the card it drop the area code, so 915551234567 becomes 91234567 and 95551234567 becomes 91234567.

I can't figure out what config to look in, any suggestion would be helpful.

│ PIAF Installed Version = 2.0.6.4 under *HARDWARE*
│ FreePBX Version = 2.11.0.2
│ Running Asterisk Version = 11.4.0
│ Asterisk Source Version = 11.4.0
│ Dahdi Source Version = 2.6.2
│ Libpri Source Version = 1.4.12
│ Operating System = CentOS release 6.4 (Final)
│ Kernel Version = 2.6.32-358.6.2.el6.x86_64 - 64 Bit

edit: Noticed I still had dahdi config installed from my previous card, uninstalled it and it has seem to fix the problem. Don't know for sure but time will tell.
 
I was going to say to check your outbound routes and trunk dialing patterns. Looks like you are stripping digits. Let us know if it is indeed fixed.
 
That is what I thought before I posted and it wasn't the case. This only affected my dahdi extension. It also after I 'fixed' the out bound issue, had it stripping the first digit off my dialing of extensions.

So I figured I would uninstall wanpipe and start fresh without dahdi config, now i have really bad dahdi_test results but both dailing work. I have since removed wan pipe again and now starting dahdi with asterisk doesn't work. So I am guessing it's time I reinstall fresh and downgrade my dahdi to 2.6.2 since the new pay has 2.7.0 and manual restore everything. To see if I can get it all working.

Is there anything I shouldn't be doing in the wanpipe install? Like not setting load on boot or something?
 
Just wanted to give an update on this issue. I got it working with 9+npa numbers but internal was still broken. A month a half later I have just got time to reinvestigate it and it turns out to an issue with the hardware echo canceller. Using the debugging information on sangoma I found that digging deeper was my answer to the issue, running the command:

Code:
wan_ec_client wanpipe1 disable

Allowed both internal and external calls to work without missing any digits. Next I will have to figure out the hwec recording and contact sangoma support.
 

Members online

Forum statistics

Threads
26,687
Messages
174,410
Members
20,257
Latest member
Dempan
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Back
Top