# Enhanced Routing Algorithm Based on Reinforcement Machine Learning--A Case of VoIP Service
## 5 Results and Discussions
\begin{table}
\begin{tabular}{c c c c c c} \hline \hline \multicolumn{6}{c}{**Mode 2**} \\ \hline  & \multicolumn{2}{c}{**T3**} & \multicolumn{2}{c}{**T4**} \\ \hline  & **3 Drops** & **5 Drops** & **7 Drops** & **3 Drops** & **5 Drops** & **7 Drops** \\ \hline  & **(kbps)** & **(kbps)** & **(kbps)** & **(kbps)** & **(kbps)** & **(kbps)** \\ \hline e-RLRP & **2.78** & **3.33** & **5.92** & **2.81** & **3.35** & **6.17** \\ RLRP & 4.78 & 4.72 & 7.95 & 4.90 & 4.82 & 6.41 \\ Batman & 9.90 & 12.20 & 15.45 & 10.20 & 11.98 & 14.85 \\ OLSR & 3.92 & 5.10 & 6.80 & 4.10 & 5.33 & 6.21 \\ \hline \hline \end{tabular}
\end{table} 
Table 23: Overhead (kbps) Obtained in Scenario R with Three flows considering AMR-WB Mode 8. \begin{table}
\begin{tabular}{c c c c c c} \hline \hline \multicolumn{6}{c}{**Mode 2**} \\ \hline  & \multicolumn{2}{c}{**T3**} & \multicolumn{2}{c}{**T4**} \\ \hline  & **3 Drops** & **5 Drops** & **7 Drops** & **3 Drops** & **5 Drops** & **7 Drops** \\ \hline  & **CE/FB/IH** & **CE/FB/IH** & **CE/FB/IH** & **CE/FB/IH** & **CE/FB/IH** \\ \hline  & **(kbps)** & **(kbps)** & **(kbps)** & **(kbps)** & **(kbps)** \\ \hline e-RLRP & **27.84** /27.87** /27.77 & **27.86** /27.65** /27.82 & **27.48** /27.31** /27.67 & **27.85** /**27.86** / **27.76** / **27.76** / **27.56** / **27.71** / **27.84** & **27.50** / **27.35** / **27.69** \\ RLRP & 27.83 /27.71 /27.73 & 27.80 /27.70** / **27.66** & 27.46 / 27.30 / 27.23 & 27.84 / 27.76 / 27.75 & 27.65 / 27.74 / 27.82 & 27.48 / 27.34 / 27.20 \\ Batman & 27.69 / 27.47 / 27.76 & 27.60 / 27.63 / 27.66 & 26.69 / 26.97 / 26.87 & 27.07 / 27.75 / 27.75 & 27.63 / 27.68 / 27.71 & 26.87 / 26.91 / 26.80 \\ OLSR & 27.57 / 27.66 / 27.77 & 27.06 / 27.49 / 27.61 & 27.23 / 27.29 / 27.20 & 27.61 / 27.65 / 27.71 & 27.24 / 27.48 / 27.65 & 27.21 / 27.24 / 27.23 \\ \hline \hline \end{tabular}
\end{table} 
Table 24: Throughput (kbps) Obtained in Scenario R with Three Flows considering AMR-WB Mode 2. \begin{table}
\begin{tabular}{c c c c c c} \hline \hline \multicolumn{6}{c}{**Mode 8**} \\ \hline  & \multicolumn{2}{c}{**T3**} & \multicolumn{2}{c}{**T4**} \\ \hline  & **3 Drops** & **5 Drops** & **7 Drops** & **3 Drops** & **5 Drops** & **7 Drops** \\ \hline  & **(kbps)** & **(kbps)** & **(kbps)** & **(kbps)** & **(kbps)** & **(kbps)** \\ \hline e-RLRP & **2.78** & **3.33** & **5.92** & **2.81** & **3.35** & **6.17** \\ RLRP & 4.78 & 4.72 & 7.95 & 4.90 & 4.82 & 6.41 \\ Batman & 9.90 & 12.20 & 15.45 & 10.20 & 11.98 & 14.85 \\ OLSR & 3.92 & 5.10 & 6.80 & 4.10 & 5.33 & 6.21 \\ \hline \hline \end{tabular}
\end{table} 
Table 23: Overhead (kbps) Obtained in Scenario R with Three flows considering AMR-WB Mode 8. We can see from the results of the 4-flow scenarios that e-RLRP outperforms other protocols in most cases in terms of Throughput and Ppl. Regarding the overhead e-RLRP obtained the best results in all tested scenarios. In addition, it is worth mentioning that the overhead in general increases when there are more flows, however, specifically the overhead generated by the Hello control message is not so impacted. This is because Hello messages are exchanged regardless of the number of streams in the network. In the results presented in Tables 27, 28, 30 and 31, regarding Throughput and Ppl, we can observe that one of the traffic flow (noted as MK) reached a _Ppl_ almost equal to O, because there is a direct route between the two pairs of nodes and no drops occurred in this path. The extra flows were added in order to overload the network. Analyzing the results of the scenarios with more than one traffic flow, specifically three and four flows, it is possible to observe that the e-RLRP outperforms the other routing protocols in most of the network scenarios tested, in terms of _Ppl_ and Throughput. Regarding overhead, we can see that e-RLRP continues overcoming the other protocols. The experimental results confirmed that e-RLRP obtained a lower overhead than the RLRP in most of the scenarios, even when the number of traffic flows, the number of routes or node drops were increased.