Vood 100 200 Config

Configuration Manual
for the Vood 100 & 200 Series
This product is developed and manufactured by i3 micro technology.

Copyright © 2005 i3 micro technology
Vood 100 & 200 Configuration Manual
Version 6.0G
March 2005
Copyright© Notice
This document is confidential. The document and its contents may not be disclosed in any form
to a third party without written authorization from i3 micro technology ab.
Copyright© 2005 i3 micro technology ab, Sweden.
i3 micro technology ab
finlandsgatan 62
se – 164 74 kista, sweden
tel: +46 (0)8 506 38800
fax: +46 (0)8 506 38875
info@i3micro.com
www.i3micro.com
Vood 100 & 200 Configuration Manual Table of Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 About the Vood IRG/ITA Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
1.2 Target Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
1.3 Document Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
1.4 Support Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
1.5 Standard Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
2 Abbreviations and Conventions . . . . . . . . . . . . . . . . . . . . . . . 3

2.1 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
2.2 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
2.3 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
2.4 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
3 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4 Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5 Booting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.1 IRG/ITA Boot Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
5.1.1 Mandatory base parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
5.1.2 Common boot steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
5.2 Starting the Boot Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
5.3 Boot Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

5.3.1 Automatic booting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
When to use automatic booting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
The automatic boot sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
5.3.2 Semi-automatic booting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
When to use semi-automatic booting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Boot sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
5.3.3 Manual booting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Using factory installed parameters only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Telephone option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Web browser option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.4 Additional DHCP Server Configuration . . . . . . . . . . . . . . . . . . . . . . 14
6 LED Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.1 During Bootup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.2 During Normal Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7 Manual IRG/ITA Configuration . . . . . . . . . . . . . . . . . . . . . . . 16

7.1 Name and Password Configuration . . . . . . . . . . . . . . . . . . . . . . . . 16
7.2 Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

7.2.1 Using the web configuration utility . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.2.2 Accessing subscriber settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.2.3 Using the phone interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.3 Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

7.3.1 Factory reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
March 2005 Vood 100 & 200 Configuration Manual Version 6.0G i (viii)
7.3.2 Password reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.1 Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.2 Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

8.2.1 Dial Plan instructions do not apply to MGCP . . . . . . . . . . . . . . . . . . . . 20
8.2.2 Phone number configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Phone Number A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Phone Number B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.2.3 Call barring configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.2.4 Special number configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Enable Smart Dial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Minimum digits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Special Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Optional Prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.2.5 General prefix configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.2.6 Hotline and warmline configuration . . . . . . . . . . . . . . . . . . . . . . . . . 23
Hot Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Warm Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8.2.7 Busy Tone on hang-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8.3 Call Waiting with Call Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8.3.1 Call waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8.4 Inquiry Call with Call Hold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.5 Message Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.6 Three-Way Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.7 Click to Dial Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.8 Fast Re-Dial Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
8.9 Diversion Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

8.9.1 Diversion Services control via phone or web interface . . . . . . . . . . . . . . . 25
8.9.2 Call diversion .............. . . . . . . . . . . . . . . . . . . . . . . . 25
8.9.3 Call forwarding unconditional service . . . . . . . . . . . . . . . . . . . . . . . . 25
8.9.4 Call forwarding on busy service . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
8.9.5 Call forwarding on no reply service . . . . . . . . . . . . . . . . . . . . . . . . . 26
8.10 Answering Machine Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
8.10.1 Mail configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Mail address 1 (user parameter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Mail address 2 (user parameter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
SMTP address (user parameter). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
8.10.2 Administration of locally stored messages . . . . . . . . . . . . . . . . . . . . . 28
8.10.3 Recording a greeting message . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
8.10.4 Redirect to the answering machine . . . . . . . . . . . . . . . . . . . . . . . . . 28
8.11 Caller ID Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

8.11.1 DTMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
8.11.2 FSK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
8.12 Service Calling Line ID Restriction for Anonymous Calling . . . . . . . . . . 29
9 Protocol Specific Configuration. . . . . . . . . . . . . . . . . . . . . . . 30
10 Parameters and Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

10.1 Parameter Entry Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
March 2005 Vood 100 & 200 Configuration Manual Version 6.0G ii (viii)
10.2 Country Specific Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

10.2.1 Country ............ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
10.2.2 Sound volume configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
10.2.3 Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
10.2.4 Time zone configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
10.2.5 Polarity reversal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
10.3 Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
10.3.1 Use DHCP ......... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
10.3.2 EM address from DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
10.3.3 IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
10.3.4 Netmask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
10.3.5 IP gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
10.3.6 Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
10.3.7 EM address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
10.4 Switch Configuration for Vood 111 . . . . . . . . . . . . . . . . . . . . . . . . 35
10.4.1 Physical interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
10.4.2 VLAN/CoS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
VLAN user priority/Class of Service 802.1p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
VLAN CFI bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
VLAN ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

10.5.1 When Switch Configuration Entries Take Effect . ... . . . . . . . . . . . . . . . 36
10.5.2 Similarities between Vood 121 and Vood x42. .... . . . . . . . . . . . . . . . 36
10.5.4 VLAN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Enable VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Activate, ID and Port membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Tag Outgoing Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Untag Outgoing Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Ingress VLAN Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Discard Non PVID Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Default VLAN tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
10.5.5 QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Differentiated Services Ingress Classification: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
802.1p Ingress Classification: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
High/Low Priority Marking on Ingress Packets: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
10.5.6 Rate limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
10.5.7 Storm protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Port Enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Multicast Storm Enabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

10.6.2 VLAN/CoS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
VLAN user priority/Class of Service 802.1p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
VLAN CFI bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
VLAN ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
10.7 Switch Configuration for Vood x42 . . . . . . . . . . . . . . . . . . . . . . . . 41

Enable VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Activate, ID and Port membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Tag Outgoing Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Untag Outgoing Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Ingress VLAN Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Discard Non PVID Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Default VLAN tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
10.7.3 QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
March 2005 Vood 100 & 200 Configuration Manual Version 6.0G iii (viii)

High/Low Priority Marking on Ingress Packets: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
10.7.4 IGMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Query Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Uplink Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Leave Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
10.7.5 Rate limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
10.7.6 Storm protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Port Enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Multicast Storm Enabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

10.8.1 Physical interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
10.8.3 QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
No Ingress QoS Classification: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Combined 802.1p and Differentiation Services ingress Classification . . . . . . . . . . . . . . 53
10.8.4 IGMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Query Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Uplink Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
10.8.5 Rate limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Ingress Packet Rate Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Egress Packet Rate Limit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
10.8.6 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Physical interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
802.1q VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
10.9 DNS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

10.9.1 Use DNS from DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
10.9.2 DNS address 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
10.9.3 DNS address 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
10.10 NTP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

10.10.1 NTP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
10.11 SNMP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
10.11.1 SNMP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
10.12 NAT Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
10.12.1 MGCP, H.323, SIP and support for NAT configuration .. . . . . . . . . . . . . . 57
10.12.2 UPnP support ........................ . . . . . . . . . . . . . 58
10.12.3 STUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
10.12.4 Manual NAT Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
NAT address from SIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
NAT Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
NAT Bindings refresh timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
10.13 Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

10.13.1 Phone number configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
10.13.2 Call barring configuration.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
10.13.3 Special number configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Enable Smart Dial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Minimum digits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Special Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Optional Prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
10.13.4 General prefix configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
10.13.5 Hotline configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Warm Line Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
10.13.6 Busy tone on hang up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
March 2005 Vood 100 & 200 Configuration Manual Version 6.0G iv (viii)
10.14 Codec Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

10.14.1 Codec configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
10.14.2 G711 A codec options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
G711 A 64kb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
G711 A 64kb priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
G711 A 64kb preferred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
G711 A 64kb max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
G711 A 64kb DTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
10.14.3 G711 µ codec options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
G711 µ 64kb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
G711 µ 64kb priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
G711 µ 64kb preferred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
G711 µ 64kb max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
G711 µ 64kb DTX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
10.14.4 GSM codec options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
GSM priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
GSM preferred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
GSM max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
GSM DTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
10.14.5 G723 codec options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
G723 ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
G723 priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
G723 preferred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
G723 max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
G723 DTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
10.14.6 G729 codec options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
G729 ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
G729 priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
G729 preferred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
G729 max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
G729 DTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
10.14.7 T38 facsimile protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
10.14.8 Echo Cancellation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
11 SNMPv2 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
12 Additional EM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 72
12.1 EM-Configured Security Parameters . . . . . . . . . . . . . . . . . . . . . . . 72
12.1.1 EM-Configured parameters: user privileges . . . . . . . . . . . . . . . . . . . . . 72
Start webserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Enable root web pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Enable conf web pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
................. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Enable user web pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Enable analog Conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
12.1.2 EM-configured parameters: username and passwords . . . . . . . . . . . . . . . 73
Root pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Conf pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
User pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
12.2 EM-Configured Services Parameters . . . . . . . . . . . . . . . . . . . . . . . 74

12.2.1 EM-Configured parameters: enable call diversion..... . . . . . . . . . . . . 74
12.2.2 EM-Configured parameters: enable call waiting...... . . . . . . . . . . . . 74
12.2.3 EM-Configured parameters: enable answering machine . . . . . . . . . . . . . . 74
12.2.4 EM-Configured parameters: anonymous call . . . . . . . . . . . . . . . . . . . . 74
Allow anonymous call end user configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Enable always anonymous call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
12.2.5 EM-Configured parameters: Caller ID . . . . . . . . . . . . . . . . . . . . . . . . 75
Swap name and number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
12.2.6 EM-Configured parameters: supplementary service codes . . . . . . . . . . . . 75
Supplementary Service Code Transparent mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Multipart Transparent mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Dynamic service codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
March 2005 Vood 100 & 200 Configuration Manual Version 6.0G v (viii)
12.3 EM-Configured User Behavior Setting Parameters . . . . . . . . . . . . . . . 76

12.3.1 EM-Configured parameters: Called Party OnHook Timeout . . . . . . . . . . . . 76
12.3.2 EM-Configured parameters: optional incoming call prefix . . . . . . . . . . . . . 76
12.4 EM-Configured System Parameters . . . . . . . . . . . . . . . . . . . . . . . . 77
12.4.1 EM-Configured parameters: diffserv configuration . . . . . . . . . . . . . . . . . 77
12.4.2 EM-Configured parameters: EM server connection . . . . . . . . . . . . . . . . . 77
Vood terminals poll the Centre EM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Enable poll of EM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Start time for poll. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Poll interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Triple play services path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
12.4.3 EM-Configured parameters: IGMP . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Enable IGMP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
12.4.4 EM-Configured parameters: Jitter buffer control . . . . . . . . . . . . . . . . . . 78
Max Jitter buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
................... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Min Jitter buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Target Jitter Buffer Margin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
12.5 EM-Configured H323 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 79

12.5.1 EM-Configured parameters: Alternative Gatekeeper (CCS) . . . . . . . . . . . . 79
12.6 EM-Configured SIP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 79
12.6.1 EM-Configured parameters: device description . . . . . . . . . . . . . . . . . . . 79
12.6.2 EM-Configured parameters: ptime . . . . . . . . . . . . . . . . . . . . . . . . . . 79
12.7 EM-Configured MGCP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 79
12.7.1 EM-Config parameters: ignore call agent echo cancellation control . . . . . . . . 79
13 Known Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Appendix A:
Zone Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Appendix B:
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Appendix C:
H.323. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
2.1 Web Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
3 Phone Number Configuration . . . . . . . . . . . . . . . . . . . . . . . . 88

Phone Number A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Phone Number B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4 H.323 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.1 H.323 Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.1.1 CCS address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.1.2 Time to live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.1.3 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Enable authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Authentication key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Authentication Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.1.4 Enable fast start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
March 2005 Vood 100 & 200 Configuration Manual Version 6.0G vi (viii)
4.1.5 Enable H.245 Tunneling ..... . . . . . . . . . . . . . . . . . . . . . . . . . . 91

4.1.6 Disable RAS Channel ....... . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.1.7 Network Generated Dial Tone . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.1.8 RAS port range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.1.9 H225 port range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.1.10 H245 port range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.1.11 RTP port range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.1.12 H.323 ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.2 User Input Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
5 Known Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Appendix D:
SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
2.1 Web Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
3 Phone Number Configuration . . . . . . . . . . . . . . . . . . . . . . . . 95

Phone Number A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Phone Number B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4 SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4.1 SIP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4.1.1 Registration on/off channel A ... . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.1.2 Registration server channel A ... . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.1.3 Registration interval channel A . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.1.4 Outbound proxy channel A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.1.5 Registration on/off channel B . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4.1.6 Registration server channel B . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4.1.7 Registration interval channel B . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4.1.8 Outbound proxy channel B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.1.9 SIP port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.1.10 RTP port range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.1.11 Username . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.1.12 Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4.1.13 Transport Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4.1.14 SIP Telephone Syntax (RFC 2806) . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4.1.15 DTMF Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
RFC 2976 DTMF Generation (SIP INFO Method) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Dynamic Payload Type for DTMF, RFC 2833 (end of tone retransmission) . . . . . . . . . . . 99
5 Known Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Appendix E:
MGCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
2.1 Web Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
2.2 Analog Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
March 2005 Vood 100 & 200 Configuration Manual Version 6.0G vii (viii)
3 MGCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
3.1 MGCP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
3.1.1 Call agent ...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
3.1.2 End point name A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
3.1.3 End point name B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
3.1.4 Phone number A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
3.1.5 Phone number B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
3.1.6 AM trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
3.1.7 Gateway name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
3.1.8 Use NCS (on/off) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
3.1.9 Use DNS (on/off) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
3.1.10 Use NSE (on/off) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
3.1.11 Min interval (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
3.1.12 Max interval (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
3.1.13 Max attempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
3.1.14 Gateway port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
3.1.15 RTP port range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
3.2 Dynamic Payload Type for DTMF, RFC 2833 . . . . . . . . . . . . . . . . . 107
3.2.1 RFC 2833 (end of tone retransmission) . . . . . . . . . . . . . . . . . . . . . . 107
4 Known Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
March 2005 Vood 100 & 200 Configuration Manual Version 6.0G viii (viii)
Vood 100 & 200 Configuration Manual Introduction
1 Introduction
1.1 About the Vood IRG/ITA Unit

The i3 micro Vood IRG/ITA unit is a terminal adaptor that connects a standard analog
touch-tone telephone to IP-based networks. The unit is designed to be installed on
the customer premises.
1.2 Target Groups

This document is intended for:
Broadband operators and network administrators who offer network connectiv-

ity to the i3 Vood products IP Residential Gateways (IRGs) and Terminal Adap-
tors (ITAs).
Service providers who offer Voice over IP (VoIP) services to end-users.
It should be useful for:
Assisting with network design for a Vood installation
Vood terminal parameter entry in the i3 Centre EM
The technicians using this manual should be familiar with VoIP terminology and IP
networks.
1.3 Document Scope

This document is valid for the following Vood products:
Vood 111
Vood 121
Vood 122 (End of life, no longer supported)
Vood x42 (Vood 142 and Vood 242 share the same software versions)
Vood 292
1.4 Support Information

Should support be needed, please provide the following data for the IRG/ITA unit:
Software Version
Terminal Serial Number
MAC Address
IP Address
March 2005 Vood 100 & 200 Configuration Manual Version 6.0G 1 (108)
This data can be accessed on the Information menu from a web interface. For instruc-
tions about how to do this, see “Using the web configuration utility” on page 16.
1.5 Standard Equipment

Some i3 clients have arranged with i3 to have their i3 products adapted to their
unique needs, such that the hardware or software they receive from i3 will have non-
standard features. This manual has been written for standard i3 equipment and soft-
ware. If your company has unique (non-standard) i3 hardware or software that
requires additional (unique) instructions, these will be provided separately.
Contact i3 directly if you have questions about instructions for non-standard features.
Vood 100 & 200 Configuration Manual Abbreviations and Conventions
2 Abbreviations and Conventions
2.1 Abbreviations
Acronym Meaning
CCS Call Control Server.
CFI Canonical Format Indicator.
DHCP Dynamic Host Configuration Protocol, RFC 2131, RFC 1541.
DNS Domain Name System.
EM Element Manager.
FQDN Fully Qualified Domain Name.
HTTP HyperText Transfer Protocol, RFC 2616.
HTTP Server In this context equal to i3 Centre EM, which contains the Vood
management application and an HTTP server.
IGMP Internet Group Management Protocol.
IRG IP Residential Gateway
ITA IP Terminal Adapter
IVR Interactive Voice Response.
LAN Local Area Network.
MGCP Media Gateway Control Protocol.
NAT Network Address Translation.
NTP Network Time Protocol, RFC 1305.
RTP Real Time Protocol, RFC 1889.
SIP Session Initiation Protocol.
Vood 100 & 200 Configuration Manual Abbreviations and Conventions
Acronym Meaning
SNMPv2 Simple Network Management Protocol, version 2.
STUN Simple Traversal of UDP through NATs.
TFTP Trivial File Transfer Protocol, RFC 1350.
TFTP Server In this context equal to i3 Centre EM, which contains the Vood
management application and a TFTP server.
UDP User Datagram Protocol.
UPnP Universal Plug and Play.
VoIP Voice over IP.
WAN Wide Area Network.
2.2 Conventions
Bold: buttons on a web page, or important items.
<angle brackets >: name of a specific web page.
Italic: parameter names, menu items.
The ‘dotted quad’ format xxx.xxx.xxx.xxx for IP addresses should be inter-

preted as follows: ‘xxx’ is a decimal integer, 0 through 255.
2.3 References
1) Vood Operator’s manual.
2) IRG/ITA Quick Reference Guide.
3) Vood IRG/ITA User Guide.
2.4 Terminology
Terms for telephony features may vary according to geographical region. Some of
these include:
“R” Button — “Flash” Button
Call Barring — Call Blocking
Congestion Tone — Fast Busy
Vood 100 & 200 Configuration Manual Prerequisites
3 Prerequisites
Before you proceed, you must connect the adaptor to a network (Ethernet) and to its
voltage adaptor. If necessary, refer to Ref. [2], ”IRG/ITA Quick Reference Guide.” for
information about how to do this.
4 Network Elements
The network elements are shown in “Fig. 1” on page 5 below. Elements with an aster-
isk (*) are crucial to a successful booting and operation of the IRG/ITA unit.
DHCP server EM* and DNS server NTP CCS*/SIP

HTTP/TFTP* server Proxy*
server
Fig. 1 The network elements
The IRG/ITA unit uses one or several of these elements to obtain the parameters nec-
essary for booting and operation:
The DHCP server is used for obtaining the unit’s IP address, the IP gateway
address and the netmask.
The Element Manager (EM) supplies the unit with software and a parameter
set, see “Protocol Specific Configuration” on page 30.
The Domain Name System (DNS) server supplies the translation of domain
names into IP addresses.
The Network Time Protocol (NTP) server is used for time synchronization.
The CCS (Call Control Server) is H.323 specific and is used for registering the
unit in the network and for mapping telephone numbers to IP addresses when
setting up calls. Another name for this server is Gatekeeper. For SIP (Session
Initiation Protocol), this server corresponds to the SIP Proxy.
As mentioned above, not all of these servers must be present for the IRG/ITA to be
able to operate; their roles are explained in “Boot Scenarios” on page 8.
Vood 100 & 200 Configuration Manual Booting
5 Booting
Section 5.2 describes the generic booting procedure. Boot scenarios are described in
section 5.3.
5.1 IRG/ITA Boot Steps
5.1.1 Mandatory base parameters

As a minimum, the following base parameters must to be known to the IRG/ITA unit
for the unit to establish contact with the network:
IP address
Network route address (IP Gateway)
Netmask.
There are several ways these base parameters can be acquired, resulting in various
boot scenarios, see “Boot Scenarios” on page 8.
5.1.2 Common boot steps

All scenarios have the steps shown in “Fig. 2” on page 6 in common.
1. 4.
Perform Start voice and
hardware test config. application
2. 5.
Configure unit’s Register with
IP stack the
CCS/SIP Proxy
3.
Contact
EM, get configu-
ration parame-
ters, and update
software, if nec-
essary
Fig. 2 IRG/ITA common boot steps
5.2 Starting the Boot Procedure

To start the boot procedure, connect the IRG/ITA unit’s voltage adaptor to a suitable
power source. The unit has no on/off switch.
1) Hardware test: The boot procedure starts with extensive tests of the unit’s
hardware. If the hardware tests are passed, the Linux kernel boots. The LEDs
indicate this by going dark. (See note below.)
2) Configure IP stack: During this step, the IP stack of the unit is configured,
either by the DHCP server or by internal default settings. The IP stack param-
eters are: the unit’s IP address, the default IP Gateway address, and the net-
mask.
The unit’s DHCP client starts and the LEDs flash twice repeatedly in a slow
fashion.
– If a connection to a DHCP server is established, the IP stack is configured

