You are on page 1of 15

SR-S6000 1.9.

2
Release Notes

2016 SwitchRay Inc.

SR-S6000
NGN Softswitch with Limited SBC Functions & IP PBX

Document type

Release Notes

Software version

1.9.2

Release date
Internal ID

2016-05-19
DOC064195

Department

Documentation Dept.

SwitchRay Inc. reserves the right to change any information contained in this document without prior notice.

COPYRIGHT INFO RM ATIO N

The information contained in this document is the property of SwitchRay Inc.


All rights reserved. No parts of this work may be reproduced in any form or by any means graphic,
electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval
systems without the written permission of SwitchRay Inc.
No third party, organization or individual, is authorized to grant such permission.
Products that are referred to in this document may be either trademarks and/or registered trademarks of the
respective owners. The publisher and SwitchRay Inc. make no claim to these trademarks.
While every precaution has been taken in the preparation of this document, the publisher and the author
assume no responsibility for errors or omissions, or for damages resulting from the use of information
contained in this document or from the use of programs and source code that may accompany it. In no event
shall the publisher and the author be liable for any loss of profit or any other commercial damage caused or
alleged to have been caused directly or indirectly by this document.

Connecting the World for a Brighter Future


25910 Acero, Ste 240, Mission Viejo, CA USA 92691 www.switchray.com

3 | Release Notes

SR-S6000

Table of Contents
SR-S6000 1.9.2-10 ................................................................................................................................. 4
1

Important Changes ....................................................................................................................... 4


1.1

Class 4 Traffic Manager ...................................................................................................... 5

1.2

Class 5 Traffic Manager ...................................................................................................... 5

New Features and Enhancement.................................................................................................. 6


2.1

Traffic Switch (TS) .............................................................................................................. 6

2.2

Class 4 Traffic Manager ...................................................................................................... 6

2.3

Class 5 Traffic Manager ...................................................................................................... 9

Fixed Bugs.................................................................................................................................. 10
3.1

Traffic Switch (TS) ............................................................................................................ 10

3.2

Class 4 Traffic Manager .................................................................................................... 10

SR-S6000 1.9.2-20 ............................................................................................................................... 11


1

Important Changes ..................................................................................................................... 11


1.1

Class 5 Traffic Manager .................................................................................................... 11

New Features and Enhancement................................................................................................ 11


2.1

Traffic Switch (TS) ............................................................................................................ 11

2.2

Class 4 Traffic Manager .................................................................................................... 12

2.3

Class 5 Traffic Manager .................................................................................................... 12

Fixed Bugs.................................................................................................................................. 13
3.1

Class 4 Traffic Manager .................................................................................................... 13

3.2

Class 5 Traffic Manager .................................................................................................... 13

Major Known Issues .......................................................................................................................... 14


Class 5 Traffic Manager ............................................................................................................... 14
Other Known Issues ........................................................................................................................... 14
SR-S6000 1.9.2-21 ............................................................................................................................... 15
1

New Features and Enhancement................................................................................................ 15

SR-S6000

Release Notes | 4

SR-S6000 1.9.2-10
Previous version: 1.9.1-23c

Important Changes
1. Internet Protocol version 6 is now supported. SR-S6000 can work in the mixed IPv4/IPv6
network (Dual-Stack).
Restrictions:

Link-local IPv6 addresses are not supported.

Class 5 Traffic Manager does not support IPv6 addresses.

SS7 Call Agent node does not support IPv6 addresses.

SR-S6000 does not support IPv6 addresses when processing H.323 traffic.

You cannot input IPv6 addresses when configuring connection to DNS, ENUM and
Redis NPDB servers.

SR-S6000 may work with the RADIUS protocol either via IPv4 only or via IPv6
only.

IPv4 addresses encapsulated into the IPv6 format are not supported.

Distinctive features:

Each IP zone can contain a set of subnets of one IP version only.

