Professional Documents
Culture Documents
VSX UserGuide Ver705 PDF
VSX UserGuide Ver705 PDF
Important Notices
Warnings!
Sansay, Inc.
4650 Lusk Blvd. Suite 204, San Diego, CA 92121 (858) 678-0200; FAX (858) 678-0203
S-VSX-301-TP-1B
Sansay VSX
Voice Session Exchange
Users Guide
Sansay, Inc.
May, 2006
TABLE OF CONTENTS
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Who Should Use This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
How To Use This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Textual Callouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Service and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VSX Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Session Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Border Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Protocol Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gatekeeper Interconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SIP Proxy Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VSX OS and Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
High Availability Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Media Switch VMX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VMX Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VSX Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
1
1
2
3
4
5
5
6
7
7
8
8
13
13
14
14
15
15
15
17
17
18
18
20
21
ix
Configuring Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Routes Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Adding Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Chapter 5. Adding and Configuring Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Opening the Resource Add Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resource Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Digit Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ingress Action Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Egress Action Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Codecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resource Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25
26
28
28
31
33
36
36
36
37
39
39
41
43
44
45
45
47
55
55
56
57
57
58
59
59
60
61
63
63
64
64
64
65
Table of Contents
72
73
74
74
75
76
76
77
78
79
80
81
83
83
84
85
85
86
87
87
89
91
93
94
96
97
97
97
98
101
101
103
104
106
107
108
109
109
109
110
110
111
113
113
114
114
xi
115
115
116
119
122
125
126
126
126
127
xii
LIST OF FIGURES
Figure 1. VSX Session Controller Application Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Figure 2. VSX Border Gateway Application Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Figure 3. VSX Protocol Support Application Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Figure 4. Gatekeeper Interconnect Application Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 4
Figure 5. SIP Proxy Connect Application Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 6. VSX 1U and 2U Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Figure 7. NEBS Compliant VSX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Figure 8. High Availability Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Figure 9. VMX Cluster Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Figure 10. VSX Front Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Figure 11. VSX Rear Panel External Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 12. VSX Default IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 13. VSX Login Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 14. Edit Network Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 15. Edit System Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 16. VSX Resources Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 17. Resource Add Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 18. VSX Routes Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 19. Add Route Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 20. VSX Import Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 21. VSX Save Route Table Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 22. Digit Mapping List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 23. Digit Mapping Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 24. Digit Mapping Call Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 25. VSX Users Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 26. Add User Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 27. Edit User Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 28. VSX Gateway Statistics Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 29. VSX Route Statistics Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Figure 30. VSX System Statistics Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 31. System Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Figure 32. Edit System Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 33. Edit Network Connections Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Figure 34. VSX Advanced System Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 35. Restore System Configuration Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Figure 36. VSX Save System Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 37. VSX Upload Code Upgrade Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 38. VSX Reboot System Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Figure 39. VSX Restart Software Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 40. System Offline Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Figure 41. Generate System Key Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Figure 42. Radius Server Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 43. Edit Radius Servers Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 44. VSX Login Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
xiii
xiv
LIST OF TABLES
Table 1. Possible Problem Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2. CDR Header Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3. Call Detail Record Body. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4. Detail Field Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5. Release Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6. 1St Release Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 7. Release Codes from Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 8. Release Messages from VSX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9. VSX Internal Release Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 10. VSX Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 11. VSX Server Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . .
111
115
116
119
122
123
123
124
124
129
130
xv
xvi
xvii
Textual Callouts
This book uses two distinct symbols displayed in the textual
margins to call your attention to information that is of particular interest.
These call-outs are:
Note
Caution
Getting Help
If a problem occurs, a message normally displays on the system monitor. These messages belong to one of the following
categories:
xviii
Message Type
Displays
Informational
Error
xix
xx
CHAPTER 1
INTRODUCTION
This chapter describes the functionality of a Sansay VSX
and describes how the VSX operates within a network environment.
VSX Applications
The VSX can be implemented to provide the following services:
Gatekeeper Interconnect
SIP Proxy
Session Controller
When implemented as a session controller, the VSX:
Border Gateway
When implemented as a border gateway, the VSX:
Introduction
Protocol Interworking
The VSXs versatile protocol compatibility supports:
Gatekeeper Interconnect
The VSXs gatekeeper interconnect supports:
Introduction
Non-redundant. AC only
Redundancy
Multiple VSX servers can be implemented to provide:
Introduction
Standby VSX
Figure 8. High Availability Node
VMX Cluster
To handle call media requirements, multiple VSX units can
be implemented in a VMX cluster configuration (Figure 9) to
provide:
Call Signaling
Call Media
VSX Integration
The Sansay VSX can be deployed singularly or in pairs to
provide maximum network reliability. In the latter configuration, VSXs are interconnected and synchronized through
dedicated, 100Base-T LAN interfaces.
A single VSX can support a large network of gateways; however, VSXs can also be deployed regionally and operate
together to provide the call processing and switching structure for multiple proprietary networks.
CHAPTER 2
VSX Unit
Accessory Kit
User Documentation on CD
A set of hand tools (such as cordless screwdriver, #2 Phillips screwdriver, 5/16 flat blade screwdriver)
10
Power cord
LAN Port
120/250 VAC
11
12
CHAPTER 3
System IP Addresses
Gateway/Resource Address
Protocols
Configuration Overview
This section presents a high-level approach for initially configuring the VSX. This information is presented in the recommended logical sequence.
13
Configuration Sequence
This section presents the recommended process flow you
need to initially configure a VSX. Access the following
screens in the order below:
System Page
Routes Page
Users Page
System Page
The System page enables you to specify the initial required
configuration parameters for the VSX system. See "System
Page" on page 85 for more information.
Access the System page by clicking on the System tab on the
user interface. From this page you will need to set:
14
Alias Name
System Mode
Default Router
Subnetwork Mask
Resources Page
The Resources page enables you to add, edit, and delete
gateways, softswitches, and IP phones. See "Resources
Page" on page 89 for more information. See also Adding and
Configuring Resources on page 25.
Access the Resources page by clicking on the Resources tab
on the user interface. From this page you will need to:
Routes Page
The Routes page enables you to add, edit, and delete routes
accessible to the VSX system. You can establish a primary
route and up to seven alternate routes. See "Routes Page" on
page 91 for more information. See also Adding and Configuring Routes on page 39.
Access the Routes page by clicking on the Routes tab on the
user interface. From this page you will need to specify:
Alias name
Trunk IDs
Users Page
The Users page enables you to add, edit, and delete users
authorized to access the VSX system. In addition, you can
establish access priveleges for each user. See "Users Page"
on page 93 for more information.
Access the Users page by clicking on the Users tab on the
user interface. From this page you will need to:
15
16
CHAPTER 4
INITIAL CONFIGURATION
The Sansay Session Controller features a comprehensive,
easy to use graphical user interface that enables you to configure and manage the VSX. Using a standard Internet
browser you can access this interface by entering the default
IP address of the VSX.
Logging In
Open a standard web browser and enter the default IP
address of the VSX unit (see below). The default IP address
is HTPPS://192.168.0.100:8888/.
HTPPS://192.168.0.100:8888/
After entering the default IP address of the VSX unit, a welcome screen should display enabling you to login to the system. If the browser cannot locate the page, refer to the
troubleshooting tips in Troubleshooting the VSX on
page 110. The welcome screen is shown below in Figure 13.
17
Enter your user name and password and click the Login button to proceed to the configuration screens. The default user
name is superuser and the default password is sansay. The
System Statistics screen displays by default. Click the Users
tab to begin to edit the user settings.
Changing Passwords
For security reasons the username and password should be
changed from the defaults. These should be easily memorized and stored in a secure place. This is done under the
Users tab by clicking on the edit link next to the superuser
name. Enter the new username and passwords and then
click Submit. Log out and then back in to the VSX in order
to test the changes.
In order to allow Sansay technical support access to your
system please add a user name of your choice with superuser privilege and send email to support@sansay.com with
the username and password of their login.
18
Initial Configuration
19
20
Initial Configuration
21
Note
When submitting changes to the VSX FQDN, Default Gateway, Subnet Mask, or Local Payload Port Start settings, the
system will restart.
Configuring Resources
You are now ready to configure the system to send and
receive calls. Any device which will be either sending you
calls (originating) or receiving your calls (terminating) is
considered a resource.
After setting the initial system parameters, use the
Resource screen to configure gateways, IP phones/clients,
soft switches, and proxies. For more information, see Adding and Configuring Resources on page 25.
Routes Tab
After adding the resource gateways, use the Routes screen
to add new routes, or view and edit existing routes. For more
information, see Adding and Configuring Routes on
page 39.
22
Initial Configuration
Adding Users
From here, you will need to access the Users page. The
Users page enables you to enter all users authorized to
access the VSX system. Initially, the superuser entry displays by default. For more information, see Managing
Users on page 55.
23
24
CHAPTER 5
25
26
27
Adding Resources
When configuring a new resource, the essential parameters
are the resource Name (an alias for your convenience), the
FQDN or IP address, the VoIP protocol used, the Trunk ID
(TID), and the digit stripping or prepending method.
General Info
You will need to configure the following fields and controls:
Trunk ID
Specify the desired trunk ID for the resource. This will
be the default trunk ID. For numbering purposes, the
TID range for Resources can be 1-49,999.
Name
Use this field to specify the resource's alias name. You
can enter a name of up to 40 alphanumeric characters,
including periods and hyphens. This field is optional.
Company Name
Use this field to enter a label to identify the gateway's
owner. You can enter a company name of up to 40 alphanumeric characters, including periods and hyphens. This
field is mandatory.
FQDN
Enter the fully-qualified domain name or a unique IP
address of the new resource (for example,
192.168.0.1). If you do not know the FQDN or the IP
address of the resource, check with your network administrator. This field is mandatory.
A range of addresses can be entered using a syntax such
as 192.168.0.2 /32. If an FQDN is entered it must be
28
29
Note
30
Resource Type
Resource Type fields enable you to select the resource protocol type and set operational parameters such as Service
State, directional properties, network address translation
(NAT) and media handling.
Protocol
The protocol selection is used to control the outbound
call request protocol. All calls sent to this resource will
use the configured protocol. However, inbound calls are
accepted with either SIP GW, SIP Proxy, H.323 GW,
H.323 GK, or ENUM Server protocols.
SIP GW will generate invites with the DNIS@ip address
of the configured FQDN. SIP Proxy will do the same.
H.323 GK will send LRQs to the configured FQDN.
When the ARQs are returned the VSX will generate
H.323 GK protocol to the returned FQDN. The VSX does
not need to know the addresses of the GWs for outound
calls. However on H.323 GKs used for inbound traffic the
VSX needs to be configured with the GW addresses
unless the configured GK is used in "routed mode".
Port Address
Use this field to specify the port address for the resource.
If you do not know the port address of the resource,
check with your network administrator.
Service State
Determine the operational state for the gateway. Select
In Service to bring the gateway online, Block to disable
access to/from the gateway, or Trace to enable the tracing function.
31
Note
Direction
Determine if the gateway will send calls to the VSX,
receive calls from the VSX, or both. Select In to designate the gateway as an ingress gateway to the VSX.
Select Out to designate the gateway as an egress gateway from the VSX. Select Both for bidirectional operation.
The VSX determines inbound calls based on the IP
Address and Tech Prefix. If Tech Prefixes are not used,
inbound calls will find the first TID that matches the IP
address in order or ascending TID number. If you have
inbound TIDs, they should be numbered lower than the
outbound TIDs.
NAT
Indicate whether or not the gateway is located behind
NAT (network address translation). When accessing a
network through a firewall, address translation can be
necessary. To indicate address translation is required,
select One. Select None to indicate that no network
address translation is necessary.
This feature requires the Firewall to be configured to
send to the SIP (UDP 5060) messages to the specified
gateway. Otherwise traffic we send to the gateway may
not reach it. The function of this setting is to ignore the
provided SDP and to auto-learn the ports being used on
each call.
32
Digit Translation
Digit Translation fields enable you to enter the number of
digits (ie., how many) that you want to strip. The Digit
Prepending (or Appending) fields, enable you to enter the
exact (literal) digits to be added. It is important to consider
your routing table design for it to be flexible and extensible.
The VSX system provides to options for both ingress and
egress traffic.
The most common approach is to route based on the country
code, so you need to consider this when configuring how
many digits to strip. You will need to configure the following
fields and controls:
Match
Use this field to specify your digit matching requirements for both ingress and egress traffic. Digit matching
is used to determine if the call should use this translation rule or not. If the leading digits on the DNIS do not
match the digits entered here, the call will not use the
translation values entered. Use All in order to force all
calls to use this rule.
33
34
Digits 1
Specify the number of digits to be operated on by the
Action 1 setting for both Ingress 1 and Ingress 2.
Digits 2
Specify the number of digits to be operated on by the
Action 2 setting for both Ingress 1 and Ingress 2.
Action 1
Specify the first action to be performed on outgoing digits for both Egress 1 and Egress 2. Select None for no
action, Left Strip or Right Strip to mask specified digits,
or Prepend to add specified leading digits to the outgoing
number. For an example, see Egress Action Example
on page 36.
Action 2
Specify the second action to be performed on outgoing
digits processed by Action 1 for both Egress 1 and Egress
2. Select None for no action, Left Strip or Right Strip to
mask a specified number of digits, or Prepend to add
specified leading digits to the outgoing number. For an
example, see Egress Action Example on page 36.
Digits 1
Specify the number of digits to be operated on by the
Action 1 setting for both Egress 1 and Egress 2.
Digits 2
Specify the number of digits to be operated on by the
Action 2 setting for both Egress 1 and Egress 2.
When you have finished making your selections, click Submit to save the configuration. Repeat this process for each
new resource. To abandon the changes, click Cancel.
35
Codecs
Codec Policy allows you to advertise a specific codec or group
of codecs to a resource. This allows you to tailor the codec
choices used on each resource and to limit the selection process of the terminating endpoint.
To use this feature change the setting from transparent to
enforced. Then use the pull down menus to select Codec 1,
Codec 2 Codec 8. Codec 1 is advertised as the preferred
codec on all calls setup to that resource, Codec 2 is the sec-
36
Note
Note
Resource Groups
A Resource Group is a collection of gateways which are not
in a contiguous range, but are part of the same TID. In this
configuration you can have up to 64 IP addresses in a single
TID. It is not possible to use IP ranges within Resource
Groups. For numbering purposes the TID range for
Resource Groups can be from 50,000-99,9999.
37
38
CHAPTER 6
Click Add Route to open the Add Route dialog shown below
(Figure 19).
39
40
Configuring a Route
A route is designated by an Alias, Digit Match, and the
Route Table it applies to. To set up a route, you will need to
configure the following:
Alias
Assign an alias name to the new route. You can enter up
to 40 alphanumeric characters.
Digit Match
Enter an access code for the route under configuration.
You can enter up to 10 characters that range from 09,
including *, #, +, A, B, C, and D. For example, you can
enter 011 (leading digits) for international long-distance
routing. Incoming leading digits are first parsed for leading digits 011; then 01; then 0. Calls that match one or
more specified leading digits are routed appropriately. If
no digit match occurs, the call fails.
Note: The # character is not adviseable to use in VoIP
phone calls. The SIP protocol uses URL specifications for
phone numbers, and the # symbol is treated differently
by various vendors.
The SPX will accept either type of # character in a SIP
URL. However it will use the IETF-specified control
character (%23) when generating an Invite with the #.
Some devices will not recognize this as a # on incoming
calls.
Route Table
This control enables you to select an alternate route
table. Route tables are configured by using the Route
Table List tab on the Routes List page.
Trace
Use this control to enable or disable tracing.
41
42
Proportional Routing
Proportional Routing is used to divide up calls for a route
between several termination resources (TIDs). Proportional
routing divides the calls on a percentage basis between the
various termination options. To select this option use the
pull down menu to select Percentage.
Once this is selected you are required to enter a Load Percentage figure for each route. The percentage of the load for
that route will be shared among the resources based on the
percentage entered. A setting of 50% for each of 2 resources
for example, will split the call evenly between them. The
percentage total of all routes shown on the page must equal
100%.
For example, 50% of the calls can start at Route 1, and the
other 50% could start at Route 2. This gives the VSX ability
to load-share the initial call request across up to 8 outbound
carriers. The percentage-based routing will still alternateroute when a call attempt fails. If the initial call goes to
Route 2 and fails, it will still alternate-route to Route 1. This
call attempt will not effect the percentage of the calls that
are assigned to Route 1. The percentage is only calculated
on the first outbound call attempt.
Routes also indicate the alternate routes taken when the
outbound call attempts fail, and lets you control the alternate routing. The Continuous Routing Yes or No setting
enables you to set a Route number to cease alternate calling.
This works well with percentage based routing because you
can divide up the calls into groups of routes without worrying about calls alternate routing between them. Thus you
can have 50% of your calls attempt Routes 1,2, and 3 and
50% attempt Routes 4,5,6,7, and 8.
Proportional routing determines the initial call attempt for
the outbound calls. If the call fails it will alternate route
through the remaining TIDs as configured.
43
Note
44
Routes
TOD Routes
Route Groups
Route Tables
45
46
Routes
TOD Routes
Route Groups
Route Tables.
Note
From the Export form, use the Select which Table to export
dropdown to choose the route or table to export. Specify the
file format for exporting. Select either CSV, or XML.
When all your selections are complete, click Export to download the file from the VSX to a workstation.
47
48
CHAPTER 7
DIGIT MAPPING
The Digit Mapping page gives access to the Digit Mapping
List and Digit mapping Table pages. The digit mapping
entries are configurable with the GUI or with XML commands.
Sansay offers a SOAP/XML client for use with the VSX or
SPX, but any XML client can be used for this task. For more
information, see Sansay SOAP Client on page 97.
49
To add a DMT value you must first create the table itself.
This is done on the Digit Mapping Table List subtab.
The Digit Mapping List performs actions based upon the
matching DNIS/ANI combination. For either the DNIS or
the ANI you can enter Match, Passthrough, or All. These
actions imply:
Match - The values which are used to match the number
are replaced by the translated numbers. If there are no
numbers in the translated field, the matched digits are
stripped.
Passthrough - The entire DNIS or ANI is maintained with
no changes.
All - The entire DNIS or ANI is replaced by the value in the
translated field.
If a call arrives which does not match the ANI and DNIS in
the DMT is will go through the table unchanged and then
enter the route selection process.
50
Digit Mapping
51
The DMT entries are only configurable with the GUI or with
XML commands. Sansay offers a SOAP/XML client for use
with the VSX or SPX, but any XML client can be used for
this task.
Two steps must be taken when configuring the DMT. Initially you must add the target table, and secondly you must
populate the entries within the DMT. For more information,
see Sansay SOAP Client on page 97.
In order to add DMTs you need to first create the Table to be
populated. Click on the ADD button and simply assign a
Table ID and an Alias.
52
Digit Mapping
53
54
CHAPTER 8
MANAGING USERS
Read this chapter to learn how to add users and manage
their ability to access the VSX resources.
55
To access the Add User form (Figure 26), click the Add User
button on the Users screen.
Adding a User
As the superuser, you will need to configure the following
fields and controls:
Login User ID
Use this field to specify the new user's login name. You
can enter a user ID name of up to 20 alphanumeric characters, including periods and hyphens. This field is
required.
Authorization
Use this field to specify access priveleges for the user.
Select one of the following access levels:
Super User
Read Only
Admin
56
Adding Users
Select Read Only to limit access to viewing existing configuration, user information, and statistics.
It is useful to have a read-only user in case you want to
doublecheck the configuration or to examine the status
of routes.
Select Admin to allow access to manage resources and
routes.
Password
This field stores the password of the newly-added user.
Enter a unique password for the user. You can enter up
to 20 characters including letters, numbers, periods and
hyphens. Re-enter the password in the password verification field. Both fields are required.
First/Last Name
Enter the first and last name of the user. This information is displayed when user status is queried. Both fields
are required.
Click Submit to upload the user information to the VSX.
Repeat this procedure for each new user.
Editing Users
To edit a users personal information, or to adjust access
rights, select a single user listing from the Users page (Figure 25 on page 55) and click its respective Edit link. The
Edit User form displays as shown in Figure 27.
57
Deleting Users
To delete one or more users, select a user from the Users
page (Figure 25 on page 55) by checking its respective selection checkbox. Multiple users can be selected in this way.
Click Select All to select all listed users.
Click the Delete button. A Confirmation dialog displays to
verify the deletion(s). If you change your mind, click Cancel
to abandon the delete operation. The Confirmation dialog
clears without changing the selected user settings.
Sansay strongly recommends deleting or changing the
default username to something unique for each customer.
This greatly reduces the security risk with remote access.
58
CHAPTER 9
VIEWING STATISTICS
This chapter describes how to use the Statistics viewer to
assess system traffic and performance for the VSX system,
its gateways, and routes.
59
From this page you can view inbound and outbound Call
Attempts (CA), Answer Sieze Ratio (ASR), Failed Call Ratio
(FCR), and Average Call Duration (ACD) statistics over 15minute, one-hour, and 24-hour intervals. ACD is the average time between when an answer message is received and
the time the call is disconnected. This is often the same
value used for billing.
The Refresh button asserts an immediate update to the
Gateway Statistics page. Select the auto-refresh interval by
clicking the appropriate radio button.
From this page you can view Call Attempts (CA), Answer
Sieze Ratio (ASR), and Fail Call Ratio (FCR) statistics over
15-minute, one-hour, and 24-hour intervals for each table,
digit match, route alias, and trunk ID. The Refresh button
asserts an immediate update to the Route statistics page.
Select the auto-refresh interval by clicking the appropriate
radio button.
60
Wiewing Statistics
61
Resource allocations
The Refresh button asserts an immediate update to the System Statistics page. Select the auto-refresh interval by clicking the appropriate radio button. Click Clear to clear the
page and begin collecting new statistics.
This page should be checked regularly to ensure that system
performance is as expected. The LAN ports should be
checked to ensure that errors are not being generated over
time. All LAN connections should be Full Duplex to minimize transmission errors. Disk space should never fall
below 15 GB. If it does, contact Sansay support.
62
CHAPTER 10
Gateways
Routes
63
Editing Gateways
To edit a gateways configuration, you must first ensure that
the gateway is brought out of service. Use the following procedure:
1. Select a gateway from the resource screen. Click the
selected gateways Edit button.
2. From the Edit Gateway screen, change the gateways
service state to Provision.
3. From the Edit Gateway screen, change the configuration
settings as necessary. When the new settings are complete, Click Submit to assert the changes. A Confirmation dialog displays to verify the changes.
4. If you change your mind, click Cancel to abort the edits.
The Confirmation dialog clears without changing the
selected gateway settings.
Deleting Gateways
To delete a gateway from the resource list, use the following
procedure:
1. Select a gateway from the resource screen by checking
its selection checkbox.
2.
3. If you change your mind, click Cancel to abort the deletion. The Confirmation dialog clears without changing
the selected gateway.
Editing Routes
Use the following procedure to edit a route:
1.
Select a route from the Routes screen. Click its respective Edit button. The Edit Route screen displays.
64
settings as necessary. When the new settings are complete, Click Submit to assert the changes. A Confirmation dialog displays to verify the changes.
3. If you change your mind, click Cancel to abandon the
edits. The Confirmation dialog clears without changing
the selected route settings.
Deleting Routes
Use the following procedure to delete a route:
1.
2.
65
66
CHAPTER 11
67
System Tab
The System page displays read-only information specific to
the systems native hardware and software configuration.
The System page is shown in Figure 31.
68
Edit System
69
From this page you can add or edit the following fields:
Alias Name
This field specifies the alias name for the VSX system. The
alias name can be up to 128 alphanumeric characters in
length and can include commas, semicolons, spaces, periods,
hyphens, underscores, the @ symbol, and question marks.
CDR System Name
The call detail record (CDR) system name parameter specifies the CDR filename prefix used for the VSXs internal file
naming convention. Up to eight characters are supported for
this filename prefix.
CDR File Interval
Specify the number of seconds that will transpire between
CDR file writes. The default value is 600 seconds (10 minutes). The value range is 180 to 86,400 seconds.
CDR Password
The CDR password enables access to collect call detail
records. CDR retrieval can be done by using FTP, SFTP,
or SCP. For more information about accessing CDRs, see
Collecting Call Detail Records on page 81.
Local Payload Port Start
This field displays the base (starting) address for UDP
ports used by the VSX system. This value is chosen as a
multiple by 4 of the VSXs call capacity. The default UDP
port base address is 10000.
SIP Port Address
Specify the SIP port address for the VSX system.
H323 Port Address
Specify the H323 port address for the VSX system.
70
Gatekeeper ID
When using Gatekeeper-to-Gatekeeper protocol, the VSX
must provide the other gatekeeper it's ID. This field is a
global gatekeeper ID which will be used for all gatekeeper messages sent from the VSX. This needs to be
coordinated with any partners using gatekeeper control
for their network.
RAS Port Address
RAS port is used to control what UDP port we send the
Radius messages to on the Radius Server. The Shared
Secret is the password used for accessing the Radius
server.
NTP Server1/2
These fields display IP addresses for up to two network
time protocol servers used for reference to external time
standards.
DNS Server 1/2
The VSX can use either a host file or a DNS server to
resolve the Fully Qualified Domain Names (FQDNs) to
IP addresses. The IP addresses of the DNS servers are
entered into these fields.
SIP Reinvite Timer
The VSX can send out a periodic reinvite message to poll
the status of the call on the SIP call legs. If the reinvite
is not acknowledged the call will be disconnected. This
setting controls how frequently the reinvite will be sent
out on the call legs. The default value is 11 minutes. The
value range is 1 to 180 minutes.
Trace Unauthorized Call
The VSX can automatically log unauthorized calls into
the Session Trace file which is viewable in the Trace >
Show Session Trace tab. Only one call at a time will be
traced, so the file will not get too large or occupy too
much processor time. An unauthorized call is one origi-
71
Note
72
Subnet Mask
This field displays the ethernet subnetwork mask for the
VSX system. This address is specified during initial configuration of the VSX system. The subnet mask controls the
boundary between the public and private network address
spaces. It indicates how many network addresses are used
for the private network; all others are considered public.
The default value is 16. The value range is 1-24.
Default Gateway
This field displays the IP address of the default gateway
that the VSX will use. This address is specified during initial configuration of the VSX system.
After editing these fields, click Submit to assert the changes
or click Cancel to abandon the process.
Restore a Configuration
Save a Configuration
Upgrade Code
73
Restoring A Configuration
The Restore Config button opens the Restore System
Configuration form (Figure 35) that enables you to
restore the previously-saved configuration after configuration changes are made. You can enter the name of the
configuration file, or click Browse to navigate to the file
you want. After selecting the file, click Submit to reinstate the configuration.
Saving a Configuration
The Save Config button opens the Save System Configuration dialog (Figure 36) that enables you to save the
current configuration to a configuration file.
74
Note
75
Note
76
Note
77
Note
78
Note
This button is only viewable if the system has a Load Balancing license.
79
80
81
82
CHAPTER 12
Logging In
After entering the default IP address of the VSX unit, a welcome screen displays that enables you to login to the system.
The welcome screen is shown below in Figure 44.
Enter your user name and password and click the Login button to proceed to the configuration screens. The default user
name is superuser and the default password is sansay.
83
Configurator GUI
The VSX configurator consists of six pages that are accessed
by clicking their respective tabs. These pages are:
84
System
Resources (default)
Routes
Statistics
Trace
Users
Digit Mapping
System Page
The System page displays read-only information specific to
the systems native hardware and software configuration.
The Basic System page is shown in Figure 45.
85
Advanced Tab
Click the Advanced tab to access the Advanced System
control panel. From this panel you can:
Restore a Configuration
Save a Configuration
Upgrade Code
86
Upgrade Code
The Upgrade Code button opens the Upgrade Code form
that enables you to upgrade or change the system capacity. For more information, see Upgrading VSX Code on
page 75.
Reboot System
The Reboot System button opens the Reboot System dialog. Click Reboot Now to issue an explicit command that
completely reinitializes the VSX system. This action is
service-affecting. For more information, see Rebooting
the System on page 76.
Restart Software
The Restart Software button opens the Restart Software
dialog. Click Restart Now to issue an explicit command
that restarts the VSX system software. This action is
service-affecting. For more information, see Restarting
the VSX Software on page 76.
87
88
Resources Page
After login, the Resource page displays by default. It displays existing connected gateways, IP phones/clients, soft
switches, and proxies. In addition, it enables you to add
additional gateways and edit existing access parameters.
The Resources page is shown in Figure 46.
89
90
Edit
Invokes the Edit Resource Gateway dialog. For more
information, see Editing and Deleting Resources on
page 63.
Help
Displays online help for the Resources screen.
Logout
Logs out the user and dismisses the Resources screen.
Routes Page
The Routes page enables you to add new routes, or view and
edit existing routes. The Routes page is shown in Figure 47.
91
92
Users Page
The Users page displays all users authorized to access the
VSX system. Initially, the superuser entry displays by
default. The Users page is displayed in Figure 48.
93
User ID
Displays a hyperlinked reference number for the listed
user. Clicking this link displays information specific to
the selected user.
Authorization
Displays the access priveleges granted to the user by the
superuser. Access rights can be Superuser, Admin, or
Read Only.
Last Login Date/Time
Displays the most-recent session the listed users were
engaged in.
Remote Host
Displays the IP address of the remote host associated
with a listed user.
Edit
Invokes the Edit User dialog. This dialog is used to modify individual user information. For more information,
see Managing Users on page 55.
Monitoring Page
The VSX Monitoring page is shown in Figure 49 on page 95.
Inbound or outbound statistics are collected for in-service
trunks at 15- minute, 1-hour, and 24-hour intervals. The
Gateway Stats page displays by default.
94
95
Trace Page
If calls are failing you may need to enable tracing for the
problem gateway or routes. The Trace page enables you to
perform traces for troubleshooting purposes.
Advanced
96
CHAPTER 13
XML Schema
The SOAP client includes a number of files which are XML
schema. These represent the format of the database structure which can be updated on the VSX using XML. It is
important to note that the database structure changes as
new features are added to the VSX system. If you upgrade a
version of software it may include new features which are
not in the SOAP client's XML file schema. As such it is
worthwhile to Export the new configuration in the GUI
using the Export > XML button on the Resource or Route
tabs on a new system or after a significant version change.
97
Add
Delete
Upload
Download
Update
Resource
Resource Group
Route
Route Table
Route Group
98
99
100
CHAPTER 14
TROUBLESHOOTING
Read this chapter for information on solving problems you
may encounter when using the VSX Configurator and session controller.
Failing Calls
If calls are failing within your network you can verify this by
using the Statistics tab. This will show you the percentage of
answered calls as well as the percentage of failed calls
within the VSX. You can monitor either all the calls inbound
from a resource or just the calls outbound to a specific route.
To monitor the Inbound calls, select the Statistics tab and
then click the Show Gateway Statistics button. This will
show you the calls inbound from each Gateway or partner.
The first column is the Trunk ID associated with the
resource, the company name, and the gateway alias. The
display can be sorted by clicking on the heading for each of
these headings. Each TID will show the Inbound Call
Attempts (CA), the Answered Sieze Ratio (ASR), and the
Failed Call Ratio (FCR).
The ASR is the ratio of the answered calls on the TDM side
of the GW versus call attempts. It will normally indicate
below 100% because not all calls are answered. If the ASR is
100%, most likely the end gateway is providing you answer
supervision on all calls whether they are answered or not.
101
102
Troubleshooting
Tracing Calls
If the calls are failing you may need to enable tracing for the
problem gateway or routes. Tracing is enabled by editing the
route or gateway and changing the Service State to Trace.
You can then select the Trace tab and use the menu selections.
Advanced
103
104
Troubleshooting
time for the session, the Answer time (if empty it means it
was unanswered), and the Release time. One line shows the
Stack Cause for either the Originating (O) or Terminating
(T) side of the call. These are in accordance with either the
IDSN Cause Code (H.323) or the SIP message type. Please
see the appendix for cause code listings in Release Causes
on page 122.
The second portion of the sesson trace shows the Origination
TID and the protocol used on this session. The ANI and the
DNIS are shown as they arrived to the VSX (untranslated).
The IP/UDP for the signaling and media are also shown as is
the CODEC list provided on the incoming calls.
The third portion of the trace shows essentially the same
information on the Termination side of the call. In this case
the information is exactly as it leaves the VSX, ie., post
translation. The codec list here should reflect the CODEC
used on the call.
The fourth portion shows the media packets that were sent
and received on the call. The Orig line shows the voice packets inbound from the origination gateway (Pkt In) and the
packets outbound toward the origination gateway (Pkt Out).
The bottom line shows the voice packets sent and received
from the terminating gateway.
105
106
Troubleshooting
107
Advanced Trace
Advanced tracing gives a detailed view of Call sessions, Protocol tracing and VSX System processes. Advanced tracing
tools should only be used under the guidance of the Sansay
technical support staff. They are used for detailed debugging
of system software. They are not needed for normal troubleshooting or diagnostics. Large amounts of data are created
and these traces should not be left enabled for any length of
time.
108
Troubleshooting
Configuration Problems
This section presents a summary of the common causes of
configuration errors and suggestions to troubleshoot each:
1. A conflict with a selected protocol.
2. A routing error.
109
Basic Steps
110
Troubleshooting
Corrective Action
First, check the In/Out Action rule to ensure that applying the In/Out Action will produce dialed digits that
match the configured route.
Make sure that the prefix and DNIS are the correct ones
the terminating partner is expecting.
111
Description
Corrective Action
Access the VSX Configurator System page from a standard web browser.
112
Troubleshooting
Getting Help
If after installing and configuring your Sansay equipment,
you cannot establish communications to or from the unit,
carefully review the information in this book prior to calling
Sansays Technical Assistance Center (TAC).
Checklist
Ensure that you have checked the following possibilities:
Check your software version. To ensure that all our customers have the latest enhancements and product features, Sansay ships every new or factory-upgraded unit
with the latest software version.
Therefore, whenever you are installing units into your
system, check each unit to verify that all units are
equipped with identical software versions.
113
Contacting TAC
If, after carefully reviewing the information in this book
your problem persists, contact either your product representative or a service representative at Sansays Technical
Assistance Center. Prior to calling, ensure that you have
assembled all the pertinent data that will assist in resolving
your problem. These items include:
A complete listing of your system components and configuration. Include your units serial number and the
software version number it is running
Contacts
Address:
Sansay, Inc.
4650 Lusk Blvd. Suite E204
San Diego, CA 92121 USA
Telephone:
1-858-678-0200
114
APPENDIX A
Introduction
Call detail records (CDRs) are an integral part of the VSX as
they contain the usage information to bill your customers.
Therefore, you should review the CDR formats in this chapter for complete information on the CDR fields. .
Table 1. CDR Header Structure
Parameter
Max ASCII
Characters
Description
Notes
Version Number
Record Type
Record Data
Variable
Notes:
1. Current version: V1.8
2.
115
CDR fields that contain no data will contain the string NA.
The semicolon character (;) is used as a delimiter to separate
the fields of a CDR record. Each CDR record in the file is
separated by a line feed character (\n).
Max ASCII
Characters
Description
Notes
ConnectionType
16
Type of connection
SessionID
32
Release Cause
32
32
Release TOD
32
32
32
New in v1.1
New in v1.1
O: origination, T: termination
New in v1.1
Trunk ID -- Origination
128
128
116
Max ASCII
Characters
Description
Origination Destination
Number
128
Origination Destination
Host Name
128
Origination Call ID
128
Origination Call ID
128
16
16
128
10
10
10
10
Number of Egress (out from Sansay system) payload octets in origination dialogue
10
10
10
Notes
117
Max ASCII
Characters
Description
Notes
Trunk ID -- Termination
128
128
Termination Destination
Number
128
Termination Destination
Host Name
128
Termination Call ID
128
16
16
2.00,2.10
C,2.00,2.10
128
C,2.00,2.10
10
I,2.00,2.10
10
Number of Egress (out from Sansay system) payload packets in termination dialogue
f,C,2.00,2.10
Termination Ingress
Octets
10
d,2.00,2.10
10
Number of Egress (out from Sansay system) payload octets in termination dialogue
g,2.00,2.10
Termination Ingress
Packet Loss
10
i,2.00,2.10
118
Max ASCII
Characters
Description
Notes
10
f,C,2.00,2.10
Termination Ingress
Packet Jitter
10
d,2.00,2.10
New in V1.3
Routing Digits
64
New in 1.4
New in 1.5
New in 1.6
New in 1.6
Duration in mini-seconds
10
New in 1.8
Conf_ID
36
Conference ID
New in 1.9
Size in Bytes
ConnectionType
16
SessionID
32
Release Cause
32
32
Release TOD
32
32
32
119
Size in Bytes
Trunk ID - Origination
128
128
128
128
Origination Call ID
128
16
16
128
10
10
10
10
10
10
10
Trunk ID -- Termination
128
128
128
128
Termination Call ID
128
16
16
128
120
Size in Bytes
10
10
10
10
10
10
10
Routing Digits
64
Call Duration
PDD
Ring Time
Call Duration in ms
10
Conf-ID
36
121
Release Causes
This Section provides a list of the Sansay VSX Call Release
causes. The CDR records generated by the Sansay VSX contains four fields that can be used to determine the exact
cause of a call termination.
1. Session Release Causes: ( Field #3 in CDR body)
This is mainly for successful calls ( answered, ring no
answer) calls. All session release causes of 00x indicates the
call is not failed ( Field #3 in CDR body). For all the failed
calls, the released stack and stack release cause can provide
more information.
Table 4. Release Codes
122
Cause Code
Description
01
02
03
04
402
403
404
405
406
500
501
502
503
600
601
602
603
2. 1st Release Dialogue (Field #10 in CDR) a one character value identifying the side of the call that initiated the
teardown.
Table 5. 1St Release Codes
Cause Code
Description
Description
No route to destination
16
Normal clearing
17
User Busy
19
21
Call rejected
28
Address incomplete
34
For a SIP call leg originated release, it's a RFC 3261 release
cause value received from the far side.
123
Description
Malformed message
Unsupported method
480 Temporarily
Unavailable
481 Transaction
Does Not Exist
Origination cancel
488 ReInvite
Rejected
124
Cause Code
Description
Description
Route Rejected
Radius Rejected
Gatekeeper Reject
DNS/GK Timeout
No Response to INVITE
200 OK Timeout
002452502;V1.2;R;WithMedia;181-1071459514@192.188.0.28;0001;Mon Dec 15
11:38:34 2003;Mon Dec 15 11:38:41 2003;Mon Dec 15 11:38:48 2003;480;
EndedByRemoteUser;3;T;000200;H323;;192.188.0.38;9001;192.188.0.28;f0faf
f54-2e6c-11d8-8c4bbd4d562c2265;192.188.0.38;18044;192.188.0.28;10756;G.729b;240;460;6066;
14060;0;0;0;000200;H323;;192.188.0.28;8811;192.188.0.38;e83af3d3-1d2dd811-9f98003048424934;192.188.0.38;19236;192.188.0.28;10758;G.729b;460;240;14060
;6066;0;0;0; F;9001;
Example VSX Call Detail Record
125
126
127
128
APPENDIX B
VSX SPECIFICATIONS
This appendix provides product information regarding the
server that is used by Sansays VSX. All VSX specifications
are subject to change without notice. For additional information regarding VSX servers, contact a Sansay representative
or visit the Sansay web site.
Table 9 lists the available VSX servers and their Sansay
part numbers.
Table 9. VSX Servers
Sansay Part Number
Description
nnn-nnn-nnn
nnn-nnn-nnn
nnn-nnn-nnn
nnn-nnn-nnn
129
Environmental Specifications
Table 10 shows the environmental specifications for the
VSX servers.
Table 10. VSX Server Environmental Specifications
Electromagnetic Interference
AC Input Power
xxx Watts
Physical Dimensions
Operating Temperature
Non-Operating Temperature
20C/hour
5% to 90%, noncondensing
Operating Altitude
Non-Operating Altitude
For information on and an illustration of the rear panel connectors, see Chapter 2, Setting up the VSX.
130
S-VSX-301-TP-1B
131
Place
Postage
Here
Sansay, Inc.
Information Development
4650 Lusk Blvd. Suite 204
San Diego, CA 92121
WARRANTY
Please take a few minutes to complete the product warranty card found at the back of
this book and return it to Sansay, Inc. In addition, if you have any comments or questions regarding Sansay product features, we would appreciate hearing from you. Contact our marketing department directly at:
Sansay, Inc.
Marketing Department
4650 Lusk Blvd. Suite 204
If you have any comments or questions regarding publications for Sansay products,
please direct them to the Technical Publications Department at the above address or
to publications@sansay.com. Be sure to specify the book and section to which your
comment refers.
Warranty
Sansay, Inc., 4650 Lusk Blvd. Suite 204, San Diego, CA 92121
S-VSX-301-TP-1B
Sansay, Inc.
4650 Lusk Blvd. Suite 204, San Diego, CA 92121 (858) 678-0200; FAX (858) 678-0203