[cisco-voip] FXO disconnect

[Wes Sisk]

hmm, no easy way to just limit call duration especially with any  
intelligence about voice detection.

couple of creative options though:
1. if mgcp use 'mgcp timer receive-rtcp <timer>' to configure the  
MGCP gw to disconnect the call after 30 seconds of no RTCP.  IPPhones  
do not generate RTCP.

1. if h323 configure the gw to RTCP timeout in 30 seconds. again  
ipphones do not generate RTCP
http://www.cisco.com/univercd/cc/td/doc/product/software/ 
ios123/123tcr/123tvr/vrht_t2.htm#wp1644934

2 . if your paging system does not provide inband audio back to  
ipphone, configure an ACL to block UDP traffic from the GW toward the  
ipphones and return ICMP unreachable messages.  then configure the  
RTP unreachable timeout down to 30 seconds
http://www.cisco.com/univercd/cc/td/doc/product/software/ 
ios123/123tcr/123tvr/vrht_m2.htm#wp1362166

3. use an IPCCX / CRA / IVR script to initiate the call to the paging  
system and disconnect after 30 seconds

/Wes

On Feb 10, 2006, at 5:21 PM, Jim McBurnett wrote:

Has anyone seen a way to limit a call out an FXO port to X seconds?

I have a situation where I would like to disconnect an FXO call after 30
- 45 seconds.

An external paging system is getting inadvertantly activated via the 999
extension call by 7920s'

When the user puts the 7920 in his/her pocket and 999 is dialed the page
is open until someone goes into CM and finds them and goes to the
Gateway and disconnects them.

We would like to just like the activation of the page to 30 - 45 seconds
and not have to change the # or have the users lock the phone keypad...


Anyone have an idea?

Thanks,
Jim

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip