---
span_1 = DAHDI/g1
1,1,dial(${span_1}/${EXTEN:0})
---
I can only presume some form of precedence overrides the group configuration
in the recent asterisk installs and not for the servers set up earlier.
On 26/5/09 4:01 PM, "Kal Feher" <kalman.feher at
melbourneit.com.au> wrote:
> Ok I've solved the problem. I do not think it was as switchtype issue
after
> all as it is now working with a national2 configuration.
>
> I need to sort out some of the changes and I'll post back for
reference.
> However it appears to be some form of parsing order issue between all the
> locations that define dahdi trunk groups. What is odd is that this appears
> anecdotally to be different between 1.4.22 and 1.4.24. But I'll confirm
and
> reply.
>
>
> On 26/5/09 3:46 PM, "Kal Feher" <kalman.feher at
melbourneit.com.au> wrote:
>
>> My thoughts exactly. I've tried National2, 4ess and now ni1
>> ni1 just worked on Asterisk 1.4.22. (failover box I downgraded). So
I'm
>> swapping back to 1.4.24 to test that now.
>>
>>
>> On 26/5/09 3:34 PM, "Danny Nicholas" <danny at
debsinc.com> wrote:
>>
>>> Based on this link -
>>>
http://www.trixbox.org/forums/vendor-forums-certified/sangoma/a101dx-hangup-
>>> cause-code-90-outbound-calls
>>>
>>> I'd check my polarity settings in dahdi.conf. Maybe signaling?
>>>
>>> -----Original Message-----
>>> From: asterisk-users-bounces at lists.digium.com
>>> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of
Kal Feher
>>> Sent: Tuesday, May 26, 2009 8:22 AM
>>> To: Asterisk Users Mailing List - Non-Commercial Discussion
>>> Subject: Re: [asterisk-users] Unable to make outbound calls
>>>
>>> Sorry. I don't get many opportunities to test this system as
its live. Here
>>> are the results:
>>>
>>> -- Executing [9 at DLPN_DialPlan1:1]
Dial("SIP/19722-b650fb80", "DAHDI/1")
>>> in new stack
>>> -- Requested transfer capability: 0x00 - SPEECH
>>> -- Called 1
>>> -- Channel 0/1, span 1 got hangup, cause 90
>>> WARNING[6454]: app_dial.c:765 wait_for_answer: Unable to forward
voice or
>>> dtmf
>>> -- Hungup 'DAHDI/1-1'
>>> == Everyone is busy/congested at this time (1:0/0/1)
>>>
>>>
>>> On 20/5/09 3:52 PM, "Danny Nicholas" <danny at
debsinc.com> wrote:
>>>
>>>> This all looks ok. What happens if you try to access the DAHDI
channel
>>>> outside of Asterisk control:
>>>> In dialplan
>>>> Exten => 9,1,Dial(DAHDI/1)
>>>>
>>>> Dial 9
>>>> Get dialtone
>>>> Dial number
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: asterisk-users-bounces at lists.digium.com
>>>> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf
Of Kal Feher
>>>> Sent: Wednesday, May 20, 2009 2:55 AM
>>>> To: Asterisk Users Mailing List - Non-Commercial Discussion
>>>> Subject: Re: [asterisk-users] Unable to make outbound calls
>>>>
>>>> I attached the show channels in my first post, but removed it
to reduce
>>> the
>>>> length of replies. Here it is again along with show status.
>>>> Note that there is only 1 PRI currently attached.
>>>>
>>>> geriatrix*CLI> dahdi show status
>>>> Description Alarms IRQ
bpviol
>>>> CRC4
>>>> T2XXP (PCI) Card 0 Span 1 OK 0
0
>>> 0
>>>> T2XXP (PCI) Card 0 Span 2 RED 0
0
>>> 0
>>>>
>>>> geriatrix*CLI> dahdi show channels
>>>> Chan Extension Context Language MOH Interpret
>>>> pseudo default default
>>>> 1 DID_span_1 default
>>>> 2 DID_span_1 default
>>>> 3 DID_span_1 default
>>>> 4 DID_span_1 default
>>>> 5 DID_span_1 default
>>>> 6 DID_span_1 default
>>>> 7 DID_span_1 default
>>>> 8 DID_span_1 default
>>>> 9 DID_span_1 default
>>>> 10 DID_span_1 default
>>>> 11 DID_span_1 default
>>>> 12 DID_span_1 default
>>>> 13 DID_span_1 default
>>>> 14 DID_span_1 default
>>>> 15 DID_span_1 default
>>>> 16 DID_span_1 default
>>>> 17 DID_span_1 default
>>>> 18 DID_span_1 default
>>>> 19 DID_span_1 default
>>>> 20 DID_span_1 default
>>>> 21 DID_span_1 default
>>>> 22 DID_span_1 default
>>>> 23 DID_span_1 default
>>>> 25 DID_span_2 default
>>>> 26 DID_span_2 default
>>>> 27 DID_span_2 default
>>>> 28 DID_span_2 default
>>>> 29 DID_span_2 default
>>>> 30 DID_span_2 default
>>>> 31 DID_span_2 default
>>>> 32 DID_span_2 default
>>>> 33 DID_span_2 default
>>>> 34 DID_span_2 default
>>>> 35 DID_span_2 default
>>>> 36 DID_span_2 default
>>>> 37 DID_span_2 default
>>>> 38 DID_span_2 default
>>>> 39 DID_span_2 default
>>>> 40 DID_span_2 default
>>>> 41 DID_span_2 default
>>>> 42 DID_span_2 default
>>>> 43 DID_span_2 default
>>>> 44 DID_span_2 default
>>>> 45 DID_span_2 default
>>>> 46 DID_span_2 default
>>>> 47 DID_span_2 default
>>>>
>>>>
>>>>
>>>> On 19/5/09 6:31 PM, "Danny Nicholas" <danny at
debsinc.com> wrote:
>>>>
>>>>> Please post your CLI output from dahdi show status and
dahdi show
>>>> channels.
>>>>>
>>>>> -----Original Message-----
>>>>> From: asterisk-users-bounces at lists.digium.com
>>>>> [mailto:asterisk-users-bounces at lists.digium.com] On
Behalf Of Kal Feher
>>>>> Sent: Tuesday, May 19, 2009 11:22 AM
>>>>> To: asterisk-users at lists.digium.com
>>>>> Subject: Re: [asterisk-users] Unable to make outbound calls
>>>>>
>>>>>
>>>>>> Can you make an outbound call after your first incoming
call? That's
>>>> what
>>>>> I
>>>>> experienced with 1.4.24.
>>>>>
>>>>> No I can't. I saw similar threads while searching for a
solution, but in
>>>> my
>>>>> case outbound calls are never possible.
>>>>>
>>>>>
>>>>> Regardless, thank you for your suggestion.
>>>>>
>>>>> On 19/5/09 4:47 PM, "Kal Feher" <kalman.feher
at melbourneit.com.au> wrote:
>>>>>
>>>>>>> I've got an asterisk 1.4.24 box with dahdi
complete 2.1.0.3+2.1.0.2
>>>>>>>
>>>>>>> I've got a 2 port T2XXP card attached with on
T1 currently plugged in.
>>>>>>>
>>>>>>> Inbound calls work fine, but outbound fail with the
rather cryptic:
>>>>>>> [May 19 17:28:07] WARNING[11360]: app_dial.c:1237
dial_exec_full:
>>> Unable
>>>>> to
>>>>>>> create channel of type 'DAHDI' (cause 0 -
Unknown)
>>>>>>>
>>>>>>> There are similar threads I've found on the net
but they tend to be
>>>>> related
>>>>> to
>>>>>>> dahdi not being loaded or similar. In my case dahdi
is loaded and
>>>>> channels
>>>>>>> visible.
>>>>>>>
>>>>>>> I've rsync'd a configuration (/etc/asterisk
and /etc/dahdi) from
>>> another
>>>>>>> server that is currently working fine. But still no
luck.
>>>>>>>
>>>>>>> Any hints would be appreciated. In particular if
someone can suggest
>>>> some
>>>>>>> documentation on what _could_ cause a (cause 0 -
Unknown) then I can
>>>>>>> investigate those.
>>>>>>>
>>>>>>> Some details below:
>>>>>>> <removed in reply to keep email readable>
>>>>>
--
Kal