A call with different versions of IP addresses at the incoming and outgoing legs
cannot be made in the direct connection mode, but only when media traffic is
proxied.

Class 4 Traffic Manager allows using IPv6 addresses almost in every field of the web
interface where you can input an IPv4 address (except for the above-mentioned restrictions).
For a more convenient configuration, the IP version drop-down list was added to the
Equipment table, and the IPv6 zones table was included into the Traffic Switch > TS
configuration > Zones page.
As an IPv6 address is 128 bit long (against 32 bit in case of IPv4), log files and CDRs
containing IPv6 addresses inevitably grow larger. Please note this when allocating free disk
space.
2. Starting from 1.9.2, notifications on problems in SR-S6000 operation are configured in the
Class 4 Traffic Manager web interface. For this, the folder of Traffic Switch > TS
configuration > Notifications settings was added. In addition to already existing methods
of alarms sending (email, SNMP traps and EMS server) you can now configure delivery of
SMS messages by means of connecting to remote SMS gateways via the SMPP protocol
(Short Message Peer-to-peer Protocol). The new function also allows creating several lists of
notification recipients with individual delivery criteria.
Please note:

SR-S6000 automatically records all notification settings made in the web interface in
the /etc/mvts3g/mvts3g-mail.conf file. During upgrade to 1.9.2, already existing
configuration in this file will be changed in accordance with the new format of the

5 | Release Notes

SR-S6000

file, but you will have to manually copy the existing settings to the web interface,
otherwise your notifications wont work.
The format of the Subject field in email messages with notifications was changed.
Now this field has the following format: <Letter subject>.<Alarm ID>, for
example Running out of disk space.DISKSPACE. In the previous versions of SRS6000, the Subject field contained only a subject configured with the help of the
ALARM_SUBJECT parameter in the /etc/mvts3g/mvts3g-mail.conf file. The format
of the field was not changed for email messages with grouped notifications.

1.1 Class 4 Traffic Manager


1. It is now possible to configure partner access to the Class 4 Traffic Manager web interface.
The new function allows granting access for third-party providers to their CDRs, statistics
based on their CDRs, and settings of their equipment.
To organize partner access to the web interface, the administrator creates a special user
account. When a partner signs in using this account, a limited number of web interface pages
are displayed:

All data is read-only. The administrator defines a set of displayed CDR fields separately for
incoming and outgoing call legs.
With appearance of the new CDR fields Incoming leg partner and Outgoing leg partner
you can now build statistical reports with filters by partners. Partners can view reports
generated for them by the administrator.
For more information, refer to SR-S4000 1.9.2 How-to Guide, section 3 Organizing partner
access to web interface.
2. The new version allows adding several tasks for scheduled export of CDRs. For this, the
Export CDRs tool (CDRs > Export CDRs > Scheduled export) was transformed to a table.
3. To ensure reliability of scheduled export to an FTP server, you can now configure access to a
backup FTP server using the following parameters: Backup FTP server: address, Backup
FTP server: login and Backup FTP server: password.
1.2 Class 5 Traffic Manager
1. The procedure of starting, restarting, and stopping Class 5 Traffic Manager logical nodes was
simplified. Now such nodes are managed by the Phoenix process. This allows starting,
stopping, and restarting all logical nodes using one start, stop, or restart command. For more
information, refer to SR-S6000 1.9.2 Traffic Switch Administration Guide.

SR-S6000

Release Notes | 6

2. The Class 5 Traffic Manager scalability was improved: you can now use several active
control logics (Local Exchange Logic & VAS Logic), and allocate a separate Local Exchange
Logic to a domain, which allows you to have a much greater number of subscribers. Besides,
you can now choose whether to have a common entry point of SIP balancer node, or to use a
separate one for each domain. For more information, refer to SR-S5000 1.9.2 Traffic Manager
Web Interface Reference Guide.
3. Graceful shutdown mechanism was implemented: you can now configure unloading of Class
5 logical nodes upon completion of calls. For more information, refer to SR-S6000 1.9.2
Traffic Switch Administration Guide.

