____________________________________________________________________________________
____________________________________________________________________________________
52 VoIP subscriber gateways
– Periodic SIP server polling (Keepalive NAT sessions) – allows you to support active UDP-session
when you work on NAT. It obviates the necessity to create the rules of port forwarding on the
external router. Session activity is supported by periodical sending one of the message types to SIP
server: OPTIONS, NOTIFY or CLRF.
Mode – message type selection for sending to SIP server (OPTIONS, NOTIFY or CLRF), Off –
disable SIP server polling;
Keepalive timeout, s – SIP server polling time period to support active UDP connection;
– Three-party conference – service provides establishing connection between three subscribers;
Mode – selection of three-party operation mode:
Local – conference assembly is performed locally by the TAU-8.IP device after
pressing 'flash+3'; operation mode algorithm is described in the section 5.3.1;
Remote – conference assembly is performed at the remote server; after pressing
'flash+3', 'Invite' message will be sent to the server using number specified in the
'Conference server' field. In this case, conference operation complies with the algorithm
described in RFC4579. For detailed algorithm description, see 5.3.2;
Conference server – in general, address of the server that establishes conference using
algorithm described in RFC4579. Address is specified in the following format SIP-URI:
user@address:port. You may specify the 'user' URI part only—in this case, 'Invite'
message will be sent to the SIP proxy address;
– IMS settings:
IMS mode – service control configuration:
Off – simulation services by using IMS (3GPP TS 24.623) is disabled;
Implicit – implicit IMS subscription. Under this option, the gateway does not send
SUBSCRIBE requests after subscriber registration, processing only NOTIFY requests
received from IMS and used to manage subscriptions;
Explicit – explicit IMS subscription. Under this option, the gateway does not send
SUBSCRIBE requests after subscriber registration, processing only NOTIFY requests
received from IMS and used to manage subscriptions;
– XCAP name for call hold – name of the XML element located in the 'Notify' message body that
is used for transmission of 'Call hold' enabling/disabling commands. For example, if the
service name value is 'call-hold', enabling command will be as follows:
<call-hold active="true"/>
Disabling command:
<call-hold active="false"/>
– XCAP name for call waiting – name of the XML element located in the 'Notify' message body
that is used for transmission of 'Call waiting' enabling/disabling commands. For example, if
the service name value is 'call-waiting', enabling command will be as follows:
<call-waiting active="true"/>
Disabling command:
<call-waiting active="false"/>
– XCAP name for three-party conference – name of the XML element located in the 'Notify'
message body that is used for transmission of 'Three-way conference call' enabling/disabling
commands. For example, if the service name value is 'three-party-conference', enabling
command will be as follows:
< three-party-conference active="true"/>
Disabling command:
< three-party-conference active="false"/>
– XCAP name for hotline – name of the XML element located in the 'Notify' message body that
is used for transmission of 'Hotline' enabling command. In the enabling command, you should
pass the hotline number and the call timeout. For example, if the service name value is 'hot-
line-service' and you should call the number 30001 in 6 seconds after the phone handset is
picked up, the enabling command will be as follows:
<hot-line-service>
<addr>30001</addr>
To Next Page
Loading...
