Voice redesign - voice to Vsat need hep in creating a test plan briefly to check the voice in all possible ways

We have performed extensive RF site surveys on all of the Permian rigs to determine the best cellular options. In essence this was three hours spent on each rig with a RigNet technician repointing the directional antennas while on both Verizon and AT&T. The results were not spectacular. Ultimately there is only one Verizon and AT&T tower that is usable on any of these rigs. The Verizon tower is closer and provides a better signal strength, but the bandwidth is atrocious and phones would cut out when using it. That appears to be due to extremely high congestion on that tower, given that everyone in Orla is trying to use it. The AT&T tower is much further away but is less congested. All three of these rigs are running on AT&T currently. We continue to see some periods of latency and packet loss on those connections (generally during peak hours) but overall they are serviceable. The bandwidth available to them is limited to about 2 Mbps down 1 Mbps up, however. Sol: To give you some background on this, 3 Rig Sites in Permian are having intermittent issues impacting productivity and need a design fix from the Network side ASAP. The fix suggested is as follows: Put Voice onto VSAT. (no need to failover voice back to LTE on failure of VSAT) If VSAT fails, the Rig has portable SAT phone. VSAT link to have QoS on it to prioritize voice. LTE when it fails over to VSAT should not impact voice calls. Cellular should be locked to LTE only. Please go through the attached documents which should give you an idea about how the Permian Rigs are currently designed, Rig Nets FPL showing the Equipment list, Work packs and RF plan. ************************************ Deployed: This is the testing packet which is not on the network, we are implementing a route for voice traffic from router to VSAT below are the policy based commands that we are pushing on to the router (DNC0018-R-01: [login to view URL]) on the testing packet, there are no changes to be made under the DC1 and DC2 router cause the inbound traffic is already configured to the router via rignet. We are making sure the outbound and inbound traffic has to communicate from rignet and not involving cellular inbetween. access-list 5 permit [login to view URL] access-list 5 deny any log route-map DNC0018-Voice permit 10 match ip address 5 set ip next-hop verify-availability [login to view URL] 20 track 1 set interface GigabitEthernet0/1 interface Async1 no ip address encapsulation slip ip policy route-map DNC0018-Voice ip sla 9 icmp-echo [login to view URL] source-ip [login to view URL] tos 160 threshold 100 frequency 30 ip sla schedule 9 life forever start-time now track 1 ip sla 9 reachability