New Features and Enhancement

2.1 Traffic Switch (TS)


1. Traffic Switch now adds the Date field in SIP 200 messages in response to SIP REGISTER
requests as per RFC 3261, section 20.17.
2. Rotation of log files of TS configurator and scripting nodes was stabilized. For this, the
rotation mechanism has now a different source of current addresses of nodes of these types. In
the previous versions, the administrator had to explicitly define addresses which might change
dynamically. Now it is enough to define node names for the rotation mechanism to fetch
addresses required for rotation from the management node.
2.2 Class 4 Traffic Manager
1. For a more flexible processing of the Diversion SIP header field, the following methods of
sending redirecting numbers to termination SIP equipment were added:

Send translated

Send original

Send only the first and the last

Send only the first

Send all, except the last

In accordance with this addition, the Term. Dispatch redirecting numbers to the out. leg
parameter in equipment settings was replaced with the Term. Policy of sending redirecting
numbers parameter, and the Override dispatching of redirecting numbers parameter in
dial peer settings was renamed Policy of sending redirecting numbers.
2. For writing the Diversion header field in INVITEs to be sent to external SIP routing servers,
the parameter Policy of sending redirecting numbers to SIP-server was added to the
Equipment table.
3. The URI match pattern for redirecting number parameter was added to the Equipment
table. It allows configuring extraction of URIs from the Diversion SIP header field.
4. The Term. Use incoming parameters for ISUP check box was added to the Equipment
table. It allows defining policy of sending ISUP parameters to termination SIP-T/I equipment.
With this check box selected:

7 | Release Notes

SR-S6000

If origination equipment works under the SIP-T/I protocol, SR-S6000 sends


parameters from the ISUP section of the incoming SIP message to the termination
equipment.

If origination equipment works under the SIP, H.323 or SS7 protocol, SR-S6000
sends termination equipment ISUP parameters generated from incoming signaling
data obtained after translations defined in the settings of the origination equipment
record.

The cleared check box corresponds to the old behavior, that is, SR-S6000 generates ISUP
parameters for outgoing calls based on incoming signaling data obtained after all translation
stages.
5. The Term. realIP sending policy parameter was added to the Equipment table. It allows
defining a method of recording the realip proprietary parameter into the From header field
of SIP INVITE requests sent to termination equipment. Possible values of the parameter are:

Do not send

Send orig. realIP, if exists

Send orig. realIP (if exists) or IP address from Contact

Send orig. realIP (if exists) or IP address where INVITE came from

6. To speed up inserting and processing of CDRs, values in the fields with disconnect codes
(Disconnect code, Aux. SRC disconnect codes, Aux. DST disconnect codes) are now saved
as plain text, not as references to corresponding records in the table of disconnect codes. After
upgrade to 1.9.2 these fields will become empty in those CDRs which were saved in previous
versions. To fill them please contact our technical support team. You can still use old
counterparts of the above-mentioned fields during CDR export.
7. The Successful call field was added to the tables with CDRs. Class 4 Traffic Manager
determines successfulness of a call by a disconnect code with which a call was ended (the
Successful field in the table of Global settings > Disconnect codes).
8. The following web interface text strings were renamed:

Basic configuration -> Routing configuration

Basic proxy configuration -> Routing configuration

Basic routing -> Routing configuration

Local balancing group -> Outgoing load balancing group

Proxy balancing group name -> Name

Proxy balancing groups for IPv4 -> Outgoing SIP load balancing groups

Proxy global configuration -> Global configuration

Register routing module -> Registrations routing method

Request routing module -> Requests routing method

Remote balancing group -> Incoming load balancing group

Signaling balancing group name -> Name

Signaling balancing groups for IPv4 -> Incoming load balancing groups

SR-S6000

Release Notes | 8

SIP Proxy -> SIP balancer node

SIP proxy balancing group -> Outgoing SIP load balancing group

SPStaticRouting -> Static routing

SPTSRouting -> Dynamic load balancing

TS routing -> Load balancing

TS routing configuration -> Balancing groups selection

9. Results of the call simulation procedure now contain more detailed information on involved
rules of pre-routing translations.
10. The new version features the Quick Search function. It allows filtering any web interface table
by values in any of its columns. Search results appear almost immediately, without page
reloading.

For more information, refer to SR-S4000 1.9.2 Web Interface Reference Guide (6.4.4 Using
Quick Search).
11. The function of simple/advanced settings is now unavailable for tables and tools which have
less than 5 columns (parameters).
12. You can now jump to the following related tables (using the Filter related tables item in the
context menu):

From the table of Dial peers:

From the table of Routing policies:

From the table of SIP-routing groups:

From the tables with CDRs:

9 | Release Notes

SR-S6000

In the table of Call debugging rules, you can now jump to four more related tables:

13. You can now jump to a related table not only with the help of the context menu, but also by
clicking the icon, which appears when you hover over a record in a source table:

14. The new version allows quickly switching to a page with information on a lookup record. For
this, the icon was added. It appears to the right of a lookup record name when you hover
over a source record in a table:

15. It is now possible to automatically fill out the form of the Debugging > Call simulation tool
based on the information from a specific CDR. For this, the Related procedures > Call
simulation item was added to the context menu of a CDR.
2.3 Class 5 Traffic Manager
1. We implemented the possibility to make calls through a registered gateway without replacing
Destination number with the gateway registration name. To support the previous behavior,
after the upgrade, a rule will be created to translate destination numbers into the gateway
registration name (Phone number translation section in gateway settings).
2. Now it is possible to configure the format of recorded conversation files (Call recording >
Common settings page). For more information, refer to SR-S5000 1.9.2 Traffic Manager
Web Interface Reference Guide.
3. To provide users of Mayak Mobile application with more detailed information about their
contacts, we implemented the possibility to use vCards. To upload subscriber vCards, open

SR-S6000

Release Notes | 10

the Value added services tab in subscriber account settings. To upload external contacts
vCards, open the Subscribers > Contact groups for Mayak Mobile page. For more
information, refer to SR-S5000 1.9.2 Traffic Manager Web Interface Reference Guide.
4. To provide ROOT domain subscribers who use Mayak Mobile application with the possibility
to get a contact list of all subscribers of this domain, we made it possible to create a Virtual
group in the ROOT domain (Subscribers > Contact groups for Mayak Mobile page).
5. Now it is possible to view detailed information about the amount of allocated and used objects
and services of a domain you are logged in and its child domains (Basic configuration >
Licenses > Objects usage information page). For more information, refer to SR-S5000 1.9.2.
Traffic Manager Web Interface Reference Guide.
6. Now it is possible to make calls over the internal protocol (NULL) without proxying media
traffic. To do so, select Direct after connect in the Proxy Media Policy drop-down list in the
settings of endpoint profile that uses the internal protocol. This improvement allows
significantly reducing load on media nodes.

Fixed Bugs

3.1 Traffic Switch (TS)


1. In the redundancy scheme with several active nodes, when SR-S6000 interworked with a
signaling gateway in the so-called override mode (that is, when a signaling gateway
independently selected one of the available SS7 Call Agent nodes to work with), upon
deactivation and the consecutive attempt of activation of a previously active node, servicing
of SS7 calls completely stopped.
3.2 Class 4 Traffic Manager
1. Routing policies with the dp.cps expression worked incorrectly. Class 4 Traffic Manager recalculated values of this statistical parameter only when a call passed through a dial peer. Due
to such behavior dial peers with bigger CPS values could stuck at the end of the list with
routing alternatives. Starting from 1.9.2 values of this parameter are updated when it is used
in a routing policy.
2. Upon selection of a pre-routing translation rule during call processing, Class 4 Traffic
Manager used an initial set of origination groups, disregarding modifications defined in the
pre-routing translation rules selected previously during processing of the same call.
3. When the user deleted records from the following tables:

