Messages

1

MiVoice Office 250/Mitel 5000 / Dropped calls between networked branches

« on: April 13, 2016, 12:13:31 PM »

Hey guys,

I have 4 branches networked together, and there is currently a big problem  between two of them wherein calls between them are frequently being dropped. This company was having lots of issues a few months ago with every branch going down frequently, and this was fixed by upgrading each branch to 6.0.11 (the latest version at the time). Since then, things have been relatively smooth between most branches, though I understand there have been a few calls dropped between other branches, however, between two of them in particular, there have been a lot of issues. The phone systems are set up on a VPN that runs through their main office as a central hub, so all call traffic is routed through the main office. They are all running on (decently) fast internet connections so I don't think that should be causing any problems. Does anyone have any suggestions? The client would like to know if they should take the phone systems off the VPN. The only way I am aware of doing this is to put each phone system on its own external IP address, which we would get directly from the ISP, but the client was wondering if they could simply put it on the internal network and use port forwarding (I do not think this would be a good idea even if it is feasible).

Thoughts? Ideas?

Thanks!

2

MiVoice Office 250/Mitel 5000 / IP Phone Issue... Erased Main Load, phone bricked?

« on: March 09, 2016, 02:06:32 PM »

Hi, was having some issues with an IP phone. As per a co-worker's idea, I tried erasing the main load to reset the phone's firmware. After doing this, however, I can't seem to find any way to set the IP phone's options. Holding the volume keys just brings up something that says "Press and hold * to RESTORE DEFAULTS" and that is apparently the only thing I am able to manipulate. I can't find any way to alter IP settings for the phone now. Any help?

3

MiVoice Office 250/Mitel 5000 / Re: Gmail Security Denying UVM

« on: March 07, 2016, 04:15:22 PM »

I think I figured this out. Just want to bump the thread with my solution in case others need help:


Go into individual users' account settings and go to Sign-in and security, then change Allow less secure apps to ON. Voicemails all just came through after doing that. Now I just have to do it for a ton of other email addresses... 

4

MiVoice Office 250/Mitel 5000 / Gmail Security Denying UVM

« on: March 07, 2016, 03:56:16 PM »

How do I get around this? I try using the really long URL in the WEBALERT part of the following log, but Gmail tells me they're  preventing my sign in attempt as they think I've stolen the password. I've already gone to the other URL and enabled device access, but Gmail's security still blocks me out. Is there anyway I can loosen these security settings? This is such a PITA. Using Enhanced Integration with Gateway setup as smtp.gmail.com on port 587, and individual users set up with imap.gmail.com as their Email Server.

Check out this log:

