100% found this document useful (1 vote)
194 views61 pages

Sharing Session SBC For NOC

This document provides an overview of SIP signalling and services, and the implementation of SIP in Telkomsel's network. It discusses how SIP is used for voice over IP services, smart voice communication partners, and SIP trunking. It introduces session border controllers (SBCs), their functions, and how they are used to link different SIP domains and provide security. Monitoring tools for SBCs are also presented, including Wireshark, Cacti, SDreporter, and the NNC management system. Health scores, alarms, CPU usage, SIP logs, and the fault management GUI can all be used to monitor SBC performance and troubleshoot issues.

Uploaded by

andrea
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
194 views61 pages

Sharing Session SBC For NOC

This document provides an overview of SIP signalling and services, and the implementation of SIP in Telkomsel's network. It discusses how SIP is used for voice over IP services, smart voice communication partners, and SIP trunking. It introduces session border controllers (SBCs), their functions, and how they are used to link different SIP domains and provide security. Monitoring tools for SBCs are also presented, including Wireshark, Cacti, SDreporter, and the NNC management system. Health scores, alarms, CPU usage, SIP logs, and the fault management GUI can all be used to monitor SBC performance and troubleshoot issues.

Uploaded by

andrea
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 61

Sharing Session

SBC for NOC


CSO DEPARTMENT
4TH MARCH 2016

Outline

Introduction SIP Signalling and service

Implementation SIP in Telkomsel

Introduction to SBC

Monitoring SBC

I. SIP Service and


Signalling

SIP Definition

SIP is one of the protocol that commonly used in VOIP


Technology

Based of RFC 3261 :


SIP is an application-layer control protocol
that can establish, modify, and terminate
multimedia sessions (conferences) such as
Internet telephony calls

Other Options

Protocol-protocol used in VOIP :

H.323

Media Gateway Control Protocol (MGCP)

Session Initiation Protocol (SIP)

H.248 (Megaco)

Real-time Transport Protocol (RTP)

Real-time Transport Control Protocol (RTCP)

Secure Real-time Transport Protocol (SRTP)

Session Description Protocol (SDP)

Inter-Asterisk eXchange (IAX)

Jingle XMPP VoIP extensions

Skype protocol

Call Flow H323 and SIP

Example Topology

SIP and VOIP

Voice over IP (VoIP) is


a methodology and
group of technologies
for the delivery of
voice
communications and
multimedia sessions
over Internet Protocol
(IP) networks

OTT Communications is gaining Momentum


Communication wants to be free
1990s free from places
w Mobile

2000s free from


devices w Smartphone

2010s free from


price OTT

?? From free operators


w Virtual SIM

Skype
Facebook
BlackBerry
KakaoTalk
Viber Media
Nimbuzz
Fring
Tango
Rebtel
Truephone
Vopium

OTTmessagingproviders

WhatsApp
Skype
Facebook
BlackBerry
KakaoTalk
Nimbuzz
Tango
Apple
Kik
Line
Tencent

OTTvideochatproviders

Fring
OoVoo
Tango
Apple
Line

ViberMedia, messagingtraffic,
4Q11-1Q13
15
10
5
0

4Q11

1Q12

3Q12

1Q13

WhatsApp, messagespermonth,
4Q11-2Q13
800
Messages(bil.)

OTTVoIPproviders

Messagespermonth(bil.)

Telkomsel SMS: 7 Bil/Month (June 14)

600
400
200
0
4Q11

1Q12

3Q12

1Q13

2Q13

SIP Call Flow

1. Registration

2. Simple Session Establishment

3. Detail SIP Message

Call Flow
LDAP

Voice call

GMSC
NVS/MSS

Call from NCS client to PSTN


1.
2.
3.

4.

3
.

NCS client registers to NVS


NCS client makes a phone call to PSTN
number [email protected]
NVS routes the call to GMSC server which
NVS strips off the domain part. GMSC
routes the call to the the PSTN
the call is completed to fixed phone

+6221350xxxx

SBC

Signaling traffic (eg. call setup)


Media traffic (voice and data)

2
.

WLAN
network
1
[email protected]
.

MGW

4
.

+6221350xxxx
+628128888xxxx@telkomsel.
co.id

Voice call

LDAP

Call from 2G/3G to NCS Client


1
1.
.
2.
2
.
3
3.
.

4
4.
.
5.
5.

NCS client registers to the


