| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index |
Hi Scott and all,yes i have read that page as well.I was stubbornly trying to get a grip on inviteSessionHandle as soon as i sent the Invite message, however i realized that i can store the appdialogset when i send the message and i can save the invitesessionhandle as soon as i enter the onNewSession() methods.thanks for the help and suggestions :)On Tue, Dec 6, 2016 at 1:48 AM, <slgodin@xxxxxxxxx> wrote:Have you seen the following wiki page:. http://www.resiprocate.org/DUM_Associating_Applicatio n_Data_with_DialogSets_and_ Dialogs Scott
Sent from my iPhoneThanks Scott,yes i am studying basicCall and i will try it against my Asterisk server,however what i don't get (and i did not find in the basicCall code) is this: in all the callbacks i.e. onNewSession() one parameter is the inviteSession from which i can retrieve the appdialogset (that is the testappdialogset derived class in basicCall where you store the appdata).But when i do send an invite i pass an appdialogset pointer and i get a message as return value. How do i get a correlation between invitesession and appdialogset? when is the invitesession created?thanks again and sorry if my questions are a bit dumb...On Mon, Dec 5, 2016 at 7:58 PM, <slgodin@xxxxxxxxx> wrote:I highly recommend you take a close look at the dum/test/basicCall example if you haven't already done so. It should help with your other question as well.Try registering with your Asterisk from it and see if you get the same results.Scott
Sent from my iPhoneHello Scottthanks for your reply.I am running the DUM and stack on their own InterruptableStackThread as in the examples (or at least i do hope i have done it right). In that thread i do have a timer that executes "while (dum->process(100);)"Do you have any other ideas?thanks againOn Thu, Dec 1, 2016 at 3:51 PM, Scott Godin <sgodin@xxxxxxxxxxxxxxx> wrote:It sounds to me like your processing loop is bad. You need to be constantly giving DUM and the stack process cycles. It's not good to only process DUM events every 100ms. Please see this page:ScottOn Thu, Dec 1, 2016 at 8:47 AM, Francesco Lamonica <alienpenguin@xxxxxxxxx> wrote: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/