[asterisk-bugs] [Asterisk 0013056]: rtptimeout and rtpholdtimeout can only be set globally for users

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=13056 
====================================================================== 
Reported By:                davidw
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   13056
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.21 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             07-10-2008 12:48 CDT
Last Modified:              07-11-2008 16:25 CDT
====================================================================== 
Summary:                    rtptimeout and rtpholdtimeout can only be set
globally for users
Description: 
rtptimeout and rtpholdtimeout can be set in the global SIP configuration,
in which case they are honoured for incoming calls matched against a user
entry.  They can also be specified for an individual device provided it is
configured as a peer or friend.  In the case of a friend, they are not
honoured when an incoming call is matched against the user part of the
configuration.

This seems inconsistent, especially as it is meaningful and useful to
apply such timeouts on calls that match as users.  In our case we want to
ensure that an AgentLogin type agent gets logged out if they lose their
connection, but we are wary of setting the timeouts globally, in case we
have a connection that does silence suppression and doesn’t use RTCP.

Note that sip.conf.sample doesn’t list these parameters as allowed for
users.  Nonetheless, I think that it would only make sense if were
allowed.

====================================================================== 

---------------------------------------------------------------------- 
 russell - 07-11-08 16:25  
---------------------------------------------------------------------- 
closing it out since this "feature" already exists in trunk 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-11-08 16:25  russell        Status                   new => resolved     
07-11-08 16:25  russell        Resolution               open => fixed       
07-11-08 16:25  russell        Assigned To               => russell         
07-11-08 16:25  russell        Note Added: 0090129                          
======================================================================