TELES VoIPBox BRI, Reference Manual

Page: 272 / 280

12 Troubleshooting
VoIPBox BRI Version 18.0.002 Page 272
|
Keep your firewall entries in the correct order if you are
using the quick command: place the more specific en-
tries above the more general ones because the search is
done from top to bottom and stops at the first match.
VoIP: Problems with incoming calls often originate in the glo-
bal VoIP settings in the
pabx.cfg
file. Global VoIP settings ap-
ply to the whole system, not just to any particular VoIP profile.
|
Check that the SIP port has been set correctly and
matches the sender’s destination port. If not, an incom-
ing VoIP call will not reach the gateway. If you are using
the default SIP and H.225 ports (SIP: 5060, H.225: 1720),
you don’t need to set these two parameters in the global
VoIP settings. For an explanation of the global VoIP set-
tings please go to Chapter 4.2.1.6 Global Settings
→
.
VoIP : Authentication problems can also be the reason why a
VoIP call does not arrive on the gateway.
|
Often, gateways need to register at the VoIP carrier be-
fore being able to receive calls. Nowadays authentica-
tion is mostly done using registrar (SIP) or gatekeeper
(H.323) profiles, which you configure in the
route.cfg
file.
If a VoIP call does not arrive on the gateway, this might
be due to incorrect or missing registrar or gatekeeper
profiles. To look up the registration state of your gate-
Example 12.2 udp 5060 (SIP) for IP 195.4.12.0/24 range enabled, all other udp ports blocked
fw=pass in quick on emac0 proto udp from 195.4.12.0/24 to any port eq 5060 keep state
fw=block in quick on emac0 proto udp all keep state
Example 12.3 Global VoIP settings in the
pabx.cfg
; IP Configuration
VoipGlobalMaxChan=16
H225Port=1720 ;default port
SipPort=5060 ;default port
...