Messages

1

Mitel MiVoice Business/MCD/3300 / SOLVED Re: 5610 Cordless Handset

« on: February 05, 2014, 04:04:19 PM »

Thank for your help on this, we have solved the problem. It turns out to be a firewall problem involving RTP. When Mitel installed the system at our location, they gave us documentation for configuring our firewall, which included forwarding port 5060 through for SIP/RTP to the IP addresses assigned to our phones. In the configuration for the 5610 IP DECT stands they configured the SIP local port to use 5060 and the SIP/RTP port also as 5060, then they set the RTP port range at 20. After reading the debug logs on the 5610's I noticed that for every call they were trying to use various ports between 5060 and 5080 and failing with RTP handler errors. Once I discovered that I changed the single port forwarding of port 5060 to a port range of 5060 to 5080 and the problems went away.

2

Mitel MiVoice Business/MCD/3300 / Re: 5610 Cordless Handset

« on: February 02, 2014, 08:55:41 PM »

After reading MiTel's information on the 5610 cordless handset, it raises some questions, can the IP DECT stand and 5610 cordless handset be used as a standalone device? or does it have to be paired with an IP phone? currently ours are connected to 5320e IP phones.

After reading all the information i can find, its not easily discernible, most everything i've read states that the IP DECT stand and cordless handset are an accessory to be used with an IP phone, other things read like it can be used as a standalone device. 

3

Mitel MiVoice Business/MCD/3300 / Re: 5610 Cordless Handset

« on: February 02, 2014, 04:21:03 PM »

Our service is hosted by Mitel, so even out internal calls go through the firewall, they are sent to MiTel's call server then routed back to our network.

There are a couple things i noticed while reading the IP DECT Stand Configuration and Administration Guide regarding DHCP:

First on page 22:

Setup\IP Settings
You can use DHCP to provide a dynamic IP address to the handsets. Standard Mitel DHCP options (43/60 or 124/125) are not supported.

And on page 26

DHCP
The handsets can be provisioned with an IP address automatically by using DHCP.

When configured, the DHCP option 66 returns an IP address or a DNS string of a TFTP server. The handsets use this DHCP feature to etrieve the address of the configuration server. Even though DHCP specifications refer to the TFTP, the handsets use the retrieved address for HTTP as well, if transport is configured for HTTP (HTTP is default method). In order to use DHCP to retrieve information of configuration server address, you must configure the following parameters. The parameters can be configured using the handset menu or via a configuration file on a boot server.

We have option 43 configured in DHCP for the 5330 IP phones but option 66 isnt configured, should it be? If so should it have the same string as option 43? Could this be a situation where the handsets aren't pulling the correct IP address from the configuration server?

If I understand things correctly, both the cordless handsets and the IP Dect Stand should have their own IP addresses?


Also looking in the debug log for one of the IP DECT stands, I found this:


0130102433 [N](01):Call Outgoing from UA#0 (CallId#11)
0130102434 [N](01):Call Respond #100 received UA#0 (CallId#11) Dialog#855764
0130102434 [N](01):Call Respond #100 received UA#0 (CallId#11) Dialog#855764
0130102434 [N](01):Call Respond #183 received UA#0 (CallId#11) Dialog#855764
0130102434 [N](01):Call Connected call id #11
0130102434 [N](01):Call (CallId#11) RTP Ch: 0 Opened Len: 160, RxPort: 5060, TxPort: 20864
0130102434 [N](01):Call Accept received UA#0 Dialog#855764
0130102434 [W](01):Call RTP Ch: 0 No route to PCM Id
0130102434 [W](01): Bf RuntimeError: l=206, f=ecTask\RtpHandler.c, d=7dc,0,0,0,ffff,ffff
0130102434 [W](01): Bf RuntimeError: l=214, f=ecTask\RtpHandler.c, d=9,0,0,0,ffff,ffff
0130102434 [W](01): Bf RuntimeError: l=235, f=ecTask\RtpHandler.c, d=9,0,0,0,ffff,ffff
0130102434 [W](01): Bf RuntimeError: l=140, f=\Net\Rtp\rtpsstrm.c, d=0,0,0,0,0,0
0130102434 [W](01): Bf RuntimeError: l=246, f=ecTask\RtpHandler.c, d=2,0,0,0,ffff,ffff
0130102434 [N](01):Call RTP Ch: 0 routed PCM Ch: 0, Codec Type: 4
0130102440 [N](01):Call Terminate sent UA#0 Dialog#855764
0130102440 [N](01):Call RTP Ch: 0 Closed.

Does anyone know what these errors are related to?

4

Mitel MiVoice Business/MCD/3300 / Re: 5610 Cordless Handset

« on: January 31, 2014, 01:00:59 PM »

For our network we have 2 HP Procurve 2910al 48 port PoE switches stacked with a 10GbE interconnect using spanning tree, we have a Sophos UTM-9 for the firewall. we have about 40 phones on a vlan all in the same subnet. the 2 5610 IPDECT stands are plugged into 5320 phones. The phones are on a different subnet from the data.

All of the phones work fine, including the 2 that the IPDECT stands are plugged into. I'm not sure its a firewall issue because we would be seeing problems across the board with the phones. The cordless phones are using the same ports as the other phones and the ports are forwarded correctly and QoS is all set up right.

Whats odd is, if the user replaces the call immediately after the first call. everything works fine.

5

Mitel MiVoice Business/MCD/3300 / 5610 Cordless Handset

« on: January 30, 2014, 04:25:11 PM »

I'm working with 2 5610 cordless handsets and the IPDECT stand. When the user places a call and the call is answered neither person can hear anything, however if they hang up and call right back the call goes through fine. We have 30+ Mitel phones and this problem only appears on the cordless phones. Mitel is trying to say is our Sophos UTM firewall, which is outright bull***Censored***, they want to replace our Sophos with a sonicwall, but we are refusing to let them.

Does anyone have any idea what could be causing this?