December 17, 2017, 01:27:06 pm *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: 1 [2]
  Print  
Author Topic: Monthly or annually *autopay* E911 service to use with Obi200?  (Read 1719 times)
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3973



« Reply #20 on: November 15, 2017, 05:08:02 pm »

Thanks, I finally got it to work.

It's confusing to set up because when Obitalk asks for the "Callcentric Number," it sounds like they are asking for my Callcentric phone number rather than an extension id-- which is further compounded by the fact the 1777xxxxxxx looks like an eleven digit phone number. 

The form looks pretty self-explanatory to me.  Oh well, glad you figured it out.


* screenshot-www.obitalk.com-2017-11-15-17-06-41-993.png (50.6 KB, 831x276 - viewed 51 times.)
Logged

Rick441
Jr. Member
**
Posts: 22


« Reply #21 on: November 15, 2017, 05:36:11 pm »

Made me a little uncomfortable that I had to try three times before Google would ring my phone using the free CallCentric number (so that I could add it as a forwarding number).

 Is it normal for there to be about a 10-12 second delay after dialing 933 (to test 911) before it responds?  Also, why is it that the phone number read back to me by 933 is not my Callcentric number (though I tested it from my cell and it did ring the Obi-attached phone)?

A few more questions:

If I choose to, can I still use GV for inbound calls, while having Callcentric continue to function for E911? (I do note that the 933 test worked even when I temporarily disabled GV forwarding to the free Callcentric, suggesting the answer is "yes," but thought I would still ask).

Finally, is/could any latency be added by using the CallCentric number, forwarded to GV, for incoming calls?  I already notice a bot of latency using GV (exclusively) through the Obi200, though in practical terms it seems to have negligible impact on calls.

Thanks.
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3973



« Reply #22 on: November 15, 2017, 05:44:29 pm »

Most of those questions has already been discussed in other threads.

Don't make anything out of the attempts to add the CC number.  It has nothing to do with normal use.

Same answer to the 933 question.  I have actually had a real emergency, called 911, and they answered immediately, using CC's service.

The question about using GV vs. CC is just basic OBi configuration settings.  If you use the portal and click the box to use the CC SPx for 911 calls, that is what it will do.

There is a negligible latency added.  If it bothers you, then don't use CC for inbound calls.  It isn't necessary to do that in order for 911 service to work.

The phone number displayed to the 911 operator is different, on purpose.  It's designed that way, because the service can be used without having a real inbound telephone number from CC.  The system assigns a phone number to display to the 911 operator, so they can call you back in case the call gets disconnected.  It will automatically route to your OBi.
Logged

GPz1100
Full Member
***
Posts: 121


« Reply #23 on: November 15, 2017, 06:22:26 pm »

But if I were having these problems, wouldn't it be affecting any calls to the obi?  It's working fine with Google Voice, in and out (although maybe that does not use sip traffic?).

GV uses xmpp, callcentric is sip.  Two different protocols.

Garbage in, garbage out. Top picture is from obi port, buttom from callcentric extensions page.





Callcentric properly identifies the fields.  Obi form leaves one very confused.  Someone that deals with sip on a regular bases knows exactly what goes where. The lay person on the other hand makes certain assumptions based on the information in front of them.  

Does obi mean the callcentric account login, DID, or sip usename for the callcentric number field.  Same for password.  Way too much ambiguity. Frankly, unless you're using the obi box for gv, forget about the obitalk portal entirely and set the service up manually through the local admin console.  You'll learn much more and be less confused at the end.
« Last Edit: November 15, 2017, 06:25:15 pm by GPz1100 » Logged
Rick441
Jr. Member
**
Posts: 22


« Reply #24 on: November 15, 2017, 07:44:23 pm »

Yes, GPz1100, exactly!  Thanks for your help, including answering my original question about CallCentric billing.  And of course thanks to SteveInWa for providing so much useful information, and to everyone else who helped.

Logged
Rick441
Jr. Member
**
Posts: 22


« Reply #25 on: November 17, 2017, 04:02:41 pm »

The phone number displayed to the 911 operator is different, on purpose.  It's designed that way, because the service can be used without having a real inbound telephone number from CC.  The system assigns a phone number to display to the 911 operator, so they can call you back in case the call gets disconnected.  It will automatically route to your OBi.

My test cellphone call to the number read back to me by Callcentric 933 does indeed ring the Obi-connected phone.  While that's all that really matters (since it indicates a 911 dispatcher could call back) I'm surprised that call doesn't show on my Google Voice log (or on Callcentric's)?   Any idea why? I am currently using GV for incoming calls, and using my Callcentric "Free" NY number solely for the E911 that comes with it.
« Last Edit: November 17, 2017, 04:04:43 pm by Rick441 » Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3973



« Reply #26 on: November 17, 2017, 05:37:13 pm »

The phone number displayed to the 911 operator is different, on purpose.  It's designed that way, because the service can be used without having a real inbound telephone number from CC.  The system assigns a phone number to display to the 911 operator, so they can call you back in case the call gets disconnected.  It will automatically route to your OBi.

My test cellphone call to the number read back to me by Callcentric 933 does indeed ring the Obi-connected phone.  While that's all that really matters (since it indicates a 911 dispatcher could call back) I'm surprised that call doesn't show on my Google Voice log (or on Callcentric's)?   Any idea why? I am currently using GV for incoming calls, and using my Callcentric "Free" NY number solely for the E911 that comes with it.

When you make an outbound 911/933 call, it is using Callcentric, not Google Voice.  When you call the substitute 631 area code number, it is again coming into your Callcentric SPx, not Google Voice.  You can see the two calls in your Callcentric call logs.  The second, inbound call to CC will only show the calling number, not the number that was called, since it's not actually calling a real phone number, but a special number assigned by CC to ring the SP that was set up to make 911 calls.

Remember:  Google Voice cannot make 911 calls.  If you attempted to do so, you'd just get an error message.
Logged

Rick441
Jr. Member
**
Posts: 22


« Reply #27 on: November 17, 2017, 11:27:38 pm »

Thanks for the explanation.  BTW, while I do indeed see both calls when I look at the detailed Callcentric log, the second one, from my cell to the special 911-callback number, *does* show the full 11-digit number dialed (an 845 area code in my case).
« Last Edit: November 17, 2017, 11:47:20 pm by Rick441 » Logged
Pages: 1 [2]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC