Support for notification popups on computers
MichiganTelephone:
QBZappy - I watched your video but it did not explain how it would show me traffic that's not flowing through the computer that is running Wireshark. Since the OBi devices communicate directly with the Internet, their traffic would not be available to Wireshark. The only thing Wireshark might be able to capture is traffic between the user's computer (specifically the Web browser) and the OBi device's web interface. And that's assuming you know what you're doing with that software!
QBZappy:
Hi,
I've been thinking of another possible method, but first let me correct you about wireshark (or any other flavor of network packet sniffers), they don't read web pages, they intercept packets that run over the router. Obi is facing the internet however all the packets must go through the router.
The other possible method I was thinking would be to access and parse the data directly from the Obi unit. If the devs would show us how to root the device we could read and parse the data directly. I tried one method to see if I could analyze the file structure without success. I don't really want to risk bricking my Obi. It would be simpler to get the devs to show us the best way to achieve this using this more direct method.
Is you idea to get pop-ups from the Obi only, or from Asterisk in general?
You don't think the call history offers real time info which can be used for this design?
MichiganTelephone:
Quote from: QBZappy on February 19, 2011, 01:04:27 pm
Hi,
I've been thinking of another possible method, but first let me correct you about wireshark (or any other flavor of network packet sniffers), they don't read web pages, they intercept packets that run over the router. Obi is facing the internet however all the packets must go through the router.
But that would only work if you were running Wireshark on the router. I'm going to go out on a limb here and say that I think maybe it's you that doesn't fully understand Wireshark's capabilities (or lack thereof). It would be a serious security risk if ANY user on a local network could run Wireshark and look at any and all traffic on the network. I just don't believe you can run Wireshark on a computer and look at packets that are not flowing through that computer. And you can tell me I'm wrong until your fingers are bleeding from typing it, but what you are saying doesn't make sense and therefore I don't believe it.
Quote from: QBZappy on February 19, 2011, 01:04:27 pm
The other possible method I was thinking would be to access and parse the data directly from the Obi unit. If the devs would show us how to root the device we could read and parse the data directly. I tried one method to see if I could analyze the file structure without success. I don't really want to risk bricking my Obi. It would be simpler to get the devs to show us the best way to achieve this using this more direct method.
You know what would be simpler yet? If they actually give us a way to get the notifications without having to do a bunch of tricky stuff that might break something. I don't want to root the device!
Quote from: QBZappy on February 19, 2011, 01:04:27 pm
Is you idea to get pop-ups from the Obi only, or from Asterisk in general?
Right now I'm looking for a way to get them from the OBi device. Most OBi users won't be running Asterisk, you know!
Quote from: QBZappy on February 19, 2011, 01:04:27 pm
You don't think the call history offers real time info which can be used for this design?
The Call History is no easier to access than the Call Status page, and the latter would provide much better and more useful information for this purpose. However, as I explained in an earlier message, it's really beyond my abilities to pull the data off of that, because you first need to authenticate and then somehow run the JavaScript that appears to actually fetch the data. And I know absolutely zilch about JavaScript (other than that it's a real nuisance at times).
QBZappy, may I just say, it seems to me you're kind of hijacking this thread with a lot of speculation and suggestions that aren't going to help most users, and definitely aren't helping me. Wireshark is particularly irrelevant to this topic, and I wish you'd never brought it up. I understand you're trying to be helpful, but at this point I'd really like to hear what others may have to say on the subject.
jimates:
someone mentioned an upcoming softphone, why can't it be that simple. A small program that runs in the system tray and connects to the corresponding Obi. The Obi sends the info to the app with that information.
Perhaps it could be configured with what info we want to show in the ballon. Maybe we just want name and number, but the app could actually save some or all the info that the call staus log has.
NerdUno:
Try these links using the correct IP address of your OBi and then scrape away:
http://192.168.0.109/DI_S_.xml
http://192.168.0.109/callstatus.htm
http://192.168.0.109/callhistory.htm
http://192.168.0.109/PI_FXS_1_Stats.xml
The wget syntax would look like this:
wget --http-user=admin --http-password=yourpassword -qO- http://192.168.0.109/PI_FXS_1_Stats.xml
Navigation
[0] Message Index
[#] Next page
[*] Previous page