UC360 Registration on Mitel 5000 Controller

[txmod777]

Hi!

I have had this UC360 (A/V Model 50006474, Mitel SW Version: 2.1.7.1) since January.

I have exhausted my resources in trying to get this thing registered to our Mitel 5000 Controller (Release: 2.6.22.19-4.03.0-mitel_acp5000. 6.2 SP2, CP Version 6.2.6.80).

Before I dig into what I have found so far: There is another post on here where someone shared the UC360 admin guide. The configurations section in the admin guide specifies the need for a UC360 (Audio Only 50006580). My licensed Mitel vendor has told me these (A/V UC360) are supposed to work on our controller and he himself attempted to register it (although I believe it was a half-hearted attempt).

I have created the SIP Phone and SIP Phone Group as instructed (in the guide as well as many other places). But, despite that, my UC360 will display "VCS Service Binding" and then, a few moments later, will display "Internal Error".

Wireshark logs show that the controller is attempting to reach the UC360 back on some port (looks like the packets are addressed to UDP 17?) and reports that the port on the UC360 is unreachable. I've been mirroring the traffic between the 5000 and the UC360 and, after some TCP resets, it just says repeats the same "port unreachable" errors.

I have tried every variation of configuration in the 5000 over the past few months. All of them have included the 5060 SIP port (as well as on the UC360 itself). The closest I ever got to seeing progress (which was before my vendor stepped in) was having the controller throw a registration error alarm (although I suspect it was because I had decreased the registration timeout on the UC360 to something particularly low).

