Messages

1

Mitel Software Applications / Re: MBG Teleworker License consumption/use

« 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.

2

SIP On Mitel / Re: SIP Paging Device

« on: November 10, 2024, 11:59:41 AM »

why is the auth domain "ShoreTel" and the UA "ShoreGear"? that's not an MiVB.

I would say it is MiVoice Connect. (Legacy Shoretel Connect)
https://www.mitel.com/articles/what-happened-shoretel-products

Mitel products have expanded again with buying Unify. Believe we're going to see a bit more of their SBC (OpenScape SBC)

well, yes, but the OP said this was MiVB call server, or at least I thought he did..... MiVB doesn't use that domain for authentication. I had thought this was the MiVB call server. So, other than that, I haven't a clue.

3

Mitel Software Applications / Re: Change Mitel Border Gateway to run behind firewall

« on: November 09, 2024, 10:10:46 AM »

you can change MBG to be single nic by rerunning the setup my server and de-selecting the WAN interface

then you can open ports on MBG public ip on firewall and allow them to teh Internal Address of the MBG.
MBG with 2 interfaces is only supported when one of them has a public IP
if its lan mode or in DMZ it MUST have single network interface Eth0
its its got a WAN interface (Eth1 ) the WAN MUST be direct connected and have a public IP assigned

"got a WAN interface (Eth1 ) the WAN MUST be direct connected and have a public IP assigned"

not true.. the WAN connection can be in a private network (like a DMZ) without a direct public ip assigned to the interface. You do require a public ip assigned to MBG, but that can be owned by the f/w (routing all traffic to MBG). In MBG, you select a "custom" network profile and populate the "setside streaming address" to be the public (and the "icpside" one to be the lan address).

4

SIP On Mitel / Re: SIP Paging Device

« on: November 07, 2024, 09:16:39 AM »

why is the auth domain "ShoreTel" and the UA "ShoreGear"? that's not an MiVB.

5

Mitel Software Applications / Re: Upgrade from 9.7.1.110 to 9.8.1.12.01

« on: October 17, 2024, 02:17:15 PM »

Hi all

I started the update inside Micollab with the appropriate function

Thanks Alessandro

report this to Mitel Product Support.. this shouldn't happen.

6

Mitel Software Applications / Re: Upgrade from 9.7.1.110 to 9.8.1.12.01

« on: October 17, 2024, 12:12:42 PM »

how was the upgrade performed?

7

SIP On Mitel / Re: SIP Paging Device

« on: October 03, 2024, 11:08:46 AM »

not my area.. what call server is that?

8

SIP On Mitel / Re: SIP Paging Device

« on: October 03, 2024, 07:41:50 AM »

It's a Honeywell US Digital Design ATX Station Alerting Controller.

google search turned up this, which has a section for programming sip.

https://prod-edam.honeywell.com/content/dam/honeywell-edam/hbt/en-us/documents/manuals-and-guides/installation-guides/usdd-installation-manuals/hbt-fire-LS10392-USDD-EN-A-ATX-Install-Manual.pdf

9

SIP On Mitel / Re: SIP Paging Device

« on: October 02, 2024, 06:24:25 PM »

It looks like my first post was cutoff.  Basically the two systems see each other they just don't know what to do.  Our tech is unsure how to program the SIP Profile in the Mitel Director page to communicate with the device.  There are some files attached showing some logs.

In regards to the manual, unfortunately it only has this:  "The ATX has a built-in SIP client for receiving VoIP phone calls. The ATX can be configured to register one or more extensions with a phone switch that supports SIP, and when a call is directed to one of the extensions the ATX will answer the call and route the audio to the station

well that's less than useful... how "can the ATX be configured to register one or more extensions"... that's the most important part... other than that, it's just MiVB programming and it could be as simple as a phone DN you call to send an announcement... But i'm sure there's MiVB folks here who know a lot more than I do wrt MiVB programming.

Does the ATX have a model number and manufacturer?

10

SIP On Mitel / Re: SIP Paging Device

« on: October 02, 2024, 03:36:26 PM »

does it come with a manual telling you how to program configuration sip on this device

11

SIP On Mitel / Re: Mitel Telephony - Silent Call Issues

« on: October 02, 2024, 12:29:08 PM »

K, that's getting outside my knowledge of how customer are managed.

tug logs are on MBG... tug is the name of the linux process that does "all" the work (though my partner Mike would disagree)..

In MBG web interface, under "administration" on LH panel, go to "view log files".. you can download a single tug log file (ie. tug/tug.log) or rather them all (plus more) by selecting "collect log files and diag data".. that's called an "sosreport" file if you're ever ask to provide one.

I'm confused why this issue wasn't brought to mitel's PS attention and, if so, why it didn't get escalated enough that the logs would have been looked at to confirm what I posted earlier.

12

SIP On Mitel / Re: Mitel Telephony - Silent Call Issues

« on: October 02, 2024, 11:02:48 AM »

yup, it does.

Best I can offer is to look through the tug logs to see the rtp stats on the calls that have issues... if there are rtp stream issues, it WILL show up there. You can also set up a call recorder to see if the recording also shows a rtp loss (or silence)..

the issue boils down to one of:

• rtp not flowing in one direction
• rtp is flowing in both directions but audio itself is just "silence" packets

Curious, what is "Mitel MSP"?

13

SIP On Mitel / Re: Mitel Telephony - Silent Call Issues

« on: October 02, 2024, 10:33:13 AM »

response not clear...

can't repo on internal calls... good
agent calls via trunks.. failure

is agent using 6920 in this failure?
do 6920 trunks calls (non-agent) have issues?

14

SIP On Mitel / Re: Mitel Telephony - Silent Call Issues

« on: October 02, 2024, 10:10:37 AM »

"Physical Mitel desk phones configured and tested (issues still occur)"

well, if that is the case, it's not a PC or s/w issue... so a physical phone connected to MBG also has instances of silence? Is this on trunk calls or internal calls?

15

Mitel Software Applications / Re: VoIP Softphone Issues Over VPN (MiCollab)

« on: September 20, 2024, 03:12:55 PM »

your edited message got shortened, but going by the original (in my email notification), running any VoIP application over corporate VPNs is generally a bad idea and often has issues. Corp VPNs are usually more than "just" a VPN, they are often firewalls as well as address translation (NAT) and many don't allow full routing to work properly.