[Asterisk-Users] TE410P E1 PRI problem

[Tomica Crnek]

Hi everyone!
 
Here is my configuration and messages taken from Asterisk startup. The E1 PRI trunk is connected to our national telecom company here in Croatia. When I call from outside over this trunk to my company I get 'error in connection' respnse. In the same moment I can't see anything in Asterisk, nothing that will tell me that the call reached Asterisk. I think there is a problem with PRI synchronization or PRI to zap communication.
 
The card I am using is TE410P, the first port is the one that I use.
 
/etc/zaptel.conf
-----------------
# port 1: trunk to telecom
span=1,0,0,ccs,hdb3
bchan=1-15,17-31
dchan=16
 
After loading module ztcfg shows:
----------------------------------
[root at ceres asterisk]# /sbin/ztcfg -v
Zaptel Configuration
======================
SPAN 1: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
31 channels configured.

 
/etc/asterisk/zapata.conf
------------------------
; trunk:
switchtype = euroisdn
signalling = pri_cpe
group = 2
context = default
channel => 1-15,17-31
 
extensions.conf
---------------
I have demo context section included in default context where incoming calls from PRI trunk are terminated. (When I dial from SIP phone terminated in same default context I get the response., so I think there is no problem with context)
 
During Asterisk startup I get this output regarding Zap channel
---------------------------------------------------------------
 
 [chan_zap.so] => (Zapata Telephony w/PRI)
  == Parsing '/etc/asterisk/zapata.conf': Found
Jan 31 17:04:41 WARNING[1074441696]: chan_zap.c:7552 setup_zap: Ignoring rxwink
    -- Registered channel 1, PRI Signalling signalling
    -- Registered channel 2, PRI Signalling signalling
    -- Registered channel 3, PRI Signalling signalling
    -- Registered channel 4, PRI Signalling signalling
    -- Registered channel 5, PRI Signalling signalling
    -- Registered channel 6, PRI Signalling signalling
    -- Registered channel 7, PRI Signalling signalling
    -- Registered channel 8, PRI Signalling signalling
    -- Registered channel 9, PRI Signalling signalling
    -- Registered channel 10, PRI Signalling signalling
    -- Registered channel 11, PRI Signalling signalling
    -- Registered channel 12, PRI Signalling signalling
    -- Registered channel 13, PRI Signalling signalling
    -- Registered channel 14, PRI Signalling signalling
    -- Registered channel 15, PRI Signalling signalling
    -- Registered channel 17, PRI Signalling signalling
    -- Registered channel 18, PRI Signalling signalling
    -- Registered channel 19, PRI Signalling signalling
    -- Registered channel 20, PRI Signalling signalling
    -- Registered channel 21, PRI Signalling signalling
    -- Registered channel 22, PRI Signalling signalling
    -- Registered channel 23, PRI Signalling signalling
    -- Registered channel 24, PRI Signalling signalling
    -- Registered channel 25, PRI Signalling signalling
    -- Registered channel 26, PRI Signalling signalling
    -- Registered channel 27, PRI Signalling signalling
    -- Registered channel 28, PRI Signalling signalling
    -- Registered channel 29, PRI Signalling signalling
    -- Registered channel 30, PRI Signalling signalling
    -- Registered channel 31, PRI Signalling signalling
  == Starting D-Channel on span 1
  == Registered channel type 'Zap' (Zapata Telephony Driver w/PRI)
  == Registered channel type 'Tor' (Zapata Telephony Driver w/PRI)
  == Registered application 'CallingPres'
  == Manager registered action ZapTransfer
  == Manager registered action ZapHangup
  == Manager registered action ZapDialOffhook
 
If I turn on pri debugging in Asterisk CLI (pri intense debug span 1) I get this every second:
--------------------------------------------------------------------------
> [00 01 7f ]
> Unnumbered frame:
> SAPI: 00  C/R: 0 EA: 0
>  TEI: 000        EA: 1
>   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode extended) ]
> 0 bytes of data
Sending Set Asynchronous Balanced Mode Extended
 
 
The other direction, if I try to call out from internal SIP phone:
------------------------------------------------------------
    -- Executing Dial("SIP/7001-da6d", "Zap/g1/098227655") in new stack
Jan 31 17:36:20 NOTICE[1256866752]: app_dial.c:527 dial_exec: Unable to create channel of type 'Zap'
  == Everyone is busy at this time
 
 
an anyone help, please!
 
Tomica Crnek
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20040131/95a511d2/attachment.htm