BusinessPhone Communication Platform 5.1
Facilities

## VoIP Gateway

Definition
Definitions & Abbreviations
References to other documents
Use
Operation
Programming Examples
Common part for all Examples
Example 1: 2 node network (point to point)
Example 2: 3 node network (point to multipoint)
Maintenance
Limitations
Equipment
RJ 45 connector of the BTU-D cable

## Definition

The primary intention of the 'VoIP Gateway' feature is that BusinessPhone 128i as gateway node supports MD110 for signalling conversion between circuit switched and packet (IP) switched networks.

### Definitions & Abbreviations

Abbreviation / Term | Definition
BP 128i | BusinessPhone with 5 board slot cabinet building practice, ASB150 02 (R13)
FECU | Feature Enabling Control Unit
GFP | Generic functional protocoll
IP | Internet Protocol
IP trunk | Trunk individual located on IPU
ISDN | Integrated Services Digital Network
MD110 | ASB501 04 (BC11)
Node | PBX in a private network environment
PBX | Private Branch Exchange (ASB 150 02)
QSIG | Q interface SIGnalling protocol, a uniform international corporate network signalling standard.
UUI | User-to-User Information
UUS | User-to-User Signalling
VoIP | Voice over IP
VoIPGW call | A call setup between Circuit Switched and Packet Switched

## 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

BusinessPhone Voice over IP Gateway offers full feature transparency. This means that the available networking features are independent from the network connection type (QSIG - leased lines or IP). So all networking features that are possible from MD110 to MD 110 via QSIG are also possible from MD110 - VoIPGW via IP to VoIPGW - MD110. All networking features that are possible from MD110 to BusinessPhone via QSIG are also possible from MD110 - VoIPGW via IP to BusinessPhone.

## Operation

The 'BusinessPhone VoIP Gateway' functionality is controlled with:

- new FECU index ’CPU-D4, FECU Full Networking unlimited number of interfaces without PBX functionality’ (KDUBS 130 13/11)
- new VoIP license on the IPU ’IPU gateway license 16 channel’ (FALBS 102 43/16).

Both the FECU licence and the VoIP licence must have a correct type before the ’VoIP Gateway' functionality is activated.

Only external originated or external terminated QSIG transit/gateway calls are allowed in the system. A VoIP gateway call is established between an IP trunk and a QSIG trunk or vice versa.

Internally originated and/or internally terminated calls will be blocked, except Maintenance calls to an internal destination and Operational access to the system is allowed.

The BusinessPhone VoIP gateway deactivates all other internal PBX functionality (user features). All programming will be allowed. Calls which are not allowed will be deactivated during the traffic execution phase and will cause a FECU warning.

A change to another FECU licence will block all IP trunks.

The full feature transparency mechanism allows full proprietary network support for MD 110 as for any other 3rd party PBX, where the networking protocol is based on QSIG. This applies also for standard QSIG services.

## Programming Examples

### Common part for all Examples

#### Possible layout of BP 128i

CPU-D4 + FECU /11 | BTU-D | IPU 1 | empty | IPU 2
#700 | #730 |  | #746
#729 | #745 |  | #761
| IP adress: |  | IP adress:
| 10.0.0.xxx |  | 10.0.0.xxx

#### Link Parameters:

The BTU-D must be set as Q-Interface:

Command | Value | Comment
1910 | 01000 | Position of BTU-D

The BTU-D must be the ’slave’ of MD110:

Command | Value | Comment
1912 | 1:Slave | MD110 must be the master

The BTU-D must be synchronized from MD110:

Command | Value | Comment
2601 | 01000 | Position of BTU-D

#### Individual trunk numbers

To avoid possible numbering conflicts all individual trunk numbers of the BTU-D should start with #700 (instead of 700). Individual trunk numbers of the IPU 1 should start with #730 (instead of 730). Individual trunk numbers of the IPU 2 should start with #746 (instead of 746).

Command | Value
5607 | #700

#### Route selection

All Q-SIG trunks should belong to route #10. All IP trunks should belong to route #11 and route #12. For details please refer to document Route selection (444/155 34-ASB 150 02 Uen)

##### Q-SIG (BTU-D) and IP (IPU 1 and IPU 2) routes:

Command | Q-SIG (BTU‑D) route: | IP (IPU 1 and IPU 2) routes
5401 | #10 | #11 | #12
3201 | #700 | #730 | #761
| #701 | #731 | #760
| : | : | :
| #729 | #761 | #730
3301 | No | No | No

