Re: Late fork pending context not interested in new register

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:	Mon, 6 Apr 2020 23:45:51 +0530