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

Pages: [1]
1
MiVoice Office 250/Mitel 5000 / 5320 handset on Call Manager?
« on: March 26, 2014, 10:18:07 AM »
I have acquired an office currently running MiTel 5000 with 5320 handsets.  All other locations are running Cisco Call Manager.  Has anyone successfully added 5320s in a call manager environment?  I'm sure there is some resale value to the handsets but if possible I would like to use them.

2
MiVoice Office 250/Mitel 5000 / Re: 5320 Teleworker down
« on: August 30, 2013, 02:11:23 PM »
Never mind.  This thread http://mitelforums.com/forum/index.php/topic,4195.msg17772.html#msg17772 led me to look at the NAT address.  Not sure how that would have been incorrect but once I changed it to the public IP of the server all is well.

Thank you.

3
MiVoice Office 250/Mitel 5000 / Re: 5320 Teleworker down
« on: August 30, 2013, 01:37:06 PM »
Did some more digging and found the following settings that seem to point away from a VPN connection.

In DB Programming the phone is set to Audio Stream Receive Port 50100 - already opened. NAT Address Type NAT.

4
MiVoice Office 250/Mitel 5000 / Re: 5320 Teleworker down
« on: August 30, 2013, 01:25:04 PM »
Thank you for the reply Dave.  I can't rule anything out, shouldn't I be able to confirm the previous setup on the server side? 

5
MiVoice Office 250/Mitel 5000 / 5320 Teleworker down
« on: August 30, 2013, 11:40:20 AM »
I inherited this system when we acquired the office so I'm not as familiar with MiTel as I should be. 

I have a single teleworker and her 5320 phone is able to connect to the server, able to make/receive calls but there is no voice heard on either end.  Problem started when two changes were made at the same time - teleworker converted from DSL to AT&T UVerse and our Cisco vendor made firewall changes to add this location to our WAN.

After many searches here and elsewhere it appears that the problem is almost always a port issue in the firewall.  I have confirmed that I have the following ports open:

UDP 50098-50508
UDP 67-69
UDP 20001
UDP 5004-5069
UDP 6004-7039
UDP 5567
TCP 6800-6802
TCP 3998-3999
TCP 5566
TCP 5570
TCP 4000
TCP 80
TCP 44000
TCP 443

The 5320 has been assigned a static LAN IP (192.168.254.x) with the public IP loaded as the Cur Controller IP & ICP1 IP Address.

Any thoughts on what would cause no sound given that those ports are open and that I can connect?

Pages: [1]