keywords: ip pbx voip gateway gsm gateway

×

Notice

The forum is in read only mode.
× Questions on Asterisk with SS7 Chinese variant. (有关Asterisk+中国七号信令的问题)

ss7安装问题

15 years 5 months ago #2128 by zy7884
ss7安装后,asterisk不能启动,日志如下,请问是什么问题
[root@data modules]# asterisk -vvvvvvvvvvcg
Asterisk 1.4.21.2, Copyright (C) 1999 - 2008 Digium, Inc. and others.
Created by Mark Spencer <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
=========================================================================
== Parsing '/etc/asterisk/asterisk.conf': Found
== Parsing '/etc/asterisk/extconfig.conf': Found
== Parsing '/etc/asterisk/logger.conf': Found
Asterisk Event Logger Started /var/log/asterisk/event_log
[2008-11-05 16:36] ERROR[5341]: asterisk.c:2982 main: Asterisk has detected a problem with your Zaptel configuration and will shutdown for your protection. You have options:
1. You only have to compile Zaptel support into Asterisk if you need it. One option is to recompile without Zaptel support.
2. You only have to load Zaptel drivers if you want to take advantage of Zaptel services. One option is to unload zaptel modules if you don't need them.
3. If you need Zaptel services, you must correctly configure Zaptel.



ss7.conf 文件内容
[linkset-siuc]

; The linkset is enabled
enabled => yes

; The end-of-pulsing (ST) is not used to determine when incoming address is complete
enable_st => yes

; Reply incoming call with CON rather than ACM and ANM
use_connect => no

; The CIC hunting policy (even_mru, odd_lru, seq_lth, seq_htl) is even CIC numbers, most recently used
hunting_policy => even_mru

; Incoming calls are placed in the ss7 context in the asterisk dialplan
context => incoming_1

; The language for this context is da
language => en

; The value and action for t35. Value is in msec, action is either st or timeout
; If you use overlapped dialling dial plan, you might choose: t35 => 4000,st
t35 => 15000,timeout

; The subservice field: national (8), international (0), auto or decimal/hex value
; The auto means that the subservice is obtained from first received SLTM
subservice => auto

; The host running the mtp3 service
; mtp3server => localhost

;addr_type => ansi
;a_cat => 0x18
;trans_ind => 0x00

[link-l1]

; This link belongs to linkset siuc
linkset => siuc

; The speech/audio circuit channels on this link
channels => 1-15,17-31

; The signalling channel
schannel => 16
; To use the remote mtp3 service, use 'schannel => remote,16'

; The first CIC
firstcic => 1

; The link is enabled
enabled => yes

; Echo cancellation
; echocancel can be one of: no, 31speech (enable only when transmission medium is 3.1Khz speech), allways
echocancel => no
; echocan_train specifies training period, between 10 to 100 msec
echocan_train => 350
; echocan_taps specifies number of taps, 32, 64, 128 or 256
echocan_taps => 128


[host-gentoo1]
; chan_ss7 auto-configures by matching the machines host name with the host-<name>
; section in the configuration file, in this case 'gentoo1'. The same
; configuration file can thus be used on several hosts.

; The host is enabled
enabled => yes

; The point code for this SS7 signalling point is 0x8e0
opc => 0x8e0

; The destination point (peer) code is 0x3fff for linkset siuc
dpc => siuc:0x3fff

; Syntax: links => link-name:digium-connector-no
; The links on the host is 'l1', connected to span/connector #1
links => l1:1

; The SCCP global title: translation-type, nature-of-address, numbering-plan, address
;globaltitle => 0x00, 0x04, 0x01, 4546931411
;ssn => 7


;[jitter]
;
JITTER BUFFER CONFIGURATION
; jbenable = yes ; Enables the use of a jitterbuffer on the receiving side of a
; SIP channel. Defaults to "no". An enabled jitterbuffer will
; be used only if the sending side can create and the receiving
; side can not accept jitter. The SIP channel can accept jitter,
; thus a jitterbuffer on the receive SIP side will be used only
; if it is forced and enabled.

; jbforce = no ; Forces the use of a jitterbuffer on the receive side of a SIP
; channel. Defaults to "no".

