1

Proposed NGN based

Class 5 solution
- Veraz

Prepared & Presented By : Kishore Sachdev

Index
2

1. Network Element Details

2. Service & Feature Supported
3. Detailed Architecture Design
4. Redundancy
5. Capacity
6. Protocols Supported
7. Interoperability
8. Market Presence & Support
9. Call Flow
10. Solution Summary
11. Deviation from RFP
Network Element Details
3

Network Elements Model name Vendor Brief Functional Description Protocol

CCP- MGW ->MGCP

Call controller, controls MGW using MGCP
MGC CCP Veraz CCP- Broadsoft ->SIP
protocol
CCP- GK* -> H.323
Gatekeeper Not available
Signaling Gateway SGW Veraz Interfaces to PSTN Domain for SS7 SS7
Trunking Media I-Gate4000 MGW - CCP ->MGCP
Veraz For Terminating PSTN calls
Gateway Pro Access- ISDN PRI
Contains user defined Policy and Routing
PE Veraz
database
Routing &
translation support
NS
Broadsoft NS - Acts as Routing and SIP redirect Server

ICE - GK -> H.323

For Peering with 3rd party GK and Feature
IP Peering / ICE Veraz ICE - FS -> SIP
Server
Network Element
NS Broadsoft For Peering with 3rd party Softswitch SIP
 Network Element Details – Cont.
4

Network Elements Model name Vendor Brief Functional Description Protocol

Feature / Call controller, Acts as SIP proxy and MGC
AS Broadsoft SIP, MGCP
Application server for SIP and MGCP end-user respectively
SIP calls are Handled by Application Server,
SIP Proxy AS Broadsoft SIP
which acts as SIP proxy.
AS - Cotains subcriber database
Subscriber
AS and NS Broadsoft NS - Contains information on Polies, users
database
and Resource
Media / 1) Announcement recording and playback
Announcement MS Broadsoft 2) DTMF digit detection
Server 3) Conferencing
Access Media
- - - -
Gateway
 Network Element Details – Cont.
5

Network Elements Model name Vendor Brief Functional Description Protocol

Session Border
VoIP Seurity, NAT, QoS, Protocol Traslation,
Controller (SBC) / Voice Flow Kagoor SIP, H.323 and MGCP
Remote monitoring and management.
Security

1) EC is resposible for collection and storage

1) EC - Push
call-related events from various Elements
1) EC 1) Veraz 2) Mediation Device Pull
2) CDRM handles the billing data formatting
Billing Support 2) CDRM 2) Veraz from CDRM
and trasporting fuctions.
3) AS 3) Broadsoft 3) Broadsoft - Push & Pull
3) AS - further iputs awaited

1) xMS 1) xMS - MGW

Veraz
2) EMS 2) EMS - Core Call control Elements
EMS Broadsoft
3) EMS 3) EM - NS, AS, MS and CS
Kagoor
4) Netflow 4) Netflow - Voice Flow
 Service & Feature Supported
6

Broadsoft - 1) IP Centrex
2) Unified Messaging

Kagoor - 1) Supports NAT

2) Security
3) QoS
4) Protocol Interworking (SIP and H.323)
Detailed Architecture Design
7
Veraz Softswitch Domain
PE/SEE
CDRM
ICE

CS MS AS NS EC

CCE

SBC Managed IP Network

MGCP SIP MGCP

SIP
MGW PSTN
IAD IAD Router
E1/STM

Analog KTS
Phones PBX IP Phones
ISDN PRI
PC Clients
PBX

Customer Premises
 Redundancy
8

Network Elements :
1. CCE 1:1 (Geographical Redundancy)
2. SGW 1:1
3. I-Gate Pro 4000 Card level Redundancy
a. Control Set (TPSM, TPSI) – 1:1 Redundancy
b. Interface – STM – 1:1 Redundancy
c. All other interface and DSPK - N:1 Redundancy

4. Broadsoft AS - 1:1 (Geographical Redundancy)

NS - Clustering up to 7 servers (Geog. Redundancy)
MS – N:1 (Geographical Redundancy)
CS – N:1 (Geographical Redundancy)

5. Voice Flow 1:1 (Geographical Redundancy)

 Capacity
9

1. Max. Subscriber Supported / AS 250K

2. BHCA in Million/ AS 1000 K
3. Announcement storage capacity (inputs awaited)
4. BHCA in Million/ CCP 0.6 Million
5. No. of MGW supported / CCE (inputs awaited)
6. Max. DS0s. Supported / CCE (based on no. of MGW)
7. No. of Signaling links / SGW 48/ 96 (Single / Mated pair)
8. No. of Ports Per MGW 8K
9. SBC capacity – 100,000 Concurrent Session
750 CPS
10. Max. No. NE under single EMS control (inputs awaited)
 Protocols Supported
10

1. Feature Server – Subscribers SIP and MGCP

2. MGC - Feature Server SIP
3. MGC – TGW MGCP
4. MGC – SGW ISDN (IUA)
5. MGW to TDM (Signaling Protocol) ISDN PRI, ‘F’ Links
6. Peering Protocol supported H.323 and SIP
7. SBC protocols supported H.323, SIP and MGCP
8. SBC interworking Protocol H.323 and SIP
 Interoperability
11
Vendor & Model :
1. IADs Cisco 24xx, Polycom NetEngine 6x00 & 7x00,
Vpacket 6100 series, Carrier Access adit 600,
MCK SetConnex
2. IP Phones Cisco 7905-40-60, Pingtel - xpressa,BCM HP 400,
Polycom-Sunpoint IP, IPDial- SIPTone, Mitel 5055,
Siemens – optiPoint 400

