[cisco-voip] Use an FXO port for outbound calling only - no answering of incoming calls

[Wes Sisk]

+1 for Ryan's recommendation.

It's actually a bit of trickery - it specifies how long the router 
should wait to receive callerid before processing the call.  It should 
have the same desired effect.

Regards,
Wes

On 5/4/2011 3:45 PM, Ryan Ratliff wrote:
> Try the 'ring number' command under the voice-port.
>
> http://www.cisco.com/en/US/docs/ios/12_3/vvf_c/voice_port_configuration_guide/ch2_alog.html#wpxref97673
>
> Yeah that doc looks to be old but you have to be able to control how 
> many rings before an FXO port answers.
>
> -Ryan
>
> On May 4, 2011, at 3:25 PM, Tim Reimers wrote:
>
> Yup –
> It’s a CME implementation at home, actually –
> My regular copper phone line is POTS – that is connected to the 
> red/green pair running throughout the house, with multiple phones on it.
> It’s also connected to an FXO port on a 2600 acting as a gateway –
> For now, I want CME (and the associated VOIP phones/devices) not to be 
> answering calls on that line
> *otherwise my non-technical family will not be amused that the house 
> phones ring once and never again
> I want the regular house phones to ring until someone answers or the 
> answering machine picks up.
> As it is, with no dial-peers at all on the router, the FXO port goes 
> off hook after one ring and tries it’s best to do something to process 
> that call.
> At some point down the road, I may integrate the rest of the house 
> phones on an ATA or something like that – but only after I’ve worked 
> out some kind of
> failover scenario such that if there were a power-failure (or 
> router-failure), the regular phones would get all incoming calls.
> I’d get even more ‘leave the phones alone’ kind of thing if in order 
> to ‘fix’ the phone system, my family had to go log into a router and 
> restart something while I was at work….
> ;-)
> *From:*Ryan Ratliff [mailto:rratliff at cisco.com]
> *Sent:*Wednesday, May 04, 2011 3:19 PM
> *To:*Paul
> *Cc:*Tim Reimers;cisco-voip at puck.nether.net 
> <mailto:cisco-voip at puck.nether.net>
> *Subject:*Re: [cisco-voip] Use an FXO port for outbound calling only - 
> no answering of incoming calls
> I think the idea is he has two devices on the same copper and doesn't 
> want one of them to ever ring.
> Think of it as having two phones in your house.  You want one of them 
> to only be used for outbound calls and the other to ring and be able 
> to answer inbound calls.
> Unless you can do something with the physical wiring to make the FXO 
> never see ring voltage I think you are better off sticking an FXS card 
> into the router with the FXO, connecting the same device currently 
> sharing the pair with the FXO to this FXS and directing inbound calls 
> to the FXS port.
> -Ryan
> On May 4, 2011, at 2:06 PM, Paul wrote:
> I believe so long as you keep the phone number that is associated with 
> that CO trunk, nobody should be calling it in the first place except 
> by chance. If you want to dedicate it for outbound calling and want it 
> to give a busy signal when someone calls it, just PLAR it to an 
> non-existent number within that box. A called FXO port will 
> automatically ring and give you dialtone with nothing configured as 
> it's supposed to.
> ------------------------------------------------------------------------
>
> *From:*Tim Reimers <treimers at ashevillenc.gov 
> <mailto:treimers at ashevillenc.gov>>
> *To:*cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> *Sent:*Wednesday, May 4, 2011 8:08 AM
> *Subject:*Re: [cisco-voip] Use an FXO port for outbound calling only - 
> no answering of incoming calls
>
> Hi all –
> I’d like to use an FXO port for outbound calling only –
> I don’t want the port to go offhook    _/at all/_  for any incoming 
> call/ring event-
> there is other POTS equipment on the same copper pair that should 
> answer any inbound calls.
> Currently, I have no dial-peers at all in it-  but it’s still 
> answering calls even with nothing configured on it.
> I can shutdown the ports obviously, but that’s rather 
> counterproductive to using them for outbound calling  ;-)
> thanks, Tim
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> This body part will be downloaded on demand.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110504/91c188e9/attachment.html>