From a872835935719f670d2dfb457f63a91a7e8eb30c Mon Sep 17 00:00:00 2001
From: Marco Capetta <mcapetta@sipwise.com>
Date: Mon, 17 Mar 2025 16:20:04 +0100
Subject: [PATCH] MT#62220 Fix counters in invite_peerout_max_out test

In the test we were setting peers max call limit to
 -1 to prevent a call to a peer
 0 to let the call go through a peer

Thsi is logically wrong and it is now fixed setting
the limits to 0 and 1.

Change-Id: Ia3ad63ea5db6981d87f402f35224703cc0a2fc73
---
 scenarios/invite_peerout_max_out/prefs.json.tt2 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scenarios/invite_peerout_max_out/prefs.json.tt2 b/scenarios/invite_peerout_max_out/prefs.json.tt2
index 325cdbf2..c0dd430b 100644
--- a/scenarios/invite_peerout_max_out/prefs.json.tt2
+++ b/scenarios/invite_peerout_max_out/prefs.json.tt2
@@ -3,9 +3,9 @@
         "nat_sipping": "no"
     },
     "peer_00_invite_peerout_max_out_host0": {
-        "concurrent_max_out": 0
+        "concurrent_max_out": 1
     },
     "peer_01_invite_peerout_max_out_host0": {
-        "concurrent_max_out": -1
+        "concurrent_max_out": 0
     }
 }