Connections & Call Routing

MamtaClient Success ManagerMamta has been with netsapiens for about 8 years; with a background in Organization Development. She has worked with many aspects of netsapiens; including support, training, deployment, and sales.

@BuchMamta

Buch

Agenda

• What are Connections?• What Does The System Match On?• Adding & Configuring Connections• Troubleshooting Connections• Adding & Configuring Call Routes

Connections

• Connections are SIP trunks to origination/termination carriers, other geo nodes, SIP trunks to IP PBXs and CPE (such as Adtran).• Inbound calls must match a connection, pass

any checks, and then be processed via the selected dial translation table

What Are Connections?

Inbound Call Flow

Connections can match the origination on Req-URI, From-URI, To-URI, Contact

INVITE sip:18587645202@nms-nyc.netsapiens.com SIP/2.0Via: SIP/2.0/UDP 54.214.50.165:5092;branch=z9hG4bKLklx1ppPNAoK8h1e027A6BCall-ID: 20140908214219015559-8f1338ed949ac632d4840cd552b6f381Contact: <sip:nms-nyc@54.214.50.165:5092;transport=udp>CSeq: 201 INVITEFrom: "ARCADIA CA" <sip:16268214800@sbc.netsapiens.com>;tag=Lklx1ppPNAoK8h1e027A6BMax-Forwards: 20To: <sip:18587645202@nms-nyc.netsapiens.com>

• Matching on From-URI is most common, followed by Contact. Every trunk is different, reviewing the invite in call history of a failed call will help you determine the right connection.

Making a Connection

• Destination Host – the IP address in the invite that is matched on

• IP Address – the IP Address that invites will be accepted from

• Orig – Inbound• Term – Outbound• Dial Translation - for calls that are inbound the

Inbound DID dial translation is needed to normalize the format of the incoming DIDs

• Dial Permission - can be set at the connection level to only allow the types of calls you want

• Limits• Orig – Inbound calls• Term – Outbound calls• Total – Total calls• OR – Origination rate (calls per second)• TR – Termination rate (calls per second)

Adding A Connection

How Do I Add New Connections?

• Check the Call History for a failed call attempt and to review the INVITE• Look for a unique, consistent pattern on the

invites (e.g. From is always @ProxyIP)• If not perfectly consistent you can apply a *

(e.g. From can be 74.34.23.*)• Generally do not match on the NMS IP, if you

must ensure you limit the source IPs or otherwise authenticate

What Is Matched On?

Received Packet from 208.87.2.221:5060INVITE sip:16133662500@208.87.2.222 SIP/2.0Content-Type:application/sdpTo:sip:16133662500@208.87.2.222From:sip:208.87.2.221; Contact:sip:208.87.2.221:5060Via:SIP/2.0/UDP 208.87.2.221:5060;

Where Is This Call Coming From?

208.87.2.221 is the origination carrier208.87.2.222 is the Core Module

Where Is This Call Coming From?Received Packet from 68.65.253.60:5060INVITE sip:12123527500@64.13.255.83 SIP/2.0From: "6465593755"<sip:6465593755@68.65.253.60:5060>;tag=5C10324631353641000B0934To: <sip:12123527500@64.13.255.83:5060>Contact: <sip:6465593755@68.65.253.60:5060>

68.65.253.60 is the origination carrier64.13.255.83 is the Core Module

• Make sure you lock down connections either by authentication, registration, or CheckIPtoken• IP Address field for CheckIP can be a subnet;

for example, 50.12.59.0/24• Add appropriate dial permissions• If registered, disable auth invite

Securing Connections

Outbound calls can be manipulated via the connection Request, To and From fields.

Outbound Translations

Q - What is this connection being created for?

• CheckIP - Only accept invites from the IPs that are added to the IP Address field.

• ShowServer - If it exists, include the "Server" header to show Server Information in SIP messages.

• Codec Priority - Set codec priority by listing NAME/SAMPLING RATE in preferred order; for example, PCMU/8000 G729/8000.

• PcmuOnly - only accept/offer G711u.

• NoForceCid - Will not change the caller ID from extension to user's telephone number (commonly used in geo node connections).

• NoPortChange - Lock the port for the associated Connection (RTP)

• NoSessionTimer - Disable the configured SessionTimer for this connection.

• OrgMatchTo/OrgMatchReq – Specify which SIP header is to be used as the Origination Match to select the connection for an inbound call. Default is From-URI.

• RouteByReq – Specify Request-URI to be used for routing decision rather than To-URI (useful if calls are coming from a forwarded DID).

• WanGW - Specify whether the Gateway is on the WAN side and if the NatWan address translation is to be applied for messages towards the GW.

Connection Rules

Troubleshooting Connections

• If registered/authenticated, check Admin UI Reject Log

• Otherwise check Call History

Adding a New Carrier Connection

Signaling IPs• 81.201.82.45• 81.201.84.195 • 81.201.83.45• 81.201.86.45 • 81.201.85.45

You want to create a connection(s) to your new carrier – VoxBone. They are an origination only provider signaling from the IPs shown.

Lab

• You just found out VoxBone also allowed termination via the following IP addresses• 81.201.82.45 and • 81.201.84.195

• Modify the connection.

Adding a New CarrierExample – Part 2

Call Routing

• Call Routes enabled you to choose specific outbound connections based on the caller (source) number/domain and called (destination) number/domain; for example, calls from a certain domain, or calls to a certain NPA-Nxx• The destination can also be manipulated by

connection; for example:• Adding in prefixes/billing codes• Stripping dialing codes• Terminating 911 calls through a specific trunk• Terminating 011 international calls through a

different trunk than domestic calls

Call Routes

Outbound Call Flow

• You want to test a new carrier for termination, make a route for all outbound calls to your new carrier from your test domain

Make a Call Route for a DomainExample

• Say you have a UK local term provider, send 01144 calls to that connection first, make the call formatted for local. Why do this in routing rather than connections or dial translations?

dialed: 011448717893642local: 08717893642

Send UK calls to the UK trunkExample

Questions?

Thank You!

1. Download the presentation by visiting our event site at bit.ly/NSUGM17.

2. Practice what we learned by creating test connections and call routes.