Failure to negotiate a call connection will prevent the call from connecting. While Pickle implements measures to ensure as many calls as possible are successful, some circumstances are outside of Pickle's control, with such issues typically originating from local network hardware, firewalls, and their configuration.

Some networks, especially highly secure corporate networks, may prevent UDP packets from traversing through the NAT (Network Address Translator). While Pickle connections may transmit audio packets via TCP, instead, those packets are merely UDP framed by TCP. As such, networks that perform deep packet analysis may still restrict their transport through the NAT.

SIP ALG (Application Layer Gateway) is an extension of many NAT’s (Network Address Translators) and Firewalls and are commonly found in commercial and home-based router devices. The intention of SIP ALG was to address shortcomings in SIP / VoIP packet handling, but many fail to correctly manage such data, resulting in numerous call quality deficiencies and, as importantly, call establishment.

Call connections and call quality within the Pickle app is completely managed from the application itself. As such, any use of SIP ALG can only hinder calls made using PickleCall.

VPN’s (Virtual Private Networks) provides a tunnel to another location so that throughput to and from your device appears to originate from another location. Aside from adding potential latency, jitter, and packet loss to your Pickle call’s, using a VPN may also negatively impact call negotiation, as the network addressing can become confused, resulting in call connections missing their intended recipient.