Problem dialing over PRI?

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Problem dialing over PRI?

Postby Nortelguy » Fri Feb 06, 2009 5:54 pm

getting the following errors

== Manager 'sendcron' logged on from 127.0.0.1
-- Executing AGI("Local/913057815757@default-9587,2", "agi://127.0.0.1:4577/call_log") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing Dial("Local/913057815757@default-9587,2", "Zap/g1/3057815757||To") in new stack
Feb 6 17:52:04 NOTICE[5321]: app_dial.c:1076 dial_exec_full: Unable to create channel of type 'Zap' (cause 34 - Circuit/channel congestion)
== Everyone is busy/congested at this time (1:0/1/0)
-- Executing Hangup("Local/913057815757@default-9587,2", "") in new stack
== Spawn extension (default, 913057815757, 3) exited non-zero on 'Local/913057815757@default-9587,2'
-- Executing DeadAGI("Local/913057815757@default-9587,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----34-----CONGESTION----------") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1

------
dialer*CLI> zap show status
Description Alarms IRQ bpviol CRC4
wanpipe1 card 0 OK 0 0 0
dialer*CLI>

----
Extensions.conf
; dial a long distance outbound number
; This 'o' Dial flag is VERY important for VICIDIAL on outbound calls
exten => _91NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91NXXNXXXXXX,2,Dial(${TRUNK}/${EXTEN:1},,To)
exten => _91NXXNXXXXXX,3,Hangup

; local area code
exten => _91305NXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91305NXXXXXX,2,Dial(${TRUNK}/${EXTEN:2},,To)
exten => _91305NXXXXXX,3,Hangup

; local area code
exten => _91786NXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91786NXXXXXX,2,Dial(${TRUNK}/${EXTEN:2},,To)
exten => _91786NXXXXXX,3,Hangup
-----
This is a sangoma card .. Any ideas?
Nortelguy
 
Posts: 120
Joined: Wed Sep 24, 2008 9:06 pm

Postby williamconley » Fri Feb 06, 2009 11:38 pm

Hey, Nortelguy, please remember to post your configuration (read the stickies).

Unable to create channel of type 'Zap'


This would be an Asterisk issue, vicidial cannot work with channels that do not dial (of course ... if they will dial, but not in Vicidial, that's a different story).

Have you demonstrated that your sangoma card is properly installed with the appropriate tools before attempting vicidial calls with it?
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: Vicidial Agent Only Beep - Beta
http://www.PoundTeam.com # 352-269-0000 # 888-883-8488 # +44(203) 769-2294
williamconley
 
Posts: 20427
Joined: Wed Oct 31, 2007 4:17 pm
Location: Bartow, FL (In the boondocks)

Postby mflorell » Sat Feb 07, 2009 2:07 am

Is this a PRI?

Have you tried pri debug?

is the D channel up?
mflorell
Site Admin
 
Posts: 18406
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

pri

Postby arvindsandilya24 » Sat Feb 07, 2009 8:39 am

Hi,

This is the problem of zaptel is not configured properly.
Just check what is configured with TRUNK in extensions.conf

exten => _91NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91NXXNXXXXXX,2,Dial(${TRUNK}/${EXTEN:1},,To)
exten => _91NXXNXXXXXX,3,Hangup

Here just be clear that TRUNK= ? in extension.conf.
If you configured all channels in a group in zapata.conf such as group = 0
Then in extension.conf , TRUNK = g0 should be.

Thanks & regards
Arvind
arvindsandilya24
 
Posts: 192
Joined: Sun Oct 12, 2008 4:33 am

Postby Nortelguy » Sat Feb 07, 2009 11:28 am

This is all I get over and over ona debug no matter if I am placing a call or not it never changes.

> Unnumbered frame:
> SAPI: 00 C/R: 0 EA: 0
> TEI: 000 EA: 1
> M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
> 0 bytes of data
Nortelguy
 
Posts: 120
Joined: Wed Sep 24, 2008 9:06 pm

Postby Nortelguy » Sat Feb 07, 2009 11:49 am

Looks like the D-Chan is down .. argh.
Nortelguy
 
Posts: 120
Joined: Wed Sep 24, 2008 9:06 pm

Postby Baylink » Sat Feb 07, 2009 1:11 pm

And, the most important questions not answered in this post:

Was this working, and it just broke?

Or is it new, and you have never had it work?

Generally, you'll know if your D-channels are down from looking at the logs; it will continually try to bring them up, and then notice that they're not.
Baylink
 
Posts: 77
Joined: Wed Aug 06, 2008 10:58 am


Return to Support

Who is online

Users browsing this forum: Google [Bot] and 103 guests