by the DHCP server, and the next stage of the boot procedure is entered.
– If a connection to a DHCP server cannot be established within one

minute, the IP stack is configured according to internal default settings.
See sections 10.3.3 on page 33 through 10.3.5 on page 34.
3) Contact EM: The unit establishes contact with the EM to download the unit’s
parameter set, see “Protocol Specific Configuration” on page 30, and to
update the software, if necessary.
The IP address of the EM is obtained either from the DHCP communication

session, or from information obtained from the network service provider.
If contact is established with the EM, the unit checks if the internal software
is up to date or not:
– If the software is correct, the voice application and configuration appli-

cation start.
– If the unit needs a software update, the new software is downloaded.

When the software update procedure is finished, the unit reboots auto-
matically.
During the software update procedure, the LEDs flash three times repeatedly
in a slow fashion.
4) Start voice service: As the voice and configuration application start, the
LEDs flash four times repeatedly in a slow fashion until the voice application
has been properly configured and the voice service is fully functional.
5) Registration: The unit sends registration data to the CCS/SIP Proxy. This
makes the unit an endpoint in the IP network. When the voice service is func-
tional, the LEDs of the unit show a steady light. The boot procedure is then
complete.
Note: Step 1: If hardware faults occur, the boot procedure is terminated. The unit
indicates this by continuously flashing its front LEDs. See Appendix B: “Trouble-
shooting” on page 87.
5.3 Boot Scenarios

This section outlines the three major boot scenarios:
Automatic booting
Semi-automatic booting
Manual booting
In the boot sequence descriptions below, the hardware test is always carried out,
though not mentioned in the text.
5.3.1 Automatic booting

Automatic booting is the easiest way for the end-user to put the IRG/ITA unit into
operation, and should be the preferred boot method whenever possible.
Also, since very little end-user intervention is required, troubleshooting will be kept
at a minimum.
When to use automatic booting
Automatic booting can be used when the service provider owns or controls the DHCP
server, see “Fig. 3” on page 9 below. The total booting time will be around five min-
utes or less.
Prerequisites
The DHCP server’s Next Server field (also known as a the siaddr field) has been
configured with the Element Manager IP address. See “Additional DHCP Server
Configuration” on page 14
The Element Manager (EM) has the IRG/ITA production file data.
The EM has the relevant data — The terminal is configured with correct SW and
configuration.
The Call Control Server (CCS)/SIP Proxy has the user account data.
The automatic boot sequence
1) When booting, the IRG/ITA contacts the DHCP server, which configures the
parameters of the unit’s IP stack. The LEDs at the unit’s front flash twice
repeatedly in a slow fashion.
2) Optional — The DHCP server can provide the terminal with VLAN information.
A new DHCP request is then sent using the obtained VLAN.
3) The DHCP server provides the unit with the IP address of the Centre EM.
4) The unit checks that it has the latest version of all software and downloads
updates from the EM, if needed. In such cases, the unit reboots automatically.
5) The unit fetches its configuration parameters from the EM. The parameters
are described in “Protocol Specific Configuration” on page 30.
6) As the voice and configuration application start, the LEDs flash four times
repeatedly in a slow fashion until the voice application has been properly con-
figured and the voice service is fully functional.
7) The unit registers with the CCS/SIP Proxy, so that the CCS/SIP Proxy can
authorize the unit and set it up as an IP endpoint in the network. When the
voice service is functional, the LEDs of the unit show a steady light.
The unit is now fully operational.
DHCP server EM* and HTTP/TFTP* CCS*/SIP Proxy*

server
IP services provider
IP
End-user
IRG/ITA unit
Fig. 3 The automatic booting scenario
5.3.2 Semi-automatic booting

In the semi-automatic booting scenario, the DHCP server does not belong to the net-
work service provider’s network. Instead, the provider has obtained the DHCP ser-
vices needed from a third-party provider. This complicates the boot sequence, since
the IRG/ITA unit then cannot get the IP address of the EM from the DHCP server.
Instead, the end-user must configure the unit with the EM’s IP address. Once the
EM’s IP address has been entered, the information will be stored and used for subse-
quent bootups. (The end-user needs to do this only once.)
When to use semi-automatic booting
Semi-automatic booting can be used when the network service provider does not own
or control the DHCP server, see “Fig. 4” on page 11 below.
Boot sequence
When the Vood IRG/ITA unit is powered on for the first time, it contacts the DHCP
server, which configures the parameters of the unit’s IP stack. When this first-time
bootup is completed it will not yet have contacted the EM.
The end-user must now provide the unit with the EM’s IP address so that the next unit
bootup will contact the EM.
This can be accomplished in one of three different ways:
Enter the EM address by using a telephone. The network service provider will
have supplied the end-user with the EM address in ‘dotted quad’
(xxx.xxx.xxx.xxx) format.
Enter the EM address by using a web browser. The network service provider
will have supplied the end-user with the EM address in ‘dotted quad’
(xxx.xxx.xxx.xxx) and/or FQDN format.
The end user enters the “operator specific code” by using a telephone. The net-
work service provider will have supplied the end-user with this “operator spe-
cific code”.
Using the telephone option:
This option requires that you use the ‘dotted quad’ format.
1) Power on the Vood IRG/ITA unit.
2) Connect a telephone to the unit.
3) Enter the EM IP address as:
Where each of the four ‘xxx’ represents a part of the IP address in ‘dotted
quad’ format. (Do not enter leading zeros.) See “EM address” on page 34
4) Reboot (power-cycle) the unit.
Instruction end
Using the web browser option:
1) Power on the Vood IRG/ITA unit.
3) Check the unit’s IP address, typing: and write it down.See “IP

address” on page 33.
4) Connect a PC to a proper port of the unit and start a web browser.
5) In the browser address field, type the unit’s <IP address>/conf and press
Enter.
6) A login dialog box opens; log in as admin (User ID and Password are case sen-
sitive):
7) User ID: Conf
8) Password: admin
9) The start page opens.
10) Click the Configuration button and configure the unit with the EM IP
address, and click the Save button to save the settings.
11) Click the Activate button to reboot (power-cycle) the unit.
Instruction end
Using the operator specific code option:
This option requires that the operator has received a specific code from i3micro and
supplied it to the end user.
2) Enter the operator specific code as: . Where the

four ‘xxxx’ represents the operator specific code.
3) The unit reboots itself (power-cycle).
Instruction end
Once the EM ‘s IP address has been entered, the unit has all the data it needs to
carry out a complete boot sequence. When rebooting the unit, the boot scheme is
almost identical to that of the automatic booting, see “The automatic boot
sequence” on page 8. The only difference is that the unit does not get the EM IP
address from the DHCP server, but from the user setting described above.
DHCP server EM* and HTTP/TFTP* CCS*/SIP Proxy*
IP
End-user
IRG/ITA unit
Fig. 4 The semi-automatic booting scenario
5.3.3 Manual booting

In the manual booting scenario, there is no DHCP server at all. This scenario splits
into two distinct cases:
1) The network service provider has preconfigured the IRG/ITA unit. The boot
sequence is then the same as for the automatic sequence; see “The automatic
boot sequence” on page 8.
2) The unit is equipped with factory installed default parameters only. This case
is described next:
Using factory installed parameters only
Since there is no DHCP, the unit lacks relevant values for the IP configuration (its own
IP address, the network mask, the IP address of the default IP Gateway and the
address of the EM).
The end-user must provide the unit with these values, either using a telephone or a
web browser. In either case, the network service provider has supplied the end-user
with the required data, where the IP addresses are in ‘dotted quad’
(xxx.xxx.xxx.xxx) and FQDN format. In some cases, the end-user has to provide
DNS and NTP addresses as well.
Telephone option
This option requires that you use the ‘dotted quad’ format.
To set the parameters:
2) Enter the terminal IP address (using the supplied value) as:

where each of
the four ‘xxx’ represents a part of the IP address in ‘dotted quad’ format.
3) Enter the netmask (using the supplied value) as:
4) Enter the default gateway IP address (using the supplied value) as:
5) Enter the EM IP address (using the supplied value) as:
6) If required, enter the DNS and NTP addresses. (Supplied by the network serv-
ice provider)
7) Finally, reboot (power-cycle) the unit.
Instruction end
Web browser option
This method requires a PC and a web browser.
To set the parameters:
1) Set the PC IP address to the default gateway address 192.168.0.1
2) Set the PC netmask to 255.255.0.0
3) Set the PC default gateway address to 192.168.0.1 (the IP address for the
default gateway).
4) Reboot the PC (if the operating system so requires). The PC can now connect
to the unit.
5) Connect the PC to a proper port of the unit and start a web browser.
6) In the browser address field, type the unit’s default

<IP address>192.168.0.10/conf and press Enter.
7) A login dialog box opens; log in as admin (User ID and Password are case sen-
sitive):
– User ID: Conf
– Password:admin
– The start page opens.
8) Click the Configuration button. The configuration page opens.
9) Enter the values for default gateway, net mask and EM IP address, and click
the Save button to save the settings.
10) If required, enter the DNS and NTP addresses (Supplied by the network serv-
ice provider), and click the Save button.
11) Click the Activate button to reboot (power-cycle) the unit.
Instruction end
The unit now has all the data it needs to carry out a complete boot sequence.
When rebooting the unit, the boot scheme follows that of the automatic booting,
from step 5) and forward; see “The automatic boot sequence” on page 8.
EM* and HTTP/TFTP* CCS/SIP Proxy*

