Hi Mike, Blink does not have an explicit keep-alive mechanism, but it does respond to keep alive packets like an OPTIONS packet sent by a SIP server.
As a rule of thumb, a SIP provider should not depend on clients for keeping their registrations alive. Their infrastructure could be missing some logic if they need clients to do stuff to stay connected. If the client registration is lost you could try lowering the registration time (again the server could force that as well without any configuration in the client) or you can switch to a reliable transport like TCP or TLS, again is up to the server to force these as well. Another culprit could be a broken NAT router, google for "SIP ALG problem” whereby a router can break the SIP signalling by mangling packets. The solution is found in the search result. If you have more specific information about the type of keep alive required by the server we could perhaps formulate a more accurate answer. Regards, Adrian > On 28 Aug 2018, at 15:28, Mike Phillips <pat...@gmail.com> wrote: > > I tried using Blink with a VOIPo account, but the results were unpredictable. > Callers complained that they received busy signals or that no one answered. > When we switched to another SIP client, the problem went away. We then > started using the JK Audio IP2 interface, and the problems returned. Enabling > "Keep Alive" in the JK box solved the problem. > > Is there a way to tell Blink to Keep Alive? I've read that forwarding a port > to the client might help. > > _______________________________________________ > Blink mailing list > Blink@lists.ag-projects.com > http://lists.ag-projects.com/mailman/listinfo/blink
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Blink mailing list Blink@lists.ag-projects.com http://lists.ag-projects.com/mailman/listinfo/blink