Note

In all VoIP gateways the route members of route #11 are grouped ascending, the route members of route #12 are grouped descending for load regulation.

### Example 1: 2 node network (point to point)

#### Possible layout BP 128i A

CPU-D4 + FECU /11 | BTU-D | IPU 1 | empty | IPU 2
#700 | #730 |  | #746
#729 | #745 |  | #761
| IP adress: |  | IP adress:
| 10.0.0.155 |  | 10.0.0.156

#### Possible layout BP 128i B

CPU-D4 + FECU /11 | BTU-D | IPU 1 | empty | IPU 2
#700 | #730 |  | #746
#729 | #745 |  | #761
| IP adress: |  | IP adress:
| 10.0.0.165 |  | 10.0.0.166

The programming example refers to the drawing and the layout assumptions above.

#### Networking via Voice over IP Lines

##### BP 128i A

- PNR 113 uses route #10 (BTU-D)
- PNR 123 uses route #11 (IPU 1 and IPU 2)

##### BP 128i B

- PNR 113 uses route #12 (IPU 1 and IPU 2)
- PNR 123 uses route #10 (BTU-D)

For details please refer to document Networking via Voice over IP Lines (366/155 34-ASB 150 02 Uen)

#### PNR Table

If the PNR does not define the complete number then COMPLETE called party NL has to be set to the value of ’number of PNR digits +1’.

##### BP 128i A

Private network Access Code | Destination PBX | TON priv calling | 1 Route choice | 2 Route choice |
|  | remove digits | predigits | COMPLETE called party NL | IP ref. |  |  | remove digits | predigits | COMPLETE called party NL | IP ref.
route choice | TON priv/pub called | route choice | TON priv/pub called
113 | proprietary | PNP/UNK | #10 | PNP/UNK |  |  | 4 |  |  |  |  |  |  |
123 | proprietary | PNP/UNK | #11 | PNP/UNK |  |  | 4 | 3 | #11 | PNP/UNK |  |  | 4 | 4

##### BP 128i B

Private network Access Code | Destination PBX | TON priv calling | 1 Route choice | 2 Route choice
|  | remove digits | predigits | COMPLETE called party NL | IP ref. |  |  | remove digits | predigits | COMPLETE called party NL | IP ref.
route choice | TON priv/pub called | route choice | TON priv/pub called
113 | proprietary | PNP/UNK | #12 | PNP/UNK |  |  | 4 | 2 | #12 | PNP/UNK |  |  | 4 | 1
123 | proprietary | PNP/UNK | #10 | PNP/UNK |  |  | 4 |  |  |  |  |  |  |

#### IP Reference table

Node number | Signalling protocol | IP number (IP-Address: Port number)
1 | 101 | 10.0.0.155:7000
2 | 101 | 10.0.0.156:7000
3 | 101 | 10.0.0.165:7000
4 | 101 | 10.0.0.166:7000

Note

The IP reference table should be programmed in the same way for all VoIP gateways involved in this scenario.

### Example 2: 3 node network (point to multipoint)

#### Possible layout BP 128i A

CPU-D4 + FECU /11 | BTU-D | IPU 1 | empty | IPU 2
#700 | #730 |  | #746
#729 | #745 |  | #761
| IP adress: |  | IP adress:
| 10.0.0.155 |  | 10.0.0.156

#### Possible layout BP 128i B

CPU-D4 + FECU /11 | BTU-D | IPU 1 | empty | IPU 2
#700 | #730 |  | #746
#729 | #745 |  | #761
| IP adress: |  | IP adress:
| 10.0.0.165 |  | 10.0.0.166

#### Possible layout BP 128i C

CPU-D4 + FECU /11 | BTU-D | IPU 1 | empty | IPU 2
#700 | #730 |  | #746
#729 | #745 |  | #761
| IP adress: |  | IP adress:
| 10.0.0.175 |  | 10.0.0.176

The programming example refers to the drawing and the layout assumptions above.

#### Networking via Voice over IP Lines

Assumption:

#### BP 128i A

- PNR 113 uses route #10 (BTU-D)
- PNR 123 uses route #11 (IPU 1 and IPU 2)
- PNR 133 uses route #12 (IPU 1 and IPU 2)

#### BP 128i B

- PNR 113 uses route #12 (IPU 1 and IPU 2)
- PNR 123 uses route #10 (BTU-D)
- PNR 133 uses route #11 (IPU 1 and IPU 2)