3. Soft Phones (PC based) X-ten

4. Media Gateway Cisco MGX8260-8850, Telica Plelux 9000

5. Application server Telica Plelux 9000

6. LIM (Inputs awaited)

7. SBC Kagoor
 Market Presence & Support
12

Broadsoft – 1) Customer base is more than 90 network operators, including

BellSouth, MCI,Telstra, and XO Communications
2) More than 750,000 lines deployed
3) No TAC support in India

Veraz – 1) CallControl Switches and Media Gateway's are deployed

worldwide including US, Turkey, Russia, France and more
2) Has Global office in New Delhi- India
3) No TAC support in India

Kagoor – 1) Trials and initial deployments with most major dominant IP

Centrex players in the US and other worldwide carriers.
Call Flow
13

1) ON – Net
2) Off – Net
IP – Other operator using ‘F’ link
RIM – IP using ‘A’ link
IP to IP (IP peering through SBC)
Call Flow On Net
14
Veraz Softswitch Domain
PE/SEE
CDRM / EC
ICE

CS MS AS NS Signaling
SG

Bearer

CCE

SBC Managed IP Network

MGCP SIP MGCP

SIP

IAD IAD Router

Analog
PSTN
KTS
Phones PBX IP Phones

PC Clients
MGW

Customer Premises
Call Flow: SIP to SIP (On Net)
15

SIP-A AS
SIP-B

SIP: INVITE
SIP: INVITE
SIP: 100 Trying
SIP: 100 Trying
Phone rings

SIP: 180 Ringing

SIP: 180 Ringing
Ringback B Answers
SIP: 200 OK
tone to A
SIP: 200 OK
SIP: ACK
SIP: ACK

User A and B are in conversation)

A goes SIP: BYE
SIP: BYE
on-hook
SIP: 200 OK
SIP: 200 OK

User A and B are idle

Off – Net SIP – PSTN
16
Veraz Softswitch Domain
PE/SEE
CDRM / EC
ICE

CS MS AS NS Signaling
SG

Bearer
‘A’ link
CCE
MG for
Signaling

SBC
Managed IP Network

SIP
SIP IP
MGCP
Other
IAD Router Operator

KTS IP Phones
PBX
‘F’ link
PC Clients

MGW

Customer Premises
Call Flow: SIP to PSTN
17
AS / NS I-Gate 4000 Pro
SIP-A
SGW
CCE/ICE PSTN -B

SIP: INVITE
SIP: INVITE
Call request
SIP: 100 Trying
SIP: 100 Trying
SS7 IAM
SS7 ACM
MGCP CRCX

MGCP 200 OK

SIP: 180 Ringing Call response

SIP: 180 Ringing
Call Setup SS7 ANM
SIP: 200 OK
SIP: 200 OK
SIP: ACK
SIP: ACK

User A and B are in conversation)

SIP: BYE SIP: BYE

SIP: 200 OK Release
REL
SIP: 200 OK MGCP DLCX
MGCP 200 OK
RLC

User A and B are idle

Off – Net RIM – IP using ‘A’ link
18
Veraz Softswitch Domain
PE/SEE
CDRM / EC
ICE

CS MS AS NS Signaling
SG

Bearer
‘A’ link
STP N/w
CCE

SG

SBC
Managed IP Network

SIP
MGCP IP ‘A’ link

Router

IP Phones

PC Clients

MGW GMSC/ MSC

Customer Premises
Off – Net IP to IP (IP peering through SBC)
19
Veraz Softswitch Domain
PE/SEE
CDRM / EC
ICE

CS MS AS NS Signaling
SG

Bearer

CCE

SBC

SBC Managed IP Network IP Network Other Operator

SIP
IP Phones
Router

IP Phones

PC Clients

Customer Premises
Solution Summary
20

Pros
Entire Solution is based on open platform – Sun Netra
Peering Protocols are SIP and H.323
Interworking between SIP and H.323 is supported
Supports Geographical Redundancy

Cons
Multi Vendor Solution (Veraz, Broadsoft and Kagoor)
Multiple Element Management Systems (Veraz, Broadsoft and Kagoor)
Veraz-Broadsoft integrated solution not deployed anywhere so far
Does not support H.323 at the access side (support for Peering only)
E1R2, V5.2 not supported
 Deviation from RFP
21

SL No. Mandatory RFP Parameters Supported Roadmap

Deviation from
Protocols & Signaling
RFP is 31.81
1 IP Phones – SIP based Y
2 IADs – SIP Based Y
3 IP Phone – MGCP & H.323 based Y (N for H.323)
4 IADs – MGCP & H.323 based Y (N for H.323)
5 Soft Phones – PC based on H.323 / SIP Y (N for H.323) After
6 Application server - SIP protocol Y Considering
Roadmap
7 INAP triggers (CS-1) N
deviation
8 E1 – PRI Signaling Y
reduces to
9 E1 – R2 Signaling N Y 22.72
10 ETSI – ISUP SS7 - ‘F’ Link on MGW Y
11 ETSI – ISUP SS7 - ‘A’ Link on Signaling Gateway Y
Others
12 End to End QoS Monitoring & Tracing the calls Y
13 IP Interface FE & GE with Hot standby Redundancy Y
14 Lawful Intercept system Y
15 IPv6 supported N
16 Native Session Border Controller (SBC) supported N
17 Interface Type on MGW E1 & STM-1 Y
18 Hotstandby & Geographic redundancy Support Y
19 Centrex Y
20 Single Vendor Solution N Y
21 Less no. of Nes N
Total N
Overall in line with RFP out of 100 % 68.18% 9.09%
22