Channel different from DAHDI/ZAP/SIP

Discussions about development of VICIDIAL and astGUIclient

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

Channel different from DAHDI/ZAP/SIP

Postby TieFighter » Thu Jan 15, 2015 9:52 am

Hi Dears,

I'm implementing ViciBox 6.0.3, VERSION: 2.10-469a BUILD: 150114-2249. For this project, I need to use a different hardware. It's Khomp E1 trunk which works with very proprietary channcel_drive.

Channel name on dial is: Khomp/B0C0-0.0
On agent screen I get the call correct, but I cannot put it on hold, or transfer, etc. So, I have no control over the call, beside hangup.

All outgoing calls are placed like this:
[Jan 15 11:32:45] VERBOSE[7187] pbx.c: [Jan 15 11:32:45] -- Executing [997321313@default:1] AGI("Local/8600052@default-00000001;1", "agi://127.0.0.1:4577/call_log") in new stack
[Jan 15 11:32:45] VERBOSE[7187] res_agi.c: [Jan 15 11:32:45] -- AGI Script Executing Application: (EXEC) Options: (Set(_CAMPCUST=HONDA))
[Jan 15 11:32:45] VERBOSE[7187] res_agi.c: [Jan 15 11:32:45] -- <Local/8600052@default-00000001;1>AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
[Jan 15 11:32:45] VERBOSE[7187] pbx.c: [Jan 15 11:32:45] -- Executing [997321313@default:2] Dial("Local/8600052@default-00000001;1", "Khomp/g1/97321313,,To") in new stack
[Jan 15 11:32:45] VERBOSE[7187] app_dial.c: [Jan 15 11:32:45] -- Called Khomp/g1/97321313
[Jan 15 11:32:47] VERBOSE[7187] app_dial.c: [Jan 15 11:32:47] -- Khomp/B0C0-0.0 is making progress passing it to Local/8600052@default-00000001;1
[Jan 15 11:32:47] VERBOSE[7187] app_dial.c: [Jan 15 11:32:47] -- Khomp/B0C0-0.0 is ringing
[Jan 15 11:32:58] VERBOSE[7187] app_dial.c: [Jan 15 11:32:58] -- Khomp/B0C0-0.0 answered Local/8600052@default-00000001;1
[Jan 15 11:36:27] VERBOSE[7187] pbx.c: [Jan 15 11:36:27] -- Executing [h@default:1] AGI("Local/8600052@default-00000001;1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16-----ANSWER-----222-----209") in new stack

How can I add support for this channel type on VD?
____
ViciBox v.7.0.1-160223 | VERSION: 2.12-561a BUILD: 160708-0745 | Asterisk 11.21.0 | Cluster: 8 E1s/80 Extensions DualCore@2.41GHz 8RAM (Asterisk 11) | 1 DB: QuadCore@2.40GHz 32RAM | 2 WEB: QuadCore@3.10GHz 8RAM | 8 Tel: QuadCore@3.10GHz 8RAM
TieFighter
 
Posts: 15
Joined: Tue May 20, 2014 6:08 pm

Re: Channel different from DAHDI/ZAP/SIP

Postby mflorell » Thu Jan 15, 2015 10:53 am

Never heard of Khomp before. If you want to use it with Vicidial you basically need to find all of the places that "Zap" or "DAHDI" exists in the code and add "Khomp" in there too. I know there are dozens of places in dozens of scripts that are affected, but it should be possible to do.
mflorell
Site Admin
 
Posts: 18379
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Re: Channel different from DAHDI/ZAP/SIP

Postby TieFighter » Thu Jan 15, 2015 2:38 pm

I changed things on:
/srv/www/htdocs/agc
/srv/www/htdocs/vicidial
/var/lib/asterisk/agi-bin/

Same behavior, no channel control at all. Can you point out whereelse should I look for Vicidial scripts?
____
ViciBox v.7.0.1-160223 | VERSION: 2.12-561a BUILD: 160708-0745 | Asterisk 11.21.0 | Cluster: 8 E1s/80 Extensions DualCore@2.41GHz 8RAM (Asterisk 11) | 1 DB: QuadCore@2.40GHz 32RAM | 2 WEB: QuadCore@3.10GHz 8RAM | 8 Tel: QuadCore@3.10GHz 8RAM
TieFighter
 
Posts: 15
Joined: Tue May 20, 2014 6:08 pm

Re: Channel different from DAHDI/ZAP/SIP

Postby mflorell » Thu Jan 15, 2015 2:40 pm

/usr/share/astguiclient/

You should also reboot your machine after making all of your changes.

There will also be some values in the database(like the phones table) that will probably need to be changed.
mflorell
Site Admin
 
Posts: 18379
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Re: Channel different from DAHDI/ZAP/SIP

Postby TieFighter » Thu Jan 15, 2015 4:32 pm

No sucess. I changed all codes, but no channel control at all. So, tried a new approach, but still not working. Please, give me your opinion about it:

I created two IAX trunk (iaxlocal1 ==> iaxlocal2). Vicidial dials over iaxlocal1 and iaxlocal2 receives the call on it onw context. On that context, the call is made on Khomp channel. It's working (I mean, the call is placed), but I still see on agent screen "Channel: Khomp/B0C0-0.0", when I was expecting "Channel: IAX2/iaxlocal1-6957". As I still seeing Khomp as customer channel, no control at all over the call.

I'm about to install a second server (pure asterisk), just to deal with Khomp driver and then make a IAX2 trunk to it, so Vicidial will dial with IAX Channels and the second server will make the khomp channel calls. It's not perfect, but should work by now.

Any input on this approach?
____
ViciBox v.7.0.1-160223 | VERSION: 2.12-561a BUILD: 160708-0745 | Asterisk 11.21.0 | Cluster: 8 E1s/80 Extensions DualCore@2.41GHz 8RAM (Asterisk 11) | 1 DB: QuadCore@2.40GHz 32RAM | 2 WEB: QuadCore@3.10GHz 8RAM | 8 Tel: QuadCore@3.10GHz 8RAM
TieFighter
 
Posts: 15
Joined: Tue May 20, 2014 6:08 pm

Re: Channel different from DAHDI/ZAP/SIP

Postby mflorell » Mon Sep 21, 2015 12:36 pm

Sounds like a good plan.

I'm not familiar at all with Khomp hardware or what their driver installation does to Asterisk to get it to run, so I really am not going to be much help with getting it to work natively.


Last bumped by TieFighter on Mon Sep 21, 2015 12:36 pm.
mflorell
Site Admin
 
Posts: 18379
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida


Return to Development

Who is online

Users browsing this forum: No registered users and 46 guests

cron