Forward one Obihai (both inbound and outbound) to another.
RonR:
Quote from: jimates on October 31, 2011, 10:36:22 pm
I don't guess it would matter but, with both Obi's set to fork the calls to each other, wouldn't that create a loop on the Obitalk Services.
It definitely matters and would be a serious problem, but it won't occur:
Voice Services -> OBiTALK Service -> InboundCallRoute : {200123456:ph},{ph,pp(ob200123456)}
Calls from the other OBi only go to the PHONE Port and don't fork.
Jean-Charles:
I've been playing around with this idea for a bit now and I've now got 2 additional questions:
1) I can get the call forwarding correctly using essentially this method, however when OBi1 calls OBi2 over the ObiTALK network, regardless of the peer number I set, OBi2 treats the call from OBi1 as though I'm not spoofing at all. In other words, this scenario:
OBi1 has an OBiTALK # of 111 111 111
OBi2 has a # of 222 222 222
OBi1 SP1 has an inbound call route of {ph,pp(333333333>ob222222222)}
OBi2 OBiTALK has an inbound call route of {111111111:aa},{333333333:ph}
If I were to call into OBi1's SP1, OBi2's call log would show 333333333 but would go to AA (the rule for 111111111, not the rule for 333333333).
Why is that?
2) I can't seem to get the $1 variable to work. For example, if I use the following inbound call route:
{ph,pp($1>ob111111111)}, the call log on that OBi will show a call from "$1" instead of the caller's number. Why?
Thanks!
bukzin:
I guess my request for a simple answer is too tricky.
Maybe this device is beyond us non- techies.
bukzin:
OK,
Found some info which does address a few of my questions.
May be of interest to others.
http://michigantelephone.wordpress.com/2011/01/22/review-of-the-obihai-obi110-voip-device-part-1-use-your-phone-with-google-voice-for-free-incoming-and-outgoing-calls/
whee:
Quote from: Jean-Charles on November 02, 2011, 08:05:20 pm
I've been playing around with this idea for a bit now and I've now got 2 additional questions:
1) I can get the call forwarding correctly using essentially this method, however when OBi1 calls OBi2 over the ObiTALK network, regardless of the peer number I set, OBi2 treats the call from OBi1 as though I'm not spoofing at all. In other words, this scenario:
OBi1 has an OBiTALK # of 111 111 111
OBi2 has a # of 222 222 222
OBi1 SP1 has an inbound call route of {ph,pp(333333333>ob222222222)}
OBi2 OBiTALK has an inbound call route of {111111111:aa},{333333333:ph}
If I were to call into OBi1's SP1, OBi2's call log would show 333333333 but would go to AA (the rule for 111111111, not the rule for 333333333).
Why is that?
2) I can't seem to get the $1 variable to work. For example, if I use the following inbound call route:
{ph,pp($1>ob111111111)}, the call log on that OBi will show a call from "$1" instead of the caller's number. Why?
Thanks!
Did you find a solution to this problem? I'm experiencing the same thing. 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. I figured spoofing the CID would work, but I see $1 as the peer number and the OBi110 seems to act as if I hadn't spoofed the CID when it evaluates the InboundCallRoute (i.e., the AA picks up). Seems broken.
Navigation
[0] Message Index
[#] Next page
[*] Previous page