Call any OBi for FREE Right from Your WebRTC Capable Browser !! How ?
giqcass:
Quote from: YASH on November 22, 2014, 08:34:01 am
But still, it brings that voice message of giving options of press 1 / 2 / 3 on dialpad.
I just tried couple of times,...
It still brings that dialpad pressing of options as usual,..
Try rebooting the Obi202 and see if the voice goes away.
EDIT: The easy way to reboot. From a phone connected to the Obi press *** then press 9 then press 1 to confirm.
YASH:
Quote from: giqcass on November 22, 2014, 12:29:04 pm
Quote from: YASH on November 22, 2014, 08:34:01 am
But still, it brings that voice message of giving options of press 1 / 2 / 3 on dialpad.
I just tried couple of times,...
It still brings that dialpad pressing of options as usual,..
Try rebooting the Obi202 and see if the voice goes away.
EDIT: The easy way to reboot. From a phone connected to the Obi press *** then press 9 then press 1 to confirm.
Sir,..
First of all,.. thanks for your extreme cooperation and efforts,
with lots of tolerance,........ and without losing any patience, with me. Thank you, again.
BTW,
..I did exactly, like you said,
. ( ***9,1 on both the phones ) and Still that obi voice message was coming,..
I also turned the power plug OFF of the obi device, rebooted device,. and still the OBI voice message ( of pressing 1/2/3 options ) was coming, as it is !
Finally, I found the remedy,
I went back to the "InboundCallRoute" area to check the status ph,ph2 which was also fine,..
but this time,.. I took off the tic mark from that first column of the small square box there ( last time when I removed that tic from the second column, it had jumped to the first column to bring that ph,ph2 automatically.
[ As it was not letting me, repair those typings manually ]
So, ( now no tic marks in any columns in front of "InboundCallRoute", has taken care of that annoying OBI voice messages with its options.
BUT,
The phone not ringing disorder (struggling 4-5 times
and then and then once only it rings the phone
- annoyance is as it is ! ( No matter,... I use Google chrome or Firefox )
When it rings the phone, via Google chrome, phone shows,..number as
29-040-0758
When it rings the phone, via Firefox, phone shows,..number as
00-000-0000
If I am logged ON, I don't need to enter the matching code, [ it never asks ]
If I am not logged ON, I need to enter the code.
But, regardtheless,
a) whether I use firefox or Google chrome,..
b) whether I am logged ON or OFF
c) whether I dial by
1) entering device ID number ( 500xxxyyy ) or,..
2) In speed dialing, selecting my device,.... and it brings 2* in the display area of the phone number or,
3) entering 2*1302XXXYYYY [ 302 is my area code,..XXXYYYY is one of my OBI202s phone number allotted ]
it still does not always ring,..
and many a times, I listen to the first initial two fake rings,.. and then green letters shows Ringing
and the phone never rings, even if I waited for another 10 minutes.
giqcass:
Quote from: YASH on November 22, 2014, 03:43:27 pm
entering 2*1302XXXYYYY [ 302 is my area code,..XXXYYYY is one of my OBI202s phone number allotted ]
You should NEVER be entering 2*1302XXXYYYY to call your own Obi. If someone else is trying to call your Obi they should NEVER be using 2*1302XXXYYYY either. Let me explain what happens when you do that. 2* will call your Obi via webRTC. 2*1302XXXYYYY will create an incoming call to your Obi but the call will be diverted and the Obi will attempt a second outgoing call to 1302XXXYYYY using the service that is set under the Auto Attendants PrimaryLine. That can cause a whole host of issues and unpredictable behavior. The call may go through some of the time(with a delay) other times you could end up with timeouts, voice mail, or a busy tone.
The 2 correct ways to connect to your Obi via WebRTC are 2* from your own account or using the device ID number ( 500xxxyyy ) when not logged in to your account. Any other method will cause unpredictable results with too many variable to ever hope to troubleshoot.
YASH:
Thanks for letting me know that,
also I noticed that,
Never give away your device ID
to any non-trustworthy persons, or on any unknown members in forums,
etc.
Coz, if someone starts annoying you,
you have no idea even who is calling you, as your phone display does not know,.. from where the web phone is coming and you will be really annoyed and irritated by strangers. Right ?
giqcass:
That is true. I wouldn't post my Obi device number just like I wouldn't post a phone number. To reduce the possibility of spam calls the WebRTC form makes users enter a captcha code before they make a call if they are not logged in. It's possible to block calls from people without an account if it were to ever become an issue. You could even set the Obi to only take calls from specific numbers or device ID's if you wanted to.
Navigation
[0] Message Index
[#] Next page
[*] Previous page