Traffic Switch > TS configuration > SS7 > [SS7 Call Agent node name] >
ISUP/Call Control > ISUP Connections (either manually, or using the Delete
ISUP connection wizard),

Traffic Switch > TS configuration > SS7 > [SS7 Call Agent node name] >
MGCP > MGCP endpoints

the data was removed from the database, but was left behind in internal Traffic Switch tables.
This problem caused hanging of objects pertaining to SS7 Call Agent nodes.

11 | Release Notes

SR-S6000

SR-S6000 1.9.2-20
Previous version: 1.9.2-10

Important Changes
1. You can now configure encryption/decryption of SIP calls. This feature allows you to
prevent eavesdropping, tampering, and forgery of SIP calls, as well as to service SIP traffic
where it is partially or completely forbidden for various reasons, for example, legislatively,
or on the level of providers networks who want to secure their corporate interests.
Encrypted signaling messages are transmitted via the secure TLS channel with the help of an
SSL certificate. An encrypted media flow is transferred according to the SRTP protocol. For
more information about the new feature, as well as instructions on its configuration, refer to
SR-S6000 1.9.2 Traffic Switch Administration Guide.

1.1 Class 5 Traffic Manager


1. A new service, called Mass calling, was created. The service allows organizing automatic
dialing of a defined list of numbers in order to play voice messages to the called party or to
connect the called party with an agent. For more information about the service use and
configuration, refer to SR-S5000 1.9.2 Administrator's How-to Guide.
2. The schedule functionality was extended:
Every schedule configured in the settings page of a rule (routing, call forwarding,
agents availability, etc.) is now saved in the Basic configuration > Schedules page
and can be then applied to configure other rules.
Schedule settings consists of the Common schedule used to configure worktime of a
rule per weekdays and the Special schedule used to configure special schedule for
particular dates (for example, holidays).
Schedules are created based on templates, which makes it easier to create new
schedules and to edit existing ones: adding a special schedule to a template applies
to all schedules based on this template.

New Features and Enhancement


1. The logic of email and SMS notifications sending was improved (the Class 4 web interface
table of Traffic Switch > TS configuration > Notifications settings > Notifications >
Subscription). In the previous versions, SR-S6000 sent a notification, if both an alarm and
its severity level were selected in a record of this table. Now SR-S6000 sends a notification,
if either an alarm or its severity level is chosen.

2.1 Traffic Switch (TS)


1. You can now re-define the default delay (200 msec.) before sending of SIP 100 Trying
messages in response to SIP INVITEs arriving at the SIP balancer node. For this, a new
parameter called Delay in Trying response, msec was added to the Class 4 web interface
table of Traffic Switch > TS configuration > Realms.

SR-S6000

Release Notes | 12

2.2 Class 4 Traffic Manager


1. For the purpose of troubleshooting of problems related to translations of redirecting
numbers, the following CDR fields were added:

Incoming redirecting number type

Outgoing redirecting number type

2. It is now possible to block and unblock ISUP connections of an SS7 Call Agent node via
API. An example of the source code can be found in SR-S4000 1.9.2 API Reference Guide
(5.9.2 Calling Context Procedures).
3. Now the user can quickly get log of the first debug call matching a call debugging rule. For
this, a special function called Get Call Log was added to the context menu of the
Debugging > Call debugging rules table.
4. For a more flexible and transparent processing of ISUP parameters of incoming SIP-T/I
calls, the following parameters were changed in the Equipment table:

The Orig. use ISUP SRC alias check box is now the Orig. use SRC number
parameters from drop-down list

The Orig. use ISUP DST alias check box is now the Orig. use DST number from
drop-down list

