![D-Link DRO-220i Скачать руководство пользователя страница 62](http://html.mh-extra.com/html/d-link/dro-220i/dro-220i_user-manual_75203062.webp)
Frequently Asked Questions
Dlink DRO-220i User Guide
62
Connect your Web Servers to the DMZ Port and configure DMZ Systems in a
specific private subnet (e.g 192.178.1.0/24).
Go to NAT
→
Virtual Server/NAPT and add an entry to redirect your Server
traffic (eg. HTTP, FTP) from the Global IP to the DMZ Internal Server IP
Address.
Instead of Virtual Server configuration, you can also use One-To-One NAT. Go
to NAT
→
NAT Configuration, and configure a One-To-One NAT entry mapping
the global IP Address to the Internal Server IP Address.
Q11.
I am unable to access my server in the DMZ Port. What could be the problem?
Ans:
To troubleshoot this issue, follow the below steps:
Ensure that Virtual Server or One-To-One NAT has been configured to access the
DMZ Server. Specifically verify the global IP Address, private IP Address and
Port Number configuration.
If everything is proper but still not working, then verify Status
→
Log Tables
→
Blocking Log to see the reason why the traffic has been blocked from entering
inside.
Q12.
I am using SIP-ALG for VoIP Calls between my branch offices. But I am not
able to register my phones to the SIP Server. What could be the problem?
Ans:
Follow the steps below to troubleshoot this issue:
Verify the phone network configurations for default gateway and dns server
Verify the phone sip configurations for user name, password and proper
registration port
Ensure that the SIP Server IP Address is reachable by pinging to it.
Q13.
What are the call features supported by SIP-ALG?
Ans:
The call features supported by SIP-ALG are as below:
a.
Registration
b.
Call Establishment
c.
Attended Call transfer
d.
Unattended Call transfer
e.
Call Forward
f.
Voice Mail
g.
Conference Call
Q14.
I am using SIP-ALG for VoIP Calls between my branch offices. My VoIP Call
has been established, but I am unable to hear the voice of the other person. What
could be the problem?
Ans:
This problem can occur if the SIP Phone has been registered to the Server with the
private IP Address/Port. Ensure that your phone’s signaling port or the SIP Server
signaling port has been configured at the router via NAT
→
SIP-ALG.