[Asterisk-Users] Problems with E100P
Carlos Hernandez
carlosh at linuxservices.co.nz
Tue Aug 10 17:20:31 MST 2004
Guys:
Have you sorted this issues?
I am interested to know if C.A.S. is supported.
Any idea?
I saw googled some posts from the developers, but as far as January this
year, it was still under development.
Much appreciated beforehand,
Carlos H.
Marcelo Rodriguez wrote:
>Well I turn on the pri intense debuging and the only message that I
>could find was this:
> [ 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
>
>Also Scott was right I was using the wrong setting , changes the
>zaptel.conf file with this
>span=1,1,0.ccs,hdb3
>
>the /proc/zaptel/1 now shows this :
>Span 1: WCT1/0 "Digium Wildcard E100P E1/PRA Card 0" HDB3/CCS
>ClockSource
>
>But I can't still get the Zap channel to dial , any other thoughts?
>
>
> Thanks in advance
>
>Marcelo Rodriguez
>
>
>
>On Wed, 2004-08-04 at 09:58, Horacio J. Peña wrote:
>
>
>>>Well as you sugested I changed to ccs, hdb3 and nothing happen. Well the
>>>message on /proc/zaptel/1 changes to
>>>Span 1: WCT1/0 "Digium Wildcard E100P E1/PRA Card 0" HDB3/CCS YELLOW
>>>ClockSource
>>>But at the end when I try to dial I still have the same errors
>>>
>>>
>>> Any thoughts?
>>>
>>>
>>I'm very new to asterisk, so take my words with a grain of salt.
>>
>>First, you should ask your provider what signalling type you should use (ami/hdb3,
>>cas/ccs, crc4/nocrc) Then configure that on zaptel.conf
>>
>>On asterisk, "pri intense debug span 1" will let you see anything that is
>>happening over the E1.
>>
>>
>>
>>>Saludos>!
>>>
>>>
>>Saludos? Si hablas castellano no nos gastemos en usar ingles :-)
>>
>>
>>
>>>Aug 4 09:40:51 DEBUG[1217602880]: pbx.c:1255 pbx_extension_helper:
>>>Launching 'Dial'
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 1
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 2
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 3
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 4
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 5
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 6
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 7
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 8
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 9
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 10
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 11
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 12
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 13
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 14
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 15
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 17
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 18
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 19
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 20
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 21
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 22
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 23
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 24
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 25
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 26
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 27
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 28
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 29
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 30
>>>Aug 4 09:40:51 DEBUG[1217602880]: chan_zap.c:6535 zt_request: Using
>>>channel 31
>>>Aug 4 09:40:51 NOTICE[1217602880]: app_dial.c:714 dial_exec: Unable to
>>>create channel of type 'Zap'
>>> == Everyone is busy/congested at this time
>>>Aug 4 09:40:51 DEBUG[1217602880]: app_dial.c:974 dial_exec: Exiting
>>>with DIALSTATUS=CHANUNAVAIL.
>>>
>>>
>>>
>>>
>>>
>>>On Wed, 2004-08-04 at 09:28, Horacio J. Peña wrote:
>>>
>>>
>>>>>[zaptel.conf]
>>>>>span=1,1,0,cas,ami
>>>>>
>>>>>
>>>>Are you sure that "cas,ami" is correct? I'm using "ccs,hdb3"
>>>>
>>>>Saludos,
>>>> HoraPe
>>>>---
>>>>Horacio J. Peña
>>>>horape at compendium.com.ar
>>>>horape at uninet.edu
>>>>
>>>>
>
>_______________________________________________
>Asterisk-Users mailing list
>Asterisk-Users at lists.digium.com
>http://lists.digium.com/mailman/listinfo/asterisk-users
>To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
>
>
>
>
More information about the asterisk-users
mailing list