InboundCallRoute timer for call forward?

(1/3) > >>

totalimpact:
Can I use timers in InboundCallRoute to ring the phone for a few seconds, then re-route the call to a number at SP1?

OBi-Guru:
Don't use InboundCallRoute.

On the Physical-Interface->LinePort:

CallForwardOnNoAnswerEnable = yes
CallForwardOnNoAnswerNumber = **1-your-number
CallForwardOnNoAnswerRingCount = 4 (adjust as you like)

submit and reboot the device

QBZappy:
If we don not use the line port, can we still do this with the phone connect to the phone port?

I did not realize the line port seems to have more powerful call handling features than the phone port.

obiliving:
QBZappy,

Call Forward and other calling features, such as DND, etc., are available on all trunks in the OBi device (OBiTALK, SP1, SP2, and LINE). They can be configured under the respective service's web page. OBiTALK, SP1/2, and LINE are trunks that provide voice services, while the PHONE Port and AA are consumers of these services. For the OBi devices, features such as call forward and DND are applied to incoming calls on a per trunk basis, so that they would provide the expected behavior regardless where the incoming calls are routed to (could be AA, PH, or other trunks). If SP1 or SP2 is hard-wired to ring the PH and the PH only, then you can say these call features are similar to those offered in some other ATA implementations. OBi's design is more general. Hope this is what you're looking for.

totalimpact:
I think there is something wrong - if the call comes in on PSTN Line and is never answered, how can it use the **1 OutboundCallRoute which is assigned on the Phone port - if the phone does not have the call?

Or is that how you guys have made it - so that ports can use the dialplan of another port?

It would make more sense that I need to make a new digitmap in a Trunk Group for **1... - no?

I tried both and could not get the call to forward.

Navigation

[0] Message Index

[#] Next page