Call OBi button (WebRTC)

<< < (2/3) > >>

QBZappy:
carl,

If you press the allow it should ring the phone (?). There is a way to automate this in the privacy advanced settings.

Ostracus:
Huh. I was wondering what was going on. Maybe anything lessor than an 202 (or derivative) doesn't have the space or horsepower?

QBZappy:
Quote from: Ostracus on June 11, 2013, 11:16:19 pm

Huh. I was wondering what was going on. Maybe anything lessor than an 202 (or derivative) doesn't have the space or horsepower?


This is the new OBiAPP. It's an OBi to OBI call. If you could call it before using the OBiAPP then the receiving unit specs are sufficient. The browser becomes a sip client.

I wonder what the CID is on this call. Do the inbound call routing rules apply to these calls? I tried it on another computer using once again the Chrome beta version. It hangs on "Calling 500111222". No info on the OBi202 status or call history suggesting the call was received.

dircom:
Just tried calling From chrome to my obi 100 in another state.  Rang twice, then call ended
Person on the other end heard it ring twice also

giqcass:
I tried it from a Mac on Chrome.  It rings but when I try to answer it I just get a dial tone.  Here is my call history with my Obi numbers anonymized.

Quote

From 'Jim' PP1(000000000; GW=000000000)
Fork to:PH1 PH2
Ringing (PH1) Ringing (PH2)
Call Ended   

By the way here is a link.  
http://www.obitalk.com/obinet/services/webrtc/webphone2/callobi.php

I don't know if the link is going to be useful.  You need to know the variable names to use it.


The code must be embedded from the looks of it.

Navigation

[0] Message Index

[#] Next page

[*] Previous page