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 - DB32120

Pages: [1]
1
Might be wrong but the DLM needs to be equivalent or higher version than the other elements

2
Mitel MiVoice Business/MCD/3300 / Re: Accessing VMCD MSL page issue
« on: June 10, 2015, 06:57:16 AM »
Your browsing to the wrong IP address. That's the IP for the vMCD you need the know the IP for the MSL.

You can find the IP address of MSL via the System IP Properties form on MCD

3
Mitel MiVoice Business/MCD/3300 / Re: DHCP Issue
« on: June 10, 2015, 06:54:26 AM »
since your using HP switches I would go down the route of LLDP as Lundah said.

Take a look at the below as an example of LLDP on HP switches

Quote
Our basic HP config is as follows ( simple and seems to work well)


int 24
name "mitel"
Vlan 1
name "data"
ip address 10.100.10.10 255.255.255.0
untagged 1-23,25-28
exit
vlan 2
name "voice"
ip address 172.16.1.254 255.255.255.0
untagged 24
tagged 1-23,25-28
qos priority 5
voice
exit
ip routing
ip route 0.0.0.0 0.0.0.0 10.100.10.1
lldp run
- The mitel we have as 172.16.1.2 , 255.255.255.0 gateway 172.16.1.254 ( hp switch)
- in its DHCP server we dont provide any vlan options

The phone boots up and does a dhcp request
the switch recognises it as a voice device and forces it into vlan 2 where it does another dhcp request
the mitel's port is forced into Vlan 2 and every packet leaving it is tagged as vlan 2
- the mitel supplies the dhcp for phones
- our server  in the 10.100.10 network supplies any laptops / pc's with DHCP
our gateway 10.100.10.1 has a static route to the 172.16.1.0 network as follows

route 172.16.1.0 255.255.255.0 10.100.10.10

- ie route all 172.16.1.0 packets to the HP switch

The most important command is the "untagged in vlan2 for the Mitel port"

4
As long as the ring group and mailbox match it should be a simple case of pointing the overflow point to the voicemail hunt group.

good luck with getting a message waiting indicator though, if you require that your going to have to use ACD path which interflows to single line etc.

5
MiVoice Office 250/Mitel 5000 / Re: Looking for IP Card
« on: June 10, 2015, 06:37:49 AM »
Do you have any remote phones working already?

If not have you made sure you have changed the NAT settings on the IP connections?

6
I've never been able to remove this. Would be interested if someone has.

I think best you can do it record the name of the mailbox as the destination, for example "Sales"

7
Mitel Software Applications / Re: Shellshock Worm
« on: October 03, 2014, 05:46:31 AM »
This was fixed in a new patch a few hours ago.

For those with MOL access you can find the latest update here.

http://domino1.mitel.com/ProdSupp/prodsupkb.nsf/ByProduct/611D18460FF313BA85257D65006C6547?opendocument&login

For those that don't, here is the update:

Article ID #
14-1263-00115      Article Type
Technical Bulletin

      
Article Title
#2014-1004-04 - MBG Remediation Plan - Remote Code Execution Vulnerability in BASH Interpreter -       Publish Date
Oct-2-2014
      

Body/Solutions
MBG Servicelink Update for ShellShock Bug

This service link eliminates a publicly-known defect in the BASH interpreter that affects MiVoice Border Gateway (MBG) and can potentially lead to a security vulnerability. This bug is widely known as “Shellshock.”

About the BASH Defect

The ShellShock bug is a group of serious vulnerabilities in the popular BASH shell interpreter. It is also widespread, existing in most Linux-based products. Since the initial vulnerability was first announced and patched, new aspects of the vulnerability have been discovered. This servicelink update eliminates all currently-known vulnerabilities in BASH related to ShellShock. These are being

tracked as:

• CVE-2014-6271,

• CVE-2014-7169,

• CVE-2014-7186,

• CVE-2014-7187,

• CVE-2014-6277, and

• CVE-2014-6278.

The flaw involves improper processing of environment variables. In certain configurations, the ShellShock vulnerability may allow an unauthenticated remote attacker to execute malicious code on a targeted system. Of particular concern are services that receive a request via HTTP and use BASH to execute commands on the server. In some configurations, this vulnerability could be used to install malware on a server. Independent reports indicate that vulnerable systems are being targeted and compromised for use in botnets.

Risk to MiVoice Border Gateway Systems

ShellShock is rated as a serious vulnerability, but the actual risk varies from system to system. In most deployments of the MBG, the risk is relatively small. Two of the most common ways of exploiting the ShellShock vulnerability is through CGI programs on a web server or via a poorly secured SSH server. However, Mitel normally recommends that the SSH server be disabled by default and most MBGs have no CGI scripts. The exceptions to this are MBGs configured to support YA clients or secure call recording. Even in these configurations, these CGI scripts are unlikely to be known to the malicious scanning engines that are the most prevalent threats “in the wild.”

Nonetheless, Mitel strongly recommends that all customers install the servicelink update to correct the defect. Mitel continues to monitor the situation around the ShellShock bug.

Remediation Plan for Stand Alone Mitel Border Gateway Systems


Mitel Border Gateway Version 8.1

An updated version of the Mitel Standard Linux has been released via AMC to allow for systems to pick up the ShellShock fix. For both physical and virtual servers, please open the blades panel in server-manager, select update list and click upgrade beside the 10.1.0.31 service link load.
As with all upgrades, make a backup of the system before proceeding, and another is recommended following the update.

Any new install must be running 10.1.31.0 or AMC may fail to download license keys.

Mitel Border Gateway Version 8.0

An updated version of the Mitel Standard Linux has been released via AMC to allow for systems to pick up the ShellShock fix.
Physical systems may access the blades panel in server-manager, and execute the servicelink upgrade to 10.0.51.0.
It is recommended to then upgrade MBG to the latest 8.0 blade.

Virtual systems must redeploy the MBG ova file, using 8.0.26.0, and restore the database. Then upgrade the servicelink via the blades panel to 10.0.51.0, and then MBG to 8.0.27.0.
Alternatively, if SWA is active, deploying 8.1.13.0, restoring the db and upgrading servicelink to 10.1.31.0 is also an option.

As with all upgrades, make a backup before proceeding, and a second backup following the upgrade is recommended.

Mitel Border Gateway Version 7.1

An updated version of the Mitel Standard Linux has been released via AMC to allow for systems to pick up the ShellShock fix.
For both physical and virtual servers, please open the blades panel in server-manager, select update list and click upgrade beside the 9.4.39.0 service link load.

As with all upgrades, make a backup of the system before proceeding, and another is recommended following the update


Mitel Border Gateway Version 7.0

An updated version of the Mitel Standard Linux has been released via AMC to allow for systems to pick up the ShellShock fix.
For both physical and virtual servers, please open the blades panel in server-manager, select update list and click upgrade beside the 9.3.31.0 service link.

As with all upgrades, make a backup of the system before proceeding, and another is recommended following the update

8
I have raised this with Mitel 3rd Line in the past. It's because the STAR answers the call and transfers it elsewhere the system thinks of the call as an internal call so it gives the outside caller the internal ring back, not the BT standard.

As mentioned the only work around is buying a second MOH license and using that. It's stupid and for this reason I try ans avoid STAR's when possible.

Pages: [1]