Passing CID from Google Voice to CallCentric
Stewart:
Quote from: RJDB on January 04, 2012, 09:33:16 pm
Is there a way I can pass the inbound SP1 CID to the outbound SP2 - so the distant CC end shows the CID of the initiating phone (the inbound SP1 CID)??
This can be a really tough problem, not because of what you have already seen, but because the low-cost routes to foreign mobiles generally won't pass caller ID. Some solutions don't involve the OBi.
Get a DID from Anveo and forward to your destination. Quality and reliability are excellent, caller ID gets correctly delivered, but this is a fairly expensive solution.
Next step down, try Localphone. Unfortunately, a US caller ID gets sent as 10 digits (without the initial 1), so e.g. a call from 415 area code may be interpreted and parsed by your phone as coming from Switzerland and will likely not match the entry in your contact list. However, if you visually recognize the number, you'll know who is calling.
Through the OBi, if the call comes to a provider that supports call transfer via REFER, and you send it back out via the same provider, the call will be transferred rather than bridged, so the caller ID will be correct (if provider's upstream carrier passes it correctly).
What you were originally trying to do will work with Voxbeam. They give you $1 credit at signup, so you can test without making a payment. Unfortunately, OBi won't spoof on a VGx, so you would have to "burn" SP2 for Voxbeam. You'd then have to move Callcentric to a VGx, perhaps using SIP URI to get incoming calls. Of course, you'll need to use Premium route to ensure caller ID delivery.
Flowroute is likely a better solution than Voxbeam, because you won't have to hassle with IP authentication. They also give you a small test credit when you sign up. I'm not a Flowroute customer, though, so can't supply the details.
CustomATA:
Quote from: RJDB on January 04, 2012, 09:33:16 pm
Is there a way I can pass the inbound SP1 CID to the outbound SP2 - so the distant CC end shows the CID of the initiating phone (the inbound SP1 CID)??
What you want is easily done. As per RonR's post, you need Service Providers -> ITSP Profile B -> SIP -> X_SpoofCallerID checked.
You also need an entry in Voice Services -> SP1 Service -> X_InboundCallRoute to bridge your inbound calls to the remote extension via callcentric's public interface, i.e. "in.callcentric.com" (not "callcentric.com"). The entry should look something like "{sp2(17775551234@in.callcentric.com)}", where you'd replace "17775551234" with the actual callcentric extension you want to ring. If you want to ring both the remote extension as well as any phone attached to the OBi, you can make the entry "{ph,sp2(17775551234@in.callcentric.com)}" instead.
Stewart:
Quote from: CustomATA on January 05, 2012, 06:14:29 pm
... You also need an entry in Voice Services -> SP1 Service -> X_InboundCallRoute to bridge your inbound calls to the remote extension via callcentric's public interface, i.e. "in.callcentric.com" (not "callcentric.com").
This is very interesting news. I had learned (the hard way) that OBi won't spoof on a VGx, but didn't know that a direct URI would bypass that limitation. I don't want to test that now; my OBi is far away and there is a risk of losing control when the device is rebooted.
I see two great uses for this feature. Can you please confirm whether either or both will work?
1. Send the call to a second CC account, using in.callcentric.com, then forward it on to your foreign mobile, via a Call Treatment.
2. Send the call directly to a foreign mobile via e.g. Voxbeam or Flowroute, with X_InboundCallRoute = {sp2(0011101xxxxxxxxxxx@sbc.voxbeam.com)}
RJDB:
Quote from: CustomATA on January 05, 2012, 06:14:29 pm
Quote from: RJDB on January 04, 2012, 09:33:16 pm
Is there a way I can pass the inbound SP1 CID to the outbound SP2 - so the distant CC end shows the CID of the initiating phone (the inbound SP1 CID)??
What you want is easily done. As per RonR's post, you need Service Providers -> ITSP Profile B -> SIP -> X_SpoofCallerID checked.
You also need an entry in Voice Services -> SP1 Service -> X_InboundCallRoute to bridge your inbound calls to the remote extension via callcentric's public interface, i.e. "in.callcentric.com" (not "callcentric.com"). The entry should look something like "{sp2(17775551234@in.callcentric.com)}", where you'd replace "17775551234" with the actual callcentric extension you want to ring. If you want to ring both the remote extension as well as any phone attached to the OBi, you can make the entry "{ph,sp2(17775551234@in.callcentric.com)}" instead.
It worked like a Champ!!! The originating CID was displayed on my cell softphone (CC account) - at the distant/receiving end.
Thanks!!!
CustomATA:
Quote from: Stewart on January 05, 2012, 07:45:50 pm
I don't want to test that now; my OBi is far away and there is a risk of losing control when the device is rebooted.
I don't have an OBi myself. "My" OBi actually belongs to a family member, for whom I manage it remotely through provisioning. Haven't had any issues at all doing it. If you manage yours via the OBiTalk portal, you may want to consider provisioning it yourself instead.
Quote
I see two great uses for this feature. Can you please confirm whether either or both will work?
1. Send the call to a second CC account, using in.callcentric.com, then forward it on to your foreign mobile, via a Call Treatment.
2. Send the call directly to a foreign mobile via e.g. Voxbeam or Flowroute, with X_InboundCallRoute = {sp2(0011101xxxxxxxxxxx@sbc.voxbeam.com)}
I only have free IP Freedom accounts with Callcentric, and no Voxbeam or Flowroute accounts, so I'm afraid you'll have to confirm it yourself, or have someone else try it for you. As Callcentric goes, I'd expect that they'd forward to the PSTN with the DID associated with the forwarding CC extension as caller id. Since in.callcentric.com accepts any arbitrary caller id, there could be potential regulatory issues in blindly passing such along to the PSTN. I have no idea what Voxbeam or Flowroute do.
Navigation
[0] Message Index
[#] Next page
[*] Previous page