Field Name Values Description
Enable (STUN) Y/N Enables STUN client functionality in the MultiVOIP.
STUN (Simple Traversal of UDP through NATs (Network Address Translation)) is a protocol that allows a server to assist client gateways behind a NAT firewall or router with their packet routing.
Name/IP (Server) n.n.n.n IP address of the STUN server.
Port (Server;
NAT/STUN)
port;
default=
3478
The data port (TDM time slot) at which STUN info will be transmitted and received.
Keep Alive (Timers;
NAT/STUN)
60 – 3600 (seconds)
The interval at which the STUN client sends indicator (“Keep Alive”) packets to the STUN server to determine whether or not the STUN server is available.
Field Name Values Description
Select Channel Channel 1 The channel to be configured is selected here.
Call Transfer Enable Y/N Select to enable the Call Transfer function in the VOIP unit.
This is a “blind” transfer and the sequence of events is as follows:
Callers A and B are having a conversation.
Caller A wants to put B into contact with C.
Caller A dials call transfer sequence.
Caller A hears dial tone and dials number for caller C.
Caller A gets disconnected while Caller B gets connected to caller C.
A brief musical jingle is played for the caller on hold.
Transfer Sequence Any phone keypad character
The numbers and/or symbols that the caller must press on the phone keypad to initiate a call transfer.
The call-transfer sequence can be 1 to 4 characters in length using any combination of digits or characters (* or #).
The sequences for call transfer, call hold, and call waiting can be from 1 to 4 digits in length consisting of any combination of digits 1234567890*#.
Call Hold Enable Y/N Select to enable Call Hold function in VOIP unit.
Call Hold allows one party to maintain an idle (non-talking) connection with another party while receiving another call (Call Waiting), while initiating another call (Call Transfer), or while performing some other call management function.
Hold Sequence phone keypad characters
The numbers and/or symbols that the caller must press on the phone keypad to initiate a call hold.
The call-hold sequence can be 1 to 4 characters in length using any combination of digits or characters (* or #).
Call Waiting Enable Y/N Select to enable Call Waiting function in VOIP unit.
Retrieve Sequence Phone keypad characters, two characters in length
The numbers and/or symbols that the caller must press on the phone keypad to initiate retrieval of a waiting call.
The call-waiting retrieval sequence can be 1 to 4 characters in length using any combination of digits or characters (* or #).
This is the phone keypad sequence that a user must press to retrieve a waiting call. Customize-able. Sequence should be distinct from sequence that might be used to retrieve a waiting call via the PBX or PSTN.
Call Name
Identification Enable
Enables CNI function. Call Name Identification is not the same as Caller ID. When enabled on a given VOIP unit currently being controlled by the MultiVOIP interface (the ‘home VOIP’), Call Name
Field Name Values Description
Identification sends an identifier and status information to the administrator of the remote VOIP involved in the call. The feature operates on a channel-by-channel basis (each channel can have a separate identifier).
If the home VOIP is originating the call, only the Calling Party field is applicable. If the home VOIP is receiving the call, then the Alerting Party, Busy Party, and Connected Party fields are the only applicable fields (and any or all of these could be enabled for a given VOIP channel). The status information confirms back to the originator that the home VOIP, is either busy, or ringing, or that the intended call has been completed and is currently connected.
The identifier and status information are made available to the remote VOIP unit and appear in the Caller ID field of its Statistics – Call Progress screen. (This is how MultiVOIP units handle CNI messages; in other VOIP brands, H.450 may be implemented differently and then the message presentation may vary.)
Calling Party, Allowed Name Type (CNI)
If the ‘home’ VOIP unit is originating the call and Calling Party is selected, then the identifier (from the Caller Id field) will be sent to the remote VOIP unit being called. The Caller Id field gives the remote VOIP administrator a plain-language identifier of the party that is originating the call occurring on a specific channel.
This field is applicable only when the ‘home’ VOIP unit is originating the call.
Example. Suppose a VOIP system has offices in both Denver and Omaha. In the Omaha VOIP unit (the
‘home’ VOIP in this example), Call Name Identification has been enabled, Calling Party has been enabled as an Allowed Name Type, and “Omaha Sales Office Voipchannel 2” has been entered in the Caller Id field.
When channel 2 of the Omaha VOIP is used to make a call to any other VOIP phone station (for example, the Denver office), the message “Calling Party - Omaha Sales Office Voipchannel 2” will appear in the “Caller Id” field of the Statistics - Call Progress screen of the Denver VOIP.
Alerting Party, Allowed Name Type (CNI)
If the ‘home’ VOIP unit is receiving the call and Alerting Party is selected, then the identifier (from the Caller Id field) will tell the originating remote VOIP unit that the call is ringing.
This field is applicable only when the ‘home’ VOIP unit is receiving the call.
Example. Suppose a VOIP system has offices in both Denver and Omaha. In the Omaha VOIP unit (the
‘home’ VOIP unit in this example), Call Name Identification has been enabled, Alerting Party has been enabled as an Allowed Name Type, and “Omaha Sales Office Voipchannel 2” has been entered in the Caller Id field of the Supplementary Services screen.
When channel 2 of the Omaha VOIP receives a call from any other VOIP phone station (for example, the Denver office), the message “Alerting Party - Omaha Sales Office Voipchannel 2” will be sent back and will appear in the Caller Id field of the Statistics – Call Progress screen of the Denver VOIP. This confirms to the Denver VOIP that the phone is ringing in Omaha.
Busy Party, Allowed Name Type (CNI)
If the ‘home’ VOIP unit is receiving a call directed toward an already engaged channel or phone station and Busy Party is selected, then the identifier (from the Caller Id field) will tell the originating remote VOIP unit that the channel or called party is busy.
This field is applicable only when the ‘home’ VOIP unit is receiving the call.
Example. Suppose a VOIP system has offices in both Denver and Omaha. In the Omaha VOIP unit (the
‘home’ VOIP unit in this example), Call Name Identification has been enabled, Busy Party has been enabled as an Allowed Name Type, and “Omaha Sales Office Voipchannel 2” has been entered in the Caller Id field of the Supplementary Services screen.
When channel 2 of the Omaha VOIP is busy but still receives a call attempt from any other VOIP phone station (for example, the Denver office), the message “Busy Party - Omaha Sales Office Voipchannel 2”
will be sent back and will appear in the Caller Id field of the Statistics – Call Progress screen of the Denver VOIP. This confirms to the Denver VOIP that the channel or phone station is busy in Omaha.
Connected Party, Allowed Name Type (CNI)
If the ‘home’ VOIP unit is receiving a call and Connected Party is selected, then the identifier (from the Caller Id field) will tell the originating remote VOIP unit that the attempted call has been completed and the connection is made.
This field is applicable only when the ‘home’ VOIP unit is receiving the call.
Example. Suppose a VOIP system has offices in both Denver and Omaha. In the Omaha VOIP unit (the
‘home’ VOIP unit in this example), Call Name Identification has been enabled, Connected Party has been enabled as an Allowed Name Type, and “Omaha Sales Office Voipchannel 2” has been entered in the Caller Id field of the Supplementary Services screen.
Field Name Values Description
When channel 2 of the Omaha VOIP completes an attempted call from any other VOIP phone station (for example, the Denver office), the message “Connect Party - Omaha Sales Office Voipchannel 2” will be sent back and will appear in the Caller Id field of the Statistics – Call Progress screen of the Denver VOIP. This confirms to the Denver VOIP that the call has been completed to Omaha.
Caller ID This is the identifier of a specific channel of the ‘home’ VOIP unit. The Caller Id field typically describes a person, office, or location, for example, “Harry Smith,” or “Bursar’s Office,” or “Barnesville Factory.”
Default When this button is clicked, all Supplementary Service parameters are set to their default values.
Copy Channel Copies the Supplementary Service attributes of one channel to another channel. Attributes can be copied to multiple channels or all channels at once.