Forwarding Setup

<< < (2/3) > >>

pitcritter:
Thanks again Zappy.  I'm off for the next couple of days, so it's time to play.  I'll report back results.

Is there any advantage to forking to the OBI number as opposed to a VOIP provider like FPL or GV?

The way I see it, if I only setup forking on SP1 and SP2 incoming calls and not on PP1 on both devices and fork to the OBI#, that would avoid ping-ponging back and forth.

I don't use the OBI# for anything else.

QBZappy:
Actually the most direct route between the two OBis is to use a sip uri address as the forking number. It avoids any 3rd party disruptions. Any of these methods will work and give you the same result. Just pick one and see how it goes.

pitcritter:
OK, now you're just showing off!!  ;D

I have no idea how to use a "SIP uri address".  I'm not looking to be spoonfed, but how about a nudge in the right direction?

pitcritter:
I tried

{(x.9051111111|x.9052222222):aa},{ph},{PP(ob555555555)}

The call didn't get forwarded to the other Obi device

Would this work?

{(x.9051111111|x.9052222222):aa},{PP(ob555555555),ph}

QBZappy:
Sorry for the above. Here is a more detailed way to do it with explanations for what you want, directly from obihai and RonR:

Quote from: obi-support2 on March 21, 2011, 10:34:40 am

The Call forward destination number fields only allow 1 number at present.

The Inbound Call route parameters, on the other hand, would allow you to fork the call the multiple numbers, simultaneously. The limit 4.

Some examples with SP1 InboundCallRoute:

{ph,SP1(12345678),SP2(11112234),SP2(44445555)}, OR

{(33931111|3399xxxx):ph,PP(ob200123456),SP2(11112234),SP2(44445555)}


This is assuming you can support at least 2 calls per SP service. Whichever number answers first will "win" and the other calls will be canceled by the OBi automatically.

---------
Note: If you include LI(some-number) in the route, however, LI will "win" most of the time since there is no easy way to tell if the call on the analog PSTN line is answered; so the device simply assumes the call is connected once it finishes dialing out the number on the PSTN line (hence it wins).

In 1.2 (currently in beta) we offer a new feature to detect if outbound call on PSTN line is connected based on tones and signal detected on the LINE. But this may require some tweaking for your local phone company. By default that feature is not enabled.



Quote from: RonR on October 30, 2011, 06:11:37 pm

If you're wanting each OBi to simultaneously ring its own phone plus the phone connected to the other OBi, make the following changes as applicable.

For SP1 Service:

Voice Services -> SP1 Service -> X_InboundCallRoute : {ph,pp(ob200123456)}

For SP2 Service:

Voice Services -> SP2 Service -> X_InboundCallRoute : {ph,pp(ob200123456)}

For OBiTALK Service:

Voice Services -> OBiTALK Service -> InboundCallRoute : {200123456:ph},{ph,pp(ob200123456)}

For LINE Port:

Physical Interfaces -> LINE Port -> InboundCallRoute : {ph,pp(ob200123456)}

where 200123456 is the OBiTALK number of the other OBi.



As for an explanation on sip uri, you can refer to these posts:
sip uri using GTALK (note not direct as it uses GTALK)
http://www.obitalk.com/forum/index.php?topic=3573.0

General discussion on using sip uri (Direct if pointing to the ip of the OBi)
http://www.dslreports.com/forum/r26327633-Obi110-SIP-URI-s-SIP2SIP-

Navigation

[0] Message Index

[#] Next page

[*] Previous page