Page 1 of 1

Call Hangup On PRI

PostPosted: Tue Aug 05, 2014 6:42 am
by puneet_143
Hi,

I am facing issue on outbound dialing my calls are getting hangup while speaking to customer, i get following error:-

chan_dahdi.c: Set option AUDIO MODE, value: ON(1) on DAHDI/1-1
chan_dahdi.c: Not yet hungup... Calling hangup once with icause, and clearing call
chan_dahdi.c: Set option AUDIO MODE, value: OFF(0) on DAHDI/1-1
logger.c: -- Hungup 'DAHDI/1-1'


Please help

Regards,
Puneet

Re: Call Hangup On PRI

PostPosted: Tue Aug 05, 2014 7:03 am
by puneet_143
These are the recent logs

[Aug 5 04:22:43] DEBUG[24526] chan_dahdi.c: Set option AUDIO MODE, value: ON(1) on DAHDI/90-1
[Aug 5 04:22:43] DEBUG[24526] chan_dahdi.c: Not yet hungup... Calling hangup once with icause, and clearing call
[Aug 5 04:22:43] DEBUG[24526] chan_dahdi.c: Set option AUDIO MODE, value: OFF(0) on DAHDI/90-1
[Aug 5 04:22:43] VERBOSE[24526] logger.c: [Aug 5 04:22:43] -- Hungup 'DAHDI/90-1'
[Aug 5 04:22:43] VERBOSE[24526] logger.c: [Aug 5 04:22:43] -- No one is available to answer at this time (1:0/0/0)

Re: Call Hangup On PRI

PostPosted: Wed Aug 06, 2014 10:38 pm
by gardo
Sounds like a timing source configuration issue in your config file.

Code: Select all
# Span Configuration
# ^^^^^^^^^^^^^^^^^^
# First come the span definitions, in the format
#
#   span=<span num>,<timing source>,<line build out (LBO)>,<framing>,<coding>[,yellow]
#
# All T1/E1/BRI spans generate a clock signal on their transmit side. The
# <timing source> parameter determines whether the clock signal from the far
# end of the T1/E1/BRI is used as the master source of clock timing. If it is, our
# own clock will synchronise to it. T1/E1/BRI connected directly or indirectly to
# a PSTN provider (telco) should generally be the first choice to sync to. The
# PSTN will never be a slave to you. You must be a slave to it.
#
# Choose 1 to make the equipment at the far end of the E1/T1/BRI link the preferred
# source of the master clock. Choose 2 to make it the second choice for the master
# clock, if the first choice port fails (the far end dies, a cable breaks, or
# whatever). Choose 3 to make a port the third choice, and so on. If you have, say,
# 2 ports connected to the PSTN, mark those as 1 and 2. The number used for each
# port should be different.
#
# If you choose 0, the port will never be used as a source of timing. This is
# appropriate when you know the far end should always be a slave to you. If
# the port is connected to a channel bank, for example, you should always be
# its master. Likewise, BRI TE ports should always be configured as a slave.
# Any number of ports can be marked as 0.
#
# Incorrect timing sync may cause clicks/noise in the audio, poor quality or failed
# faxes, unreliable modem operation, and is a general all round bad thing.