Technical Configuration | MultiVOIP User Guide | ||
|
|
|
|
|
|
|
|
| Supplementary Services Definitions (cont’d) | ||
|
|
|
|
| Field Name | Values | Description |
|
|
|
|
| Busy Party, |
| If the ‘home’ voip unit is receiving a |
| Allowed |
| call directed toward an already |
| Name Type |
| engaged channel or phone station and |
| (CNI) |
| 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. |
|
|
|
|
