Grandstream Networks GXW40XX - Page 46

FIRMWARE VERSION 1.0.6.8 GXW40XX USER MANUAL Page 46 of 59
Use random port
Default is No. If set to Yes, the device will pick randomly-generated SIP and RTP ports.
This is usually necessary when multiple GXW40XX/HT50X are behind the same NAT.
Refer to Use Target
Contact
Default is No. If set to YES, then for Attended Transfer, the “Refer-To” header uses the
transferred target’s Contact header information.
Transfer on
Conference
Hang up
Default is No. In which case if conference originator hangs up the conference will be
terminated. When option YES is chosen, originator will transfer other parties to each
other so that B and C can choose either to continue the conversation or hang up.
Enable Ring-Transfer
Default is No, this will create a Semi-Attendant Transfer. When set to Yes, device can
transfer the call upon receiving ring back tone.
Disable Bellcore Style
3-Way Conference
Default is No. you can make a Conference by pressing ‘Flash’ key. If set to Yes, you
need to dial *23 + second callee number.
Remove OBP from
Route Header:
Default is No. If set to Yes, the Outbound Proxy will be removed from the route header.
Support SIP Instance
ID
Default is Yes. If set to Yes, the contact header in REGISTER request will contain SIP
Instance ID as defined in IETF SIP Outbound draft.
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.
SIP T1 Timeout
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.
SIP T2 Interval
Maximum retransmission interval for non-INVITE requests and INVITE responses.
DTMF Payload Type
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.
Disable DTMF
Negotiation
Default is No. If set to yes, use above DTMF order without negotiation