mod03 gl features training

EN8811EN00EN Siemens Enterprise Communications GmbH & Co. KG 2011. All rights reserved.Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG

1

OpenScape Voice Siemens

OpenScape Voice

Contents1 CMP GUI Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 CMP Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 Configuration tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.2.1 OpenScape Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2.2 OpenScape Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.2.3 RG8700 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.2.4 Unified Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.2.5 CMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.3 Maintenance tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.4 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Flexible Ethernet circuit and IP Address Configuration . . . . . . . . . . . . . . . . . . . . 172.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.2 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.3 Node Configuration Parameters Editor (NCPE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Remote Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.2 Supported Platfforms / Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.3 Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 RTP Parameter Management via Assistant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.2 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.3 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 Provisioning Errors in CMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

FN9821FNUTFN_BABZZZEDDZ

EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11

EN8811EN00EN Siemens Enterprise Communications GmbH & Co. KG 2011. All rights reserved.

Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG

2

OpenScape VoiceSiemens

5.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375.2 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385.3 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 OSV Node Status Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416.2 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

6.2.1 Change Functional Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446.2.2 Restart Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456.2.3 Power Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466.2.4 Change Operational Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476.2.5 SRXCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

7 Activate and Synchronize OSV partitions via CMP . . . . . . . . . . . . . . . . . . . . . . . . 517.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517.2 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517.3 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

7.3.1 Activate Backup version and Synchronize Active version to Backup . . . . . . 537.3.2 Activate backup version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567.3.3 Software Activation enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

8 Split Audit Functionality fromRegistration Renewal 63

8.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638.2 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638.3 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659 Emergency Call SNMP Trap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699.2 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699.3 Emergency Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709.4 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

9.4.1 Configure Emergency Calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719.4.2 Enabling E911 SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

10 SIPQ CodSet4 Transit Counter IE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8110.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8110.2 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8110.3 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8311 Best Effort SRTP for SDES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8511.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8511.2 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8711.3 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9212 Support for multiple prime line registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10312.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10312.2 Application secanrio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


3


12.3 Functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10512.4 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10613 PIN for private / business calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10913.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10913.2 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11013.3 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

13.3.1 CDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11613.4 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11914 Intercom / Speaker Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12114.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12114.2 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

14.2.1 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12214.3 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12314.4 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



4



EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


5


1 CMP GUI Changes

1.1 CMP OverviewThe new default screen after successful logon.

Active Alarm view

Current user settingsThe new tab bar


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



6


In Version 6 your personalized user options are limited to Number of Rows and Disabling Con-firmations.

The timeout value has been moved to Configuration CMP System_Settings


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


7


1.2 Configuration tabWe have a completely redesigned Configuration tab where all the various assistants have been moved.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



8


1.2.1 OpenScape VoiceThis is the biggest change for your daily use. The tabs are gone and everything is ICON based.

There explanations are at the bottom.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


9


We have opened each ICON to show the available content. As you can see these are very sim-ilar to what was available previously via the buttons on the top for BG Global General and Administration.

V6

V5


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



10


1.2.2 OpenScape BranchItems have been moved from buttons across the top, to the side, new items to be covered du-ring the OpenScape Branch course.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


11


1.2.3 RG8700The RG8700 menu items have been moved from buttons across the top, to the side, but nothing really new.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



12


1.2.4 Unified CommunicationsThe Unified Communications menu was previously found in the Users & Resources tab. Plus a few new fields that will be shown during the UC Training course.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


13


1.2.5 CMPYou now have a tab for CMP information / configuration.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



14


1.3 Maintenance tabThe Maintenance Tab is very similar to previous versions.

V6

V5


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


15


1.4 User ManagementWe also have a completely new tab for User Management. This will be used for global user management (HPUM is the predecessor application). This will be explained later in the trai-ning.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



16



EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


17


2 Flexible Ethernet circuit and IP Address Configuration

2.1 OverviewThis feature allows for a flexible configuration of Ethernet circuits and IP addresses.In extreme cases an OSV can now be installed with one used Ethernet circuit (pair in case of redundancy) and one single IP address.The OSV feature of flexible Ethernet circuits and IP addresses applies only to new installations, i.e. split mode upgrade and toolkit migration will not support

l Reduction or combination of IP addresses or Ethernet circuits of current existing in-stallations

OpenScape Voice V5 node with 4 ethernet circuit pairs

OSV Node 1

AdminLAN / VLAN / IP subnet

Mtc Controller(IMM, iRMC)

SignalingLAN / VLAN / IP subnet

X-ChannelLAN / VLAN / IP subnet

Router(admin)

Router(billing)

Router(signaling)

Router(x-channel)

1 Admin Eth. pair

1 Billing Eth . pair

1 Signaling Eth. pair

1 X-Ch Eth. pair

BillingLAN / VLAN / IP subnet

Layer 2 Switch

with VLANs

Or

separateLAN

switches


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



18


OpenScape Voice V6 node with 1 ethernet circuit pair and x-channel shared

However, once OSV is installed on the new SW releasel The Easy IP address changing feature (NCPE) can be used to change the number

of used Ethernet circuits and IP address values.This feature also applies to virtual OSVs.

OSV Node 1

Mtc Controller(IMM, iRMC)

1 Eth. Pair for

Admin, Billing ,

Signaling, X-Channel Admin and Signaling and Billingand X-Channel Default Router

Layer 2 Switch


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


19


2.2 Functional DescriptionThe OSV node can be installed to use less than the current 4 Ethernet circuit pairs (3 ports for simplex) and with less IP addresses, down to one single IP address.The underlying platform (physical and virtual) should still have the default number of Ethernet ports to allow for future port expansion. The default number of 'platform' ports is:Entry: 1Simplex: 3Duplex: 8Virtual: 4

However, if a port is not used, i.e. not assigned to admin / billing / signaling / x-channel, it will be ignored by OSV SW (e.g. never alarmed).For the virtual OSV this means that the virtual machine always needs to be created with 4 net-work connections, in the following sequence:NIC 1: adminNIC 2: signalingNIC 3: billingNIC 4: cross_connect

Even if, e.g., NIC 2 and NIC 3 are not used if signaling, billing and admin are assigned to the same IP subnet labeled admin.

7The billing and cross connection on virtual installations has been swapped in V6 !Remember to change the guest vSwitch mappings !


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11

Ope

nScape

Voice

EN8811EN

00EN

Siem

en

s E

nterp

rise C

om

mu

nication

s G

mbH

& C

o. KG

2011. All

rights re

served

.

Siem

en

s E

nterp

rise C

om

mu

nication

s G

mbH

& C

o. KG

is a

trade

mark

licen

see of

Siem

en

s AG

Siem

en

s

20

With this feature, OSV installation associates logical interfaces with physical interfaces by assigning each logicalinterface to a nafo-group and Ethernet circuit or bond device:

Example of logical/physical interface mapping in a V5 OSV system using 4 separate subnets and in a V6 OSV system using 1 shared subnet (eth assignment on IBM X3550 M2/M3 or FSC RX200 S6)

Logical-Interface

NafoGroup

Entry IntegratedSimplexStandardDuplex Virtual

V5 / V6 V5 V6 V5 V6 V5 V6Admin nafo_alias

eth0eth0

eth0bond0 = eth0 + eth4

bond0 = eth0 + eth4

eth0

eth0Signalling nafo_udp eth1 bond1 = eth1 + eth5 eth1

Billing nafo_bms eth2 bond2 = eth2 + eth6 eth2X-Channel nafo_xch N/A bond3 = eth3 + eth7 eth3


EN8811ENTTEN_L._Maldonado_Pastor_17-10-11


21


OpenScape Voice IPs and Subnets

Function forIP address

Subnet Remark Virtual

Admin

Admin

The node IP address used for installation and all OAMP functions

no

LSM On this IP the OpenScape Voice receives SNMP traps from routers reporting link status changes

yes

RSA Integrated Maintenance Controller of node(IMM, iRMC or VMK)

no

Signaling

Signaling

Static IP address for the signaling network (no traffic). noSIP SIP signaling over UDP, TCP or TLS yesSIP MTLS SIP signaling over MTLS (mutual TLS) yesMGCP MGCP / NCS signaling for media server yesCSTA CSTA signaling over TCP yesSBC LAN Local IP address for the SBC function of the OSV Entry,

used for signaling and mediano

Billing Billing For sending billing (CDR) files noX-Channel X-Channel For the node to node communication. no

may move if nodes share the same network

>The purpose of the Superuser IP is to control the 'access control list' that defines which SOAP TCP/IP port can access what OSV data via the SOAP/XML interface.This is needed to set up the access control when OSV is configured in a hostedscenario with customers accessing the OSV directly (not through CMP).In the hosted scenario, it is expected that access control is made available to an Ad-ministrator logged on to CMP.So he can specify the access to different ports based on the customer's access to specific data, e.g. BG related.Typically the super IP address is set to CMP's address.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



22


IPs and Subnets outside OpenScape Voice

Function forIP address

Subnet Remark

Default GW

Admin

Default admin gateway for source based routingGateway for RSA Router IP to reach maintenance controller of partner nodeSuperUser IP address of management server with super user

privileges (generally the integrated Assistant)SurvivalAuthority

Needs to be accessible from both nodes admin network and has to be installed at a third location

Default RouterSignaling

Default router for all HiPath traffic not explicitly routed, e.g. by static routes or source based routing

Default GW Default signaling gateway for source based rutingDefault GW Billing Default billing gateway for source based routingGateway GW X-Channel Router IP, if the x-channels subnets of the two nodes are

different


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


23


Standard IP address assignment (4 network segments)The following tables shows the default IP addresses used from the NCPE with 4 networks.Note: All netmasks are 255.255.255.240.

Management

1 = If node 1 is down

2 = Not for IBM X3250 M2

Signaling

Billing

Cluster Interconnect

Node Same subnet Separated subnets Simplex EntryNode 1 Node 2 Node 1 Node 2

Admin Subnet 1.2.3.0 1.2.3.0 1.2.4.0 1.2.3.0 1.2.3.0Physical .6 .7 .6 .7 .6 .6LSM .14 .14 (1) .14IMM / iRMC .10 .11 .10 .11 .10 .10 (2)


Signaling Subnet 1.2.3.48 1.2.3.48 1.2.4.48 1.2.3.48 1.2.3.48Physical .52 .53 .54 .55 .52 .53SIP .54 .55 .54 .55 .54 & .55 .55MLTS .56 .57 .56 .57 .56 & .57 .57MGCP .58 .59 .58 .59 .58 & .59 .59CSTA .60 .61 .60 .61 .60 & .61 .61


Billing Subnet 1.2.3.32 1.2.3.32 1.2.4.32 1.2.3.32 1.2.3.32Billing .38 .39 .38 .39 .38


X-Ch. Subnet 10.1.3.0 10.2.3.16 10.2.4.16X-Ch. Logical .1 .2 .22 .23


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



24


Standard IP address assignment (admin, signalling and billing network merged)The following tables shows the default IP addresses used from the NCPE with 2 networks.Note: All netmasks are 255.255.255.240.

Management / Signalling / Billing




Admin Subnet 1.2.3.0 1.2.3.0 1.2.4.0 1.2.3.0Physical .6 .7 .6 .7 .6LSM .14 .14(1) .14IMM / iRMC .10 .11 .10 .11 .10 .10 (2)SIP

.12 .13 .6 .7 .6SIP-MTLSMGCPCSTA

X-Ch. Subnet 10.1.3.0 same as Adminsame as Admin

X-Ch. Logical .1 .2 .22 .23


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


25


Standard IP address assignment (minmized set of IP addresses)The following tables shows the default IP addresses used from the NCPE with one network.Note: All netmasks are 255.255.255.240.

Management / Signalling / Billing



3 = When the OSV is installed with the same IP address for SIP(UDP/TCP/TLS) and for

SIP(MTLS), then non-standard port 5161 has to be used. All SIP endpoints that are to be connected via MTLS have to use this non-standard TCP/IP port when connecting to the OS-VSIP-MTLS uses Port 5161.This port can be changed via the Parameter Srx/Sip/IpPortMTLS.

UC Mediaserver on Entry / Integrated SimplexThe UC Media Server SIP listening ports and the MS SIP endpoint in the integrated OSV (in-cluding OSV Entry) will be associated with the non-standard port numbers 5062 and 5063 for SIP and SIP-TLS signaling between OSV and MS. This includes the creation of the necessary packet filter rule and the automatic change during upgrade to V6.Make sure that the UC Media Server SIP listening ports will be changed via CMP from 5060 / 5061 to 5062 / 5063 !

Node DuplexSame subnet

DuplexSeparated subnets

Simplex Entry

Node 1 Node 2 Node 1 Node 2Admin Subnet 1.2.3.0 1.2.3.0 1.2.4.0 1.2.3.0 1.2.3.0Physical Admin

.6 .7 .6 .7.6Physical Signalling

Physical BillingX-ChannelIMM / iRMC .10 .11 .10 .11 .10 .10 (2)SIP

.12.13

.6 .7 .6 (3) .7 (3)SIP-MTLSMGCPCSTALSM .12 (1)


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



26


2.3 Node Configuration Parameters Editor (NCPE)There are two important changes on the NCPE in the IP Configuration menu:

IP Configuration 1 of 6

>The VLAN support for the OpenScape Voice Entry has been removed already ion V5.

Software Installation Server(not used for OpenScape Voice)

Bondig interface (for redundancy)Network Interface Configuration(should not be changed)

Physical IP for Node 1

1.

2.

Default routerSubnet sharing. Can be ether:l Mgmt-Billing-Signaling-Separated

Same scenario as used up to V5l Mgmg-Billing-Shared

Combines the Managemnt / Billingl Mgmt-Billing-Signalling-Shared

Combines all regular networksCombines X-Link with Managent

Gateway for this segment

Network definition (Node 1 + 2 !)


New in V6

Link Status Manager IP

}


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


