ConnectivityProblems » History » Version 4
Adrian Georgescu, 07/21/2013 10:19 PM
| 1 | 1 | Adrian Georgescu | h1. Connectivity Problems |
|---|---|---|---|
| 2 | |||
| 3 | Sometimes communication between end-points fails. What can be the reasons? Here is a short checklist: |
||
| 4 | |||
| 5 | h2. Local Computer |
||
| 6 | |||
| 7 | 2 | Adrian Georgescu | * Firewall software. Check if no software blocks access to the ports used by your application |
| 8 | 1 | Adrian Georgescu | |
| 9 | 2 | Adrian Georgescu | h2. Internet Router |
| 10 | 1 | Adrian Georgescu | |
| 11 | 2 | Adrian Georgescu | * SIP ALG enabled. Check of the router has any so called SIP support and disabled it. |
| 12 | 1 | Adrian Georgescu | |
| 13 | 3 | Adrian Georgescu | h2. Internet Provider |
| 14 | 1 | Adrian Georgescu | |
| 15 | 2 | Adrian Georgescu | * 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. |
| 16 | 1 | Adrian Georgescu | |
| 17 | 3 | Adrian Georgescu | h2. SIP Service Provider |
| 18 | 1 | Adrian Georgescu | |
| 19 | 4 | Adrian Georgescu | * 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 |
| 20 | * Some codecs are not supported. Instead of rejecting such sessions with an appropriate code, they simply won't answer. |
||
| 21 | |||
| 22 | |||
| 23 | |||
| 24 | 1 | Adrian Georgescu | |
| 25 | |||
| 26 | |||
| 27 | |||
| 28 |