[01324  3-07-2016 15:50:12 ]*UM* IMAP INFO: Trying IP address [74.125.69.109]
[01325  3-07-2016 15:50:13 ]*UM* IMAP INFO: Gimap ready for requests from 75.144.72.30 v3mb251157451igs
[01326  3-07-2016 15:50:13 ]*UM* IMAP WARNING: [WEBALERT https://accounts.google.com/ContinueSignIn?sarp=1&scc=1&plt=AKgnsbs7cCWIkHkIDBln_k-epYynwo13gzg_DYtHGAHTn1brRi8ET6mf722_XurXOikeFmh2kebsAR8Zjc8CzC0uMdSYxzKBhLOt47Wo75xvF4UjJmacYP_61uUylTTNhWKHKmfC0Wfdga27dBo_K17qWT1Vp3HWWAgqNGom1Qs2PJFRh5xbSUeAWBR_Tz51XWN2lA_Sx7TD6CM5qdMl0Dtp4w2UgdTcgc2WcqVaiT6IaHGgp9wX3_M] Web login required.
[01327  3-07-2016 15:50:13 ]*UM* IMAP WARNING: [ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)
[01328  3-07-2016 15:50:13 ]*UM* IMAP ERROR: Connect failed; SSL Authentication Failure
[01329  3-07-2016 15:50:13 ]*UM* 108: FAILED to connect to IMAP Server
[01330  3-07-2016 15:50:13 ]*UM* IMAP ERROR: [CLOSED] IMAP connection broken (command)
[01331  3-07-2016 15:50:13 ]*UM* 108: Restarting Main Thread
[01332  3-07-2016 15:50:13 ]*UM* 108: Entering Main Account Thread Loop
[01333  3-07-2016 15:50:13 ]*UM* 108: The previous connection attempt failed, waiting for 30 minutes.

5

MiVoice Office 250/Mitel 5000 / Re: Trouble with DNS? UVM issue

« on: March 07, 2016, 03:53:34 PM »

Thanks,

I've used that as well. I've used a bunch of different servers, just kind of throwing things at it because I wasn't sure what would stick. I think I've used outlook.office365.com for it. I've used it for other clients successfully, but this client was/continues to have issues.

6

MiVoice Office 250/Mitel 5000 / Re: Trouble with DNS? UVM issue

« on: March 01, 2016, 09:47:15 AM »

I think we were using 587. I've tried all 3 though. Like I said, when I SSH into the phone system and ping out to domains it resolves them. When I ping out to the mail server, it resolves that, too. But when I look in the log to see what's failing with UVM, it still says the host cannot be found.

7

MiVoice Office 250/Mitel 5000 / Trouble with DNS? UVM issue

« on: February 17, 2016, 02:58:26 PM »

Hi,

I'm trying to set up UVM on a system and I notice it cannot find the host. I connected into the phone system via SSH and tried pinging out to various hosts and I realized that I cannot ping out to any domains. I set the DNS servers as 75.75.75.75 and 75.75.76.76 (Comcast DNS servers) but am not sure what to set the DNS Search List to (currently set to a .local on the network, per ipconfig -all) and frankly I've never been sure what to set this value to, so maybe it's sheer dumb luck that I've ever got UVM to work in the past at all. I should mention that most of our clients are small businesses without IT departments or any fancy network setup. I am trying to configure this to work with their Office 365 setup currently. I am pretty sure the problem lies in DNS... any ideas?


Edit: Nevermind. I figured this out. Apparently those DNS servers that I used... don't work??? I am using Google DNS now and can ping domains from the SSH connection now.
Still not sure what to put under DNS Search List though.

Double  Edit:

I am still getting this error
[12805  2-17-2016 15:00:31 ]*UM* IMAP ERROR: No such host as smtp.office365.com
[12806  2-17-2016 15:00:31 ]*UM* IMAP ERROR: Connect failed; TCP Connection Failed
[12807  2-17-2016 15:00:31 ]*UM* 102: FAILED to connect to IMAP Server

8

MiVoice Office 250/Mitel 5000 / Re: Networked Nodes, dropped calls

« on: December 08, 2015, 01:33:57 PM »

Over the last week or two this has degenerated into complete inability to call between certain branches (Busy).

Branches 2 and 3 have some problems connecting to other branches. Branch 4 is the most recently added one, and branch 2 and 3 have  hard time connecting to it, though it can connect to them...

here's some stuff from the message print for node 3

-03:655- 13:03 12-08 M2039 INF HW CP Dead Socket Response From node: 4 Reason(304): Broken pipe
-03:656- 13:03 12-08 M2036 INF HW CP Established IP LINK To node 4
-03:657- 13:08 12-08 M2039 INF HW CP Dead Socket Response From node: 4 Reason(304): Broken pipe
-03:658- 13:08 12-08 M2036 INF HW CP Established IP LINK To node 4
-03:659- 13:24 12-08 M2037 INF HW CP Closed IP LINK To node 4 - Reason(701): Socket timed out
-03:660- 13:24 12-08 M2036 INF HW CP Established IP LINK To node 4
-03:661- 13:25 12-08 M2039 INF HW CP Dead Socket Response From node: 4 Reason(304): Broken pipe
-03:662- 13:25 12-08 M2036 INF HW CP Established IP LINK To node 4
-03:663- 13:26 12-08 M5122 WRN HW CP Nodes Did Not Respond To Broadcast Message From 'PP022' : Nodes 4


As you can see it's only having problems with node 4, but the Network Information monitor shows Node 3 to Node 4 is busy as well as Node 3 to Node 2. It also shows Node 2 to Node 1 (the hub of the VPN through which all connections traverse) is busy.

9

MiVoice Office 250/Mitel 5000 / Re: Networked Nodes, dropped calls

« on: December 04, 2015, 10:10:57 AM »

Every other branch is on 6.0.11 except the main branch which is on 6.0.10. The main branch is also the one with the least amount of errors appearing in their ipra logs. Maybe there is a correlation. I'll look into it, thanks... unfortunately we don't have a certified Mitel technician anymore so we are unable to get tech support from Mitel.

10

MiVoice Office 250/Mitel 5000 / Re: Networked Nodes, dropped calls

« on: December 03, 2015, 10:32:57 AM »

Hi, thanks for the reply...
I thought this was solved as the client has been stable for a few weeks but had another hiccup the other day so I'm back on site looking into things.

Looking through logs for other branches reveals a lot of different errors using any number of different ports that I didn't know Mitel even used... the branch I am at now, however, only seems to have errors on port 5570

here's some of the log for one of the branches:

[01Dec15 02:13:53] ipra_app[INFO]: cc_socket_mgr_t: socket 37 timed out!

[01Dec15 02:13:53] ipra_app[INFO]: cc_socket_mgr_t: socket 37 closed connection to 192.168.2.254:49556, error:  EKATIMEOUT! (701)

[01Dec15 02:13:53] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.2.254:49557!

[01Dec15 03:26:26] ipra_app[ERR]: cc_socket_mgr_t: recv() returned 0!

[01Dec15 03:26:26] ipra_app[INFO]: cc_socket_mgr_t: socket 38 closed connection to 192.168.4.254:53832, error:  Unknown Error! (304)

[01Dec15 03:26:26] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.4.254:43374!

[01Dec15 03:34:25] ipra_app[ERR]: cc_socket_mgr_t: recv() returned 0!

[01Dec15 03:34:25] ipra_app[INFO]: cc_socket_mgr_t: socket 37 closed connection to 192.168.2.254:49557, error:  Unknown Error! (304)

[01Dec15 03:34:26] ipra_app[ERR]: cc_socket_mgr_t: recv() returned 0!

[01Dec15 03:34:26] ipra_app[INFO]: cc_socket_mgr_t: socket 38 closed connection to 192.168.4.254:43374, error:  Unknown Error! (304)

[01Dec15 03:34:27] ipra_app[ERR]: cc_socket_mgr_t: recv() returned 0!

[01Dec15 03:34:27] ipra_app[INFO]: cc_socket_mgr_t: socket 34 closed connection to 192.168.0.254:50881, error:  Unknown Error! (304)

[01Dec15 03:34:34] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.2.254:40223!

[01Dec15 03:34:34] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.4.254:59670!

[01Dec15 03:34:36] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.0.254:46715!

[01Dec15 04:26:41] ipra_app[INFO]: cc_socket_mgr_t: socket 34 timed out!

[01Dec15 04:26:41] ipra_app[INFO]: cc_socket_mgr_t: socket 34 closed connection to 192.168.2.254:40223, error:  EKATIMEOUT! (701)

[01Dec15 04:26:41] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.2.254:59321!

[01Dec15 04:27:08] ipra_app[INFO]: cc_socket_mgr_t: socket 37 timed out!

[01Dec15 04:27:08] ipra_app[INFO]: cc_socket_mgr_t: socket 37 closed connection to 192.168.4.254:59670, error:  EKATIMEOUT! (701)

[01Dec15 04:27:12] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.4.254:53990!

[01Dec15 04:27:42] ipra_app[ERR]: cc_socket_mgr_t: recv() returned 0!

[01Dec15 04:27:42] ipra_app[INFO]: cc_socket_mgr_t: socket 37 closed connection to 192.168.4.254:53990, error:  Unknown Error! (304)

[01Dec15 04:27:42] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.4.254:53991!

[01Dec15 04:54:26] ipra_app[INFO]: cc_socket_mgr_t: socket 34 timed out!

[01Dec15 04:54:26] ipra_app[INFO]: cc_socket_mgr_t: socket 34 closed connection to 192.168.2.254:59321, error:  EKATIMEOUT! (701)

[01Dec15 04:54:26] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.2.254:37782!

[01Dec15 05:10:03] ipra_app[INFO]: cc_socket_mgr_t: socket 37 timed out!

[01Dec15 05:10:03] ipra_app[INFO]: cc_socket_mgr_t: socket 37 closed connection to 192.168.4.254:53991, error:  EKATIMEOUT! (701)

[01Dec15 05:10:03] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.4.254:46861!

[01Dec15 05:13:36] ipra_app[INFO]: cc_socket_mgr_t: socket 37 timed out!

[01Dec15 05:13:36] ipra_app[INFO]: cc_socket_mgr_t: socket 37 closed connection to 192.168.4.254:46861, error:  EKATIMEOUT! (701)

[01Dec15 05:13:36] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.4.254:36333!

[01Dec15 05:41:49] ipra_app[INFO]: cc_socket_mgr_t: socket 34 timed out!

[01Dec15 05:41:49] ipra_app[INFO]: cc_socket_mgr_t: socket 34 closed connection to 192.168.2.254:37782, error:  EKATIMEOUT! (701)

[01Dec15 05:41:50] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.2.254:44891!

[01Dec15 05:51:42] ipra_app[INFO]: cc_socket_mgr_t: socket 37 timed out!

[01Dec15 05:51:42] ipra_app[INFO]: cc_socket_mgr_t: socket 37 closed connection to 192.168.4.254:36333, error:  EKATIMEOUT! (701)

[01Dec15 05:51:43] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.4.254:55657!

[01Dec15 06:29:18] ipra_app[ERR]: cc_socket_mgr_t: recv() returned 0!

[01Dec15 06:29:18] ipra_app[INFO]: cc_socket_mgr_t: socket 37 closed connection to 192.168.4.254:55657, error:  Unknown Error! (304)

[01Dec15 06:29:18] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.4.254:47036!

[01Dec15 06:32:39] ipra_app[INFO]: cc_socket_mgr_t: socket 34 timed out!

[01Dec15 06:32:39] ipra_app[INFO]: cc_socket_mgr_t: socket 34 closed connection to 192.168.2.254:44891, error:  EKATIMEOUT! (701)

[01Dec15 06:32:39] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.2.254:55829!

[01Dec15 07:00:29] ipra_app[ERR]: cc_socket_mgr_t: recv() returned 0!

[01Dec15 07:00:29] ipra_app[INFO]: cc_socket_mgr_t: socket 37 closed connection to 192.168.4.254:47036, error:  Unknown Error! (304)

[01Dec15 07:00:29] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.4.254:33145!

[01Dec15 07:45:56] ipra_app[INFO]: cc_socket_mgr_t: socket 34 timed out!

[01Dec15 07:45:56] ipra_app[INFO]: cc_socket_mgr_t: socket 34 closed connection to 192.168.2.254:55829, error:  EKATIMEOUT! (701)

[01Dec15 07:45:57] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.2.254:45186!

[01Dec15 08:03:59] ipra_app[ERR]: cc_socket_mgr_t: recv() returned 0!

[01Dec15 08:03:59] ipra_app[INFO]: cc_socket_mgr_t: socket 37 closed connection to 192.168.4.254:33145, error:  Unknown Error! (304)

[01Dec15 08:03:59] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.4.254:39748!

[01Dec15 08:05:07] ipra_app[INFO]: cc_socket_mgr_t: socket 34 timed out!

[01Dec15 08:05:07] ipra_app[INFO]: cc_socket_mgr_t: socket 34 closed connection to 192.168.2.254:45186, error:  EKATIMEOUT! (701)

[01Dec15 08:05:46] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.2.254:41670!

[01Dec15 08:05:52] ipra_app[INFO]: cc_socket_mgr_t: socket 33 accepted call-control connection from 192.168.2.254:41668!

11

MiVoice Office 250/Mitel 5000 / Re: Voice Mail to Email (Copy and forward) sending multiple Emails

« on: November 18, 2015, 11:11:20 AM »

Hey, we had a similar issue with Exchange using Enhanced Integration. The thread for that is here: http://mitelforums.com/forum/index.php?topic=7461

Maybe my troubleshooting methods will help you, maybe not. In the end I am not entirely sure what fixed it, but I believe it was a combination of things. Do you have the Domain field in IP settings filled out?

12

MiVoice Office 250/Mitel 5000 / Networked Nodes, dropped calls

« on: November 18, 2015, 09:44:42 AM »

Hi all,

Have 4 branches networked together and the connections seem stable now, I believe every port is forwarded that ought to be (though would appreciate any insight into that) but we occasionally have some dropped calls between branches. I checked out the logs to try to see what is happening but while I can see in the log that there's an error, the error is not verbose at all and I'm trying to figure out what is actually happening. I saw a number of errors occurring overnight while the system was not in use, but just witnessed one on site with the client while they were on the phone with another branch. The call dropped (no "insufficient bandwidth" alarm or anything), and they were able to call right back and complete the call. I immediately refreshed the log and caught it happening, but again, I don't know what the error is or why it's happening... seems to happen a lot on port 5570, which the client says is forwarded.

Here's the error, 192.168.4.254 is the remote node they were on the line with when the call dropped, this is from the local node's logs:


[18Nov15 09:32:12] ipra_app[ERR]: cc_socket_mgr_t: recv() returned 0!

[18Nov15 09:32:12] ipra_app[INFO]: cc_socket_mgr_t: socket 49 closed connection to 192.168.4.254:5570, error:  Unknown Error! (304)

[18Nov15 09:32:13] ipra_app[INFO]: cc_socket_mgr_t: socket 49 established call-control connection to 192.168.4.254:5570!

13

MiVoice Office 250/Mitel 5000 / Re: Office 365 using port 25 Forward and Copy [Solution]

« on: November 09, 2015, 11:13:40 AM »

Camoron,

I understand that troubleshooting remotely is a time saver for both you and your company, but there are times when it is necessary to go out to a site so you can see what is going on. If they do not have port 22 open to allow for SSH, which they shouldn't, then getting to the command prompt is pretty much a no go. The NTP service on the other hand would work if they have port 443 opened up so you can get to the logs through the web service, again they shouldn't allow this over the Internet for security reasons.

I hope that you are able to get this resolved for your customer as it has been a few days for them and I know our customers would be ready to hang someone by now.

Thanks,

TE

I was actually using Remote Desktop to connect into their system, the one time I did. Anyways, going to the client is what I would have preferred, but my boss wanted me to help remotely... frankly, I am not even sure if our company is charging them for our time as it is an "old friend" of my boss (the owner).

We have confirmed the client's unit is online as he had another issue with IP Phones which we now have working. Our client isn't in a particular hurry to get Unified Messaging working, I guess, and as far as I know it's still not working, so I'll follow up and see what I can find out. I am really pretty stumped on this but I still think it's some sort of internal problem.

14

MiVoice Office 250/Mitel 5000 / Re: mitel upgrade from v 2.3 to 6.0.11

« on: November 02, 2015, 10:47:15 AM »

I am not sure about the old version, I don't think it matters though. When you restore the database you should  see a check box that says Restore Voice Processor data from: and then you pick the USB drive and it will restore both the database and the voice processor data from the flash drive. If I'm wrong on this or it didn't work for you someone please correct me.

15

MiVoice Office 250/Mitel 5000 / Re: Office 365 using port 25 Forward and Copy [Solution]

« on: November 02, 2015, 10:40:50 AM »

Thanks for the very helpful info... It has been my suspicion all along that the phone system wasn't connected to the internet, and now I can test that theory... assuming I can get  into the client's system. I was working with them remotely on this entirely over the phone, I have never seen their database and I don't know how it's set up beyond what they've told me, but you've given me a lot to go on. Thanks!