Call forward to mutiple numbers?
jimates:
I had read that and tried it, made no difference.
I thought since I am forwarding an incoming call to another Obi via Obitalk service that there should be a way to do it.
jimates:
Just FYI for those that read this thread. The Obitalk Service is suppose to be able to pass the caller id with firmware 1.3, coming "soon".
randomLettersandNumbers:
Cool!
ccchih:
Is there any settings I can do to make terminalA rings first and ring terminalB simultaneously 4 secs later?
Anyway, I took the examples obi-support2 provided and make a few test calls.
It seems that if I apply the setting of --- {ph,SP1(12345678),SP2(11112234),SP2(44445555)}
When a call is coming, all the 4 terminals are ringing which is working as expected.
Apply the 2nd setting of --- {(33931111|3399xxxx):ph,PP(ob200123456),SP2(11112234),SP2(44445555)}
I guess the purpose of this example is followings.
1. Ring PP(ob200123456),SP2(11112234),SP2(44445555) simultaneously for every single call.
2. AND also ring ph if the caller is making a call from 33931111 or 3399xxxx
But for my testing, it seems that:
1. If the caller is making a call from 33931111 or 3399xxxx, ph will ring. And ONLY ph is ringing.
2. For all the other callers, nothing happens! None of the terminals ring.
BTW, I am testing it with firmware 1.3.
RonR:
ccchih,
The OBi does appear to be broken in this area. Given an SP1 X_InboundCallRoute rule of:
{12341234567:ph,sp2(12347654321)}
If the call is from 12341234567, the PHONE Port rings and the call is forked to 12347654321 using SP2 as expected.
If the call is NOT from 12341234567, the incoming call is totally ignored.
Navigation
[0] Message Index
[#] Next page
[*] Previous page