problem with outgoing DAHDI only

mjopling

New Member
Joined
Dec 5, 2007
Messages
24
Reaction score
2
I've had success using SIP outgoing routes and trunks, DAHDI and SIP incoming routes and trunks, but continue to fail at outgoing DAHDI trunk.

The numbers are correct, yet give errors from external POTS which are different depending if the trunk is set as group or specific analog channel.

Either way I can not make outgoing calls except to my SIP trunks. Any hints on how to move forward?

=============================
If I set DAHDI trunk as a specific channel

long pause
- multiple rings then answer
- error tone
- message: "the area code or telephone called is not valid please check the number and try again. The following tones are for the deaf communnity...."

-- Executing [s@macro-dialout-trunk:19] Dial("DAHDI/1-1", "DAHDI/4/2345678,300,") in new stack
-- Called 4/2345678
== Begin MixMonitor Recording DAHDI/1-1
-- DAHDI/4-1 answered DAHDI/1-1

=============================
If I set DAHDI trunk as a group


long pause
- multiple rings then answer
- error tone
- message: "it is not necessary to dial a one when calling this number. Please hang up and call again...."

portion of asterisk CLI >

-- Executing [s@macro-dialout-trunk:19] Dial("DAHDI/1-1", "DAHDI/4/6142345678,300,") in new stack
-- Called 4/6142345678
== Begin MixMonitor Recording DAHDI/1-1
-- DAHDI/4-1 answered DAHDI/1-1
 
So sorry ---


Date and Time = 201106192311
PIAF color = PURPLE
Asterisk Status = ONLINE
Dahdi Status = ONLINE
Zaptel Status = OFFLINE
MySql Status = ONLINE
SSH Status = ONLINE
Apache Status = ONLINE
Iptables Status = ONLINE
Ip6tables Status = ONLINE
Fail2ban Status = OFFLINE
IP Connect Status = ONLINE
Bluetooth Status = ONLINE
HIDD Status = ONLINE
NTPD Status = ONLINE
Sendmail Status = ONLINE
Samba Status = OFFLINE
Webmin Status = ONLINE
Ethernet 0 Status = ONLINE
Ethernet 1 Status = N/A
Wlan Status = N/A
PIAF Version = 1.7.5.6
Freepbx Version = 2.8.1.4
Running Asterisk = Asterisk 1.8.4.1
Asterisk Source Version = 1.8.4.1
Dahdi Source = 2.4.1.2+2.4.1
Zaptel Source = UNAVAILABLE
Libpri Source = 1.4.11.5
Addons Source = UNAVAILABLE
pbx.local on 192.168.xxx.xxx - eth0
CentOS release 5.6 (Final) :32 Bit Kernel: 2.6.18-238.9.1.el5
********************************************************************
Ifconfig output
eth0 Link encap:Ethernet HWaddr 00:xx:xx:xx:xx:xx
inet addr:192.168.xxx.xxx Bcast:192.168.xxx.255 Mask:255.255.255.0
inet6 addr: xxxx::xxx:xxxx:xxxx:xxxx/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1416342 errors:0 dropped:0 overruns:0 frame:0
TX packets:1152022 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:283876142 (270.7 MiB) TX bytes:286850408 (273.5 MiB)
Interrupt:177

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:855324 errors:0 dropped:0 overruns:0 frame:0
TX packets:855324 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:117587485 (112.1 MiB) TX bytes:117587485 (112.1 MiB)

********************************************************************
Network Configuration output ifconfig-eth0
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=static
IPADDR=192.168.xxx.xxx
NETMASK=255.255.255.0
GATEWAY=192.168.xxx.xxx
********************************************************************
uname -a output
Linux pbx.local 2.6.18-238.9.1.el5 #1 SMP Tue Apr 12 18:10:56 EDT 2011 i686 i686 i386 GNU/Linux
********************************************************************
Routing Info - route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.xxx.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
default 192.168.xxx.xxx 0.0.0.0 UG 0 0 0 eth0
********************************************************************
Free Memory free -m output
total used free shared buffers cached
Mem: 3168 1210 1958 0 178 781
-/+ buffers/cache: 250 2918
Swap: 760 0 760
********************************************************************
Disk Info df output
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 945313512 3927316 892592376 1% /
/dev/sda1 101086 11520 84347 13% /boot
tmpfs 1622520 0 1622520 0% /dev/shm
********************************************************************
Output of hosts file
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 pbx.dyndns.org pbx.local pbx localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
********************************************************************
 
