BusinessPhone Communication Platform 7.0
Facilities

## Networking via Voice over IP lines

Definition
References to other documents
Use
Operation
General
Gatekeeper and Gateway Functions
Configuration examples
Traffic handling mode without gatekeeper assistance
BusinessPhone H.323 Networking towards MD110 (ELU-32 or ITG) and Webswitch
Traffic handling mode with gatekeeper assistance
Traffic handling mode with GK assistance, back-up and neighbourhood GKs, local breakout
Traffic handling mode with gatekeeper assistance and a public neighbourhood gatekeeper
Traffic handling mode with assistance of a public gatekeeper
Capacity
Limitation
Installation
Hardware Installation
Programming
Start of operation
Test the Installation
Maintenance
Equipment/Environment
IPU board
Networking via IP lines
Pre-requisites to the customer‘s LAN environment
Glossary

## Definition

The IPU board of ASB 150 02 R14 hosts a H.323 compliant trunk gateway and optional a Gatekeeper. With the function “Networking via Voice over IP lines”, ASB 150 02 provides an integrated trunk gateway functionality between circuit switched telephony and IP network.

Up to release 13 only proprietary IP networking was possible. Since release 14 additionally the Gatekeeper and the H.323 trunk gateway functionality based on the IP Unit (IPU) can be used to build up a standard H.323 network by using the existing customer LAN/WAN environment alternatively to leased lines.

The function “Networking via Voice over IP lines” is primarily based on the functionality of “Networking via digital lines”. From a networking functionality it does not matter whether the connection between the nodes is built up via leased lines or IP lines over the corporate network (Intranet).

Therefore this document does not focus on the whole networking functionality, it only describes the additional features on Voice over IP (VoIP) lines.

### References to other documents

Board description of the IPU see System description, (1551‑ASB 150 02 Uen)

Installation and Prerequisites see Installation instruction for ASB 150 02, (1531‑ASB 150 02 Uen)

Licensing of voice channels see Maintenance Instructions, (1541‑ASB 150 02 Uen)

Capacity upgrading of the IPU see Maintenance Instructions, (1541‑ASB 150 02 Uen)

First test after Installation and Programming see Start of Operation, (1537-ASB 150 02 Uen)

Firmware upgrading of the IPU see Maintenance Instructions, (1541‑ASB 150 02 Uen)

Technical Data - Voice over IP lines / IP Extensions see System overview, (1555‑ASB 150 02 Uen)

## Use

By using the existing data infrastructure the Gatekeeper / trunk IP-Gateway makes it possible to save costs especially for network configurations with nowadays parallel data networks as the amount of leased lines is minimized.

An ASB 150 02 configured with an IPU board, can act as end, transit, or gateway node in a mixed configuration with circuit switched lines.

## Operation

### General

#### Functionality

##### Voice functionality

Apart from the networking functionality based on QSIG and proprietary UUS signalling, the following additional functionality will be provided for voice calls.

- 4, 8 or 16 simultaneous bi-directional voice channels according to the used license.
- Address translation between telephony (PNR, route or trunk individual) and network number (IP number= IP address + TCP port).
- Definition of Voice Transmission Quality (VTQ) for VoIP calls on individual extension levels by using three different Voice-codecs: G.711, G723.1 and G.729 Annex A (with Annex B)
- To provide Quality of Service for Voice over IP calls “Type of Service “ (prioritization of voice packets) is supported in the IP header.
- DTMF handling
- Manual hand over to circuit switched lines in case of insufficient voice quality.
- Echo cancellation
- Comfort noise generation
- Silence suppression

##### IP functionality

From the IP world point of view, the following functionality is supported.

- IP address administration
  The IPU supports a static IP address, BootP or DHCP.
- Application selection through predefined ports:

- proprietary Networking with ASB 150 02 nodes
- 4 I/O ports
- standard H.323 Networking

- H.323 Gateway
- H.323 Gatekeeper

#### VoIP Networking packages

The function networking via Voice over IP lines is licensed from two perspectives - from Networking and from the IPU point of view.

##### Networking packages

The networking functions are licensed according the licensing concept. For details please refer to Facility Description - General. Basically following packages are available:

- Standard digital Networking Package
- Full digital Networking Package

with different variations from 2 to unlimited number of trunk individuals. For detailed information see document “Networking via digital lines (365/15534-ASB 150 02 Uen).

##### IPU packages

These packages focus on the amount of available bi-directional voice channels through the IP network.

For detailed description about the IPU licensing, refer to document Maintenance instructions, 1541‑ASB 150 02 Uen.

For a detailed description of the license ordering process see Order information ’BusinessPhone Communication platform’,113 62-11/ASB 150 02

### Gatekeeper and Gateway Functions

#### Gatekeeper

For this function the IPU hosted gatekeeper gets configured with the following information:

- Gatekeeper identifier
- Time to live interval length (for GW reregistration purposes)
- Heart beat interval length (for NGK availability checking purposes)
- Trusted H.323 Extension IP Address Range
- Gateways to be controlled by the GK (trusted H.323 trunk gateways)
- Neighborhood gatekeepers

##### Trusted Gateways

The gatekeeper must be able to decide if a gateway is allowed to register with it or not. Additionally, the gatekeeper decides about access level to be granted to a gateway. See Traffic handling mode with GK assistance, back-up and neighbourhood GKs, local breakout. For this purpose the following information will be configured manually:

- Gateway identification (RAS transport address)
- Access level (local only or local and network) - see command 2146 GW Network access

During the registration process the gatekeeper will complete its configuration with alias(es) for which the gateway is registered, as well as with the GW call signalling address, etc.

The gatekeeper keeps track of the gateway registration status. The time-to-live registration timer is engaged as heart beat mechanism, where the GW has to re-register. Otherwise it is assumed - after time out - that it is not registered - > no outgoing or incoming calls to GW. This mechanism can be switched off per gateway.

##### Neighborhood gatekeepers

The gatekeeper gets configured with information about its neighborhood. Symmetry is not required when programming neighborhood gatekeepers (i.e. if the GK1 is configured as neighborhood gatekeeper for GK2, it is not obligatory that the GK2 is programmed as neighborhood gatekeeper for GK1). The following information is configured manually:

- Primary neighborhood gatekeeper RAS transport address
- Primary neighborhood gatekeeper identifier
- Backup neighborhood gatekeeper RAS transport address - optional
- Backup neighborhood gatekeeper identifier - conditionally mandatory
- Alias address(es) for which the neighborhood gatekeeper is responsible

The gatekeeper will keep track of its neighborhood gatekeeper’s status and on the call base decide if the location requests will be sent to the primary or to the backup position.

##### Gatekeeper data persistence (non-volatile storage)

The gatekeeper does not store any trunk gateway related information neither in the onboard SRAM nor on the Compact Flash Disk.
Instead preserving actual information about gateways and neighborhood gatekeepers status and relying on this information after a restart, the gatekeeper is initiating a dynamic update of its data base whenever restarted. For this purpose all gateways are assumed unregistered and all neighborhood gatekeepers are assumed present on primary and on backup position (if applicable). The gateways will be registered at the latest with the next registration request at the time to live timer expiry (Command 2175 GK Time to live interval). Admission requests from not registered trusted gateways are rejected by the gatekeeper with the reason “callerNotRegistered”, so the gateway is informed that its registration is invalid and must be redone. It should be noticed here that the GK is aware of the configured RAS transport address of a trusted gateway. Although this address might be not valid any more, it is used for sending of ARJ message. Admission requests from non-trusted gateways are rejected by the gatekeeper without notice.

#### IPU hosted H.323 gateway

For this feature the IPU hosted H.323 gateway gets configured with the following information:

- Operational information
- Known cooperating gateways

##### Operational information

The IPU hosted H.323 gateway get manually configured the following operational information:

- Own call signalling port number
- Own password which is going to be registered at the gatekeeper as H.323 alias, and will be used for calling system authentication purposes.
- Availability check timer for pre-configured gateways (used in case that there is no gatekeeper)

Additional settings, if the GW is registered at a Gatekeeper

- Own RAS port number
- RAS transport address (i.e. IP address + port number) of the primary gatekeeper position, with which the gateway should register.
- RAS transport address (i.e. IP address + port number) of the backup gatekeeper position, with which the gateway should register whenever the primary gatekeeper position is not reachable. This entry is optional if the primary GK is defined, otherwise prohibited.
- NPI alias aliases the gateway should register with the active gatekeeper - this aliases are going to be registered at the gatekeeper as public or private party numbers.

