Grandstream Networks HT386 SIP Server, Outbound Proxy, SIP User ID, Myuserid, Authenticate ID

Models: HT386

1 34
Download 34 pages 17.21 Kb
Page 23
Image 23

 

TABLE 10: HT-386 FXS PORT1/FXS PORT2 SETTINGS PAGES DEFINITIONS

 

 

 

 

 

 

 

 

 

SIP Server

 

This field contains the URI string or the IP address (and port, if different from

 

 

 

 

 

5060) of the SIP proxy server. e.g., the following are some valid examples:

 

 

 

 

 

sip.my-voip-provider.com, or sip:my-company-sip-server.com, or

 

 

 

 

 

192.168.1.200:5066

 

 

 

 

 

 

 

 

 

Outbound Proxy

 

 

IP address or Domain name of Outbound Proxy, or Media Gateway, or

 

 

 

 

Session Border Controller. Used by ATA for firewall or NAT penetration in

 

 

 

 

 

different network environment. If symmetric NAT is detected, STUN will not

 

 

 

 

 

work and ONLY Outbound Proxy will work.

 

 

 

 

 

 

 

 

SIP User ID

 

 

User account information, provided by VoIP service provider (ITSP), usually

 

 

 

 

 

has the form of digit similar to phone number or actually a phone number. This

 

 

 

 

 

field contains the user part of the SIP address for this phone. e.g., if the SIP

 

 

 

 

 

address is sip:my_user_id@my_provider.com, then the SIP User ID is:

 

 

 

 

 

my_user_id.

 

 

 

 

 

 

Do NOT include the preceding “sip:” scheme or the host portion of the SIP

 

 

 

 

 

address in this field.

 

 

 

 

 

 

 

 

Authenticate ID

 

 

ID used for authentication, usually same as SIP user ID, but could be different

 

 

 

 

 

and decided by ITSP.

 

 

 

 

 

 

 

 

Authentication

 

 

Password for ATA to register to (SIP) servers of ITSP. Purposely blank out

 

 

Password

 

 

once saved for security. Maximum length is 25.

 

 

 

 

 

 

 

 

 

Name

 

 

User name, not user ID, for information only.

 

 

 

 

 

 

 

 

Use DNS SRV:

 

 

Default is No. If set to Yes the client will use DNS SRV to lookup for the server

 

 

 

 

 

 

 

User ID is Phone

 

 

If the HT-386 has an assigned PSTN telephone number, this field should be

 

 

Number

 

 

set to “Yes”. Otherwise, set it to “No”.

 

 

 

 

 

 

. If set to yes, a “user=phone” parameter will be attached to the “From” header

 

 

 

 

 

in SIP request

 

 

 

 

 

 

 

 

SIP Registration

 

 

This parameter controls whether the HT-386 needs to send REGISTER

 

 

 

 

 

messages to the proxy server. The default setting is “Yes”.

 

 

 

 

 

 

 

 

Unregister On Reboot

 

 

Default is No. If set to Yes, the device will first send registration request to

 

 

 

 

 

indicate SIP registra to remove previous bindings.

 

 

 

 

 

 

 

 

Register Expiration

 

 

This parameter allows the user to specify the time frequency (in minutes) the

 

 

 

 

 

HT-386 will refresh its registration with the specified registrar. The default

 

 

 

 

 

interval is 60 minutes (or 1 hour). The maximum interval is 65535 minutes

 

 

 

 

 

(about 45 days).

 

 

 

 

 

 

 

 

Local SIP port

 

 

This parameter defines the local SIP port the HT-386 will listen and transmit.

 

 

 

 

 

The default value is for FXS1 is 5060, FXS2 is 5062

 

 

 

 

 

 

 

 

Local RTP port

 

 

This parameter defines the local RTP-RTCP port pair the HT-386 will listen

 

 

 

 

 

and transmit. It is the base RTP port for channel 0. When configured, channel

 

 

 

 

 

0 will use this port_value for RTP and the port_value+1 for its RTCP; channel

 

 

 

 

 

1 will use port_value+2 for RTP and port_value+3 for its RTCP. The default

 

 

 

 

 

value for FXS1 is 5004, FXS2 is 5008.

 

 

 

 

 

 

 

 

Use Random Port

 

 

Default No. If set to Yes, the device will pick randomly-generated SIP and RTP

 

 

 

 

 

ports. This is usually necessary when multiple SIP devices are behind the

 

 

 

 

 

same NAT. For Direct IP to IP call, this should be set to No.

 

 

 

 

 

 

 

DTMF Payload Type

 

 

This parameter sets the payload type for DTMF using RFC2833

 

 

 

 

 

 

 

Send DTMF

 

 

This parameter specifies the mechanism to transmit DTMF digit. There are 3

 

 

 

 

 

modes supported: in audio which means DTMF is combined in audio signal

 

 

 

 

 

(not very reliable with low-bit-rate codec), via RTP (RFC2833), or via SIP

 

 

 

 

 

 

 

 

 

Grandstream Networks, Inc.

 

HT-386 User Manual

Page 23 of 34

 

 

 

 

 

Firmware 1.0.3.64

Last Updated: 2/2007

 

Page 23
Image 23
Grandstream Networks HT386 SIP Server, Outbound Proxy, SIP User ID, Myuserid, Authenticate ID, Authentication, Name