[asterisk-ss7] my chan_ss7 status is going up and down
ADEGOKE ARUNA
goksie at gmail.com
Sat Mar 18 12:28:40 MST 2006
Thank you for the past responses,
Can someone please help me point out my flaws again?
I am working on fedora core 3 with sangoma a104d and lastest stable asterisk
and libs.
I have disabled my chan_zap.so
After compiling my chan_ss7-0.8.3
WIRELESS2*CLI> load chan_ss7.so
Loaded /usr/lib/asterisk/modules/chan_ss7.so => (SS7 Protocol Support)
Mar 18 19:10:08 NOTICE[11525]: config.c:320 load_config_linkset: Using
default language '' for linkset 'siuc'
Mar 18 19:10:08 NOTICE[11525]: config.c:463 load_config_link: Configured
link 'l1' on linkset 'siuc', firstcic=1
Mar 18 19:10:08 NOTICE[11525]: config.c:463 load_config_link: Configured
link 'l2' on linkset 'siuc', firstcic=33
Mar 18 19:10:08 NOTICE[11525]: config.c:463 load_config_link: Configured
link 'l3' on linkset 'siuc', firstcic=65
Mar 18 19:10:08 NOTICE[11525]: config.c:463 load_config_link: Configured
link 'l4' on linkset 'siuc', firstcic=97
Mar 18 19:10:08 WARNING[11525]: config.c:622 load_config_host: Missing
interface entries for host 'WIRELESS2'.
Mar 18 19:10:08 NOTICE[11525]: config.c:772 load_config: Configuring DPC 60
for linkset 'siuc'.
-- Starting cluster thread, pid=3976.
Mar 18 19:10:09 NOTICE[11525]: mtp.c:1934 mtp_init: Initialising 1
signalling links
-- Starting MTP thread, pid=3976.
-- Starting continuity check thread, pid=3976.
== Registered channel type 'SS7' (SS7 Protocol Driver)
-- SS7 channel loaded successfully.
-- Starting monitor thread, pid=3976.
Mar 18 19:10:09 WARNING[14785]: mtp.c:1539 mtp_thread_main: Empty Zaptel
output buffer detected, outgoing packets may have been lost on link 'l1'.
WIRELESS2*CLI> ss7
block cluster dump linestat link reset unblock
WIRELESS2*CLI> ss7 li
linestat link
WIRELESS2*CLI> ss7 linestat
Linkset: siuc>
Mar 18 19:11:24 WARNING[14785]: mtp.c:393 t2_timeout: MTP2 timer T2 timeout
(failed to receive 'O', 'N', or 'E' after sending 'O'), initial alignment
failed on link 'l1'.
when I dialed 6210006
i get this:
-- Executing Dial("IAX2/marko-2", "ss7/6210010|60") in new stack
-- SS7 request (ss7/6210010) format = 0x8.
Mar 18 20:15:59 WARNING[5495]: chan_ss7.c:425 cic_hunt_even_mru: No idle
circuit found.
Mar 18 20:15:59 WARNING[5495]: chan_ss7.c:646 ss7_requester: SS7 requester:
No idle circuit available.
Mar 18 20:15:59 NOTICE[5495]: app_dial.c:1011 dial_exec_full: Unable to
create channel of type 'ss7' (cause 17 - User busy)
== Everyone is busy/congested at this time (1:1/0/0)
== Auto fallthrough, channel 'IAX2/marko-2' status is 'BUSY'
:22:37 WARNING[14785]: mtp.c:1438 mtp_thread_main: Excessive poll delay
20978!
Mar 18 19:22:37 WARNING[14785]: mtp.c:1438 mtp_thread_main: Excessive poll
delay 20979!
Mar 18 19:22:37 WARNING[14785]: mtp.c:1438 mtp_thread_main: Excessive poll
delay 20977!
Mar 18 19:22:37 WARNING[14785]: mtp.c:1438 mtp_thread_main: Excessive poll
delay 20978!
Mar 18 19:22:37 WARNING[14785]: mtp.c:1438 mtp_thread_main: Excessive poll
delay 20978!
Mar 18 19:22:38 WARNING[14785]: mtp.c:1438 mtp_thread_main: Excessive poll
delay 20979!
Mar 18 19:25:20 WARNING[15612] mtp.c: Excessive poll delay 20979!
Mar 18 19:25:20 WARNING[15624] chan_ss7.c: No idle circuit found.
Mar 18 19:25:20 WARNING[15624] chan_ss7.c: SS7 requester: No idle circuit
available.
Mar 18 19:25:20 NOTICE[15624] app_dial.c: Unable to create channel of type
'SS7' (cause 17 - User busy)
Extensions.conf
[default]
Exten => _621XXXX,1,Dial(ss7/${EXTEN},60)
zaptel.conf
loadzone = uk
defaultzone = uk
#span definitions
span = 1,1,0,ccs,hdb3,crc4,yellow
span = 2,2,0,ccs,hdb3,crc4,yellow
span = 3,3,0,ccs,hdb3,crc4,yellow
span = 4,4,0,ccs,hdb3,crc4,yellow
#channel definitions
#bchan = 1-124
#bchan = 1-15,17-124
#dchan = 16
zapata.conf
;[trunkgroups]
;trunkgroup => 1, 16
;spanmap
;spanmap => 1,1,1
;spanmap => 2,1,2
;spanmap => 3,1,3
;spanmap => 4,1,4
[channels]
;context = default
;switchtype = Euroisdn
;usecallerid = yes
;echocancel = yes
;echocancelwhenbridged = yes
;rxgain = 0.0
;txgain = 0.0
;signalling = pri_cpe
;group = 1
;channel = 1-15,17-31
one of the wanpipe#.conf that controls sangoma interface
#================================================
# Sangoma Technologies Inc.
#================================================
[devices]
wanpipe1 = WAN_AFT_TE1, Comment
[interfaces]
w1g1 = wanpipe1, , TDM_VOICE, Comment
[wanpipe1]
CARD_TYPE = AFT
S514CPU = A
CommPort = PRI
AUTO_PCISLOT = NO
PCISLOT = 13
PCIBUS = 6
FE_MEDIA = E1
FE_LCODE = HDB3
FE_FRAME = CRC4
FE_LINE = 1
TE_CLOCK = NORMAL
TE_REF_CLOCK = 0
TE_HIGHIMPEDANCE = NO
LBO = 120OH
FE_TXTRISTATE = NO
MTU = 1500
UDPPORT = 9000
TTL = 255
IGNORE_FRONT_END = NO
TDMV_SPAN = 1
TDMV_DCHAN = 0
[w1g1]
ACTIVE_CH = ALL
TDMV_ECHO_OFF = NO
TDMV_HWEC = YES
ss7.conf is as below
[linkset-siuc]
enabled => yes
enable_st => no
use_connect => no #bcos am connect to alcatel s12 which doesn't lik con
hunting_policy => even_mru
subservice => auto
[link-l1]
linkset => siuc
channels => 1-15,17-31
schannel => 16
firstcic => 1
enabled => yes
[link-l2]
linkset => siuc
channels => 1-31
schannel =>
firstcic => 33
enabled => yes
[link-l3]
linkset => siuc
channels => 1-31
schannel =>
firstcic => 65
enabled => yes
[link-l4]
linkset => siuc
channels => 1-31
schannel =>
firstcic => 97
enabled => yes
[host-WIRELESS2]
enabled => yes
opc => 900
dpc => siuc:60
links => l1:1,l2:2,l3:3,l4:4
The following output is produced
Mar 18 19:25:24 WARNING[15612] mtp.c: Excessive poll delay 20979!
Mar 18 19:25:25 WARNING[15612] mtp.c: Excessive poll delay 20978!
Mar 18 19:25:25 WARNING[15612] mtp.c: Excessive poll delay 20979!
Mar 18 19:25:25 WARNING[15612] mtp.c: Excessive poll delay 20979!
Mar 18 19:25:25 WARNING[15612] mtp.c: Excessive poll delay 20979!
Mar 18 19:25:25 WARNING[15612] mtp.c: Excessive poll delay 20979!
Mar 18 19:25:25 WARNING[15612] mtp.c: Excessive poll delay 20980!
and its just to much and that the log growths in MB per minute
after I rebooted my pc and applying the kai Militzer's patch I got the
following error
Verbosity is at least 3
Mar 18 20:13:30 WARNING[5478]: mtp.c:414 t3_timeout: MTP2 timer T3 timeout
(failed to receive 'N', or 'E' after sending 'O'), initial alignment failed
on link 'l1'.
Mar 18 20:13:33 WARNING[5478]: mtp.c:414 t3_timeout: MTP2 timer T3 timeout
(failed to receive 'N', or 'E' after sending 'O'), initial alignment failed
on link 'l1'.
Mar 18 20:13:36 WARNING[5478]: mtp.c:414 t3_timeout: MTP2 timer T3 timeout
(failed to receive 'N', or 'E' after sending 'O'), initial alignment failed
on link 'l1'.
Mar 18 20:13:38 WARNING[5478]: mtp.c:414 t3_timeout: MTP2 timer T3 timeout
(failed to receive 'N', or 'E' after sending 'O'), initial alignment failed
on link 'l1'.
Mar 18 20:13:41 WARNING[5478]: mtp.c:414 t3_timeout: MTP2 timer T3 timeout
(failed to receive 'N', or 'E' after sending 'O'), initial alignment failed
on link 'l1'.
Mar 18 20:13:44 NOTICE[5478]: mtp.c:1197 mtp2_read_su: MTP2 bitstream frame
format error, entering octet counting mode on link 'l1'.
Mar 18 20:13:46 WARNING[5478]: mtp.c:414 t3_timeout: MTP2 timer T3 timeout
(failed to receive 'N', or 'E' after sending 'O'), initial alignment failed
on link 'l1'.
Mar 18 20:13:49 WARNING[5478]: mtp.c:414 t3_timeout: MTP2 timer T3 timeout
(failed to receive 'N', or 'E' after sending 'O'), initial alignment failed
on link 'l1'.
Mar 18 20:13:52 WARNING[5478]: mtp.c:414 t3_timeout: MTP2 timer T3 timeout
(failed to receive 'N', or 'E' after sending 'O'), initial alignment failed
on link 'l1'.
ss7 link status
linkset siuc, link l1, schannel 16, ALIGNED, rx: 3, tx: 0/4,
sentseq/lastack: 127/127, total 73792, 73856
WIRELESS2*CLI> ss7 linestat
Linkset: siuc>
CIC 1 Idle Reset pending
CIC 2 Idle Reset pending
CIC 3 Idle Reset pending
|
|
|
CIC 125 Idle Reset pending
CIC 126 Idle Reset pending
CIC 127 Idle Reset pending
-----Original Message-----
From: Kai Militzer [mailto:km at westend.com]
Sent: Friday, March 17, 2006 4:39 PM
To: ADEGOKE ARUNA
Subject: Re: chan_ss7.c: Failure in ZT_SPECIFY for circuit 1: Device or
resource busy
Hi Goksie,
ADEGOKE ARUNA wrote:
> What do you ask to disable?
If you had this system at first running with ISDN E1s (no SS7) you have
to disable your config for that at first.
And did you tell your Telco that they have to configure the S12 to talk
SS7 instead of ISDN to you? For me it doesn't look that way.
Nevertheless it's not that easy to find your problem without more
information.
I am off into the weekend now, if you need more help send me an email, i
will answer you on monday.
Regards,
Kai
--
Kai Militzer WESTEND GmbH | Internet-Business-Provider
Technik CISCO Systems Partner - Authorized Reseller
Lütticher Straße 10 Tel 0241/701333-14
km at westend.com D-52064 Aachen Fax 0241/911879
More information about the asterisk-ss7
mailing list