It still would be nice to see a trace as to what the proxy is seeing. Subscribing to ot picking up a call from rls instead of the proxy just doesn't seem right.
Perhaps a "service" that hooks into both of the others would be a way to keep RLS from becoming impacted and keeping cdr's and other items at the proxy. I'd like to see the Jira for the failed pickup at the proxy for sure. To design any enhancement it would be helpful to see phone behavior and generically why it fails. On 9/18/10, Martin Steinmann <[email protected]> wrote: > Jean > > I suggest you open issues for the two enhancements you mention below. They > both sound interesting. > > Do we have consensus among the experts that an expiration value of zero is > the right thing? > > Also, does the RLS server establish a subscription to all the phones in the > system automatically or only to the ones for which a user requested > monitoring? I.e. for VOP do you manually create a resource list that > includes all the phones a receptionist might want to monitor or is that > already there? > > --martin > > >> -----Original Message----- >> From: [email protected] [mailto:sipx-dev- >> [email protected]] On Behalf Of Jean-Hugues Royer >> Sent: Saturday, September 18, 2010 1:57 PM >> To: [email protected] >> Subject: [sipx-dev] sipXecs / Call Pickup (*78) >> >> Hi, >> >> The call (ringing) pickup (*78) system is failing with several phones >> and can be enhanced. >> >> When you try to pick up a call ringing on extension (using *78), >> sipXecs >> subscribes (RFC4235) to the ringing extension to find out the ringing >> call information (callid, from-tag, to-tag) to be able to send an >> INVITE/Replaces to the caller extension to replace the call. >> >> This is indeed the good way to do it but right now there is one problem >> and one possible enhancement. >> >> First the problem, the subscription has an expiration time of 1 >> (Expires: 1), several phones refuses the subscription with "423 >> Interval >> too small" because this is a too small expiration value, the good >> value >> for polling should be zero. The result is that the pickup fails with >> these phones. >> >> Second the enhancement, sipXecs should first try to look int all its >> RLS, because it is very likely that this ringing call information is >> already there and it would spare a subscription and thus would likely >> succeed faster and with more phones. >> >> Regards. >> >> _______________________________________________ >> sipx-dev mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > -- Sent from my mobile device ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
