
Chapter 3 – Related MultiVOIP Setup Parameters
FXO Interface: Parameter Definitions (cont’d)
| Field Name | Values | 
 | 
 | 
 | Description | 
 | 
 | 
 | |||||||
| FXO Disconnect On (cont’d) | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | ||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | |||
| Disconnect | 1st tone pair | 
 | 
 | 
 | These are DTMF tone pairs. | ||||||||||
| Tone Sequence | + | 
 | 
 | 
 | 
 | 
 | Values for first tone pair are: | ||||||||
| 
 | 2nd tone pair | 
 | 
 | 
 | |||||||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | *, #, 0,  | 
 | 
 | |||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | Values for second tone pair are: | |||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | none, 0,  | |||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | The tone pairs  | |||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | phone sets. The tone pairs  | |||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | are used for various PBX functions. | |||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | |
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | ||
| 
 | 
 | 
 | 
 | 
 | DTMF Tone Pairs | 
 | Low Tones | 
 | |||||||
| 
 | 
 | 
 | 
 | 1 | 
 | 
 | 2 | 
 | 3 | 
 | 
 | A | 
 | ||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 697Hz | 
 | |||||
| 
 | 
 | 
 | 
 | 4 | 
 | 
 | 5 | 
 | 6 | 
 | 
 | B | 770Hz | 
 | |
| 
 | 
 | 
 | 
 | 7 | 
 | 
 | 8 | 
 | 9 | 
 | 
 | C | 852Hz | 
 | |
| 
 | 
 | 
 | 
 | * | 
 | 
 | 0 | 
 | # | 
 | 
 | D | 941Hz | 
 | |
| 
 | 
 | High Tones | 
 | 1209Hz | 
 | 1336Hz | 
 | 1447Hz | 
 | 1633Hz | 
 | 
 | |||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | ||||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
| Silence | 
 | 
 | 
 | Disconnection to be triggered by silence in one direction only or in | |||||||||||
| Detection | 
 | 
 | 
 | both directions simultaneously. | |||||||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | |||
| Silence Timer | integer value | 
 | 
 | 
 | Duration of silence required to trigger disconnection. | ||||||||||
| in seconds | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | |||
| Disconnect on | Y/N | 
 | 
 | 
 | Allows call on FXO port to be disconnected when a PBX issues a call- | ||||||||||
| Call Progress | 
 | 
 | 
 | 
 | 
 | 
 | 
 | progress tone denoting that the phone station on the PBX that has | |||||||
| Tone | 
 | 
 | 
 | 
 | 
 | 
 | 
 | been involved in the call has been hung up. | |||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | |||
| Ring Count, | 
 | 
 | 
 | 
 | 
 | Number of rings required before the MultiVOIP answers the | |||||||||
| FXO | 
 | 
 | 
 | 
 | 
 | 
 | 
 | incoming call. | 
 | 
 | 
 | ||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
| Flash Hook Options fields | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | ||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | |||
| Generation | 50 - 1500 | 
 | 
 | 
 | 
 | 
 | Length of flash hook that will be generated and sent out when the | ||||||||
| 
 | milliseconds | 
 | 
 | 
 | remote end initiates a flash hook and it is regenerated locally. | ||||||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | Default = 600 ms. | 
 | 
 | |||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | |||
| Detection | 
 | 
 | 
 | 
 | 
 | Not applicable to FXO. | |||||||||
| Range | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
| Caller ID fields | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | ||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | |||
| Caller ID Type | Bellcore | 
 | 
 | 
 | The MultiVOIP currently supports only one implementation of Caller | ||||||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | ID. That implementation is Bellcore type 1 with caller ID placed | |||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | between the first and second rings of the call. | |||||||
| Caller ID | Y/N | 
 | 
 | 
 | Caller ID information is a description of the remote calling party | ||||||||||
| enable | 
 | 
 | 
 | 
 | 
 | 
 | 
 | received by the called party. The description has three parts: name | |||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | of caller, phone number of caller, and time of call. The  | |||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | portion is always generated by the receiving MultiVOIP unit (on FXS | |||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | channel) based on its date and time setup. The forms of the ‘Caller | |||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | Name’ and ‘Caller Phone Number’ differ depending on the IP | |||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | transmission protocol used (H.323, SIP, or SPP) and upon entries in | |||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | the phonebook screens of the remote (CID generating) voip unit. The | |||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | CID Name and Number appearing on the phone at the terminating | |||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | FXS end will come either from a central office switch (showing a | |||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | PSTN phone number), or the phonebook of the remote (CID sending) | |||||||
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | voip unit. | 
 | 
 | 
 | ||||
The Caller ID feature has dependencies on both the telco central office and the MultiVOIP phone book. See discussion below.
| 47 | 
