incoming calls on 2 Obi devices
skipro:
Can I remove the trusted configuration/value?
jimates:
Quote from: skipro on October 18, 2012, 07:56:11 pm
Can I remove the trusted configuration/value?
Now I got my head back in this particular situation.
The forking of the calls is done using the rule we added to the SP1 inbound call route.
The rule tells the Obi to fork the call to 2 places, the phone port and the other Obi.
The pp() tells it what service to use to fork the call.
The (xxxxxxxxx) is the number it is sent to.
Done
Check the Obitalk inbound call route. Set it to only ring the desired phone port, ph1 or ph2; nothing else.
The inbound call route tells the Obi what to do with the call once it gets it (from the other Obi). Since both devices are in the same account Obitalk added them to each other trusted caller list. This configuration tells the Obi to send calls from the trusted number to the AA.
The default Obitalk Service inbound call route will look somethng like this
{(290xxxxxx)>(xx.):SP1},{(290xxxxxx):aa},{ph,ph2}
remove everything except {ph,ph2} or just {ph1}, {ph2} as desired
skipro:
What are the consequences if I eliminate AA in Obitalk Inbound call route, other than maybe getting this to work? Would all AA functions cease to exist? I do not want to lose AA functions that I need/use.
It seems simpler and cleaner to use a second Obi acct for 2nd device if it would work. Tried it and it does work,, sort of. The calls to the forked number [on line 1] are being passed to Line 2 also. How can I eliminate passing the call to line 2? This only happens with this fork. As noted in my second entry in this thread, this happened when I originally forked this number in the original Obi acct.
jimates:
removing the aa from the call route will not break the whole aa. If you do want to use the aa between the two devices then the aa will have to exist at some point in the configuration. If you only want the aa usage for other callers/endpoints then we can address that after you get it working for this situation.
Get it work for this particular situation first.
What caller id shows on Obi 2 when the call is forked from Obi 1.
skipro:
On 2 Obi accts:
Obitalk Service-InboundCallRoute-default:
Both devices ring
Line 1 & 2 ring
Line 2 caller ID is caller
On 1 Obi accts:
Obitalk Service-InboundCallRoute-default:
1 Device rings
Answer -get AA
press 1
Both devices ring
Line 1 & 2 ring
Line 2 caller ID is caller.
Obitalk Service-InboundCallRoute-{ph1}:
Both devices ring
Line 1 [only] rings
I can still get AA for VM retrieval.
This setup works for my purposes.
Thanks.
Could the InboundCallRoute be modified more selectively/specifically without eliminating all but {ph} to accomplish the same thing?
Navigation
[0] Message Index
[*] Previous page