This is the only SIP phone we have (the other 100+ are 5320/5330's) so we haven't had any setup experiences with these in the past. We have purchased and applied the appropriate F class license to the controller.

The controller SIP group settings are all default with the exception of the registration IP address (set to our controller. I've tried it as all sorts of addresses up until now) and max number of calls is set to 4. The SIP Device for the UC360 has the username 1200, Display name as 1200, and I did change the password but have ensured its the same between the controller and the UC360.

The 5000 does exist on a separate VLAN but I have ensured that traffic is able to communicated between it and the other VLAN's as neccesary.

I have attached the logs from the UC360 as well as a truncated wireshark capture display the port unreachable errors.

Any assistance would be greatly appreciated!

[acejavelin]

What software version is your UC360? Have you performed a factory reset on the UC360?

Have you gone through the configuration document Mitel has to configure the MiVO250 and UC360?

[txmod777]

Hi!

The UC360 reports that it's running Mitel SW Version: 2.1.7.1.

We have reset it multiple times (to no avail each time).

I have followed the "UC360 COLLABORATION POINT ADMINISTRATION GUIDE" and the instructions it entails for registering it to the 5000 controller.

[acejavelin]

Logs show the UC360 is trying to register, it is sending the registration, but the MiVO250 is never responding.

Check in System - IP Settings - Advanced IP Settings and make sure SIP UDP Listening Port Enable is set to Yes.

Also, try putting the same credentials into X-Lite and see if you can get it to register.

[txmod777]

I did check and UDP 5060 is open and enabled!

I will try X-Lite and see if I can get any results from that today.

[txmod777]

So, I gave X-Lite a try and got the same response.

It seems, despite UDP 5060 being flagged as opened and enabled, the controller isn't actually listening on that port.

Checking open and listening ports via netstat confirms this:

netstat -tulpn
(No info could be read for "-p": geteuid()=1008 but you should be root.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:44000           0.0.0.0:*               LISTEN     -
tcp        0      0 0.0.0.0:4000            0.0.0.0:*               LISTEN     -
tcp        0      0 0.0.0.0:30081           0.0.0.0:*               LISTEN     -
tcp        0      0 0.0.0.0:5570            0.0.0.0:*               LISTEN     -
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN     -
tcp        0      0 0.0.0.0:6800            0.0.0.0:*               LISTEN     -
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     -
tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN     -
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN     -
tcp        0      0 0.0.0.0:4444            0.0.0.0:*               LISTEN     -
tcp        0      0 0.0.0.0:5566            0.0.0.0:*               LISTEN     -
tcp        0      0 0.0.0.0:3999            0.0.0.0:*               LISTEN     -
udp        0      0 0.0.0.0:4000            0.0.0.0:*                          -
udp        0      0 0.0.0.0:20001           0.0.0.0:*                          -
udp        0      0 0.0.0.0:1593            0.0.0.0:*                          -
udp        0      0 0.0.0.0:5567            0.0.0.0:*                          -
udp        0      0 0.0.0.0:67              0.0.0.0:*                          -
udp        0      0 0.0.0.0:5060            0.0.0.0:*                          -
udp        0      0 0.0.0.0:69              0.0.0.0:*                          -
udp        0      0 0.0.0.0:2427            0.0.0.0:*                          -


Is there any reason the controller wouldn't start accepting traffic to the port despite it being enabled in DB programming?

[Tech Electronics]

txmod777,

If it was enabled after starting up the system you have to perform a reboot after a backup database save to the systems compact flash. This is one of a handful of flags that require a reboot, but the system nor the help files will tell you that.

Let's start at the beginning and see what needs to be done.

1. Go to MiVoice Office 250 > Software License: Verify there is a Category F Phone License applied.

2. Go to System > IP Settings > Advanced IP Settings: Verify
SIP UDP Listening Port Enable: Yes
SIP UDP Listening Port: 5060

3. Go to System > IP-Related Information > Call Configurations: Create a new Call Configuration, most likely 3, and Lable SIP Devices

4. Go to System > IP-Related Information > Call Configurations > 3: Set the following
Audio Frames/IP Packet: 2
Minimum Playback Time: 20
DTMF Encoding Setting: RFC 2833
Speech Encoding Setting: G.711 Mu-Law
Average In Time Frame Percentage Threshold: 45 <- This is not necessary, but I set this to reduce false positives on network issues.

5. Go to System > Devices and Feature Codes > Phones > 1200: Verify that Type is SIP Phone and not MiCollab Client or 69xx SIP Phone

6. Go to System > Devices and Feature Codes > Phones > 1200 > Verify the SIP Phone Group ID: Most likely P9001

7. Go to System > SIP Peers > SIP Phone Groups > P9001 > Configuration: Verify
Port Number: 5060
Call Configuration: 3
Maximum Number of Calls: 4
DTMF Decoding Payload: 101

8. Go to System > SIP Peers > SIP Phone Groups > P9001 > Configuration > Authentication: Set the following
Enable In-bound Authentication: Yes
In-bound Authentication Username: 1200
In-bound Authentication Password: {follow standard practices}

Once you setup the UC 360 with the same credentials you should be good there.

Now, you should also turn on VLANs in the UC 360 if you are using them.

1. Go to Settings > Advanced > System Settings > Network Settings > 802.x Protocol: VLAN Enabled: Yes

I am going to assume since you have the manual for the UC 360 that you set it up properly.

Thanks,

TE

[txmod777]

Hey TE!

Thank you so much for all of your help!

I was in such a hurry yesterday afternoon I didn't have the opportunity to post here that I had finally figured it out yesterday!

Although, my next step was to definitely restart the controller (but as those opportunities don't really come often during the business day I was trying to figure something else out!).

I was digging around and saw someone had, at some point, mentioned being able to start a terminal shell from the ORM interface.
I also saw that someone had mentioned that Mitel had some built in iptables rules that caused some issues for them separate of this issue.
I had avoided digging into the controller up until this point because my Mitel vendor has been able to take care of any issues I had with our controller (up until now...).

So, I logged into the controllers ORM interface using SSH (I believe I had set the admin credentials through DB Programming a long time ago).
I entered the "Shell" command which gave me access to a terminal.

I checked the iptables configuration and sure enough there was one firewall entry in the input chain that caught my eye (using 'iptables -L --line-numbers')

17 REJECT     udp  --  anywhere             anywhere            udp dpt:sip reject-with icmp-port-unreachable

So, all I did was enter a firewall rule with slightly higher priority (I need to insert these rules above the reject rule located at line 17 so I entered them at line 16) to allow my local subnets to access the controller through UDP 5060:

iptables -I INPUT 16 -p udp --dport 5060 -s 192.168.200.0/24 -j ACCEPT

And sure enough the phones started to register!

I hadn't realized up until now that I could open a Linux terminal outside of the proprietary ORM terminal and I definitely wish I had tried before.

I've also read that these changes (the iptables changes) aren't always persistent so I'm partially expecting these additions to go away once I restart the controller.
I will most likely restart the controller this weekend to check it out and follow your instructions to ensure things are working the correct way.

I will update if anything odd comes up!

Thank you so much again; this was quite the headache (my vendor was convinced the UC360 was broken...lol).


txmod

[Tech Electronics]

txmod777,

I believe with the version of software you are running that you should have access to the firewall through the web interface of the MiVO-250. Just open a browser and point it to the IP Address of the MiVO-250 and use the admin credentials to log in. Within there you should see the firewall and its rules.

Thanks,

TE

[txmod777]

TE,

That is accurate! I don't know how I managed to miss that; I guess I assumed if it wasn't available through the System Administration and Diagnostics tool (which it may be and I may have just missed it!) then I wouldn't have found it on the web interface.

Thanks again!

txmod

[Tech Electronics]

txmod777,

Well, System Administration and Diagnostics and the Web Interface do share a lot of functionality they do not really pass information between themselves as they are both just tools to access information from the system itself.

If you look at both as separate tools you will start to see a lot of differences between the two and how each can be used to support technicians in solving issues or just gathering information.

Thanks,

TE