27


All IPs which belongs to a specific nework are now located under this screen. e.g. the signalling IPs:

Only the IPv6 IPs are still located on the 2nd menu (see next page).

Bondig interface (for redundancy)Network Interface Configuration(should not be changed)


Gateway for this segment

Network definition (Node 1 + 2 !)


}

}}

Virtual IPs for Node 1

Virtual IPs for Node 1


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



28


IP Configuration 2 of 6The IP Configuration 2 of 6 menu contains now only the in OpenScape Voice V5 introduced IPV6 configuration for the SIP, SIP-MTLS and MGCP/NCS signalling managers.All IPV4 configuration has been moved to the IP Configuration 1 of 6 menu as described on the previous page.

All other menus of NCPE are unchanged !

} IPV6 Signalling Managers for Node 1IPv6 Subnet mask for Signalling NetworkIPv6 Default Router for Signalling Network

} IPV6 Signalling Managers for Node 2


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


29


3 Remote Upgrade

3.1 OverviewThe Remote Upgrade procedure can be used to execute the upgrade from on release or DVD version to another without physical access to the OSV server.It allows the administrator to upload the Image ISO to the system(s) as well as any patches and have the system(s) get updated from a remote location.The procondition is that a Remote Management Card (RSA / RMC) is installed in the server.

3.2 Supported Platfforms / ConfigurationsThe remote upgrade is availabe on a Integrated Simplex, Standard Duplex and Virtual config-urations (with vSphere Client) on all servers with a Remote Management Card:

l IBM X3250M3

l IBM X3550M2 / M3l IBM X3650T

l FSC RX330S1l FSC RX200

The OpenScape Voice Entry (IBM X3250M2) is not supported as it does not have a Remote Management Card.The minimum installed release must be V3.1 SMR2 (imagebased installation) or the system must be converted with the upgrade MOP to a Multi-Partioning installation.

>This feature has been introduced with V5+.

7During Remote Upgrades there will be a Service Outage so please schedule this up-grade during a maintenance window.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



30


3.3 Upgrade ProcedureThe upgrade will be prepared in the following steps:

1. Initially transfer the Toolkit RPM to /software directory2. Install Toolkit RPM via

rpm -i --replacefiles --replacepkgs UNSPmigration-.rpm:

(This will create the /repository/upload directory for you).3. Move the Toolkit RPM from /software to /repository/upload

4. Upload the following files to /repository/upload directory on the system(s) Image ISO Node configuration (node.cfg.primary|secondary depending on node you are on) Patchsets (Optional, please use cumulative if possible) OSV License Files Response configuration (Optional, the image already creates default response.cfg

files for installation of OSV APPs. Should only be placed on Integrated Systems!)

5. Repeat steps above for Node 2 in a duplex configuration.

# cd /software# rpm -i --replacefiles --replacepkgs UNSPmigration-V1.05.rpmChecking rsync package : rsync-2.6.8-53.7Checking rsync package : package rsync is not installedMigration tools installed successfully.

# cd /software# mv UNSPmigration-V1.05.rpm /repository/upload

/

repository

upload

.isonode.cfg.V5.00.01.ALL.11_PS0001.tarV5.00.01.ALL.11_PS0002.tar

V5.00.01.ALL.11_PS0008.tar

xx-xx-xx-xx-xx-xx.xml

.

.

.

V5.00.01.ALL.11_PS0008E01.tar


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


31


Now, connect to the Remote Management Card to make sure that the upgrade process can be monitored. Start the upgrade on node 1 by executing the upgrade8k command (this will export the current configuration and lock the partition) and reboot the system.

Once the system has been rebooted, the license agreement must be confirmed and the ques-tion for overriding the harddisk must be answered with yes.

