01-26-2009 11:12 PM - last edited on 03-25-2019 10:33 PM by ciscomoderator
Is this possible? The usage is like this:
Incoming PSTN line is split from the wall to go to 1) UC520 (FXO Port 0) and 2) home phone.
UC520 should not answer incoming calls on FXO port 0, but should be able make calls using FXO port 0.
Regards,
Luis
Solved! Go to Solution.
01-27-2009 01:16 PM
You can use CCA to configue inbound call routing so the FXO goes to the extension assigned to the FXS. If you need CLI, you can use "connection plar opx" under the FXO port and point to the number assigned to the FXS. The OPX keyword causes the call to connect when the FXS user answers and not before, therefore reducing the chance for FXO disconnect issues.
Marcos
01-27-2009 02:12 AM
You can't directly configure an FXO port to not answer calls, but if you create a dummy phone (x210 say) and remove all the call forwarding config from that phone, you can then configure the FXO port to connect to x210. Because x210 never answers the call, the FXO port will never go off hook. So this should give you the effect you are trying to achieve. Note that there does not have to be a physical phone associated with that record, so no additional hardware is required.
Cheers,
Dave.
01-27-2009 10:03 AM
The "ring number" command can be used to increase the number of rings before answering a call but only up to a maximum of 10 rings:
Phil
01-27-2009 01:12 PM
That would work, although I think what I might do is put the home phone on FXS port 3, if there's a way to route FXO port 0 calls directly to FXS port 3, bypassing CUE altogether.
If I assign an extension to this FXS port, and do not configure NoAnswer/Busy - UC520 would let the call ring indefintely, correct?
How would I force incoming calls on FXO 0 to FXS 3?
Regards,
Luis
01-27-2009 01:16 PM
You can use CCA to configue inbound call routing so the FXO goes to the extension assigned to the FXS. If you need CLI, you can use "connection plar opx" under the FXO port and point to the number assigned to the FXS. The OPX keyword causes the call to connect when the FXS user answers and not before, therefore reducing the chance for FXO disconnect issues.
Marcos
01-27-2009 01:51 PM
Thanks for all the help, using custom incoming call handling was the most elegant solution, as I simply didn't want any UC interaction with this line, aside from connecting the incoming to call to the specific FXS port, and allowing me to use the line for outgoing calls when available.
Regards,
Luis
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide