Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - dilkie

Pages: [1] 2 3 ... 24
1
SIP On Mitel / Re: Setting up SIP, but first TFTP...
« on: May 12, 2025, 01:22:31 PM »
sorry folks, the server was decommissioned a few weeks ago. Hopefully someone has another up and running.

2
there is no telnet access (anymore), and http was removed after a certain version (which i can't remember).

3
Mitel Software Applications / Re: MBG Fails Cyber Essentials Plus Audit
« on: January 20, 2025, 04:31:30 PM »
what ports?

4
Mitel Software Applications / Re: MBG / SRC recording
« on: January 16, 2025, 10:15:58 AM »
you need to also have a MiTAI or CSTA connection to MiVB to get all the call details and merge that with the events from MBG.

5
should be available at 66.46.196.230 on tftp port 69 and 20001.. point your set there.

6
Mitel Software Applications / Re: MBG Teleworker License consumption/use
« on: January 01, 2025, 10:23:45 AM »
What Dogbreath said.. only NATed sets consume a teleworker license.

And no, the IPv6 license wasn't due to what you think (no NAT in ipv6 land, thankfully!), the ipv6 license itself costs nothing, it was only a way to see if ipv6 was being adopted (it wasn't). That license was dropped in mbg 12.0 and a lot more ipv6 support was included (setside plus, now, icpside traffic).

7
run tcpdump to see what the connection is failing at... looks like a network issue to me.

correction, i read the original issue wrong, thought you said the problem resolved after re-booting.

8
hat sounds like a temporary error trying to access the blades server. The licensing server, AMC (soon to be SLS), is different from where the s/w is located and download from. SWDL (SoftWare DownLoad)

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

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

11
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).

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

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

14
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?

15
SIP On Mitel / Re: SIP Paging Device
« on: October 03, 2024, 11:08:46 AM »
not my area.. what call server is that?

Pages: [1] 2 3 ... 24