Blackhole app usage example

528 views
Skip to first unread message

Kirill Sysoev

unread,
Jul 17, 2014, 10:53:48 AM7/17/14
to 2600h...@googlegroups.com
Hi

Wanted to post it to "Asterisk AMI simulation needed", but google somehow forbids to do it.
https://groups.google.com/forum/#!searchin/2600hz-dev/AMI/2600hz-dev/KP5NU8awGPY/snHrbSgBVMMJ

So, as could be seen, blackhole app settles already several months at github.
The only thing still absent is websockets connection over SSL (KAZOO-2632)

I've ordered development of a small Pop-Up application which could be an example of the blackhole app usage.

It is done now. (It is not intended to be used in production , but as an example)

It could be found over here: https://github.com/onnet/kazoo_popup

This application:

- connects to Kazoo whapp blackhole;
- listens for incoming calls;
- queries third party server whether it knows anything about caller (caller's number);
- Pop's Up window with provided info.

It is written in Qt which promises to be crossplatform application (hopefully).

Welcome :)

Best regards,
Kirill


P.S If anyone would like to order further development, please contact application's developer directly: Alexey Lysenko lysenko...@gmail.com

Darren Schreiber

unread,
Jul 17, 2014, 11:11:49 AM7/17/14
to 2600h...@googlegroups.com
This is AMAZING Kirill, thanks for this contribution! Thank you!!!
>--
>You received this message because you are subscribed to the Google Groups
>"2600hz-dev" group.
>To unsubscribe from this group and stop receiving emails from it, send an
>email to 2600hz-dev+...@googlegroups.com.
>For more options, visit https://groups.google.com/d/optout.

Darren Schreiber

unread,
Jul 21, 2014, 11:19:13 PM7/21/14
to 2600h...@googlegroups.com, i...@onnet.info
So I got this compiled on Mac OS X. Nice job Kirill! I am inclined to make this a default app we ship/host/enhance and accept it into the community-scripts, would that be OK?

I have some questions, though. I haven't actually gotten it working yet, still getting there, BUT:

1) What is the MD5? Can't figure that out.
2) Doesn't seem to be any indication of status as to whether it's connected to the remote server or not. Can we add this? I would sponsor this work but it would be useful to know if the thing was connected.
3) Is there reconnect code in case the server is restarted / becomes unavailable / network connection changes state?

I literally haven't looked at the code yet, only compiled & such. So forgive my ignorance but hoping you know the answers to these before I go poking around :-)

Also I see it's MPL, please confirm if it's OK to accept into community-scripts of 2600hz.

Again, thanks for this awesome contribution, this will help a lot of people, which just generates more usage of the platform and makes it better! I sincerely appreciate this!!!

Kirill Sysoev

unread,
Jul 22, 2014, 7:54:56 AM7/22/14
to Darren Schreiber, 2600h...@googlegroups.com
Hi Darren

Great to know that it could also be compiled on Mac OS X.

So it is Linux, Windows and Mac OS now! :)

Here are some answers:

1)

MD5 - secret key to get authenticated at third-party server which provides you with information about CID

MD5 hash should be created from "calling_number:md5_secret" string and send as an additional parameter in get request.

Made for tests dummy-server-responder could be seen over here: https://github.com/onnet/mod_zonnet/blob/master/services/service_zonnet_cidinfo.erl

Request example: https://onnet.su:8443/api/zonnet/cidinfo?calling_number=78122404700&md5=a2c2109445b3f16ad982be191e55ee38

MD5 secret, sat by default: vhbxzj947yisfbl  (configured our server with this key back again, so that people you could run first test quicker)

2, 3) Nor indication about connection, neither reconnect mechanism exists.  Could be added though. The thing is, that till SSL would be introduced in Blackhole, it couldn't be considered as production ready app.
         The same could be said about connection and reconnection - these functions needed more to production rather than to sandbox :)
         So, despite I also thought about these functions, I decided to leave it for future as many other bells and whistles :)
     
As I wrote, if anyone would like to add needed stuff, developer could be contacted directly.
And certainly, I could manage this personally for you :)   

And Yes, it is intended to reside at community-scripts of 2600hz.
The only thing, please leave developer's email in the code in order he could be contacted directly just because I am not a QT guy at all :)

Regards,
Kirill

Darren Schreiber

unread,
Jul 22, 2014, 8:05:24 AM7/22/14
to Kirill Sysoev, 2600h...@googlegroups.com
Hi Kirill,
I would leave attribution to you and developer and probably add an About to the tray icon which lists it. Just my 2 cents, credit where credit is due.

I have reached out to the developer already. We have enough requests for this that we were ironically already working on it. You saved me a bunch of time :-) Thank you.

We’ll move forward with the developer to complete this. I really appreciate it. We will post it back here when done.

Thanks again.

- Darren

kirill.sysoev

unread,
May 29, 2015, 9:44:54 AM5/29/15
to 2600h...@googlegroups.com, i...@onnet.info, dschr...@2600hz.com
Hi Darren and Karl

There is a question regarding current state of Kazoo PopUp.

The initially proposed version of popup was based on the idea of providing information about the caller already in popping up window.
This information should be taken from third party service over it's API.

We use this feature in our own office's work and it looks very helpful.

Just as an example, in addition to CID we provide the next info in popping up window:
- company name;
- contact person name;
- agreement status and its balance;
- Additional contact info - phone number, email ..

Having such information allows us to understand who it's better to pick up the phone and talk to this customer, and we can serve customer even often without going to its CRM page which is quicker.
 
In the 2600hz's popup version third party service request was removed. It is understandable, because it was our very own API, and not something that was unified for common usage.

But we started receive CRM integration requests from our Kazoo users recently. 
And again it goes about providing some Caller's information in popping up window, and also link to customer's page at CRM system or just creating a lead if no existing customer found.

It looks like PopUp needs a kind of plug-in feature, to be able to use different CRM's APIs.

So my question is if there are any thoughts about this or is there any plans regarding popup at all?

Regards,
Kirill

вторник, 22 июля 2014 г., 15:05:24 UTC+3 пользователь Darren Schreiber написал:
Reply all
Reply to author
Forward
0 new messages