Author Topic: MBG Teleworker License consumption/use  (Read 260 times)

Offline bojo387

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 242
  • Country: sg
  • Karma: +3/-0
    • View Profile
MBG Teleworker License consumption/use
« on: November 11, 2024, 01:14:59 AM »
MiVoice Border Gateway 12.0.2.132 (with MiVB)
I am playing with 1 MiNET set and a couple of SIP sets in my lab at home and connect over internet to the WAN (public IP) interface of the MBG at our office.

Observed Behavior (via MBG Dashboard):
a MiNET set: Consumes 1 TW license when connected via WAN.
a SIP set: Does not consume TW licenses when connected via WAN, even though they are registered and functional. - As I understand, this should also consume a TW license as long as I connect from external.
License Persistence: After removing all devices/sets under Teleworker tab, the license count remains at 1 until the MBG service is restarted.

Questions:
Is there a console command or tool to monitor real-time license usage or device connections in the MBG?
We've read that excess TW users/sets can be created, but connections are limited by the actual license count. Is this correct?
Known Issues: Has anyone else experienced similar discrepancies between device connections and license consumption? How did you resolve it?

BR/Bojo


Offline dilkie

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 344
  • Karma: +11/-0
    • View Profile
Re: MBG Teleworker License consumption/use
« Reply #1 on: November 11, 2024, 08:19:32 AM »
MiVoice Border Gateway 12.0.2.132 (with MiVB)
I am playing with 1 MiNET set and a couple of SIP sets in my lab at home and connect over internet to the WAN (public IP) interface of the MBG at our office.

Observed Behavior (via MBG Dashboard):
a MiNET set: Consumes 1 TW license when connected via WAN.
a SIP set: Does not consume TW licenses when connected via WAN, even though they are registered and functional. - As I understand, this should also consume a TW license as long as I connect from external.
License Persistence: After removing all devices/sets under Teleworker tab, the license count remains at 1 until the MBG service is restarted.

Questions:
Is there a console command or tool to monitor real-time license usage or device connections in the MBG?
We've read that excess TW users/sets can be created, but connections are limited by the actual license count. Is this correct?
Known Issues: Has anyone else experienced similar discrepancies between device connections and license consumption? How did you resolve it?

BR/Bojo
sip consumes TW license(s) when in a call (plural, since a sip call can host multiple media streams, audio and video, for example)... minet consumes a license when the set connects.

The reason why we don't consume licenses for minet in a call as it is a stimulus set and MBG cannot reject a call (at least in any way that would make sense to the user). Sip, however, is a different model (essentially it's a peer call control itself) and we can reject a call due to "no licenses" or "out of bandwidth"... etc

and, mbg can send a display "message" to a minet set telling the user that they are out of licenses and to "contact admin".. not possible with sip and simply rejecting a registration just generates support calls.

Also, mbg does "give" you 10% extra licenses to deal with various "glare" conditions.

license count should revert back when sets are disconnected.. if not, and you're sure, raise a trouble ticket.

as for monitoring.. easiest thing is to ssh into mbg and use "tugtail" to watch the live logs. If all you want is license counts.

tugtail | grep " Stats@ Local"

will show something like:

[root@mbg-70 ~]# tugtail | grep " Stats@ Local"
2024-11-11 08:17:44.920-0500 Stats@ Local   :       0/100          0/10000        0/100          1/5000
2024-11-11 08:17:46.123-0500 Stats@ Local   :       0/100          0/10000        0/100          1/5000

the LAST column is the TW license count for this node of a cluster (if you are clustered) and the total licenses allowed.

Offline bojo387

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 242
  • Country: sg
  • Karma: +3/-0
    • View Profile
Re: MBG Teleworker License consumption/use
« Reply #2 on: November 11, 2024, 11:09:30 PM »
Thanks a lot, dilkie! I appreciate the detailed explanation on the license consumption and how it works on both MiNET and SIP.

Thanks for the tugtail command as well. Where can we find documentation on this to help with troubleshooting?

I did another test but even with two WAN connected SIP over a call, the license stayed at 1. I kept the call active for more than 10 minutes but there was no change to the TW license in use both in dashboard and in the console.

2024-11-12 11:49:04.660+0800 Stats@ Local   :       0/0            0/6            0/2            1/3
2024-11-12 11:49:07.462+0800 Stats@ Local   :       0/0            0/6            0/2            1/3
2024-11-12 11:49:37.493+0800 Stats@ Local   :       0/0            0/6            0/2            1/3
2024-11-12 11:50:05.723+0800 Stats@ Local   :       0/0            0/6            0/2            1/3
2024-11-12 11:50:07.523+0800 Stats@ Local   :       0/0            0/6            0/2            1/3
2024-11-12 11:50:37.555+0800 Stats@ Local   :       0/0            0/6            0/2            1/3
2024-11-12 11:51:06.784+0800 Stats@ Local   :       0/0            0/6            0/2            1/3
2024-11-12 11:51:07.585+0800 Stats@ Local   :       0/0            0/6            0/2            1/3
2024-11-12 11:51:37.617+0800 Stats@ Local   :       0/0            0/6            0/2            1/3
2024-11-12 11:52:07.652+0800 Stats@ Local   :       0/0            0/6            0/2            1/3
2024-11-12 11:52:08.853+0800 Stats@ Local   :       0/0            0/6            0/2            1/3
2024-11-12 11:52:37.681+0800 Stats@ Local   :       0/0            0/6            0/2            1/3
2024-11-12 11:53:07.714+0800 Stats@ Local   :       0/0            0/6            0/2            1/3
2024-11-12 11:53:09.917+0800 Stats@ Local   :       0/0            0/6            0/2            1/3
2024-11-12 11:53:37.746+0800 Stats@ Local   :       0/0            0/6            0/2            1/3
2024-11-12 11:54:07.778+0800 Stats@ Local   :       0/0            0/6            0/2            1/3
2024-11-12 11:54:10.983+0800 Stats@ Local   :       0/0            0/6            0/2            1/3
2024-11-12 11:54:37.811+0800 Stats@ Local   :       0/0            0/6            0/2            1/3

We'll downgrade our MiVB to version 11 for comparison and to gather more information before escalating to TCT if needed.

BR/Bojo


 

Sitemap 1 2 3 4 5 6 7 8 9 10