server
IP
End-user
IRG/ITA unit
Fig. 5 The manual booting scenario
5.4 Additional DHCP Server Configuration
With automatic provisioning the following MUST be configured/distributed by the

DHCP server. Otherwise they MAY be configured/distributed by the DHCP server. In
addition to the normal information, such as IP configuration, DNS, NTP, etc., the fol-
lowing can also be configured:
Element Manager IP Address — The EM IP address can be distributed in the

“Next Server” field. This field is also known as “siaddr”. If a Windows DHCP is
used, option 66 should be used, but you also have to configure option 67 with
a dummy value. Option 67 should not be empty; any dummy entry is accept-
able.
VLAN configuration — A VLAN tag can be configured in private option 150,

syntax: VLAN:xxxx (xxxx = VLAN tag 1 - 4095). An “empty” terminal will at
boot send a DHCP request to a DHCP server, the server responds with a VLAN
tag. The terminal is then configured with the obtained VLAN tag and sends a
new DHCP request using the newly configured VLAN.
Vendor Class Identifier — All terminals have option 60 specified with “i3 micro
HAG”. This can be used for creating a specific group in the DHCP server with a
special configuration like the above.
Vood 100 & 200 Configuration Manual LED Behavior
6 LED Behavior
6.1 During Bootup
The flashes mentioned refer to all LEDs flashing in bursts of one, two, or three in a
row
1) One short flash after power on — Internal testing

(If repeated slow flashing after power on: internal testing failed)
2) LEDs off — kernel boot
3) One flash, repeated in a slow fashion — Initiation of peripheral circuits, for

example a switch
4) Two flashes, repeated in a slow fashion — Network configuration
5) Three flashes, repeated in a slow fashion — Element Manager

interaction
Note: Some of the steps above might be to quick to be visible for the user
6.2 During Normal Operation
Four flashes repeated in a slow fashion — Voice application not registered
Steady light — Voice application ready
LED on for 500ms, off for 100ms — The IVR utility can be used (only applicable
for MGCP protocol OR if Hotline/Network generated Dial Tone is configured)
Repeated rapid flashing — Message waiting indication
Vood 100 & 200 Configuration Manual Manual IRG/ITA Configuration
7 Manual IRG/ITA Configuration
This chapter describes how to manually configure the Vood IRG/ITA unit.
Alternatively, you can configure the unit using the Vood Centre/Element Manager.
This procedure is described in the ”Vood Operator’s manual.”, Ref. [1].
7.1 Name and Password Configuration

The user ID and the password for the configuration utility can be changed, once you
have logged in. To change them, enter new strings in the configuration menu
Name & Password.
7.2 Configuration Options

Start the IRG/ITA configuration application. There are two ways to configure the
IRG/ITA:
You can use a web browser – See “Using the web configuration utility” on
page 16.
You can use an ordinary analog phone – See “Using the phone interface” on
page 19.
The web browser interface can be used to configure all parameters, while only a sub-
set can be configured by the phone configuration tool. It is, however, possible to read
back the parameter values from the subset over the phone (provided that a proper
configuration has been entered).
7.2.1 Using the web configuration utility

The web configuration utility is accessed from a web browser.
The following browsers, or later, are supported:
Internet Explorer 6.0
Netscape 7
Mozilla 1.3
Opera 7
Note: To access the web configuration utility, the computer and the unit must be net-
worked and visible to one another.
To configure via the web:
1) The IP address of the IRG/ITA unit can be obtained from the phone connected
to the unit: Lift the receiver and enter the following sequence:
Example:
If the IP address obtained is 192.168.0.10, the correct URL is:

http://192.168.0.10/conf
2) Open the web browser on the PC and enter the URL of the <configuration>
page of the unit, and press Enter. http://<IP address>/conf
3) A login dialog box opens – log in (User ID and Password are case sensitive):
– User ID: Conf
– Password: admin
The start page opens; see Fig. 6 below.
Fig. 6 The start page
4) Click the Configuration button.
5) The configuration page opens; see Fig. 7 below. The figure shows a
screenshot where H.323 is used. If you are using SIP or MGCP, the screenshot
will look different.
Fig. 7 The configuration page
6) Set all parameters. Note that each configuration change has to be saved by
clicking the Save Changes button on the corresponding web page. Only the
fields actually being changed are stored locally in the terminal.
When the configuration has been completed, click the Activate button, caus-
ing the unit to reboot.
The configuration is finished when the boot sequence has been completed.
See “Booting” on page 6.
Instruction end
Note: You should now change the password and User ID to prevent unauthorized
access to the web configuration utility.
7.2.2 Accessing subscriber settings

See ”Vood IRG/ITA User Guide.”
7.2.3 Using the phone interface

The phone (analog) interface can be used to configure and check key parameters of
the unit. This option is intended for end-users who do not have access to a web
browser.
For the phone interface, the key is used as a delimiter, while the key is used
as the Enter key.
Example:
The code for entering a new IP address is:
Entering the IP address 10.2.11.23 is accomplished by entering the following key

sequence:
Note: For configuration changes to come into effect, the IRG/ITA must be rebooted
(power-cycled).
7.3 Default Settings
7.3.1 Factory reset

In order to reset the Vood Terminal to factory settings, use the analog configuration
interface.
Phone code to reset:
WARNING: All previously entered configuration data will be lost. This means
that you will have to configure the terminal all over again.
7.3.2 Password reset

In order to only reset the passwords to default, use the analog configuration inter-
face.
Phone code to reset:
Vood 100 & 200 Configuration Manual Services
8 Services
This chapter contains the services supported by H.323, SIP, and MGCP.
Note: It is up to the Call Agent to see to that the services in this chapter are supported
by MGCP.
8.1 Service Configuration

The services provided in the IRG/ITA depend on the software version used. Each ser-
vice available in a software release can be enabled or disabled for the end-user.
Some services require a configuration by the operator.
The corresponding IRG/ITA Software release note document describes each service
from an end-user perspective as well as from an operator’s configuration perspective.
8.2 Dial Plan
8.2.1 Dial Plan instructions do not apply to MGCP
This section (8.2) is not applicable to MGCP.
8.2.2 Phone number configuration
Phone Number A
Phone Number A is the phone number associated with the analog interface marked
‘A’ (for Vood 111 the analog interface is marked ‘Phone’).
Phone Number B
Phone Number B is the phone number associated with the analog interface marked
‘B’ (not valid for Vood 111).
Note: When there are two phone number fields to be entered (Vood models
122/142/242/292) you should be sure to enter two separate phone numbers.
8.2.3 Call barring configuration

This setting blocks calls to certain numbers. You can specify up to ten prefixes per
channel on the Dial Plan web page.
Example:
Prefix = 123 will bar all outgoing calls beginning with 123.
8.2.4 Special number configuration
Enable Smart Dial
The Enable Smart Dial checkbox enables or disables the Smart Dial function. When a
dialed string ends with the key, the IRG/ITA accepts the digits and tries to estab-
lish a call. In order not to have to terminate all phone numbers with the key, the
smart dial function should be enabled.
Note: When the Smart Dial function is enabled, phone numbers with a terminating
key are accepted as well.
The smart dial function measures the time between the keys pressed to decide when
all digits have been entered. To achieve the best performance of this function the
Minimum digits parameter should be set to the largest value possible. That is, to the
number of digits contained in the shortest normal number in the dial plan used. Spe-
cial numbers shorter than specified Minimum digits, like 112 in Europe and 911 in the
US, are handled separately by setting the Special Numbers parameters.
Note: When the Smart Dial function is enabled, using the key will immediately
trigger a call attempt, bypassing the time-out period.
Minimum digits
Minimum digits is the minimum number of digits the end-user has to input before the
dialed string is accepted as a complete number.
Note: The minimum digits value should be set to the number of digits contained in the
shortest number in the dial plan used.
Special Number
Special Number (up to four can be defined on the web page, up to 15 from the EM)
is used when the smart dial function is enabled. The parameter defines a number or
a number series that is an exception to the general rule of the parameter
Minimum digits. The ‘.’ character is used as wildcard when specifying series of num-
bers. Alarm numbers, like 112 (Europe) or 911 (US) should be configured here.
Example:
Setting a Special Number to 9.. makes all three digit numbers starting with a 9 to
be accepted as a complete phone number.
Optional Prefix
Each special number on the Dial Plan web page can by default have an optional prefix
added to the number. This optional prefix field appears to the left of the special num-
ber to which it applies.
Example 1:
Optional number prefix = 50638; special number = 8.. (. = wildcard). When 846
is entered, a call to 50638846 is initiated.
Example 2:
Minimum digits setting = 7; the optional number prefix field is blank; the special
number = 911. When 911 is entered, a call to 911 is initiated.
8.2.5 General prefix configuration

The terminal can be configured to handle number prefixes in three ways. These can
be combined in various ways.
If a dialed number starts with aaa, remove these numbers
If dialed number starts with bbb, remove these numbers and replace them with
ccc
Prepend (add as an inserted prefix) ddd to the dialed number
Example:
If dialed number starts with <22> remove that, or else
if dialed number starts with <11> replace that with <01234>
or else add <999> to the dialed number.
Number 22454545 will be sent as 454545
Number 11676767 will be sent as 01234676767
Every other outgoing call will be sent as 999xxxxxx
General prefixes may be used for accounting codes, long distance access or for any
reason whatsoever.
8.2.6 Hotline and warmline configuration
Hot Line
Outgoing calls will be placed to a specified hotline number on the Dial Plan web page
when the receiver is lifted. A hotline connection may be used to automatically con-
nect to another (call-placing) server or to automatically place an emergency call,
such as to a nursing station in a health-care facility.
Note: The IVR functionality will be operational for 30 seconds after boot, if Hotline is
activated. During these 30 seconds the LED is on for 500ms and off for 100ms,
IVR can be permanently activated (and Hotline disabled). The activation of IVR
is initiated by lifting the handset and pressing the hash key four times:
. To use the IVR configuration utility on the phone, see section 7.2.3.
When you are finished using the IVR function, you can either: reboot the termi-
nal, or press and hang up the handset.
Warm Line
A warm line is similar to a hotline, except that a call will be automatically placed only
after a specified time-out period.
Outgoing calls will be placed to a specified hotline number when the receiver has
been lifted and the warm line timer has timed out. The phone can be used the normal
way until the timer has timed out.
For example: with a warm line feature in a health-care facility, a resident could use
their telephone in a normal manner. But if a phone is taken off-hook for 45 seconds
and no keys are pressed, the nursing station is called automatically.
8.2.7 Busy Tone on hang-up

The Busy Tone on Hang-up checkbox enables or disables, if busy tone is to be gen-
erated on hang-up.
8.3 Call Waiting with Call Hold
8.3.1 Call waiting

For H.323, the H.450.6 standard is supported.
To activate:
To deactivate:
To activate after a specified time, press . Then insert the time, using the
range 5–120 sec. Finish by pressing .
When you already are engaged in a call, two beeps will inform you that someone else
is calling.
Default: On
During an established call:
If you do not want to answer the waiting call, press . If call forwarding
on busy or answering machine on busy is configured, the appropriate service
will then be activated. Otherwise, the waiting call will get a busy signal. If you
do not answer the waiting call within a specified time, action will be taken as if
had been pressed.
If you do want to answer the waiting call, press .
To switch back to the original call, press again.
Pressing a number of times will switch back and forth between the two
calls.
Pressing will finish the current call. When you press you will also
automatically switch to the other call.
8.4 Inquiry Call with Call Hold

When you have established a call with person 1, press R to start a new call. Dial the
number to person 2 and wait for an answer. When both calls have been established,
you can press to switch back and forth between the two calls. Press to
terminate one of the calls and switch to the other.
8.5 Message Waiting

If an incoming call is diverted to the answering machine, the LEDs will flash: they will
alternate between on for 100 ms, and off for 100 ms. The message waiting indication
can be cancelled by lifting the receiver
8.6 Three-Way Conferencing

To start three-way conferencing, perform the Inquiry call service, then press .
If a call is waiting, answer the waiting call with and then press to estab-
lish three-way conferencing.
8.7 Click to Dial Service

It is possible to use Click to dial from the web server’s phone lists. If a stored number
is clicked and the receiver is lifted within 15 seconds, that number is dialed automat-
ically. It is also possible to first lift the receiver and then click the number. In this case
the number will be dialed directly.
8.8 Fast Re-Dial Service

To repeat the last dialed number, press the asterisk key three times ( ) on
your phone keypad.
8.9 Diversion Services
8.9.1 Diversion Services control via phone or web interface
The different types of diversions can either be controlled from the phone or from the
web interface.
This is controlled from the subscriber’s <incoming call handling> web page. The web
page that controls these services is self-explanatory, while the codes that control the
services from the phone interface are presented below.
After activating/deactivating a diversion, a tone is played. If the activation/deactiva-

tion was successful, two beeps are heard. If the command failed, the congestion tone
is heard.
8.9.2 Call diversion

For H.323, the H.450.3 standard is supported.
8.9.3 Call forwarding unconditional service

To activate:
<diverted-to-number>
Example:
To have all incoming calls diverted to 50638800, dial
To deactivate:
8.9.4 Call forwarding on busy service

To activate:
Example:
To have incoming calls diverted to 50638800 when busy, dial
To deactivate:
8.9.5 Call forwarding on no reply service

To activate:
Example:
To have incoming calls diverted to 50638800 when no reply, dial
To deactivate:
8.10 Answering Machine Service

The answering machine service is an optional feature that is licensed separately (and
ordered specifically) from i3. If you have not signed an agreement to license the
answering machine service from i3, it will not appear in your software.
The IRG/ITA unit's built-in answering machine works in conjunction with a possible e-
mail server. The answering machine records messages to sound files that are stored
locally and can also append them to e-mails sent to a specified e-mail address. The
local sound files can be administrated using the telephone. The e-mail sound files can
be listened to by opening the e-mail in a mail client.
Note: Please note regarding the answering machine service:
The locally stored sound files are NOT stored permanently. This means that if
the IRG loses power or reboots due to manually entered configuration changes,
etc., the locally stored messages will be lost. So usage of the e-mail function is
recommended.
The amount of storage is limited on the IRG/ITA so when the storage area is
full the oldest message will automatically be removed. The number of mes-
sages that can be stored locally is today 20 on the ITA and 10 for each tele-
phone port on the IRG. Each message can be max ~40 seconds long.
The answering machine is managed either from an analog phone or web page. If the
UVM service is activated, the subscriber has to make some settings in <user> web
pages before the answering machine mail service is operational.
8.10.1 Mail configuration
Mail address 1 (user parameter)
The user must define a mail address in the IRG/ITA, to where recorded messages
should be sent. The parameter can be found in the user specific web page <answer-
ing machine>.
The parameter is mail address 1.
Default: –
Example:
john.smith@home.se
Mail address 2 (user parameter)
mail address 2 is optional. It can be used if the recorded message should be sent
to an additional mail address.
Default: –
SMTP address (user parameter)
The e-mail server to contact has to be configured in the parameter SMTP address.
Default: –
Example:
mailserver.company.se
When the mail address and SMTP address have been defined, a test mail can be sent
with the current settings. To do this, click the Test Mail button in the user specific
<answering machine> web page.
8.10.2 Administration of locally stored messages

By using the telephone and dialing the code you can administrate your
recorded messages. After dialing the code the IRG will automatically play every
recorded message in the order they were recorded. When no more messages are
available a continuos beeping is played.
See ”Vood IRG/ITA User Guide.” for information how to do this.
8.10.3 Recording a greeting message

You also need to record a greeting message. This can be done either from the web
interface or from the telephone. The greeting message can be max ~20 seconds
long.
8.10.4 Redirect to the answering machine

It is possible to redirect calls to the answer machine in three different ways.
Immediately directed to the answering machine.
Directed to the answering machine on busy.
Directed to the answering machine if there is no answer within a specified time.
8.11 Caller ID Service

Caller ID has to be configured before it can be used, since there are different stan-
dards concerning this function.
The parameters concerning Caller ID configuration can be found on the <configura-

tion> web page <enable services> of the web interface.
8.11.1 DTMF
DTMF controls if the method to produce the caller ID on the analog interface should
be with DTMF tones.
Default: Off
Standards: Choose the DTMF standard according to the standard (and country) your
caller ID equipment supports.
Default: ETSI, EN 300 659-1 (Sweden)
8.11.2 FSK
FSK controls if the methods to produce the caller ID on the analog interface should
be with FSK modulation technology.
Default: Off
Standards: Choose the FSK standard according to the standard (and country) your
caller ID equipment supports.
Default: ETSI, Europe
8.12 Service Calling Line ID Restriction for Anonymous Calling

For outgoing calls from the terminal, the following procedure can be applied to sup-
press Calling line ID presentation at the called party end. This restriction will be valid
for one call:
Press to activate Calling line ID restriction for the next outgoing call. A
dial tone will indicate that the service has been activated.
The service will be disabled automatically when the call is terminated.
Vood 100 & 200 Configuration Manual Protocol Specific Configuration
9 Protocol Specific Configuration
The IRG/ITA is able to support any of the three main call control protocols:
H.323
SIP
MGCP
Only one of these call control protocols can be used in a system, however, and deter-
mining which one of these will be used is decided when a system is ordered and
installed. Selecting which call control protocol will be used is not a software-select-
able option. The software for a protocol is delivered as a separate part of the overall
software package, and for each protocol there will be a distinct set of configuration
parameters.
The protocol-associated configuration parameters are described in the appendices.
For protocol:
H.323 — See Appendix C: H.323
SIP — See Appendix D: SIP
MGCP — See Appendix E: MGCP
Vood 100 & 200 Configuration Manual Parameters and Settings
10 Parameters and Settings
This section provides the information about all parameters and their settings. Each
parameter is tagged with the method by which it is accessed – by web, phone, or
either.
10.1 Parameter Entry Overview

Many parameter entry screens have four fields:
Default:
Controlled from:
Phone code to set:
Phone code to check:
The Default field displays the default setting from factory.
The Controlled from field specifies the access methods by which this parameter may
be changed.
If the parameter is allowed to be changed by telephone, The Phone code to set field
is the code to be used to trigger a change in this parameter.
The Phone code to check field will trigger a computer-voice report on what is the cur-
rent parameter setting.
10.2 Country Specific Configuration
10.2.1 Country
Choose which impedance (country) the analog interface should match. Thereby, the
country standard tones, ring pattern, etc., are configured.
Note: The analog interface impedance configuration is only applicable to Vood 111,
Vood 121, Vood x42 and Vood 292.
10.2.2 Sound volume configuration

You can increase or decrease the sound volume. 5 is the highest/loudest; 1 is the
lowest/quietest.
Default: 3
Controlled from: Web, EM
10.2.3 Language
Choose which language the <user> pages should use.
10.2.4 Time zone configuration

Find your region/country in Appendix A. Configure the time and date with the time
zone code accordingly, using uppercase letters. See Appendix A: Zone Codes. It is
not necessary to reboot the IRG. An NTP Server should also be configured. For con-
figuring the IRG to find the NTP server, see “NTP address” on page 57.
Default: CET
The current time is displayed, and if it is wrong, i.e., if an NTP server isn’t used, it can
be configured manually by clicking on the time.
Note: Because of country specific daylight saving time rules, etc., the time could be
one hour off.
10.2.5 Polarity reversal

There have been customer requests to use the Vood products together with analog
pay-phones to offer IP telephony to pay-phone booths and Internet cafés. Then
polarity reversal is the method used. If enabled, polarity reversal is performed for the
calling party A, on the analog interface, in case of a call setup (called party B answer
the call) and call release (A or B hangs up).
Default: Off
Note: This is only applicable for SIP protocol
10.3 Network Configuration

In this section the network connectivity parameters are described. Also described are
network architecture parameters deciding whether DHCP and/or Static IP is to be
used.
10.3.1 Use DHCP

Use DHCP decides whether the IRG/ITA will start a DHCP client in the boot procedure
or not.
Default: On
Note: If the Use DHCP parameter is set and there is no DHCP server, the IRG/ITA is
configured according to the default IP stack configuration after a time out of 60
seconds.
10.3.2 EM address from DHCP

EM address from DHCP decides if the “next-server” field in the “DHCP offer” message
should be used as the IP address of the EM.
Default: On
10.3.3 IP address
IP address is the network address of the IRG/ITA.
Default: 192.168.0.10
Controlled from: Web, EM, Phone: (‘dotted quad’ format for both)
Phone code to set:
10.3.4 Netmask
Netmask is the network mask of the IRG.
Default: 255.255.0.0
Phone code to set:
10.3.5 IP gateway
IP Gateway is the network route of the IRG.
Default: 192.168.0.1
Phone code to set:
Note: During boot the IRG/ITA will try to ARP the default gateway, this will time-out
after ~60 sec. if the default gateway isn’t reachable.
10.3.6 Broadcast
Broadcast is the broadcast address used by the IRG.
Default: 192.168.255.255
Controlled from: Web, EM: (‘dotted quad’ format)
Phone code to set: –
Phone code to check: –
10.3.7 EM address
EM Address is the IP address used by the IRG when contacting the HTTP/TFTP server
in the Element Manager. The EM Address can be in either FQDN or in ‘dotted quad’
format (xxx.xxx.xxx.xxx).
Default: 0.0.0.0
Controlled from: Web, EM: (FQDN or ‘dotted quad’ format)
Phone: (‘dotted quad’ format)
Phone code to set:
Note: One can set the EM address by telephone. However, if a DHCP is used to get an
EM address, you cannot then use the telephone to assign it. A DHCP-assigned
EM address over-rides a telephone-assigned EM address. (Also, a DHCP-
assigned EM address cannot be listened to on a telephone.)
10.4 Switch Configuration for Vood 111
10.4.1 Physical interface

Auto negotiation is always enabled.
10.4.2 VLAN/CoS configuration

The Vood 111 can set the 802.1Q VLAN tag for the VoIP application, if desired. If no
VLAN tag is wanted, then all three parameters concerning VLAN and priority must be
left empty. The ITA must be rebooted.
VLAN user priority/Class of Service 802.1p
The parameter VLAN user priority sets the priority bits of the VLAN header. The value
must be entered in hexadecimal form, 3 bits.
Default: –
VLAN CFI bit
The parameter VLAN CFI bit sets the CFI bit of the VLAN header. The value must be
entered in hexadecimal form, 1 bit.
Default: –
VLAN ID
The parameter VLAN ID sets the identity field of the VLAN header. The value must be
entered in hexadecimal form, 12 bits.
Default: –
10.5.1 When Switch Configuration Entries Take Effect
All switch configurations are activated when submitted, that is, there is no need for
rebooting the IRG.
10.5.2 Similarities between Vood 121 and Vood x42
The same principles are used for Vood 121 as for Vood x42, therefore for pictures and
examples see 10.7 Switch Configuration for Vood x42. The main difference between
Vood 121 and Vood x42 is only the number of ethernet ports.

The following parameters can be configured for each port individually:
Auto negotiation
Full or half duplex
100Mb or 10Mb
10.5.4 VLAN configuration

The Vood 121 can support up to 16 active 802.1Q VLAN tags in the Ethernet frames.
Enable VLAN
Enable VLAN specifies if VLAN should be used or not.
Default: Off
Activate, ID and Port membership
Activate enables each tag.
ID sets the VLAN ID. The value must be entered in decimal form (1-4094, 12 bit).
Finally, select the VLAN tag port membership.
Default: –
Tag Outgoing Packets
Tag Outgoing Packets sets which ports should tag outgoing packets. The parameter
tags untagged packets with the ingress port default VID. This should, for example,
most likely be set for the uplink.
Default: –
Untag Outgoing Packets
Untag Outgoing Packets sets which ports should untag outgoing packets. This could
be useful if non-VLAN supporting equipment is connected.
Default: –
Ingress VLAN Filtering
Ingress VLAN Filtering will discard packets whose VID port membership in the VLAN
table do not include the ingress port.
Default: –
Discard Non PVID Packets
Discard Non PVID Packets will discard packets whose VID do not match the ingress
port default VID, that is, only those packets whose VID equals the default VID will be
allowed.
Default: –
Default VLAN tag
All ports have a default tag. The value must be entered in decimal form, 16 bit.
The first three bits are VLAN user priority (Bits 15–13)
The fourth bit is the VLAN CFI bit (Bit 12)
The 12 last bits are the VLAN ID (Bits 11–0).
Default: –
10.5.5 QoS
Three different types of prioritization can be configured in the Vood 121:
Differentiated Services Ingress Classification:
Enable diffserv priority classification for ingress packets per port.
Default: Off
The Differentiated Services Code Point (DSCP) uses the 6 key bits in the Type of Ser-
vice (TOS) field to assign incoming packets a high or low priority. These 6 bits in the
IP header field allow for 64 possible DSCP codes. Each packet’s DSCP code will be
compared to the code points marked in the DSCP web page. Marked code points are
given high priority; unmarked code points are given low priority.
Specify which code points that should be assigned a high priority.
802.1p Ingress Classification:
Enable 802.1p priority classification for ingress packets per port.
Default: Off
This setting is used to assign priority to incoming 802.1Q packets. If priority >= 4,
the packet is classified as high priority, otherwise as low priority.
High/Low Priority Marking on Ingress Packets:
Enable High/Low Priority Marking on ingress packets per port.
Default: On (CPU port)
Note: Diffserv and 802.1p priority classification override this port based priority.
10.5.6 Rate limit

Rate limit sets the port throughput. Each port can be rate limited, both for High and
Low priority, and also for incoming and outgoing packets. The rate limit is specified
in absolute values in Kbps. For example, if the rate is set to 700, then the throughput
will be 700 Kbps. The value must be entered in decimal form, 0–100000. The switch
uses one second as an interval. At the beginning of each interval the counter is
cleared to zero and the rate limit mechanism starts to count the number of bytes. If
the number of counted bytes exceeds the programmed limit, the switch will stop
receiving/transmitting packets on the port until the “one second” interval expires.
Default:
Note: Leave the parameter empty to disable this feature.
Note: A zero will block the port.
Note: The rate is quantized in steps of 32 Kbps. Therefore a rate setting of 300 Kbps
will in reality be ~288 Kbps. The minimum rate (except for zero) is 32 Kbps.
10.5.7 Storm protection

Each port can be broadcast storm protected. Multicast storm protection can also be
enabled.
Rate
Rate specifies a rate limit that is specified in percent of maximum bandwidth. That is,
if the link is a 10Mbps, then 10 corresponds to a maximum throughput of 10% of all
broadcast packets. The value must be entered in decimal form, 0–100.
Default: 1%
Port Enabling
Port Enabling enables broadcast storm protection for ingress packets per port.
Default: Off
Multicast Storm Enabling
Multicast Storm Enabling sets if multicast packets are to be storm protected. The
same rate as that for broadcast is used.
Default: Off

Auto Negotiation
Full or Half duplex
100Mb or 10Mb
The interface is automatically re-initiated, that is, you do not need to reboot the IRG.
Note: Both ports get the same configuration.
10.6.2 VLAN/CoS Configuration

The Vood 122 can set the 802.1Q VLAN tag for the VoIP application, if desired. If no
VLAN tag is wanted then all three parameters concerning VLAN and priority must be
left empty.
The IRG must be rebooted.
VLAN user priority/Class of Service 802.1p
The parameter VLAN user priority sets the priority bits of the VLAN header. The value
must be entered in hexadecimal form, 3 bits.
Default: –
VLAN CFI bit
The parameter VLAN CFI bit sets the CFI bit of the VLAN header. The value shall be
entered in hexadecimal form, 1 bit.
Default: –
VLAN ID
The parameter VLAN ID sets the identity field of the VLAN header. The value must be
entered in hexadecimal form, 12 bits.
Default: –
10.7 Switch Configuration for Vood x42

All switch configurations are activated when submitted, that is, there is no need for
rebooting the IRG.

Auto Negotiation
Full or Half duplex
100Mb or 10Mb
Note: Please note regarding the switch physical interface:
The WAN port can't be configured for Vood 242, it's static configured for full
duplex, 100Mbps.
The Vood 242 has the possibility of “disable far end fault” for the optical inter-
face (WAN port)

The Vood x42 can support up to 16 active 802.1Q VLAN tags in the Ethernet frames.
Example:
We have three VLANs configured. The CPU and WAN ports belong to VID 111. Port
A and the WAN port belong to VID 222. Ports B, C and the WAN port belong to VID
333. All outgoing packets on ports B and C will be untagged. All incoming packets
on ports B and C will be tagged with the default tag 333. See Fig. 8.
Fig. 8 VLAN configuration example
Enable VLAN
Enable VLAN specifies if VLAN should be used or not.
Default: Off
Activate, ID and Port membership
Activate enables each tag.
ID sets the VLAN ID. The value must be entered in decimal form (1-4094, 12 bit).
Finally, select the VLAN tag port membership.
Default: –
Tag Outgoing Packets
Tag Outgoing Packets sets which ports that should tag outgoing packets. The param-
eter tags untagged packets with the ingress port default VID. This should, for exam-
ple, most likely be set for the uplink.
Default: –
Untag Outgoing Packets
Untag Outgoing Packets sets which ports that should untag outgoing packets. This
could be useful if non-VLAN supporting equipment is connected.
Default: –
Ingress VLAN Filtering
Ingress VLAN Filtering will discard packets whose VID port membership in VLAN table
do not include the ingress port.
Default: –
Example:
Ports A and C are set to VID = 7 in the VLAN table. All incoming packets having
VID = 7 on port B will be discarded. See Fig. 9.
Fig. 9 Ingress VLAN filtering example
Discard Non PVID Packets
Discard Non PVID Packets will discard packets whose VID do not match the ingress
port default VID, that is, only those packets whose VID equal the default VID will be
allowed.
Default: –
Example:
Port A and C are set to VID = 7, Port A and B are set to VID = 4 in the VLAN table.
If Discard Non PVID Packets is set for Port A, then all incoming packets on port A
with VID ≠ 7 will be discarded. See Fig. 10.
Fig. 10 Discard Non PVID Packets example
Default VLAN tag
All ports have a default tag. The value must be entered in decimal form, 16 bit.
The first three bits are VLAN user priority (Bit 15–13)
The fourth bit is the VLAN CFI bit (Bit 12)
The 12 last bits are the VLAN ID (Bit 11–0).
Default: –
10.7.3 QoS
Three different kind of prioritization can be configured in the Vood x42:
Enable diffserv priority classification for ingress packets per port.
Default: Off
The Differentiated Services Code Point (DSCP) uses the 6 key bits in the Type of Ser-
vice (TOS) field to assign incoming packets a high or low priority. These 6 bits in the
IP header field allow for 64 possible DSCP codes. Each packet’s DSCP code will be
compared to the code points marked in the DSCP web page. Marked code points are
given high priority; unmarked code points are given low priority.
Specify which code points that should be assigned a high priority.
Enable 802.1p priority classification for ingress packets per port.
Default: Off
This setting is used to classify priority for incoming 802.1Q packets. The priority is
compared against this value. If priority >= 4, the paket is classified as high priority,
else classified as low priority.
High/Low Priority Marking on Ingress Packets:
Enable High/Low Priority Marking on ingress packets per port.
Default: On (CPU port)
Note: Diffserv and 802.1p priority classification override this port based priority.
10.7.4 IGMP
Query Performance
If the switch receives an IGMP Leave, the switch sends an IGMP query to find out if
there is another set-top box listening on the same multicast channel. Parameter
IGMP query time-out specifies how long the switch should wait for an answer before
forwarding the IGMP Leave uplink. Therefore, if only one set-top box is connected per
switch port, this parameter should be set to zero.
Default: 0
Valid values for this parameter are 0-7. For example, ‘3’ will set the query time-out
to 300ms.
Uplink Configuration
Configure the port/ports connected to a multicast server. The WAN port should nor-
mally be included.
Default: WAN
Controlled from: Web
Leave Delay
This parameter should be equal to the time for a multicast channel to be dropped by
the nearest upstream switch, i.e. the time between the first leave and channel
removal.
Default: 30
Valid values for this parameter are 0-200. For example, ‘30’ will set the parameter to
3000ms = 3 seconds.
10.7.5 Rate limit

Rate limit sets the port throughput. Each port can be rate limited, both for High and
Low priority, and also for incoming and outgoing packets. The rate limit is specified
in absolute values in Kbps. for example, if the rate is set to 700, then the throughput
will be 700 Kbps. The value must be entered in decimal form, 0–100000. The switch
uses one second as an interval. At the beginning of each interval the counter is
cleared to zero, and the rate limit mechanism starts to count the number of bytes. If
the number of counted bytes exceeds the programmed limit, the switch will stop
receiving/transmitting packets on the port until the “one second” interval expires.
Default:
Note: Leave the parameter empty to disable this feature.
Note: A zero will block the port.
Note: The rate is quantized in steps of 32 Kbps. Therefore a rate of 300 Kbps will in
reality be ~288 Kbps. The minimum rate (except for zero) is 32 Kbps.
10.7.6 Storm protection

Each port can be broadcast storm protected. Multicast storm protection can also be
enabled.
Rate
Rate specifies a rate limit that is specified in percent of maximum bandwidth. That is,
if the link is a 10Mbps, then 10 corresponds to a maximum throughput of 10% of all
broadcast packets. The value must be entered in decimal form, 0–100.
Default: 1%
Port Enabling
Port Enabling enables broadcast storm protection for ingress packets per port.
Default: Off
Multicast Storm Enabling
Multicast Storm Enabling sets if Multicast packets are to be storm protected. The
same rate as that for broadcast is used.
Default: Off

The Vood 292 has nine external ports and one internal port.
WAN One fiber-optic interface. 100Mbps, full duplex multimode.

Normally considered as the “uplink”.
Ports A - H Eight fast Ethernet, fully compliant with the applicable sections
of IEEE802.3, IEEE802.3u and IEEE802.3x. Automatic
MDI/MDIX crossover for 100BASE-TX and 10BASE-T. The
fourth bit is the VLAN CFI bit (Bit 12)
CPU One “internal” port for the CPU of the Vood 292.

Auto Negotiation
Full or Half duplex
100Mb or 10Mb
If auto negotiation is enabled, it is possible to configure what to advertise. The status

page displays the actual link information per port.
Note: The WAN port can't be configured for Vood 292, it's static configured for full
duplex, 100Mbps.

The Vood 292 can support up to 64 active 802.1Q VLAN tags in the Ethernet frames.
Each port can be configured with the following “default” information: See Fig. 11
Enable 802.1q — Enable 802.1q. Activates the VLAN functionality per port
Default Priority — This Priority will be assigned to ingress non-tagged pack-

ets.
Default VID — This VID will be assigned to ingress non-tagged packets.
Fig. 11 VLAN “default” configuration
Configure VLAN:
To add a new VLAN, press link “Configure new VID”. See Fig. 11and Fig. 12
VID- Actual VLAN ID to be configured
For a specific VID each port can be configured with:
VLAN Membership- One of four different memberships can be chosen per port.
Member, Egress Unmodified: The port is a member of the “actual VID”,

packets egress unmodified.
Not Member: The port is not a member of the “actual VID” and VID packets
are not switched in any direction. This should be the default setting for ports
with 802.1q disabled.
Member, Egress Untagged: The port is a member of the “actual VID”, pack-
ets egress untagged. This setting must be used for ports connected to equip-
ment that are NOT 802.1q capable. The default VID and priority will be used
for ingress packets.
Member, Egress Tagged: The port is a member of the “actual VID”, packets
egress tagged. This setting should be used for ports connected to equipment
that are capable of 802.1q tagging.
When a VLAN configuration is saved, the <802.1Q VLAN> page will automatically be
loaded and all configured VLAN are displayed. By clicking on the VID, you can modify
an existing VLAN, see Fig. 12. You can also delete an existing VLAN configuration.
A typical triple play solution could be to have one VLAN for IP telephony, one for
media and one for PC “internet traffic”. The WAN port is purely tagged also known as
a trunk
Fig. 12 Create/Modify a VID
Example:
We have two VLANs configured. One used for IP telephony/Web Management -

VID 10, and one used for multicast streaming - VID 20, see Fig. 13. All packets on
the ingress WAN port are assumed to be tagged with either VID 10 or 20.
Eight ports are used for multicast streaming, default VID 20. The CPU must have
default VID 10, since that is the IP telephony/Web management VLAN.
Fig. 13 802.1Q VLAN page
The VLAN configuration is displayed on the status page.
The IP Telephony/Web Management VLAN must be configured as egress

untagged for the CPU port. The multicast VLAN should be configured as
egress tagged for the CPU port. Failing to do so might leave the Vood 292 in a
state where it cannot be accessed, a factory reset might be necessary to resolve this
condition.
Note: The default setting for ingress rate limit is 128Kbps, for broadcast and multicast
packets. This configuration can/should still be configured even though multicast
streaming is performed. No rate limit will be performed on desired multicast
channels.
10.8.3 QoS
The Vood 292 can configure QoS for incoming packets in one of four ways:
No ingress QoS classification.
802.1p ingress classification.
Differentiation services ingress classification.
A combined 802.1p and differentiation services ingress classification
If you decide to use 802.1p or differentiated services ingress classification (or some
combination), packets will be separated into four priority queues.
No Ingress QoS Classification:
No classification will be performed on ingress packets.
Specify which 802.1p priority tags that should correspond to each priority queue.
802.1p priority classification for ingress packets can be enabled on port basis.
Specify which code points that should correspond to each priority queue. Diffserv pri-
ority classification for ingress packets is enabled on port basis.
Combined 802.1p and Differentiation Services ingress Classification
If you select his option, you should indicate which of these two methods is to take
precedence over the other.
10.8.4 IGMP
Query Performance
If the switch receives an IGMP Leave, the switch sends an IGMP query to find out if
there is another set-top box listening on the same multicast channel. Parameter
IGMP query time-out specifies how long the switch should wait for an answer before
forwarding the IGMP Leave uplink. Therefore, if only one set-top box is connected per
switch port, this parameter can be set to zero.
Default: 0
Valid value for this parameter is 0-7. For example, 3 - sets the query time-out to
300ms.
Uplink Configuration
Configure the port/ports connected to a multicast server. The WAN port should nor-
mally be included.
Default: WAN
Controlled from: Web
10.8.5 Rate limit

Each port can be rate limited, both for incoming and outgoing packets.
Ingress Packet Rate Limit
Ingress rate limit can be applied on one of following modes.
All packets
Broadcast, Multicast and flooded Unicast packets
Broadcast and Multicast packets
Only Broadcast packets
The rate on incoming packets can also be limited differently for each priority queue.
Note: The default setting for ingress rate limit is 128Kbps, for broadcast and multicast
packets. This rate limit can/should still be configured even though multicast
streaming is performed. No rate limit will be performed on desired multicast
channels.
Egress Packet Rate Limit
One rate limit can be selected for outgoing packets. This rate is applied on all types
of packets.
10.8.6 Status
See Fig. 14 as an example.
Physical interface
Each port's link status is monitored in real time (on page reload). The following
parameters are displayed.
Link Status (Up or Down)
Speed (100 Mbps or 10 Mbps)
Duplex (Full or Half)
Note: The speed and duplex status are only valid if the link is up.
802.1q VLAN
All configured VLANs are presented in table form.
Fig. 14 Status page
10.9 DNS Configuration

The DNS Configuration section allows the selection of one or two DNS servers.
10.9.1 Use DNS from DHCP

If enabled, the DNS address will be taken from the DHCP server (if available).
Default: on
10.9.2 DNS address 1

DNS Address 1 is the IP address used by the IRG when first contacting a DNS server.
Default: 0.0.0.0
Phone code to set:
10.9.3 DNS address 2

DNS Address 2 is the IP address used by the IRG when the first DNS server is not
responding.
Default: 0.0.0.0
Controlled from: Web, EM: (‘dotted quad’ format)
Phone code to set: –
Phone code to check: –
10.10 NTP Configuration

The NTP Configuration section allows the selection of one NTP server.
10.10.1 NTP address

NTP Address is the IP address used by the IRG when contacting a NTP server. The
NTP Address can be in either FQDN or in ‘dotted quad’ format (xxx.xxx.xxx.xxx).
Default: 0.0.0.0
Controlled from: Web: (FQDN or ‘dotted quad’ format)
Phone: (‘dotted quad’ format)
Phone code to set:
10.11 SNMP Configuration

The SNMP Configuration section allows the selection of one SNMP Management sta-
tion.
Note: SNMP configuration is only applicable to Vood x42 and Vood 292.
10.11.1 SNMP address

The SNMP Address parameter is the IP address used by the IRG for ‘authentication’
of SNMP Management station, that is, only queries from this IP address will be
accepted. The SNMP Address can be in either FQDN or in ‘dotted quad’ format
(xxx.xxx.xxx.xxx).
Default: 0.0.0.0
Controlled from: Web, EM: (FQDN or ‘dotted quad’ format)
10.12 NAT Configuration
10.12.1 MGCP, H.323, SIP and support for NAT configuration
Please note regarding NAT configuration:
NAT configuration is not applicable to MGCP

H.323 supports only UPnP
SIP supports both UPnP and STUN
10.12.2 UPnP support

The IRG/ITA will, dependent on this parameter, try to use UPnP to set up communi-
cation through a NAT. So if a IRG/ITA is located behind a NAT and the NAT supports
UPnP service WANIPConnection or WANPPPConnection, this service will be used to
open up the NAT for media and H.323 communication.
Enable UPnP
Enable UPnP, determines whether if UPnP should be used when the IRG/ITA is located
behind a NAT server/firewall.
Default: On
Note: If UPnP discovery fails, UPnP will not be used
10.12.3 STUN
For many NAT routers it is necessary to refresh the WAN/LAN address bindings to
make it possible for the Vood to be reached at all times. The Keep Alive parameters
are used to accomplish this. The Keep Alive Server is typically the outbound proxy. If
no outbound proxy is used, it's then typically the registration server. The Keep Alive
Interval is typically 20 - 30 seconds.
If the STUN protocol for automatic detection of address bindings in NAT routers is
supported by the Service Provider, it will typically be supported by the server used as
the registration server. If some other server is used as the STUN server, you could
configure this server in the STUN Server parameter. Most of the time, however, this
will not be necessary.
Note: If STUN discovery fails, STUN will not be used
Enable STUN
If STUN is enabled, STUN will be attempted after UPnP is attempted (if UPnP is
enabled). If a UPnP attempt succeeds, STUN will not be attempted.
Default: On
STUN server
This setting determines which STUN Server is to be used.
Default: Registration Server (FQDN or IP address)
10.12.4 Manual NAT Configuration
NAT address from SIP
The IRG/ITA will be manually configured with a WAN address and port values taken
from SIP. This manual configuration will be performed if UPnP or STUN discoveries fail
or are disabled.
Default: Off
Note: Only applicable for SIP protocol
NAT Address
NAT Address is the WAN IP address used by the IRG when it is located behind a NAT
Server/firewall.
Default:
Note: This NAT address will only be used in the call setup messages. The web server
will use the IP address configured in section “Network Configuration” on
page 32.
NAT Bindings refresh timer
Default: 20
10.13 Dial Plan

The Dial Plan section allows for setting of phone numbers, one for each analog inter-
face and also for dial plans settings (the Vood 111 has only one analog interface,
labeled Phone). There is also a parameter that controls if a local busy tone must be
generated if the peer hangs up.
10.13.1 Phone number configuration

Instructions for phone number configuration have been moved to the respective pro-
tocol appendix. See “Phone Number Configuration” on page 88 for H323 and “Phone
Number Configuration” on page 95 for SIP.
10.13.2 Call barring configuration

