Application Guide
P a g e  |  45   
DP750/DP720 Administration Guide 
Version 1.0.3.37 
SIP Settings - Security Settings 
Validate Incoming 
Messages 
Defines whether incoming messages will be validated or not.  
Default is No. 
Check SIP User ID 
for Incoming INVITE 
Checks SIP User ID in the Request URI of incoming INVITE; if it doesn't match the 
base SIP User ID, the call will be rejected. Direct IP calling will also be disabled. 
Default is No. 
Accept Incoming 
SIP from Proxy 
Only 
Checks SIP address of the Request URI in the incoming SIP message; if it doesn't 
match SIP server address of the account, the call will be rejected.  
Default is No.     
Authenticate 
Incoming INVITE 
Challenges  the  incoming  INVITE  for  authentication  with  SIP  401  Unauthorized 
message.   
Default is No. 
Authenticate Server 
Certificate Domain 
Checks server TLS certificate to ensure that common name matches the configured 
SIP server.   
Default is No. 
Authenticate Server 
Certificate Chain 
Checks server TLS certificate to ensure that it is authorized by a known certificate 
authority.  
Default is No. 
Trusted CA 
Certificate 
Treats entered certificate as a valid CA for authenticating the server TLS certificate. 
Default is No. 
Audio Settings 
Send DTMF 
Specifies the mechanism to transmit DTMF digits. There are 3 supported modes: 
•  In audio: which means DTMF is combined in the audio signal (not very reliable 
with low-bit-rate codecs);   
•  Via RTP (RFC2833): permits to specify DTMF with RTP packet. Users could 
know the packet is DTMF in the RTP header as well as the type of DTMF;   
•  SIP INFO: uses SIP INFO to carry DTMF. The defect of this mode is that it's 
easily to cause desynchronized of DTMF and media packet for the reason the 
SIP and RTP are transmitted respectively.  
Default is via RTP (RFC2833) 
Disable DTMF 
Negotiation 
Uses above DTMF order without negotiation.  
Default is No. 
DTMF Payload Type 
Defines payload type for DTMF using RFC2833. 










