Reference9:PBX/Objects/Gateway

From innovaphone wiki
Revision as of 14:47, 2 July 2012 by Ckl (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
There are also other versions of this article available: Reference | Reference7 | Reference9 (this version) | Reference11r2 | Reference12r2 | Reference13r1 | Reference13r2

The Gateway PBX object is used to register a gateway with the PBX. A Gateway object in contrast to a User object allows additional dialing digits to be sent. Also for incoming calls the incoming calling party number is passed on.

Gateway Object specific Configuration

Enblock Count
If this number of digits is dialed after the number of the Gateway object itself, the call is sent out as enblock call. This is useful to connect to gateway which are not capable of overlap receiving.
Enblock as Diverting No
If this checkmark is set, the called party number is transmitted as diverting leg2 information. As called party number the number of the gateway object is sent or no number if the Prefix checkmark is set. This is useful with Microsoft Exchange since this expects the number of the mailbox as diverting number.
Prefix
If this checkmark is set, the number of the Gateway object itself is removed from the called party number for outgoing calls and added to the calling party number for incoming calls
Domain
Route calls with matching domain part in the destination to this object.
Loop Detect
If checked outgoing calls are blocked if a call with identical source and destination addresses already exists.
Internal Destination
If this checkmark is set, all calls from devices registered at this object are marked as Internal (Numbering plan set to private). This is usefull if systems are registered to this object, which cannot send calls with the private numbering plan but should be regarded as internal (e.g. voicemail systems).

The device registering with a gateway object is normally expected to send local extension numbers as calling party number (i.e. extensions local to the PBX and 'behind' the gateways own number). However, if it sends these numbers as full numbers (that is, including the various prefixes such as county code, are code, trunk, etc.), these can be stripped using the next 3 fields:

International Match
If a call is received with an international calling party number, it is compared to this number. If there is a match (head match) this number is removed from the calling party number, so that only additional digits remain. If the calling party number does not match, it is removed completely. e.g. on an incoming call from a registration on this Gateway object the CGPN I49703173009123 will be mapped to 123.
National Match
Same as 'International Match' only for national calling party number. e.g. on an incoming call from a registration on this Gateway object the CGPN N703173009123 will be mapped to 123.
Subscriber Match
Same as 'International Match' only for subscriber calling party number. e.g. on an incoming call from a registration on this Gateway object with the CGPN S73009123 will be mapped to 123.

Multiple Gateway Registrations

If multiple Gateways are registered to a Gateway object, Gateways registered to the same device config are used round-robin. The gateways registered to different devices are used in the sequence of the configured devices.

Call Diversions

CFU
If configured a CFU is executed, so calls to the Gateways object are diverted.
CFB
A CFB is executed if a call is rejected with User Busy by remote destination
CFNR
A CFNR is executed if a call is rejected because of a local problem (no channel, no gatway registered, ...)