Hey everyone,
A few employees have noticed some problem here and there when trying to
make outgoing phone calls. After it happens, they try again, and are
able to call through.
The dial plan for outbound calling looks like below. Which I know they
are getting to the Congestion part (which explains the busy) but what I
can't seem to figure out is the cause for why they are getting sent there.
exten => s,1,SetCallerID(${ARG1})
exten => s,2,Wait(2)
exten => s,3,Dial(${TRUNK1}/${ARG2})
exten => s,4,Congestion(10)
exten => s,104,Congestion(10)
The log for a call looked like this
May 26 12:21:08 VERBOSE[6997] logger.c: -- Channel 0/4, span 1 got
hangup request
May 26 12:21:08 VERBOSE[16613] logger.c: -- Zap/4-1 is circuit-busy
May 26 12:21:08 VERBOSE[16613] logger.c: -- Hungup 'Zap/4-1'
May 26 12:21:08 VERBOSE[16613] logger.c: == Everyone is busy/congested
at this time (1:0/1/0)
My question is it asterisk having an issue with the PRI or is the PRI
really reporting the number is busy. I know one case like this I was
calling home, and which when I got through to them, they were not even
on the phone. Are there any tests that I can run on the T1 card in the
server to the PRI? Any suggestions would be helpful.
Kevin
I think asterisk dropping you to s-BUSY, s-CONGESTED, s-UNREACHABLE priority, better have a look there (you can play a busy tone, or playback(called-party-is-busy))> A few employees have noticed some problem here and there when trying to > make outgoing phone calls. After it happens, they try again, and are > able to call through. > > The dial plan for outbound calling looks like below. Which I know they > are getting to the Congestion part (which explains the busy) but what I > can't seem to figure out is the cause for why they are getting sent there. > > exten => s,1,SetCallerID(${ARG1}) > exten => s,2,Wait(2) > exten => s,3,Dial(${TRUNK1}/${ARG2}) > exten => s,4,Congestion(10) > exten => s,104,Congestion(10) > > The log for a call looked like this > > May 26 12:21:08 VERBOSE[6997] logger.c: -- Channel 0/4, span 1 got > hangup request > May 26 12:21:08 VERBOSE[16613] logger.c: -- Zap/4-1 is circuit-busy > May 26 12:21:08 VERBOSE[16613] logger.c: -- Hungup 'Zap/4-1' > May 26 12:21:08 VERBOSE[16613] logger.c: == Everyone is busy/congested > at this time (1:0/1/0) > > My question is it asterisk having an issue with the PRI or is the PRI > really reporting the number is busy. I know one case like this I was > calling home, and which when I got through to them, they were not even > on the phone. Are there any tests that I can run on the T1 card in the > server to the PRI? Any suggestions would be helpful. > > Kevin > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users-- WoodOO-[P]an[G]alaktikan[A]gent-People <][> http://shadow.pganet.com wpeople@shadow.pganet.com]iCQ#33118021[wpeople.on.iRCNet]wpeople@RedHat.users
I'd change s,104 to something along the lines of a playback for debugging purposes just to be sure, but it looks as though all of your channels are busy. The way I am reading that is that you have 4 voice channels on your PRI, is that correct? Could you already have 4 simultaneous calls going on when this call is placed? Other than that, the only thing I can think of is that you are getting an all circuits are busy from your carrier. Haven't yet encountered this, so I don't know how this is reported on a PRI. I guess one more thing, are you sure you are dialing the correct number? Maybe one more item, and this goes along with the first. Is TRUNK1 is defined as a group? I ask this because if not, then I believe Asterisk will use only the defined channel and not go to the next available channel. That being the case, you cannot have more than 1 simultaneous call. On 5/26/06, Kevin Smith <kevin.smith@mercury.net> wrote:> > Hey everyone, > > A few employees have noticed some problem here and there when trying to > make outgoing phone calls. After it happens, they try again, and are > able to call through. > > The dial plan for outbound calling looks like below. Which I know they > are getting to the Congestion part (which explains the busy) but what I > can't seem to figure out is the cause for why they are getting sent there. > > exten => s,1,SetCallerID(${ARG1}) > exten => s,2,Wait(2) > exten => s,3,Dial(${TRUNK1}/${ARG2}) > exten => s,4,Congestion(10) > exten => s,104,Congestion(10) > > The log for a call looked like this > > May 26 12:21:08 VERBOSE[6997] logger.c: -- Channel 0/4, span 1 got > hangup request > May 26 12:21:08 VERBOSE[16613] logger.c: -- Zap/4-1 is circuit-busy > May 26 12:21:08 VERBOSE[16613] logger.c: -- Hungup 'Zap/4-1' > May 26 12:21:08 VERBOSE[16613] logger.c: == Everyone is busy/congested > at this time (1:0/1/0) > > My question is it asterisk having an issue with the PRI or is the PRI > really reporting the number is busy. I know one case like this I was > calling home, and which when I got through to them, they were not even > on the phone. Are there any tests that I can run on the T1 card in the > server to the PRI? Any suggestions would be helpful. > > Kevin > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-- Lacy Moore Aspendora, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060528/64488d6b/attachment.htm