Call Barring bars calls to certain numbers. You can specify up to ten prefixes per
channel.
Default: –
10.13.3 Special number configuration
Enable Smart Dial
The Enable Smart Dial checkbox enables or disables the smart dial function. When a
dialed string ends with the key, the IRG/ITA accepts the digits and tries to estab-
lish a call. In order not to have to terminate all phone numbers with the key, the
smart dial function should be enabled.
The smart dial function measures the time between the keys pressed to decide when
all digits have been entered. To achieve the best performance of this function the
Minimum digits parameter should be set to the largest value possible. That is, to the
number of digits contained in the shortest normal number in the dial plan used.
Special numbers shorter than specified Minimum digits, like 112 in Europe and 911
in the US, are handled separately by setting the Special Numbers parameters.
Default: On
Note: When the Smart Dial function is enabled, phone numbers with a terminating
key are accepted as well.
Minimum digits
Minimum digits is the minimum number of digits the end-user has to input before the
dialed string is accepted as a complete number.
Default: 5
Note: The minimum digits value should be set to the number of digits contained in the
shortest number in the dial plan used.
Special Number
Special Number (up to four can be defined) is used when the smart dial function is
enabled. The parameter defines a number or a number series that is an exception to
the general rule of the parameter Minimum digits. The ‘.’ character is used as wild-
card when specifying series of numbers. Alarm numbers, like 112 (Europe) or 911
(US) should be configured here.
Default: –
Example:
Setting a Special Number to 9.. makes all three digit numbers starting with a 9 to
be accepted as a complete phone number.
Optional Prefix
Each special number in the Dial Plan web page can have a prefix added to the number
by default.
Default: –
Example:
Optional prefix = 50638, special number = 8.. (‘.’ = Wildcard)
All three digits outgoing call starting with an 8 will be sent to 506388..
10.13.4 General prefix configuration

Each channel can have a general prefix for every outgoing call in the Dial Plan web
page.
Default: –
Example:
General Prefix = 424 Unless starting with 02
Every outgoing call that doesn’t start with 02 will automatically add 424 in the
beginning of the number.
10.13.5 Hotline configuration

Outgoing calls will be placed to a specified hotline number on the Dial Plan web page
when the receiver is lifted.
Default: –
Note: The IVR functionality will be operational for 30 seconds after boot, if Hotline is
activated. During these 30 seconds, IVR can be permanently activated (and
Hotline disabled). The activation of IVR is initiated by lifting the handset and
pressing the hash key four times:
Warm Line Timer
Outgoing calls will be placed to a specified hotline number when the receiver has
been lifted and the warm line timer has timed out. The phone can be used the normal
way until the timer has timed out.
Default: –
10.13.6 Busy tone on hang up

Busy Tone on Hang up is set if a busy tone must be generated locally should the peer
hang up.
Default: On
10.14 Codec Configuration
10.14.1 Codec configuration overview
This section contains the codecs supported by H.323, SIP and MGCP.
The codec configuration menu configures the codecs the IRG/ITA should offer to the
calling or called party when a call connection is first established. The different codecs
can be enabled/disabled and be given a priority to indicate the preferred order.
The preferred packet size and the maximum packet size of the media packets can be
set as well. The DTX function can be enabled/disabled for each supported codec.
The distinction between preferred and maximum packet size is as follows: When the
packet size of the media session is negotiated between the peers, the maximum size
is used to indicate the largest packet size the IRG/ITA can receive. The preferred size
is used to indicate the packet size that is most wanted (for either bandwidth or round
trip delay reasons).
– The maximum packet size must be greater than or equal to the preferred
packet size
– The unit for packet size is milliseconds
The supported codecs depend on the software release in use. As a minimum, the
ITU–T G.711 A-law, µ-law (64 kbit/s) and ETSI GSM full rate codec (13 kbit/s) is sup-
ported.
Note: The IRG/ITA will accept any packet size less than or equal to the maximum size
and it will send with the preferred packet size if this is smaller than the peer’s
maximum packet size.
10.14.2 G711 A codec options
G711 A 64kb
G711 A 64kb enables the ITU–T G.711 A-law codec for 64 kbit/s rate.
Default: On
G711 A 64kb priority
G711 A 64kb Priority prioritizes the ITU–T G.711 A-law codec for 64 kbit/s rate with
respect to the other enabled codecs.
Default: 1
Note: This priority value must be unique within the set of enabled codecs.
G711 A 64kb preferred
G711 A 64kb Preferred sets the preferred amount of data contained in one media
packet sent from the IRG/ITA.
Default: 30
Note: The unit is milliseconds. The value must be less than or equal to the corre-
sponding parameter G711 A 64kb Max.
G711 A 64kb max
G711 A 64kb Max sets the maximum amount of data contained in one media packet
that the IRG/ITA is willing to receive from the peer.
Default: 60
Note: The unit is milliseconds. The value must be greater than or equal to the corre-
sponding parameter G711 A 64kb Preferred.
G711 A 64kb DTX
G711 A 64kb DTX enables the discontinuous transmission function (DTX) for the
associated codec.
Default: off
10.14.3 G711 µ codec options
G711 µ 64kb
G711 µ 64kb enables the ITU–T G.711 µ-law codec for 64 kbit/s rate.
Default: On
G711 µ 64kb priority
G711 µ 64kb Priority prioritizes the ITU–T G.711 µ-law codec for 64 kbit/s rate with
respect to the other enabled codecs.
Default: 2
G711 µ 64kb preferred
G711 µ 64kb Preferred sets the preferred amount of data contained in one media
packet sent from the IRG/ITA.
Default: 30
Note: The unit is milliseconds. The value must be less than or equal to the corre-
sponding parameter G711 µ 64kb Max.
G711 µ 64kb max
G711 µ 64kb Max sets the maximum amount of data contained in one media packet
that the IRG/ITA is willing to receive from the peer.
Default: 60
Note: The unit is milliseconds. The value must be greater than or equal to the corre-
sponding parameter G711 µ 64kb Preferred.
G711 µ 64kb DTX
G711 µ 64kb DTX enables the discontinuous transmission function (DTX) for the
associated codec.
Default: off
Controlled from:Web, EM
10.14.4 GSM codec options
GSM
GSM enables the ETSI GSM full rate codec for 13 kbit/s rate.
Default: On
GSM priority
The parameter GSM Priority prioritizes the ETSI GSM full rate codec for 13 kbit/s rate
with respect to the other enabled codecs.
Default: 3
GSM preferred
The parameter GSM Preferred sets the preferred amount of data contained in one
media packet sent from the IRG/ITA.
Default: 1
Note: The unit is GSM frames. The value must be less than or equal to the corre-
sponding parameter GSM Max. One GSM frame corresponds to 20ms of speech.
GSM max
The parameter GSM Max sets the maximum amount of data contained in one media
that packet the IRG/ITA is willing to receive from the peer.
Default: 3
Note: The unit is GSM frames. The value must be greater than or equal to the corre-
sponding parameter GSM Preferred.
GSM DTX
The parameter GSM DTX enables the discontinuous transmission function (DTX) for
the associated codec.
Default: off
Note: Besides the standard codecs, this release also supports the G.723.1 codec. This
codec is supported through a special license agreement.
10.14.5 G723 codec options
G723
G723 enables the ITU-T G.723 codec.
Default: off
G723 priority
G723 Priority prioritizes the ITU-T G.723 codec with respect to the other enabled
codecs.
Default: 4
Note: The prioritization parameter must be unique within the set of enabled codecs.
G723 preferred
G723 Preferred sets the preferred amount of data contained in one media packet sent
from the IRG/ITA.
Default: 1
Note: Please note regarding G723 preferred:
The unit is G.723 frames; the value must be less than or equal to the corre-
sponding parameter G723 Max.
One G723 frame corresponds to 30ms of speech.
G723 max
G723 Max sets the maximum amount of data contained in one media packet the
IRG/ITA is willing to receive from the peer.
Default: 2
Note: The unit is G.723 frames; the value must be greater than or equal to the corre-
sponding parameter G723 Preferred.
G723 DTX
G723 DTX enables the discontinuous transmission function (DTX) for the associated
G723 codec.
Default: off
10.14.6 G729 codec options
G729
G729 enables the ITU-T G.729 codec.
Default: off
G729 priority
G729 Priority prioritizes the ITU-T G.729 codec with respect to the other enabled
codecs.
Default: 5
Note: The prioritization parameter must be unique within the set of enabled codecs.
G729 preferred
G729 Preferred sets the preferred amount of data contained in one media packet sent
from the IRG/ITA.
Default: 3
Note: Please note regarding G729 preferred:
The unit is G.729 frames; the value must be less than or equal to the corre-
sponding parameter G729 Max.
One G.729 frame corresponds to 10ms of speech.
G729 max
G729 Max sets the maximum amount of data contained in one media packet the
IRG/ITA is willing to receive from the peer.
Default: 6
Note: The unit is G.729 frames; the value must be greater than or equal to the corre-
sponding parameter G729 Preferred.
G729 DTX
G729 DTX enables the discontinuous transmission function (DTX) for the associated
G729 codec.
Default: off
10.14.7 T38 facsimile protocol

The T38 facsimile protocol can be enabled/disabled.
Default: on
Controlled from:Web, EM
Note: T38 is only supported by the H.323 and SIP protocols.
10.14.8 Echo Cancellation

The echo cancellation feature can be enabled/disabled.
Default: on
Vood 100 & 200 Configuration Manual SNMPv2 Support
11 SNMPv2 Support
This release of i3 Vood supports applicable parts from
SNMPv2-MIB, RFC 1907
IF-MIB, RFC 2863.
UPS-MIB, RFC 1628. (Only supported by Vood 292)
Note: SNMP is only applicable to Vood x42 and Vood 292.
12 Additional EM Configuration
This chapter contains information about the parameters that are ONLY configurable
from the EM.
12.1 EM-Configured Security Parameters
12.1.1 EM-Configured parameters: user privileges
Start webserver
This parameter enables the activation of the webserver.
Default: on
Enable root web pages
This parameter enables the possibility of accessing the root pages. The “root” pages
are currently only used for debugging and internal testing and shouldn’t be available
for the end user.
For access : http://”terminal IP address”/
Default: off
Enable conf web pages
This parameter enables the possibility of accessing the configuration pages.
For access : http://”terminal IP address”/Conf
Default: on
Vood 100 & 200 Configuration Manual Additional EM Configuration
Enable user web pages
This parameter enables the possibility of accessing the user pages.
For access : http://”terminal IP address”/User
Default: on
Enable analog Conf
This parameter enables the possibility of configure the IRG/ITA via an analog phone.
Default: on
Note: When this parameter is set to “off” the end-user cannot configure parameters
using the telephone (although they can still listen to current parameter values).
The end-user will, however, still be able to reset passwords using the tele-
phone.
12.1.2 EM-configured parameters: username and passwords
The syntax for username and password configuration is <username:password>
Root pages
Default: -
Conf pages
Default: Conf:admin
User pages
Channel A
Default: SubA:SubA
Channel B
Default: SubB:SubB
Note: Channel B is not applicable to the Vood 111 and Vood 121.
12.2 EM-Configured Services Parameters
12.2.1 EM-Configured parameters: enable call diversion

Enables service call diversion. See “Call diversion” on page 25.
Default: on
12.2.2 EM-Configured parameters: enable call waiting

Enables service call waiting. See “Call waiting” on page 23.
Default: on
In addition to just enabling the call waiting service, you can also configure the default
values for the special service "On busy set call waiting for X seconds".
12.2.3 EM-Configured parameters: enable answering machine

Enables service answering machine. See “Answering Machine Service” on page 26.
Default: on
12.2.4 EM-Configured parameters: anonymous call
Allow anonymous call end user configuration
This parameter allows the end user to be able to configure anonymous call via the
user pages. See ”Vood IRG/ITA User Guide.”.
Default: on
Enable always anonymous call
Enables service always anonymous call: all calls placed will be anonymous, i.e, it will
be unnecessary to enter the “anonymous call supplementary code” first. See “Service
Calling Line ID Restriction for Anonymous Calling” on page 29.
Default: off
12.2.5 EM-Configured parameters: Caller ID
Swap name and number
This parameter allows the operator to change the order of Name and Number for the
CID presentation.
Default: 0 (Number is sent first)
12.2.6 EM-Configured parameters: supplementary service codes
Supplementary Service Code Transparent mode
An operator can use the Element Manager to configure whether or not the processing
of service codes (in call setup/INVITE messages) should be peformed by the IRG/ITA
or by the proxy server. With the default “off” setting all service code entries are pro-
cessed by the local IRG/ITA and only the normal phone call data is transmitted to the
proxy server. When this setting is “on” the service codes are not processed at all by
the IRG/ITA , all the raw data is forwarded to the proxy server as entered and the
proxy server will execute the indicated service.
Default: off
Multipart Transparent mode
An operator can use the Element Manager to configure whether or not the processing
of multipart services — R1, R2 (hook flash), etc. — should be peformed by the
IRG/ITA or by the proxy server. With the default “off” setting any R-button (hook
flash) service code entry is processed by the local IRG/ITA and only the normal phone
call data is transmitted to the proxy server. When this setting is “on” the multipart
service codes are not processed at all by the IRG/ITA, all the raw data is forwarded
to the proxy server as entered and the proxy server will execute the indicated ser-
vice.
Default: off
Dynamic service codes
Each operator can use the Element Manager to configure “their own” (country spe-
cific) supplementary service codes. This is useful since different countries have their
own set of codes for call diversion, call waiting, etc.
Default: Swedish standard codes
Note: Not applicable for MGCP.
12.3 EM-Configured User Behavior Setting Parameters
12.3.1 EM-Configured parameters: Called Party OnHook Timeout
The Called Party OnHook Timeout feature allows you to hang up one phone and pick
up another phone within a specified time period without disconnecting the call. You
will be able to do this only when receiving a call. The feature does not apply to the
calling party at the other end.
This parameter specifies how long you can hang up on an incoming call without the
call disconnecting. The acceptable range is 0 - 90 seconds.
Default: 0
Note: Only applicable for SIP and H.323.
12.3.2 EM-Configured parameters: optional incoming call prefix
In the case of an incoming call, a prefix can be added to the number. This could be
useful if one or more digits are being stripped (due to whatever reason) in the net-
work and you still want the user call list to work properly
Default: -
Note: Only applicable for H323.
12.4 EM-Configured System Parameters
12.4.1 EM-Configured parameters: diffserv configuration
The TOS value can be configured for RTP media and UDP signalling.
Default: -
12.4.2 EM-Configured parameters: EM server connection
Vood terminals poll the Centre EM
When a terminal is located behind NAT, there’s no way for the EM to initiate contact
with the terminal.
This is solved by having the terminal poll the EM at regular intervals for new software
and/or new configuration.
Enable poll of EM
Enables poll of EM by the terminal.
Default: on
Start time for poll
The start time for the first poll may be set to a number between 0- 23 (inclusive) rep-
resenting an hour of the day. Polling will then periodically take place at regular inter-
vals.
A random time of +- 2 hour is also added.
Default: 3 (03:00 AM)
Example:
If the start time is set to 13, then, at some time between 11:00 - 15:00, the ter-
minal will poll the EM for new software and/or a new configuration.
Poll interval
This parameter controls how often the terminal should poll the EM. The interval can
be set to once every 3, 6, 12, 24, 48, 96, or 168 hours.
Default: 24 hours
Example:
If poll interval is set to 48, then the terminal will poll the EM every other day for
new software and/or a new configuration.
Triple play services path
For an incoming call to be presented on a TV screen, a path to the service in EM must

