By default, sofia-sip uses OPTIONS to keep the connection. This is what I see in the logs rakiasofia-DEBUG: 08.06.2015 21:47:36.5841: outbound(0x8fb500): FAILED to validate <sip:me@myip:41151;transport=udp> rakiasofia-DEBUG: 08.06.2015 21:47:36.5909: outbound(0x8fb500): FAILED with 200 OK rakiaevents-DEBUG: 08.06.2015 21:47:36.5975: rakia_base_connection_sofia_callback: event nua_i_outbound: 200 OK rakiaevents-DEBUG: 08.06.2015 21:47:36.6016: rakia_base_connection_sofia_callback: connection 0x8ee180, refcount 1 rakiaevents-DEBUG: 08.06.2015 21:47:36.6058: rakia_base_connection_sofia_callback: dispatching to target 0x8ee180 (handle 0x8fb500) rakiaevents-DEBUG: 08.06.2015 21:47:36.6105: rakia_base_connection_sofia_callback: event nua_i_outbound for target 0x8ee180 was not consumed rakiaevents-DEBUG: 08.06.2015 21:47:36.6150: rakia_base_connection_sofia_callback: exit After several of such FAILEDs, SIP server seem to stop answering to requests, and then instead I see rakiaevents-DEBUG: 08.06.2015 21:57:40.64382: rakia_base_connection_sofia_callback: event nua_i_outbound: 403 Forbidden rakiaevents-DEBUG: 08.06.2015 21:57:40.64475: rakia_base_connection_sofia_callback: connection 0x2284180, refcount 1 rakiaevents-DEBUG: 08.06.2015 21:57:40.64539: rakia_base_connection_sofia_callback: dispatching to target 0x2284180 (handle 0x2291d00) rakiaevents-DEBUG: 08.06.2015 21:57:40.64605: rakia_base_connection_sofia_callback: event nua_i_outbound for target 0x2284180 was not consumed rakiaevents-DEBUG: 08.06.2015 21:57:40.64677: rakia_base_connection_sofia_callback: exit At this point SIP account stops getting incoming calls.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-rakia/issues/27.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.