; jbmaxsize = 200 ; Max length of the jitterbuffer in milliseconds.

; jbresyncthreshold = 1000 ; Jump in the frame timestamps over which the jitterbuffer is
; resynchronized. Useful to improve the quality of the voice, with
; big jumps in/broken timestamps, usually sent from exotic devices
; and programs. Defaults to 1000.

; jbimpl = fixed ; Jitterbuffer implementation, used on the receiving side of a SIP
; channel. Two implementations are currently available - "fixed"
; (with size always equals to jbmaxsize) and "adaptive" (with
; variable size, actually the new jb of IAX2). Defaults to fixed.

; jblog = no ; Enables jitterbuffer frame logging. Defaults to "no".
;


zaptel.conf内容
# Autogenerated by /usr/sbin/genzaptelconf -- do not hand edit
# Zaptel Configuration File
#
# This file is parsed by the Zaptel Configurator, ztcfg
#

# It must be in the module loading order


# Span 1: WCT1/0 "Digium Wildcard TE110P T1/E1 Card 0"
span=1,1,0,ccs,hdb3
# termtype: te
bchan=1-31
loadzone = cn
defaultzone = cn
15 years 5 months ago #2130 by miaolin
ERROR[5341]: asterisk.c:2982 main: Asterisk has detected a problem with your Zaptel configuration and will shutdown for your protection. You have options:
1. You only have to compile Zaptel support into Asterisk if you need it. One option is to recompile without Zaptel support.
2. You only have to load Zaptel drivers if you want to take advantage of Zaptel services. One option is to unload zaptel modules if you don't need them.
3. If you need Zaptel services, you must correctly configure Zaptel.


ztcfg运行了没有?zapata.conf对不对?
15 years 5 months ago #2132 by zy7884
下面是ztcfg运行结果,zapata.conf不是不用配置吗,只要配置ss7.conf就好吗
[root@data modules]# ztcfg -vv

Zaptel Version: 1.4.11
Echo Canceller: MG2
Configuration
======================

SPAN 1: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)

Channel map:

Channel 01: Clear channel (Default) (Slaves: 01)
Channel 02: Clear channel (Default) (Slaves: 02)
Channel 03: Clear channel (Default) (Slaves: 03)
Channel 04: Clear channel (Default) (Slaves: 04)
Channel 05: Clear channel (Default) (Slaves: 05)
Channel 06: Clear channel (Default) (Slaves: 06)
Channel 07: Clear channel (Default) (Slaves: 07)
Channel 08: Clear channel (Default) (Slaves: 08)
Channel 09: Clear channel (Default) (Slaves: 09)
Channel 10: Clear channel (Default) (Slaves: 10)
Channel 11: Clear channel (Default) (Slaves: 11)
Channel 12: Clear channel (Default) (Slaves: 12)
Channel 13: Clear channel (Default) (Slaves: 13)
Channel 14: Clear channel (Default) (Slaves: 14)
Channel 15: Clear channel (Default) (Slaves: 15)
Channel 16: Clear channel (Default) (Slaves: 16)
Channel 17: Clear channel (Default) (Slaves: 17)
Channel 18: Clear channel (Default) (Slaves: 18)
Channel 19: Clear channel (Default) (Slaves: 19)
Channel 20: Clear channel (Default) (Slaves: 20)
Channel 21: Clear channel (Default) (Slaves: 21)
Channel 22: Clear channel (Default) (Slaves: 22)
Channel 23: Clear channel (Default) (Slaves: 23)
Channel 24: Clear channel (Default) (Slaves: 24)
Channel 25: Clear channel (Default) (Slaves: 25)
Channel 26: Clear channel (Default) (Slaves: 26)
Channel 27: Clear channel (Default) (Slaves: 27)
Channel 28: Clear channel (Default) (Slaves: 28)
Channel 29: Clear channel (Default) (Slaves: 29)
Channel 30: Clear channel (Default) (Slaves: 30)
Channel 31: Clear channel (Default) (Slaves: 31)

31 channels to configure.

[root@data modules]#
Time to create page: 0.035 seconds
Powered by Kunena Forum