ConnectivityProblems
Version 4 (Adrian Georgescu, 07/21/2013 10:19 pm) → Version 5/31 (Adrian Georgescu, 07/21/2013 10:20 pm)
h1. Connectivity Problems
Sometimes communication between end-points fails. What can be the reasons? Here is a short checklist:
h2. Local Computer
* Firewall software installed. software. Check if no software blocks access to the ports used by your application or enable the use of the proper ports in the firewall configuration.
h2. Internet Router
* SIP ALG enabled. Check of the router has any so called SIP support and disabled it.
* Firewall enabled. Check if no software blocks access to the ports used by your application or enable the use of the proper ports in the firewall configuration.
h2. Internet Provider
* Policy that blocks either SIP signalling or RTP media. You can try use another SIP service provider that provides access over TCP or TLS instead of UDP or is using custom ports.
h2. SIP Service Provider
* Eequires use of STUN protocol so that the SIP devices uses a public IP address in the Contact header. This is wrong and unreliable, such behaviour is explicitly discouraged by the "standards":http://projects.ag-projects.com/projects/blinkc/wiki/MostEncounteredProblems#SIP-Provider-requires-STUN
* Some codecs are not supported. Instead of rejecting such sessions with an appropriate code, they simply won't answer.
Sometimes communication between end-points fails. What can be the reasons? Here is a short checklist:
h2. Local Computer
* Firewall software installed. software. Check if no software blocks access to the ports used by your application or enable the use of the proper ports in the firewall configuration.
h2. Internet Router
* SIP ALG enabled. Check of the router has any so called SIP support and disabled it.
* Firewall enabled. Check if no software blocks access to the ports used by your application or enable the use of the proper ports in the firewall configuration.
h2. Internet Provider
* Policy that blocks either SIP signalling or RTP media. You can try use another SIP service provider that provides access over TCP or TLS instead of UDP or is using custom ports.
h2. SIP Service Provider
* Eequires use of STUN protocol so that the SIP devices uses a public IP address in the Contact header. This is wrong and unreliable, such behaviour is explicitly discouraged by the "standards":http://projects.ag-projects.com/projects/blinkc/wiki/MostEncounteredProblems#SIP-Provider-requires-STUN
* Some codecs are not supported. Instead of rejecting such sessions with an appropriate code, they simply won't answer.