[asterisk-ss7] asterisk-ss7 Digest, Vol 33, Issue 17

Dmitri Sologoubenko dmitri.sologoubenko at cwnet.it
Wed Nov 28 12:19:31 CST 2007


asterisk-ss7-request at lists.digium.com ha scritto:
> Send asterisk-ss7 mailing list submissions to
> 	asterisk-ss7 at lists.digium.com
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.digium.com/mailman/listinfo/asterisk-ss7
> or, via email, send a message with subject or body 'help' to
> 	asterisk-ss7-request at lists.digium.com
> 
> You can reach the person managing the list at
> 	asterisk-ss7-owner at lists.digium.com
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of asterisk-ss7 digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: Strange problem with TE120P (asterisk & Zap-SS7)
>       (Matthew Fredrickson)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 27 Nov 2007 13:24:43 -0600
> From: Matthew Fredrickson <creslin at digium.com>
> Subject: Re: [asterisk-ss7] Strange problem with TE120P (asterisk &
> 	Zap-SS7)
> To: asterisk-ss7 at lists.digium.com
> Message-ID: <474C6EFB.2030002 at digium.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> Dmitri Sologoubenko wrote:
>> Hello, guys!
>>
>> I have recently installed trunk versions of asterisk-1.4, zaptel, libpri
>> and libss7. I Have also plugged in and configured a Digium's TE120P card.
>> ztcfg, zttool and other zaptel utilities seems to work ok, zaptel driver
>> modules seems to be correctly loaded and both zaptel and asterisk start
>> with no error messages.
>> But Zap channel type is not listed in asterisk CLI, no "zap ..." CLI
>> commands are available, and no Dial(Zap/...) works.
> 
> Typically when no zap commands are available, it means that chan_zap.so 
> didn't load.  You may check /var/log/asterisk/messages and figure out 
> what the error is when asterisk starts and tries to load chan_zap.
> 
> Matthew Fredrickson
> 
>> Can anybody help me?
>>
>> Thanks in advance,
>> D.S.
>>
>> Here's the output:
>>
>> *CLI> module show like zap
>> Module                         Description                          	Use
>> Count
>> chan_zap.so                    Zapata Telephony
>> 0
>> codec_zap.so                   Generic Zaptel Transcoder Codec Translat
>> 0
>> app_zapras.so                  Zaptel ISDN Remote Access Server
>> 0
>> app_zapbarge.so                Barge in on Zap channel application
>> 0
>> app_zapateller.so              Block Telemarketers with Special Informa
>> 0
>> app_zapscan.so                 Scan Zap channels application
>> 0
>> 6 modules loaded
>>
>> ----
>>
>> *CLI> core show channeltypes
>> Type        Description                              Devicestate
>> Indications  Transfer
>> ----------  -----------                              -----------
>> -----------  --------
>> Agent       Call Agent Proxy Channel                 yes          yes
>>        no
>> Phone       Standard Linux Telephony API Driver      no           yes
>>        no
>> USTM        UNISTIM Channel Driver                   no           yes
>>        no
>> Skinny      Skinny Client Control Protocol (Skinny)  yes          yes
>>        no
>> IAX2        Inter Asterisk eXchange Driver (Ver 2)   yes          yes
>>        yes
>> Local       Local Proxy Channel Driver               yes          yes
>>        no
>> Console     OSS Console Channel Driver               no           yes
>>        no
>> SIP         Session Initiation Protocol (SIP)        yes          yes
>>        yes
>> MGCP        Media Gateway Control Protocol (MGCP)    yes          yes
>>        no
>> ----------y*CLI>
>> 9 channel drivers registered.
>>
>> ----
>>
>> *CLI> core show channeltype zap
>> portability*CLI>
>> zap is not a registered channel driver.
>> Command 'core show channeltype zap' failed.
>>
>> ----
>>
>>
>> # lsmod
>> Module                  Size  Used by
>> zttranscode            11784  0
>> wcte12xp               37696  1
>> zaptel                187428  6 zttranscode,wcte12xp
>> ipv6                  250369  14
>> dm_mirror              29713  0
>> dm_mod                 56665  1 dm_mirror
>> video                  19269  0
>> sbs                    18533  0
>> i2c_ec                  9025  1 sbs
>> button                 10705  0
>> battery                13637  0
>> asus_acpi              19289  0
>> ac                      9157  0
>> parport_pc             29157  0
>> lp                     15849  0
>> parport                37513  2 parport_pc,lp
>> sg                     35933  0
>> 8139too                28737  0
>> r8169                  31561  0
>> mii                     9409  1 8139too
>> i2c_i801               11469  0
>> pcspkr                  7105  0
>> i2c_core               23745  2 i2c_ec,i2c_i801
>> serio_raw              10693  0
>> crc_ccitt               6337  1 zaptel
>> usb_storage            76193  0
>> ata_piix               17609  14
>> libata                 96857  1 ata_piix
>> sd_mod                 22977  16
>> scsi_mod              130637  4 sg,usb_storage,libata,sd_mod
>> raid1                  25153  6
>> ext3                  123081  6
>> jbd                    56553  1 ext3
>> ehci_hcd               32845  0
>> ohci_hcd               23261  0
>> uhci_hcd               25421  0
>>
>>
>>
>>
>> _______________________________________________
>> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>>
>> asterisk-ss7 mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-ss7
> 
> 

Problem solved!

module reload chan_zap.so was not working (no error messages), but when
I' executed via *CLI "module unload chan_zap.so" and then "module load
chan_zap.so" I had an error message on a missing required ss7 parameter.

Thank a lot for your replies,

Best wishes,

Dmitri Sologoubenko




More information about the asterisk-ss7 mailing list