##### Known cooperating gateways

The Network IP Address Data (also called ’1000’ node table) is used for configuration of gateways which are operated without consulting the gatekeeper. The ’1000 node’ table is contains the following information that are all related to the known cooperating gateway:

- Network node reference (usage of this information is described in Traffic handling mode without gatekeeper assistance).
- Protocol identifier.
- Network node address (Call signalling transport address).
- Network node password, which is used for cooperating node authentication purposes.

The IPU hosted gateway keeps track of the pre configured gateways availability.

#### Third party H.323 gateway

The third party H.323 gateway requires similar configuratioh as the IPU hosted H.323 trunk gateway (i.e. it also requires registration information or cooperating gateway information).

Nevertheless, some configuration related limitations may pop up in conjunction with a particular third party device, e.g:

- Most gateways do not support backup gatekeeper at all.
- Most gateway will not be able to configure call signalling or RAS port to values other than the “well known” ones.
- Some gateways are not able to operate both modes (with and without gatekeeper), or at least they can not operate both modes simultaneously.
- Other configuration limitations may occur in conjunction with a particular third party GW.

#### Traffic handling - general

Generally speaking the traffic is handled either with gatekeeper consulting or without it. It is possible to mix the two modes on the same gateway.

If the Network node reference has a value “0” it means the call will be made with gatekeeper assistance (the GW will perform RAS procedures towards the active gatekeeper) and all other values indicate a manually configured destination (points to the Network IP Address Data - also called ’1000’ node table) -

in this case the GW will not perform RAS procedures towards the gatekeeper. On the incoming side, if the calling gateway can be identified as a pre configured node (in the Network IP Address Data - also called ’1000’ node table) in the gateway the call will be handled without involving the gatekeeper, otherwise an admission request procedure towards the active gatekeeper will be started.

Regardless the operation mode (with or without gatekeeper assistance) and the cooperating system type (proprietary or other vendor PBX), the IPU hosted GW entity is always trying to detect an according to H.323 Annex M.1 tunnelled QSIG message within the H.225 message. If no Annex M is received -> basic call. Furthermore, the IPU hosted GW entity is always including the QSIG message (as specified in the H.323 standard - Annex M.1) in the H.225 message.

Note

Since Release 14 VoIP calls can be performed without using PNRs, which means, that a route number or a trunk individual number is dialed. In this case the call is built up always with gatekeeper assistance.

#### Traffic handling mode without gatekeeper assistance

In this mode the traffic will be handled without involving the gatekeeper entity - i.e. standard Q.931 and H.245 signalling procedures apply only (RAS procedures will not be employed).

The source system has configured call signalling address and optional password of the target system. Configuration symmetry is required, i.e. if the node A has configured information about node B, it is required for B to have configured information about A.

##### Outgoing call setup - H.225 (Q.931) and H.245

Standard Q.931 and H.245 signalling procedures are followed. In the originating gateway, a pre configured gateway matching the indicated Network node reference will be searched for. If there was no such gateways found, the call will be terminated towards the CSW with the reason “no route to destination”.

If at least one pre configured gateway with matching Network node reference was found, a call attempt towards the first found destination will be made. If this destination rejects the call due to any reason, another call attempt will be made to the next matching destination - until the call is accepted or the last matching destination has rejected the call (in which case the call will be terminated towards the CSW with the reason “no route to destination”). Pre configured destination password is inserted in the SETUP message as H.323 identifier in field “destinationAddress” in addition to the eventually existing dialled number, which is also contained in this field as a Public or PrivatePartyNumber - dependent on the type of number indicated by the CSW.

##### Incoming call setup - H.225 (Q.931) and H.245

The IPU hosted gateway on the incoming side does as first authenticate the calling system. For this purpose it is required for the caller to supply the calling party call signalling address or the destination system password or both. If the password is supplied it must match the configured gateway password. SETUP messages which do not supply password will be accepted and processed only if the originator can be identified as one of pre configured gateways (i.e. the calling party call signalling address must match the call signalling address of a pre configured gateway), all other call attempts will be rejected with the reason “securityDenied“. After successful authentication procedure, the gateway initiates call processing procedures. If the source system can not be identified as one of pre configured gateways (based on source transport address in “sourceAddress“ field of the SETUP message) the call handling procedures described in Call setup - incoming side will apply.
If the source system can be identified as one of the pre configured gateways, the call handling is continued without gatekeeper assistance (no RAS procedures will be performed for this call).

##### Call maintenance - H.225 (keep alive)

Standard Q.931 procedure STATUS ENQUIRY / STATUS is used as keep alive mechanism in the same way as it was introduced in ASB15002 R13 for the extension gateway feature.

##### Call clearing - H.225 (Q.931) and H.245

Standard Q.931 and H.245 signalling procedures for call clearing are followed - the gateway will not invoke disengage procedure for the calls being handled without consulting the gatekeeper.

#### Traffic handling mode with gatekeeper assistance

The IPU hosted gateway consults the gatekeeper whenever a call was initiated with Network node reference value “0” - standing for “Gatekeeper controlled”. Standard Q.931, H.245 and RAS signalling procedures will be employed in this mode.

##### Call setup - outgoing side

In the originating gateway, the admission request procedure is started towards the active gatekeeper. If the gatekeeper has rejected the admission request with the reason “incompleteAddress” the gateway waits for more digits. On reception of further dialled digits the gateways invokes again admission request procedure until the admission is confirmed or rejected with any other reason than “incompleteAddress” (in which case the call will be terminated towards the CSW with the reason “no route to destination”).
On admission confirm a call attempt towards the best suitable destination will be made.
If the target system rejects the call due to any reason, another call attempt will be made to the next matching destination as received in ACF - until the call is accepted or the last suitable destination has rejected the call (in which case the call will be terminated towards the CSW with the reason “no route to destination”).

The destination password which is contained in the ACF message in “aliasAddress” filed for primary destination and in the “alternateEndpoints” filed for the alternate destinations must be inserted in the related SETUP message as H.323 identifier in field “destinationAddress” in addition to the eventually existing dialled number, which is also contained in this field as a Public or PrivatePartyNumber - dependent on the type of number indicated by the CSW.

Further signalling flows follow the H.323 standard.

##### Call setup - incoming side

Basically the same rules can be applied as for incoming calls without gatekeeper assistance. As the call is gatekeeper assisted, usually the callers data do not appear in the “1000 node table”.

- If no Password is received from the caller - the call will be rejected unless:

- no Password is required (no own Password set by command 2198)
- caller is one of pre configured gateways - “1000 node table”

- If a Password is received from the caller it must comply with the own one. Otherwise the call will be rejected.

After successful password verification, the call handling is continued with an admission request procedure towards the active gatekeeper - made by called gateway.

If the gatekeeper rejects admission request due to any reason the call will be terminated towards the network. On admission confirm the call will continue by following the H.225 and H.245 standard.

##### Call maintenance

No RAS procedures suitable for active call phase (e.g. bandwidth control) are going to take place.

Standard Q.931 procedure STATUS ENQUIRY / STATUS is used as keep alive mechanism in the same way as it was introduced in ASB15002 R13 for the extension gateway feature.

##### Call clearing

The gateway will invoke disengage procedure towards the gatekeeper which has admitted the call.

Standard Q.931 and H.245 signalling procedures for call clearing are followed.

## Configuration examples

### Traffic handling mode without gatekeeper assistance

##### PNR Table

