[asterisk-r2] OpenR2 Thailand problem
Peter Lindquist
peter.lindquist.th at gmail.com
Tue Oct 28 00:38:41 CDT 2008
Dear all,
Trying to get OpenR2 working in Thailand with TOT (Telephone
Organization of Thailand). Unfortunately I have very little information
from TOT, they basically just say it's a E1 CAS R2 they provide.
I have latest Trixbox set up together with libmfcr2 (OpenR2 version:
0.1.1, revision: 64) and asterisk compiled from the svn source
(1.4.21.2) from libopenr2.org.
My problems are the following:
1) When I make an incoming call - there is absolutely nothing happening,
I see no ring indication or anything on the PBX. The call is eventually
timed out by my telco.
2) When I make an outgoing call I see the following in the asterisk log:
[Oct 27 21:06:32] DEBUG[13425] chan_zap.c: no MFC/R2 category specified
for chan Zap/1-1, using default National Subscriber
[Oct 27 21:06:32] DEBUG[13425] chan_zap.c: Chan 1 - Attempting to make
call (ANI=2133, DNIS=0819369108, category=National Subscriber)
[Oct 27 21:06:32] DEBUG[13425] chan_zap.c: Chan 1 - ABCD Raw Rx << 0x09
[Oct 27 21:06:32] DEBUG[13425] chan_zap.c: Chan 1 - No change in bits
[Oct 27 21:06:32] DEBUG[13425] chan_zap.c: Chan 1 - Call started at Mon
Oct 27 21:06:32 2008 on chan 1
[Oct 27 21:06:32] DEBUG[13425] chan_zap.c: Chan 1 - ABCD Tx >> [SEIZE] 0x00
[Oct 27 21:06:32] DEBUG[13425] chan_zap.c: Chan 1 - ABCD Raw Tx >> 0x03
[Oct 27 21:06:32] VERBOSE[13425] logger.c: -- Called g0/0819369108
[Oct 27 21:06:40] DEBUG[13425] chan_zap.c: Chan 1 - calling callback on
chan 1
[Oct 27 21:06:40] WARNING[13425] chan_zap.c: Chan 1 - Seize Timeout Expired!
[Oct 27 21:06:40] ERROR[13425] chan_zap.c: Chan 1 - Protocol error.
Reason = Seize Timeout, R2 State = Seize Transmitted, MF state = MF
Engine Off, MF Group$
[Oct 27 21:06:40] DEBUG[13425] chan_zap.c: Chan 1 - DNIS = 0819369108,
ANI = 2133, Last MF Signal =
[Oct 27 21:06:40] DEBUG[13425] chan_zap.c: Chan 1 - ABCD Tx >> [IDLE] 0x08
[Oct 27 21:06:40] DEBUG[13425] chan_zap.c: Chan 1 - ABCD Raw Tx >> 0x0B
[Oct 27 21:06:40] ERROR[13425] chan_zap.c: MFC/R2 protocol error on chan
1: Seize Timeout
[Oct 27 21:06:40] DEBUG[13425] chan_zap.c: disconnecting MFC/R2 call on
chan 1
3) When reloading chan_zap I see:
[Oct 27 21:10:09] VERBOSE[13434] logger.c: -- Reloading module
'chan_zap.so' (Zapata Telephony)
[Oct 27 21:10:09] VERBOSE[13434] logger.c: == Parsing
'/etc/asterisk/zapata.conf': [Oct 27 21:10:09] VERBOSE[13434] logger.c:
Found
[Oct 27 21:10:09] WARNING[13434] chan_zap.c: Ignoring signalling
[Oct 27 21:10:09] WARNING[13434] chan_zap.c: Ignoring mfcr2_variant
[Oct 27 21:10:09] WARNING[13434] chan_zap.c: Ignoring mfcr2_get_ani_first
[Oct 27 21:10:09] WARNING[13434] chan_zap.c: Ignoring mfcr2_max_ani
[Oct 27 21:10:09] WARNING[13434] chan_zap.c: Ignoring mfcr2_max_dnis
[Oct 27 21:10:09] WARNING[13434] chan_zap.c: Ignoring mfcr2_category
[Oct 27 21:10:09] WARNING[13434] chan_zap.c: Ignoring mfcr2_logdir
[Oct 27 21:10:09] WARNING[13434] chan_zap.c: Ignoring mfcr2_logging
[Oct 27 21:10:09] WARNING[13434] chan_zap.c: Ignoring mfcr2_call_files
[Oct 27 21:10:09] WARNING[13434] chan_zap.c: Ignoring
mfcr2_metering_pulse_timeout
[Oct 27 21:10:09] VERBOSE[13434] logger.c: -- Reconfigured channel
1, MFC/R2 signalling
..
[Oct 27 21:10:09] VERBOSE[13434] logger.c: -- Reconfigured channel
31, MFC/R2 signalling
Even if my /etc/asterisk/zapata.conf has:
;MFCR2 settings
signalling=mfcr2
mfcr2_variant=cn
mfcr2_get_ani_first=no
mfcr2_max_ani=20
mfcr2_max_dnis=7
mfcr2_category=national_subscriber
mfcr2_logdir=span1
mfcr2_logging=all
mfcr2_call_files=yes
mfcr2_metering_pulse_timeout=-1
callgroup=0
pickupgroup=0
channel => 1-15,17-31
4) Some other info:
core show channeltypes:
Zap Zapata Telephony Driver w/PRI w/OPENR2 no
yes no
mfcr2 show channels:
Chan Variant Max ANI Max DNIS ANI First Immediate Accept Tx State Rx State
1 CN 20 7 No No IDLE IDLE
2 CN 20 7 No No IDLE BLOCK
..
31 CN 20 7 No No IDLE BLOCK
zttool:
Current Alarms: No alarms.
Sync Source: Rhino R1T1 E1/PRA Card 0
IRQ Misses: 0
Bipolar Viol: 0
Tx/Rx Levels: 0/ 0
Total/Conf/Act: 31/ 31/ 30
1111111111222222222233
1234567890123456789012345678901
TxA 111111111111111-111111111111111
TxB 000000000000000-000000000000000
TxC 111111111111111-111111111111111
TxD 111111111111111-111111111111111
RxA 111111111111111-111111111111111
RxB 011111111111111-111111111111111
RxC 011111111111111-111111111111111
RxD 111111111111111-111111111111111
I could really use some help in how to troubleshoot this and get it working!
Best regards,
Peter Lindqvist
www.voxion.net / www.voipperiod.com
More information about the asterisk-r2
mailing list