Re: Late fork pending context not interested in new register

On Tue, Apr 7, 2020 at 2:18 PM Nik Pakar <address@hidden> wrote:

I'm trying this. It should grab all dependencies and work. But still failing

git clone git://git.linphone.org/flexisip --depth 1 --recursive
cd flexisip
./prepare.py flexisip
make -C WORK/flexisip/cmake

On Tue, 7 Apr 2020 at 1:17 pm, Mikhail Sviridov <address@hidden> wrote:

Yes I’ve managed to compile it from the sources. It was tricky but it worked. Now I do not remember what exactly did I do for that. One thing is certain - you need all dependencies resolved. Mostly it includes a lot of the code from other linphone projects, so you need to pull a lot of the code from the repository and install other dev-* code.

But in my case the whole idea was – to go with the installations from the repository, so I did not do that again.

With Best Regards,

Mikhail.

Sent from Mail for Windows 10

From: Nik Pakar
Sent: Tuesday, April 7, 2020 10:41 AM
To: Mikhail Sviridov
Cc: address@hidden
Subject: Re: Late fork pending context not interested in new register

Have u managed to compile flexisip from the source?

On Tue, 7 Apr 2020 at 12:30 pm, Nik Pakar <address@hidden> wrote:

Yes i have done quite a lot to get it to so far. It was not just setting up flexisip. But analyising every bit of its protocol stack and implement them on a client side.

To further analyse by setting some breakpoints in router module, i started downloding the source and compile. But that has become a nightmare. Gives so much dependency errors.

Yeh may be developers are not online these days. Hope every one safe and protected.

On Tue, Apr 7, 2020 at 12:27 PM Mikhail Sviridov <address@hidden> wrote:

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,

Mikhail.

Sent from Mail for Windows 10

From: Nik Pakar
Sent: Tuesday, April 7, 2020 9:49 AM
To: Mikhail Sviridov
Cc: address@hidden
Subject: Re: Late fork pending context not interested in new register

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:

Indeed FlexiSIP developers are here… sometime. Also FlexiSIP is Open Source project, so technically everyone is/could be FlexiSIp developer. I’ve downloaded sources of the FlxexiSIP and it helped a lot when you can take a look inside sources. For example the issue with the iOS push notifications.

Indeed you will have push notifications working with the Linphone based phone only, because FlexiSIP needs to know token of the phone for the push happened. And that token FlexiSIP acquires during registration when Linphone based phones send those tokens as part of the REGISTER message. If you take a look in the debug logs you can see those messages and tokens inside. If other phones can provide that REGISTER same way as Linphone dose – they will be able to participate in the push notification, if not – not a chance. I do not know any other way to supply FlexiSIP with the tokens. May be it exists, but I doubt it.

Other SIP servers need those tokens too and those SIP serves use different tricks to obtain tokes. F.e. in Kamailio you can write script to receive the token but you need to write something on the client side too – just to send this token. In FlexiSIP + Linphone phones it works automatically. BTW that was one of key points that we choose FlexiSIP.

With Best Regards,
Mikhail.

Sent from Mail for Windows 10

From: Nik Pakar
Sent: Tuesday, April 7, 2020 6:23 AM
To: Mikhail Sviridov
Cc: address@hidden
Subject: Re: Late fork pending context not interested in new register

Thanks Mikhail,

I thought this is developer forum and flexisip developers are here.

Did u manage to do iOS push with flexisip and linphone or other client? Problem is it's all works fine with linohone but not with another client even if u try to supplement with all required parameters.

On Mon, 6 Apr 2020 at 11:54 pm, Mikhail Sviridov <address@hidden> wrote:

Hi Nick,

Nope the mailing list is not dead. Just not everyone has required experience. I can install some simple proxy + iOS push notifications, yet your problem requires some advanced skills in FlexiSIP. At this very moment I do not have much time to play with FlexiSIP, sorry about that.

With Best Regards,

Mikhail.

Sent from Mail for Windows 10

From: Nik Pakar
Sent: Monday, April 6, 2020 9:17 PM
To: address@hidden
Subject: Re: Late fork pending context not interested in new register

