> > Hi All, > > XX-4849 provides the support for per-user forward timer > due to which User call forwarding screen provides a field > where the user can specify how long his phone should ring > before the call gets forwarded to his voicemail box OR to the > configured forwarding number. The default value being 20 seconds. > > > > > The question is where does this field get the value 20 > seconds from ? Is this a default value assigned to this field > OR is this value got from the "Default serial fork > expiration" (default value = 20 seconds) > > If the "per-user forward time" is got from the > "Default serial fork expiration", then changing the Default > serial fork expiration should change the "per-user forward > time" for users who have not configured this field , or > atleast for new users added. (This does not happen as of now) > > If the "per-user forward time" is NOT got from the > "Default serial fork expiration" then where is the Default > serial fork expiration used ? Why do we need this parameter? > It comes into picture when "huntgroup with call forwarding" , > "huntgroup with fallback destination as another huntgroup" is > used. Can someone please throw more light into this? > > If "huntgroup with callforwarding " is configured as follows: > initially call---220---expiration=30 > if no response --221--expiration=30 > enable only the 'allow callforwarding' checkbox > > Set callforwarding for user 221 as follows : > extension 221 will ring first for 5 seconds > Always, Enabled, "if no response" forward to 224 ring > for 30 seconds > > NOTE:-- here the per-user forward time for 221 is 5 > seconds and the "default serial fork expiration" is 55 seconds > > Now call the Huntgroup extension --->user 220 rings for > 30 seconds, upon no answer user 221 rings for 20 seconds and > call is forwarded to 224 which rings for 10 seconds and the > call gets disconnected. > --Here the question is why 221 rings only for 20 > seconds? Which parameter is a value of 20 referring to? Its > neither the 'per-user forward time' nor the 'default serial > fork expiration' . Please let me know if I have missed out something. > > Note: In the above scenario , if the "default serial > fork expiration" is changed to 10 or 55 , the user 221 rings > only for 20 seconds and then forwards the call to 224 > > Once the INVITE for 221 was sent to the registrar and > registrar sends a 302 moved temporarily, I could see the > following lines in the sipXproxy.log:-- > > 2009-07-10T06:51:51.802303Z:10829:SIP:DEBUG:jupiter.qantom.int > :SipClientTcp-18:B65F1B90:SipXProxy:sipXproxymain::userCfwdTim > eCallbackurl=<sip:[email protected]> > <mailto:sip:[email protected]> ;user=phone tmr=20 > > 2009-07-10T06:51:51.802318Z:10830:SIP:DEBUG:jupiter.qantom.int > :SipClientTcp-18:B65F1B90:SipXProxy:SipUserAgent::getUserSeria > lExpiresSeconds user=sip:[email protected];user=phone time=20 > > 2009-07-10T06:51:51.802362Z:10831:SIP:DEBUG:jupiter.qantom.int > :SipClientTcp-18:B65F1B90:SipXProxy:SipTransaction::recurseDns > SrvChildren transaction 0xb60db880 setting timeout 20 secs. > > > Thanks, > Chaitra > >
The 20 seconds is the default for the field, we don't yet have a way to change the default for multiple users based on a system-wide a group-wide default. The legacy "Default serial fork expiration" is used if the per-user timer lookup doesn't find the user. In your case it is using the default because the user is "phone". I'm not yet sure why changing the default timer to 55 seconds doesn't have any effect, I would expect that to behave the same as in previous releases. Dave. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
