
| 
 | 
 | 
 | Chapter 3 – Related MultiVOIP Setup Parameters | |
| 
 | 
 | 
 | 
 | 
 | 
| 
 | 
 | 
 | Network Parameter Definitions (cont’d) | 
 | 
| 
 | 
 | 
 | 
 | 
 | 
| 
 | Field Name | Values | Description | 
 | 
| 
 | ARQ | 
 | 
 | |
| 
 | PreGrant | Y/N | Select to cause the Gatekeeper to send a pregrantedARQ permission in | 
 | 
| 
 | ALL | 
 | the RCF message for each endpoint that wishes to register. The | 
 | 
| 
 | 
 | 
 | pregranted ARQ permission is given to both makeCall and answerCall | 
 | 
| 
 | 
 | 
 | with routed mode. When an endpoint receives the permission, it may | 
 | 
| 
 | 
 | 
 | start the call with a Setup message or directly answer the call with a | 
 | 
| 
 | 
 | 
 | Connect message. | 
 | 
| 
 | 
 | 
 | 
 | 
 | 
| 
 | Line Hunting | 
 | 
 | |
| 
 | Information | 
 | 
 | |
| 
 | Call to Out- | Y/N | “Y” enables the sending of RAI messages. In a normal scenario, the | 
 | 
| 
 | 
 | gatekeeper will hunt among all the available endpoints that have been | 
 | |
| 
 | Supplier | 
 | registered using the same  | 
 | 
| 
 | 
 | 
 | gatekeeper about its resource availability using an RAI (Resource | 
 | 
| 
 | 
 | 
 | Available Indication) message. Upon receiving an RAI message from | 
 | 
| 
 | 
 | 
 | an endpoint, the gatekeeper would consider that endpoint as an  | 
 | 
| 
 | 
 | 
 | Service Supplier. The ‘Almost Out of Resources’ configuration would | 
 | 
| 
 | 
 | 
 | allow the gatekeeper to hunt such  | 
 | 
| 
 | 
 | 
 | for routing the calls. | 
 | 
| 
 | 
 | 
 | 
 | 
 | 
| 
 | Remove | Y/N | When selected, the gatekeeper will not convey in its outgoing setup | 
 | 
| 
 | H.245 Addr | 
 | message the H.245 address received in an incoming setup message. | 
 | 
| 
 | in Call Hunt | 
 | This prevents H.323 terminals from establishing a channel for a call | 
 | 
| 
 | 
 | 
 | only to refuse the call later. | 
 | 
| 
 | 
 | 
 | 
 | 
 | 
| 
 | Service | Y/N | When “Y” is selected, the gatekeeper will perform a Priority Based Line | 
 | 
| 
 | Configurable | 
 | Hunting among those destinations registered using the same tech- | 
 | 
| 
 | Properties | 
 | prefix. | 
 | 
| 
 | 
 | 
 | 
 | 
 | 
| 
 | Call Proceeding | This parameter group pertains to the gatekeeper’s handling of Q.931 | 
 | |
| 
 | 
 | 
 | 
 | |
| 
 | 
 | 
 | 
 | 
 | 
| 
 | Send | Y/N | Immediate return of  | 
 | 
| 
 | Immediately | 
 | When selected, the gatekeeper will send the Q.931 call  | 
 | 
| 
 | 
 | 
 | message to the originating endpoint immediately after receiving that | 
 | 
| 
 | 
 | 
 | endpoint’s call setup request. | 
 | 
| 
 | 
 | 
 | 
 | 
 | 
| 
 | With H.245 | Y/N | When enabled, gatekeeper supplementary services will remove the | 
 | 
| 
 | Addr | 
 | H.245 address from the outgoing setup in order to prevent early H.245 | 
 | 
| 
 | 
 | 
 | establishment to the call’s destination. This destination can be changed | 
 | 
| 
 | 
 | 
 | during Forward on Busy or during Forward on No Response (CFNR). | 
 | 
| 
 | 
 | 
 | 
 | 
 | 
| 
 | After | Y/N | Delayed return of  | 
 | 
| 
 | Overlapped | 
 | When selected (in routed mode), the gatekeeper will send a Q.931 call- | 
 | 
| 
 | Sending | 
 | proceeding message to the originating endpoint after it receives a | 
 | 
| 
 | 
 | 
 | return  | 
 | 
| 
 | 
 | 
 | 
 | 
 | 
| 60 | 