Dear all, is this mailing-list dead ?

On Mon, Apr 6, 2020 at 12:26 AM Nik Pakar <address@hidden> wrote:

Dear all,

I have a problem with late fork with a late registered client. Its not forking to newly registered client. It says there is a pending context but not interested in new register.

Appreciate if some one can give some help to identify the reason. Below is the log.

-Nik

==========================

2020-04-05 17:51:09:163 flexisip-debug-Replying Request SIP message: 200 Registration successful

2020-04-05 17:51:09:163 flexisip-debug-tport_tsend(0x55f85e271530) tpn = UDP/251.180.238.9:5060

2020-04-05 17:51:09:163 flexisip-debug-tport_resolve addrinfo = 251.180.238.9:5060

2020-04-05 17:51:09:163 flexisip-debug-tport_by_addrinfo(0x55f85e271530): not found by name UDP/251.180.238.9:5060

2020-04-05 17:51:09:163 flexisip-debug-tport_vsend returned 874

2020-04-05 17:51:09:163 flexisip-debug-nta: sent 200 Registration successful for REGISTER (2)

2020-04-05 17:51:09:163 flexisip-debug-nta_incoming_destroy: 0x55f85e29c420

2020-04-05 17:51:09:163 flexisip-debug-Terminate SipEvent 0x55f85e279860

2020-04-05 17:51:09:163 flexisip-debug-Delete IncomingTransaction 0x55f85e2799c0

2020-04-05 17:51:09:163 flexisip-debug-Publish topic = address@hidden, uid = "<urn:uuid:30172c0a-1bff-40e2-9e4c-05aa2d0031d3>"

2020-04-05 17:51:09:163 flexisip-debug-Notify topic = address@hidden, uid = "<urn:uuid:30172c0a-1bff-40e2-9e4c-05aa2d0031d3>"

2020-04-05 17:51:09:163 flexisip-debug-Step: 1 Found contact sip:address@hidden -> sip:2007@bbb.invalid;app-id=929724111839;pn-type=firebase;pn-timeout=0;pn-tok=eSU1YsrXrV8:APA91bHdw3wi_9Zbuh0pHy8z0ONEjaS5WlbeeyF04s_r7IcnhbpXERiAGog_y0v1t5weAibXn487Nnq8_nUCaxN1YjwG9uhen6c9_IqjvtXYrS6Y8LBva8BklB0nvEfktEjIaUsqaZ81;pn-silent=1;ov-ob=8e9da0352c;fs-conn-id=df04a1e177ce955 usedAsRoute:0

2020-04-05 17:51:09:163 flexisip-debug-Step: 1 Returning collected records 1

2020-04-05 17:51:09:163 flexisip-debug-Notify topic = address@hidden to listener 0x55f85e279d60

2020-04-05 17:51:09:163 flexisip-debug-Listener invoked for topic = address@hidden, uid = "<urn:uuid:30172c0a-1bff-40e2-9e4c-05aa2d0031d3>", sipUri = sip:address@hidden

2020-04-05 17:51:09:164 flexisip-debug-Searching for fork context with key address@hidden

2020-04-05 17:51:09:164 flexisip-debug-ForkContext 0x55f85e2880a0: onNewRegister(): pending transaction for this destination.

2020-04-05 17:51:09:164 flexisip-debug-Found a pending context but not interested in this new register.

2020-04-05 17:51:09:856 flexisip-debug-Call id 3893230802

2020-04-05 17:51:09:856 flexisip-debug-There are 1 calls active in the MediaRelay call list.

2020-04-05 17:51:14:856 flexisip-debug-Call id 3893230802

2020-04-05 17:51:14:856 flexisip-debug-There are 1 calls active in the MediaRelay call list.

2020-04-05 17:51:19:856 flexisip-debug-Call id 3893230802

2020-04-05 17:51:19:856 flexisip-debug-There are 1 calls active in the MediaRelay call list.

2020-04-05 17:51:24:856 flexisip-debug-Call id 3893230802

From:	Nik Pakar
Subject:	Re: Late fork pending context not interested in new register
Date:	Tue, 7 Apr 2020 15:17:23 +0530