|
|
|
| calls. |
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
| ||
|
| Register Expiration |
| This parameter allows the user to specify the time frequency (in minutes) the HT70X |
| ||
|
|
|
| refreshes its registration with the specified registrar. The default interval is 60 minutes |
| ||
|
|
|
| (or 1 hour). The maximum interval is 65535 minutes (about 45 days). |
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
| |
|
| Registration Retry Wait |
| Retry registration if the process failed. Default is 20 seconds. |
|
| |
|
| Time |
|
|
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
| ||
|
| Local SIP port |
| Defines the local SIP port the HT70X will listen and transmit. The default value for FXS |
| ||
|
|
|
| port is 5060. |
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
| ||
|
| Local RTP port |
| Defines the local |
| ||
|
|
|
| RTP port for channel 0. When configured, |
|
| |
|
|
|
| channel 0 uses this port _value for RTP and the port_value+1 for its RTCP |
| ||
|
|
|
| The default value for FXS port is 5004. |
|
| |
|
|
|
|
|
| ||
|
|
|
|
|
| ||
|
| Use Random SIP Port |
| Default is No. This parameter forces the random generation of The local SIP ports |
| ||
|
|
|
| when set to Yes. This is usually necessary when multiple HT70X are behind the same |
| ||
|
|
|
| NAT. |
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
| ||
|
| Use Random RTP Port |
| Default is No. This parameter forces the random generation of the local RTP ports |
| ||
|
|
|
| when set to Yes. This is usually necessary when multiple HT70X are behind the same |
| ||
|
|
|
| NAT. |
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
| ||
|
| Refer to Use Target |
| Default is No. If set to YES, then for Attended Transfer, the |
| ||
|
| Contact |
| transferred target’s Contact header information. |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||
|
| Transfer on Conference |
| Default is No. In which case if the conference originator hangs up the conference will |
| ||
|
| Hang up |
| be terminated. When option YES is chosen, originator will transfer other parties to |
| ||
|
|
|
| each other so that B and C can choose to either continue the conversation or |
| ||
|
|
|
| hang up. |
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
| ||
|
| Enable |
| Default is No, this will create a |
| ||
|
|
|
| transfer the call upon receiving ring back tone or SIP message 180. |
|
| |
|
|
|
|
|
| ||
|
|
|
|
|
| ||
|
| Disable Bellcore Style |
| 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 |
| Default is No. When option YES is chosen, the Out Bound Proxy will be removed from |
| ||
|
| Route Header |
| 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 |
| Default is No. If set to yes all incoming SIP messages will be strictly validated |
| ||
|
| message |
| according to RFC rules. If message will not pass validation process, call will be |
| ||
|
|
|
| rejected. |
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
| ||
|
| Check SIP User ID for |
| Default is No. Check the incoming SIP User ID in Request URI. If they don’t match, the |
| ||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FIRMWARE VERSION 1.0.3.1 | HT70X USER MANUAL | Page 37 of 52 |
| |||