Private network Access Code | Destination PBX | NPI for private calling | 1 Route choice | 2 Route choice
|  | digit arrangement |  |  |  | digit arrangement |
route choice | NPI priv/pub called | remove | predigits | node ref. | route choice | NPI priv/pub called | remove | predigits | node ref.
Node 1:
4 | proprietary | RL0 | 10 | UNK, priv |  |  | 2 | 00 | UNK,pub | 1 | 811884 |
5 | other vendor PBX’ | RL0 | 10 | UNK, priv |  |  | 3 | 00 | UNK,pub | 1 | 0512420505 |
6 | other vendor PBX’ | RL0 | 10 | UNK, priv |  |  | 3 | 00 | UNK,pub | 1 | 0512420506 |
8445 | other vendor PBX’ | RL1 | 10 | UNK, priv |  |  | 3 | 00 | UNK,pub | 4 | 0512420505 |
8446 | other vendor PBX’ | RL1 | 10 | UNK, priv |  |  | 3 | 00 | UNK,pub | 4 | 0512420506 |
Node 2:
2 | proprietary | RL0 | 10 | UNK, priv |  |  | 1 | 00 | UNK,pub | 1 | 811002 |
3 | proprietary | RL0 | 10 | UNK, priv |  |  | 1 | 00 | UNK,pub | 1 | 811003 |
5 | other vendor PBX’ | RL0 | 10 | UNK, priv |  |  | 3 | 00 | UNK,pub | 1 | 0512420505 |
6 | other vendor PBX’ | RL0 | 10 | UNK, priv |  |  | 3 | 00 | UNK,pub | 1 | 0512420506 |
8445 | other vendor PBX’ | RL1 | 10 | UNK, priv |  |  | 3 | 00 | UNK,pub | 4 | 0512420505 |
8446 | other vendor PBX’ | RL1 | 10 | UNK, priv |  |  | 3 | 00 | UNK,pub | 4 | 0512420506 |

Note

If the value of command 9117 Node reference 1 is 0 then the call set up is made with gate keeper assistance. If the value of command 9117 Node reference 1 is 1 - 1000 the it points to command 2186 Network Node reference

Note

Use #... for route numbers and *...for trunk individual numbers

##### Network Node Table for Node 1 and Node 2

The Network Node Table (also called IP Reference table or ’1000’ node table) shows all known Gateways

Network Node reference | Signalling protocoll | Network IP address | Network Node Password
1 | 102 | 10.155.166.177:10040 |
2 | 102 | 10.133.144.155:10040 |
2 | 102 | 10.133.144.156:10040 |
3 | 102 | 10.188.199.122:10040 | IP400_01

Note

Command 2186 Network Node reference represents the nodes. As shown in the table above one of command 2186 Network Node reference (here 2) can have several entries, which means that node 2 has two IPUs. In this case the originating IPU (of node 1) searches for all valid entries in the Network Node Table, which reduces the PNR - configuration effort.

Note

If BusinessPhone makes an outgoing call then the call signalling Port number (Q.931) (part of command 2164 Network IP address) of the IP Reference table must correspond with the Q.931 - Port number of the destination PBX. In case, that the destination PBX is a BusinessPhone, then the Port number has to correspond with the value of command 2194 H.323 Trunk GW Q.931‑port of the destination BusinessPhone.

##### Gateway settings PBX Node 1:

Function | Command |  | IP address | Port
Own call signalling transport address - any free port number | 2152 IP address (own) |  | 10.155.166.177 |
2194 H.323 Trunk GW Q.931-port |  |  | 10040

Function | Command |  | IP address | Port
Own H.323 Trunk GW Password which is going to be registered at the gatekeeper as H.323 alias, and will be used for calling system authentication purposes. | 2198 H.323 Trunk GW Password | BP_250_A

Function | Command |  | time in seconds
Check towards a preconfigured gateway which is currently unavailable. | 2199 H.323 Trunk GW Keep alive timer |  | 300

Note

If BusinessPhone gets an incoming call then the received password is compared with the value of command 2198 H.323 Trunk GW Password. In case, that the calling PBX is a BusinessPhone, then the value of command 2187 Network Node Password has to correspond with the value of command 2198 H.323 Trunk GW Password of the gateway of the destination BusinessPhone.

### BusinessPhone H.323 Networking towards MD110 (ELU-32 or ITG) and Webswitch

Basically the same as in example Traffic handling mode without gatekeeper assistance, but some hints:

- MD110-System needs BC12.1 or higher
- BP-System needs CSW R14 or higher
- Networking License
- IPU needs Application Image R4D or newer
- put the IPU-trunks into one Route and configure the basic IPU data like usual
- Gatekeeper in BP is not used for Networking, since MD110 supports only GW<->GW connection, so this can remain disabled if not used somewhere else
- IMPORTANT: command 2194 (H.323 Trunk gateway Q.931-port) has to be modified and set to 1720
- IMPORTANT: since command 2185 (H.323 Extension Gateway Q.931-port) is set by default to 1720 this would be in conflict with the modified command 2194, so this command has to be changed to any other free port number, e.g. 17200
- within the Network IP-Address Data table (1000 node table) the other's node IP-trunk Gatway IP-Address have to be entered.

- IMPORTANT: Signaling Protocol - command 2163: 102
- IMPORTANT: Port Number - command 2164: 1720
- BusinessPhone will accept calls only from IP-addresses stated within this table; for outgoing calls the network node reference - command 2186 - has to be stated within the corresponding PNR

