[asterisk-r2] Not receiving incoming calls

Mariano Bianchi marianito.bianchi at gmail.com
Thu Jan 6 14:53:05 UTC 2011


Hi everyone:
                 Here are the details of my issue:
Elastix 2.0 server with Asterisk 1.6.2.15, libopenR2 1.3.0, dahdi 2.4.0.,
libpri 1.4.11.5.
I have a Xorcom Astribank 2 USB connected to the server. The E1 is up and
running (telmex E1 R2, in Mar del Plata, Argentina), and the outbound calls
are working OK.
The problem is with the incoming calls. They are not working. I receive busy
tone when dialing. Here are the logs:

[Jan  6 17:45:58] DEBUG[5681] chan_dahdi.c: Chan 15 - Bits changed from 0x08
to 0x00
[Jan  6 17:45:58] DEBUG[5681] chan_dahdi.c: Chan 15 - CAS Persistence check
is enabled, waiting 500 ms
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 17 - Bits changed from 0x08
to 0x00
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 17 - CAS Persistence check
is enabled, waiting 500 ms
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 15 - calling timer 3
(cas_persistence_check) callback
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 15 - CAS signal 0x00 has
persisted, handling ...
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 15 - CAS Rx << [SEIZE] 0x00
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 15 - Initialized R2 MF
detector
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 15 - CAS Tx >> [SEIZE ACK]
0x0C
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 15 - CAS Raw Tx >> 0x0D
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 15 - Bits changed from 0x00
to 0x08
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 15 - CAS Persistence check
is enabled, waiting 500 ms
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 17 - calling timer 3
(cas_persistence_check) callback
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 17 - CAS signal 0x00 has
persisted, handling ...
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 17 - CAS Rx << [SEIZE] 0x00
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 17 - Initialized R2 MF
detector
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 17 - CAS Tx >> [SEIZE ACK]
0x0C
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 17 - CAS Raw Tx >> 0x0D
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 17 - Bits changed from 0x00
to 0x08
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 17 - CAS Persistence check
is enabled, waiting 500 ms
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 15 - calling timer 4
(cas_persistence_check) callback
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 15 - CAS signal 0x08 has
persisted, handling ...
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 15 - CAS Rx << [CLEAR
FORWARD] 0x08
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 15 - Call ended
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 15 - CAS Tx >> [IDLE] 0x08
[Jan  6 17:45:59] DEBUG[5681] chan_dahdi.c: Chan 15 - CAS Raw Tx >> 0x09
[Jan  6 17:46:00] DEBUG[5681] chan_dahdi.c: Chan 17 - calling timer 4
(cas_persistence_check) callback
[Jan  6 17:46:00] DEBUG[5681] chan_dahdi.c: Chan 17 - CAS signal 0x08 has
persisted, handling ...
[Jan  6 17:46:00] DEBUG[5681] chan_dahdi.c: Chan 17 - CAS Rx << [CLEAR
FORWARD] 0x08
[Jan  6 17:46:00] DEBUG[5681] chan_dahdi.c: Chan 17 - Call ended
[Jan  6 17:46:00] DEBUG[5681] chan_dahdi.c: Chan 17 - CAS Tx >> [IDLE] 0x08
[Jan  6 17:46:00] DEBUG[5681] chan_dahdi.c: Chan 17 - CAS Raw Tx >> 0x09

Do you know what could be happening?
Thanks,
Ing. Mariano Bianchi.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-r2/attachments/20110106/cbe2389f/attachment.htm>


More information about the asterisk-r2 mailing list