The Orig. use ISUP Diversion check box is now the Orig. use Diversion from
drop-down list

The Orig. use ISUP CPC check box is now the Orig. use CPC from drop-down list

For each drop-down list the following values are available:

SIP header

ISUP section (if present), or else SIP header

ISUP section

Upgrade to the new version will automatically change the existing equipment records. For
selected check boxes, the ISUP section (if present), or else SIP header value will be
selected. For unselected check boxes the drop-down lists will have the SIP header value.
2.3 Class 5 Traffic Manager
1. The Class 5 Traffic Manager scalability was extended: you can now use a separate server for
call recording.
2. Using API it is possible now to search for subscriber accounts by a group (of access, feature,
pickup types) or by a service package. For information about new commands, refer to SRS5000 1.9.2 API Reference Guide (Subscriber Account Commands).
3. Editing subscriber accounts using API becomes more flexible: you can now add/remove
groups and service packages without involving other parameters of a subscriber account. All
groups and service packages that are not specified in the request remain unchanged. For
information about new commands, refer to SR-S5000 1.9.2 API Reference Guide
(Subscriber Account Commands).
4. For a more flexible balancing of outgoing SIP traffic, it is now possible to select a balancing
group for static endpoints in subscriber and gateway settings.

13 | Release Notes

SR-S6000

5. Within the Call Transfer service, it is now possible to display the transferee phone number
to the subscriber receiving the call transfer.

Fixed Bugs

3.1 Class 4 Traffic Manager


1. The call simulation procedure hung when:

A dial peer selected for simulation had a termination equipment list, in which a SIP
routing server was followed by an equipment record with the Gateway type.

The resulting list of routes contained codec groups with different numbers of codecs.

2. When processing Calling Partys Categories (CPCs), Class 4 Traffic Manager did not
differentiate between records having equal codes, but different types (ISUP and ISUP-R).
For example, ISUP, 9 and ISUP-R, 9.
3. When SR-S6000 processed calls, it did not select records from the table of Equipment >
Default gateway endpoints, if they had non-empty Override registration address list. The
user was also not able to add a record to this table with more than one address or network in
the Override registration address list.
4. After the user edited records in the following tables:

Equipment > Origination groups

RADIUS configuration > RADIUS attributes

Global settings > Disconnect codes

the scripting node re-read changes only after it had been restarted.
3.2 Class 5 Traffic Manager
1. The Music on hold prompt of the Hunt Group service started playing to the caller from
the very beginning every time after it had been interrupted for playing waiting time and
position in queue prompts. Now the Music on hold prompt resumes its playback from
where it stopped.

SR-S6000

Release Notes | 14

Major Known Issues


Class 5 Traffic Manager
1. Simultaneous editing of the same object through different web sessions results in saving
invalid data to the DB. This can lead to serious System failures, if, for example, routing data
is changed this way.
Workaround: Several administrator should not simultaneously edit the same object (a
subscriber account, a gateway, a service instance, etc.).

Other Known Issues


The full list of known issues is available on our Help Desk.
For SR-S4000:
Knowledgebase : IN ENGLISH > SR-S4000 / MVTS Pro > Troubleshooting > Known
Issues
For SR-S5000 & SR-S6000:
Knowledgebase : IN ENGLISH > SR-S5000 & 6000 / RTU > Troubleshooting > KNOWN
ISSUES

15 | Release Notes

SR-S6000

SR-S6000 1.9.2-21
Previous version: 1.9.2-20

1 New Features and Enhancement


Earlier, when the Traffic Switch running on multiple servers notified a user of a problem via
email or SMS, it was not clear on which server the problem occurred. Now, if needed, the
Traffic Switch can specify server identification information in email and SMS notifications
(in the subject field of an email message and in the text of an SMS). To configure this
function, the metavariables {ip_addr}, {hostname} and {fqdn} are used.