Forward one Obihai (both inbound and outbound) to another.
Stewart:
Quote from: whee on December 31, 2011, 02:06:22 pm
I'd like to be able to directly call an OBi110 through OBiTALK and get the AA, but also be able to forward incoming calls on the LINE port to the other OBi110 and ring the phone.
It does seem to be broken, but there is probably a solution by using SIP, rather than OBiTALK, for one of the paths. What services do you presently have on each of the OBi devices?
RonR:
It's not broken, it's designed badly. From the v1.3.0 release notes:
- Allow Caller-id spoofing for calls bridged via OBiTALK service. But use the obi number for circle-of-trust authentication.
whee:
Quote from: Stewart on December 31, 2011, 07:14:03 pm
Quote from: whee on December 31, 2011, 02:06:22 pm
I'd like to be able to directly call an OBi110 through OBiTALK and get the AA, but also be able to forward incoming calls on the LINE port to the other OBi110 and ring the phone.
It does seem to be broken, but there is probably a solution by using SIP, rather than OBiTALK, for one of the paths. What services do you presently have on each of the OBi devices?
Each OBi has Callcentric on SP1 (different accounts) and Flowroute on SP2 (same account, only used for outbound). I don't believe Callcentric will let me spoof CID, but Flowroute does. I could probably get a similar (and free) end result with a Flowroute -> Callcentric SIP address call between the two.
It's just a cleaner model (mentally and configuration-wise :D) if the forwarding/bridging part were a separate service, like OBiTALK. Hopefully it gets ironed out.
RonR:
Quote from: whee on December 31, 2011, 02:06:22 pm
I'd like to be able to directly call an OBi110 through OBiTALK and get the AA, but also be able to forward incoming calls on the LINE port to the other OBi110 and ring the phone.
Since you have SIP configured on each OBi, these easiest solution is to route the OBiTALK Service to the Auto Attendant in the normal way and forward your LINE Port calls to the other OBi's PHONE Port via SIP:
Physical Interfaces -> LINE Port -> InboundCallRoute : vg1
Voice Services -> Gateways and Trunk Groups - Voice Gateway1
AccessNumber : SP1(hostname or ipaddress of other OBi)
You will need to forward ports 5060 - 5061 in the router serving the 'other OBi' if the first OBi is on a different LAN.
Stewart:
If the direct path suggested by RonR won't work, e.g. because of router or DNS constraints, you could set it up so an incoming call on the LINE port dials the other OBi's CC 1777 number, via the local CC account, which should ring the PHONE port on the other OBi. When you call the other OBi via OBiTALK, it would recognize your caller ID and route to the AA.
However, I assume that you want to access the AA, so you can make calls from the remote OBi's LINE port (which doesn't offer any other services that you don't already have on the local OBi). If that is your goal, you can set it up so that you can dial through directly, avoiding the AA and the need for two-stage dialing. It should even be possible to configure the digit map so that calls to certain destinations would use the remote OBi's LINE port automatically.
Navigation
[0] Message Index
[#] Next page
[*] Previous page