[asterisk-users] E1 R2 Congestion Status
I have a 'CONGESTION' Status with R2 protocol.
While testing this scenario sip GW--àAsterisk Digium E1 R2
ProtocolàCisco E1 R2 protocolàsip Gw
Find below my error and configuration ,where are the errors in my
configuration ?
=
Connected to Asterisk SVN-branch-1.6.2-r235775 currently running on
rev-212-98-156-56 (pid = 3614)
Verbosity is at least 3
== Using SIP RTP CoS mark 5
-- Executing [00223...@default:1] Dial(SIP/98.34.56.216-000e,
DAHDI/g1/00223344) in new stack
[Dec 22 06:02:49] WARNING[4756]: app_dial.c:1745 dial_exec_full: Unable to
create channel of type 'DAHDI' (cause 34 - Circuit/channel congestion)
== Everyone is busy/congested at this time (1:0/1/0)
-- Auto fallthrough, channel 'SIP/98.34.56.216-000e' status is
'CONGESTION'
Cisco Gateway
show controller
Controller E1 slot(0)/port(0)
E1 Link is UP
No Alarm detected.
Applique type is Channelized E1.
Framing is CRC4, Line Code is HDB3.
Signalling type is R2-MFC.
0 Line Code Violations, 0 Framing Bit Errors
0 Far End Block Errors, 0 CRC Errors
signalling type = r2
clock source = slave
channel group 0 = 1-31
1 2 3
allocated timeslots = YYYNYYY
outgoing barred channel group =
channel order = ascending
b-channel negotiation = exclusive
overlap receiving by forced = disabled
overlap sending by forced = disabled
protocol side = network
R2 get calling number = none
ISDN virtual connect = disabled
ISDN Layer 2 is DOWN
ISDN Values
ISDN Layer 2 values
k= 7
N200 = 3
N201 = 260
T200 = 1 seconds
T203 = 10 seconds
ISDN Layer 3 values
T301 = 180 seconds
T303 = 4 seconds
T304 = 20 seconds
T305 = 30 seconds
T306 = 30 seconds
T308 = 4 seconds
T310 = 10 seconds
T313 = 10 seconds
T316 = 120 seconds
T322 = 4 seconds
T309 = 90 seconds
N303 = 1
---
/etc/asterisk/chan_dahdi.conf
[trunkgroups]
signalling=mfcr2
mfcr2_variant=mx
trunkgroup = 1,16
spanmap = 1,1,1
[channels]
signalling=mfcr2
mfcr2_variant=mx
context=default
signalling=mfcr2
mfcr2_variant=mx
signalling=mfcr2
mfcr2_variant=mx
usecallerid=yes
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
group=1
callgroup=1
pickupgroup=1
callerid = asreceived
useincomingcalleridondahditransfer = yes
tonezone = 0 ; 0 is US
channel = 1-15,17-31
signalling=mfcr2
mfcr2_variant=itu
mfcr2_max_ani=7
mfcr2_max_dnis=8
mfcr2_get_ani_first=no
mfcr2_category=national_subscriber
mfcr2_logdir=span1
mfcr2_logging=all
;EOF
cat /etc/dahdi/system.conf
# Autogenerated by /usr/sbin/dahdi_genconf on Tue Dec 22 01:59:02 2009
# If you edit this file and execute /usr/sbin/dahdi_genconf again,
# your manual changes will be LOST.
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: TE4/0/1 T4XXP (PCI) Card 0 Span 1 (MASTER) HDB3/CCS/CRC4 RED
span=1,1,0,cas,hdb3,crc4
# termtype: te
#bchan=1-15,17-31
#dchan=16
cas=1-15:1101
dchan=16
cas=17-31:1101
echocanceller=mg2,1-15,17-31
# Span 2: TE4/0/2 T4XXP (PCI) Card 0 Span 2 HDB3/CCS/CRC4 RED
span=2,2,0,ccs,hdb3,crc4
# termtype: te
bchan=32-46,48-62
dchan=47
echocanceller=mg2,32-46,48-62
# Span 3: TE4/0/3 T4XXP (PCI) Card 0 Span 3 HDB3/CCS/CRC4 RED
span=3,3,0,ccs,hdb3,crc4
# termtype: te
bchan=63-77,79-93
dchan=78
echocanceller=mg2,63-77,79-93
# Span 4: TE4/0/4 T4XXP (PCI) Card 0 Span 4 HDB3/CCS/CRC4 RED
span=4,4,0,ccs,hdb3,crc4
# termtype: te
bchan=94-108,110-124
dchan=109
echocanceller=mg2,94-108,110-124
# Global data
loadzone= us
defaultzone = us
[default]
exten = _X.,1,Dial(DAHDI/g1/${EXTEN})
*
No employee or agent is authorized to conclude any binding agreement on behalf
of Xplorium with another party by e-mail without express written confirmation
by an officer of Xplorium. Any views expressed by an individual in this
electronic message do not necessarily reflect views of Xplorium or its
subsidiaries and associates.
This electronic message and its attachments are solely addressed to the
addressee(s), and contain confidential information protected from disclosure
belonging to Xplorium.
If you are not the intended addressee of this electronic message and its
attachments, kindly delete it immediately from your system and notify the
sender by electronic mail. You must not copy this message or attachment or
disclose its content to any other
Re: [asterisk-users] E1 R2 Congestion Status
On Tue, Dec 22, 2009 at 9:08 AM, Khaled W Chehab kche...@xplorium.comwrote: I have a 'CONGESTION' Status with R2 protocol. While testing this scenario sip GW--àAsterisk –Digium E1 R2 ProtocolàCisco E1 R2 protocolàsip Gw Find below my error and configuration ,where are the errors in my configuration ? Typically you will be better off in the asterisk-r2 mailing list. Your message is more easily spotted by R2 people. First thing is to check you have green status in your E1, do you? and make sure you have the right clock settings, I never configured a cisco but it seems you configured the cisco to be a slave and I don't see any port in DAHDI system.conf with master clock settings. (span=1,0,0...etc) After that, enable R2 call logging using mfcr2_call_files=yes and pastebin the generated call file (if any), if no file is generated it means the problem is not at R2 but in your local trunk settings (may be dialing in the wrong group or something). -- Moises Silva Senior Software Engineer Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada t. 1 905 474 1990 x 128 | e. m...@sangoma.com ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] E1 R2 Congestion Status
Hello,
You are dialing 00223344 with what you show: DAHDI/g1/00223344
That is not a real PSTN number in any country as for as I know. Do you have
the proper outbound route setup? Is your outbound route stripping digits?!
-Bruce
On Tue, Dec 22, 2009 at 9:08 AM, Khaled W Chehab kche...@xplorium.comwrote:
I have a 'CONGESTION' Status with R2 protocol.
While testing this scenario sip GW--àAsterisk –Digium E1 R2 ProtocolàCisco
E1 R2 protocolàsip Gw
Find below my error and configuration ,where are the errors in my
configuration ?
=
Connected to Asterisk SVN-branch-1.6.2-r235775 currently running on
rev-212-98-156-56 (pid = 3614)
Verbosity is at least 3
== Using SIP RTP CoS mark 5
-- Executing [00223...@default:1] Dial(SIP/98.34.56.216-000e,
DAHDI/g1/00223344) in new stack
[Dec 22 06:02:49] WARNING[4756]: app_dial.c:1745 dial_exec_full: Unable to
create channel of type 'DAHDI' (cause 34 - Circuit/channel congestion)
== Everyone is busy/congested at this time (1:0/1/0)
-- Auto fallthrough, channel 'SIP/98.34.56.216-000e' status is
'CONGESTION'
Cisco Gateway
show controller
Controller E1 slot(0)/port(0)
E1 Link is UP
No Alarm detected.
Applique type is Channelized E1.
Framing is CRC4, Line Code is HDB3.
Signalling type is R2-MFC.
0 Line Code Violations, 0 Framing Bit Errors
0 Far End Block Errors, 0 CRC Errors
signalling type = r2
clock source = slave
channel group 0 = 1-31
1 2 3
allocated timeslots = YYYNYYY
outgoing barred channel group =
channel order = ascending
b-channel negotiation = exclusive
overlap receiving by forced = disabled
overlap sending by forced = disabled
protocol side = network
R2 get calling number = none
ISDN virtual connect = disabled
ISDN Layer 2 is DOWN
ISDN Values
ISDN Layer 2 values
k= 7
N200 = 3
N201 = 260
T200 = 1 seconds
T203 = 10 seconds
ISDN Layer 3 values
T301 = 180 seconds
T303 = 4 seconds
T304 = 20 seconds
T305 = 30 seconds
T306 = 30 seconds
T308 = 4 seconds
T310 = 10 seconds
T313 = 10 seconds
T316 = 120 seconds
T322 = 4 seconds
T309 = 90 seconds
N303 = 1
---
/etc/asterisk/chan_dahdi.conf
[trunkgroups]
signalling=mfcr2
mfcr2_variant=mx
trunkgroup = 1,16
spanmap = 1,1,1
[channels]
signalling=mfcr2
mfcr2_variant=mx
context=default
signalling=mfcr2
mfcr2_variant=mx
signalling=mfcr2
mfcr2_variant=mx
usecallerid=yes
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
group=1
callgroup=1
pickupgroup=1
callerid = asreceived
useincomingcalleridondahditransfer = yes
tonezone = 0 ; 0 is US
channel = 1-15,17-31
signalling=mfcr2
mfcr2_variant=itu
mfcr2_max_ani=7
mfcr2_max_dnis=8
mfcr2_get_ani_first=no
mfcr2_category=national_subscriber
mfcr2_logdir=span1
mfcr2_logging=all
;EOF
cat /etc/dahdi/system.conf
# Autogenerated by /usr/sbin/dahdi_genconf on Tue Dec 22 01:59:02 2009
# If you edit this file and execute /usr/sbin/dahdi_genconf again,
# your manual changes will be LOST.
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: TE4/0/1 T4XXP (PCI) Card 0 Span 1 (MASTER) HDB3/CCS/CRC4 RED
span=1,1,0,cas,hdb3,crc4
# termtype: te
#bchan=1-15,17-31
#dchan=16
cas=1-15:1101
dchan=16
cas=17-31:1101
echocanceller=mg2,1-15,17-31
# Span 2: TE4/0/2 T4XXP (PCI) Card 0 Span 2 HDB3/CCS/CRC4 RED
span=2,2,0,ccs,hdb3,crc4
# termtype: te
bchan=32-46,48-62
dchan=47
echocanceller=mg2,32-46,48-62
# Span 3: TE4/0/3 T4XXP (PCI) Card 0 Span 3 HDB3/CCS/CRC4 RED
span=3,3,0,ccs,hdb3,crc4
# termtype: te
bchan=63-77,79-93
dchan=78
echocanceller=mg2,63-77,79-93
# Span 4: TE4/0/4 T4XXP (PCI) Card 0 Span 4 HDB3/CCS/CRC4 RED
span=4,4,0,ccs,hdb3,crc4
# termtype: te
bchan=94-108,110-124
dchan=109
echocanceller=mg2,94-108,110-124
# Global data
loadzone= us
defaultzone = us
[default]
exten = _X.,1,Dial(DAHDI/g1/${EXTEN})
--
*
No employee or agent is authorized to conclude any binding agreement on
behalf of Xplorium with another party by e-mail without express written
confirmation by an officer of Xplorium. Any views expressed by an individual
in this electronic message do not necessarily reflect views of Xplorium or
its
