
FIRMWARE VERSION 1.0.10.9 GXW40XX USER MANUAL Page 47 of
60
Validate incoming SIP
message
Default is No. If set to yes all incoming SIP messages will be strictly validated according
to RFC rules. If message does not pass validation process, call will be rejected.
Check SIP user ID for
incoming INVITE
Default is No. Check the SIP User ID in Request URI. If they don’t match, the call will
be rejected.
Allow Incoming SIP
Messages from SIP
Proxy Only
Default is No. If incoming SIP message does not match with SIP Server, it will be
rejected.
T1 is an estimate of the round-trip time between the client and server transactions.
If the network latency is high, select larger value for more reliable usage.
Maximum retransmission interval for non-INVITE requests and INVITE responses.
Sets the payload type for DTMF using RFC2833.
Preferred DTMF
method (in listed
order)
The GXW40xx supports up to 3 different DTMF methods including in-audio, via RTP
(RFC2833) and via Sip Info. The user can configure DTMF method in a priority list.
Default is No. If set to yes, use above DTMF order without negotiation
Default is No. If set to yes, flash will be sent as a DTMF event.
Default is Yes. (If Yes, call features using star codes will be supported locally)
SIP Extension to notify SIP server that the unit is behind the NAT/Firewall.
NAT IP address used in SIP/SDP message. Default is blank.
Use SIP User-Agent
Header
Used to replace SIP User-Agent Header (No Default)
Comentarios a estos manuales