be specified.
Default: -
12.4.3 EM-Configured parameters: IGMP
Enable IGMP Support
This parameter enables or disables the IGMP support.
Default: On
Note: Only applicable for Vood x42 and Vood 292.
12.4.4 EM-Configured parameters: Jitter buffer control
Min and Max values for the jitter buffer can be configured from EM. Also the jitter
buffer margin for FAX/Data connections can be configured.
Note: Do NOT change the default values unless you’re sure of what you are doing.
Max Jitter buffer
Default: 150 (ms)
Min Jitter buffer
Default: 10 (ms)
Target Jitter Buffer Margin
Default: 100 (ms)
12.5 EM-Configured H323 Parameters

This chapter is only valid for terminals with H.323 software.
12.5.1 EM-Configured parameters: Alternative Gatekeeper (CCS)
An alternative gatekeeper can be configured. If no contact is established with the pri-

mary gatekeeper , this secondary address will be used (if configured).
Default: -
12.6 EM-Configured SIP Parameters

This chapter is only valid for terminals with SIP software.
12.6.1 EM-Configured parameters: device description
Each operator can use the Element Manager to configure “their own” device descrip-
tion, i.e. the text specified in the SIP Header field User-Agent.
Default: -
12.6.2 EM-Configured parameters: ptime
The SIP parameter ptime can be configured.
Default: 30
12.7 EM-Configured MGCP Parameters

This chapter is only valid for terminals with MGCP software
12.7.1 EM-Config parameters: ignore call agent echo cancellation control
An operator can use the Element Manager to configure whether or not the IRG/ITA
should ignore call agent echo cancellation disable/enable orders.
Default: off
Vood 100 & 200 Configuration Manual Known Limitations
13 Known Limitations
The known limitations of this i3 Vood release are:
DTX in forward direction is not implemented for the G.711 codecs.
Support for country specific SLIC configuration is only supported by software

release and not resolved run-time for the Vood 122.
Only the FSK Standards ETSI (Europe), BT (UK), CCA (UK), Telcordia (USA),
and TIA (USA) are supported.
Note: If there are other FSK standards you would like to see supported, please con-
tact tech@i3micro.com
Vood 100 & 200 Configuration Manual Zone Codes
Appendix A:
Zone Codes
This Appendix contains a list of regions/countries and their corresponding time zone
code. The list starts with countries that are -12 hours ahead of GMT (12 hours ahead
of London). This list is by no means complete.
Zone Code Region/Country
LINT Line Islands (Kiribati)
PHOT Phoenix Islands (Kiribati)
TOT Tonga
CHAST Chatham Island (New Zealand)
WFT Wallis & Futuna
WAKT Wake
TVT Tuvalu
NRT Nauru
MHT Marshall Islands
KOST Kosrae (Micronesia)
GILT Gilbert Islands (Kiribati)
FJT Fiji
NZST New Zealand
NFT Norfolk (Australia)
SBT Solomon Islands
PONT Ponape (Micronesia)
March 2005 Vood 100 & 200 Configuration Manual Version 6.0G A-81 (108)
NCT New Caledonia
VUT Vanuatu
LHST Lord Howe Island (Australia)
YAPT Yap (Micronesia)
TRUT Truk (Micronesia)
PGT Papua New Guinea
MPT Mariana Islands
ESTA Eastern Australia
CST Central Australia
PWT Palau
KST Korea
JAYT Jayapura (Indonesia)
JST Japan
WST Western Australia
ULAT Ulan Bator (Mongolia)
SGT Singapore
PHT Philippines
MYT Malaysia
BNT Brunei
BORT Borneo (Indonesia)
CST China
CXT Christmas Island (Australia)
JAVT Java (Indonesia)
ICT Indochina
CCT Cocos (Australia)
MMT Myanmar (formerly Burma)
LKT Sri Lanka
BTT Bhutan
ALMT Alma-Ata (Kazakhstan)
BDT Bangladesh
NPT Nepal
IST India
UZT Uzbekistan
TMT Turkmenistan
TJT Tajikistan
MVT Maldives
KGT Kyrghyzstan
IOT British Indian Ocean Territory
GET Georgia
AQTT Aqtobe (Kazakhstan)
PKT Pakistan
AFT Afghanistan
SCT Seychelles
RET Reunion
AZT Azerbaijan
AMT Armenia
GST Gulf
IRT Iran
EAT Eastern Africa
AST Arabia
MSK Moscow
SAST South Africa
EET Eastern Europe
CAT Central Africa
IST Israel
WAT Western Africa
MEZ Germany
CET Central Europe
UTC Universal Coordinated
WET Western Europe
GMT Greenwich Mean/British Summer
EGT Eastern Greenland
AZOT Azores (Portugal)
FST Fernando de Noronha (Brazil)
WGT Western Greenland
ART Argentina
NST Newfoundland
AST Atlantic
HNE Quebec
EST Eastern
CST Central
MST Mountain
PST Pacific
PNT Pitcairn
GAMT Gambier Islands (French Polynesia)
AKST Alaska
MART Marquesas Islands (French Polynesia)
CKT Cook Islands (New Zealand)
TKT Tokelau
TAHT Tahiti (French Polynesia)
GST Guam
HAST Hawaii-Aleutians
HST Hawaii
WST Western Samoa
NUT Niue
SST American Samoa
Vood 100 & 200 Configuration Manual Troubleshooting
Appendix B:
Troubleshooting
This appendix contains basic advice on troubleshooting the Vood IRG/ITA unit.
Table 1: Hardware troubleshooting
Boot stage Possible cause Suggested action
Hardware test fails. RAM error. Contact an i3micro representative.
The boot sequence No link to Ethernet. Connect cable and reboot.

halts at the stage
where the unit’s LEDs
flash four times,
repeatedly.
Table 2: Software troubleshooting
Possible cause Suggested action
The boot sequence Error in configuration. Check the configuration.

halts at the stage
where the unit’s LEDs
flash four times,
repeatedly.
Can’t login on terminal Wrong IP configuration Verify the IP configuration via analog
web-server telephone
Can’t login on terminal Wrong path Use path:

web-server http://”terminal IP address”/Conf
for configuration pages
Use path:
http://”terminal IP address”/User
for user pages
Can’t login on terminal Wrong password Reset the password via analog telephone
web-server
General problems with Too old web browser is Upgrade your web-browser
the WEB-GUI used
March 2005 Vood 100 & 200 Configuration Manual Version 6.0G B-87 (108)
Appendix C:
H.323
1 Introduction
This document describes the features and parameters of this H.323 release. The fea-
tures are described from the operator’s and the subscriber’s perspective.
A detailed description of the services and how they are controlled is included in this
document.
H.323 parameters and their settings options may change from one Vood software
release to another, so i3 will periodically issue H.323 configuration documentation
updates to keep you informed.
For more information about the EM, see the separate document, i3 Centre User
Guide.
2 Configuration
The parameters described in this document can only be configured using the built-in
web server of the IRG/ITA unit, or by auto provisioning from the Element Manager
management system in the product i3 Centre or Vood Element Manager. This docu-
ment describes the web server configuration interface. The auto-provisioning inter-
face is described in a separate document, the Vood Operator’s Manual.
2.1 Web Configuration

For instructions about how to access the web configuration utility of the IRG/ITA unit,
see 7.2.1 “Using the web configuration utility” of the manual.
3 Phone Number Configuration
Phone Number A
Phone Number A is the phone number associated with the analog interface marked
‘A’ (for Vood 111 the connector is marked ‘Phone’).
Example: 085063880
Default: –
March 2005 Vood 100 & 200 Configuration Manual Version 6.0G C-88 (108)
Vood 100 & 200 Configuration Manual H.323
Phone Number B
Phone Number B is the phone number associated with the analog interface marked
‘B’ (not valid for Vood 111).
Example: 085063880
Default: –
4 H.323
Applicable parts of ITU H.323 v.2 are supported in this release.
FastStart procedure with multiple OpenLogicalChannel structures.
H.235 Annex J Authentication using HMAC-SHA1-96 or HMAC-SHA1-160
FAX through G.711 pass through (automatic switch to G.711)
H.245
H.245 Tunneling
DTMF through H.245 User Input Indication.
Alternative Gatekeeper
4.1 H.323 Parameters

The parameters described below are found in the <H.323> page of the <configura-
tion> web page.
All parameters that specify a port address allow a range ports to be specified. If a sin-
gle port number is required, then the range must start and end with the same value,
e.g. 1720–1720.
Port addresses for different parameters must not overlap. Ports that are used to con-
tact the gatekeeper are determined by the H.323 standard, and also published by the
gatekeeper (CCS, Call Control Server).
4.1.1 CCS address

CCS address is the IP address to the Gatekeeper (Call Control Server), where the
H.323 endpoints of the IRG/ITA will register. The CCS address can be in either FQDN
or in ‘dotted quad’ format (xxx.xxx.xxx.xxx).
Default: –
Controlled from: Web, EM, Phone
Phone code to set:
Note: Only the dotted quad format (xxx.xxx.xxx.xxx) can be used when setting the
CCS address via phone.
4.1.2 Time to live

Time To Live decides the suggested re-registration time-out of the IRG/ITA end-
points. The unit is seconds.
Default: 800
4.1.3 Authentication
Enable authentication
Enable Authentication turns the authentication mechanism on or off.
Note: If this feature is set to ‘on’, the gatekeeper must support this function and the
keys must be distributed from the service provider.
Default: off
Authentication key
Authentication Key contains the authentication key/password. The value for this
parameter, if used, is supplied from the service provider.
Default: –
Authentication Method
Authentication Method contains the authentication method to be used. Either of two

methods can be chosen:
HMAC-SHA1-96 (H.235 compliant)
HMAC-SHA1-160 (proprietary)
Default: HMAC-SHA1-96
4.1.4 Enable fast start

Enable Fast Start decides if the H.323 procedure Fast Connect is going to be used or
not.
Default: on
Note: Even if this parameter is set, the H.245 procedures can be initiated depending
on the outcome of the Fast Connect procedure.
4.1.5 Enable H.245 Tunneling

Enable H.245 Tunneling decides if the H.245 tunneling will be used or not.
Default: off
4.1.6 Disable RAS Channel

Disable RAS Channel decides if the H.323 RAS channel is going to be used or not.
Default: off
4.1.7 Network Generated Dial Tone

Network Generated Dial Tone, the network generates the dial tone. A setup is sent
immediately after off hook to the CCS, i.e. same principle as Hotline without the need
of a Hotline configuration.
Default: off
4.1.8 RAS port range

RAS Port Range sets the port numbers that can be used for the H.323 RAS channel.
Default: 1719–1719
4.1.9 H225 port range

The H225 Port Range parameter sets the port numbers that can be used for the H225
channel.
Default: 1720–1720
4.1.10 H245 port range

H245 Port Range sets the port numbers that can be used for the H245 channel.
Default: 2000–2010
4.1.11 RTP port range

RTP Port Range sets the port numbers that can be used for the RTP media channel.
All media channels use the same RTP port range. The range must start at an even
number and end at an odd number. Use a range equal to or greater than 8, and port
numbers larger than 1024.
Default: 10000–10007
4.1.12 H.323 ID
H.323 ID is the H.323 identity.
Default: –
4.2 User Input Handling

