|Subject:||RE: Late fork pending context not interested in new register|
|Date:||Tue, 7 Apr 2020 06:57:35 +0000|
Ah… I see - this is very advanced stage, I did not have to go that far. I guess for that you really need FlexiSIP developers. Some of those guys were shown in the forum and you can try to send direct e-mail to them… The problem is they are in France and CoVid 19 hit France very hard, so my guess is – they are sitting at home (self-isolation or something) now… probably.
With Best Regards,
Sent from Mail for Windows 10
I have done all that to support my sip client as same as linphone app. Obtain token and been sent over register contact-uri in exact same way how it does with linphone app.
Every single parameter has been addressed, but the above is my error. It clearly show push works perfectly with the token and some thing else refusing to resume the forked call to the newly registered app.
Yes i have had a look in the code and it says it should match the uid. which is uuid in this case or it can set as even pn-tok or even a line parameters. Hope u can understand how deep i have went into troubleshoot this.
According to the code the newly reg sip_uri and uid must match with the previously queued invite message to resume and thats what i have been doing.
i have spent tremendous amount of time and effort to develop it so far, but this penny hitch is putting a deadlock to flexisip approach.
On Tue, Apr 7, 2020 at 11:38 AM Mikhail Sviridov <address@hidden> wrote:
|[Prev in Thread]||Current Thread||[Next in Thread]|