Re: [asterisk-users] PRI Down but zaptel lets calls through

I havent gotten any responses so i would like to add some more info that might help someone give me some advice. 

 

At first i thought that the reason it wasnt giving an error or falling through was because the zaptel status of the wanpipe was OK, but now i am monitoring that it still doesnt error or fall through even if the status is RED.  This doesnt make sense to me if zaptel knows its down then why is it connecting these calls (or thinks it is)

 

here is an example log:

 

[Jan  7 13:22:29] VERBOSE[6160] logger.c:     -- Executing [5735551815@from-sip:1] Set("SIP/802-082d2a58", "CALLERI
D(Num)=5735553977") in new stack
[Jan  7 13:22:29] VERBOSE[6160] logger.c:     -- Executing [5735551815@from-sip:2] Dial("SIP/802-082d2a58", "ZAP/G1
/19736631815|60") in new stack
[Jan  7 13:22:29] VERBOSE[6160] logger.c:     -- Called G1/15735551815
[Jan  7 13:22:33] VERBOSE[6160] logger.c:     -- Zap/1-1 answered SIP/802-082d2a58
[Jan  7 13:22:45] VERBOSE[6160] logger.c:     -- Hungup 'Zap/1-1'
[Jan  7 13:22:45] VERBOSE[6160] logger.c:   == Spawn extension (from-sip, 5735551815, 2) exited non-zero on 'SIP/80
2-082d2a58'

here is the relevant extensions.conf:

$maintrunk is a variable for ZAP/G1

 

exten => _1NXXNXXXXXX,1,Set(CALLERID(Num)=5735553977)
exten => _1NXXNXXXXXX,2,ChanIsAvail(${MAINTRUNK})
exten => _1NXXNXXXXXX,3,Dial(${MAINTRUNK}/${EXTEN},60)
exten => _1NXXNXXXXXX,4,Hangup

 

exten => _1NXXNXXXXXX,103,NoOp(Trying 2nd)
exten => _1NXXNXXXXXX,104,Dial(${SECONDTRUNK}/${EXTEN},60)
exten => _1NXXNXXXXXX,105,Hangup

 

here is zap show status:

 

Description                              Alarms     IRQ        bpviol     CRC4
Wildcard TDM400P REV I Board 1           OK         0          0          0
wanpipe1 card 0                          RED        0          0          0

 

As you can see from the log it never jumps on error to the 2nd trunk.  it actually thinks that the call is going through till it doesnt and the caller hangs up.  Also i added the chanisavail in the code above after that log section and it still doesnt work.

 

thanks

 

mike

 

 

---

From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Michael J. Liberatore
Sent: Friday, January 11, 2008 12:55 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [asterisk-users] PRI Down but zaptel lets calls through

Hi, i am having a problem with my point to point t1, which is being resolved and is a seperate issue.  sangoma support has been a huge help and i am waiting on verizon to increase the signal output of the smartjack.

 

But my issue is that in the meantime my fallover extensions arent working.  Well they are on the CPE side but not on the NET side.  The NET side still thinks its making calls, they obviously dont go through, and they dont return errors.  I tried adding ChanIsAvail hoping that would detect the line is down but thats not working either.  So basically i have no way to fail over the calls.  I have the code in place to have the calls re routed over iax but its just not working since asterisk thinks the calls are going through until the person hangs up. 

 

So can anyone help me get this working properly?  There has got to be a way to have this work, the pri span registers as "Down" so i would think asterisk would realize it cant make calls over those zap channels, but...

 

thanks in advance.

 

mike

 

 

This E-mail, including any attachments, may be intended solely for the personal and confidential use of the sender and recipient(s) named above. This message may include advisory, consultative and/or deliberative material and, as such, would be privileged and confidential and not a public document. Pursuant to 42 CFR, any information in this e-mail identifying a former, present, or potential client of Straight & Narrow is confidential. If you have received this e-mail in error, you must not review, transmit, convert to hard copy, copy, use or disseminate this e-mail or any attachments to it and you must delete this message. You are requested to notify the sender by return e-mail.