You are here: CSP Developer’s Guide: Overview > 6 Layer 4 Call Control PPL Information > RTR - Router (0x0064)
Configuration Bytes
The table below shows the PPL Configuration Byte values for the Router component.
|
BYTE |
Description |
Values |
|---|---|---|
|
0x01 |
Hunting Algorithm |
0x00 = Reserved |
|
0x02 |
Reserved |
|
|
0x03 |
Route entry on rejection |
0x01 - Do Not Retry Routing (default) 0x02 - Retry Routing |
|
0x04 |
Resource Group Table ID |
The Resource Group Table |
|
0x05 |
Route Table ID |
The Route Table to |
General Purpose Registers
The table below shows the General Purpose Register values for the Router component.
|
GPR # |
Description |
|---|---|
|
1 |
Routing Method |
|
2 |
Search Key |
|
3 |
Route Table Entry row index |
|
4 |
Entry Data Tag; Resource Group member counter |
|
5 |
Entry Data TLV Count |
|
6 |
Resource Group Member Count |
|
7 |
Hunting Algorithm |
|
8 |
Resource Group Address Element Type |
|
9 |
Resource Group Member counter |
|
10 |
Reserved |
|
11 |
Index to the Entry Data TLVs |
|
12 |
TLV Data |
|
13 |
Error Codes for rejecting Route requests |
|
14 |
Reserved |
|
15 |
Reserved |
|
16 |
Flag for Criteria/Route Group ID |
|
17 |
Resource Group Tag length |
|
18 |
Resource Group Data |
|
19 |
Flag to track whether the Request initiator being CM or RTR |
|
20 |
Reserved |
|
21 |
Reserved |
|
22 |
More Criteria |
|
23 |
Num Digits to compare |
|
24 |
Criteria Type |
|
25 |
Route Group ID from Route Table |
PPL Timers
The table below shows the PPL Timer values for the RTR component.
|
Timer ID |
Timer Name |
Default Value (seconds) |
|---|---|---|
|
2 |
60 |
|
|
3 |
Initiating RTR Route Operation Complete Event Wait |
30 |
PPL Events
The table below shows the PPL events sent to the Router component.
|
Event |
Description |
|---|---|
|
To Router from CM |
|
|
(1) L4RTRevL4CM_CALL_SERVICE_ROUTE_REQUEST |
Indication of CM requesting a route derivation for an incoming call. |
|
Router to Router |
|
|
(2) L4RTRevL4RTR_CALL_SERVICE_ROUTE_REQUEST |
Indication of RTR requesting a route derivation of an incoming call on a different node. |
|
(3) L4RTRevL4RTR_CALL_SERVICE_REQUEST_ACK |
Indication of RTR successfully deriving a route for a CSR. |
|
(5) L4RTRevL4RTR_CALL_SERVICE_REQUEST_REJECT |
Indication of RTR being unsuccessful in deriving a route for a CSR. |
|
(7) L4RTRevL4RTR_CALL_SERVICE_REQUEST |
Indication of RTR requesting a route derivation to the RTR component at the other node. |
|
(8) L4RTRevL4RTR_ROUTE_OP_COMPLETE |
RTR Indicating to the other RTR about completion of an association among the two RTR components. |