NVS from WLAN coverage.
3G makes a call to NCSclient where uses NCSclients Tel URI
+628128888xxxx.
2
The call signaling is routed
.
+628128888xxxx
to NVS which makes ENUM
query and finds NCS uses
SIP URI
The call signaling is routed Phone
MGW
UTRAN
+628121232xxxx
GERAN
to NCS client through the IP
4
network using the SIP URI
.
Media (voice) flow

NVS/MSS

3
.

[email protected]

5
.
SBC

Internet
Access

Signaling traffic (eg. call setup)


Media traffic (voice and data)
SIP client

1
.
S

SIP-Client
+628128888xxxx@telkomsel.
co.id

Applicable also
Applicable also
for SIP-Phone and
for SIP-Phone and
Web2Call in WiFi
Web2Call in WiFi

Voice call

LDAP

VoIP call from NCS Client to NCS Client


1.
1
.
2
2.
.
3
3.
.

4.
4.

NVS/MSS

A-number enters WLAN


coverage area. SIP-client
registers to NVS.
B-number enters to other WLAN
hot spot and also registers to
the same NVS.
A-number makes a VoIP call to
B-number. A-number uses Bnumber MSISDN number or
alternative his SIP URI. The call
is routed to NVS which finds Bnumber uses SIP address and
routes it to B-number.
Media (voice) flow

3
.
MGW

SBC

Internet
Access

A-Number
Signaling traffic (eg. call setup)
Media traffic (voice and data)

Internet
Access

1
.

Applicable also
Applicable also
for SIP-Phone and
for SIP-Phone and
Web2Call in WiFi
Web2Call in WiFi

B-Number

4.
4.

2
.

Voice call

LDAP

Call from NCS client to PSTN

GMSC
NVS/MSS

11.
.
2.
2
.
33.
.
44.
.

NCS client registers to NVS


NCS client makes a phone call to PSTN
number
[email protected]
NVS routes the call to GMSC server
which NVS strips off the domain part.
GMSC routes the call to the the PSTN
... the call is completed to fixed phone

3
.

+6221350xxxx

SBC

Signaling traffic (eg. call setup)


Media traffic (voice and data)

2
.

WLAN
network
1
[email protected]
.

MGW

4
.

+6221350xxxx
+628128888xxxx@telkomsel.
co.id

Registration flow
REGISTER
F1 REGISTER Bob -> SIP Server
REGISTER sips:ss2.biloxi.example.com SIP/2.0
Via: SIP/2.0/TLS
client.biloxi.example.com:5061;branch=z9hG4bKnashds7
Max-Forwards: 70
From: Bob <sips:[email protected]>;tag=a73kszlfl
To: Bob <sips:[email protected]>
Call-ID: [email protected]
CSeq: 1 REGISTER
Contact: <sips:[email protected]>
Content-Length: 0

Simple Session Establishment


INVITE
F1 INVITE Alice -> Bob
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/TCP client.atlanta.example.com:5060;branch=z9hG4bK74bf9
Max-Forwards: 70
From: Alice <sip:[email protected]>;tag=9fxced76sl
To: Bob <sip:[email protected]>
Call-ID: [email protected]
CSeq: 1 INVITE
Contact: <sip:[email protected];transport=tcp>
Content-Type: application/sdp
Content-Length: 151
v=0
o=alice 2890844526 2890844526 IN IP4 client.atlanta.example.com
s=c=IN IP4 192.0.2.101
t=0 0
m=audio 49172 RTP/AVP 0
a=rtpmap:0 PCMU/8000

Simple Session Establishment


200 OK
F3 200 OK Bob -> Alice
SIP/2.0 200 OK
Via: SIP/2.0/TCP client.atlanta.example.com:5060;branch=z9hG4bK74bf9
;received=192.0.2.101
From: Alice <sip:[email protected]>;tag=9fxced76sl
To: Bob <sip:[email protected]>;tag=8321234356
Call-ID: [email protected]
CSeq: 1 INVITE
Contact: <sip:[email protected];transport=tcp>
Content-Type: application/sdp
Content-Length: 147
v=0
o=bob 2890844527 2890844527 IN IP4 client.biloxi.example.com
s=c=IN IP4 192.0.2.201
t=0 0
m=audio 3456 RTP/AVP 0
a=rtpmap:0 PCMU/8000

II. Implementation
SIP in Telkomsel

SIP Service in Telkomsel


Smart

Voice Communication
SIP Trunking

Smart Voice Communication

Currently there are 8 Smart Voice Communication partner use SIP service
Telkomsel

