Ernie Dunbar
2010-Nov-12 18:17 UTC
[asterisk-users] Sending calls to a particular T1 port.
We have two Asterisk servers. One is a live server supporting our customers, and the other is a backup server that's being upgraded and pressed into service. Both servers have a Digium TE405P T1 card in them, and in order to test the T1 service on the backup server, I've created a T1 crossover cable (as per http://www.voip-info.org/wiki/view/crossover+T1+cable) that goes from port 4 on the live server to port 1 on the backup server. Both TE405P's have been configured, and I get a green light on port 4 on the live server and port 1 on the backup server. The problem I have is trying to route calls through this T1 connection. To the best of my knowledge, this configuration on the live server should work: In /etc/asterisk/chan_dahdi.conf: group=4 context=local switchtype = national signalling = pri_cpe channel => 73-95 context = default group = 63 In /etc/asterisk/extensions.conf: exten => _*88,1,Dial(DAHDI/g4/123456789) However, in the Asterisk console, I get this error on the live server: -- Executing [*88 at lightspeedout:1] Dial("SCCP/lightspeed7-00000062", "DAHDI/g4/123456789") in new stack [Nov 12 09:24:41] WARNING[1970]: app_dial.c:1286 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) == Everyone is busy/congested at this time (1:0/0/1) == Auto fallthrough, channel 'SCCP/lightspeed7-00000062' status is 'CHANUNAVAIL' And no messages at all on the backup server, except this one every 4 seconds: [Nov 12 10:08:04] WARNING[4473]: chan_dahdi.c:4169 pri_find_dchan: No D-channels available! Using Primary channel 24 as D-channel anyway! Which Googling reveals to be a fairly mundane and harmless warning message (it happens on real T1's apparently, and isn't related to any kind of outage). Also, I'm not entirely sure how to enable changes to chan_dahdi.conf without restarting asterisk or otherwise killing the 15+ DAHDI channels in progress. Doing this at off-peak times is very slow, as I'm asleep during those times, and thus it can only happen once per day.
Jonathan Thurman
2010-Nov-12 18:42 UTC
[asterisk-users] Sending calls to a particular T1 port.
On Fri, Nov 12, 2010 at 10:17 AM, Ernie Dunbar <maillist at lightspeed.ca> wrote:> that goes from port 4 on the live server to port 1 on the backup server.> In /etc/asterisk/chan_dahdi.conf: > > group=4 > context=local > switchtype = national > signalling = pri_cpe > channel => 73-95 > context = default > group = 63What is the configuration on the backup server? One side needs to act as the network side with signalling=pri_net> In /etc/asterisk/extensions.conf: > > exten => _*88,1,Dial(DAHDI/g4/123456789) > > However, in the Asterisk console, I get this error on the live server: > > ? ?-- Executing [*88 at lightspeedout:1] Dial("SCCP/lightspeed7-00000062", > "DAHDI/g4/123456789") in new stack > [Nov 12 09:24:41] WARNING[1970]: app_dial.c:1286 dial_exec_full: Unable to > create channel of type 'DAHDI' (cause 0 - Unknown) > ?== Everyone is busy/congested at this time (1:0/0/1) > ?== Auto fallthrough, channel 'SCCP/lightspeed7-00000062' status is > 'CHANUNAVAIL'What is the output of 'pri show spans' or 'dahdi show channels'? Specifically does Asterisk recognize the channels as up/active an In Service. -Jonathan
Steve Totaro
2010-Nov-12 18:45 UTC
[asterisk-users] Sending calls to a particular T1 port.
On Fri, Nov 12, 2010 at 1:17 PM, Ernie Dunbar <maillist at lightspeed.ca>wrote:> We have two Asterisk servers. One is a live server supporting our > customers, and the other is a backup server that's being upgraded and > pressed into service. Both servers have a Digium TE405P T1 card in them, > and in order to test the T1 service on the backup server, I've created a > T1 crossover cable (as per > http://www.voip-info.org/wiki/view/crossover+T1+cable) that goes from port > 4 on the live server to port 1 on the backup server. Both TE405P's have > been configured, and I get a green light on port 4 on the live server and > port 1 on the backup server. > > The problem I have is trying to route calls through this T1 connection. To > the best of my knowledge, this configuration on the live server should > work: > > In /etc/asterisk/chan_dahdi.conf: > > group=4 > context=local > switchtype = national > signalling = pri_cpe > channel => 73-95 > context = default > group = 63 > > In /etc/asterisk/extensions.conf: > > exten => _*88,1,Dial(DAHDI/g4/123456789) > > However, in the Asterisk console, I get this error on the live server: > > -- Executing [*88 at lightspeedout:1] Dial("SCCP/lightspeed7-00000062", > "DAHDI/g4/123456789") in new stack > [Nov 12 09:24:41] WARNING[1970]: app_dial.c:1286 dial_exec_full: Unable to > create channel of type 'DAHDI' (cause 0 - Unknown) > == Everyone is busy/congested at this time (1:0/0/1) > == Auto fallthrough, channel 'SCCP/lightspeed7-00000062' status is > 'CHANUNAVAIL' > > And no messages at all on the backup server, except this one every 4 > seconds: > > [Nov 12 10:08:04] WARNING[4473]: chan_dahdi.c:4169 pri_find_dchan: No > D-channels available! Using Primary channel 24 as D-channel anyway! > > Which Googling reveals to be a fairly mundane and harmless warning message > (it happens on real T1's apparently, and isn't related to any kind of > outage). > > Also, I'm not entirely sure how to enable changes to chan_dahdi.conf > without restarting asterisk or otherwise killing the 15+ DAHDI channels in > progress. Doing this at off-peak times is very slow, as I'm asleep during > those times, and thus it can only happen once per day. > > >On the main server, if you type, dahdi show channels or whatever, do you see the fourth span? Your configuration should probably be signalling = pri_net and the new server should be signalling = pri_cpe Thanks, Steve T -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20101112/a48636c1/attachment.htm
Jimmy Godbout
2010-Nov-12 22:48 UTC
[asterisk-users] Sending calls to a particular T1 port.
Don't forget to setup a d-chan for that group since it's not part of the 1st one.> -----Original Message----- > From: maillist at lightspeed.ca > Sent: Fri, 12 Nov 2010 12:44:39 -0800 > To: asterisk-users at lists.digium.com > Subject: Re: [asterisk-users] Sending calls to a particular T1 port. > > Oh, this is most excellent. Although it means that my google-fu has > failed > me. ;) > >> On Fri, Nov 12, 2010 at 1:42 PM, Jonathan Thurman >> <jonathan at thurmantech.com>wrote: >> I didn't read the whole thing, but it looks pretty OK at a glance. >> >> http://www.cadvision.com/blanchas/Asterisk/DahdiT1trunk.html >> >> I hope that helps, >> Steve Totaro >> -- >> _____________________________________________________________________ >> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >> New to Asterisk? Join us for a live introductory webinar every Thurs: >> http://www.asterisk.org/hello >> >> asterisk-users mailing list >> To UNSUBSCRIBE or update options visit: >> http://lists.digium.com/mailman/listinfo/asterisk-users > > > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users____________________________________________________________ Share photos & screenshots in seconds... TRY FREE IM TOOLPACK at http://www.imtoolpack.com/default.aspx?rc=if1 Works in all emails, instant messengers, blogs, forums and social networks.
Seemingly Similar Threads
- Asterisk 1.6 produces *many* zombie processes on Debian.
- How do *you* test your changes to dialplans ruled by GotoIfTime?
- SIP connections over OpenVPN connection get one-way voice.
- Problem compiling res_fax_spandsp.c on Debian server.
- SIP connections over OpenVPN connection get one-way voice.