CDR stands for Call Detail Record. It is a metadata containing the detailed information about the call session produced by Edge. A CDR has various data of each leg of calls, and typically includes: When the call took place – How long the call lasted – Who called to whom – and many more. 

Edge CDR Metadata

Example:

1 {
2  "data" : {
3    "module" : "call",
4    "eventName" : "vendorCDRExtra",
5    "timestamp" : 1614575657225,
6    "txnUuid" : "fdd9be18-7dfa-49d0-8c47-33f3b4598917",
7    "legs" : {
8     "147d2eac-9ba8-450e-8513-65380b2866d6" : {
9       "edge-SGSBC" : {
10        "rtp_crypto" : "",
11        "correlation_id" : "147d2eac-9ba8-450e-8513-65380b2866d6",
12        "duration" : "6538",
13        "transport" : "udp",
14        "answer_time" : "2021-03-01 13:14:17",
15        "uuid" : "b9aac7ca-2d9f-4e0e-827d-2ffc3b51efee",
16       "codec" : "PCMA",
17        "sip_resp_code" : "sip:200",
18        "seshid" : "147d2eac-9ba8-450e-8513-65380b2866d6",
19        "hangup_cause" : "NORMAL_CLEARING",
20        "end_time" : "2021-03-01 13:14:17",
21        "status" : "ANSWERED",
22        "direction" : "outbound",
23        "iso_answer_time" : "2021-03-01T05:14:17.170092+00:00",
24        "nodename" : "awszntedge1",
25        "edge_network" : "172.31.12.2,18.140.31.74",
26        "callid" : "96db8896-f4e0-1239-fcb5-0677079ea32c",
27        "start_time" : "2021-03-01 13:14:17",
28        "disposition" : "EDGE_SEND_BYE",
29        "interface" : "voice2",
30        "iso_end_time" : "2021-03-01T05:14:17.170136+00:00",
31        "local_media_address" : "111.22.33.4:56789",
32        "caller" : "+6561111111",
33        "peername" : "SGSBC",
34        "iso_start_time" : "2021-03-01T05:14:17.169920+00:00",
35        "user_agent" : "B3Networks",
36        "context" : "inside",
37        "callee" : "+6562222222",
38        "remote_signalling_address" : "00.11.234.56:5060",
39        "remote_media_address" : "00.11.234.56:10648"
40      }
41       }
42     }
43 },
44 "gateKeeperSpec" : {
45   "domain" : "gelcccs.zonetel.com.sg",
46   "orgUuid" : "ea6f73ee-9960-40f9-91c3-8473ade58a8a"
47 },
48 "version" : "v1"
49 }

The post Call Detail Record (CDR) appeared first on Data Dynamics Pte Ltd.

The post Backup – Restore appeared first on Data Dynamics Pte Ltd.

The post Netcap appeared first on Data Dynamics Pte Ltd.

The post Routing appeared first on Data Dynamics Pte Ltd.

Introduction

Interconnection Trunk is the trunk group used to connect one or multiple carriers’ networks with B3networks’s network for the purposes of exchanging Telecommunications traffic.Edge Server is designed to be reliable and flexible. It allows the system admin to add/remove/update attributes of the interconnection on the fly, which means that the change will not impact service operation including call drop, audio. For example, you have calls that rely on the Interconnection Trunk named ANYNAME, and need to re-prioritize codec list or change signaling address, the change can be submitted immediately without worrying about affecting the currently active calls. 

Protocol

Edge Server represents a full user agent and controls the necessary signaling protocol and media streaming to process calls. 
Edge Server uses Session Initiation Protocol (SIP) for signaling and Real-Time Transport Protocol (RTP) for media streaming to other endpoints.
SIP is a text-based protocol, defining the specific format of messages exchanged and the sequence of communications for the cooperation of the participants. SIP carries SDP in payload to perform media negotiation and setup to employ RTP. SIP is independent with transport protocol, and can use UDP/TCP/TLS.

Functions

By using interconnection’s attributes, Edge Server is able to provide powerful functions with minimal and simple configuration:

• Health-check Voice Server by SIP OPTION with configurable ping interval
• Load balancing among interconnect signaling  
• Outbound digest authentication
• Secure communication with TLS/SRTP
• Flexible update setting of codec, number translation, rate limit, or SIP header manipulation for interoperability
• Easy to scaling edge cluster with distributed node members.
• Firewall management automatically
• Re-routing indirected call 
• Suspend interconnection trunk

Parameters

The below table shows parameters in a particular trunk:

How to create a new trunk

1. Go to Trunks > Create trunk

2. Give your trunk a name > Choose a preset Capacity and Codec > Choose Direction for your new trunk > Configure Username, Password and Ping if the direction is outbound (optional) > Fill in Signaling, Port, Protocol, Media based on your vendors' interconnection form

