Send calls from OBi200 to OBi202
N7AS:
I sent azrobert a pm a day or so before posting here. I guess he has not read it or knows it's there.
N7AS:
Quote from: SteveInWA on October 23, 2018, 11:37:32 am
In that case, AZRobert will likely exchange a bunch of posts with you to get it working that way.
Just something to consider: with Google Voice's new SIP-based platform and new caller ID name feature, you'll get better audio quality and more reliable calls if you get rid of the detour through Callcentric for inbound calls, and just go pure GV. On inbound calls, GV will now send caller ID name if that phone number is in your Google Contacts, or if it's a business known to Google (e.g. the business is on Google Maps).
I'm not just using Callcentric for Free CNAM dips, but also have some DIDs with Voxbeam sent via SIP URI so I can't remove Callcentric from the equation.
azrobert:
I missed your message. When I'm signed into the forum it shows "No Messages", but when I actually look at messages, yours is there. Another forum bug? There are other options you can use.
Delete Callcentric from the OBi200 to free a slot for another GV then:
1. Route calls from CC to the OBi200 via SIP URI. You will need to setup port forwarding in your router. If you have a dynamic public IP, you should setup dynamic DNS.
2. Define CC on the OBi202 and route inbound calls to the OBi200.
You might want to consider one of these because of what I learned from the DLSReports forum. I previously posted the following:
A provider can send audio to the calling device without connecting the call. This is called Early Media. An example is a Busy signal. The call is never connected, but you hear a busy signal. Early Media gets broken when you bridge a call between 2 devices, so if you call a number that is busy with the bridging technique, you will just hear ringing.
When you call another GV number and the call is forwarded to voice mail, you will also have problems. When you bridge a call over the local network, the call will fail with a 503 error. I just tested a call over the OBiTalk network from an OBi110 and it caused my OBi200 to reboot.
(408) 269-1999 is a Busy test number. Call it directly with the OBi200 and you will hear a Busy. Call it with an OBi1xx bridged to an OBi200 and you will just hear ringing.
N7AS:
I need CC to stay on my OBi200 as I receive calls from Voxbeam DIDs. I do not intend to connect a physical phone to the OBi202.
Taoman:
Quote from: N7AS on October 23, 2018, 04:29:06 pm
I need CC to stay on my OBi200 as I receive calls from Voxbeam DIDs. I do not intend to connect a physical phone to the OBi202.
Do you receive incoming calls on your Localphone config? If not, you could easily make outbound calls via Localphone using a Voice Gateway freeing up an SP slot.
Navigation
[0] Message Index
[#] Next page
[*] Previous page