| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
Thanks both for suggestions, i will try those :)Now i am asking for ideas on what to look for to solve a little register problem.I have this simple app that registers to an asterisk; it is configured to process DUM events every 100ms with a timeout of 100ms.Whenever a reply to a REGISTER is sent back from asterisk it takes around 300ms to my app to reply with an authenticated REGISTER with the correct response for digest authentication, so far so good.If i leave the application open (no screensaver, no standby, etc.) after 3 re-registration in 15 minutes (asterisk responds to REGISTER with an expire of 300s) i am not able to register anymore.The reason is that after 15min when a REGISTER is sent, my app responds to the 401 from asterisk after 10secs!Asterisk, on its side, destroys the dialog for the REGISTER request after 6400ms hence i am not able to register anymore.Do you have any ideas on what might be going on?i am testing this with resiprocate 1.10.2 on mac os x yosemite.thanks a lot.On Wed, Nov 30, 2016 at 6:23 PM, Scott Godin <sgodin@xxxxxxxxxxxxxxx> wrote:You can start your own timer and use ClientRegistration::requestRefresh() instead. ScottOn Wed, Nov 30, 2016 at 11:10 AM, Francesco Lamonica <alienpenguin@xxxxxxxxx> wrote:______________________________Hello there,is there a way to set the time when the dum will send a re-register?it seems that the default for dum is to send 15sec before registration ends.is it possible to send it before?thanks_________________
resiprocate-users mailing list
resiprocate-users@resiprocate.org
List Archive: http://list.resiprocate.org/archive/resiprocate-users/