# upgrade8kcommon8k: Your current working directory is valid.//////////////////////////////////Current Active image://////////////////////////////////Active:primary, Fallback:secondaryDetected scsi disk.Toolkit Version : UNSPmigration-1.06-01 - Checking root password for expiry. - Checking solid password for expiry. - Checking srx password for expiry.

.

.

.

//////////////////////////////////Current Active image://////////////////////////////////Active:primary, Fallback:secondary - Processing for current build V5.00.01.ALL.11. - Admin ip: 1.21.210.101Export completed : Thu Sep 8 20:09:49 CEST 2011.upgrade8k: Checking for licenses to import.Extracting image dvd.167216 blocksupgrade8k: Setting up primary boot device(sda)./////////////////////////////////////////////////////////////////upgrade8k:Remember to reboot the node(s) to complete the upgrade./////////////////////////////////////////////////////////////////Done.

Note: Typing yes or format will erase all data from unlocked partition on the disk. : yes - Erases data from the first unlocked image. : no - Aborts installation. : format - Reformats harddisk, user looses all the data. : lockprim - Erases data from the secondary partition. : locksec - Erases data from the primary partition.Do you want to continue with Installation - Enter yes/no/format/lockprim/locksec) ? yes


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



32


The upgrade process wil lbe started and executes the following steps:

l Image Installation will be started and the user will be asked (on both nodes if duplex) whether to proceed with the Image Installation on Inactive Partition. Once user accepts (on both nodes if duplex), Image Installation will commence.

l System(s) will reboot once Image Install completes.l If patches were provided these will also get applied.l Once system(s) reach state 4 the configuration will be imported and the license files will

be applied.l Partitions will be unlocked

upgrade8k started viaRemote Managemnt Card

Configuration willbe exported

Partition will be locked

ImageInstallation

Install OSV Patches

Partition will be unlocked

Configuration willbe reimported

ApplyLicense File


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


33


4 RTP Parameter Management via Assistant

4.1 OverviewThis feature introduces a generic interface in OpenScape Voice Assistant GUI for the manage-ment (view / modify) of OpenScape Voice RTP Parameters. This interface will support RTP pa-rameter data such as

Current value Default/Recommended value Value type/range/unit Description