3. Drag the chosen Translation DNIS, CLID and Manipulation Profile to the right column (optional) > Create

4. Finish

The post Interconnection Trunk appeared first on Data Dynamics Pte Ltd.

Introduction

The variances among SIP networks, such as incompatible interconnection, can disrupt SIP operations. In order to resolve these problems, Edge Server provides SIP Header Manipulation, giving Edge operators the ability to control SIP traffic by manipulating SIP messages. Shortly, Manipulation is to modify SIP Header.

Functions

• Add custom SIP Header, Parameters
• Capture information from a message and insert it into another message
• Remove all custom SIP headers
• Execute the change if the condition is satisfied
• Drop call or Log message if the condition is not satisfied

Contract

• Manipulation rule is only applicable to Outbound Trunk.
• Manipulation rule has a restriction to protect Edge Function, which does not allow to modify native SIP Header or native Session Variable.
• X-EDGE  and V-EDGE are reserved for Edge and not available to modify.
• X- indicates custom SIP Header
• V- indicates custom Session Variable

Parameters

Parameter	Role	Description
Conditions	Optional	Conditions are the set of conditions (max 5 rules) that will be used to decide which action to be performed in Statements or Else Statement.  If no conditions is set, it means always matches > always trigger actions in Statements.
Statements	Required	Sequence of actions (max 5 rules) to perform if conditions match.
Else Statement	Optional	Sequence of actions (max 3 rules) to perform if conditions do not match.

1. Conditions

Parameter	Role	Description
variable	Required	Session Variable or SIP Header, SIP Params
pattern	Required	The regex is used to define a search pattern

2. Statements

Parameter	Role	Description
reference	Optional	Session Variable or SIP Header, SIP Params
pattern	Optional	The regex is used to define a search pattern
target	Required	New Variable (V-) or new Header (X-)
values	Required	The list of values which can be fix chars, or back-reference from reference with pattern

3. Else Statement

Parameter	Role	Description
action	Required	2 available actions:Log: add log message (can be used to monitor/alert)Drop: hang up the call
param	Required	String base, depending on the value of action:Message content for logHangup reason for drop

The pattern must follow Perl Compatible Regular Expressions (PCRE)  syntax.

Syntax Description

The below table shows most formalisms provide the following operations to construct regular expressions.

How to create a new manipulation rule

1. Go to Settings > Manipulation > New profile

Fill in Conditions (optional) > Statements (required) > Else Statement (optional) > Create

3. Finish

The post Settings – Manipulation appeared first on Data Dynamics Pte Ltd.

Introduction

The translation rule replaces a sub string of the input number if the number matches the match pattern. The regex engine is used to check for a match based on the match pattern.In other words, this translation rule is to convert the prefix of number as your requirement.Translation rule is applicable to both types of trunks: Inbound and Outbound.

• Number of translation rules can be created: unlimited.
• Number of translation rules can be applied to one trunk: maximum 5 rules.

Parameters

• Name: name of translation rule
• Pattern: the pattern of number which will be applied to translation rule
• Replacement: the replacement for the number if pattern is matched

Pattern and Replacement must follow Perl Compatible Regular Expressions (PCRE)  syntax.

Syntax Description

The below table shows most formalisms provide the following operations to construct regular expressions.

Create new Translation Rule

1. Go to Setting > Translation > Click New profile

2. Give new rule a name > Input Pattern & Replacement > Create

3. Finish

Example

Test the Translation Rule

You can use this link for regex testing.

 

The post Settings – Translation appeared first on Data Dynamics Pte Ltd.

• Step 1: Get some basic settings ready before creating a trunk:
  • Codec:  G711A (PCMA) / G711U (PCMU) / G729
  • Capacity:  number of CPS, concurrent call 
  • Translation Rule (optional)
  • Manipulation (optional)
    .
• Step 2:  Create 2 Trunks (Inbound & Outbound) for your vendor based on their interconnection form

• Step 3:  Configure routing plan for your Edge Server:
  • DNIS routing (required)
  • CLID routing (optional)

The post Get Started: How to connect B3networks with Vendors through Edge Server appeared first on Data Dynamics Pte Ltd.

1. Call per second (cps) – Max: 50: the amount of calls you can initiate in a single second. 
2. Concurrent Call – Max: 1000: the total amount of live calls (including calls in calling state) you can have at the same time.

This can help prevent a DOS type attack. If the cps limit is reached, the host will be blocked by software in 60 second.  If the Concurrent Call limit is reached, new call will not be processed.
To configure it, please follow the steps below.

The post Settings – Capacity appeared first on Data Dynamics Pte Ltd.

The post Settings – Codec appeared first on Data Dynamics Pte Ltd.