Topic: zap to dahdi issue..

[gippsweb]

I've just upgraded to 1.4.25.1 asterisk with dahdi and sail 2.3.1-20.

It appears most of it is working fine except for a ring group which appears to be looking for a zap channel still, instead of the new dahdi one.. This stops that line from ringing with the rest of the group.

I have deleted and recreated the group.
I can ring the extension from other ext's and call out from it.

CLI looks like this >>

 -- Starting simple switch on 'DAHDI/4-1'
    -- Executing [s@mainmenu:1] GotoIf("DAHDI/4-1", "1?DAHDI4-1|1") in new stack
    -- Goto (mainmenu,DAHDI4-1,1)
    -- Executing [DAHDI4-1@mainmenu:1] AGI("DAHDI/4-1", "selintra|Inbound|DAHDI4-1") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
    -- AGI Script selintra completed, returning 0
    -- Executing [7000@internal-presets:1] AGI("DAHDI/4-1", "selintra|Alias|SIP/5006 SIP/5007 Zap/1|7000") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
    -- AGI Script Executing Application: (Dial) Options: (SIP/5006&SIP/5007&Zap/1||)
    -- Called 5006
    -- Called 5007
[Jul  1 16:43:23] WARNING[5332]: channel.c:3210 ast_request: No channel type registered for 'Zap'
[Jul  1 16:43:23] WARNING[5332]: app_dial.c:1272 dial_exec_full: Unable to create channel of type 'Zap' (cause 66 - Channel not implemented)

Anybody have any ideas??

[SARK devs]

Yup - its a greenie in the callgroup builder.

We'll have that fixed in two shakes of a rats tail...  or at least by the next point release.

Best

S

[gippsweb]

And here I am thinking it's something I did wrong.....

No worries will keep my eye out for any other bugs...

[SARK devs]

OK you just got promoted to chief greenie tester for today....

use your favourite line editor...  pico, nano, vi, vim, whatever.

edit a file...

/etc/e-smith/templates/etc/asterisk/extensions.conf/90-presets

At around line 103 find

Code: [Select]

if ($technology eq 'Analogue' || $technology eq 'ISDNHFC' || $technology eq 'HFC-4S-8S') {
    $dialnum = db_get_prop(\%selintra, $_, 'channel') || '';
    $technology = 'Zap';

Change the line

Code: [Select]

$technology = 'Zap';

to

Code: [Select]

$technology = 'Dahdi';
Let me know how you get on

Best

S

[gippsweb]

That cures that one.
I'm now seeing

[Jul  2 08:49:34] WARNING[11655]: chan_dahdi.c:4565 dahdi_handle_event: Didn't finish Caller-ID spill.  Cancelling.

Obviously it's similar to what use to happen when we started using zap & CID is being sent later than asterisk is looking for it...

[SARK devs]

yup...

The dahdi equivalent of zapata.conf (where you would normally put the CLID recognition stuff) is chan_dahdi.conf and you can find it in headers.  As far as I know, the fields and setup are identical to zapata.

Best

S