User input handling refers to the sending of information about which buttons a user
has pushed (0–9, #, *, the R-button).
The sending of this information from the IRG/ITA can be configured in four different
ways:
The sending is fully H.323 compliant. The information is sent using the H.245
UserInputIndication message. The alphanumeric format is used.
The information is sent using the H.245 UserInputIndication message. The sig-
nal format is used.
The information is sent using DTMF in-band (in the media stream). It is not
sent using the H.245 UserInputIndication message.
The information is sent using the Q.931 Information message.
5 Known Limitations
The known limitations of this H.323 release are the following:
For the Vood 122, support for country specific SLIC configuration is only sup-
ported by software release, and is not resolved at run-time.
Only the FSK standards ETSI (Europe), BT (UK), CCA (UK), Telcordia (USA),
Appendix D:
SIP
1 Introduction
This document describes the features and parameters of this SIP release. The fea-
document.
SIP parameters and their settings options may change from one Vood software
release to another, so i3 will periodically issue SIP configuration documentation
Guide.
2 Configuration
management system of the product i3 Centre or Vood Element Manager. This docu-
face is described in a separate document, the Vood Operator’s Manual.

For instructions about how to access the web configuration utility of the IRG/ITA,
see“Using the web configuration utility” on page 16 of the manual.
March 2005 Vood 100 & 200 Configuration Manual Version 6.0G D-94 (108)
Vood 100 & 200 Configuration Manual Phone Number Configuration
3 Phone Number Configuration
Phone Number A
Phone Number A is the phone number/SIP user for the SIP account associated with
the analog interface marked ‘A’ (for Vood 111 the connector is marked ‘Phone’).
Example 1: 085063880
Example 2: john.doe
Default: –
Phone Number B
Phone Number B is the phone number/SIP user for the SIP account associated with
the analog interface marked ‘B’ (not valid for Vood 111).
Example 1: 085063880
Example 2: john.doe
Default: –
4 SIP
Applicable parts of SIP RFC 3261 are supported in this release.
Authentication using digest MD5.
Record route/route
UDP transport, including retransmission.
TCP transport.
Early media support.
Support for DNS SRV records.
4.1 SIP Parameters

Parameters concerning the SIP protocol are accessed through a SIP web page of the
IRG/ITA. The parameters described below are found in the <SIP Configuration> page
of the <configuration> web page.
Vood 100 & 200 Configuration Manual SIP
Note: Since the Vood 122/Vood x42/Vood 292 has more than one analog channel, you
can now configure different "Registration Server"/"Outbound proxy" for each
channel. If "Registration Server B"/"Outbound proxy B" is left "blank", channel
A's parameter will be used IF "Registration On/Off channel B" is "On".
Some parameters that specify a port address allow a range ports to be specified. If a
single port number is required, then the range must start and end with the same
value, e.g. 1720–1720.
Port addresses for different parameters must not overlap. Ports that are used to con-
tact the registrar or proxy are determined by the SIP standard.
4.1.1 Registration on/off channel A

Registration on off is the parameter that controls if registration will be performed or
not.
Default: on
4.1.2 Registration server channel A

Registration server is the address of the SIP Registrar, where the SIP clients of the
IRG/ITA will register. The parameter consists of IP address or host name of the SIP
Registrar. Optionally, a port number can be specified.
FormatIP address|host name[:port]
Example:
10.0.0.17:5061
proxyname.com
Default: –
4.1.3 Registration interval channel A

Registration interval decides the re-registration time-out of the IRG/ITA clients. The
unit is seconds.
Default: 3600
4.1.4 Outbound proxy channel A

Outbound proxy is the address of the proxy, where the SIP clients of the IRG/ITA will
route the SIP messages. The parameter consists of IP address or host name of the
SIP Registrar. Optionally, a port number can be specified.
Format: IP address|host name[:port]
Example:
10.0.0.17:5061
proxyname.com
Default: –
4.1.5 Registration on/off channel B

Registration on off is the parameter that controls if registration will be performed or
not.
Default: on
4.1.6 Registration server channel B

Registration server is the address of the SIP Registrar, where the SIP clients of the
IRG/ITA will register. The parameter consists of IP address or host name of the SIP
Registrar. Optionally, a port number can be specified.
FormatIP address|host name[:port]
Example:
10.0.0.17:5080
proxyname.com
Default: –
4.1.7 Registration interval channel B

Registration interval decides the re-registration time-out of the IRG/ITA clients. The
unit is seconds.
Default: 3600
4.1.8 Outbound proxy channel B

Outbound proxy is the address of the proxy, where the SIP clients of the IRG/ITA will
route the SIP messages. The parameter consists of IP address or host name of the
SIP Registrar. Optionally, a port number can be specified.
Format:IP address|host name[:port]
Example:
10.0.0.17:5081
proxyname.com
Default: –
4.1.9 SIP port

SIP Port sets the port where the IRG/ITA listens for SIP messages.
Default: 5060

RTP Port Range sets the port numbers that can be used for the RTP media channel.
For each simultaneous call, four RTP Ports will be needed. The number of ports spec-
ified by the RTP Port Range parameter should therefore be a multiple of four.
All media channels use the same RTP port range. The range must start at an even
number and end at an odd number. Use a range equal to or greater than 8, using port
numbers larger than 1024.
Default: 10000–10007
4.1.11 Username
Username is the MD5 digest authentication user. The value for this parameter, if
used, is supplied by the service provider.
Default: –
4.1.12 Password
Password contains the MD5 digest authentication password. The value for this
parameter, if used, is supplied by the service provider.
Default: –
4.1.13 Transport Protocol

Choose the preferred protocol, UDP or TCP. The IRG/ITA listens for both protocols.
Default: UDP
4.1.14 SIP Telephone Syntax (RFC 2806)
Enables usage of telephone syntax for outgoing calls from Vood (RFC 2806). Could be
enabled when the IRG/ITA is interoperating with other devices with RFC 2806 support
(tel-URI addressing format).
Default: Off
4.1.15 DTMF Generation
RFC 2976 DTMF Generation (SIP INFO Method)
Enables or disables outband RFC 2976 DTMF generation (SIP INFO method). If RFC
2976 is enabled, inband DTMF generation and outband RFC 2833 DTMF generation
will be disabled.
Default: Off
Dynamic Payload Type for DTMF, RFC 2833 (end of tone retransmission)
Support for propagation of DTMF and fax tones using the IETF standard RFC 2833.
RFC 2833 is a protocol for transmission of DTMF and other tones. According to this
protocol, the last packet, indicating that a tone has ended, should be retransmitted
three times. This is done to make sure that a receiver actually detects the end of tone
indication in poor networks. However, some vendors’ equipment does not handle
these redundant packets; instead they cause an unpleasant noise. In such cases, the
retransmission mechanism can be turned off, or be set to a lower value.
Default: 3
5 Known Limitations
The known limitations of this SIP release are the following:
ported by software release, and is not resolved at run-time.
You can’t place call between two IRG/ITA’s behind the same NAT if the Regis-
tration Server/proxy is located outside the NAT. (Direct calls between the two
terminals is of course possible).
Symmetrical NAT routers are not supported.
Only the FSK standards ETSI (Europe), BT (UK), CCA (UK), Telcordia (USA),
Vood 100 & 200 Configuration Manual MGCP
Appendix E:
MGCP
1 Introduction
This document describes the features and parameters of this MGCP release. The fea-
document.
MGCP parameters and their settings options may change from one Vood software
release to another, so i3 will periodically issue MGCP configuration documentation
Guide.
2 Configuration
management system In the product i3 Centre or Vood Element Manager. This docu-
face is described in the separate document, the Vood Operator’s Manual.

For instructions about how to access the web configuration utility of the IRG/ITA unit,
see “Using the web configuration utility” on page 16 of the manual.
2.2 Analog Configuration

After startup, the terminal starts a continues flashing where the LED is on for 500ms
and off for 100ms. From the time this blink sequence starts you have 30 seconds to
activate the IVR function:
Lift the handset. You will hear a stutter dial tone instead of normal dial tone. To acti-
vate the IVR function, press the hash key four times: .
A successful activation is indicated by a short confirmation tone.
To use the IVR configuration utility on the phone, see “Using the phone interface” on
page 19 in the guide.
When you are finished using the IVR function you can either reboot the terminal, or
press and hang up the handset. The latter will cause the terminal to try
to register itself with the Call Agent the usual way.
March 2005 Vood 100 & 200 Configuration Manual Version 6.0G E-101 (108)
3 MGCP
Applicable parts of MGCP RFC 2705 are supported in this release.
Support for MGCP communication using the NCS 1.0 profile.
FAX through G.711 pass through (automatic switch to G.711)
3.1 MGCP Parameters

MGCP protocol parameters are accessed through a MGCP web page on the terminal.
The parameters described below can be found in the <MGCP Configuration> page of
the <configuration> web page.
Some parameters that specify a port address allow a range ports to be specified.
Port addresses for different parameters must not overlap.
It must be noted that the port numbers are the port numbers used as own ports by
the endpoint in the Terminal. Ports that are used to contact the Call Agent are deter-
mined by the MGCP standard.
3.1.1 Call agent

The Call Agent parameter specifies the address to the Call Agent. It will be used as
the provisioned Notified Entity. The parameter must be set to a valid Call Agent
address. If a host name is used, this must be a name that can be resolved using a
DNS.
Format: [name@] IP address | host name[:port]
The default port value is 2727.
Example:
localname@mycallagent.host.se
10.0.0.230:2527
ca.host.com
Default: –
3.1.2 End point name A

The End Point Name A parameter specifies the name of the end point representing
line A. The parameter must be set to a name that matches what has been configured
in the Call Agent for this gateway. If End Point Name A is set to empty string no reg-
istration will be done for the end point (and the end point can not be used).
Format: namestring
Example:
aaln/1
a001
Default: aaln/1
3.1.3 End point name B

The End Point Name B parameter specifies the name of the end point representing
line B. The parameter must be set to a name that matches what has been in the Call
Agent for this gateway. If End Point Name B is set to empty string no registration will
be done for the end point (and the end point can not be used).
Format: namestring
Example:
aaln/2
a002
Default: aaln/2
Note: This parameter is not applicable to the Vood 111 product (since this product has
only one line interface).
3.1.4 Phone number A

The Phone Number A parameter specifies the phone number for line A. The parame-
ter is only used for the UVM service and is therefore only visible if the UVM service is
enabled. The phone number is used in the voice mail so it's easy to see where the
mail comes from. The parameter is NOT used for any MGCP specific data.
Format: digits
Example:
8522727
Default: 11111
3.1.5 Phone number B

The Phone Number B parameter specifies the phone number for line B. The parame-
ter is only used for the UVM service and is therefore only visible if the UVM service is
enabled. The phone number is used in the voice mail so it's easy to see where the
mail comes from. The parameter is NOT used for any MGCP specific data.
Format: digits
Example:
522728
Default: 22222
Note: This parameter is not applicable to the Vood 111 product (since this product has
only one line interface).
3.1.6 AM trigger
The AM Trigger parameter specifies what MGCP events should trigger the UVM to
start. The parameter is only used for the UVM service and is therefore only visible if
the UVM service is enabled. The events that can be chosen from is: l/rg (ring signal),
l/r0-r7 (distinctive ringing). It's up to the call agent how the different distinctive ring
signals are used so you need to know how your call agent are using them to specify
the correct AM triggers. If you don't know use only the l/rg event. If more than one
event is specified use a comma sign as delimiter.
Format: string
Example:
l/rg
l/rg,l/r0,l/r5
l/rg,l/r0,l/r1,l/r2,l/r3,l/r4
Default: l/rg
3.1.7 Gateway name

The Gateway Name parameter specifies the name of the gateway.
The parameter must be a name that matches what has been configured in the Call
Agent for this gateway.
If no value is specified, the gateway will try to find out it's name using a DNS reverse
lookup. If the reverse lookup fails the gateway name will be set to the gateways MAC
address if DHCP is used or to the gateways IP address if a fixed IP address is used.
Format: namestring
Example:
gateway1.host.com
Default: MAC Address, IP address, or a successful DNS reverse lookup.
3.1.8 Use NCS (on/off)

The Use NCS parameter specifies if the NCS 1.0 profile should be used or not. This
should only be on if your call agent requires NCS.
Default: Off
3.1.9 Use DNS (on/off)

The Use DNS parameter specifies if the DNS should be used to resolve the MGCP noti-
fied entity parameter or not. This should only be on if you know that your call agent
is sending notified entity parameters that are possible to resolve using DNS or if your
call agent are only sending IP addresses in the notified entity parameter.
Default: Off
3.1.10 Use NSE (on/off)

The Use NSE is a parameter that controls if you should use RFC 2833 or the Cisco
variant called NSE for transferring of phone events over the media channel. The dif-
ference between the two is that event number 192 and 193 is used for fax detection
events in the NSE case instead of event number 32 and 33 for RFC 2833.
Default: Off (i.e. use RFC 2833)
3.1.11 Min interval (ms)

The Min Interval parameter specifies the minimum retransmission interval.
This is the time it takes for the first retransmission to take place. The next retrans-
mission will take place at Min Interval * 2, until Max Interval has been reached. The
unit is milliseconds.
Format: digits
Example:
500 // Wait half a second until first retransmission
Default: 500
3.1.12 Max interval (ms)

The Max Interval parameter specifies the maximum retransmission interval.
This will be the longest time interval until next retransmission will take place. Next
retransmission will take place at Min Interval * 2 until Max Interval has been reached.
If a provisional response is received during retransmission all following retransmis-
sions will take place at max interval. The unit is milliseconds.
Format: digits
Example:
4000 // Longest retransmission interval is 4 seconds
Default: 4000
3.1.13 Max attempts

The Max Attempts parameter specifies the maximum number of retransmission
attempts before the gateway is going into disconnection state.
With Min Interval set to 500, Max Interval to 4000, and Max Attempts to 6, the
retransmissions will take place at 0.5, 1.0, 2.0, 4.0, 4.0, and 4.0 seconds.
So with the example values the gateway will after 15.5 seconds without responses
from the Call Agent enter a disconnection state where it tries to get in contact with
the Call Agent again using restart in progress messages.
Format: digit
Example:
Default: 6
3.1.14 Gateway port

The Gateway Port parameter specifies the port that the gateway will listen on for
MGCP messages.
This should normally be 2427, since that is the value used by Call Agents.
Format: digits
Example:
2527
Default: 2427

RTP Port Range sets the port numbers that will be used for the RTP media channels.
For each simultaneously call, two ports will be needed. The number of ports specified
by the RTP Port Range should therefore be a multiple of two. All media channels
regardless of phone line use the same port range. The range must start at an even
number and end at an odd number. Use a range equal to or greater than 8, using port
numbers larger than 1023 and less than 65536.
Default: 10000–10007
3.2 Dynamic Payload Type for DTMF, RFC 2833

We now support propagation of DTMF and fax tones using the IETF standard RFC
2833.
This includes negotiation in the MGCP/SDP protocol of what tones should be propa-
gated in this way.
3.2.1 RFC 2833 (end of tone retransmission)

RFC 2833 is a protocol for transmission of DTMF and other tones. According to this
protocol, the last packet, indicating that a tone has ended, should be retransmitted
three times. This is done to make sure that a receiver actually detects the end of tone
indication in poor networks. However, some vendors equipment does not handle
these redundant packets, instead they cause a unpleasant noise. In such cases, the
retransmission mechanism can be turned off, or be set to a lower value.
Default: 3
4 Known Limitations
The known limitations of this MGCP release are the following:
ported by software release and is not resolved at run-time.
Only FSK Standards: ETSI (Europe), BT (UK), CCA (UK), Telcordia (USA), TIA
(USA) are supported.

Vood 100 200 Config

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Vood 100 200 Config

Transféré par

Droits d'auteur :

Formats disponibles

Configuration Manual

for the Vood 100 & 200 Series

This product is developed and manufactured by i3 micro technology.

Copyright© 2005 i3 micro technology ab, Sweden.

1.2 Target Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

1.3 Document Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

1.4 Support Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

1.5 Standard Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

2 Abbreviations and Conventions . . . . . . . . . . . . . . . . . . . . . . . 3

5.3 Boot Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

5.4 Additional DHCP Server Configuration . . . . . . . . . . . . . . . . . . . . . . 14

6.2 During Normal Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

7 Manual IRG/ITA Configuration . . . . . . . . . . . . . . . . . . . . . . . 16

7.2 Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

7.3 Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

7.3.2 Password reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

8.2 Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

8.5 Message Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

8.6 Three-Way Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

8.7 Click to Dial Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

8.8 Fast Re-Dial Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

8.9 Diversion Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

8.11 Caller ID Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

9 Protocol Specific Configuration. . . . . . . . . . . . . . . . . . . . . . . 30

10 Parameters and Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

10.2 Country Specific Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

10.5 Switch Configuration for Vood 121 . . . . . . . . . . . . . . . . . . . . . . . . 36

10.6 Switch Configuration for Vood 122 . . . . . . . . . . . . . . . . . . . . . . . . 40

10.7 Switch Configuration for Vood x42 . . . . . . . . . . . . . . . . . . . . . . . . 41

Differentiated Services Ingress Classification: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

10.8 Switch Configuration for Vood 292 . . . . . . . . . . . . . . . . . . . . . . . . 49

10.9 DNS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

10.10 NTP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

10.13 Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

10.14 Codec Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

12.2 EM-Configured Services Parameters . . . . . . . . . . . . . . . . . . . . . . . 74

12.3 EM-Configured User Behavior Setting Parameters . . . . . . . . . . . . . . . 76

12.5 EM-Configured H323 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 79

3 Phone Number Configuration . . . . . . . . . . . . . . . . . . . . . . . . 88

4.1.5 Enable H.245 Tunneling ..... . . . . . . . . . . . . . . . . . . . . . . . . . . 91

3 Phone Number Configuration . . . . . . . . . . . . . . . . . . . . . . . . 95

5 Known Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

2.2 Analog Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

4 Known Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

1.1 About the Vood IRG/ITA Unit

1.2 Target Groups

Broadband operators and network administrators who offer network connectiv-

Service providers who offer Voice over IP (VoIP) services to end-users.

It should be useful for:

Assisting with network design for a Vood installation

Vood terminal parameter entry in the i3 Centre EM

1.3 Document Scope

Vood 122 (End of life, no longer supported)

1.4 Support Information

Terminal Serial Number

1.5 Standard Equipment

2 Abbreviations and Conventions

CCS Call Control Server.

CFI Canonical Format Indicator.

DHCP Dynamic Host Configuration Protocol, RFC 2131, RFC 1541.

DNS Domain Name System.

FQDN Fully Qualified Domain Name.

HTTP HyperText Transfer Protocol, RFC 2616.

IGMP Internet Group Management Protocol.

DHCP server EM* and HTTP/TFTP* CCS/SIP Proxy

DHCP server EM* and HTTP/TFTP* CCS/SIP Proxy