This service uses :

NVS for registration, call establishment

LDAP for storing customer profile

SBC for registration triggering, back to back user agent to customer,


manipulation SIP message

Smart Voice Communication Work Flow

SIP Trunking
RBT

RBT played by CRP server

CRP Server owned by Digital Service Telkomsel

Currently there are two types of CRP server :

CRP TDM

CRP IP

CRP TDM work using SS7 technology, connected to TMGW


Telkomsel using E1 connection

CRP IP work using SIP technology, connected to GCS Telkomsel


using SIP connection

Ideally there is SBC between GCS and CRP server

SIP Trunking
RBT

SIP Trunking
Call Center Telkomsel

Call Center Telkomsel has migrated from TDM based to IP Based

IP Based Call Center uses SIP Technology

Call Center Telkomnsel located in 4 location :

Medan For Sumatra area, connect to YMDN1 via SBC Medan

Bandung For Jabodetabek and West Java area, Connect to YBRN1 via SBC Buaran

Surabaya For East Java and Balinusra area, connect to YSBY1 and YSBY2 via SBC
Surabaya

Makassar For Kalimantan, Sulawesi and Puma area, connect to YUPD2 via SBC
Makassar

SIP Trunking
Call Center Telkomsel

SIP Trunking
POI SIP Trunking

POI SIP trunking is connection to OLO network using SIP between


Telkomsel gateway and OLO gateway

Currently POI SIP trunkingn is in trial

SIP Trunking
POI SIP Trunking

Other SIP Telkomsel service


VAS Telkomsel service

Other SIP Telkomsel service


Tecarla

III. SBC
Introduction

Introduction SBC

SBC uses as sessions control at border

SBC link connection between mobile core network and other SIP domain

SBC perform SIP manipulation to match interoperability between SIP


connections

SBC uses as security gateway

SBC block unwanted packets or message before its reach gateway of core
network

SBC only open specific port requested on the signaling

SBC perform topology hiding to prevent network discovered by peer

Perform registration from SBC using surrogate agent mechanism

Service Using SBC

all Centre enterprise

VAS SIP service

POI SIP trunking

Tecarla

SBC OAM Connection

Login to CLI
From NNC1
telnet <SBC name>
SBC
SBC
SBC
SBC
SBC
SBC
SBC
SBC
SBC
SBC
SBC
SBC
SBC

1
SBC 2
Balilkpapan-1 SBC Balikpapan-2
Bandung-1
SBC Bandung-2
Banjarmasin-1 SBC Banjarmasin-2
Batam-1
SBC Batam-2
Buaran-2
SBC Buaran-3
Buaran-4
SBC Buaran-5
Denpasar-1
SBC Denpasar-2
Makassar-2
SBC Makassar-3
Medan-2
SBC Medan-3
Pekanbaru-1 SBC Pekanbaru-2
Semarang-1 SBC Semarang-2
Surabaya-2
SBC Surabaya-3

SBC tbs-1
SBC Timika-1

SBC tbs-2
SBC Timika-2

Virtual

SBC Buaran-1

SBC Makassar-1
SBC Medan-1

SBC Surabaya-1

Version
SBC 4500
SBC 4500
SBC 4500
SBC 4500
SBC 9200
SBC 4500
SBC 4500
SBC 9200
SBC 9200
SBC 4500
SBC 4500
SBC 9200

SBC 14000
SBC 4500

Physical Connection SBC Buaran

Tools 1 : wireshark

Tools 2 : cacti
http://10.2.233.25/donita/graph_view.php?action=tree&tree_id=13&leaf_id=2868

Tools 3 : SDreporter
10.1.176.126:7080/analyzer/oss_ta_ccs_report_1.htm

Tools 4 : NNC
http://10.1.176.128:8080/

Monitoring SBC and Fault Management

Health Score

Show Health NN9200

Show Health NN4500 dan


NN14000

Display Alarm NN9200

Display Alarm NN4500 &


NN14000

Alarm Description example:

System Management

Uptime, Clock, Features, and


Session License

CPU Usage NN9200

CPU Usage NN4500 & NN14000

Application Performance

SIP Log Messages NN9200

SIP Log messages NN4500 &


NN14000

Check Agen SIP NN9200

Check SIP Agent NN4500 &


NN14000

Check Fault Management NNC GUI

Summary View NNC

Summary View NNC

Summary View NNC

Fault Manager Event NNC

Fault Manager Alarm SBC

You might also like