#### BP 128i C

- PNR 113 uses route #11 (IPU 1 and IPU 2)
- PNR 123 uses route #12 (IPU 1 and IPU 2)
- PNR 133 uses route #10 (BTU-D)

For details please refer to document Networking via Voice over IP Lines (366/155 34-ASB 150 02 Uen)

#### PNR Table

If the PNR does not define the complete number then COMPLETE called party NL has to be set to the value of ’number of PNR digits +1’.

##### BP 128i A

Private network Access Code | Destination PBX | TON priv calling | 1 Route choice | 2 Route choice |
|  | remove digits | predigits | COMPLETE called party NL | IP ref. |  |  | remove digits | predigits | COMPLETE called party NL | IP ref.
route choice | TON priv/pub called | route choice | TON priv/pub called
113 | proprietary | PNP/UNK | #10 | PNP/UNK |  |  | 4 |  |  |  |  |  |  |
123 | proprietary | PNP/UNK | #11 | PNP/UNK |  |  | 4 | 3 | #11 | PNP/UNK |  |  | 4 | 4
133 | proprietary | PNP/UNK | #12 | PNP/UNK |  |  | 4 | 6 | #12 | PNP/UNK |  |  | 4 | 5

##### BP 128i B

Private network Access Code | Destination PBX | TON priv calling | 1 Route choice | 2 Route choice |
|  | remove digits | predigits | COMPLETE called party NL | IP ref. |  |  | remove digits | predigits | COMPLETE called party NL | IP ref.
route choice | TON priv/pub called | route choice | TON priv/pub called
113 | proprietary | PNP/UNK | #12 | PNP/UNK |  |  | 4 | 2 | #12 | PNP/UNK |  |  | 4 | 1
123 | proprietary | PNP/UNK | #10 | PNP/UNK |  |  | 4 |  |  |  |  |  |  |
133 | proprietary | PNP/UNK | #11 | PNP/UNK |  |  | 4 | 5 | #11 | PNP/UNK |  |  | 4 | 6

##### BP 128i C

Private network Access Code | Destination PBX | TON priv calling | 1 Route choice | 2 Route choice |
|  | remove digits | predigits | COMPLETE called party NL | IP ref. |  |  | remove digits | predigits | COMPLETE called party NL | IP ref.
route choice | TON priv/pub called | route choice | TON priv/pub called
113 | proprietary | PNP/UNK | #11 | PNP/UNK |  |  | 4 | 1 | #11 | PNP/UNK |  |  | 4 | 2
123 | proprietary | PNP/UNK | #12 | PNP/UNK |  |  | 4 | 4 | #12 | PNP/UNK |  |  | 4 | 3
133 | proprietary | PNP/UNK | #10 | PNP/UNK |  |  | 4 |  |  |  |  |  |  |

#### IP Reference table

Node number | Signalling protocol | IP number (IP-Address: Port number)
1 | 101 | 10.0.0.155:7000
2 | 101 | 10.0.0.156:7000
3 | 101 | 10.0.0.165:7000
4 | 101 | 10.0.0.166:7000
5 | 101 | 10.0.0.175:7000
6 | 101 | 10.0.0.176:7000

Note

The IP reference table should be programmed in the same way for all VoIP gateways involved in this scenario.

## Maintenance

Due to the fact that no modem or data call is possible via IP lines, access to the built-in modem is only possible via:

- a PC which is connected directly to the LAN
- a router
- a pure circuit switched connection

e.g. the Remote PC can access directly the built-in modem of BP 128i A (circuit switched connection via MD110_A) and BP 128i C (circuit switched connection via MD110_C). To access BP 128i B a connection to the LAN via the router is necessary.

## Limitations

Traffic capacity: The VoIP licensing/packaging will allow a maximum traffic capacity of 30 simultaneous VoIP gateway calls. This is a recommendation, not system controlled, to ensure an acceptable processing performance of the VoIP gateway calls.

## Equipment

The ordering number for the BP IP Gateway / 30 channels package is K-R13-IPGW. For details please refer to the ordering information 131 62‑13/ASB 150 02

### RJ 45 connector of the BTU-D cable

120 Ohm twisted pairs

pin | color | meaning
1 | Green | Incoming_A1
2 | Green/White | Incoming_B1
4 | Brown | Outgoing_A2
5 | Brown/White | Outgoing_B2

Revision: A © Ericsson Enterprise 2003