More info --


pbx*CLI> dahdi show status
Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO
Wildcard TDM400P REV I Board 5 OK 0 0 0 CAS Unk 0 db (CSU)/0-133 feet (DSX-1)
Wildcard TDM400P REV I Board 5 OK 0 0 0 CAS Unk 0 db (CSU)/0-133 feet (DSX-1)
pbx*CLI> dahdi show channels
Chan Extension Context Language MOH Interpret Blocked State
pseudo default default In Service
1 from-internal default In Service
2 from-internal default In Service
3 from-pstn default In Service
4 from-pstn default In Service
5 from-analog default In Service
6 from-analog default In Service
7 from-analog default In Service
8 from-internal default In Service
pbx*CLI> dahdi show channel
pbx*CLI> dahdi show channel 4
Channel: 4
File Descriptor: 19
Span: 1
Extension:
Dialing: no
Context: from-pstn
Caller ID:
Calling TON: 0
Caller ID subaddress:
Caller ID name:
Mailbox: 728@device
Destroy: 0
InAlarm: 0
Signalling Type: FXS Kewlstart
Radio: 0
Owner: <None>
Real: <None>
Callwait: <None>
Threeway: <None>
Confno: -1
Propagated Conference: -1
Real in conference: 0
DSP: no
Busy Detection: no
TDD: no
Relax DTMF: no
Dialing/CallwaitCAS: 0/0
Default law: ulaw
Fax Handled: no
Pulse phone: no
Gains (RX/TX): 0.00/0.00
Dynamic Range Compression (RX/TX): 0.00/0.00
DND: no
Echo Cancellation:
128 taps
(unless TDM bridged) currently OFF
Wait for dialtone: 0ms
Actual Confinfo: Num/0, Mode/0x0000
Actual Confmute: No
Hookstate (FXS only): Offhook
 
Where did you put your dialing pattern? In the trunk setting or in the outbound route?
 
Try adding a 'w' to your outbound dial prefix in the trunk configuration. It looks like the system is trying to dial before the line is ready.
 
Try adding a 'w' to your outbound dial prefix in the trunk configuration. It looks like the system is trying to dial before the line is ready.

Just for interest, how did you deduce this from the info presented?
 
Eugene,

I find this to be a common problem with Zap or Dahdi and PSTN lines. It is one of the first things I do when I have trouble dialing out. It seems that the card is ready at least a quarter of a second before the Telco is.

John
 
Yeah, it was a head scratcher the first time I came across the problem. Now that I'm aware of the problem it's one of the first things I try, and I'd say about 50% of my installs require this setting.

This was the telltale for me:
Code:
Executing [s@macro-dialout-trunk:19] Dial("DAHDI/1-1", "DAHDI/4/6142345678,300,") in new stack
- message: "it is not necessary to dial a one when calling this number. Please hang up and call again...."

So, obviously, it missed the 6 and started with the 1.

A good butt-set is also extremely helpful with stuff like this. Being able to tap into the line and hear whats going on takes out a lot of the guesswork.
 
I am having a very similar problem, but the "w" flag in the outbound dial prefix didn't do the job. When I dial out, I can see the call connect to the proper channel, but about 20 seconds into the call I get a message from the telco about how my call cannot be completed as dialed.
If I connect the Dahdi channel to an extension, then pick up that extension, I get a dial tone, and I can make outgoing calls, but if I just dial it won't work. Is is possible that the delay is longer and the w is not sufficient? Please help!
 
When I dial out, I can see the call connect to the proper channel, but about 20 seconds into the call I get a message from the telco about how my call cannot be completed as dialed.

That sounds like a trunk setting for your outgoing dial rules. How are you setting your dial rules?
 
Ahhh, the ole' Slip in a 'w' fix again..

My lines here sometimes are a little slow to start.

I don't know if its good practice or not by I find myself just adding it to prevent any headaches, need it or not..

But, What do I know anyway?
 
I am having a very similar problem, but the "w" flag in the outbound dial prefix didn't do the job. When I dial out, I can see the call connect to the proper channel, but about 20 seconds into the call I get a message from the telco about how my call cannot be completed as dialed.
If I connect the Dahdi channel to an extension, then pick up that extension, I get a dial tone, and I can make outgoing calls, but if I just dial it won't work. Is is possible that the delay is longer and the w is not sufficient? Please help!

I suggest that you start a new Trunk posting rather than hijack this thread.
 

Members online

Forum statistics

Threads
26,686
Messages
174,406
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