Node Name

The logical name of the node for use within PortaBilling®

Manufacturer

Choose Cisco, Quintum, PortaOne or another from the list, depending on the manufacturer of the equipment.

Type

Node type. The options are as follows:

 Cisco

• VOIP-GW: the node functions as a gateway

• NAS: Cisco Network Access Server

• ASR Series: Cisco ASR Series Aggregation Services Routers

• PDSN: Cisco Packet Data Serving Node

Quintum

• VOIP-GW: the node functions as a gateway

PortaOne

• PortaSIP: PortaSIP server

• PortaUM: PortaUM server

• Generic: PortaOne generic node

ALOE/Mera

• MVTS Pro: Mera Networks VoIP Softswitch

BroadSoft

• BS: BroadWorks VoIP communications application server

Mikrotik

• Router: Mikrotik Router OS

• Genband (formerly Nextone)

• MSX: Nextone MSX

Huawei

• ASN: Huawei ASN gateway for WiMAX

• BRAS: Huawei BRAS CX600 Router for broadband Internet access

Dialogic

• IMG: Dialogic Integrated Media Gateway

ECI

• BRAS: ECI Broadband Remote Access Server

Iskratel

• SI3000: Multiservice access node

Alcatel-Lucent

• 7750 ESM: Service Router for broadband Internet access

Node ID

For a VoIP node, this is equivalent to a hostname for an internet server (e.g. mail1.cyberdyne.com), i.e. a descriptive, human-readable name used for identification purposes. Make sure the value you enter here matches the “hostname” parameter configured on the gateway, since that value is returned from this node in the h323-gw-id attribute, and the ability to match these values with data in billing significantly simplifies troubleshooting.

NAS-IP-Address

The IP address of the node.

RTP Proxying

Describes the NAT traversal capabilities of this node:

• Direct – RTP stream should be send directly to this node; RTP proxy should not be used.
• Optimal – This node is capable of NAT traversal; no RTP proxying is required unless specifically requested.
• OnNat – This node is not capable of NAT traversal; engage RTP proxy if the other party is behind the NAT.
• Always – When sending a call to this node, always engage RTP proxy, so that no direct media stream goes to it.

Client Protocol

This protocol is used for communication between the node and the billing engine. The options are as follows:

• Disabled – Select this option to disable communication between the node and the billing engine.

• RADIUS – Select this option to communicate with the billing engine if the node supports the RADIUS protocol.

• Diameter – Select this option to communicate with the billing engine if the node supports the Diameter protocol.

Radius Key

This input will be available only if the node has been designated as a Radius client. This is the authentication key for all Radius interactions. Click the Auto button to automatically generate a hard-to-guess password.

Radius Source IP

More than one interface can be present on the node; specify the IP address of the one that communicates with the Radius server.

POD Server

The POD server is a service that controls Internet sessions on the NAS based on RFC 3576.

When enabled, PortaBilling® communicates with NAS via either RADIUS or Diameter protocols to change the parameters of a current session or to terminate it. For example, when an internet-connected account runs out of balance, exceeds its data transfer limit, switches access policy or expires.

To perform real-time charging, enable the POD server for gateways that support RADIUS CoA (Change-of-Authorization) and / or DM (Disconnect Message) and Diameter RAR (re-authorization request).

Shared Key

A shared secret that is used for authenticating requests.

Radius IP

An IP address for a RADIUS RFC 3576 server to which requests are sent.

Port

The internet UDP port to which requests are sent. If not specified, the default port typical for the NAS device is used (e.g. 3799).

Realm

Specify the realm of the node. It is used to identify the node in Diameter messages.

POD Server

Select this check box to enable interaction with the POD server.