Page 1 of 1

Problem in Dahdi trunk [Solved]

PostPosted: Mon Nov 26, 2012 1:07 pm
by tux
Hello
i am new to goautodialer & i have tried many times to configure dahdi but no way :(
under carrier menu i added a zap with Globals String : TRUNK=DAHDI/g0
and dialplan :
Code: Select all
exten => _906XXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _906XXXXXXXX,2,Dial(${TRUNKX}/${EXTEN:1},,To)
exten => _906XXXXXXXX,3,Hangup

i got this logs in CLI
Code: Select all
Executing [8600051@default:1] MeetMe("Local/8600051@default-6ae4,2", "8600051|F") in new stack
  == Starting Local/8600051@default-6ae4,1 at default,910674977163,1 failed so falling back to exten 's'
-- Executing [i@default:1] Playback("Local/8600051@default-6ae4,1", "invalid") in new stack
Executing [h@default:1] DeadAGI("Local/8600051@default-6ae4,1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack


My Extensions.conf Headers :
Code: Select all
[general]
static=yes
writeprotect=no

[globals]
CONSOLE=Console/dsp                             ; Console interface for demo
TRUNK=DAHDI/g0                      ; Trunk interface
TRUNKX=Zap/r2                                   ; 2nd trunk interface
TRUNKIAX=IAX2/ASTtest1:test@10.10.10.16:4569    ; IAX trunk interface
TRUNKIAX1=IAX2/ASTtest1:test@10.10.10.16:4569   ; IAX trunk interface
;TRUNKBINFONE=IAX2/1112223333:PASSWORD@iax.xxx.xxx  ; IAX trunk interface
;SIPtrunk=SIP/1234:PASSWORD@sip.xx.yy; SIP trunk

Any help would be greatly appreciated.
Thanks.

Re: Problem in Dahdi trunk

PostPosted: Mon Nov 26, 2012 1:23 pm
by tux
On the other hand lsdahdi output :
[root@go ~]# lsdahdi
### Span 1: WCTDM/4 "Wildcard TDM400P REV I Board 5" (MASTER)
1 FXO FXSKS (SWEC: MG2)
2 FXO FXSKS (SWEC: MG2) RED
3 FXO FXSKS (SWEC: MG2) RED
4 FXO FXSKS (SWEC: MG2)
with 2 lines and
go*CLI> dahdi show channels
Chan Extension Context Language MOH Interpret

Thanks again.

Re: Problem in Dahdi trunk

PostPosted: Mon Nov 26, 2012 8:26 pm
by williamconley
exten => _906XXXXXXXX

default,910674977163

The number you dialed does not match the pattern you created for your trunk. 906 is not the same as 9106.

Re: Problem in Dahdi trunk

PostPosted: Tue Nov 27, 2012 8:07 am
by tux
Yes i see , i replaced 1 with my country code but still same problem.
is it possible to install freepbx with goautodialer ?

Re: Problem in Dahdi trunk

PostPosted: Tue Nov 27, 2012 9:13 am
by rsaaris
Have you tried using TRUNK instead of TRUNKX in the extensions.conf dialplan when calling out? Now it seems to call from TRUNKX ( ZAP/r2) and if you have configured your lines to use group 0 the calls won't work because the TRUNKX using group 2. You can check your SPAN groups from /etc/asterisk/dahdi-channels.conf.

Re: Problem in Dahdi trunk

PostPosted: Tue Nov 27, 2012 10:08 am
by tux
Thanks rsaaris.
I have tried TRUNK and TRUNKX , i can't find the chan_dahdi.conf file in /etc/asterisk where i can include dahdi-channels.conf .
i have found a sample file & copied it to /etc/asterisk !
For SPAN group in dahdi-channels.conf

Code: Select all
 Span 1: WCTDM/4 "Wildcard TDM400P REV I Board 5" (MASTER)
;;; line="1 WCTDM/4/0 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
;
it means DAHDI/g0 ?

Re: Problem in Dahdi trunk

PostPosted: Tue Nov 27, 2012 12:26 pm
by tux
Now Dahdi channels are configured correctly.
Code: Select all
go*CLI> dahdi show channels
   Chan Extension  Context         Language   MOH Interpret
 pseudo            default                    default
      1            from-pstn                  default
      2            from-pstn                  default
      3            from-pstn                  default
      4            from-pstn                  default

The main problem is the dial plan because when i make a manual call :
Code: Select all
[Nov 27 12:21:41] NOTICE[27493]: chan_sip.c:15566 handle_request_invite: Call from '100' to extension '9067977163' rejected because extension not found.

like im trying to call a local extension.

Re: Problem in Dahdi trunk

PostPosted: Tue Nov 27, 2012 12:36 pm
by williamconley
extension not found ... show your dialplan.

Re: Problem in Dahdi trunk

PostPosted: Tue Nov 27, 2012 1:36 pm
by tux
Dialplan Entry in carriers. Protocol ZAP
Code: Select all
exten => _9XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _9XXXXXXXXXX,2,Dial(${TRUNK}/${EXTEN:1},,To)
exten => _9XXXXXXXXXX,3,Hangup

Re: Problem in Dahdi trunk

PostPosted: Tue Nov 27, 2012 1:59 pm
by williamconley
No match
9067977163
9XXXXXXXXXX

Re: Problem in Dahdi trunk

PostPosted: Wed Nov 28, 2012 5:45 am
by tux
I tried all dialplan possibilities even exten => _9X.,2,Dial(${TRUNK}/${EXTEN:1},,To)
Really Don't know what the problem is.

Re: Problem in Dahdi trunk

PostPosted: Wed Nov 28, 2012 5:54 am
by DomeDan
Post the output from CLI when using that dialplan

Re: Problem in Dahdi trunk

PostPosted: Wed Nov 28, 2012 6:23 am
by tux
can't post all logs , they said my post look too spammy !
Code: Select all
Exec 8600052 @default:1 MeetMe   in new stack
 Starting Local  ****** 90674977162,1 failed so falling back to exten 's'
 Starting  at default,s,1 still failed so falling back to context 'default'
Sent into invalid extension 's' in context 'default' on Local  8600052 A-T default 562f 1
Executing h@default   DeadAGI NODEBUG in new stack

Re: Problem in Dahdi trunk

PostPosted: Wed Nov 28, 2012 7:14 am
by striker
try the below
[globals]
CONSOLE=Console/dsp ; Console interface for demo
TRUNKXYZ=DAHDI/G0 ; Trunk interface
TRUNKX=Zap/r2


[default]

exten => _9X.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _9X.,2,Dial(${TRUNKYZ}/${EXTEN:1},,TtoR)
exten => _9X.,3,Hangup

Note :

after entering the above in extension.conf
go to asterisk cli and type > reload

you need to dial any number with 9 as prefix foreg:to dia 9876543210 you need to dial as 99876543210

Re: Problem in Dahdi trunk

PostPosted: Wed Nov 28, 2012 7:29 am
by tux
Thanks striker for the support.
Here i get a different/new CLI output
Dialing 0674977163 > 90674977163

Code: Select all
  -- Executing [90674977163@default:1] AGI("SIP/100-00000004", "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 [90674977163@default:2] Dial("SIP/100-00000004", "/0674977163||TtoR") in new stack
[Nov 28 07:27:02] WARNING[7914]: channel.c:3765 ast_request: No channel type registered for ''
[Nov 28 07:27:02] WARNING[7914]: app_dial.c:1310 dial_exec_full: Unable to create channel of type '' (cause 66 - Channel not implemented)
  == Everyone is busy/congested at this time (1:0/0/1)
    -- Executing [90674977163@default:3] Hangup("SIP/100-00000004", "") in new stack
  == Spawn extension (default, 90674977163, 3) exited non-zero on 'SIP/100-00000004'
    -- Executing [h@default:1] DeadAGI("SIP/100-00000004", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----66-----CHANUNAVAIL----------") in new stack

Re: Problem in Dahdi trunk

PostPosted: Wed Nov 28, 2012 7:40 am
by tux
When i start calls from agentweb client i get :
Code: Select all
Warning 13914 app_meetme dot c 2463 conf run  Unable to write frame to channel Local 8600051 default

and
DIAL ALERT:
Call Rejected: CHANUNAVAIL
Cause: 66 - Channel type not implemented.
Close Message

Re: Problem in Dahdi trunk

PostPosted: Wed Nov 28, 2012 8:26 am
by striker
post your extension.conf

use pastebin.com to upload a large file data

or
go to asterisk cli and type

>dialplan show 90674977163@default

Re: Problem in Dahdi trunk

PostPosted: Wed Nov 28, 2012 8:49 am
by tux
Sorry i can't post URL for now "still new user"
pastebin / 93duAemK

Code: Select all
go*CLI> dialplan show 90674977163@default
[ Context 'default' created by 'pbx_config' ]
  '_9X.' =>         1. AGI(agi://127.0.0.1:4577/call_log)         [pbx_config]
                    2. Dial(${TRUNKYZ}/${EXTEN:1}||TtoR)          [pbx_config]
                    3. Hangup()                                   [pbx_config]

Re: Problem in Dahdi trunk

PostPosted: Wed Nov 28, 2012 8:54 am
by tux
My extensions.conf :
pastebin;com/93duAemK

Re: Problem in Dahdi trunk

PostPosted: Wed Nov 28, 2012 9:01 am
by tux
oops i get it :)
Code: Select all
[Nov 28 08:59:31]     -- Executing [90674977163@default:1] AGI("SIP/100-00000002", "agi://127.0.0.1:4577/call_log") in new stack
[Nov 28 08:59:31]     -- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
[Nov 28 08:59:31]     -- Executing [90674977163@default:2] Dial("SIP/100-00000002", "DAHDI/g0/0674977163||To") in new stack
[Nov 28 08:59:31]     -- Called g0/0674977163
[Nov 28 08:59:34]     -- DAHDI/1-1 answered SIP/100-00000002

Thanks everyone especially striker.

Re: Problem in Dahdi trunk

PostPosted: Wed Nov 28, 2012 9:08 am
by tux
Current extensions.conf :
Code: Select all
[globals]
CONSOLE=Console/dsp                             ; Console interface for demo
TRUNXYZ=DAHDI/G0                                    ; Trunk interface
TRUNKX=DAHDI/g0                                 ; 2nd trunk interface

___________....
Code: Select all
; This 'o' Dial flag is VERY important for VICIDIAL on outbound calls
exten => _9X.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _9X.,2,Dial(${TRUNKX}/${EXTEN:1},,To)
exten => _9X.,3,Hangup

In admin panel > carriers /- Protocol ZAP :
Globals String:
Code: Select all
TRUNKX=DAHDI/g0
Dialplan Entry : exten => _9X.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _9X.,2,Dial(${TRUNKX}/${EXTEN:1},,To)
exten => _9X.,3,Hangup

I didn't edit the extensions.conf manually .That was the problem .
Have a great day Everyone
Best regards.