> > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of Joly, > > Robert AVAYA (CAR:9D30) > > Sent: Tuesday, February 02, 2010 10:16 AM > > To: sipX-dev > > Subject: [sipX-dev] Interactions between > 'sipx-noroute=Voicemail' and > > serialfork time-outs > > > > Folks, > > I just noticed an interaction between the > 'sipx-noroute=Voicemail' URL > > parameter and the time-out values the proxy ends up using > when doing > > serial forks. Here is a scenario. > > > > User 200 has a call forwarding rule that sends calls to > user 300 if no > > response within 10 seconds. > > > > I use the sipXcallContoller to make a call to user 200 and > I instruct > > it not to forward the call to voicemail. The resulting > INVITE issued > > by the sipXcallController will generally look like this: INVITE > > sip:2...@domain;sipx-noroute=Voicemail > > > > My expectation is that the call will be presented to user > 200 for 10 > > seconds and if it does not get answered, the call will > finally go to > > 300 and ring for 30 seconds. > > > > What I'm finding however differs from what I expected. > > Basically, user 200 rings for 20 seconds (instead of the > expected 10) > > and if it does not get answered, the call will finally go > to 300 and > > ring for 30 seconds. > > > > So, to summarize, whenever a user gets invited with an INVITE that > > contains a 'sipx-noroute=Voicemail' clause, the serial fork delay > > expressed in his call forwarding rules will be disregarded and the > > default 20 second value will get used. > > > > I'm not sure I understand the rationale behind not using the user's > > custom serial fork time-out when 'sipx-noroute=Voicemail' > is present. > > I would personally see no issues with always enforcing the custom > > serial fork time-out but maybe I'm overlooking something. Anybody > > have an opinion on this? > > > > Thanks, > > bob > > > > As far as I remember the check for "sipx-noroute=Voicemail" > in SipRedirectorRegDB.cpp was added to protect against > forwarding Hunt Group calls prematurely. In a Hunt Group the > users have expiration timers defined that are applied instead > of the regular call forward timers.
Thanks for the info. I'll check that. _______________________________________________ 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/