4.2 Functional DescriptionService technicians, can view RTP paramters names and values in OpenScape Voice Assis-tant in the form of a list and search for a specific RTP parameter or for a set of RTP parameters with certain search criteria (e.g. Srx/Sip/*).On an RTP parameter basis, information such as usage, default / recommended value, type, value ranges, process restart, as well as current value is displayed. The change of the RTP parameter value is also possible for some RTP parameters.

>This feature has been introduced with V5+.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



34


4.3 UsageThe RTP Parameter can be accessed viaConfiguration OpenScape Voice Administration General Settings RTP

With the filter bar, a parameter can be search. e.g. to search a specific parameter enter the parameter name or the first part of the parameter in the Search for: field, change the value in the in field to Name and click on Search. Only the matched parameters will be shown:

Click on Show All to get the full parameter list.

>If a parameter has been changed, it will appear in red color.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


35


To get list of all changed parameters, set the in field to Is Default Value and the Search for: field to No. As the result, all parameters which are not on his default value will be shown:


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



36


To change a parameter, click on the parameter name. The following window will be opened:

If the parameter should be changed, enter or choose the new value in the Value field and click on Save.

Parameter nameValue type / range/ unit(i.e. string/integer/boolean)

Range(i.e. min. / max., false / true)

Current value

Value

Default / Recommendedvalue

Unit (i.e. seconds / number)


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


37


5 Provisioning Errors in CMP

5.1 OverviewCurrently (V6 and earlier) Provisioning errors due to inconsistency between the OSV and the devices are logged in log files (/log/HiqLogProvisioning.log.*).Prior to Version 6 you were required to review the error logs in file format which looked similar to this:

This new feature will allow us to display these logged provisioning errors in a format which is more user friendly.Accomplished by:1. Processing all log entries of provisioning errors and extracting specific information.2. Sending the zipped result file to the users desktop.3. Extracting files from zipped location to user specified folder4. User imports the file (based on | character as a delimiter) to an Excel sheet and reviews

the results.

{serial_number => 38891,time => 'Tue Apr 12 16:48:07 2011',time_secs => 1302641287,time_usecs => 68806,process_name => 'sipRegistrar11',file_name => 'sipRegAppl.cc',line_num => 966,pid => 31642,log_priority => 'HIGH',log_category => 'SUB_PROVISIONING_ERR',log_appl_reason => 69,component_id => 'UNKNOWN',appl_event_id => 69,num_prior_occurences => 60,managed_suppression_count => 10,managed_suppression_time => 1,data_length => 130,data => 'REGISTER mesg received with invalid SIP transport from DN=18146610892 device=10.41.10.93:5060. Device transport=UDP configured=TCP',}


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



38


5.2 Functional DescriptionThis feature extracts specific information from /log/HiqLogProvisioning.log.* files:l IP address of the node

l Log Categoryl Number of Occurrencesl Time and Date of the event

l Data / Description of the errorFrom this data a unique record for each event with date & time of first and last occurrence will be created (Execution of processing in asynchronous manner). The result will be provided as a compressed .csv file using the pipe symbole as the field delimiter.

Provisioning errors that are logged:1. Contact header in REGISTER msg has Expires value less than allowable OSV Expires

value.

2. Invalid transport type in incoming REGISTER message. 3. Registering DN is not a valid Line appearance on this device.4. Not Prime Registration. Secondary line is not allowed to register before primary line. 5. Registering endpoint not configured in the OSV as a subscriber line.6. Digest Auth credentials are not correct or no credentials are configured.7. Media renegotiation will occur due to unsupported secure media in the SDP.8. CPU directed feature invoked by subscriber not provisioned for this feature.9. Subscriber for call pickup service not provisioned in the OSV.10. A keyset SUBSCRIBE message was received for a DN that is provisioned as a non-keyset

device on the OSV.11. Invalid event header received in Message Waiting Indicator NOTIFY msg. 12. Invalid Toggle access code invoked or provisioned on the OSV 13. Toggle invoked for subscriber who does not have feature provisioned on the OSV.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


39


5.3 UsageThe feature is invoked from CMP under:Maintenance Monitoring Tools & Utilities OpenScape Voice Logging

A .zip archive will be downloaded:

Select the OSV (Switch Name) from witch the log files should be retrieve and a log catgory.Optional, check the Set Time and Date and choose a Start Time / Date to reduce the amount of data to be retrieved.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



40


The included file can be imported in excel by using the | (pipe key) as a delimiter:

Your content will be displayed and you can then review using the various tools from Excel.The first line shows the ammount of downloaded records. The main section (row 2) contains the categories and will help you sort based on these categories or their associated content.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


41


6 OSV Node Status Management

6.1 OverviewService has requested to support the following:l Status of the nodes

This displays OSV Cluster name, OSV Configuration, Node name, Node Hardware, Level of operation, Operation Mode, Database Role, X-Channel status, Connectivity with OSV.

l Change the level OperationThis will allow the change of the Node operation level to 2, 3 or 4.

l Restart the NodeThis will allow the Node to reboot and attain a level 2, or 3, 4.

l Graceful Shut DownThis will allow to control the shut down of the Node gracefully with an online command in-stead of power down.

l Operational Mode changesThis will allow to change of the operation mode of the Node to Normal, Stand Alone Sec-ondary and Stand Alone Primary.

Until V6 none of the above is possible from the CMP and only some of the above functions were available via CLI.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



42


6.2 UsageNavigate toMaintenance Invetory Nodesand click on the OSV name which should be controlled:


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


43


Here you can open the window to show the current status of both nodes as well change their functional state or even power off one node.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



44


6.2.1 Change Functional LevelThe following node status change will be allowed only when the connectivity is UP, if not the request must be rejected by the CMP with a reason cannot communicate with OpenScape Voice.

Level 2 - OS Implies that only Operating System will be running after the execution.3 - DB Implies that only OS and Solid DB will be running after the execution.4 - OSV Implies that OS, Solid DB and Applications such as SIPSM, SOAPServer etc are

running afterthe execution.Hazard warning of total outage (Confirmatory note) shall be provided if the Nodes current level is 4-OSV and the partner node is not in level 4-OSV.Request will be executed only when the Hazard warning is accepted.

ma

x. 1

min

ute


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


45


6.2.2 Restart NodeThis function allows the user to reboot the Node to a desired level OpenScape Voice Operation. Following are the desired levels and this function can be invokedindependent of the current le-vel of the Node:2 - OS Implies that the operating system will be restarted on theNode and the resulting node

state is the OS level.3 - DB Implies that the Operating system and DB will be restarted on the Node and the re-

sulting node state is the DB level.4 - OSV Implies that the Operating system, DB and RTP will be restarted on the Node and

the resulting node state is the 4-OSV level.For all levels above there will be a pop-up dialog warning of total outage (Confirmation Dialog) shall be provided if the Nodes current state is 4-OSV and the partner node is not in state 4-OSV. Request shall be executed only when the Hazard warning is accepted.

ma

x. 1

min

ute


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



46


6.2.3 Power DownThis function will allow the user to power off the Node.Hazard warning of total outage (Confirmatory note) shall be provided if the Nodes current state is 4-OSV and the partner node is not in state 4-OSV. Request shall be executed only when the Hazard warning is accepted.An additional note must be provided to power back up the node remotely use the Maintenance Controller of the Node from CMP available under Operations & Maintenance ->Overview ->3rd party nodes.

ma

x. 1

min

ute


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


47


6.2.4 Change Operational ModeThis function allows changing the operational mode of a Node. CMP will check the compatibi-lity with the status of the other node as stated below before allowing changing the operational mode to avoid data loss.

Any of the status change must be initiated within 1 minute of the status being displayed. This is needed to ensure that user would not change the status of a node assuming the other node is in proper state but in reality the status could change in time.

New Operation ModeNormal StandAlone-secondary StandAlone-primaryPartner Node

Operation ModeNormal StandAloneStandAlone-secondary StandAlone-primary StandAlone-synchSutting downNode Out of Service

ma

x. 1

min

ute


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



48


Example Scenario:l Retrieve the status of the Nodes.l After half hour the user decides to change the level of a Node to 3.l Assistant checks against the status it retrieved half hour back and let the user execute with-

out any warning.l Before the command is executed assume the level of partner node has changed to state

that do not handle any calls for various reasons.l This condition will cause a total outage i.e. loss of call processing. To avoid this CMP must grey out the four operations on the screen after 1 minute if no action is taken forcing the user to refresh the screen with the current status before an action is taken.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


49


6.2.5 SRXCTRLAdditional the srxctrl command has been enhanced and provides now the additional opti-ons:

Restart srxctrl -r Power Down srxctrl -p

Change Operational Mode srxctrl -o All the operations that are performed via srxctrl will be applied only to the local node. Prior to V6 srxctrl could only be executed from a Root login. Since this command has to be executed by the CMP in V6, srxctrl can now be executed from srx login as well.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



50



EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


51


7 Activate and Synchronize OSV partitions via CMP

7.1 OverviewThe application scenarios introduced with this feature:l Manage the OSV active / fallback versions via CMP

the versions that are installed in the system which is the active and which is the backup version

l Quick and Easy Repair of the OSV System after an RU failureIf the downtime is allowed, the administrator can use the easy and quick way by activating the backup version. The backup version is becoming active now and the call processing is available again in a few minutes. If the administrator wants to completely repair the system he can synchronize the two versions after the activation.

7.2 Functional DescriptionThe Multi Partition Capability introduced together with the image based installation in V3.1 SMR2 provides the capability to hold two different SW versions on the same system / harddisc. This allows an easier way of upgrading the system by keeping the previous version on the same harddisc.

Primary Partition

Secondary Partition

(e.g. V4R1)

(e.g. V5)


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



52


The sync8k command provides the capability to copy / mirror the content of the active partition to the fallback partition. For e.g., this can be used to make a copy of the current software load before installing a patchset or MOP

But the sync8k command had to invoked via the CLI. This feature allows now easely to syn-chronize the partitions via the CMP.

Primary

Secondary

sync8k

(Active)

(Fallback)

Primary

Secondarysy

nc8

k (Fallback)

(Active)

Primary is active partition Secondary is active partition


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


53


7.3 Usage

7.3.1 Activate Backup version and Synchronize Active version to Backup

The administrator navigates to OpenScape Voice dashboard.Maintenance Inventory ModesClick on your node.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



54


The Active and the Backup version are displayed. Additionally, two new functionalities are offe-red so the administrator is able to Activate the Backup version or Synchronize the Active versi-on to Backup.

Dashboard Synchronize Option:The option to synchronize the Active version to Backup version, has been added to the CMP. This is using the CLI command sync8k, in prior versions this was only a CLI option.The administrator selects to synchronize the two versions. Since the existing data in the backup version will be overwritten by the data of the active version the administrator has to verify this selection.

Content of Active / Backup partition Synchronize partitionsor

switch to backup version (requires reboot)


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


55


Synchronize Example:

>This procedure cannot be canceled via CMP.

1.

2. 3.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



56


7.3.2 Activate backup versionThe has been enhanced in order to provide the information about the active and the backup version of the OSV system. Once the administrator selects to activate the backup version of the OSV system, CMP willlogin to the OSV system as srx user and trigger the activate8k to switch from the active to the fallback and reboot the OSV. In case of a problem, CMP gets the error message from OSV and informs the user. The activation of the backup version is followed by a system reboot. Once the system reboot is initiated the communication between CMP and OSV is lost, so CMP cannot monitor this job anymore.

State description of the procedure Activate Backup VersionState 1: Initial State

a) Event: ActivateAction(s): A warning pop-up is createdNext State: Wait for user's verification

State 2: Wait for user's verificationa) Event: OK

Action(s): Call MMGR to start a backup version Activation JobNext State: Start Activation

b) Event: CancelAction(s): The warning pop-up closesNext State: Initial State

State 3: Start Activationa) Event: MMGR response: OK

Action(s): Get the Job Id and inform userNext State: Reboot System

b) Event: MMGR response: FailureAction(s): Inform UserNext State: Wait for user's input: [Close](close the window and return to the initial state)

State 4: Reboot System End of the procedure


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


57


Dialog box display from the Activate button

7This will cause a full system outage !


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



58


7.3.3 Software Activation enhancementsThis feature introduces changes in CMP at the start and at the end of software activation pro-cedure.Initially the user has the option to perform versions synchronization or not.If the user selects not to perform versions synchronization, CMP initiates the software activation as in previous versions.If the user selects to perform versions synchronization (default value), CMP shall initiate versi-ons synchronization on both nodes. Once this job is completed successfully, CMP continues with the software activation as it has in previous releases.If the Rolling Upgrade is completed with no error, CMP handles the Software Activation as it currently does. Currently if an error occurs the user is prompted to contact next level of techni-cal support. This feature introduces an additional option in case of a failure.The user has the capability to repair the system quickly by activating the backup software ver-sion. Once the user verifies his selection, MCP initiates backup version activation (aka activate8k ).Additionally, CMP shall offer the option to download log files. When this option is selected, CMP shall login to the system as srx user and trigger the script spt_log_collector.sh. Then CMP transfers via FTP the log files and the user can save the log files locally to his laptop.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


59



EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



60


If there is any problems during patching, it is recommended to download the log files so devel-opment can locate the source of the problem.The administrator selects the option Download Logs and the pop-up to save the log files locally in his laptop is presented. The administrator saves the log files and is ready to proceed with the fix of the Rolling Upgrade Failure.

He has two options:l the existing one is to escalate the problem directly to next level of technical support. This

option is applicable if no downtime is allowed and the administrator has enough time to de-bug the issue.

l the new one is the Quick Repair. This option will activate the Backup version of the Open-Scape Voice system and the system will be rebooted. This option is applicable if the down-time is possible, the administrator has no time to debug the issue and it is very important to have the system back to level 4 as soon as possible.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


61


OSV Assistants additional checksWhen one of the Jobs, version synchronization, backup version activation, software activation, is in progress OSV Assistant will not allow the initiation of another job.E.g. When a Software Activation is in progress, OSV Assistant shall prevent the user to start a Version Synchronization or a Backup Version Activation.The following table summarizes the additional checks that will be done from OSV Assistant:

User wantsto start

JobIn progress

SoftwareActivation

VersionSynchronization

Activate BackupVersion

Software Activation Get SW activationstatus

Not allowed Not allowed

Version Synchronization Not allowed Not allowed(covered by mmgr)

Not allowed

Activate Backup Version Not allowed Not allowed Not allowed(covered by mmgr)


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



62



EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


63


8 Split Audit Functionality fromRegistration Renewal

8.1 OverviewThis Feature intends to split the audit functionality off from the Registration Renewal feature and make it an automatic feature of OpenScape Voice.Registration Renewal is a system-wide feature that when turned on, triggers OpenScape Voice to extend a SIP subscriber's registration when OSV determines that it cannot communi-cate to a branch office (identified by the subscriber and its dynamically associated endpoint). This feature will now be turned on always. It was introduced in V2.2 and requires that the dy-namically associated endpoint does not have the Do Not Audit endpoint attribute set (i.e. can be audited).While OSV cannot communicate with the branch office the SIP subscriber moves into theSuspended state when its registration expires or when OSV tries to reach the subscriber. The advantage of the Suspended state is that OSV will not attempt to contact the phone via the WAN until the audit to the dynamically associated endpoint succeeds. If the SubscriberRerouting feature is enabled, Subscriber Rerouting will be attempted immediately - improving the user friendliness of OSV. Up to OSV V5 auditing of gateways is only done when the Registration Renewal feature isturned on this was fine up to now, however by extending the audit mechanism to all SIPendpoints and having this audit mechanism controlled by the Registration Renewal feature does not make sense anymore.At the same time the Audit mechanism is decoupled from the Alarming.

8.2 Functional DescriptionThe current behavior of SIP endpoints alarming, the auditing mechanism and registrationrenewal has been decoupled from each other.OpenScape Voice will always alarm when it detects that it cannot communicate with a SIPendpoint. The alarm will be cleared as soon as communication is reestablished.The Reestablished State is now Depending on the state of the Do Not Audit endpoint attri-bute.Communication is considered reestablished:l When Do Not Audit is disabled (i.e. auditing is enabled), after a successful audit to the SIP

endpoint.l When Do Not Audit is enabled (i.e. auditing is disabled), as soon as a SIP request is re-

ceived from the SIP endpoint.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



64


The following operational states are defined for a SIP endpoint:l Normal State:

The Normal operational state of a SIP endpoint indicates that communication with the end-point is possible. In this state the SIP endpoint must have the Inaccessible endpoint at-tribute disabled.

l Inaccessible state:The Inaccessible state of a SIP endpoint indicates that a scheduled audit is running against the SIP endpoint. In this state the SIP endpoint must have the Inaccessible endpoint at-tribute enabled and the Do Not Audit attribute must be disabled. In this state only OP-TIONS requests are sent to the endpoint.

l Communication Lost state:The Communication Lost state indicates that OSV could not communicate with the SIP endpoint. In this state no audit is scheduled or running against the endpoint. In this state the SIP endpoint must have the Do Not Audit and Inaccessible endpoint attributes enabled. In this state, no restrictions are imposed on sending messages to the endpoint, even though they are expected to time out.

Normal

Inaccessible Communication Lost

Endpoint Operational States

-Inaccessible: false-Do Not Audit: false

Normal-Inaccessible: false-Do Not Audit: true

Set Do Not Audit to true

Set Do Not Audit to false

-Inaccessible: true-Do Not Audit: false

-Inaccessible: true-Do Not Audit: true

Set Do Not Audit to true(cancel scheduled audit +all Suspended to Registered)Set Do Not Audit to false(+ on-demand + scheduledaudit)

Call/R

egis

tratio

n Ti

meo

ut

(+ Ra

ise

Com

mAl

arm

)

Cal

l/Reg

istra

tion Ti

meo

ut

(+ Ra

ise

Com

mAl

arm

)

Audi

t Res

ult

OK(+

all S

usp

ende

dTo

Re

new

ed+

Cl

ear

Com

mAl

arm

)

Inco

min

g R

eques

t(+

Cle

ar Co

mm

Alar

m)


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


65


8.3 ProvisioningPre V6 Registration Renewal feature setting was optional to be set by the administrator under:OpenScape Voice Administration Signalling Managament SIP

The capability of disabling the Registration Renewal feature is removed from the SIP Signaling Manager Administration in V6 and set now automatic by the OSV.

V5


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



66


Application ScenarioThe Registration Renewal feature has become an automatic feature of OpenScape Voice in V6 and the responsible attribute has been removed from the SIP Settings screen.The audit parameters (quantity, interval and supervision time) can still be configured under:OpenScape Voice Administration Signalling Managament SIP


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


67


Per default the audit of a SIP Endpoint is enabled. By setting the Do Not Audit endpoint at-tribute on a specific SIP Endpoint, the audit of that specific SIP Endpoint can be turned off.

>Note that the Do Not Audit endpoint attribute should only be used for dummyendpoints.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



68


The current behavior of SIP endpoints alarming, the auditing mechanism and registration re-newal has been decoupled from each other.OpenScape Voice will always alarm when it detects that it cannot communicate with a SIP end-point. The alarm will be cleared as soon as communication is reestablished.

The Reestablished State is now Depending on the state of the Do Not Audit endpointattribute.

Communication is considered reestablished:l When Do Not Audit is disabled (i.e. auditing is enabled), after a successful audit to the

SIP endpoint.l When Do Not Audit is enabled (i.e. auditing is disabled), as soon as a SIP request is re-

ceived from the SIP endpoint.The CMP is showing the Inaccessible endpoint attribute and shows the operational states Nor-mal, Communication Lost and Inaccessible in the endpoint overview:


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


69


9 Emergency Call SNMP Trap

9.1 OverviewThis feature generates an SNMP trap on an emergency call and sends all the pertinent data to the NOC in real-time for event notification.The SNMP Trap contains:

Dialed Digits Calling Party Number Calling Party IP Address LIN

LIN Description Route Number (postfix digits)

9.2 Functional DescriptionSome customers asked to be notified in case an emergency call will be executed so that they are able to send their own security personal to the emergency location. This feature extends the existing Emergency Feature by sending an optional a SNMP trap to the configured recei-vers when an emergency call will be placed.In same cases, only one gateway is used but the destination number must be modified. In this case, all destinations points to the same GW.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



70


9.3 Emergency Call RoutingThe emergency call will be executed in two steps. In the 1st step, the call will be sent via the PAC to a destination code which points to the emergency call service. This service adds spec-ified information, e.g. LIN, based on the subscribers IP address to the call. The call goes now again to the subscribers PNP PAC and can use a special routing entry.

In same cases, only one gateway is used but the destination number must be modified. In this case, all destinations points to the same GW.

PAC

PNPDest Code DESTINATION A

ROUTE

Dest Code

E911 Definition

x.x.x.xx.x.x.x 999

999IP / Net. Route

DESTINATION BROUTE

GW_B GW_A

Dest Code

PAC

PNPDest Code DESTINATION A

ROUTE

Dest Code

E911 Definition

x.x.x.xx.x.x.x 999

999IP / Net. Route

DESTINATION BROUTE

GW

Dest Code


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


71


9.4 Provisioning

9.4.1 Configure Emergency CallingThe already a few version ago implemented emergency calling feature is able to identify the subscriber location based on his current IP address. This definition must be done underConfiguration OpenScape Voice Business Group General Emergency Calling SubnetThe Emergency Calling Subnets definition assigns a route ID and a Location Identifier Number (LIN) to the subscriber based on a single IP address or a entire IP subnet.

Subnet or Single IPNetmask

1.21.11.0 / 255.255.255.0 defines a class C networkor

1.21.11.200 / 255.255.255.255defines a single IP

Use LIN as Calling Party Number(must be defined on LIN tab)Route Number max 4 digits (will be added to original dialed number)Passcode and ALI DB ID is current-ly not used but mandatory parame-ter (6 digits)

Description (Optional)


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



72


For our Labs we replaced the dialed EmergencyNumber + RouteID with a routable E164 num-ber in order to receive the subscriber in the PSAP Center.1st, create a destination for emergency calls:

And save it.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


73


Open the previosly created destination again. On the Routes tab, add the gateway which should be used.

Replace dialed Emer-gency Number (1121) with our Test Subscriber and set correct NOA(International).

Enter priority for this route between 1 (high-est) and 255 (lowest)

Enter / choose endpoint (gateway)


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



74


Add a prefix access code which forwards the emergency call to the Destination Code. e.g. the emergency calling number, which is dialed from is subscriber is 112. In the 2nd step, the same number extended with the route ID goes again into this PAC.

Emergency Number

Allows to dial plain Emergen-cy Number as well with Route ID with the same PACForward number unmodified to next level

Call Type is Off-net Access and will be forwarded to the Destination Code


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


75


We need two different Destination Codes. The first code points to the service destination, which is used to lookup the emergency calling information.

PAC (enter manually or press to select) and Nature of Ad-dress from previous step

Traffic Type Emergencyignores call restrictions

Service Emergency looks up Emergency Calling Subnet Definitions


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



76


For every Routing ID, which is defined in the emergency calling subnets, a destination code is required to send the call to a gateway.

PAC followed by the definied route ID(must be entered man-ually) and Nature of Address from previous step

Traffic Type Emergencyignores call restrictions

Destination EmergencyMUC will be used to send the call to the PSAP


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


77


9.4.2 Enabling E911 SNMP TrapsThe feature will be enabled by changing the SRX ParameterSrx/Service/E911/EmergencySNMPEvent

to RtpTrue. This can be done in the CMP under:Configuration OpenScape Voice Administration General Settings RTP

Locate the System Parameter manual or via the Search for field and change the parameter to True. The feature becomes be immediately active.


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



78


If an emergency call will be initated, an SNMP trap will be sent to all configured SNMP receiv-ers. This alarm will be shown in the CMP underMaintenance Monitoring Alarms Active Alarmswith the Alarm ID 948:

By clicking on the Alarm ID, the alarm details will be shown on the Description tab:


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


79


Here is an example of a sucessfull and a unsucessfull alarm:Sucessfull emergency callsysUpTime: 7 days, 18:17:43.26 rtpEvtCurrId: 30198 rtpEvtSet: 250 rtpEvtNum: 1 rtpEvtReportingObject: APPL:v6sys1n1.uce2 rtpEvtFaultyObject: APPL:v6sys1n1.Endpoint 498970071002 192.168.50.60 rtpEvtEndkey: noRecoveryDefined rtpEvtAlarmType: service rtpEvtShortText: FaultyObject = Endpoint 498970071002 192.168.50.60: Emergency Call from endpoint DN 498970071002 to Emergency Number = 112.CPN=498970071002, BG=SEN, IP=192.168.50.60, RT=89, AoR=498970071002, SubIP=192.168.50.60, SubPort=10001. rtpClusterName: vmv6cluster rtpEvtFilterLastTransId: 5450 hiQEmergencyCallIdTrap: The OSV server is processing an Emergency Call .

Unsucessfull emergency calllsysUpTime: 7 days, 17:55:50.77 rtpEvtCurrId: 30124 rtpEvtSet: 250 rtpEvtNum: 1 rtpEvtReportingObject: APPL:v6sys1n1.uce1 rtpEvtFaultyObject: APPL:v6sys1n1.Endpoint 498970071002 192.168.50.60 rtpEvtEndkey: noRecoveryDefined rtpEvtAlarmType: service rtpEvtShortText: FaultyObject = Endpoint 498970071002 192.168.50.60: Emergency Call from endpoint DN 498970071002 to Emergency Number = 112.CPN=498970071002, BG=SEN, IP=192.168.50.60, RT=89, AoR=498970071002, SubIP=192.168.50.60, SubPort=10001, Unsuccessful. rtpClusterName: vmv6cluster rtpEvtFilterLastTransId: 5429 hiQEmergencyCallIdTrap: The OSV server is processing an Emergency Call .

LegendCPN = Calling Party NumberBG = Business GroupRT = Route Number (E911 definition)AoR = Address of RecordSubIP = Subscriber IP addressSubPort = Subscriber Port Number (default 5060)


EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11



80



EN88

11EN

TTEN

_L._M

aldon

ado_

Pasto

r_17-1

0-11


81


10 SIPQ CodSet4 Transit Counter IE

10.1 OverviewThe codeset 4 Transit Counter IE is an optional QSIG supported IE sent / received in a Q.931 SETUP message. It applies to both call-related and non-call related (i.e., CISC) connections. Its purpose is to limit the number of transit nodes that a call setup request may be routed th-rough. If the limit is exceeded, call clearing will occur. The IE provides a provisional level of con-trol for loop prevention within the private network.OSV already supports in previous versions incrementing this IE when received, but, not gene-rating it or checking against a max. threshold value.Typically, the maximum number of transit nodes allowed for a call is provisioned consistently at each node in the network.

10.2 Functional DescriptionThe codeset 4 Transit counter IE will be supported over SIPQ for call-related / non-call related SETUP messages as follows:OriginationSend a locking shift to codeset 4 and Transit counter IE with the cou

mod03 gl features training

Documents

functional description

change functional level

provisioning errors

unified communications

cmp overview51

backup version

osv node status management

configuration tab71