Home
>
Multi-Tech Systems
>
Communications System
>
Multi-Tech Systems Mvp-2400/2410/3010, Mvp-210/410/810 Voice/ip Gateways S000249C User Guide
Multi-Tech Systems Mvp-2400/2410/3010, Mvp-210/410/810 Voice/ip Gateways S000249C User Guide
Have a look at the manual Multi-Tech Systems Mvp-2400/2410/3010, Mvp-210/410/810 Voice/ip Gateways S000249C User Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 104 Multi-Tech Systems manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
MultiVOIP User Guide Technical Configuration (Analog) 221 the channel over which the call is being originated (for example, “Calling Party - Omaha Sales Office Line 2”). If that voip channel is dedicated to a certain individual, the descriptor could say that, as well (for example “Calling Party - Harold Smith in Omaha”). When the home voip receives a call from any remote voip, the home voip sends a status message back to that caller. This message confirms that the home voip’s phone channel is either busy or ringing or that a connection has been made (for example, “Busy Party - Omaha Sales Office Line 2”). These messages appear in the Statistics – Call Progress screen of the remote voip. Note that Supplementary Services parameters are applied on a channel- by-channel basis. However, once you have established a set of Supplementary parameters for a particular channel, you can apply this entire set of parameters to another channel by using the Copy Channel button and its dialog box. To copy a set of Supplementary Services parameters to all channels, select “Copy to All” and click Copy.
MultiVOIP User Guide Technical Configuration (Analog) 222 The Supplementary Services fields are described in the tables below. Supplementary Services Parameter Definitions Field Name Values Description Select Channel1-2 (210); 1-4 (410); 1-8 (810)The channel to be configured is selected here. Call Transfer EnableY/NSelect 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. Transfer Sequenceany phone keypad characterThe 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*#.
MultiVOIP User Guide Technical Configuration (Analog) 223 Supplementary Services Definitions (cont’d) Field Name Values Description Call Hold EnableY/NSelect 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 Sequencephone 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 EnableY/NSelect to enable Call Waiting function in voip unit. Retrieve Sequencephone 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.
MultiVOIP User Guide Technical Configuration (Analog) 224 Supplementary Services Definitions (cont’d) Field Name Values Description Call Name Identification EnableEnables 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 GUI (the ‘home voip’), Call Name 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 callee (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.)
MultiVOIP User Guide Technical Configuration (Analog) 225 Supplementary Services Definitions (cont’d) Field Name Values Description 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.
MultiVOIP User Guide Technical Configuration (Analog) 226 Supplementary Services Definitions (cont’d) Field Name Values Description 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.
MultiVOIP User Guide Technical Configuration (Analog) 227 Supplementary Services Definitions (cont’d) Field Name Values Description 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.
MultiVOIP User Guide Technical Configuration (Analog) 228 Supplementary Services Definitions (cont’d) Field Name Values Description 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. 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.
MultiVOIP User Guide Technical Configuration (Analog) 229 Supplementary Services Definitions (cont’d) Field Name Values Description 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.
MultiVOIP User Guide Technical Configuration (Analog) 230 16. Set Baud Rate. The Connection option in the sidebar menu has a “Settings” item that includes the baud-rate setting for the COM port of the computer running the MultiVOIP software. First, it is important to note that the default COM port established by the MultiVOIP program is COM1. Do not accept the default value until you have checked the COM port allocation on your PC. To do this, check for COM port assignments in the system resource dialog box(es) of your Windows operating system. If COM1 is not available, you must change the COM port setting to COM2 or some other COM port that you have confirmed as being available on your PC. The default baud rate is 115,200 bps.