vicidial.org

Hi,

I manage many callcenters in Brazil. All them are using ViciDial for, at least, 6 years. I've using Digium, FoneBridge and SIP trunk on ViciDial projects. On last two years, I've changed all hardware platform to Khomp devices (http://www.khomp.com.br/v2/eng/). Including all callcenters running ViciDial. My problems is: ViciDial is not compatible with khomp channel. So, an IAX trunk do the magic with an external server running pure Asterisk + Khomp hardware.

So, I was in contact with Khomp CTO and they are interest in fund the work to add support of Khomp Channel into ViciDial and donate some hardware for homologation by ViciDial Dev Team.

This company is on telephony business for 20 years. All its products are designed for callcenters application. All major callcenter in Brazil use Khomp + CTI application (non-Asterisk). Since 2005, Khomp developed an Asterisk Channel that allows use Khomp + Asterisk, but, as best as I know, none of this big callcenters are using Khomp+Asterisk, and of course none of them use ViciDial. Except, one under my belt that is running ViciDial + Asterisk bridged by IAX2 to server with Asterisk + Khomp.

All documentation about khomp channels is already in English/Portuguese.

So, Is there interest on this project? Can I have a quotation?

Just have them send a request to sales@vicidial.com with some more information.

I'm certainly not opposed to it, but we have seen with some other component makers that they cause some problems within Asterisk when they create their own set of new drivers and channels, and there can be issues with what versions of Asteirsk they choose to support as well.

Hello,

I´m interested in Khomp support too. So far my machines are working using a IAX2 loopback, but that´s not supposed to happen. Is this moving forward?

Regards,

I recommend you call Khomp and ask them. If they funded it, they'd probably know.

I know thats an option too. I preferred to use the forums for a much friendlier approach since Matt directly comes here and he above all knows about Vicidial development.

true. if matt developed it, he'd know.

but if this is an asterisk integration, matt may never know. khomp would know ... their client would know, but matt may never be informed.

Vicidial will utilize any channel that asterisk will support AFAIK. Although Khomp may be an exception to that rule, I've never heard of another exception so I'm skeptical.

And don't forget: Vicibox 7.0.1 now includes asterisk 11. If khomp works with asterisk 11, this conversation may have died because it's no longer needed.

William,

Khomp supports Asterisk 1.8 and 11. That´s not the issue: we can make calls in and out without any problem.

The problem comes when Vicidial starts to listen to the channel status. For example: inside the FAST_AGI script which is always running I found regular expressions for SIP, IAX, Local and DAHDI, but since Khomp uses a different channel name, Vicidial can not acknowledge the call status and weird things begin to happen. For example:

- Established calls are marked as "hung up" by Vicidial, even though the agent is still talking to the client.
- You do not have access to call control, as in transfer, park or anything like that
- If you click in "Hungup call", Vicidial *thinks* the call was dropped, but the call goes on

That´s why what we had to do was to create an IAX2 loopback which dials into Asterisk and then dials to the outside using Khomp. That way, Vicidial thinks its dealing with IAX2, and everything works fine.

My best guess is that Khomp never reached the Vicidial group. I´ll try to get in touch with Khomp to see if they are interested in funding this support. As TieFighter commented, it is widely used in Brazil (I´m in Mexico), but no open source dialers use it due to the support on the dialing controls.

I stand (or sit, actually) corrected. Thanks for the clarification.

If you have the real channel type, a rewrite of the agi script to include that as an option would not seem very involved.

In fact, I would suggest an array of possible channel types be invoked at the top of the script so new channel types can be added later.

Probably a couple hours of production per script. And a bit extra to provide a diff to the Issue Tracker for inclusion in future versions ...

We have several callcenters using KHOMP, Asterisk 11 and ViciDial. But, so far, only using IAX2 loopback or separate Asterisk box as outbound/inbound gateway.

williamconley suggested very interesting solution. A custom channel name could support Khomp like technology on Asterisk.

If this need funding and/or support, I could help.

lmoreira wrote:...

williamconley suggested very interesting solution. A custom channel name could support Khomp like technology on Asterisk.

If this need funding and/or support, I could help.

Actually, the methodology for this would be to sponsor the customization by hiring The Vicidial Group or a 3rd party development team (such as PoundTeam where I work) to perform the service.

Otherwise, the likelihood of someone "just doing it" remains ultra-low. If someone else hires this project's completion, you may never find out.