Netmon how to build call signature (isign) service

18
Call Signature (iSign) Technical proposal

description

The document gives you idea how to build Call Signature service, which launch in Viettel, Vietnam as brand iSign. It is usefull for System engineering or Solution architecture lead.

Transcript of Netmon how to build call signature (isign) service

Page 1: Netmon how to build call signature (isign) service

Call Signature (iSign)

Technical proposal

Page 2: Netmon how to build call signature (isign) service

Last update

• Sep 2013: Netmon upgraded to support IP wrapped in VLAN 802.1Q tunnel.

• Oct 2013: Netmon upgraded to support Sccp form and BSSAP messages.

Page 3: Netmon how to build call signature (isign) service

What is Call Signature ( Viettel iSign)

• Mobile user, specially business man will not answer a call if the calling number is unknown

• Call may be rejected cause it is not yet in contact list.

• If the call is reject, then it will not generate revenue.

Page 4: Netmon how to build call signature (isign) service

Call Signature (cont)• Call Signature provides

information to the called party about caller’s information, then it increases chance the called will answer the call.

• The Signature displayed while the phone is ringing.

• The caller need not to send SMS to explain who he is after the call was rejected.

Hello darling, this is Hung

and here is my new number

Dismiss

Page 5: Netmon how to build call signature (isign) service

It make a call more attractive

• For outbound roamer: Please call me back, I’m on travel and have low balance

• Or a predefine Signature for each called person.

Dismiss

Please call me back, I’m

on travel and having low

balance

Page 6: Netmon how to build call signature (isign) service

2 models to know calls

To know the call is in progress, monitoring call is executed based on using Netmonfunctionality.

Page 7: Netmon how to build call signature (isign) service

Monitor models

• All monitoring will be non-intrusive, the signaling traffic will not be affected.

• Connection between MSC and BSC may be monitored to provide service to all subscriber

• Monitoring connection between MSC and OCS may be applied if the service is only targeted to Prepaid subscriber.

Page 8: Netmon how to build call signature (isign) service

The call monitor workflows

Dismiss

Please call me back, I’m

on travel and having low

balance

Page 9: Netmon how to build call signature (isign) service

THIS PAGE IS INTENTIONALY LEFT BLANK

Page 10: Netmon how to build call signature (isign) service

Call Monitoring

• Can monitor both legacy SS7 and SS7 over IP (Sigtran)

• The SS7analyzer engine inside CallMonitor, we call it Netmon.

• You will need CallMonitor to develop Call Signature (or MCA, Welcome )

Page 11: Netmon how to build call signature (isign) service

Netmon

• The Network Monitor module, used to decode SS7 message collected from live tapping or SPAN port.

• It is very fast, since it was developed in C++ language, for Unix based system and almost activities are C pointer movement based. No copying philosophy is applied.

• It support traffic based on M2UA, M3UA.

• Supported Stack: sccp, tcap, gsmmap and Camel

Page 12: Netmon how to build call signature (isign) service

Netmon (cont)

• Only Data is filtered, other signaling message will be drop to increase performance. I.e on M3ua layer, only Data with SCCP payload is retrieved, in Sccp layer, only UDT (and xUDT) will be retrieved.

• Sccp Reassemble is supported

• Multiple Tcap Component portions is supported.

• Performance: about 8000 Ip frames/second on a MacbookPro 2.4Ghz Duo core, 4GbRam, Debianlinux 5.x

Page 13: Netmon how to build call signature (isign) service

Netmon Decoding status

Multiple chunks supported

IP over VLAN is also

supported

Ethernet frame

IP

SCTP

M2UA/M3UA

SCCP

TCAP

CAMELMAP

Reassembly supported,

Data Only

Multiple components

supported

Call related message

supported

Location update

messages will soon

supported

Data Only

Sigtran stack

VLAN 802.1Q (

IP

BSSAP

Page 14: Netmon how to build call signature (isign) service

Netmon (cont)

• Compliant with: itut-Sccp (Q773, Q775), Itut-Tcap (Q.713), GsmMap (gsm 09.02) and Camel (ts 29.078)

• At present, only Call related messages are supported, i.e: Initital DP, requestBCSMReport,

eventBCSMReport, ApplyCharging, applyChargingReport,

• GPRS related message will soon be supported in 2013

Page 15: Netmon how to build call signature (isign) service

To use Netmon

• Dedicate a file captured with Sigtran data in pcap format.

• We will check for compatibility, customize Netmon if necessary, the give you binary Netmon.

• Decoding result will be written to a text file in nice format. Your system can read the text file for further processing.

• Information include: Sccp, Tcap, Cap data

Page 16: Netmon how to build call signature (isign) service

Integration with Netmon

• NetMon send decode message to an Application Server.

• The AppServer will callback to user application for service processing.

Page 17: Netmon how to build call signature (isign) service

To own Netmon

• Get full source with cmake ready.

• Customize netmon to redirect decoding result to a core logic via networking for processing.

• Just email [email protected] to discuss.

(You can visit scansource to see Dialogic price for Sigtran Monitor, only support to sccp layer)

Page 18: Netmon how to build call signature (isign) service

Thank you