wiki:Administrators/RadiusBasedRouting

Radius Based Routing

The routing in DataTechLabs ArrowBilling and LongBow Billing (DTL) is performed on call-per-call basis. NAS should request routing information in the same Radius Access-Request message which is used to authorize the call to specific number. DTL will respond with acceptable route information in Access-Accept message.

Applicability

This mechanism is applicable to following products: DTL ArrowBilling and LongBow Billing versions 1.8.0 and higher, versions 2.X.X

Routing Request

Routing processing can operate in one of 3 modes:

  1. Permanently switched off. No Routing information will be sent to NAS device;
  2. Permanently switched on. Every Access-Accept packet will contain Routing Instruction
  3. Routing On demand. The Routing information is supplied if NAS requests it.

Routing Request for “Routing On demand” mode:

NAS should supply following Radius AVPs to request routing information if DTL is operating in “Routing On Demand” mode:

AVP VSA Name Value
26 1 Cisco-AVPair xpgk-request-type=route
26 1 Cisco-AVPair xpgk-routing-request=1

Routing response

DTL Routing response has 3 sets AVPs which can be used to parse routing information. NAS can use any one or more of these 3 sets as they contain redundant information.

Response set 1: Cisco mode.

Contains list of AVPs with one or several routing choices. Each AVP represents ONE distinct route. The order of AVPs in message determines the order of Route priority, with first AVP being most preferred route.

AVP VSA Name Value
26 1 Cisco-AVPair h323-ivr-in=routing:<proto>/<proxy>/<redir_src_num>/<redir_dest_num>/<bill_src_num>/<bill_dest_num>/<redir_dest_ip>

Value string description:

<proto>:

protocol of terminating gateway, values:

  • ANY – any or non relevant
  • SIP – SIP
  • H323 – h.323

<proxy>:

proxy mode (not in use now, always set to 0)

<redir_src_num>:

redirected calling station ID, used for outgoing call leg

<redir_dest_num>:

redirected called station ID, used for outgoing call leg

<bill_src_num>:

calling station ID used for billing purposes

<bill_dest_num>:

called station ID used for billing purposes

<redir_dest_ip>:

redirected destination IP address

Example:

h323-ivr-in=routing:SIP/0/7004/10012127773456/7004/12127773456/192.168.10.101
Response set 2: Mera MVTS mode.

Contains list of AVPs with one or several routing choices. Each AVP represents ONE distinct route. The order of AVPs in message determines the order of Route priority, with first AVP being most preferred route.

AVP VSA Name Value
26 252 Cisco-Command-Code <proto>/<proxy>/<redir_src_num>/<redir_dest_num>/<bill_src_num>/<bill_dest_num>/<redir_dest_ip>

Value string description:

<proto>:

protocol of terminating gateway, values:

  • ANY – any or non relevant
  • SIP – SIP
  • H323 – h.323

<proxy>:

proxy mode (not in use now, always set to 0)

<redir_src_num>:

redirected calling station ID, used for outgoing call leg

<redir_dest_num>:

redirected called station ID, used for outgoing call leg

<bill_src_num>:

calling station ID used for billing purposes

<bill_dest_num>:

called station ID used for billing purposes

<redir_dest_ip>:

redirected destination IP address

Example:

SIP/0/7004/10012127773456/7004/12127773456/192.168.10.101
Response set 3: GnuGK mode.

Contains two lists: one list of redirect IP addresses, and one list of redirected called station ID numbers. Each element in each list represents ONE distinct route. The order of elements in AVP determines the order of Route priority, with first element being most preferred route.

AVP VSA Name Value
26 108 h323-redirect-ip-address h323-redirect-ip-address=<redir_dest_ip_1>;<redir_dest_ip_2>;...<redir_dest_ip_N>
26 106 h323-redirect-number h323-redirect-number=<redir_dest_num_1>;<redir_dest_num_2>;...<redir_dest_num_N>

Value string description:

<redir_dest_ip_1>:

First choice IP address

<redir_dest_ip_2>:

2nd choice IP address

<redir_dest_ip_N>:

Nth choice IP address

<redir_dest_num_1>:

First choice redirected calling station ID

<redir_dest_num_2>:

2nd choice redirected calling station ID

<redir_dest_num_N>:

Nth choice redirected calling station ID

Example:

h323-redirect-ip-address=192.168.1.1;192.168.1.10;192.168.1.2
h323-redirect-number=0012127773456;9912127773456;12127773456
Last modified 7 years ago Last modified on Dec 1, 2010, 2:36:15 PM