Obi200 + Google Voice: outgoing caller ID incorrect
SteveInWA:
Quote from: A_Friend on September 04, 2018, 09:57:51 pm
Quote from: paulbart1234 on September 04, 2018, 08:09:43 pm
Will this break "911" calling (which is on SP2/Anveo)?
Nope. You're good to go. The 911 route is defined in your OutboundCallRoute to use SP2/Anveo no matter how your PrimaryLine is set.
There is still one oddity I'm curious about. You say when you call that caller ID number, you get a non-working number? Is your Anveo service outbound only, or did you order a telephone number from them (a.k.a. "DID")?
If no DID, you might want to ask Anveo if they can set your outbound caller ID on that trunk to your incoming number. I think Emergency Services may need to be able to call you back.
For the love of God, stop making up answers. You have no idea what you are talking about.
Given that you keep describing how to manage the device via the local interface, you apparently have no understanding of how the OBiTALK portal works. There is no reason whatsoever to manually modify the outbound call route, because the portal does that automatically, when the user simply check-marks the box to use a selected SPx for emergency calling.
Furthermore, you have no understanding of how Anveo (and Callcentric) work with their E911 service provider, to configure emergency calling. There is no option to have Anveo set your inbound number as the caller ID. The service uses a specially-assigned telephone number, which will display on the PSAP operator's screen. This will not be the same as any DID on that service provider. This is specifically done so that, should the user call via a SIP registration that does not have an associated DID, a valid DID will be sent to the PSAP. The operator can then call the person back on that number, if the call gets disconnected. Anveo (or Callcentric) know which customer has been assigned that special phone number, and thus, can route the call back to that customer. The OP described this behavior: a strange/different caller ID is being sent on calls made via the Anveo SPx, because that is how the E911 system works.
The way to validate and test that E911 calling is properly set up is to call the test number, 933. After a short delay, the system will read back the street address that was set up for this account, confirming that the service is active and properly working. During this check, the system will read back the randomly-assigned phone number. There is no action required by the user, once this is set up.
dboling:
E911 explanation via Callcentric support ticket system.
For each client with 911, we have a separate hidden DID / phone number that is associated with their account as not all customers purchase DIDs from us. This number is shown on the 911 dispatchers screen and is used in case they have to call you back. Please note that the number is only active for a period of time after calling 911.
It is not possible to modify the caller ID that is shown on the 911 dispatchers end.
SteveInWA:
Quote from: dboling on September 12, 2018, 07:13:50 pm
E911 explanation via Callcentric support ticket system.
For each client with 911, we have a separate hidden DID / phone number that is associated with their account as not all customers purchase DIDs from us. This number is shown on the 911 dispatchers screen and is used in case they have to call you back. Please note that the number is only active for a period of time after calling 911.
It is not possible to modify the caller ID that is shown on the 911 dispatchers end.
Exactly.
Navigation
[0] Message Index
[*] Previous page