- PNR-Programming: command 9117 (Node Reference): see 1000 node table
- command 9110 (1-st route choice): enter the route-number
- command 9112 (Remove Digits): in the case of WS or ITG: node-number has to be removed to allow en-block sending
- command 9115 and command 9116: in case of WS or ITG: adapt called party number length to the actual number plan to allow en-block
- check in H.323 Trunk GW-control (button is found on bottom of 1000 node-table whether the peer trunk-GW is reachable.

### Traffic handling mode with gatekeeper assistance

(all nodes register at the Gatekeeper of ASB 150 02 Node A = centralized Gatekeeper)

Note

Since Release 14 VoIP calls can be performed without using PNRs, which means, that a route number or a trunk individual number is dialed. In this case the call is built up always with gatekeeper assistance.

##### PNR Table Node A

Private network Access Code | Destination PBX | NPI for private calling | 1 Route choice | 2 Route choice
|  | digit arrangement |  |  |  | digit arrangement |
route choice | NPI priv/pub called | remove | predigits | node ref. | route choice | NPI priv/pub called | remove | predigits | node ref.
842 | proprietary | RL1 | 10 | UNK, priv |  |  | 0 |  |  |  |  |
843 | proprietary | RL1 | 10 | UNK, priv |  |  | 0 |  |  |  |  |
851 | other vendor PBX’ | RL1 | 10 | UNK, priv |  |  | 0 | 00 | UNK,pub | 2 | 0512420505 |

Note

If the value of command 9117 Node reference 1 is 0 then the call set up is made with gate keeper assistance. If the value of command 9117 Node reference 1 is 1 - 1000 the it points to command 2186 Network Node reference

The Network Node Table (also called IP Reference table or ’1000’ node table) shows all known Gateways and is used for outgoing calls only - empty (for all ASB 150 02)

##### Node A Gateway A1

|  |  | IP address | Port
Own RAS transport address | 2152 IP address (own) | 10.155.166.177 |
2193 H.323 Trunk GW RAS-port |  | 10030
Own call signalling transport address - any free port number | 2152 IP address (own) | 10.155.166.177 |
2194 H.323 Trunk GW Q.931-port |  | 10040
RAS transport address of the primary gatekeeper position, with which the gateway should register | 2191 H.323 Trunk GW Primary GK IP-address | 10.155.166.177 |
2192 H.323 Trunk GW Primary GK RAS-port |  | 1719
RAS transport address of the backup gatekeeper position, with which the gateway should register whenever the primary gatekeeper position is not reachable. This entry is optional if the primary GK is defined, otherwise prohibited | 2195 H.323 Trunk GW Backup GK IP-address |  |
2196 H.323 Trunk GW Backup GK RAS-port |  |
Alias address(es) the gateway should register with the active gatekeeper - this aliases are going to be registered at the gatekeeper as public or private party numbers - used for incoming calls | 2189 NPI aliases for called number - incoming |  | Number Plan /Type of Number | Number
|  | 1 | Priv / RL1 | 841
|  | 2 |  |
|  | : |  |
|  | 30 |  |
Own H.323 Trunk GW Password which is going to be registered at the gatekeeper as H.323 alias, and will be used for calling system authentication purposes. | 2198 H.323 Trunk GW Password | BP_250_A1

Note

If BusinessPhone gets an incoming call then the received password is compared with the value of 2198 H.323 Trunk GW Password. In case, that the calling PBX is a BusinessPhone, then the value of 2187 Network Node Password has to correspond with the value of command 2198 H.323 Trunk GW Password of the gateway of the destination BusinessPhone.

##### Node A Gateway A2

|  |  | IP address | Port
Own RAS transport address | 2152 IP address (own) | 10.155.166.178 |
2193 H.323 Trunk GW RAS-port |  | 10030
Own call signalling transport address - any free port number | 2152 IP address (own) | 10.155.166.178 |
2194 H.323 Trunk GW Q.931-port |  | 10040
RAS transport address of the primary gatekeeper position, with which the gateway should register | 2191 H.323 Trunk GW Primary GK IP-address | 10.155.166.177 |
2192 H.323 Trunk GW Primary GK RAS-port |  | 1719
RAS transport address of the backup gatekeeper position, with which the gateway should register whenever the primary gatekeeper position is not reachable. This entry is optional if the primary GK is defined, otherwise prohibited | 2195 H.323 Trunk GW Backup GK IP-address |  |
2196 H.323 Trunk GW Backup GK RAS-port |  |
Alias address(es) the gateway should register with the active gatekeeper - this aliases are going to be registered at the gatekeeper as public or private party numbers - used for incoming calls | 2189 NPI aliases for called number - incoming |  | Number Plan /Type of Number | Number
|  | 1 | Priv / RL1 | 841
|  | 2 |  |
|  | : |  |
|  | 30 |  |
Own H.323 Trunk GW Password which is going to be registered at the gatekeeper as H.323 alias, and will be used for calling system authentication purposes. | 2198 H.323 Trunk GW Password | BP_250_A2

Note

If BusinessPhone gets an incoming call then the received password is compared with the value of 2198 H.323 Trunk GW Password. In case, that the calling PBX is a BusinessPhone, then the value of 2187 Network Node Password has to correspond with the value of command 2198 H.323 Trunk GW Password of the gateway of the destination BusinessPhone.

##### Mandatory Gatekeeper settings - Node A

| own Gatekeeper settings |  |
| Gatekeeper data |  |
| 2171 Gatekeeper activated? | Yes |
| 2172 Gatekeeper identifier | GK_A |
| 2175 GK Time to live interval | 10 minutes |
| 2178 GK NGK heart beat time interval | 10 minutes |
| Trusted Gateways |  |
| 2145 GW RAS transport address | 2146 GW Network access. It specifies if the GW is accessible only within the system where it reside or if it is also accessible from other systems (located via LRQ - Location ReQuest- procedure) | 2147 GW TTL enabled specifies if the GW is capable to support the TimeTo Live mechanisms as specified in H.323.
1 | 10.155.166.177:10030 | 1 - local and network access | enabled
2 | 10.155.166.178:10030 | 1 - local and network access | enabled
3 | 10.133.144.155:10030 | 1 - local and network access | enabled
4 | 10.144.155.166:10030 | 1 - local and network access | enabled
5 | 10.144.155.167:10030 | 1 - local and network access | enabled
6 | 10.188.199.122:0 | 1 - local and network access | enabled
: |  |  |
35 |  |  |

Note

The RAS Port number of an gatekeeper in ASB 150 02 R14 is fixed to 1719

### Traffic handling mode with GK assistance, back-up and neighbourhood GKs, local breakout

(each BusinessPhone has its own Gatekeeper)

Note

Since Release 14 VoIP calls can be performed without using PNRs, which means, that a route number or a trunk individual number is dialed. In this case the call is built up always with gatekeeper assistance.

##### PNR Table Node A

Private network Access Code | Destination PBX | NPI for private calling | 1 Route choice | 2 Route choice
|  | digit arrangement |  |  |  | digit arrangement |
route choice | NPI priv/pub called | remove | predigits | node ref. | route choice | NPI priv/pub called | remove | predigits | node ref.
842 | proprietary | RL1 | 10 | UNK, priv |  |  | 0 |  |  |  |  |
843 | proprietary | RL1 | 10 | UNK, priv |  |  | 0 |  |  |  |  |
900 | other vendor | UNK, pub | 10 | UNK, pub |  |  | 0 |  |  |  |  |

Note

If the value of command 9117 Node reference 1 is 0 then the call set up is made with gate keeper assistance. If the value of command 9117 Node reference 1 is 1 - 1000 the it points to command 2186 Network Node reference

The Network Node Table (also called IP Reference table or ’1000’ node table) shows all known Gateways - empty for all ASB 150 02

##### Gateway settings Node A

|  |  | IP address | Port
Own RAS transport address | 2152 IP address (own) | 10.155.166.177 |
2193 H.323 Trunk GW RAS-port |  | 10030
Own call signalling transport address - any free port number | 2152 IP address (own) | 10.155.166.177 |
2194 H.323 Trunk GW Q.931-port |  | 10040
RAS transport address of the primary gatekeeper position, with which the gateway should register | 2191 H.323 Trunk GW Primary GK IP-address | 10.155.166.177 |
2192 H.323 Trunk GW Primary GK RAS-port |  | 1719
RAS transport address of the backup gatekeeper position, with which the gateway should register whenever the primary gatekeeper position is not reachable. This entry is optional if the primary GK is defined, otherwise prohibited | 2195 H.323 Trunk GW Backup GK IP-address | 10.133.144.155 |
2196 H.323 Trunk GW Backup GK RAS-port |  | 1719

Alias address(es) the gateway should register with the active gatekeeper - this aliases are going to be registered at the gatekeeper as public or private party numbers - used for incoming calls | 2189 NPI aliases for called number - incoming |  | Number Plan /Type of Number | Number
|  | 1 | Priv/RL1 | 841
|  | 2 |  |
|  | : |  |
|  | 30 |  |
Own H.323 Trunk GW Password which is going to be registered at the gatekeeper as H.323 alias, and will be used for calling system authentication purposes. | 2198 H.323 Trunk GW Password | BP_250_A

Note

If BusinessPhone gets an incoming call then the received password is compared with the value of 2198 H.323 Trunk GW Password. In case, that the calling PBX is a BusinessPhone, then the value of 2187 Network Node Password has to correspond with the value of command 2198 H.323 Trunk GW Password of the gateway of the destination BusinessPhone.

##### Mandatory Gatekeeper settings - Node A

| own Gatekeeper settings |  |
| Gatekeeper data |  |
| 2171 Gatekeeper activated? | Yes |
| 2172 Gatekeeper identifier | GK_A |
| 2175 GK Time to live interval | 10 minutes |
| 2178 GK NGK heart beat time interval | 10 minutes |
| Trusted Gateways |  |
| 2145 GW RAS transport address | 2146 GW Network access . It specifies if the GW is accessible only within the system where it reside or if it is also accessible from other systems (located via LRQ - Location ReQuest- procedure) | 2147 GW TTL enabled specifies if the GW is capable to support the TimeTo Live mechanisms (light weight registrations) as specified in H.323.
1 | 10.155.166.177:10030 | 1 - local and network access | enabled
2 | 10.155.166.178:0 | 0 - local acces only - see Note | enabled
: |  |  |
35 |  |  |

Note

users of node B and node C can use the remote trunk for local breakout by dialling 810 and 900 - it is not possible to reach the remote trunk for local breakout by dialling 900, if command 2146 is set to local.

Note

The RAS Port number of an gatekeeper in ASB 150 02 R14 is fixed to 1719

##### Neighbourhood Gatekeeper (NGK) settings - Node A

NGK | GK Neighbourhood-GK settings |  |  |
1 | 2140 GK Primary NGK RAS transport address | 10.133.144.155:1719
2141 GK Primary NGK Identifier | GK_B
2142 GK Backup NGK RAS transport address |
2143 GK Backup NGK Identifier |
NGK alias table - command 2144 NPI aliases for called number - outgoing: For each of the in command 2140 GK Primary NGK RAS transport address specified NGKs a list of up to 21 NPI aliases, for which the NGK can provide support to locate the corresponding GW can be programmed. Each of them consists out of a 12 digit number and a corresponding type of number value. NGK alias table is used for outgoing calls in case that the gatekeeper can not identify the called destination |  | Number Plan /Type of Number | Number
1 | Priv / RL1 | 842
2 |  |
: |  |
21 |  |
2 | 2140 GK Primary NGK RAS transport address |  |  | 10.188.199.122:1719
2141 GK Primary NGK Identifier |  |  | GK_C
2142 GK Backup NGK RAS transport address |  |  |
2143 GK Backup NGK Identifier |  |  |
NGK alias table - command 2144 NPI aliases for called number - outgoing |  | Number Plan /Type of Number | Number
1 | Priv / RL1 | 843
: |  |
21 |  |
: |  |  |  |
25 |  |  |  |

### Traffic handling mode with gatekeeper assistance and a public neighbourhood gatekeeper

(ASB 150 02 does not even have an ISDN connection)

Due to lack of applied standardization, the example was verified with an ASB 150 02 simulating the public gatekeeper.

Note

Since Release 14 VoIP calls can be performed without using PNRs, which means, that a route number or a trunk individual number is dialed. In this case the call is built up always with gatekeeper assistance.

##### PNR Table

Private network Access Code | Destination PBX | NPI for private calling | 1 Route choice | 2 Route choice
|  | digit arrangement |  |  |  | digit arrangement |
route choice | NPI priv/pub called | remove | predigits | node ref. | route choice | NPI priv/pub called | remove | predigits | node ref.
0 | other vendor PBX’ | public, UNK | 10 | public, UNK |  |  | 0 |  |  |  |  |

Note

If the value of command 9117 Node reference 1 is 0 then the call set up is made with gate keeper assistance. If the value of command 9117 Node reference 1 is 1 - 1000 the it points to command 2186 Network Node reference

The Network Node Table (also called IP Reference table or ’1000’ node table) shows all known Gateways and is used for outgoing calls only - empty (for all ASB 150 02)

Gateway settings

|  |  | IP address | Port
Own RAS transport address | 2152 IP address (own) | 10.155.166.177 |
2193 H.323 Trunk GW RAS-port |  | 10030
Own call signalling transport address - any free port number | 2152 IP address (own) | 10.155.166.177 |
2194 H.323 Trunk GW Q.931-port |  | 10040
RAS transport address of the primary gatekeeper position, with which the gateway should register | 2191 H.323 Trunk GW Primary GK IP-address | 10.155.166.177 |
2192 H.323 Trunk GW Primary GK RAS-port |  | 1719
RAS transport address of the backup gatekeeper position, with which the gateway should register whenever the primary gatekeeper position is not reachable. This entry is optional if the primary GK is defined, otherwise prohibited | 2195 H.323 Trunk GW Backup GK IP-address |  |
2196 H.323 Trunk GW Backup GK RAS-port |  |
Alias address(es) the gateway should register with the active gatekeeper - this aliases are going to be registered at the gatekeeper as public or private party numbers - used for incoming calls | 2189 NPI aliases for called number - incoming |  | Number Plan /Type of Number | Number
|  | 1 | pub / national | 181100
|  | 2 |  |
|  | : |  |
|  | 30 |  |
Own H.323 Trunk GW Password which is going to be registered at the gatekeeper as H.323 alias, and will be used for calling system authentication purposes. | 2198 H.323 Trunk GW Password | BP_250_A

Note

If BusinessPhone gets an incoming call then the received password is compared with the value of 2198 H.323 Trunk GW Password. In case, that the calling PBX is a BusinessPhone, then the value of 2187 Network Node Password has to correspond with the value of command 2198 H.323 Trunk GW Password of the gateway of the destination BusinessPhone.

##### Mandatory Gatekeeper settings

| own Gatekeeper settings |  |
| Gatekeeper data |  |
| 2171 Gatekeeper activated? | Yes |
| 2172 Gatekeeper identifier | GK_A |
| 2175 GK Time to live interval | 10 minutes |
| 2178 GK NGK heart beat time interval | 10 minute |
| Trusted Gateways |  |
| 2145 GW RAS transport address | 2146 GW Network access . It specifies if the GW is accessible only within the system where it reside or if it is also accessible from other systems (located via LRQ - Location ReQuest- procedure) | 2147 GW TTL enabled specifies if the GW is capable to support the TimeTo Live mechanisms (light weight registrations) as specified in H.323.
1 | 10.155.166.177:10030 | 1 - local and network access | enabled
: |  |  |
35 |  |  |

Note

The RAS Port number of an gatekeeper in ASB 150 02 R14 is fixed to 1719

##### Neighbourhood Gatekeeper (NGK) settings

NGK | GK Neighbourhood-GK settings |  |  |
1 | 2140 GK Primary NGK RAS transport address |  |  | 10.133.144.155:1719
| 2141 GK Primary NGK Identifier |  |  | GK_public
| 2142 GK Backup NGK RAS transport address |  |  |
| 2143 GK Backup NGK Identifier |  |  |
| NGK alias table - command 2144 NPI aliases for called number - outgoing: For each of the in command 2140 GK Primary NGK RAS transport address specified NGKs a list of up to 21 NPI aliases, for which the NGK can provide support to locate the corresponding GW can be programmed. Each of them consists out of a 12 digit number and a corresponding type of number value. NGK alias table is used for outgoing calls in case that the gatekeeper can not identify the called destination |  | Number Plan /Type of Number | Number
| 1 | Pub / UNKk | 0
| 2 | Pub / UNK | 1
| : | : | :
| 10 | Pub / UNK | 9
| 21 |  |
2 |  |  |  |
: |  |  |  |
25 |  |  |  |

### Traffic handling mode with assistance of a public gatekeeper

(ASB 150 02 does not even have an ISDN connection)

Due to lack of applied standardization, the example was verified with an ASB 150 02 simulating the public gatekeeper.

Note

Since Release 14 VoIP calls can be performed without using PNRs, which means, that a route number or a trunk individual number is dialed. In this case the call is built up always with gatekeeper assistance.

##### PNR Table

Private network Access Code | Destination PBX | NPI for private calling | 1 Route choice | 2 Route choice
|  | digit arrangement |  |  |  | digit arrangement |
route choice | NPI priv/pub called | remove | predigits | node ref. | route choice | NPI priv/pub called | remove | predigits | node ref.
0 | other vendor PBX’ | public, UNK | 10 | public, UNK |  |  | 0 |  |  |  |  |

Note

If the value of command 9117 Node reference 1 is 0 then the call set up is made with gate keeper assistance. If the value of command 9117 Node reference 1 is 1 - 1000 the it points to command 2186 Network Node reference

The Network Node Table (also called IP Reference table or ’1000’ node table) shows all known Gateways and is used for outgoing calls only - empty (for all ASB 150 02)

##### Gateway settings

|  |  | IP address | Port
Own RAS transport address | 2152 IP address (own) | 10.155.166.177 |
2193 H.323 Trunk GW RAS-port |  | 10030
Own call signalling transport address - any free port number | 2152 IP address (own) | 10.155.166.177 |
2194 H.323 Trunk GW Q.931-port |  | 10040
RAS transport address of the primary gatekeeper position, with which the gateway should register | 2191 H.323 Trunk GW Primary GK IP-address | 10.133.144.155 |
2192 H.323 Trunk GW Primary GK RAS-port |  | 1719
Alias address(es) the gateway should register with the active gatekeeper - this aliases are going to be registered at the gatekeeper as public or private party numbers - used for incoming calls | 2189 NPI aliases for called number - incoming |  | Number Plan /Type of Number | Number
|  | 1 | national | 181100
|  | 2 |  |
|  | : |  |
|  | 30 |  |
Own H.323 Trunk GW Password which is going to be registered at the gatekeeper as H.323 alias, and will be used for calling system authentication purposes. | 2198 H.323 Trunk GW Password | BP_250_A

Note

If BusinessPhone gets an incoming call then the received password is compared with the value of 2198 H.323 Trunk GW Password. In case, that the calling PBX is a BusinessPhone, then the value of 2187 Network Node Password has to correspond with the value of command 2198 H.323 Trunk GW Password of the gateway of the destination BusinessPhone.

#### Other Functions

#### Voice channel handling

The voice channels on the IPU board are handled as individual IP trunks. Call control and traffic handling is based on ISDN BA links for QSIG trunks.

#### Voice Transmission Quality

##### Definition

In order to keep the required bandwidth for an VoIP call as low as possible, voice codes on the IPU are used to compress the used telephony bandwidth of 64kbit/s to a lower value. However, each compression causes a reduction in the voice transmission quality.

ASB 150 02 supports the following voice codecs.

- G.711 provides uncompressed voice transmission, and nearly the same voice quality as a circuit- switched line, however it occupies more bandwidth, which in case of heavy LAN traffic could result in some speech delays.
- G.729 Annex A (with Annex B) provides compressed voice transmission down to 8 kbit/s. The advantage of this codec is that despite of the compression the speech quality is on a very high level.
- G.723.1 provides compressed voice transmission down to 6,4 kbit/s and of course with some reductions in the voice quality, however it occupies less bandwidth.

##### Operation

ASB 150 02 is prepared for 4 different transmission quality levels, which can be defined on extension and trunk level for outgoing VoIP calls. Each level comprises a set of 5 voice codecs, whereby the access of the codecs depends on a different order of priority.

If an extension (command 0188) or a trunk (command 1040) sets up a VoIP call, the codec with the highest priority related to the dedicated codec set (VTQ table) will be requested in the own exchange. If the codec is available, it will be selected and a message is sent to the destination exchange informing about the selected and the alternative codecs. The destination exchange verifies the proposed codecs (in case of ASB 150 02 always Voice Transmission Quality Table 3) with the internal resources.

Proprietary IPGW protocol (101): The IPU confirms the first corresponding and available codec. Depending on the selected codec from the destination exchange, the originating exchange can continue call set up or reallocate a new codec (in the case another codec than the one with the first priority has been choosen from the destination exchange). If the reallocate fails, the call will be released and the ASB 150 02 automatically switches over to the alternative network.

H.323 protocol (102): The calling and the called IPU negotiate the codec. As soon as a codec is selected (can be done either from the calling or the called IPU), the originating exchange can continue call set-up.

Note

Even if codec G.711 A-Law and u-Law are not programmed by BMS, the codecs G.711 A-Law and u-Law are always present (standard H.323 - supplemented by IPU)

If the negotiation fails (e.g. not enough bandwidth), the call will be released and the ASB 150 02 automatically switches over to the alternative network.

Node 1: The calling IP trunk uses the VTQ-table received from the call originator, in the example above from the incoming trunk - see command 1040

Node 2: The called IP trunk uses always VTQ 3 - see command 2167 - to negotiate the codec usage in case of H.323. In Node 2 there is no further seizure of an outgoing IP trunk - so command 1040 of the incoming IP trunk is without any meaning.

#### Quality of Service

To provide Quality of Service for Voice over IP calls, the IPU supports “Type of Service” (prioritization of voice packets) in the IP header. It has to be verified whether this service is supported and programmed on the routers in the LAN environment. If the service is not supported by the routers, the voice packets will be sent transparently without any prioritization, which might result in some speech delay related to the current LAN traffic.To modify the Quality of service use the telnet-shell Command [i2cconfig]

#### DTMF digit handling

The DTMF digit handling is only applicable for suffix dialling in ’speech-state’ and the signalling over the IP network is done with DTMF information messages (outband signalling).

To ensure control of DTMF tone sending (inband signalling) from the end-users in the system (CSW) a DTMF receiver is always connected on the IPU during a established call. At detected DTMF tones are these translated to corresponding DTMF information messages before sent to the network side.

Received DTMF information messages from the network side are forwarded from IPU in to the system (CSW). CSW can in turn further send the DTMF digits either as information messages or as tone signals to the connected end-user, thus this is depending of the type of connected equipment/application.

#### Echo cancellation

On the IPU echo cancellers suppress the echo generated by trunks or extensions.

#### Silence suppression

In order to keep the required bandwidth during a conversation as low as possible, the noise level on each voice channel is supervised. If the noise falls below a certain limit, no further data packets will be sent to the destination site.

#### Comfort noise generation

If the silence suppression is active, the opposite conversation partner will hear silence, due to the fact that no data transmission is ongoing. In order to give conversation partner the impression that the connection is still active, a low noise will be generated on conversation partner‘s IPU.

#### Manual handover to circuit-switched lines in case of insufficient voice quality.

##### Definition

This proprietary feature allows the user to manually alter the VoIP speech path to a connected B-party. This may be relevant in cases when the Voice transmission quality over the IP Network is insufficient. The ongoing VoIP call to the B-party will be replaced by a new call using the next route choice in the PNR-table. During the handover, the connected B-party is reserved for the next incoming external call.

##### Operation

If the Voice transmission quality is insufficient, the calling user can switch over to an alternative connection by using the following procedure.

Originator (A-Party)

- predefined key
- or
- Initiate Inquiry + Dial *61*
  As soon as the new call is established, the previous call will automatically be released.

In order to switch over to an alternative connection, the following prerequisites have to be fulfilled, otherwise the function is denied and the user receives the congestion tone.

- an alternative PNR route must be available
- the originator must be allowed to use the function
- the current call is an IP call

Terminator (B-party)

After the handover has been initiated by the A-party, the called B-party (same as the one previously connected) is reserved for 20 seconds for the next incoming external call and is informed about the alternative routing by the display Message “SPEECH PATH REPLACEMENT”.
During reservation the B-party can cancel the reservation by pressing the CLEAR -key.

##### Limitation

A comparison of the A-party CLI (calling line identification) which is received via the original- and the alternative route is not possible in all cases (e.g. no or incomplete CLI is received via the alternative route). Therefore it cannot be used for a dedicated reservation of the B-party. It might happen, that another incoming external call is presented during the reservation.

The reservation and the information about the ’Handover of the IP call’ is only possible when the connected parties reside in a ASB150 02 and when USS 1,2,3 is available on the original path.

Operator telephones are not allowed to initiate a handover.

The reservation of group member extensions is not provided in case of ACD calls or PBX - group calls with parallel distribution.

## Capacity

- Multiple IPUs are supported, whereby the total capacity is limited to the maximum number of supported trunk lines as well as to the available free board positions.
- 12 (DSM1) or 16 bi-directional voice channels per DSM
- Maximum 16 voice channels per IPU

If an IPU is equipped with one DSM2 or two DSM1, then the very last position of a cabinet has to be used. If any other position has to be chosen or in case of multiple IPUs then the next right hand board position of the IPU must be left free.

ASB 150 02 R12 supports one IPU with maximum 8 voice channels only.

## Limitation

The VoIP lines are used to support “speech”, other “audio” calls e.g. modem or fax calls will be allowed but the transmission cannot be secured.

An IP link can neither be a synchronization source (master) for the system nor be synchronized against the network.

## Installation

### Hardware Installation

Please refer to the document Installation instruction for ASB 150 02, (1531- ASB 150 02 Uen).

### Programming

The following commands are only accessible via BMS:

#### Initiate Voice IP-Trunks

Enable the desired number of IP-trunks on every IPU.

Select the desired IPU and click on the IPU Licensing button in the ’Card information’ dialog, to open the IPU Licensing dialog.

The dialog shows the maximum number of licensed voice channels. These voice channels are used by the IP-Trunks and by the IP-Extensions.

Note

Any modification in this dialog, requires a restart of the IPU

#### Trunk Individuals

Define the desired number trunk individuals, which might be less or equal to the number of licensed voice channels.

Values: 0, 4, 8( default),12 and 16

#### IP-Extension Individuals

Not relevant for the Trunk Gateway

#### IP-Extension threshold

Not relevant for the Trunk Gateway

#### Voice over IP related settings

Note

Any modification of the commands 2152, 2171, 2172, 2193, 2194 require an IPU restart.

2141 |  | GK Primary NGK Identifier

2142 |  | GK Backup NGK RAS transport address

2143 |  | GK Backup NGK Identifier

2144 |  | NPI aliases for called number - outgoing

2145 |  | GW RAS transport address

2146 |  | GW Network access

2147 |  | GW TTL enabled

2149 |  | Suppress direct media routing

2151 |  | Preferred start-up protocol

2152 |  | IP address (own)

2153 |  | Gateway IP address

2154 |  | Subnet mask

2157 |  | First RTP-port number

2158 |  | Amount of RTP-sessions

2159 |  | MAC address (read only)

2160 |  | Network connection (read only)

2161 |  | Application

2162 |  | Port number

2163 |  | Signaling protocol

2164 |  | Network IP address

2165 |  | Voice Transmission Quality Table 1

2166 |  | Voice Transmission Quality Table 2

2167 |  | Voice Transmission Quality Table 3

2168 |  | Voice Transmission Quality Table 4

2169 |  | Optimal media packet size table

2175 |  | GK Time to live interval

2176 |  | Trusted H.323 Extension IP Address Range

2178 |  | GK NGK heart beat time interval

2179 |  | Periodic update time for network topology table

2180 |  | MOH and call progress tones to H.323 clients

2181 |  | H.323 Extension GK IP-address

2185 |  | H.323 Extension GW Q.931-port

2186 |  | Network Node reference

2187 |  | Network Node Password

2189 |  | NPI aliases for called number - incoming

2190 |  | H.323 Trunk GW Primary GK identifier

2191 |  | H.323 Trunk GW Primary GK IP-address

2192 |  | H.323 Trunk GW Primary GK RAS-port

2193 |  | H.323 Trunk GW RAS-port

2194 |  | H.323 Trunk GW Q.931-port

2195 |  | H.323 Trunk GW Backup GK IP-address

2196 |  | H.323 Trunk GW Backup GK RAS-port

2197 |  | H.323 Trunk GW Backup GK identifier

2198 |  | H.323 Trunk GW Password

2199 |  | H.323 Trunk GW Keep alive timer

1040 |  | Voice transmission quality

0187 |  | Expensive Route Warning Tone

0188 |  | Voice transmission quality

0190 |  | Switch to non-IP network allowed ?

#### Networking related commands

#### IP Link settings

1914 |  | Charging method

1915 |  | Provision of calling line identification

1918 |  | Provision of connected line identification

Following commands do not need to be modified, they can remain on the default value

1922 |  | Through connection after SETUP to net?

#### General settings

2084 |  | Type of network call handling

2085 |  | PBX protocol identifier

#### Programming of the “Own location code”

5431 |  | Create Own Location Code

5531 |  | Delete Own Location Code

5631 |  | Alter own location code

#### Programming of the Private Network Router (PNR)

5432 |  | Create Private Network Access Code

5532 |  | Delete Private Network Access Code

5632 |  | Change of Private Network Access Code

9101 |  | Destination PBX

9102 |  | Call back allowed?

9103 |  | NPI for private calling/connected line identification

9104 |  | Call class

9105 |  | NPI for public calling/connected line identification

6501 |  | Directory name

##### 1 st. route choice

9110 |  | 1st-route choice

9111 |  | NPI for private/public called number 1

9112 |  | Remove digits choice 1

9113 |  | Predigits choice 1

9114 |  | Travelling Class Mark 1

9115 |  | Complete called party NL 1

9116 |  | Subscriber called party NL 1

9117 |  | Node reference 1

##### 2nd route choice

9120 |  | 2nd-route choice

9121 |  | NPI for private/public called number 2

9122 |  | Remove digits choice 2

9123 |  | Predigits choice 2

9124 |  | Travelling Class Mark 2

9125 |  | Complete called party NL 2

9126 |  | Subscriber called party NL 2

9127 |  | Node reference 2

9128 |  | Send expensive route warning tone 2

##### 3rd route choice

9130 |  | 3-rd route choice

9131 |  | NPI for private/public called number 3

9132 |  | Remove digits choice 3

9133 |  | Predigits choice 3

9134 |  | Travelling Class Mark 3

9135 |  | Complete called party NL 3

9136 |  | Subscriber called party NL 3

9137 |  | Node reference 3

9138 |  | Send expensive route warning tone 3

##### 4th route choice

9140 |  | 4-th route choice

9141 |  | NPI for private/public called number 4

9142 |  | Remove digits choice 4

9143 |  | Predigits choice 4

9144 |  | Travelling Class Mark 4

9145 |  | Complete called party NL 4

9146 |  | Subscriber called party NL 4

9147 |  | Node reference 4

9148 |  | Send expensive route warning tone 4

#### PNR alternative Routing

1037 |  | PNR routes at incoming proprietary call

#### Basic call service – Travelling Class Mark

0171 |  | Travelling Class Mark

1035 |  | Travelling class mark (TCM)

#### Basic call service – Transit counter

2087 |  | Transit counter

#### Calling/Connected Line/Name identity

0170 |  | Number/name secrecy to corporate network?

2220 |  | Public number

2236 |  | Own country code

2237 |  | Own area code

1925 |  | Pre-digit removal for E.164 number plan with unknown typ of number

1926 |  | Pre-digit removal for E.164 number plan with international typ of number

1927 |  | Pre-digit removal for E.164 number plan with national typ of number

1928 |  | Pre-digit removal for E.164 number plan with network specific typ of number

1929 |  | Pre-digit removal for E.164 number plan with local directory typ of number

1930 |  | Pre-digit removal for private plan with unknown typ of number

1931 |  | Pre-digit removal for private plan with Level 1 regional type of number

1932 |  | Pre-digit removal for private plan with Level 2 regional type of number

1933 |  | Pre-digit removal for private plan with Level 3 regional type of number

1934 |  | Pre-digit removal for private plan with PTN specific type of number

1935 |  | Pre-digit removal for private plan with local type of number

1936 |  | Prefix calling number for E.164 number plan with international type of number

1937 |  | Prefix calling number for E.164 number plan with national type of number

1960 |  | Predigits to be removed for calling/connected number if TON=Unknown

1961 |  | Predigits to be removed for calling/connected number if TON=International

1962 |  | Predigits to be removed for calling/connected number if TON=National

1963 |  | Predigits to be removed for calling/connected number if TON=Network specific

1964 |  | Predigits to be removed for calling/connected number if TON=Local directory

#### Supplementary service UUS

2072 |  | MD110 release version of CN

Following commands do not need to be modified, they can remain on the default value

1940 |  | UUS services activation request

1942 |  | UU-information length for UUS service 1

1943 |  | UU-information in ALERT message

1949 |  | Carrier for proprietary services

#### Proprietary service – Call back

0177 |  | Initiate callback in corporate network?

9001 |  | Call setup version at network CBack

9002 |  | Active time for ’CBack on busy’ initPBX

9003 |  | Active time for ’CBack on free’ initPBX

9004 |  | Active time for ’CBack on busy’ superPBX

9005 |  | Active time for ’CBack on free’ superPBX

9006 |  | Maxringtime at the init extension for CBack calls

#### Proprietary service – Call diversion

0176 |  | Call diversion to corporate network allowed?

#### Proprietary service – Camp on

0108 |  | Camp-on allowed?

#### Proprietary service – Intrusion

0182 |  | Network intrusion?

#### Proprietary service – Message Waiting Indication

2023 |  | External voice mail directory number

2071 |  | ISID of external voice mailbox

#### Proprietary service – Rerouting

1110 |  | 1st, choice CN reroute position

1111 |  | 2nd, choice CN reroute position

1112 |  | 3rd, choice CN reroute position

2077 |  | First central answering position

2078 |  | Second central answering position

2079 |  | Third central answering position

### Start of operation

Read out the MAC-address of the IPU-board and provide this information to the LAN administrator for the IP address administration.
Set up the command 2151 Preferred start-up protocol according to the available services in the customer‘s LAN (DHCP,BOOTP or manual configured IP‑Address). Even if DHCP or BOOTP is configured, always the same IP address is needed (Contact the LAN administrator).

1. Configure the IPU
2. Connect the LAN cable

In case of choosing DHCP or BOOTP, it is required to invoke a board or system restart to request an IP address from the DHCP or BOOTP Server during start up.

### Test the Installation

Please refer to the document Start of Operation, (1537-ASB 150 02 Uen)

## Maintenance

For upgrading the firmware of the IPU as well as the licensed voice channels please refer to document Maintenance Instructions, (1541‑ASB 150 02 Uen), 1541‑ASB 150 02 Uen.

## Equipment/Environment

### IPU board

In order to use the function “Networking via Voice over IP lines” the system has to be equipped with an IPU board.

#### Licensed voice channels

The number of available voice channels on the IPU board will be defined by a license file.

For detailed description about the IPU licensing, refer to document Maintenance Instructions, (1541‑ASB 150 02 Uen), 1541‑ASB 150 02 Uen.

For a detailed description of the license ordering process see Order information BusinessPhone Communication platform 113 62‑11/ASB 150 02

#### Supported voice channels

Apart from the Compact Flash card, the IPU has to be equipped with DSM submodules. The number of supported voice channels depend on the type of the DSM module,

Article number | Function
ROA 219 5114/1 | DSM1 - 12 bi-directional voice channels independent of used voice codec.
ROA 219 5114/2 | DSM2 - 16 bi-directional voice channels, independent of used voice codec.
ROA 219 5114/3 | DSM3 - 16 bi-directional voice channels, independent of used voice codec.

### Networking via IP lines

In order to have access to the networking features, the proper licensing concept has to be used, see Facility Description – General (155 34-ASB 150 02 Uen), chapter ASB150 02 Licensing.

### Pre-requisites to the customer‘s LAN environment

In order to build up an ASB 150 02 network with VoIP lines, the following prerequisites have to be fulfilled.

- LAN environment
  ASB 150 02 provides an interface to an Ethernet 10BaseT/100BaseTX autosense LAN environment according to IEEE‑802.3 for half- and full duplex operation.
- TCP/IP (IP Version 4)
- Between the different network nodes which are to be connected via VoIP lines, a dedicated LAN/WAN connection (corporate Intranet) must exist. The system is not intended to be connected to the Internet.
- Bandwidth
  In order to avoid speech delay variation or conversation interruption (due to packet loss) the traffic situation on the LAN segments used for the VoIP lines should be analysed. Depending on the selected voice transmission quality, a certain bandwidth will be occupied per voice call (see following table).
- Quality of Service
  see Quality of Service

#### Codec / Bandwidth and packet size table

The following table includes parameters to optimize LAN configuration for VoIP operation (Ethernet packet size,.....)

Codec | Bandwidth | Packet duration | Packet size | Effective bandwidth per channel (one direction) | Comment
[kbit/s] | [ms] | [byte] | [kbits/s]
G.711 | 64,0 | 60 | 480 | 72,8 |
| 40 | 320 | 77,2 |
30 | 240 | 81,6 | default
20 | 160 | 90,4 |
G.723.1 | 5,3 | 120 | 80 | 9,7 |
| 90 | 60 | 11,2 |
60 | 40 | 14,1 |
30 | 20 | 22,9 | default
G.729A(B) | 8,0 | 120 | 120 | 12,4 |
| 90 | 90 | 13,9 |
60 | 60 | 16,8 |
30 | 30 | 25,6 | default
10 | 10 | 60,8 |

#### The following formulas have been used

- Packet size [byte] = Codec [kbit/s] * 125 * Packet duration [ms] / 1000
- Eff. bandwidth [kbit/s] = (Sum of all Headers [byte] * 8 / Packet duration [ms]) + Codec [kbit/s]
  For the table above: Overhead for each sent RTP package: 26 byte full Ethernet header + 20 byte IP header + 8 byte UDP header + 12 byte (minimum!) RTP header = 66 byte

Note

Codec G.711 offers the best speech quality. The bigger the packet size the longer the speech delay. Therefor the IPU limits the packet size to 480 byte.

## Glossary

Term | Explanation
10BaseT | LAN-standard for 10Mbit/s networks using twisted pair cabling (2pairs).
100BaseTX | LAN-standard for 100Mbit/s networks utilizing 2 pairs of data grade category 5 unshielded twisted pair (UTP) and shielded twisted pair (STP) cabling. 1 pair is used for the data transfer, the other pair is used for collision detection
ACF | Admission confirm
ARJ | Admission reject
CAT 5 | Category of a UTP LAN cable which is used for data transfer up to 100MHz (including 100BaseTX and ATM 155Mbps)
Codec | Compression/decompression. An overall term for the technology used in digital video and digital audio.
CN | Corporate Network
CNP | Coordinated Number Plan = closed number Plan
CSW | Central Soft Ware
Codec | Compression/decompression. An overall term for the technology used in digital video and digital audio.
DHCP | Dynamic Host Configuration Protocol. A TCP/IP protocol allowing the principal parameters of network devices (including IP addresses) to be configured by central DHCP servers. DHCP's purpose is to enable individual computers on an IP network to extract their configurations from a server (the 'DHCP server') or servers, in particular, servers that have no exact information about the individual computers until they request the information. The overall purpose of this protocol is to reduce the work necessary to administer a large IP network. The most significant piece of information distributed in this manner is the IP address.
DSM | Digital Signal Processing Module
Ethernet | A high-speed local area network (LAN), consisting of a cable technology and one or more sets of communication protocols. Developed by the Xerox Corporation, Ethernet is based on the IEEE 802.3 standard and uses the carrier sense multiple access with collision detection CSMA/CD) method to control access to the transmission medium.
GKDP | Gatekeeper Data Protocol. Proprietary protocol between ASB 150 02 Gatekeeper and Extension-Gateway
GK - Gatekeeper | An entity on the network that provides address translation and access control.
GW - Gateway | An entrance into and out of a communications network. Technically, a gateway is an electronic repeater device that intercepts and steers electrical signals from one network technology to another.
H.225 | ITU-T standard. Call signalling protocol and media stream packetization for multimedia communication system.
H.245 | ITU-T standard. Control protocol for multimedia communication.
H.323 | ITU-T standard. Packet-based multimedia communication system.
IP address | A unique, 32-bit number for a specific TCP/IP host on the Internet. Usually printed in decimal form (for example, 128.122.40.227)
IP Telephony | Technology that lets you make voice phone calls via gateways and standard telephones over the Internet or other packet networks using your PC.
LAN | Local Area Network. A LAN is a group of computers and other devices which are connected by a communications link, allowing the devices to interact on the shared network. It is confined to a small geographical area that does not use long-distance carriers, such as telephone connections. The area is usually limited by the cable length restrictions of the transportation media being used. LANs allow users to communicate and to share resources, such as hard disk storage and printers. A LAN is user-owned and does not run over leased lines, although it can have gateways to the PSTN or other private networks.
MAC address | A MAC address (also called an Ethernet address or an IEEE MAC address) is a number (typically written as twelve hexadecimal digits, 0 through 9 and A through F, or as six hexadecimal numbers separated by periods or colons, i.e. 0080002012ef, 0:80:0:2:20:ef) which uniquely identifies a computer that has an Ethernet interface. Unlike the IP number, it includes no indication of where your computer is located.
NGK | Neighbourhood Gatekeeper
QoS | Quality of Service. Guarantees network bandwidth and availability for applications.
Packet Transmission | Data files are split into packets and sent through the packet-switched network. Each packet may take a different route. The receiving side collects the packets, puts them into the correct order and reassembles the data file again.
PNR | Private Network Route
Q.931 | ITU-T standard. Describes call signalling.
RAS | ITU-T standard. Registration, Admission and Status .
subnet | A portion of a network that may be physically independent of another network portion, but both portions of the network share the same network address, and the portion is distinguished by a subnet number. The sub net number is a portion of the Internet address that designates a subnet. It is used for intranet routing but is ignored for Internet-routing purposes.
subnet mask | The bits of an IP address used for a subnetwork.
TCP | Transmission Control Protocol A connection-oriented protocol in Layer 4, that ensures that the data will arrive in the correct order. A connection is set between two communication devices to send and receive data. If this data is out of order, TCP reorders the information. If the expected information has not been received, it is requested again.
UDP | User Datagram Protocol. UDP acts parallel to TCP in Layer 4 and provides a connectionless datagram delivery service between IP host applications. Connectionless means that the protocol in the end device indicate whether data packets were lost on the way. UDP avoids the overhead of reliable data transfer mechanism by not protecting against datagram loss or duplication. For some applications, such precision is not necessary. Voice is an example. In a voice transmission, if one or two bits are wrong, the conversation will not become unintelligible. Even if an entire datagram is lost, the people at the ends can repeat themselves, and in that way recover the lost information. For these reasons, as well as the greater simplicity of UDP versus TCP, VoIP applications primarily use UDP.
UDP-pair | A UDP pair consist of two UDP one way channels whereby the first channel is used to transmit UDP packets with RTP-Header and voice and the second one is used for the RTCP protocol.
UTP | Unshielded twisted pair cable
Voice over Internet Protocol (VoIP) | Founded in 1996 by Cisco, Dialogic, Microsoft, US Robotics, VocalTec, and several other leading firms, VoIP is working to develop and promote standards for IP telephony. The VoIP efforts consist primarily of building on and complementing existing standards, like H.323.
WAN | Wide area network. A network which covers a larger geographical area than a LAN and where telecommunications links are implemented by the appropriate PTT(s).
Well known ports: | port 1718 - UDP - (unsecured) - broad cast / multicast messages
port 1719 - UDP - (unsecured)- RAS port
port 1718 - TCP (secured) - Q.931 port

Revision: D © Ericsson Enterprise 2005