Liviu, I found the problem: In the usrloc module I had "contact_refresh_timer" set to true. When I change it to false, lookup returns 2. I had not understood the relationship between the two mechanisms - should I use either one or the other, not both?
By the way, the Contact header is very large and exceeds the varchar(255) field in the DB. I've set the usrloc working mode preset to "single-instance-no-db" as a workaround. I'm not sure if the WebRTC app being tested here is exceptional or if this could be a more widespread ongoing problem that other people will encounter. John Quick Smartvox Limited -----Original Message----- From: Liviu Chircu <[email protected]> Sent: 29 July 2021 18:22 To: [email protected]; 'OpenSIPS users mailling list' <[email protected]> Subject: Re: [OpenSIPS-Users] Push Notification - lookup not returning 2 On 29.07.2021 19:07, John Quick wrote: > modparam("mid_registrar", "pn_skip_pn_interval", 6) So all looks good except for this condition [1] which returns false, otherwise the lookup() result would immediately be 2. Now, that condition will only return false if the contact had registered within the last 6 seconds, case in which your custom "pn_skip_pn_interval" kicks in, effectively skipping sending a PN to that device. Have you automated this test scenario to the point where the INVITE always lands within 6 seconds of the registration, or does the problem happen even long after the WebRTC phone registers? [1]: https://github.com/OpenSIPS/opensips/blob/master/lib/reg/lookup.c#L426 -- Liviu Chircu www.twitter.com/liviuchircu | www.opensips-solutions.com OpenSIPS Summit 2021 Distributed | www.opensips.org/events _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
